SPARC® Enterprise Mx000 & Fujitsu M10 Servers: ASR Configuration and Activation in ASR Manager 5.x

Asset ID:	1-71-2006371.1
Update Date:	2018-03-18
Keywords:

Solution Type Technical Instruction Sure

Solution 2006371.1 : SPARC® Enterprise Mx000 & Fujitsu M10 Servers: ASR Configuration and Activation in ASR Manager 5.x

Applies to:

Sun SPARC Enterprise M9000-64 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M5000 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M8000 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M4000 Server - Version All Versions to All Versions [Release All Releases]
Sun SPARC Enterprise M3000 Server - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)

Goal

This document is intended to provide assistance in configuring and activating the M-series products in ASR Manager.
It is assumed that a network connection to the Service Processor (XSCF) is available and configured.

Solution

Steps required :

1) Enable Telemetry

2) Activate ASR Asset

3) Activate 2nd XSCF - For M8000 and M9000 Servers

4) Test ASR Activation

Enable Telemetry

FMA Telemetry is not supported for M-series products. All the fault telemetry comes from the XSCF.
The steps below are always performed on the Active XSCF.

1. Initiate a connection through SSH to the IP of the XSCF network interface :

   ssh -l login_name IP_address_of_XSCF_interface

2. Log in to the XSCF and make sure the XCP version is 1115 or greater :

   XSCF> version -c xcp

   Otherwise plan for a firmware upgrade before going to next step.

   Sun SPARC[TM] Enterprise M3000, M4000, M5000, M8000, M9000 XSCF Control Package (XCP) Firmware Image Software Version Matrix Information (Doc ID 1002631.1)

3. Disable the SNMP agent :

   XSCF> setsnmp disable

Make sure you have platadm privileges before disabling the SNMP agent.
You can run showuser -p for a list of users with this privilege.
In case platadm privileges need to be added, Doc ID 1547333.1 will guide you through the process.

4. Add the ASR Manager's IP as the trap destination

   XSCF>setsnmp addtraphost -t v2 -s public -p 162 xxx.xxx.xxx.xxx
                                       |               |            |
                                                               |               |            |
                                                               |               |            |
                                                        Community   SNMP   IP of ASR
                                                           String         Port     Manager

If the trap destination is not used anymore, it can be removed using XSCF>setsnmp remtraphost -t v2 xxx.xxx.xxx.xxx

5. Enable SNMP agent :

   XSCF> setsnmp enable

6. Enable SNMP v1v2:

   XSCF> setsnmp enablev1v2c public

7. Verify the SNMP settings are correct :

   XSCF> showsnmp

   Agent Status:       Enabled
   Agent Port:         161
   System Location:    Unknown
   System Contact:     Unknown
   System Description: Unknown

   Trap Hosts:

   Hostname               Port Type   Community String    Username        Auth Protocol
   ---------------        ---- ----   ----------------    --------        -------------
   xxx.xxx.xxx.xxx         162 v2        public            n/a                n/a

   SNMP V1/V2c:

   Status:            Enabled
   Community String: public

   Enabled MIB Modules:

   SP MIB
   FM MIB

For traps to be generated properly for ASR, the FM MIB must be enabled. If it is not, please issue setsnmp enable FM_MIB on the XSCF.

Observations:

The XSCF sends fault events to the ASR Manager using the SNMP protocol (default using Port: 162/UDP).
The ASR Manager uses the SNMP GET to retrieve additional fault information (such as, FRU part number, serial number and slot location) from the product.
The ASR Manager test_snmp_get command is used to verify SNMP GET connectivity (default using Port: 161/UDP) (test_snmp_get -i <IP Address>).

For M8000/M9000 platforms, SNMP is running only on the Active XSCF.
An SNMP GET error message will be returned when ASR Manager is trying to test the connectivity with the Standby XSCF:

asr> test_snmp_get -i xxx.xxx.xxx.xxx
SNMP GET failed on: xxx.xxx.xxx.xxx
                                             |
                                             |
                                             |
                                          IP of
                                     Standby XSCF

Activate ASR Asset

Once the XSCF Telemetry is set, the asset needs to be activated in ASR Manager.

1. Connect to ASR Manager as root and type asr to enter the ASR menu

If the asr command is not added to your PATH then try /opt/asrmanager/bin/asr

2. Activate the ASR asset :

   asr> activate_asset -i [IP address]
                                               |
                                               |
                                               |
                                            IP of
                                        Active XSCF

For M8000/M9000 platforms both of the XSCF service processors should be activated for ASR with their individual
IP addresses used to send SNMP traps to the ASR Manager, not the failover/virtual IP address shared by both XSCFs.
A switch of the Standby XSCF to the Active role (switchscf) is required to activate both Service Processors.

Example of error message when activate_asset is issued on a Standby XSCF

asr> activate_asset -i xxx.xxx.xxx.xxx
Unable to contact Service Tags on asset xxx.xxx.xxx.xxx
Please check if Service Tags is installed, running, and network accessible.

If you still have an issue with service tags, please verify that service tags are actually running on the XSCF.

XSCF> showservicetag
Enabled

If the service tags show disabled, please issue setservicetag -c enable on the XSCF.

3. Check that the asset information is displayed correctly in ASR Manager :

   asr> list_asset

      IP_ADDRESS           HOST_NAME          SERIAL_NUMBER      ASR        PROTOCOL SOURCE    PRODUCT_NAME
      ---------------       ------------------------------ ------------------------------ --------       --------------- -------------- ------------------------------
     xxx.xxx.xxx.xxx     m4000-xscf0            XXXXXXXXXX        Enabled        SNMP       XSCF-FMA Sun SPARC Enterprise M4000 Server
     xxx.xxx.xxx.xxx     m8000-xscf0            XXXXXXXXXX        Enabled        SNMP       XSCF-FMA Sun SPARC Enterprise M8000 Server
     xxx.xxx.xxx.xxx     m8000-xscf1            XXXXXXXXXX        Enabled        SNMP       XSCF-FMA Sun SPARC Enterprise M8000 Server

For M3000, M4000 and M5000, there should be one activation listed for the single XSCF.
For M8000 and M9000, there should be two activations, one for each of the two XSCF's.

4. Complete the activation process by logging in My Oracle Support(MOS) and approve ASR for the asset

Doc ID 1329200.1 - How To Manage and Approve Pending ASR Assets In My Oracle Support

Activate 2nd XSCF - For M8000 and M9000 Servers

Activate only the physical interface IP's for ASR, not the Virtual IP.

xscf#0-lan#0 - XSCF0 Physical Interface - Activate
xscf#1-lan#0 - XSCF1 Physical Interface - Activate
lan#0 - Virtual IP - DO NOT Activate

Switch the active XSCF to standby to activate the 2nd XSCF for ASR if necessary.

1. Check to see which XSCF is active :

XSCF> version -c xscf

      - If the active XSCF is the one NOT currently activated on the ASR Manager, verify the XSCF SNMP configuration for ASR step #3.
      - If the active XSCF is already ASR Activated, proceed to step #2 to switch the primary XSCF to standby.

2. You may not need to switch the XSCF over, but if you have confirmed the XSCF not configured is the one on standby
    run the following on the Active XSCF to make it the standby XSCF :

    XSCF> switchscf -t standby

3. Verify the XSCF ASR Configuration :

    XSCF> showsnmp

       - Confirm the SNMP configuration is done as noted in the "Enable Telemetry" section of this document.
       - Proceed to Step #4 to activate the second XSCF from the ASR Manager.

4. Activate XSCF from ASR Manager:

    asr> activate_asset -i <physical IP address of the previously un-activated XSCF>

Test ASR Activation

M10: To verify that ASR telemetry is correctly configured, issue the following on the XSCF: rastest -c test

Mx000:

Important:

Mx000 XSCF doesn't have the option for sending a test event.

There is a workaround available for Mx000 which should confirm that the communication is working between the asset and the ASR Manager.
This can be achieved by just disabling/enabling snmp on the XSCF side, while doing a snoop in the ASR Manager.

Confirm the asset is enabled by generating a test event using either one of the following command options from ASR Manager:

    asr> send_test -i [IP_address]

    asr> send_test -h [hostname]

This validates the ASR Manager connection to Oracle and the ASR activation status of the asset. It does not validate the network connection from the asset to the ASR Manager or that the telemetry is properly configured.

Below is an example of the resulting email that is sent confirming the test was successful.

   From: no.reply@oracle.com
   Subject: Oracle ASR: *Test* Service Request
   To: undisclosed-recipients:;

   Hostname: <host name>
   Serial#: <serial number>

   Service Request test-create was successful.

   The Oracle Auto Service Request documentation can be accessed on http://oracle.com/asr.
   Please use My Oracle Support https://support.oracle.com for assistance.

References:

1) Refer to the ASR Manager User's Guide for additional ASR Commands and information.
URL: http://docs.oracle.com/cd/E37710_01/index.htm

2) Oracle Auto Service Request (ASR) (Doc ID 1185493.1)

References

<NOTE:1185493.1> - Oracle Auto Service Request (ASR)
<NOTE:1002631.1> - Sun SPARC[TM] Enterprise M3000, M4000, M5000, M8000, M9000 XSCF Control Package (XCP) Firmware Image Software Version Matrix Information
<NOTE:1329200.1> - How To Manage and Approve Pending Oracle Auto Service Request (ASR) Assets In My Oracle Support
<NOTE:1547333.1> - XSCF commands fail with 'Permission denied' error message
<NOTE:1963725.1> - Auto Service Request (ASR) Email Examples

Attachments

This solution has no attachment