Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Technical Instruction Sure Solution 1019438.1 : How to gather data from a Sun Netra[TM] CT900 system.
PreviouslyPublishedAs 239648 Description This documents describes how to collect data from the the various component parts of a Sun Netra[TM] CT900 server
This document gives details on how to gather data from components in a Netra CT900, from the chassis LEDs, ShMM, and Nodes Steps to Follow These are the steps to follow to gather the data necessary for diagnosing problems on the Netra CT900 Data can be collected from the Netra CT900 server from the following components
Note the
status of the various chassis LEDS.
The ShMMs run a version of Linux with specific applications designed to manage the CT 900 shelf such as clia There are two ShMMs one of which is active and the other back up. Failover can occur as a result of an error or can be instigated from the command line. Log into the active ShMM as root (via serial connection, telnet or ssh). See the following documents for cabling instructions
Ensure that the connection is with the active ShMM using the shmstatus command (see example below). This is required unless it is necessary to investigate a problem that is specific to backup ShMM but note that many of the script commands will produce no output when run on the backup ShMM. # clia shmstatus Pigeon Point Shelf Manager Command Line Interpreter Host: "Active"
Note the summary script is the equivalent to the Solaris[TM] explorer and also includes information about shelf configuration such as board information. Example: # /etc/summary send debug file /tmp/debug.log to PPS # The script will generate a log file (/tmp/debug.log) which should be provided to Sun[TM] Support
Example: # clia sel -v Pigeon Point Shelf Manager Command Line Interpreter 0x027A: Event: at: Sep 11 18:30:23 2008; from IPM Controller: 0x96, LUN: 0, Channel: 0 "Temperature" (0x01) sensor # 6 "Threshold" (0x01) event Deasserted "Upper Non-Critical Going High" 0x027B: Event: at: Sep 11 18:30:29 2008; from IPM Controller: 0x20, LUN: 0, Channel: 0 "IPMB Link" (0xf1) sensor # 26 "Sensor-specific" (0x6f) event Asserted "Undefined" OEM code 1: 0x00 OEM code 2: 0x87 Note: The output shown above is truncated for clarity of this document
It is beyond the scope of this document to go into detail about the switch architecture but the following discussion will allow basic configuration and statistics to be collected and provide a introduction into obtaining information from the switch. Note: There are 4 Switch Units, 2 per switch slot. Each switch slot contains a switch on the Base Network and one on the Extended Network (Fabric). For full details it is necessary to run all the commands on all the Switch Units. See the following documents for instructions and guidance for cabling
Login into the required switch as admin and ensure all output is being logged via the Unix script command or equivalent. The default password is empty (just hit return key) At this level the show command can be used to interrogate specific configuration settings. Type show ? To find the options. Example: (ATS1160 Base) >show ? bootpdhcprelay Display the value of BOOTP/DHCP relay parameters. class-map Display DiffServ Class information. classofservice Display class of service information. dot1q-tunnel Display double VLAN Tunneling configuration. dvlan-tunnel Display double VLAN Tunneling configuration. garp Display Generic Attribute Registration Protocol information. gmrp Display GMRP interface information. gvrp Display GARP VLAN Registration Protocol parameters. ip Display IP information. network Display configuration for inband connectivity. port-channel Display port-channel information. serial Display EIA-232 parameters and serial port inactivity timeout. serviceport Display service port configuration. spanning-tree Display spanning tree information. remotecon Display Telnet configuration information. vlan Display VLAN configuration and configure VLANs.
First enter into user privilege mode using the ena command. (ATS1160 Base) >ena Password: Then capture the current running configuration. Example: (ATS1160 Base) #show running-config !Current Configuration: ! !System Description "CP3240H-BEX-Z Base" !System Software Version "1.1.8.0" ! set prompt "v-ct900a-sw-b-b-gmp02" serviceport protocol none serviceport ip 129.156.204.81 255.255.252.0 129.156.204.1 vlan database exit configure ! logging buffered ipv6 router ospf exit router rip exit lineconfig exit spanning-tree configuration name "00-20-13-F1-0D-3D" router ospf exit interface 0/1 exit Note: This output is truncated for clarity
#show sysinfo System Description............................. ATS1160 Base System Name.................................... System Location................................ System Contact................................. System Object ID............................... lvl7 System Up Time................................. 25 days 0 hrs 45 mins 12 secs MIBs Supported: RFC 1907 - SNMPv2-MIB The MIB module for SNMPv2 entities RFC 2819 - RMON-MIB Remote Network Monitoring Management Information Base LVL7-REF-MIB LVL7 Reference SNMP-COMMUNITY-MIB This MIB module defines objects to help support coexistence between SNMPv1, SNMPv2, and SNMPv3. SNMP-FRAMEWORK-MIB The SNMP Management Architecture MIB SNMP-MPD-MIB The MIB for Message Processing and Dispatching --More-- or (q)uit SNMP-NOTIFICATION-MIB The Notification MIB Module SNMP-TARGET-MIB The Target MIB Module SNMP-USER-BASED-SM-MIB The management information definitions for the SNMP User-based Security Model. SNMP-VIEW-BASED-ACM-MIB The management information definitions for the View-based Access Control Model for SNMP. USM-TARGET-TAG-MIB SNMP Research, Inc. LVL7-POWER-ETHERNET-MIB LVL7 Power Ethernet Extensions MIB POWER-ETHERNET-MIB Power Ethernet MIB LAG-MIB The Link Aggregation module for managing IEEE 802.3ad RFC 1213 - RFC1213-MIB Management Information Base for Network Management of TCP/IP-based internets: MIB-II RFC 1493 - BRIDGE-MIB Definitions of Managed Objects for Bridges (dot1d) RFC 1643 - Etherlike-MIB Definitions of Managed Objects for the Ethernet-like Interface Types (dot3) RFC 2233 - IF-MIB The Interfaces Group MIB using SMIv2 RFC 2674 - P-BRIDGE-MIB The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998. Note: This output is truncated for clarity
ATS1160 Base) #show port all Admin Physical Physical Link Link LACP Intf Type Mode Mode Status Status Trap Mode ------ ------ ------- ---------- ---------- ------ ------- ------- 0/1 Enable Auto 100 Full Up Enable Enable 0/2 Enable Auto 1000 Full Up Enable Enable 0/3 Disable Auto Down Enable Enable 0/4 Disable Auto Down Enable Enable 0/5 Disable Auto Down Enable Enable 0/6 Disable Auto Down Enable Enable 0/7 Disable Auto Down Enable Enable 0/8 Disable Auto Down Enable Enable 0/9 Disable Auto Down Enable Enable 0/10 Disable Auto Down Enable Enable 0/11 Enable Auto 1000 Full Up Enable Enable 0/12 Enable Auto 100 Full Up Enable Enable 0/13 Enable Auto 1000 Full Up Enable Enable 0/14 Enable Auto 100 Full Up Enable Enable 0/15 Disable Auto Down Enable Enable 0/16 Disable Auto Down Enable Enable 0/17 Enable Auto Down Enable Enable 0/18 Enable Auto Down Enable Enable 0/19 Enable Auto Down Enable Enable --More-- or (q)uit 0/20 Enable Auto 100 Full Up Enable Enable 0/21 Enable Auto Down Enable Enable 0/22 Enable Auto Down Enable Enable 0/23 Enable Auto Down Enable Enable 0/24 Enable Auto Down Enable Enable
Where a problem indicates, it may be necessary to gather statistics for individual ports. (ATS1160 Base) #show interface 0/1 Packets Received Without Error................. 1430658 Packets Received With Error.................... 0 Broadcast Packets Received..................... 1141 Packets Transmitted Without Errors............. 22407251 Transmit Packet Errors......................... 0 Collision Frames............................... 0 Time Since Counters Last Cleared............... 44 day 3 hr 4 min 12 sec The output of the above commands should be sufficient to provide initial information when contacting Sun Support Center about a Netra CT900 switch or connectivity problem.
These boards can be a variety of architectures and running different operating systems. Use the appropriate tool such as explorer for Solaris and sosreport for Red Hat 5 to collect data. Note the ShMM section above will collect data about board power cycles, hardware type and slots. References: http://download.oracle.com/docs/cd/E19217-01/index.html
Product Sun Netra CT 900 Server Netra CP3010 Board Netra CP3020 Board Netra CP3060 Board Sun Netra CP3140 ATCA Switch Blade Sun Netra CP3220 ATCA Blade Server Sun Netra CP3260 ATCA Blade Server Netra CP3240 Switch Internal Comments This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the “Document Feedback” alias(es) listed below: Domain Lead: [email protected] Feedback Alias: [email protected] normalized, CT900, Netra, ATCA, shelf, clia, summary, pigeon point, CP3010, CP3020, CP3060, CP3220, CP3250, CP3260, CP3140, CP3240, ShMM, ShMc, Attachments This solution has no attachment |
||||||||||||
|