Sun Fire[TM]/Netra[TM] 1280/1290/E2900: Reference for Improving Remote Diagnosibility

Asset ID:	1-79-1540855.1
Update Date:	2017-10-18
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1540855.1 : Sun Fire[TM]/Netra[TM] 1280/1290/E2900: Reference for Improving Remote Diagnosibility

Applies to:

Sun Netra 1290 Server - Version Not Applicable and later
Sun Fire V1280 Server - Version Not Applicable and later
Sun Netra 1280 Server - Version Not Applicable and later
Sun Fire E2900 Server - Version Not Applicable and later
Information in this document applies to any platform.

Purpose

This document is used for configuring different aspects of the server to help improve remote diagnosability, enabling quicker more accurate resolution of hardware and software issues.

Details

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in an appropriate My Oracle Support Community - Oracle Sun Technologies Community - SPARC Legacy Servers.

Sun Fire[TM]/Netra[TM] 1280/1290/E2900 - Best Practices

Sun Fire Midframe & Entry-Level Servers Best Practices Update for Firmware 5.20.x (pdf)

The Best Practice document contains information on the following topics (This is it's Table of Contents):

    Introduction............................................................................................. 1
    Platform Configuration ...................................................................................2
         Configuring the RS-232 Serial Port ..................................................................2
         Configuring the Ethernet Port .......................................................................3
         Configuring a Switched Private Network ..............................................................3
         Configuring the Alarms Port (Entry-Level only).......................................................5
         Periodic Sun Fire SC Reboots.........................................................................6
         Configuring SC Failover (Midframe server only).......................................................7
         Setting the Date and Time on the Platform ...........................................................11
         Configuring SNTP (Midframe Servers only).............................................................12
         Changing POST Levels and Other Settings .............................................................13

    Configuring the Midframe and Entry-Level Service Processor ...............................................16
         Configuring the SP to receive Log Messages...........................................................17
         Sun MC Software .....................................................................................19
         Preparing for Firmware Updates ......................................................................19
         Explorer Data Collector .............................................................................20
         Monitoring Domain Consoles ..........................................................................22

    Platform and Domain Administration .......................................................................23

    Platform Security ........................................................................................28
         Recommendations for User Authorization ..............................................................29
         Serial Port Access ..................................................................................29
         Telnet and Secure Shell Sessions ....................................................................30
         Keyswitch Settings (Midframe Server Only)............................................................33

    Error Analysis, Diagnosis and Recovery ...................................................................33

    Maintenance Functions ....................................................................................34
         Periodic Server Maintenance .........................................................................34
         Restoring the Sun Fire SC Configuration .............................................................35
         Updating the Firmware and Real Time Operating System ................................................36
         Removing the SC from Platform Use ...................................................................37

Sun Fire[TM]/Netra[TM] 1280/1290/E2900 - Serial Port Setup

See Connecting your console to a Sun Fire[TM]/Netra[TM] 1280/1290/E2900 serial LOM port (Doc ID 1003646.1)

1. Connect the RJ45-to-RJ45 straight-thru network cable (supplied with the server)
to the Serial A/LOM port on the back panel of the 1280/2900 server. This port will be labeled "SSC1 Serial A".

Note: serial port B is not in use

serial

2. Connect the other end of the network cable to the RJ45 connector on the silver-colored DB25/RJ45 adapter
(part number 530-2889-0x) supplied with the server. If your console has a DB25 connector, use part number 530-3100.

      Sunfire/Netra 1280 Serial Port Pin-outs
    =======================================

    8-Pos RJ45         25-pin DSUB
    ------------------------------
    Pin 1 RTS ========> Pin 5 CTS
    Pin 2 DTR ========> Pin 6 DTR
    Pin 3 TXD ========> Pin 3 RXD
    Pin 4 REF ========> Pin 7 GND
    Pin 5 REF ========> Pin 7 GND
    Pin 6 RXD ========> Pin 2 TXD
    Pin 7 DSR ========> Pin 20 DTR
    Pin 8 CTS ========> Pin 4 RTS

The port settings should be 9600 bps, 8- bits, no parity, and 1 stop bit (9600-8-N-1).

Sun Fire[TM]/Netra[TM] 1280/1290/E2900 - Remote collection of data from both domain and System Controller (LOM)

See Sun Fire[TM] v1280, 3800, 4800, 4810, 6800, E2900, E4900, E6900 and Netra[TM] 1280, 2900 servers: How to collect scextended or 1280extended Explorer (Doc ID 1019066.1) for a more detailed explanation.

        - Extended explorer has to be run on a system that is able to telnet or ssh into the SC.
        - Frequently, the domain and the SCs are not on the same network.
          When this occurs, you might need to use explorer from the domain and scextended explorer from the loghost for troubleshooting purposes.
        - Oracle Explorer version 6.x and above is recommended for use.
          The latest version of Explorer can be downloaded via Oracle Explorer Data Collector - Product Information Center Document 1312847.1

Example of running explorer:

# /opt/SUNWexplo/bin/explorer -w default,1280extended,fru

Alternatively this is a procedure to collect Sun Fire[TM] Midrange Server System Controller (SC) Data
when it is not possible to capture scextended or 1280extended Explorer data.

1) Log into a system which has access to the System Controller (SC) Network Management Port (lom> prompt) and open a terminal window.

2) Open a script session so the following SC command output will be captured.

    $ script -a /tmp/scdatafile

3) Connect to the lom> prompt on the SC per your configuration's requirements (telnet, console, ssh, tip, etc):

    $ console sc_name$ telnet sc_name$ ssh sc_name

    NOTE: After initial connection, you may need to issue a "#." to get into the lom> prompt where the following commands are available.
    Note – At 5.18.0, you will be offered the option of connecting with a secure shell (ssh) only if you have an SC V2 in the IB/SSC. In this case only SSH will work not telnet

    ADDITIONAL NOTE: Do not reboot the SC before collecting this data. Doing so may erase critical troubleshooting information in the SC's log buffer.

4) From the lom> prompt, execute the following commands which will be captured in the script session that you opened previously:

    showdate -v
    showsc -v
    bootmode
    showeventreporting
    showescape
    showhostname
    shownetwork -v
    showmodel

    showcodlicense -rv
    showcodusage -vp all

    showlogs -v
    showlogs -vp (will fail on older 1280 models)

    showcomponent -v
    showresetstate -v (typically returns nothing)
    showfault
    showlocator
    showalarm 1
    showalarm 2
    showalarm 3
    showalarm system

    showchs -b (will fail for fw below 5.20.15)
    And for each suspect or faulty component
    showchs -vc /N0/IB6    (for example)

    showerrorbuffer
    showerrorbuffer -p   (will fail on older 1280 models)

    showenvironment -ltuv
    showboards -ev
    inventory
    history
    showdate

    NOTE: You might need to use a "Control right bracket" ("']") to disconnect or just type "logout", depending on how you have connected to the SC.

5) Exit the script session to save the collected data:
    Hit <control> D and you should get the message "script /tmp/scdatafile closed", "script done" or a similar message.
    Alternatively, you can also type "exit" at the prompt to close the script session.

6) Upload the data file (scdatafile in this example) utilizing the instructions in Oracle Diagnostic File Upload (Doc ID 1547088.2)

See Procedure to manually collect System Controller (SC) level failure data on Sun Fire[TM] v1280, E2900, 3800, 4800, E4900, 6800, E6900, and Netra 1280, 1290 servers. (Doc ID 1003529.1) for all the details

Sun Fire[TM]/Netra[TM] 1280/1290/E2900 - What data is needed in order to troubleshoot my software or hardware problem?

The following docs provide the Minimal/PREFERRED set of data required to progress the call in case of:

    CPU/Memory Errors
    Disk Errors
    System Crash
    System Hang
    Missing/Disabled Component
    Everything else...

Data Requirements reference: What data is needed in order to troubleshoot my software or hardware problem? (Doc ID 1019144.1)

ATTENTION: this does not replace the indication in the previous section of this Doc:

Sun Fire[TM]/Netra[TM] 1280/1290/E2900 - Remote collection of data from both domain and System Controller (LOM)

Attachments

This solution has no attachment