konfigur dan instal snmp
Install / configure SNMP solaris 10
Check package SNMP
Pkginfo –l SUNWsmagt
Bila tidak ada, lakukan install!!!
pkgadd –d {dependencies}
pkgadd –d {package SNMP Solaris}
Install create snmp file
./snmpconf –i pada directory /usr/sfw/bin
Lakukan Konfigurasi
Select the file type you wish to create:
(you can create more than one as
you run this program)
1: snmpd.conf
2: snmptrapd.conf
3: snmp.conf
Other options: quit
Select File: 1
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: 1
Section: Access Control Setup
Description:
This section defines who is allowed to talk to your running
snmp agent.
Select from:
1: a SNMPv3 read-write user
2: a SNMPv3 read-only user
3: a SNMPv1/SNMPv2c read-only access community name
4: a SNMPv1/SNMPv2c read-write access community name
Other options: finished, list
Select section: 3
Configuring: rocommunity
Description:
a SNMPv1/SNMPv2c read-only access community name
arguments: community [default|hostname|network/bits] [oid]
The community name to add read-only access for: visxl
The hostname or network address to accept this community name from [RETURN for all]:
The OID that this community should be restricted to [RETURN for no-restriction]:
Finished Output: rocommunity visxl
Section: Access Control Setup
Description:
This section defines who is allowed to talk to your running
snmp agent.
Select from:
1: a SNMPv3 read-write user
2: a SNMPv3 read-only user
3: a SNMPv1/SNMPv2c read-only access community name
4: a SNMPv1/SNMPv2c read-write access community name
Other options: finished, list
Select section: finished
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: 3
Section: Monitor Various Aspects of the Running Host
Description:
The following check up on various aspects of a host.
Select from:
1: Check for processes that should be running.
2: Check for disk space usage of a partition.
3: Check for unreasonable load average values.
4: Check on the size of a file.
Other options: finished, list
Select section: 3
Configuring: load
Description:
Check for unreasonable load average values.
Watch the load average levels on the machine.
load [1MAX=12.0] [5MAX=12.0] [15MAX=12.0]
1MAX: If the 1 minute load average is above this limit at query
time, the errorFlag will be set.
5MAX: Similar, but for 5 min average.
15MAX: Similar, but for 15 min average.
The results are reported in the laTable section of the UCD-SNMP-MIB tree
Enter the maximum allowable value for the 1 minute load average: 12
Enter the maximum allowable value for the 5 minute load average: 12
Enter the maximum allowable value for the 15 minute load average: 12
Finished Output: load 12 12 12
Section: Monitor Various Aspects of the Running Host
Description:
The following check up on various aspects of a host.
Select from:
1: Check for processes that should be running.
2: Check for disk space usage of a partition.
3: Check for unreasonable load average values.
4: Check on the size of a file.
Other options: finished, list
Select section: finished
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: 4
Section: Agent Operating Mode
Description:
This section defines how the agent will operate when it
is running.
Select from:
1: Should the agent operate as a master agent or not.
2: The system user that the agent runs as.
3: The system group that the agent runs as.
4: The IP address and port number that the agent will listen on.
Other options: finished, list
Select section: 4
Configuring: agentaddress
Description:
The IP address and port number that the agent will listen on.
By default the agent listens to any and all traffic from any
interface on the default SNMP port (161). This allows you to
specify which address, interface, transport type and port(s) that you
want the agent to listen on. Multiple definitions of this token
are concatenated together (using ‘:’s).
arguments: [transport:]port[@interface/address],…
Enter the port numbers, etc that you want the agent to listen to: 33161
Finished Output: agentaddress 33161
Section: Agent Operating Mode
Description:
This section defines how the agent will operate when it
is running.
Select from:
1: Should the agent operate as a master agent or not.
2: The system user that the agent runs as.
3: The system group that the agent runs as.
4: The IP address and port number that the agent will listen on.
Other options: finished, list
Select section: finished
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: 5
Section: System Information Setup
Description:
This section defines some of the information reported in
the “system” mib group in the mibII tree.
Select from:
1: The [typically physical] location of the system.
2: The contact information for the administrator
3: The proper value for the sysServices object.
Other options: finished, list
Select section: 1
Configuring: syslocation
Description:
The [typically physical] location of the system.
Note that setting this value here means that when trying to
perform an snmp SET operation to the sysLocation.0 variable will make
the agent return the “notWritable” error code. IE, including
this token in the snmpd.conf file will disable write access to
the variable.
arguments: location_string
The location of the system: jakarta
Finished Output: syslocation jakarta
Section: System Information Setup
Description:
This section defines some of the information reported in
the “system” mib group in the mibII tree.
Select from:
1: The [typically physical] location of the system.
2: The contact information for the administrator
3: The proper value for the sysServices object.
Other options: finished, list
Select section: finished
The configuration information which can be put into snmpd.conf is divided
into sections. Select a configuration section for snmpd.conf
that you wish to create:
1: Access Control Setup
2: Extending the Agent
3: Monitor Various Aspects of the Running Host
4: Agent Operating Mode
5: System Information Setup
6: Trap Destinations
Other options: finished
Select section: finished
I can create the following types of configuration files for you.
Select the file type you wish to create:
(you can create more than one as you run this program)
1: snmpd.conf
2: snmptrapd.conf
3: snmp.conf
Other options: quit
Select File: 3
The configuration information which can be put into snmp.conf is divided
into sections. Select a configuration section for snmp.conf
that you wish to create:
1: Default Authentication Options
2: Debugging output options
3: Textual mib parsing
4: Output style options
Other options: finished
Select section: 1
Section: Default Authentication Options
Description:
This section defines the default authentication
information. Setting these up properly in your
~/.snmp/snmp.conf file will greatly reduce the amount of
command line arguments you need to type (especially for snmpv3).
Select from:
1: The default port number to use
2: The default snmp version number to use.
3: The default snmpv1 and snmpv2c community name to use when needed.
4: The default snmpv3 security name to use when using snmpv3
5: The default snmpv3 context name to use
6: The default snmpv3 security level to use
7: The default snmpv3 authentication type name to use
8: The default snmpv3 authentication pass phrase to use
9: The default snmpv3 privacy (encryption) type name to use
10: The default snmpv3 privacy pass phrase to use
Other options: finished, list
Select section: 1
Configuring: defaultport
Description:
The default port number to use
This token specifies the default port number you want packets to
be sent to and received from.
override: with -p on the command line.
arguments: portnum
Enter the default port number to use: 33161
Finished Output: defaultport 33161
Section: Default Authentication Options
Description:
This section defines the default authentication
information. Setting these up properly in your
~/.snmp/snmp.conf file will greatly reduce the amount of
command line arguments you need to type (especially for snmpv3).
Select from:
1: The default port number to use
2: The default snmp version number to use.
3: The default snmpv1 and snmpv2c community name to use when needed.
4: The default snmpv3 security name to use when using snmpv3
5: The default snmpv3 context name to use
6: The default snmpv3 security level to use
7: The default snmpv3 authentication type name to use
8: The default snmpv3 authentication pass phrase to use
9: The default snmpv3 privacy (encryption) type name to use
10: The default snmpv3 privacy pass phrase to use
Other options: finished, list
Select section: 2
Configuring: defversion
Description:
The default snmp version number to use.
override: with -v on the command line.
arguments: 1|2c|3
Enter the default snmp version number to use (1|2c|3): 1
Finished Output: defversion 1
Section: Default Authentication Options
Description:
This section defines the default authentication
information. Setting these up properly in your
~/.snmp/snmp.conf file will greatly reduce the amount of
command line arguments you need to type (especially for snmpv3).
Select from:
1: The default port number to use
2: The default snmp version number to use.
3: The default snmpv1 and snmpv2c community name to use when needed.
4: The default snmpv3 security name to use when using snmpv3
5: The default snmpv3 context name to use
6: The default snmpv3 security level to use
7: The default snmpv3 authentication type name to use
8: The default snmpv3 authentication pass phrase to use
9: The default snmpv3 privacy (encryption) type name to use
10: The default snmpv3 privacy pass phrase to use
Other options: finished, list
Select section: 3
Configuring: defcommunity
Description:
The default snmpv1 and snmpv2c community name to use when needed.
If this is specified, you don’t need to include the community
name as an argument to the snmp applications.
override: with -c on the command line.
arguments: communityname
Enter the default community name to use: vis
Finished Output: defcommunity vis
Section: Default Authentication Options
Description:
This section defines the default authentication
information. Setting these up properly in your
~/.snmp/snmp.conf file will greatly reduce the amount of
command line arguments you need to type (especially for snmpv3).
Select from:
1: The default port number to use
2: The default snmp version number to use.
3: The default snmpv1 and snmpv2c community name to use when needed.
4: The default snmpv3 security name to use when using snmpv3
5: The default snmpv3 context name to use
6: The default snmpv3 security level to use
7: The default snmpv3 authentication type name to use
8: The default snmpv3 authentication pass phrase to use
9: The default snmpv3 privacy (encryption) type name to use
10: The default snmpv3 privacy pass phrase to use
Other options: finished, list
Select section: finished
The configuration information which can be put into snmp.conf is divided
into sections. Select a configuration section for snmp.conf
that you wish to create:
1: Default Authentication Options
2: Debugging output options
3: Textual mib parsing
4: Output style options
Other options: finished
Select section: 3
Section: Textual mib parsing
Description:
This section controls the textual mib parser. Textual
mibs are parsed in order to convert OIDs, enumerated
lists, and … to and from textual representations
and numerical representations.
Select from:
1: Specifies directories to be searched for mibs.
2: Specifies a list of mibs to be searched for and loaded.
3: Loads a particular mib file from a particualar path
4: Should errors in mibs be displayed when the mibs are loaded
5: Should warnings about mibs be displayed when the mibs are loaded
6: Be strict about about mib comment termination.
7: Should underlines be allowed in mib symbols (illegal)
8: Force replacement of older mibs with known updated ones
Other options: finished, list
Configuring: mibdirs
Description:
Specifies directories to be searched for mibs.
Adding a ‘+’ sign to the front of the argument appends the new
directory to the list of directories already being searched.
arguments: [+]directory[:directory…]
Enter the list of directories to search through for mibs: /usr/local/share/snmp/mibs (package from freeware) atau /etc/sma/snmp/mibs (package from sun)
Finished Output: mibdirs /usr/local/share/snmp/mibs
Section: Textual mib parsing
Description:
This section controls the textual mib parser. Textual
mibs are parsed in order to convert OIDs, enumerated
lists, and … to and from textual representations
and numerical representations.
Select from:
1: Specifies directories to be searched for mibs.
2: Specifies a list of mibs to be searched for and loaded.
3: Loads a particular mib file from a particualar path
4: Should errors in mibs be displayed when the mibs are loaded
5: Should warnings about mibs be displayed when the mibs are loaded
6: Be strict about about mib comment termination.
7: Should underlines be allowed in mib symbols (illegal)
8: Force replacement of older mibs with known updated ones
Other options: finished, list
Select section: finished
The configuration information which can be put into snmp.conf is divided
into sections. Select a configuration section for snmp.conf
that you wish to create:
1: Default Authentication Options
2: Debugging output options
3: Textual mib parsing
4: Output style options
Other options: finished
Select section: finished
I can create the following types of configuration files for you.
Select the file type you wish to create:
(you can create more than one as you run this program)
1: snmpd.conf
2: snmptrapd.conf
3: snmp.conf
Other options: quit
Select File: quit
Jalankan file installer
./snmpd agar konfigurasi full path pada directory /usr/sfw/sbin/ atau /usr/local/sbin (pada package freeware)
Check port SNMP
Netstat –a |grep 33161
Check configuration bila terjadi kesalahan dalam konfigurasi
/etc/sma/snmp/snmpd.conf atau /usr/local/share/snmp/snmpd.conf
/etc/sma/snmp/snmp.conf atau /usr/local/share/snmp/snmp.conf
Live upgrade solaris
live_upgrade adalah salah satu fitur dari OS solaris yang mampu memaintain beberapa “image” dalam satu system. Image disini dimaksudkan sebagai boot environment atau BE yang mewakili seset OS dan software aplikasi. Tiap BE bisa mengandung OS yang berbeda ataupun aplikasi yang berbeda.
pada suatu system yang menggunkaan software live upgrade. apabila ada suatu konfigurasi dalam current BE dan mengalami kegagalan anda bisa mengambil BE yang nonaktif, dan dengan mudah mem-fall back
Berikut adalah salah satu fungsi yang bisa dijalankan oleh live upgrade
o Anda dapat membuat satu atau lebih copy dari sistem yang sedang running
o Anda dapat meng-upgrade OS versi baru pada BE baru,unutk mengaktifkan anda dapatmem-booting BE yang baru. dan apabila suatu saat anda pun dapat mem-fall back ke solaris versi lama.
o Anda dapat menginstal aplikasi atau paket OS atau pun patch pada setiap BE
o Anda dapat pula mensplit dan menggabungkan filesystem pada BE yang baru
contohnya, anda dapat memsiahkan /usr, /var, dan /opt dari / dan meletakan menjadi partisi sendiri begitupun sebaliknya ada dapat menggabungkan menjadi satu parisi /
o anda dapat me-mount beberapa atau semua filesystem dari BE yang tidak aktif, membandingkan file dari tiap BE, menghapus atau mengubah nama BE, dan melakukan tugas administratif yang lain
berikut adalah sekumpulan cara-cara dalam menggunakan software live upgrade :
1. anda dapat membuat new BE menggunakan lucreate. pada saat membuat BE baru pada suatu sistem. anda harus mendisain BE yang sedang berjalan dengan memberikan nama. gunakan nama dan slice device yang digunakan unutk BE baru. command lucreate dapat meng-copy isi dari BE yang sedang berjalan ke BE baru
2. dengan luupgrade, anda dapat meng-upgrade versi OS pada BE yang baru atau BE yang tidak aktif
3. dengan luactive anda dapat membuat BE yang baru go production (bootable), sehingga pada saat reboot nanti BE yang baru akan prodiction
4. dengan lucompare, anda dapat membandingan system file pada BE yang berbeda
5. dengan lumount, anda dapat memount filesystem dari BE yang tidak aktif, diaktifkan untuk membuat perubahan, dan dapat dikembalikan dengan luumount
6. ketika dalam mem-booting new BE mengalami beberapa kegagalan dan error anda dapat mem-fallback ke BE sebelumnya dengan luactivate
berikut adalah summary dari command2 dalam live upgrade
lu FMLI interface unutk membuat dan administratif BE
luactivate mendisain BE agar BE siap menjadi system setelah di reboot
lucancel menggagalkan jadawal operasi sebelumnya
lucompare membandingkan isi dari dua BE
lucreate membuat BE
lucurr menampilkan BE yang berjalan saat ini
ludelete menghapus BE.
ludesc menambah atau merubah deskripsi BE
lufslist me-list filesystem pada BE
lumake membuat kembali BE berdasarkan BE yang sedang berjalan
lumount, luumount mount, unmount filesistem BE tertentu
lurename merubah nama BE.
lustatus melihat semua BE dalam system , report apakah aktif atau tidak, yang akan aktif pada reboot kedepan, dll
luupgrade upgrade OS dan install software aplikasi pada BE
membuat user di solaris
untuk membuat user dalam solaris kita dapat menggunakan dengan cara
useradd -u <id_user> -g <id_group> -d <direktori tempat user [rumahnya user]> -m -c “<commend>” -s <shell> <nama_user>
id_user dapat anda gunakan bebas asal tidak ada yang pernah menggunakan (mau mengecek bisa dilihat di /etc/passwd) mulai dari angka 1-999999~
id_group dapat anda masukkan angka yang sudah terdaftar pada /etc/group atau anda bisa membuat baru, untuk membuat baru :
groupadd -g <id_group yang diminta> <nama_group>
untuk menempatkan direktori, anda bisa bebas menentukkan. bila direktori tersebut belum ada maka perlu ada command -m setelah path direktori. tetapi jika sudah ada tanpa command -m
di tempat “command” anda bisa bebas menulis, ini digunakan untuk deskripsi dari suatu nama (nama lengkap,fungsi,jabatan dll)
anda bisa memilih layar shell yang digunakan oleh user bisa /bin/bash, /bin/ksh, /bin/sh dll setiap layar shell memiliki kelebihan dan kekurangan masing2 tergantung kecocokan anda
command useradd dijalankan akan mencatat :
/etc/passwd
/etc/shadow
jadi tanpa menjalankan useradd dengan hanya mengedit dua file diatas pun bisa, tetapi unutk password dan direktori anda harus membuat lagi secara manual.
bila dalam perjalanan membuatan user mengalami kesalahan dan anda ingin membetulkan anda dapat merubah opetion diatas dengan menggunakan comand usermod.
untuk mengganti group
usermod -g <id_group yang diinginkan> <nama_user>
untuk mengganti direktori
usermod -d <full path direktori> <nama user> –> jika direktori sudah tersedia
usermod -d <full path direktori> -m <nama user>
untuk mengganti shell
usermod -s <layar shell> <nama_user>
kesumua perubahan diatas dapat anda lakukan hanya dengan mengedit /etc/passwd
semoga bermanfaat
Share CDROM/FS di solaris
untuk men-share direktori/CDROM antar unix:
From Server :
1. masukan CDROM, atau pilih direktori yang akan di-share contoh ”/usr/share/man”
2. yakinkan bahwa nfs daemon berjalan
ps -ef |grep nfs daemon 288 1 0 May 18 ? 0:00 /usr/lib/nfs/statd daemon 284 1 0 May 18 ? 0:00 /usr/lib/nfs/nfs4cbd daemon 287 1 0 May 18 ? 0:14 /usr/lib/nfs/nfsmapid daemon 301 1 0 May 18 ? 0:00 /usr/lib/nfs/lockd root 445 1 0 May 18 ? 0:00 /usr/lib/nfs/mountd daemon 447 1 0 May 18 ? 0:00 /usr/lib/nfs/nfsd jika tidak ada jalan kan serv icenya svcadm enable svc:/network/nfs/server:default –> solaris 10 /etc/init.d/nfs.server start –> solaris 8/93. Share CDROM / direktori
#share -F nfs -o ro /CDROM
atau
#share -F nfs -o ro /usr/share/man
4. cek sharing-an
# share
– /usr/share/man rw “”
From Client :
1. Cek share CDROM/FS dari NFS server
# dfshares <hostname or IP address yang men-share>
2. Buat direktori untuk NFS mount point
3. Mount NFS CDROM/FS menggunakan direktori yang baru dibuat
#mount -F nfs -o ro <hostname or IP Address>:/CDROM /<nama direktori yang kita buat>
4. Check apakah nfs FS/CDROM sudah di mount
# df –k
Interface Setting to be Forced Full Duplex and 100 MBps
Terdapat dua cara untuk melakukan perubahan setting full duplex interface, yakni dengan cara mengedit /etc/system (butuh restart) atau dg menggunakan command ndd (bisa dilakukan on the fly). Misalkan kita akan mengeset interface qfe0 di mesin mob, sehingga diforece full duplex 100MBps. Berikut prosedurenya.
Cara 1 (Edit /etc/system)
Edit /etc/system files it will require restart domain :
* Force network interfaces to 100Mb full duplex
set qfe:qfe_adv_autoneg_cap=0
set qfe:qfe_adv_100T4_cap=0
set qfe:qfe_adv_100fdx_cap=1
set qfe:qfe_adv_100hdx_cap=0
set qfe:qfe_adv_10fdx_cap=0
set qfe:qfe_adv_10hdx_cap=0
Cara 2 (menggunakan command ndd)
Or edit /etc/rc2.d scripts to start interface (qfe/le) in full duplex and 100 Mbps mode . Below is an example for qfe2 :
root@mob # vi S99qfe
“S99qfe” 9 lines, 358 characters
#BDM 05/11/2002 ,force 100Mbps, full duplex on qfe
######## qfe2
ndd -set /dev/qfe instance 2
ndd -set /dev/qfe adv_100T4_cap 0
ndd -set /dev/qfe adv_100fdx_cap 1
ndd -set /dev/qfe adv_100hdx_cap 0
ndd -set /dev/qfe adv_10fdx_cap 0
ndd -set /dev/qfe adv_10hdx_cap 0
ndd -set /dev/qfe adv_autoneg_cap 0
Or we can manually configure on the fly. Below is an example if we want to set qfe0 interface :
root@mob # ndd –set /dev/qfe instance 0
root@mob # ndd -get /dev/qfe \?
? (read only)
transceiver_inuse (read only)
link_status (read only)
link_speed (read only)
link_mode (read only)
ipg1 (read and write)
ipg2 (read and write)
use_int_xcvr (read and write)
pace_size (read and write)
adv_autoneg_cap (read and write)
adv_100T4_cap (read and write)
adv_100fdx_cap (read and write)
adv_100hdx_cap (read and write)
adv_10fdx_cap (read and write)
adv_10hdx_cap (read and write)
autoneg_cap (read only)
100T4_cap (read only)
100fdx_cap (read only)
100hdx_cap (read only)
10fdx_cap (read only)
10hdx_cap (read only)
lp_autoneg_cap (read only)
lp_100T4_cap (read only)
lp_100fdx_cap (read only)
lp_100hdx_cap (read only)
lp_10fdx_cap (read only)
lp_10hdx_cap (read only)
instance (read and write)
lance_mode (read and write)
ipg0 (read and write)
root@mob # ndd -set /dev/qfe adv_100T4_cap 0
root@mob # ndd -set /dev/qfe adv_100fdx_cap 1
root@mob # ndd -set /dev/qfe adv_100hdx_cap 0
root@mob # ndd -set /dev/qfe adv_10fdx_cap 0
root@mob # ndd -set /dev/qfe adv_10hdx_cap 0
root@mob # ndd -set /dev/qfe adv_autoneg_cap 0
If we want to know the result of above commands, please check each of parameter has been changed by issuing below commands :
root@mob # ndd -get /dev/qfe adv_100T4_cap
root@mob # ndd -get /dev/qfe adv_100fdx_cap
root@mob # ndd -get /dev/qfe adv_100hdx_cap
root@mob # ndd -get /dev/qfe adv_10fdx_cap
root@mob # ndd -get /dev/qfe adv_10hdx_cap
root@mob # ndd -get /dev/qfe adv_autoneg_cap
It will produce the same output as the commands executed before.
Current Status qfe2 :
root@mob # ndd -set /dev/qfe instance 2
root@mob # ndd -get /dev/qfe adv_100T4_cap
0
root@mob # ndd -get /dev/qfe adv_100fdx_cap
1
root@mob # ndd -get /dev/qfe adv_100hdx_cap
0
root@mob # ndd -get /dev/qfe 10fdx_cap
0
root@mob # ndd -get /dev/qfe adv_10hdx_cap
0
root@mob # ndd -get /dev/qfe adv_autoneg_cap
0
root@mob #
Note :
Untuk melakukan perubahan ini, beri tahu user, kalau koneksi akan terputus, saat ekseskusi. The worst case, terkadang, koneksi hilang sama sekali. Untuk ini, lakukan koordinasi dgn Engineer Datacom , untuk memastikan setting port di Switch sudah Full duplex dan 100MBps. Setting di switch ini harus dilakukan sebelum, kita lakukan perubahan menggunakan command “ndd”.
konfigure cronjob in solaris
cronjob adalah semacam cara untuk menjalankan job2 atau perintah2 dengan terjadwal
setiap user dapat mengaktifkan cronjob dengan mengkonfigure cron.allow file
untuk konfigure di solaris
masukkan user pada cron.allow file (create jika belum ada) pada direktori /etc/cron.d
contohnya :
root@mauk # cat /etc/cron.d/cron.allow
root
issuud01
batman
biar terupdate dengan server restart service-nya
untuk solaris 10
svcadm restart cron
svcs -a |grep cron –> pastikan service cron online
untuk solaris 8 dan solaris 9
ps -ef |grep cron –> cek apakah cron service berjalan
/etc/init.d/cron stop
/etc/init.d/cron start
untuk memasukkan job-job atau perintah dalam crontab, kita dapat melakukan command2 berikut :
crontab -l –> untuk melihat job pada crontab
crontab -e –> unutk mengedit job pada crontab
jika pada saat menjalankan crontab -l atau crontab -e tidak tampil lakukan setting berikut :
export EDITOR=vi –> jika hal ini masih terdapat error, lakukan
export VISUAL= –> ini option jika setting diatas tidak berhasil.
contoh crontab
root@console3A # crontab -l
#ident "@(#)root 1.21 04/03/23 SMI"
#
# The root crontab should be used to perform accounting data collection.
#10 3 * * * /usr/lib/krb5/kprop_script ___slave_kdcs___
05,15,25,35,45,55 * * * * /usr/local/ADMIN/scripts/vxprint_disable > /dev/null 2>&1
0 1 * * * /usr/local/ADMIN/scripts/adi/server_info_all.pl > /dev/null 2>&1
1 0 * * 0 /usr/local/ADMIN/scripts/adi/backup_fs_conf.pl > /dev/null 2>&1
aturan
tanda # berarti job tersebut dimatikan dari cronjob
pada job terakhir 1 0 * * 0 <job> <log> berarti setiap detik kesatu pada jam 00 setiap hari minggu akan menjalankan job tersebut dan log hasil pekerjaan di buang ke null
angka pertama menndakan tiap detik
angka kedua menandakan tiap jam
angka ketiga menandakan tiap tanggal
angka keemapat menandakan tiap bulan
angka kelima menandakan tiap hari, hari ahad dengan angka 0
semoga bermanfaat, jika ada masalah dan perlu guide
Konfigur samba di solaris
samba adalah suatu aplikasi yang digunakan oleh unix base agar file2 atau direktori dapat ter-share dengan personal komputer (PC) sehingga file2 atau direktori tersebut dapat kita baca dan ubah.
Biasanya samba sudah ada di instalasi Solaris 10 tepatnya pada seri Solaris 3/05 is 3.0.4 dan Solaris 1-06 is 3.0.11, untuk melihat seri tersebut anda bisa menjalankan commmad :
#/usr/sfw/sbin/smbd -V
untuk solaris 8 dan solaris 10 anda harus menginstall package pada site berikut
untuk yang sudah install SAMBA 3.0.4 or 3.0.11, anda bisa lanjutakan dengan konfigurasi sebagai berikut :
a) file konfigurasi (jika tidak ada, anda bisa buat):
#/etc/sfw/smb.conf
b) buat folder yang akan di-share dan buat permission [jika sudah punya anda hanya configure permissionnya saja] : (e.g.)
#mkdir /disk2
chmod 777 /disk2
chmod +t /disk2
chown sys /disk2
chgrp sys /disk2
c) contoh smb.conf file:
[global]
workgroup = WORKGROUP
security = SHARE
preferred master = No
local master = No
domain master = No
ldap ssl = no
hosts allow = localhost, <ip pc mu>, <sabnet/IP yang dapat membaca share-an>
hosts deny = All
[disk2]
comment = Disk 2 storage
path = /disk2
read only = No
guest ok = Yes
[disk1]
comment = Disk 1 storage
path = /disk1
read only = No
guest ok = Yes
[respaldo]
comment = Backup
path = /backup
read only = No
guest ok = Yes
browseable = No
d) test konfigurasi:
# /usr/sfw/bin/testparm
—–> jika terjadi error seperti
/usr/sfw/lib/codepages/upcase.dat not found
bisa diperbaiki dengan (berlaku untuk semua error file yang sama)
ln -s ./codepages/upcase.dat upcase.dat jalankan testparam dan pastikan tidak ada error
e) Edit /etc/services and /etc/inetd.conf
* Untuk /etc/services, setelah line dibawah ini:
ldaps 636/udp # LDAP protocol over TLS/SSL (was sldap)
masukkan line berikut:
swat 901/tcp # Samba swat
* Untuk /etc/inetd.conf tambahkan 2 line file terahir:
Solaris 10:
netbios-ssn stream tcp nowait root /usr/sfw/sbin/smbd smbd
swat stream tcp nowait root /usr/sfw/sbin/swat swat
untuk koneksi swat , jalankan web browser pada PC anda dengan cara:http://<localhost/ip unix yang men-share>:901
anda dapat pula mengedit smb.conf file pada web browser.
jalankan command berikut untuk mengupdate konfigurasi pada SMF karena pada /etc/inet.d.conf telah mengalami perubahan:
# inetconv -i/etc/inet/inetd.conf
silakan mencoba…. jika masih ada masalah bisa hubungi aku
Guide online network with shared shell
if you have any problem with solaris, veritas and storage I could help you (if I have any time to solve your problem). just email to me or YM on shofwan@yahoo.com.
before you ask me to guide you. you must follow this prosedure :
1. you have account in sun domain
2. surely your account have installed Java (minimum required version is 1.4.2. Both Java SE 5 (1.5.0) and Java SE 6 (1.6.0) are supported)
3. Lunch shared shell for connect to me (for detail information you can visit shared shell )
4. YM or email me for assistance
Membuat filesystem dengan veritas volume manager
1. cek diskgroup yang mempunyai space kosong
root@avatar # vxdg free
GROUP DISK DEVICE TAG OFFSET LENGTH FLAGS
localdg localdg01 c2t6d180s2 c2t6d180 23202720 5243040 –
prmarc prmarc253 c2t6d253s2 c2t6d253 226494720 1105920 –
prmdb prmdb002 c2t6d2s2 c2t6d2 272626560 10467360 –
prmfs prmfs245 c2t6d245s2 c2t6d245 188743680 38856960 –
— bila segan menghitung dan dirasa banyak digit di kolom enam lakukan hal dibawah, tapi jika mau menghitung see prosedur penambahan space
2. cek ukuran space kosong diskgroup
root@avatar # vxassist -g <nama_diskgroup> maxsize
Maximum volume size: 151040000 (73750Mb)
–dalam diskgroup ini terdapat sekitar space kosong 72 G
3. membuat volume
root@avatar # vxassist -g prmfs make <nama_volume> <size=xG,xM,xk>
4. membuat filesystem
root@avatar # mkfs -F vxfs <raw disk volume>
version 4 layout
83886080 sectors, 5242880 blocks of size 8192, log size 128 blocks
unlimited inodes, largefiles supported
5242880 data blocks, 5242528 free data blocks
160 allocation units of 32768 blocks, 32768 data blocks
5. Membuat direktori
root@avatar # mkdir <nama_direktori>
6. Set permission sesuai yang diinginkan
root@avatar # chmod 775 <nama_direktori>
7. mounting disk volume agar menjadi sebuah filesystem
root@avatar # mount -F vxfs <path_disk_volume> <direktori>
8. Cek filesystem
root@avatar # df -k | grep <nama direktori>
/dev/vx/dsk/prmfs/backuplog 41943040 2528 41612864 1% <nama direktori>
Prosedur penambahan space filesystem dengan veritas volume manager
1. check diskspace menggunakan veritas volume manager
#vxdg free (list diskspace kosong di semua diskgroup)
#vxdg -g <nama_diskgroup> free (list diskspace kosong di diskgroup tertentu)
* kolom #6 (length), informasi diskspace kosong (sectors)
size(GB)=sector/2/1024/1024
* kolom #1, nama diskgroup
* kolom #2, nama disk
2. menambah/mengurangi filesystem secara online menggunakan Veritas Volume manager
#vxprint -Aht (dijelaskan informasi tentang plex, subdisk, disk, volume, diskgroup in details)
#vxprint -pt (hanya plex)
#vxprint -vt (hanya volume)
#vxprint -dt (hanya disk)
#vxprint -st (hanya subdisk)
#vxprint -g <diskgroup> -Aht (menjelaskan informasi hanya diskgroup tertentu)
Check Besarnya disk yg free :
# vxassist –g [nama_diskgroup] maxsize
namba space (sebesar) :
#vxresize -F vxfs -x -g <nama_diskgroup> volume_name +<10m/10g/12342434435>
nambah space menggunakan disk2 tertentu :
#vxresize -F vxfs -x -g <nama_diskgroup> volume_name +<10m/10g/12342434435> disk1 disk2 …
mengurangi space (sebesar) :
#vxresize -F vxfs -s -g <diskgroup_name> volume_name -<10m/10g/12342434435>
untuk merubah ukuran filesystem, yakinkan terdapat space kosong sedikitnya 5%