1. Alarms and Maintenance Guide
  2. Alarms
  3. Major Platform Alarms
  4. 32313 3000000000002000 - Server Default Route Network Error

32313 3000000000002000 - Server Default Route Network Error

Alarm Type: TPD

Description: This alarm indicates that the default network route of the server is experiencing a problem. Running syscheck in Verbose mode will provide information about which type of problem is occurring.

Caution:

When changing the network routing configuration of the server, verify that the modifications will not impact the method of connectivity for the current login session. The route information must be entered correctly and set to the correct values. Incorrectly modifying the routing configuration of the server may result in total loss of remote network access.

Severity: Major

OID: 1.3.6.1.4.1.323.5.3.18.3.1.2.14

Alarm ID: TKSPLATMA143000000000002000

Recovery

  1. Run syscheck in Verbose mode.
    The output should indicate one of the following errors: 
    • The default router at <IP_address> cannot be pinged.

      This error indicates that the router may not be operating or is unreachable. If the syscheck Verbose output returns this error, go to 4. 

    • The default route is not on the provisioning network.

      This error indicates that the default route has been defined in the wrong network. If the syscheck Verbose output returns this error, go to 4. 

    • An active route cannot be found for a configured default route.

      This error indicates that a mismatch exists between the active configuration and the stored configuration. If the syscheck Verbose output returns this error, go to 5.

  2. Run syscheck in Verbose mode.
    If the output should indicates:
    
The default router at <IP_address> cannot be pinged

    Go to 3, otherwise go to 4.

  3. Perform the these substeps:
    1. Verify the network cables are firmly attached to the server, network switch, router, hub, and any other connection points.
    2. Verify that the configured router is functioning properly.
      Request that the network administrator verify the router is powered on and routing traffic as required.
    3. Request that the router administrator verify that the router is configured to reply to pings on that interface.
    4. If the alarm is cleared, the problem is resolved.
  4. Perform the following substeps when syscheck Verbose output indicates:
    
The default route is not on the provisioning network
    1. Obtain the proper Provisioning Network netmask and the IP address of the appropriate Default Route on the provisioning network.
      This information is maintained by the customer network administrators.
    2. Log in to the server with username epapconfig.
      The server designation at this site is displayed as well as hostname, hostid, Platform Version, Software Version, and date. Verify that the side displayed is the MPS that is reporting the problem. In this example, MPS A is reporting the problem. Enter option 2, Configure Network Interfaces Menu, from the EPAP Configuration Menu. 
      
MPS Side A:  hostname: mpsa-d1a8f8  hostid: 80d1a8f8
             Platform Version: x.x.x-x.x.x
             Software Version: EPAP x.x.x-x.x.x
             Wed Jul 17 09:51:47 EST 2002
 /-------EPAP 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 | PDB Configuration Menu            |
|----|-----------------------------------|
|  9 | Security                          |
|----|-----------------------------------|
| 10 | SNMP Configuration                |
|----|-----------------------------------|
| 11 | Configure Alarm Feed              |
|----|-----------------------------------|
| 12 | Configure Query Server            |
|----|-----------------------------------|
| 13 | Configure Query Server Alarm Feed |
|----|-----------------------------------|
| 14 | Configure SNMP Agent Community    |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/
Enter Choice:  2
    3. Enter option 1, Configure Provisioning Network, from the Configure Network Interfaces Menu.
      The submenu for configuring communications networks and other information is displayed. 
      
 /-----Configure Network Interfaces Menu----\
/--------------------------------------------\
|  1 | Configure Provisioning Network        |
|----|---------------------------------------|
|  2 | Configure Sync Network                |
|----|---------------------------------------|
|  3 | Configure DSM Network                 |
|----|---------------------------------------|
|  4 | Configure Backup Provisioning Network |
|----|---------------------------------------|
|  5 | Configure Forwarded Ports             |
|----|---------------------------------------|
|  6 | Configure Static NAT Addresses        |
|----|---------------------------------------|
|  7 | Configure Provisioning VIP Addresses  |
|----|---------------------------------------|
|  e | Exit                                  |
\--------------------------------------------/
Enter choice:  1
    4. Enter option 1, IPv4 Configuration (or 2 for IPv6 Configuration), from the Configure Provisioning Network Menu. 
      MPS Side A:  hostname: EPAP17  hostid: f80a110f
            Platform Version: 6.0.2-7.0.3.0.0_86.45.0
            Software Version: EPAP 161.0.28-16.1.0.0.0_161.28.0
            Wed Jun 15 01:33:56 EDT 2016

/-----Configure Provisioning Network Menu-\
/-------------------------------------------\
|  1 | IPv4 Configuration                   |
|----|--------------------------------------|
|  2 | IPv6 Configuration                   |
|----|--------------------------------------|
|  e | Exit                                 |
\-------------------------------------------/

Enter Choice:  1
    5. The following warning is displayed. Type Y and press Enter.
      
EPAP software and PDBA are running. Stop them? [N]  Y
    6. The EPAP A provisioning network IP address is displayed.
      
Verifying connectivity with mate ...
Enter the EPAP A provisioning network IP Address [192.168.61.90]:
    7. Press Enter after each address is displayed until the Default Route address is displayed.
      
Verifying connectivity with mate ...
Enter the EPAP A provisioning network IP Address [192.168.61.90]: 
Enter the EPAP B provisioning network IP Address [192.168.61.91]: 
Enter the EPAP provisioning network netmask [255.255.255.0]: 
Enter the EPAP provisioning network default router IP Address: 192.168.61.250
    8. If the default router IP address is incorrect, type the correct address and press Enter.
    9. After you have verified or corrected the Provisioning Network configuration information, enter e to return to the Configure Network Interfaces Menu.
    10. Enter e again to return to the EPAP Configuration Menu.
    11. Go to 6.
  5. Perform the following substeps to reboot the server if the syscheck output indicates the following error. Otherwise, go to 6: 
    
An active route cannot be found for a configured default route
    1. Log in as epapconfig on the server console.
      Enter option 6, Platform Menu, from the EPAP Configuration Menu. 
      
 /-------EPAP 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 | PDB Configuration Menu            |
|----|-----------------------------------|
|  9 | Security                          |
|----|-----------------------------------|
| 10 | SNMP Configuration                |
|----|-----------------------------------|
| 11 | Configure Alarm Feed              |
|----|-----------------------------------|
| 12 | Configure Query Server            |
|----|-----------------------------------|
| 13 | Configure Query Server Alarm Feed |
|----|-----------------------------------|
| 14 | Configure SNMP Agent Community    |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/
Enter Choice:  6
    2. Enter option 2, Reboot MPS, from the EPAP Platform Menu.
      At the prompt, enter the identifier of the server to which you are logged in (A or B). In this example, A is used. 
      MPS Side A:  hostname: EPAP17  hostid: f80a110f
             Platform Version: 6.0.2-7.0.3.0.0_86.45.0
             Software Version: EPAP 161.0.28-16.1.0.0.0_161.28.0
             Wed Jun 15 01:34:39 EDT 2016

/-----EPAP Platform Menu-\
/--------------------------\
|  1 | Initiate Upgrade    |
|----|---------------------|
|  2 | Reboot MPS          |
|----|---------------------|
|  3 | MySQL Backup        |
|----|---------------------|
|  4 | RTDB Backup         |
|----|---------------------|
|  5 | PDB Backup          |
|----|---------------------|
|  e | Exit                |
\--------------------------/


Enter Choice:  2
Reboot MPS A, MPS B or BOTH? [BOTH]:  A
Reboot local MPS...
    3. Wait for the reboot to complete.
    4. Go to 6.
  6. Run syscheck.
    • If the alarm is cleared, the problem is resolved.
    • If the alarm is not cleared, go to the next step.
  7. Contact My Oracle Support with the syscheck output collected in the previous steps.
  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.
  10. Run syscheck in Verbose mode.
    The output should indicate one of the following errors: 
    • The default router at <IP_address> cannot be pinged.

      This error indicates that the router may not be operating or is unreachable. If the syscheck Verbose output returns this error, go to 4. 

    • The default route is not on the provisioning network.

      This error indicates that the default route has been defined in the wrong network. If the syscheck Verbose output returns this error, contact My Oracle Support. 

    • An active route cannot be found for a configured default route.

      This error indicates that a mismatch exists between the active configuration and the stored configuration. If the syscheck Verbose output returns this error, contact My Oracle Support.

  11. Perform the following substeps when syscheck Verbose output indicates:
    
The default router at <IP_address> cannot be pinged
    1. Verify the network cables are firmly attached to the server, network switch, router, hub, and any other connection points.
    2. Verify that the configured router is functioning properly.
      Request that the network administrator verify the router is powered on and routing traffic as required.
    3. Request that the router administrator verify that the router is configured to reply to pings on that interface.
    4. Rerun syscheck:
      • If the alarm has been cleared, the problem is solved.
      • If the alarm has not been cleared, contact My Oracle Support.
  12. Contact My Oracle Support.