Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c8613a801e016167f8a31a002b, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}


The SBC

Spacevars
0product
generates an alarm when it detects that an internal micro-service, such as a Service Discovery micro-service, is unresponsive. The alarm clears when the micro-service becomes operational again.

Service Discovery for Trap Target Destinations and EMS Registration

With regard to

When the

Spacevars
0product
performs Service Discovery for trap target destinations and

EMS

Spacevars
0model3
registration, the

SBC

Spacevars
0product
generates an alarm, sonusMicroServiceConnectionFailed, when it detects that its internal Service Discovery micro-service is unresponsive. The alarm clears with alarm sonusMicroServiceConnectionSucceeded when the micro-service becomes operational again. For more information about Service Discovery, see Service Discovery for Trap Target Destinations and RAMP Registration.

In addition, the SBC generates alarms when a DNS server is blacklisted or recovers from a blacklisted state. For these alarm descriptions, refer to sonusSbxDnsServerBlacklistedNotification - CRITICAL and sonusSbxDnsServerRecoveredNotification - CRITICAL.

This section contains the following Internal Micro-Services alarms.

Children Display
alltrue

 
Pagebreak