Smiertx Site

Shows the ethernet address arp table # arp -a Delete a stale ethernet entry for host xhost # arp -d xhost Reports disk space used in Kilobytes # du -k Reports only total disk space used in Kilobytes # du -sk Tells you how big the / files are in reverse order # du -ad / | sort -nr Mount an ISO 8660 CDROM # /bin/mount -F hsfs -o ro /dev/sr0 /cdrom Disk geometry and partitioning info # prtvtoc /dev/rdsk/c0t0d0s2 Zero's out the file without breaking pipe # cat /dev/null > filename Make a mirror image of your boot disk # dd if=/dev/rdsk/... of=/dev/rdsk/... bs=4096 Check a UFS filesystem # fsck -F ufs /dev/rdsk/cxtxdxsx Check a UFS filesystem with auto-answer "yes" # fsck -F ufs -y /dev/rdsk/cxtxdxsx Check using an alternate super block # fsck -F ufs -o b=97472 /dev/rdsk/cxtxdxsx Verify reconfigurable hardware resources # cfgadm Display kernel module information # /usr/sbin/modinfo Load a kernel module # /usr/sbin/modload Unload a kernel module # /usr/sbin/modunload -i Tune

Show I/O error solaris # iostat -eE ---- errors --- sd0 0 0 0 0 ssd0 0 0 0 0 ssd1 0 0 0 0 nfs2 0 0 0 0 sd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: TOSHIBA Product: ODD-DVD SD-C2732 Revision: 1051 Serial No: Size: 0.00GB <0 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 ssd0 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: FUJITSU Product: MAT3073F SUN72G Revision: 0602 Serial No: 0527B08LLN Size: 73.40GB <73400057856 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Failure Analysis: 0 ssd1 Soft Errors: 0 Hard Errors: 0 Transport Errors: 0 Vendor: FUJITSU Product: MAT3073F SUN72G Revision: 0602 Serial No: 0526B08BHH Size: 73.40GB <73400057856 bytes> Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0 Illegal Request: 0 Predictive Fai

For file descriptor, add this lines to /etc/system # vi /etc/system ---------------- set rlim_fd_max=8192 #(def: 1024, Process open file descriptors limit; should account for the expected load, for the associated sockets, files, pipes if any) set rlim_fd_cur=8192 #(def: 256, Process open file descriptors limit; should account for the expected load, for the associated sockets, files, pipes if any) set sq_max_size=0 #(Controls streams driver queue size; setting to 0 makes it infinity so the performance runs wont be hit by lack of buffer space) set tcp:tcp_conn_hash_size=8192 #(The connection hash table keeps all the information for active TCP connections) set autoup=60 set pcisch:pci_stream_buf_enable=0 ----------------- You should reboot your server to make changes.

Setting TCP kernel parameter solaris How to know your TCP current kernel parameter # /usr/sbin/ndd -get /dev/tcp tcp_ip_abort_cinterval; 180000 # /usr/sbin/ndd -get /dev/tcp tcp_time_wait_interval; 60000 # /usr/sbin/ndd -get /dev/tcp tcp_conn_req_max_q; 128 # /usr/sbin/ndd -get /dev/tcp tcp_conn_req_max_q0; 1024 # /usr/sbin/ndd -get /dev/tcp tcp_ip_abort_interval; 480000 # /usr/sbin/ndd -get /dev/tcp tcp_keepalive_interval; 7200000 # /usr/sbin/ndd -get /dev/tcp tcp_rexmit_interval_initial; 3000 # /usr/sbin/ndd -get /dev/tcp tcp_rexmit_interval_max; 60000 # /usr/sbin/ndd -get /dev/tcp tcp_rexmit_interval_min; 400 # /usr/sbin/ndd -get /dev/tcp tcp_smallest_anon_port; 32768 # /usr/sbin/ndd -get /dev/tcp tcp_slow_start_initial; 4 # /usr/sbin/ndd -get /dev/tcp tcp_xmit_hiwat; 49152 # /usr/sbin/ndd -get /dev/tcp tcp_recv_hiwat; 49152 # /usr/sbin/ndd -get /dev/tcp tcp_fin_wait_2_flush_interval; 30000 Change your TCP kernel parameter as you want :p /usr/sbin/ndd -set /dev/tcp tcp_ip_abort_cint

Lagi ngga ada yang mo di-post coz lagi hobi ngulik melodinya hide X-Japan ... :p jadi lupa mo ngoprek Linux, Solaris, HP-UX, BIG-IP, Cisco, dll. hehehehe ... Gw nge-fans abiz ama hide coz gaya maennya itu sebagai pionir j-rocks sampe sekarang. Walaupun Yoshiki sebagai leader dari X-Japan sekaligus pencipta mayoritas lagu X-Japan tapi gw salut banget ama hide. Sayang hide uda meninggal 2 mei 1998 akibat "accident" di apartemennya. hiks .. Setiap tahun sampe sekarang, yoshiki menggelar "Tribute to hide" untuk mengenang mantan sohibnya itu. Pink spider alias rambut pink udah jadi trade-marknya dia, kapan ya gw mo nge-cat rambut mirip dia ? berhubung uda panjang neh ... :p List ngulik minggu ini : - Kurenai - Rusty Nail

How to perform SCCP reboot based on https://support.f5.com/kb/en-us/solutions/public/6000/800/sol6836.html This applied on : BIG-IP LTM 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 BIG-IP ASM 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 BIG-IP GTM 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 Link Controller 9.x 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4, 9.3.1, 9.3, 9.2.5, 9.2.4 WebAccelerator 9.4.4, 9.4.3, 9.4.2, 9.4.1, 9.4 The SCCP is a separate sub-system that controls F5 Networks' switch hardware. It may become necessary to reboot the SCCP, if, for example, the installation of a hotfix updates the SCCP firmware package. Rebooting the SCCP F5 Networks recommends performing a clean shutdown of the host system, and reboot the SCCP and host system, by performing the following procedure: 1. Log in to the command line of the BIG-IP system. 2. Reboot the host and SCCP, by typing the following command: # /usr/bin/full_box_reboot Note: The filesys

How to performing SCCP reboot based on https://support.f5.com/kb/en-us/solutions/public/5000/400/sol5471.html This applied to : BIG-IP LTM 9.2.3, 9.2.2, 9.2, 9.1.2, 9.1.1, 9.1, 9.0.5, 9.0.4, 9.0.3, 9.0.2, 9.0.1, 9.0 BIG-IP ASM 9.2.3, 9.2.2, 9.2 BIG-IP GTM 9.2.3, 9.2.2 Link Controller 9.x 9.2.3, 9.2.2 F5 Networks recommends you perform a clean shutdown of the host system, and reboot the SCCP and host system, by performing the following steps: 1.Log in to the command line of the BIG-IP system. 2.Create the /.sccp_hard_reboot file, by typing the following command: # touch /.sccp_hard_reboot 3.Reboot the host and SCCP, by typing the following command: # reboot Note: The /.sccp_hard_reboot file will no longer exist after the system reboots.

activate ethernet interface # ifconfig ce0 plumb # ifconfig ce1 plumb Giving IP Address and IP Multipathing # ifconfig ce0 10.172.75.2 netmask 255.255.255.0 broadcast group ipmp1 up # ifconfig ce1 group ipmp1 up Now we only have 1 IP address ( 10.172.75.2 ). If this setting keep on when system reboot, check all following conf file. # more /etc/hosts 127.0.0.1 localhost 10.172.75.2 server01 # more /etc/netmasks 10.172.75.0 255.255.255.0 #more /etc/defaultrouter 10.172.75.1 # more /etc/hostname.ce0 server01 netmask + broadcast + group ipmp1 up For active-active configuration : # more /etc/hostname.ce1 group ipmp1 up For active-active configuration : # more /etc/hostname.ce1 group ipmp1 standby up Check network interface status for active-active : # ifconfig -a ce0: flags=1000843 mtu 1500 index 4 inet 10.172.75.2 netmask ffffff00 broadcast 10.172.75.255 groupname ipmp1 ether xx:xx:xx:xx:xx:xx ce1: flags=1000843 mtu 1500 index 5 inet 0.0.0.0 netmask ff000000 broadcast 0.255.2

Based on http://docs.sun.com/app/docs/doc/816-4554/emqra?a=view Here the actions : activate ethernet interface # ifconfig ce0 plumb up # ifconfig ce1 plumb up Giving IP Address and IP Multipathing # ifconfig ce0 10.172.75.3 netmask 255.255.255.0 broadcast + group ipmp1 deprecated -failover up \ addif 10.172.75.2 netmask 255.255.255.0 broadcast + failover up # ifconfig ce1 10.172.75.4 netmask 255.255.255.0 broadcast + group ipmp1 deprecated -failover up Now we have 3 IP address, 2 physical ( 10.172.75.3 & 10.172.75.4 ) and 1 virtual ( 10.172.75.2 ). If this setting keep on when system reboot, check all following conf file. # more /etc/hosts 127.0.0.1 localhost 10.172.75.2 server01-vip 10.172.75.3 server01-ce0 10.172.75.4 server01-ce1 # more /etc/netmasks 10.172.75.0 255.255.255.0 #more /etc/defaultrouter 10.172.75.1 # more /etc/hostname.ce0 10.172.75.3 netmask 255.255.255.0 broadcast + group ipmp1 deprecated -failover up \ addif 10.172.75.2 netmask 255.255.255.0

# kmtune Parameter Current Dyn Planned Module Version =============================================================================== NSTRBLKSCHED - - 2 NSTREVENT 50 - 50 NSTRPUSH 16 - 16 NSTRSCHED 0 - 0 STRCTLSZ 1024 - 1024 STRMSGSZ 65535 - 65535 acctresume 4 - 4 acctsuspend 2 - 2 aio_listio_max 256 - 256 aio_max_ops 2048 - 2048 aio_physmem_pct 10 - 10 aio_prio_delta_max 20 - 20 allocate_fs_swapmap 0 - 0 alwaysdump 1 - 1

Verify hardware information on HP RP24XX Procedure: - Execute command: #cstm cstm>sel d 1 cstm>info cstm>wait cstm>il Result: System Information for (xxxxxx) HPUX Model Number......: A500 HPUX Model String......: 9000/800/A500-6X Original Product Number: xxxxx Current Product Number.: xxxx System Serial Number...: xxx Hversion...............: xxxxxxx Sversion...............: xxxxxx Software Capabilities..: xxxxx CPU Information: Number of CPUs in the system = 2

Sometimes we confuse about is a system have an inadequate memory after look after "sar" and "free" command or not. Sar description about memory allocation : Total: how much physical memory the machine has Used: amount of used (kernel + user + buffers + cache) memory Free: how much unallocated memory Shared: how much is shared via shm, mmap, shlibs, etc. Buffers: how much is preallocated to unused kernel buffers Cached: how much is preallocated to unsued filesystem buffer cache free –m description about memory allocation : Used: amount of system memory that is actually in use. This is the first line 'used' - (buffers + cache) Free: amount of memory that isn't actually busy. This is the first line 'free' + buffers + cache. For example : # free -m total used free shared buffers cached Mem: 8007 7989 17 0 120 7053 -/+ buffers/cache: 815 7191 Swap:

SAR (default) command for showing general system reports. sar -u ( it's default, same as if we only run sar without any option) %usr: running UNIX processes ("user time") %sys: processing kernel system calls on behalf of processes ("system time") %wio: sitting around waiting to read/write data (to disks or network devices), as demanded by processes ("waiting for I/O") %idle: just plain doing nothing as there were no processes that demanded the CPU's time ("idle"). if heavy %usr and %sys it may means a poorly written application can consume infinite amounts of CPU resources. If %wio is high, your system is waiting for your I/O subsystems to catch up. You may have a slow disk or array. Check more with iostat.

If you found your BIG-IP system failed to load license or it was on un-configured system accidentally. I found that problem too, and that my opinion about that. Main root causes : 1. SOL7036: Linux uptime counter wrap after 497 days back set to zero. This is not a critical issue. This issue was discovered in 1998, and is due to the 32bit counter overflow. Currently, there is no Linux kernel patch available to resolve this issue. 2. SOL7071: The SCCP kernel driver timer wrap causes an I2C read failure. This is the result of a known issue. A timer wrap within the SCCP kernel occurs after 497 days, and resets the timer to O (zero). The timer wrap causes I2C (Inter-Integrated Circuit bus) driver read/write failures because the I2C is unable to correctly handle the kernel timer wrapping. The SMBus then enters a lockup condition, which causes all subsequent I2C read/write communications to fail until the SCCP is rebooted. As a result, the SCCP cannot gather data from the host system on chass

If you found problem on your BIG-IP 9.2.3 or below version system about chassis fan reporting failure you should not worried too much. We can check with performing this command # b platform PLATFORM INFORMATION -- ------------------- +-> CPU 1 temp 50degC fan speed 10887rpm | | CHASSIS TEMPERATURE | (1) 46degC (2) 42degC (101) -1degC (102) -1degC | | CHASSIS FAN | (101) DOWN! (102) DOWN! (103) DOWN! (104) DOWN! (105) DOWN! | (106) DOWN! | | POWER SUPPLY | (101) active -------------- We also can check at # more /var/log/ltm | grep Chassis -------------- system_check: 010d0005:3: Chassis fan 101: status (0) is bad. -------------- Actually the fan wasn't down, it just a minor bug of BIG-IP, it's code: CR63196. Solutions below : SOL7071: The SCCP kernel driver timer wrap causes an I2C read failure. This is the result of a known issue. A timer wrap within the SCCP kernel occurs after 497 days, and resets the timer