Taking explorer on SUN machines

If your system is a SunFire midframe server (38x0, 48x0, or 68x0 model), use this command to include data from the system console:

# /opt/SUNWexplo/bin/explorer -q -e -w default,scextended

If your system uses an alom (advanced lights out manager), some additional data can be collected. Systems that use that include:
Sun Fire V210,V240,V250,V245,V440,V440R,V445 Server Netra 240,440 (AC) Server
Use this command:

# /opt/SUNWexplo/bin/explorer -q -e -w default,alomextended

If your system uses T1 processors (system type starts with T, and uname -a command will say architecture is sun4v), use this command:

# /opt/SUNWexplo/bin/explorer -q -e -w default,Tx000

For any other model of Sun system, use this command:

# /opt/SUNWexplo/bin/explorer -q -e

The -q option suppresses printing of error messages during the run.
The -e option prevents explorer from automatically sending email.
The -w scextended option collects data from the system console (sc).

If you cannot run explorer for some reason, here are the most important things to collect:

/var/adm/messages or messages.# file for the time when the crash was taken. Be sure to include any messages that occurred just before panic.

/etc/system file

output of the showrev -p command, for a list of patches on system

Detailed hardware configuration of the system. To determine which command to use, issue the command uname -m to find the system architecture type.

If it is sun4u, send the output of this command:
/usr/platform/sun4u/sbin/prtdiag -v
If it is sun4v, send the output of this command:
/usr/platform/sun4v/sbin/prtdiag -v
Output of this command:
prtconf -vp

If your system is a SunFire midframe server (38x0, 48x0, or 68x0 model), include the output of these commands to collect data from the system console:

showlogs -v
showlogs -d showboards -v showplatform -v showenvironment -v showsc -v

NFS mount option for Oracle Data Pump

mount -o hard,rw,noac,rsize=32768,wsize=32768,suid,proto=tcp,vers=3 -F nfs NFSSERVER:/FILESYTEM /SOMEFILESYSTEM

Changing prompt SUN System Controller

sc> setsc sc_cliprompt testing-sc

testing-sc>

Remove iscsi targets in centOS

#service iscsi stop
#iscsiadm -m node -T iqn.NNNNNNNNNNNNNNNNNNNNNNNNNNNNNN --op=delete
#service iscsi start

Crash Dump

The hardware watchdog mechanism can automatically reboot the system in case the system hangs. This can be done with or without first generating an automated crash dump file. As superuser, do one of the following:


•To reboot without generating an automated crash dump file, type:


# eeprom error-reset-recovery=boot



•To reboot and generate an automated crash dump file, type:


# eeprom error-reset-recovery=sync

Adding SWAP space in ZFS Root filesystem

If you want additional space
# zfs create -V 2G rpool/swap1
# swap -a /dev/zvol/dsk/rpool/swap1
# swap -l

If you want to delete old swap space and add new one

# swap -d /dev/zvol/dsk/rpool/swap
# swap -l (To verify old swap is deleted)
# zfs set volsize=4G rpool/swap
# swap -a /dev/zvol/dsk/rpool/swap
# swap -l

Upgrade firmware on one of the IOM in storage Array

-> We replaced IOM.A on the Storage Arrays and there is mismatch in IOM's

Name Model Current Baseline
Tray.86.IOM.A LCSM100_E 0196 0196
Tray.86.IOM.B LCSM100_E 0196 0196
Tray.87.IOM.A LCSM100_E 0166 0196
Tray.87.IOM.B LCSM100_E 0196 0196

Login to the server which Common Array Manager installed

execute csmservice command (usually located under fms/bin directory)

./csmservice -s
Enter array name

it will give options (Enter 5 which is download IOM firmware)

Enter path to IOM formware: /esm0196.esm

Available components for install (Select the IOM from the list )