32309 3000000000000200 – Server Eagle Network A 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 Main SM network, which connects to the SM A 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 A) connects to the customer provisioning network.

• The eth02 interface (2nd from top ethernet port on the rear of the server A) connects to port 3 of switch A.

• The eth03 interface (2nd from bottom ethernet port on the rear of the server A) connects to port 3 of switch B.

• The eth04 interface (bottom ethernet port on the rear of the server A) is an optional connection to the backup customer provisioning network.

• 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 5 through 21 of switch A 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.10

Alarm ID: TKSPLATMA103000000000000200

Recovery

1. Refer to MPS-specific documentation for information regarding this alarm.
2. Contact My Oracle Support (MOS).
3. Perform the following:
   1. Verify that both servers are powered on by confirming that the POWER LEDs on both servers are illuminated green.
   2. Verify that the switch is powered on.
   3. Verify that the switch does not have any fault lights illuminated.
   4. Verify that the eth01 cable is securely connected to the top port on the server that is reporting the error.
   5. Trace the eth01 cable to the switch. Verify that the eth01 cable is securely connected at correct point of the customer uplink.
   6. Verify that the cable connecting the switches is securely connected at both switches.
4. Run syscheck (see Running syscheck Through the EPAP GUI).
   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 switch tests positive with an Ethernet Line Tester. Replace any faulty cables.
6. If the problem persists, call My Oracle Support (MOS).
7. Perform general IP troubleshooting.
   The syscheck utility reports this error when it tries to ping hosts dsmm-a and dsmm-b a set number of times and fails. This failure could mean any number of things are at fault on the network, but general IP troubleshooting will usually resolve the issue. The platcfg utility can be used to help isolate the problem. To access the platcfg utility:
   1. Log in as platcfg to the server that is generating the alarm.

      Login:  platcfg
      Password: <Enter platcfg password>
      

   2. To display various network information and statistics, select menu options:Diagnostics->Network Diagnostics->Netstat
   3. To ping the dsmb-a and/or dsmb-b select menu options:Diagnostics->Network Diagnostics->Ping
   4. To verify no routing issues exist, select menu options:Diagnostics->Network Diagnostics->Traceroute
8. Run savelogs to gather all application logs, (see Saving Logs Using the EPAP GUI).
9. Run savelogs_plat to gather system information for further troubleshooting, (see Saving Logs Using the EPAP GUI ), and contact My Oracle Support (MOS).