3.16.119 32112 - Device interface failure

Alarm Group:
PLAT
Description:
This alarm indicates either the IP bond is not configured or is down.
Severity:
Critical
Instance:
May include AlarmLocation, AlarmId, AlarmState, AlarmSeverity, and bindVarNamesValueStr
HA Score:
Normal
Auto Clear Seconds:
0 (zero)
OID:
eagleXgDsrTpdDeviceIfFailureNotify
Cause:
This alarm indicates either the IP bond is not configured or down.
Diagnostic Information:
  • Syscheck can be manually executed in the following methods:
    • Login as syscheck. When logging in, syscheck runs and then the login connection is dropped. This account does not have shell access.
    • From the root accoun,t the Command Line Interface can be utilized directly.
      • Execute syscheck -h for usage information.
    • In DSR 6.0 and later, from the admusr account the Command Line Interface can be used directly when called using sudo.
      • Execute syscheck -h for usage information.
    • Using the platcfg user interface.

      Note:

      In versions later than TPD 6.5, root access using SSH is disabled. The admusr should be used instead. If the command is to be run as admusr, sudo must be prepended to the command and the full path to the command must be used.
  • sudo /usr/TKLC/plat/bin/netAdm query --device=<bondX>
  • sudo /usr/TKLC/plat/bin/netAdm query --device=<slave device>
  • cat /proc/net/bonding/bondX, where X is bond designation
  • ethtool <slave device>

Recovery:

  1. Run syscheck in verbose mode by executing syscheck -h for usage information.
  2. Investigate the failed bond and slave devices configuration using netAdm query:
    • sudo /usr/TKLC/plat/bin/netAdm query --device=<bondX>
    • sudo /usr/TKLC/plat/bin/netAdm query --device=<slave device>
  3. Determine if the failed bond and slave devices have been administratively shut down or have operational issues:
    • cat /proc/net/bonding/bondX, where X is bond designation
    • ethtool <slave device>
  4. If bond and slaves are healthy, attempt to administratively bring bond up:
    • ifup bondX
  5. If condition persists, contact My Oracle Support and provide the system health check output and output of steps 1 through 4.
  6. It is recommended to contact My Oracle Support to request hardware replacement.