quick notes

if an llt link shows down, you can always inject some traffic through the wire and see if you can catch it on the other side.
We first, on one side of the cluster find out the mac address of our interface, then start a “dlpiping server”
process on it.
# /opt/VRTSllt/getmac /dev/ce:0
/dev/ce:0 08:00:10:A7:1E:DC
# /opt/VRTSllt/dlpiping -s /dev/ce:0
Now, on the other side of the link, on the other server, we query for the mac address in the wire.
# /opt/VRTSllt/dlpiping -c /dev/ce:0 08:00:10:A7:1E:DC
08:00:10:A7:1E:DC is alive
if it says that the mac is alive then we have a good link.

add this to your /etc/multipath.conf:

devices {
## Device attributes for EMC SYMMETRIX
device {
vendor "EMC "
product "SYMMETRIX"
path_grouping_policy multibus
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
path_selector "round-robin 0"
features "0"
hardware_handler "0"
failback immediate
}
## Device attributes for EMC CLARiiON
device {
vendor "DGC"
product "*"
path_grouping_policy group_by_prio
getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
prio_callout "/sbin/mpath_prio_emc /dev/%n"
hardware_handler "1 emc"
features "1 queue_if_no_path"
no_path_retry 300
path_checker emc_clariion
failback immediate
}
}

use:

ssh -V

fcinfo hba-port | grep -i 'port wwn‘

to capture all packets to and from “192.168.5.182” and save the conversation in “snoopy.log”

snoop -d e1000g2 -o snoopy.log -v 192.168.5.182

to view the output

snoop -vi snoopy.log

ipmitool sunoem getval /SYS/product_serial_number

or

omarras01:root# sneep
PX60438194

 

You need to plumb them to see if they have link, so

x=20;dladm show-dev| awk ‘{ print $1 }’  | while read i;do ifconfig $i plumb;((x++)) ;ifconfig $i 100.100.100.$x/24 broadcast + up;done;dladm-show-dev

Initial login to XSCF is usually eis-installer / sun123

Add the super-user account

XSCF> adduser super-user
XSCF> password -e Never super-user
XSCF> password super-user
***For the next command, use the number of domains the server is setup for. Typically, M4000’s use domainadm@1, M5000’s use domainadm@1-2***
XSCF> setprivileges super-user platadm auditadm fieldeng useradm domainadm@1-2

 

For initial access or to reset a lost XSCF password, go to the below link:

http://docs.sun.com/source/819-3601-14/

Under the Access Control section, select XSCF Passwords. You will use the procedure “To Log in Initially to the XSCF Console”

Connect To A Domain’s Console

XSCF> console -d 0  

Send A Break

XSCF> sendbreak -d 0

When a sendbreak fails for a domain, the domin mode secure setting needs to be disabled:

XSCF> setdomainmode -d 0 -m secure=off

Show Hardware Configuration

XSCF> showhardconf

Power Off A Domain

XSCF> poweroff -d 0

Show System Boards And Their Mode

XSCF> showfru -a sb  

Show System Boards In A Domain

XSCF> showboards -v -a  

Configure the XSCF on the network

This assumes you are configuring the lan#0 NIC on xscf#0. Modify as necessary:

XSCF> setnetwork xscf#0-lan#0 -m NETMASK IPADDRESS
XSCF> sethostname xscf#0 HOSTNAME-xscf0
XSCF> sethostname -d DOMAINNAME
XSCF> setroute -c add -n 0.0.0.0 -g DEFAULTGATEWAY xscf#0-lan#0
XSCF> applynetwork
XSCF> rebootxscf

Configure the DSCP Network

If the boot shows DSCP errors and/or the dscp and dcs services are failed in the OS, then SUN didn’t setup the DSCP network in the XSCF like they are supposed to before turning it over to us. This is something we can setup ourselves. Here is a standard setup on an M4000 (other M-Series servers simply increment the IPs by one for the additional domains):

 

      XSCF> setdscp
      DSCP network  [0.0.0.0        ] > 192.168.224.0

      DSCP netmask  [255.255.255.0  ] >

      XSCF address  [192.168.224.1  ] > 192.168.224.1
      Domain #00 address  [192.168.224.2  ] > 192.168.224.2
      Domain #01 address  [192.168.224.3  ] > 192.168.224.3
      Commit these changes to the database? [y|n] : y

Once the setup is complete, then a reboot of the XSCF needs to be performed:

 

      XSCF> rebootxscf

Once the XSCF has rebooted, the domain(s) configured also need to be rebooted:

 

If you do not have configured multipath.conf, but youjust have
the module enabled and no lun blacklisted you can use
this script to generate a multipath.conf:

#!/bin/ksh
echo “multipaths {”
x=0
multipath -l |egrep ‘3600|size’ |gawk ‘ORS=NR%2?””:”n”‘ | awk
‘{ print $1 $2 }’ | sed ‘s/[size=/ /g’ | while read
l;do
W=`echo $l |awk ‘{ print $1 }’`
S=`echo $l |awk ‘{ print $2 }’`
echo ” multipath {”
echo ” wwid $W”
echo ” alias disk${x}_${S}Gb”
echo ” path_grouping_policy failover”
echo ” path_checker readsector0″
echo ” path_selector “round-robin0″”

echo ” failback immediate”
echo ” }”
x=`echo “$x + 1″|bc`
done
echo “}”

Display SP firmware version:

-> version

Get Serial number:

-> show /SYS

Show available CLI commands:

-> show /SP/cli/commands

Display help information about commands and targets

-> help

Connect to host serial console:

-> start /SP/console

Send a break signal:

-> set /HOST send_break_action=break

 

 

List users with open sessions to the system console (who is using the console?):

-> show /SP/sessions

Terminate a server console session started by another user:

-> stop /SP/console

Power on host:

-> start /SYS

Power off host:

-> stop /SYS

Reset host:

-> reset /SYS

Reset ILOM:

-> reset /SP

Enable locate LED:

-> set /SYS LOCATE=on

Disable locate LED:

-> set /SYS LOCATE=off

Add a local user account:

-> create /SP/users/username password=password role=[administrator|operator]

Displaying Users:

-> show /SP/users