3000000000000400 – Server Eagle Network B error

Alarm Type: TPD

Description: This alarm is generated by the MPS syscheck software package and is not part of the TPD distribution.

Description:
Note: If these three alarms exist, the probable cause is a failed mate server.
  • 3000000000000200-Server Eagle Network A Error
  • 3000000000000400-Server Eagle Network B Error
  • 3000000000000800-Server Sync Network Error
This alarm indicates an error in the Backup SM network, which connects to the SM B ports. The error may be caused by one or more of the following conditions:
  • One or both of the servers is not operational.
  • One or both of the switches is not powered on.
  • The link between the switches is not working.
  • The connection between server A and server B is not working.
Some of the connections between the servers of the SM networks (main and backup).
  • The eth01 interface (top ethernet port on the rear of the server) connects to the customer provisioning network.
  • The eth02 interface (2nd from top ethernet port on the rear of the server) connects to port 4 of switch A.
  • The eth03 interface (2nd from bottom ethernet port on the rear of the server) connects to port 4 of switch B.
  • The eth04 interface (bottom ethernet port on the rear of the server) connects to port 6 of switch A.
  • The interfaces on the switch are ports 1 through 20 (from left to right) located on the front of the switch.
  • Ports 1 and 2 of switch A connect to ports 1 and 2 of switch B.
  • Ports 7 to 24 of switch A and ports 5 through 24 of switch B can be used for links to the Main SM ports (SM A ports) on the EAGLE.

Severity: Major

OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.11

Alarm ID: TKSPLATMA113000000000000400

Recovery

  1. Perform the following:
    1. Verify that both servers are powered on by ensuring that the POWER LEDs on both servers are illuminated green.
    2. Verify that the Ethernet hubs or switches are powered on.
    3. Verify that no fault lights on the Ethernet hubs or switches are illuminated.
  2. Perform the following substeps to verify that the network configuration is correct.
    1. Log in as elapconfig on the E5-APP-B server.

      Enter option 1, Display Configuration, from the ELAP Configuration Menu.

      /-----ELAP Configuration Menu----------\
/----------------------------------------\
|  1 | Display Configuration             |
|----|-----------------------------------|
|  2 | Configure Network Interfaces Menu |
|----|-----------------------------------|
|  3 | Set Time Zone                     |
|----|-----------------------------------|
|  4 | Exchange Secure Shell Keys        |
|----|-----------------------------------|
|  5 | Change Password                   |
|----|-----------------------------------|
|  6 | Platform Menu                     |
|----|-----------------------------------|
|  7 | Configure NTP Server              |
|----|-----------------------------------|
|  8 | Mate Disaster Recovery            |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/
Enter Choice:  1
      Output similar to the following is displayed. The network configuration information related to the EAGLE Network B (the Backup DSM network) is highlighted in bold. 
      MPS Side A:  hostname: bahamas-a  hostid: a8c0ca3d
             Platform Version: 2.0.2-4.0.0_50.26.0
             Software Version: ELAP 1.0.1-4.0.0_50.31.0
             Wed Sep  7 15:05:55 EDT 2005

ELAP A Provisioning Network IP Address = 192.168.61.202
ELAP B Provisioning Network IP Address = 192.168.61.203
Provisioning Network Netmask           = 255.255.255.0
Provisioning Network Default Router    = 192.168.61.250
ELAP A Backup Prov Network IP Address  = Not configured
ELAP B Backup Prov Network IP Address  = Not configured
Backup Prov Network Netmask            = Not configured
Backup Prov Network Default Router     = Not configured
ELAP A Sync Network Address            = 192.168.2.100
ELAP B Sync Network Address            = 192.168.2.200
ELAP A Main DSM Network Address        = 192.168.120.100
ELAP B Main DSM Network Address        = 192.168.120.200
ELAP A Backup DSM Network Address = 192.168.121.100
ELAP B Backup DSM Network Address = 192.168.121.200
ELAP A HTTP Port                       = 80
ELAP B HTTP Port                       = 80
ELAP A HTTP SuExec Port                = 8001
ELAP B HTTP SuExec Port                = 8001
ELAP A Banner Connection Port          = 8473
ELAP B Banner Connection Port          = 8473
ELAP A Static NAT Address              = Not configured
ELAP B Static NAT Address              = Not configured
ELAP A LSMS Connection Port            = 7483
ELAP B LSMS Connection Port            = 7483
ELAP A EBDA Connection Port            = 1030
ELAP B EBDA Connection Port            = 1030
Time Zone                              = America/New_York

Press return to continue...

    2. Verify that the Backup DSM Network IP address for the server reporting this alarm is correct.

      If configuration changes are needed, refer to Administration and LNP Feature Activation Guide for ELAP.

  3. Verify that both servers are powered on by confirming that the POWER LEDs on both servers are illuminated green.
    1. Verify that the switch is powered on.
    2. Verify that the switch does not have any fault lights illuminated.
    3. Verify that the eth01 cable is securely connected to the top port of the server that is reporting the error.
    4. Trace the eth01 cable to the switch. Verify that the eth01 cable is securely connected to the correct point of the customer uplink.
    5. Verify that the cable connecting the switches is securely connected at both switches.
  4. Run syscheck.
    1. If the alarm is cleared, the problem is resolved.
    2. If the alarm is not cleared, continue with the next step.
  5. Verify that the cable from eth01 to the hub tests positive with an Ethernet Line Tester. Replace any faulty cables.
  6. If the problem persists, call My Oracle Support (MOS) for assistance.
Parent topic: Major Platform Alarms