The following list provides the alarms and events defined for System Health Monitor. 

ID

Sub-ID

Type

MIB Trap NameOID

Condition

Category

Decode Key

Default Severity

Auto Clear

Notes/Description

16

1

Alarm

uxAlmApplicationServicerestarted1.3.6.1.4.1.177.15.2.1048577

Application Service restarted

Processing

Service;PodName;ContainerType

Major


  • An SBC Edge Application service was restarted.
  • Contact Ribbon Service with the information in this alarm and any core files present.
  • These can be found in Diagnostics->Restart Report under the 'Core Files' tab.

16

2

Alarm

uxAlmActivepartitionswitched1.3.6.1.4.1.177.15.2.1048578

Active partition switched

Processing

Partition;PodName;ContainerType

Major


  • System detected a problem during previous boot cycle, active partition has switched automatically.
  • Suggested Action: Backup the configuration and re-apply the upgrade to the currently inactive partition.

16

3

Alarm

uxAlmFailedtomountpartition1.3.6.1.4.1.177.15.2.1048579

Failed to mount partition

Processing

Partition;PodName;ContainerType

Major


  • Mounting failed for partition [number].

16

4

Alarm

uxAlmFailedtosetactivepartition1.3.6.1.4.1.177.15.2.1048580

Failed to set active partition

Processing

Partition;PodName;ContainerType

Major


  • Failed to set active partition.
  • Contact Ribbon Service with the information in this alarm.

16

5

Alarm

uxAlmAttempttorepairbootparametermismatchfailed1.3.6.1.4.1.177.15.2.1048581

Attempt to repair boot parameter mismatch failed.

Processing

Partition;PodName;ContainerType

Major


  • Attempt to auto repair boot parameters failed.
  • Contact Ribbon Service with the information in this alarm.

16

6

Alarm

uxAlmBootparametermismatchdetected1.3.6.1.4.1.177.15.2.1048582

Boot parameter mismatch detected

Processing

Partition;PodName;ContainerType

Major


  • Boot parameter mismatch was detected.
  • Attempting to auto repair.

16

7

Alarm

uxAlmFailedPoweronmemoryselftest1.3.6.1.4.1.177.15.2.1048583

Failed Power-on memory self test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

8

Alarm

uxAlmFailedPoweronCoreSwitchtest1.3.6.1.4.1.177.15.2.1048584

Failed Power-on Core Switch test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

9

Alarm

uxAlmFailedPoweronSecondarySwitchtest1.3.6.1.4.1.177.15.2.1048585

Failed Power-on Secondary Switch test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

10

Alarm

uxAlmFailedPoweronexternalQuadPHYtest1.3.6.1.4.1.177.15.2.1048586

Failed Power-on external Quad PHY test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

11

Alarm

uxAlmFailedPoweronexternalSinglePHYtest1.3.6.1.4.1.177.15.2.1048587

Failed Power-on external Single PHY test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

12

Alarm

uxAlmFailedPoweronCPUPHYtest1.3.6.1.4.1.177.15.2.1048588

Failed Power-on CPU PHY test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

13

Alarm

uxAlmFailedPoweronTSItest1.3.6.1.4.1.177.15.2.1048589

Failed Power-on TSI test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

14

Alarm

uxAlmFailedPoweroninternal5PortPHYtest1.3.6.1.4.1.177.15.2.1048590

Failed Power-on internal 5-Port PHY test

Equipment

Partition;PodName;ContainerType

Critical


  • Power-on self test failure.

16

15

Event

uxAlmSystemUpAfterPlannedRestart1.3.6.1.4.1.177.15.2.1048591

System Up After Planned Restart

Equipment

System;PodName;ContainerType



  • System up after planned restart.
  • Reboot reason [reason].

16

16

Alarm

uxAlmSystemUpAfterUnplannedRestart1.3.6.1.4.1.177.15.2.1048592

System Up After Unplanned Restart

Equipment

System;PodName;ContainerType

Major


  • System up after unplanned restart.
  • Reboot reason [reason].
1617AlarmuxAlmEnteredpasswordrecoverymode1.3.6.1.4.1.177.15.2.1048593Entered password recovery modeSecuritySystem;PodName;ContainerTypeMajor
  • SBC has entered password recovery mode.
1618EventuxAlmExitedpasswordrecoverymode1.3.6.1.4.1.177.15.2.1048594Exited password recovery modeSecuritySystem;PodName;ContainerType

  • SBC has exited password recovery mode.
1619AlarmuxAlmFailedtomountUSBstoragedevice1.3.6.1.4.1.177.15.2.1048595Failed to mount USB storage deviceEquipmentSystem;Service;PodName;ContainerTypeMajor
  • SBC discovered USB storage.
  • SBC can mount flash drives formatted with FAT32 file system only.
1620EventuxAlmUSBstoragedeviceconnected1.3.6.1.4.1.177.15.2.1048596USB storage device connectedEquipmentSystem;Service;PodName;ContainerType

  • USB storage device is connected.
1621AlarmuxAlmUSBstoragedevicedisconnected1.3.6.1.4.1.177.15.2.1048597USB storage device disconnectedEquipmentSystem;Service;PodName;ContainerTypeWarning
  • USB storage device is disconnected.
  • This alarm will be cleared when USB drive is connected.
1622AlarmuxAlmCriticalapplicationcrash1.3.6.1.4.1.177.15.2.1048598Critical application crashProcessingService;PodName;ContainerTypeCritical
  • A critical SBC Edge application has crashed, and the system will be restarted.
  • Contact Ribbon Service with the information in this alarm and any core files present.
  • These can be found in Diagnostics->Restart Report/Core Files tab.
1623AlarmuxAlmOlderfirmwaredetected1.3.6.1.4.1.177.15.2.1048599Older firmware detectedProcessingSystem;Service;PodName;ContainerTypeCritical
  • A USB firmware update is available.
  • To perform upgrade, please first load SW release v4.1.1.
1624EventuxAlmAutoConfigurationsuccessful1.3.6.1.4.1.177.15.2.1048600Auto Configuration successfulEquipmentSystem;Service;PodName;ContainerType

  • Auto Configuration successful after receiving SIP NOTIFY message.
1625AlarmuxAlmAutoConfigurationfailed1.3.6.1.4.1.177.15.2.1048601Auto Configuration failedProcessingSystem;Service;PodName;ContainerTypeMajor
  • Failed to perform Auto Configuration after receiving SIP NOTIFY message.
1626AlarmuxAlmSoftwareUpdateinprogress1.3.6.1.4.1.177.15.2.1048602Software Update in progressProcessingSystem;Service;PodName;ContainerTypeMajor
  • Current SIP NOTIFY message cannot be processed as software update is in progress.
1627AlarmuxAlmNodeReboot1.3.6.1.4.1.177.15.2.1048603Node RebootEquipmentService;PodName;ContainerTypeMinor
  • Node Reboot requested by user [Username] from [ipAddress].
1628AlarmuxAlmFactoryDefault1.3.6.1.4.1.177.15.2.1048604Factory DefaultEquipmentService;PodName;ContainerTypeMajor
  • Full factory default requested by user [Username] from [ipAddress].
1629AlarmuxAlmInvalidSystemMemory1.3.6.1.4.1.177.15.2.1048605Invalid System MemoryEquipmentSystem;Service;PodName;ContainerTypeMajor
  • Unexpected memory size for virtual CPU detected.
  • Please consult documentation for memory requirement.
1630AlarmuxAlmResetButtonFactoryDefault1.3.6.1.4.1.177.15.2.1048606Reset Button Factory DefaultEquipmentService;PodName;ContainerTypeMajor
  • Full factory default requested via hardware reset button.
1631Alarm

uxAlmSCMCconnectionisdown

1.3.6.1.4.1.177.15.2.1048607

SC-MC connection is downProcessingService;PodName;ContainerTypeCritical
  • Signaling container connection with media container is down.
1632Alarm

uxAlmSwitchoverToActive

1.3.6.1.4.1.177.15.2.1048608Switchover To ActiveCommunicationIPAddressMinor
  • Logged when the Standby instance switches to the active role.
  • Event Text: System has switched to active HA role.
1633Alarm

uxAlmLostHAProtection

1.3.6.1.4.1.177.15.2.1048609Lost HA ProtectionCommunicationIPAddressMajor(tick)
  • Logged when the Standby instance has gone offline.
  • Event Text: Peer HA node has gone offline.
1634Event

uxAlmHAProtectionRestored

1.3.6.1.4.1.177.15.2.1048610HA Protection RestoredCommunicationIPAddressNone
  • Event Text: Peer HA node has come back online.
  • Clears alarm 16.33.
1635Alarm

uxAlmNoSpaceAvailableInRootPartition

1.3.6.1.4.1.177.15.2.1048611No Space Available In Root PartitionEquipmentSystemCritical
  • No space is available in the root partition.
  • Suggested action: upload new firmware image and cut over partition. If the problem is still present afterwards, call TAC.
  • No labels