| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 1353629.1 : Sun Blade T6320 How To's
In this Document
Applies to:Sun Blade T6320 Server Module - Version Not Applicable and laterInformation in this document applies to any platform. PurposeThis document lists the T6320 How Tos. DetailsHow to confirm if you have ldom's configured and to find out where the memory is binded.Answer: By CharlesForgues 19 Nov 2010 16:25:10
How do I restore the H/W RAID configuration after a REM (RAID Expansion Module) replacement?Answer: The metadata on the physical disks that make up the volume have all the information needed. As long as the disks are cold-swapped (i.e. the blade is powered down, the REM swapped, and the blade powered back up) there should be no problem. The volume will appear in OBP as a foreign volume that needs to be activated. If you have existing RAID volumes and have to replace the REM (RAID Expansion Module) the following commands
will need to be run to see the volume(s) with the new REM:
{0} ok setenv auto-boot? false
auto-boot? = false
{0} ok setenv fcode-debug? true
fcode-debug? = true
{0} ok reset-all
Sun Blade T6320 Server Module, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.27.4, 3968 MB memory available, Serial #77097626.
Ethernet address 0:14:4f:98:6a:9a, Host ID: 84986a9a.
{0} ok show-disks
a) /pci@0/pci@0/pci@2/LSILogic,sas@0/disk
b) /pci@0/pci@0/pci@1/pci@0/usb@1,2/storage@1/disk
q) NO SELECTION
Enter Selection, q to quit: q
{0} ok select /pci@0/pci@0/pci@2/LSILogic,sas@0
{0} ok show-volumes ( Look for the inactive volume)
{0} ok X activate-volume (X is the volume number)
{0} ok unselect-dev
when you have completed managing the RAID volumes you can set the auto-boot? and fcode-debug? variables back and reset the system:
{1} ok setenv auto-boot? true
auto-boot? = true
{1} ok setenv fcode-debug? false
fcode-debug? = false
{1} ok reset-all
Note: When the volume is activated the RAID 1 (IM/IME) volume(s) will automatically resync. By CharlesForgues 23 Jul 2010 19:19:21
How to find the mac addresses for NICs and NEMsAnswer:There are several methods to determine the actual physical Ethernet MAC Address of a NIC. Note: Not all Sun NICs have local MAC addresses built in. They always use the system default MAC address unless overridden during bootup. Method 1: banner Using the banner at the ok> will give you the default MAC address of the system:
ok> banner Sun (TM) Enterprise 250 (2 X UltraSPARC-II 296MHz), No Keyboard OpenBoot 3.7, 1024 MB memory installed, Serial #9311264. Ethernet address 8:0:20:8e:14:20, Host ID: 808e1420. Method 2: .enet-addr From the ok> you can simply use the .enet-addr command to determine the system's MAC address:
ok> .enet-addr 8:0:20:9a:aa:55 Method 3: .properties or .attributes To find other MAC addresses that belong to other interfaces on the system, You can examine the .properties of the device on Ultra[TM] architecture (sun4u) systems. Use .attributes on sun4m and sun4c architectures.
ok> show-nets //will give you the device path for the interface// ok> cd //change to device path// ok> .properties // this should show you the MAC address of that interface// For example (sun4u):
ok> show-nets a) /pci@1f,0/pci@1/network@3 b) /pci@1f,0/pci@1/network@1 c) /pci@1f,0/pci@1/pci@4/network@0 d) /pci@1f,0/pci@1,1/network@1,1 q) NO SELECTION Enter Selection, q to quit: q ok> cd /pci@1f,0/pci@1/network@3 ok> .properties assigned-addresses 82021810 00000000 00800000 00000000 00009060 local-mac-address 08 00 20 89 94 32 For example ( sun4m ) :
ok> cd /io-unit@f,e0200000/sbi@0,0/SUNW,qfe@2,8c00000 ok> .attributes local-mac-address 08 00 20 8d 8d 64 As noted above, the local-mac-address line may not appear if the interface does not have a local MAC address built in. Method 4: showplatform (on Sun Fire[TM] Servers only) The showplatform command shows MAC addresses. SC> showplatform -v or
SC> showplatform mac MAC Address HostID ----------------- -------- Domain A 08:00:20:d8:a8:37 80d8a837 Domain B 08:00:20:d8:a8:38 80d8a838 Domain C 08:00:20:d8:a8:39 80d8a839 Domain D 08:00:20:d8:a8:3a 80d8a83a SSC0 08:00:20:d8:a8:3b 80d8a83b SSC1 08:00:20:d8:a8:3c 80d8a83c Method 5: prtconf After the machine has booted, you can use the prtconf command to examine the Ethernet MAC address. (for on-board le or hme = host assigned HW address)
$ prtconf -pv |grep idprom idprom: 01800800.208d7e88.00000000.8d7e88a9.00000000.00000000.00000000.00000000 ^^^^^^^^^^^^^ 08:00:20:8d:7e:88 newer add-on NICs have unique addresses, the following example relates to a Sun Quad Fast Ethernet (qfe) NIC:
$ prtconf -pv |grep local-mac-address local-mac-address : 'true' local-mac-address: 0800208d.7828 local-mac-address: 0800208d.7829 local-mac-address: 0800208d.782a local-mac-address: 0800208d.782b Method 6: Examine bootup messages
# dmesg or # more /var/adm/messages Ethernet address = 8:0:20:87:b3:50 .. SUNW,qfe3: Local Ethernet address = 8:0:20:aa:dd:2b SUNW,qfe3: Using local MAC addressEthernet address = 8:0:20:87:b3:50 Method 7: ifconfig Executing the ifconfig as root on a plumbed interface will display the Ethernet MAC address.
# ifconfig hme0 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 192.168.10.1 netmask ffffff00 broadcast 192.168.10.255 ether 8:0:20:9e:e7:95 Executing ifconfig -a as root will show all plumbed interfaces with their MAC addresses if system is multi-homed.
# ifconfig -a lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 192.148.12.11 netmask ffffff00 broadcast 129.148.12.255 ether 8:0:20:87:b3:50 ce0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 192.148.12.8 netmask 0 ether 8:0:20:bc:d7:82 Note that the output from the ifconfig command when run as non-root does not include the MAC address. Method 8: netstat -pn or arp -a The arp -a or netstat -pn commands will show Ethernet MAC addresses:
# netstat -pn |grep SP hme0 192.168.10 255.255.255.255 SP 08:00:20:9e:e7:95 # arp -a |grep SP hme0 hodware 255.255.255.255 SP 08:00:20:9e:e7:95 Method 9: arp 'hostname' The arp command followed by the server's hostname will also provide your MAC Address. First use the hostname command to find your server's name:
bash# hostname scooby Now type the arp command followed by the hostname you retrieved:
bash# arp scooby scooby (129.154.153.80) at 0:3:ba:5e:56:bf permanent published Method 10: non-Ethernet type interfaces For SunFDDI[TM]: *nf_macid* and nf_stat can be used on FDDI interfaces:
# nf_macid nf0 8:0:20:11:3f:4d # nf_stat -m PhyS Frame Error Lost SA UNA DNA M 2ab95e4 0 0 8:0:20:11:3f:4d 0:80:d8:0:4:8a 0:0:f8:0:0:0 For SunATM[TM]: The lanearp and lanestat commands can be used on ATM interfaces:
# lanearp -a LANE Interface lane0: Local MAC addr = 8:0:20:84:db:21 ATM addr = 47:00:00:00:00:00:00:00:00:00:00:CC:C0::08:00:20:84:DB:21::00 For Token Ring: *trsr* can be used:
# trsr -a Dev Mac-Addr Flags Timeout Len Dir Mtu Route tr0 8:0:20:c:10:ab Rslvd 4 (min) 6 0 4472 (1)1(2) tr0 8:0:20:a:8a:17 Local 2 (min) For llc2: *llc2_config* can be used on llc2 configured devices:
$ /usr/lib/llc2/llc2_config PPA State ID MACAddr Type MaxSDU MinSDU Mode Device 0 up 0000 08002050966f ethernet 1500 0 3 /dev/pcn0
See Technical Instruction: Why do all my Ethernet interfaces have the same ether MAC address? (Doc ID 1010245.1) By CharlesForgues 23 Mar 2010 19:37:20
How to determine minimum firmware/OS/patches requirements for the 10GbE ports on their Virtualized Multi-Fabric 10GbE NEM and T6320/T6320 G2 blade.Answer:The Minimum requirements for supporting the 10GbE ports on the Virtualized Multi-Fabric 10GbE NEM and T6320/T6320 G2 blade: - All T6320/T6320 G2 blades need sysfw 7.2.2.g (or later). - All T6320/T6320 G2 blades need Solaris 10 5/09 (or later). - All T6320/T6320 G2 blades need the hxge driver package SW2.1 (or later) which is an O/S patch/package for Solaris (SUNWhxge_sparc_V2.1.tar.gz) and can be downloaded from the Oracle download site. - All T6320/T6320 G2 blades need CPLD firmware patch 142151-02 (or later). - All Hydra NEM ILOM SP's need "ILOM-2_0_3_12-Sun_Fire_X4238.pkg" (or later) and can be downloaded from the Oracle download site. By CharlesForgues 01 Mar 2010 18:46:14
How to enable SSO (Single Sign On) between the CMM & the T6320 SP, verify if it's not working, and how to fix if broken.Answer: The whole point of SSO (Single Sign On) is to allow a CMM user access to a blade withouthaving to go manually configure common "usernames'. If one never wants to log in to a blade directly, and only wants to access it from the CMM, then you wouldn't have to configure anything related to user authorization on the blade, other than enable SSO. SSO is enabled by default. You should see SSO enabled under both the CMM:
-> show /CMM/services/sso
/CMM/services/sso
Targets:
Properties:
state = enabled <---<
and the T6320 SP:
-> show /SP/services/sso
/SP/services/sso
Targets:
Properties:
state = enabled <---<
If SSO isn't used (and you wanted to login to the blade SP from the CMM), then the /CH/BLx/SP/CLI/user field must be set to a username that can be used to log in to the SP (local, radius, ldap, etc). Effectively the CMM is just issuing ssh -l {value of /CH/BLx/SP/cli/user} {value of /CH/BLx/SP/network/ipaddress}. For example if they just wanted to login to the T6320 SP as root from the CMM they would just need to set the following without SSO being enabled:
-> show /CH/BL1/SP/cli
/CH/BL1/SP/cli
Targets:
Properties:
type = Blade CLI
user = root <---<
If SSO isn't enabled on the CMM and SP of the blade or the above user isn't setup you will see the following error message when trying to sign-on to the blade from the CMM:
-> cd /CH/BL1/SP/cli /CH/BL1/SP/cli -> start Are you sure you want to start /CH/BL1/SP/cli (y/n)? y start: Can't use Single Sign On for /CH/BL1/SP/cli start: Property /CH/BL1/SP/cli/user needs to be set in order to connect to the target SP start: Failed to start /CH/BL1/SP/cli Please check the above for proper configuration of SSO. If all is correct above for SSO you will be allowed to access the blade without logging in:
-> start Are you sure you want to start /CH/BL1/SP/cli (y/n)? y start: Connecting to /CH/BL1/SP/cli using Single Sign On Waiting for daemons to initialize... Daemons ready Sun(TM) Integrated Lights Out Manager Version 3.0.3.20.g Copyright 2009 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. ->
By CharlesForgues 16 Feb 2010 19:28:15
How to gather T6320/G2 Serial NumbersAnswer: On the T6320 blades the Blade Serial Number under the sc> showplatform -v command or the fru_serial_number under the -> show /SYS/MBare the same (which is the Serial Number of the Configured Blade FRU):
sc> showplatform -v (presents the Blade Serial Number) SUNW,Sun Blade T6320 G2 Server Module Blade Serial Number: 0111APO-0924YG034C <<<<--<< Chassis Serial Number: 0000000-0000000000 Slot Number: 1 . . sc>
-> show /SYS/MB
.
.
Properties:
type = Motherboard
ipmi_name = /MB
fru_name = T6320_MB
fru_description = 8C,1.4GHZ N2,T6320,DIRECT-A
fru_manufacturer = Celestica
fru_version = 01_50
fru_part_number = 5413838
fru_serial_number = 0111APO-0924YG034C <<<<----<<
fault_state = OK
clear_fault_action = (none)
.
.
->
The motherboard assembly FRU is the part that needs to be replaced in the event of a service call, which is related to the MB+metalwork (i.e. everything except REM, FEM, disks and DIMMs). This FRU Serial number is printed on a label on the top surface of the motherboard. That label will have a 541- level Sun Part Number as seen in the following "sc> showfru" output:
sc> showfru /SYS/MB
/SYS/MB (container)
SEGMENT: FL
/Configured_LevelR
/Configured_LevelR/UNIX_Timestamp32: Fri, Jul 17 2009 15:39:58 GMT
/Configured_LevelR/Sun_Part_No: 5413838 <<<-----<<
/Configured_LevelR/Configured_Serial_No: 0111APO-0924YG034C <<<----<<
/Configured_LevelR/HW_Dash_Level: 01
SEGMENT: ST
/Status_CurrentR
/Status_CurrentR/UNIX_Timestamp32: Thu, Oct 15 2009 16:58:13 GMT
/Status_CurrentR/Status: 0x00 (OK)
.
.
sc>
The EZ-label (which is on the ejector handle of the T6320/T6340 blades) is not the same number as the "blade serial number" since it represents the *whole* shipped system (MB CRU+DIMM CRUs+disk CRUs+REM CRU+FEM CRU). This value would appear at the top of the Yellow Sheet which was fixed to the outside of the shipping box. Which has a number something like: By CharlesForgues 01 Jan 2010 19:47:31
How to initially configure the SP network parameters for a Virtualized Multi-Fabric 10GbE NEM (hydra) in a Sun Blade 6000 chassis on a non-DHCP network.Answer:
Note: If on a DHCP network just plug in the NEM and your finished (DHCP is configured by default). Note: The Sun Blade 6000 chassis has its own ILOM, called a CMM ILOM, which is a separate entity from the NEM ILOM. Note: The CMM ILOM in the chassis has an Ethernet switch that supports connections to the Virtualized NEMs and its ILOMs. To use this connection, you must be connected to the same subnet as the ILOM, and you must know the NEM ILOM’s Ethernet address.
-> set pendingipdiscovery=static (Default=dhcp) -> set pendingipaddress=x.x.x.x -> set pendingipgateway=x.x.x.x -> set pendingipnetmask=x.x.x.x -> set commitpending=true By CharlesForgues 22 Dec 2009 19:50:26
How to update the ILOM Firmware Using the Web Interface.Answer: 1. Log in to the ILOM web interface as root after entering the ip address of your T6320/T6320 G2 SP (ie: https://x.x.x.x) into your web browser. 2. Select Maintenance --> Firmware Upgrade.
Note: If the Firmware Update box is grayed out you will need to make sure that the OS is shutdown and you perform a -> stop /SYS on the ILOM of the blade. After, you will also need to select any other TAB and then Select Maintenance TAB again to allow the Firmware Update box to ungray. 3. Click Enter Upgrade Mode.
4. Click OK to enter Upgrade mode or Cancel to exit the process.
5. Enter the path to the new ILOM flash image file in the Select Image File to Upload field or click Browse to locate and select the firmware update file.
6. Click Upload or Cancel to exit the process.
7. In the Verify Firmware Image page, click OK. 8. Select Preserve Configuration to keep your existing ILOM configuration settings. If you do not preserve your configuration, the settings will be overwritten by the firmware defaults.
10. After the SP and/or CMM finishes rebooting, use your browser to reconnect to ILOM. By CharlesForgues 23 Nov 2009 20:22:57
(ILOM)How to update the system firmware on a T6320/T6320 G2 using the ILOM interface (->).Answer: Note: The .pkg file needs to be installed under the /tftpboot directory or in a directory under the /tftpboot directory of the tftp server. This server is designated using the -source parameter of the -> load command. If using the latter you will also need to add the directory name in the -source parameter directory path (ie. tftp://xxx.xxx.xxx.xxx/directory/.pkg).
# ssh -l root x.x.x.x
Password:
Waiting for daemons to initialize...
Daemons ready
Sun(TM) Integrated Lights Out Manager
Version 3.0.3.20.f
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
-> load -source tftp://x.x.x.x/Sun_System_Firmware-7_2_2_g-Sun_Blade_T6320_G2_Server_Module.pkg
NOTE: An upgrade takes about 6 minutes to complete. ILOM
will enter a special mode to load new firmware. No
other tasks can be performed in ILOM until the
firmware upgrade is complete and ILOM is reset.
Are you sure you want to load the specified file (y/n)? y
Do you want to preserve the configuration (y/n)? y
................................................................................................................
Preserving configuration. Please wait.
Done preserving configuration.
Firmware update is complete.
ILOM will now be restarted with the new firmware.
-> Connection to x.x.x.x closed by remote host.
Connection to x.x.x.x closed.
#
By CharlesForgues 20 Nov 2009 17:24:30
(ALOM)How to update the system firmware on a T6320/T6320 G2 using the ALOM CMT interface (sc>).Answer: Note: The .pkg file needs to be installed under the /tftpboot directory or in a directory under the /tftpboot directory of the tftp server. This server is designated using the -s parameter of the sc> firmware command. If using the latter you will need to add the directory name in the -f parameter directory path (ie. directory/.pkg).
# ssh -l admin x.x.x.x
Password:
Waiting for daemons to initialize...
Daemons ready
Sun(TM) Integrated Lights Out Manager
Version 3.0.3.20.f
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
sc> flashupdate -s x.x.x.x -f Sun_System_Firmware-7_2_2_g-Sun_Blade_T6320_G2_Server_Module.pkg
NOTE: A flashupdate takes about 6 minutes to load a new file.
Some commands are disabled until the file load is complete.
The SC will be reset to complete the upgrade.
Are you sure you want to load the specified file (y/n)? y
..................................................................................................
.............
Preserving configuration. Please wait.
Done preserving configuration.
New firmware images were loaded. The SC will reset now to complete the upgrade.
Connection to x.x.x.x closed by remote host.
#
By CharlesForgues 20 Nov 2009 17:24:30
How to login into the Sun Blade T6320/T6320 G2 ILOM using the BUI (Browser User Interface).Answer: URL: https://x.x.x.x (IP of the ILOM you are logging into) Note: The ILOM needs to be configured with an IP Address, Netmask, and Gatewaybefore logging in using the above BUI method. By CharlesForgues 13 Nov 2009 19:22:20
How to initially configure the SP network parameters for a T6320/T6320 G2 blade in a Sun Blade 6000/6048 chassis on a non-DHCP network.Answer:
Note: If on a DHCP network just plug in the blade and network cable and your finished (DHCP is configured by default). Note: CMM v2.0.3.2 (or above) can configure the T6320/T6320 G2 service processor (SP) network parameters without a dongle. On any previous CMM versions the dongle is the only way to configure the network since the earlier CMM versions don't support -> cd /CH/BLx on these blades.
-> set pendingipdiscovery=static (Default=dhcp) -> set pendingipaddress=x.x.x.x -> set pendingipgateway=x.x.x.x -> set pendingipnetmask=x.x.x.x -> set commitpending=true
By CharlesForgues 12 Nov 2009 20:19:59
(3-Cable Dongle)How to access the Sun Fire T6320 or T6320 G2 Service Processor (SP) serial port via the 3-Cable Dongle (530-3936-01).Answer:Plug the 3-Cable Dongle into Universal Connector Port (UCP) located on the front of the blade and use the RJ45 port for serial access to the SP.
By CharlesForgues 06 Nov 2009 17:36:19
(4-Cable Dongle)How to access the Sun Fire T6320 or T6320 G2 Service Processor (SP) serial port via the 4-Cable Dongle (530-3934-02).Answer:Plug the 4-Cable Dongle into Universal Connector Port (UCP) located on the front of the blade and use the DB9 port for serial access to the SP.
By CharlesForgues 06 Nov 2009 17:33:00
How to tell if you have a Sun Fire T6320 G2 or the older Sun Fire T6320Answer: Use the ILOM show command: -> show /SYS product_name
/SYS
Properties:
product_name = Sun Blade T6320 G2 Server Module <===
Use the ALOM CMT showplatform command: sc> showplatform SUNW,Sun Blade T6320 G2 Server Module <=== Blade Serial Number: 1005LCB-091853002N Chassis Serial Number: 0111APO-0741YT0214 Slot Number: 8 By CharlesForgues 06 Nov 2009 09:07:25
Attachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||