Netra CT 900: Collecting ShMM data that not found in debug.log

Asset ID:	1-79-1552574.1
Update Date:	2017-05-02
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1552574.1 : Netra CT 900: Collecting ShMM data that not found in debug.log

Applies to:

Sun Netra CT900 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Purpose

ShMM commands to perform in case it's debug.log file does not contain details to troubleshoot.

Details

Document Netra CT900 ShMM debug.log analysis indicates how to review the ShMM debug log, /tmp/debug.log. It might not have EVERYTHING needed to debug a CT900 problem. Any output that is not there are to be requested from customer separately. Example commands & data are as follows:

# clia help fruinfo

Display the FRU Info of the dedicated FRU in the readable format
instead of <addr> <fru_id> user may use:
        power_supply <N> (valid in 2.x systems only)
        fan_tray <N>
        board <N>
        shm <N>
to access the FRU on the specified board
        fruinfo board 14
        fruinfo power_supply 4

fruinfo <addr> <fru_id>

Example:

# clia fruinfo 20 3
Product Info Area:
    Version     = 1
    Language Code            = 25
    Manufacturer Name        = Sun Microsystems, Inc.
    Product Name             = NETRA,CT900,NH7,FAN_TRAY
    Product Part / Model#    = 371-3033-01
    Product Version          = 50
    Product Serial Number    = 1005SCH-0812AW2676
    Asset Tag                = 0000000000000001
    FRU Programmer File ID   = 21596253BABIN.inf

# clia fruinfo board 1

Product Info Area:
    Version     = 1
    Language Code            = 25
    Manufacturer Name        = Sun Microsystems, Inc.
    Product Name             = Netra CP3260
    Product Part / Model#    = 00000000050178380150
    Product Version          = Monza P2.0 8CORE SLD
    Product Serial Number    = 001005LCB-0752W00027
    Asset Tag                =
    FRU Programmer File ID   = 885-1145-02.inf

PN 50178380150 reads: 501-7838-01, REV 50

# clia help sensor

Shows sensor information
instead of <addr> user may use:
        board <N>
        shm <N>
to access the sensor on the specified board
        sensor board 21 "IPMB LINK"
        sensor 20 8

sensor [ <addr> [ [ lun: ]<sensor id> | <sensor name> ] ]

Example:

# clia sensor 10 | grep Sensor
10: LUN: 0, Sensor # 0 ("FRU 0 HOT_SWAP")
10: LUN: 0, Sensor # 1 ("IPMB LINK")
10: LUN: 0, Sensor # 2 ("Local Temp")
10: LUN: 0, Sensor # 3 ("3V3_local")
10: LUN: 0, Sensor # 4 ("I2C_PWR_A")
10: LUN: 0, Sensor # 5 ("I2C_PWR_B")
10: LUN: 0, Sensor # 6 ("VBAT")
10: LUN: 0, Sensor # 7 ("Fan Tach. 0")
10: LUN: 0, Sensor # 8 ("Fan Tach. 1")
10: LUN: 0, Sensor # 10 ("Fan Tach. 2")
10: LUN: 0, Sensor # 11 ("Fan Tach. 3")
10: LUN: 0, Sensor # 13 ("Fan Tach. 4")
10: LUN: 0, Sensor # 14 ("Fan Tach. 5")
10: LUN: 0, Sensor # 15 ("-48A Bus voltage")
10: LUN: 0, Sensor # 16 ("-48B Bus voltage")
10: LUN: 0, Sensor # 17 ("-48A ACB voltage")
10: LUN: 0, Sensor # 18 ("-48B ACB voltage")
10: LUN: 0, Sensor # 19 ("-48A ACB Fuse")
10: LUN: 0, Sensor # 20 ("-48B ACB Fuse")
10: LUN: 0, Sensor # 128 ("CPLD State")
#

# clia help sensordata

Shows sensor data
instead of <addr> user may use:
        board <N>
        shm <N>
to access the sensor on the specified board
(only sensors with thresholds crossed if -t is given)
        sensordata board 21 "IPMB LINK"
        sensordata 20 8

sensordata [-t] [ <addr> [ [ lun: ]<sensor id> | <sensor name> ] ]

Example:

# clia sensordata 92 9

92: LUN: 0, Sensor # 9 ("5.0V")
    Type: Threshold (0x01), "Voltage" (0x02)
    Status: 0xc0
        All event messages enabled from this sensor
        Sensor scanning enabled
        Initial update completed
    Raw data: 179 (0xb3)
    Processed data: 4.654000 Volts
    Status: 0x00

#

# clia help getthreshold

Shows the threshold of the specified sensor
instead of <addr> user may use:
        board <N>
        shm <N>
to access the sensor on the specified board
        getthreshold board 21 "IPMB LINK"
        getthreshold 20 8

getthreshold [ <addr> [ [ lun: ]<sensor id> | <sensor name> ] ]

Example:

# clia getthreshold 92 9

92: LUN: 0, Sensor # 9 ("5.0V")
    Type: Threshold (0x01), "Voltage" (0x02)
        Lower Non-Critical Threshold, Raw Data: 0xaf      Processed data: 4.550000 Volts
        Lower Critical Threshold, Raw Data: 0xae                  Processed data: 4.524000 Volts
        Lower Non-Recoverable Threshold, Raw Data: 0xae    Processed data: 4.524000 Volts
        Upper Non-Critical Threshold, Raw Data: 0xcb Processed data: 5.278000 Volts
        Upper Critical Threshold, Raw Data: 0xcf    Processed data: 5.382000 Volts
        Upper Non-Recoverable Threshold, Raw Data: 0xd4    Processed data: 5.512000 Volts

#

# clia help getfruledstate

Returns the state of the FRU's LED(s)
instead of <addr> <fru_id> user may use:
        board <N>
        shm <N>
If the <LedId> parameter is not specified, all the LEDs related to the specified FRU
are queried; Otherwise that specified LED is queried only
If -v option is specified, additional information about LED(s) properties will be printed
Examples:
        getfruledstate 20 4 1
        getfruledstate 20 4
        getfruledstate 20

getfruledstate [-v] [<addr> [<fru_id> [<LedId>|ALL]]]

Example:

# clia getfruledstate 92

92: FRU # 0, Led # 0 ("BLUE LED"):
    Local Control LED State: LED OFF

92: FRU # 0, Led # 1 ("LED 1"):
    Local Control LED State: LED OFF

92: FRU # 0, Led # 2 ("LED 2"):
    Local Control LED State: LED ON, color: GREEN

92: FRU # 2, Led # 0 ("BLUE LED"):
    Override LED State (current state): LED OFF
    Local Control LED State: LED ON, color: BLUE

92: FRU # 2, Led # 1 ("LED 1"):
    Local Control LED State: LED OFF

92: FRU # 2, Led # 2 ("LED 2"):
    Override LED State (current state): LED ON, color: AMBER
    Local Control LED State: LED OFF

#

NOTE: 0x92 is a CP3060 blade, FRU #0 is blade itself, and FRU #2 is AMC card.

Attachments

This solution has no attachment