ID | Sub-ID | Type | MIB Trap Name | OID | Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
---|
9 | 1 | Alarm | uxAlmSIPServerNotResponding | 1.3.6.1.4.1.177.15.2.589825 | SIP Server not responding | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType | Major | | - SIP server has failed to respond and has been taken out of service.
- This alarm will be cleared by the event 'SIP server became responsive'.
|
9 | 2 | Alarm | uxAlmSignalingGroupTakenoutofService | 1.3.6.1.4.1.177.15.2.589826 | Signaling Group taken out of service | Communication | SG;PodName;ContainerType | Critical | | - All servers in SG have failed.
- This alarm will be cleared by 'SIP Signaling group enabled' event.
|
9 | 3 | Event | uxAlmSignalingGroupDisabled | 1.3.6.1.4.1.177.15.2.589827 | Signaling Group disabled | Communication | SG;PodName;ContainerType |
|
| - Configuration action has changed this Signaling Group from Enabled to Disabled.
|
9 | 4 | Alarm | uxAlmSIPTLSServerHandshakeFailure | 1.3.6.1.4.1.177.15.2.589828 | SIP-TLS Server Handshake Failure | Security | TLSProfile;IPAddress;PodName;ContainerType | Minor |
| - TLS server handshake failed with alert code.
- Action: Refer to Error Alerts in RFC 5246 for the problem.
|
9 | 5 | Alarm | uxAlmSIPTLSHandshakeInactivityTimeoutFailure | 1.3.6.1.4.1.177.15.2.589829 | SIP-TLS Handshake Inactivity Timeout Failure | Security | TLSProfile;IPAddress;PodName;ContainerType | Minor |
| - Handshake failed due to no response from peer within specified timeout.
- Action: Increase the Handshake Inactivity Timeout in TLS Profile.
|
9 | 6 | Alarm | uxAlmConfiguredPortNumberMismatch | 1.3.6.1.4.1.177.15.2.589830 | Configured port number mismatch | Processing | SG;IPAddress;Port;PodName;ContainerType | Minor |
| - Discrepancy of an FQDN/Port configured in the SipServer object that is different than the DNS SRV lookup.
- A DNS SRV record can return the port number for the selected protocol.
- The DNS SRV port value will take priority over the configured port.
|
9 | 7 | Event | uxAlmSIPServerBecameResponsive | 1.3.6.1.4.1.177.15.2.589831 | SIP Server became responsive | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType |
|
| |
9 | 8 | Alarm | uxAlmSIPclusterwentdown | 1.3.6.1.4.1.177.15.2.589832 | SIP cluster went down | Communication | SIPCluster;PodName;ContainerType | Major | | - SIP cluster went down.
- This is due to all the servers in the clusters being unresponsive.
- This alarm will be cleared by the event 'SIP Cluster Enabled'.
|
9 | 9 | Event | uxAlmSIPClusterEnabled | 1.3.6.1.4.1.177.15.2.589833 | SIP Cluster enabled | Communication | SIPCluster;PodName;ContainerType |
|
| |
9 | 10 | Event | uxAlmSIPSignalingGroupEnabled | 1.3.6.1.4.1.177.15.2.589834 | SIP Signaling group enabled | Communication | SG;PodName;ContainerType |
|
| - SIP Signaling group enabled.
|
9 | 11 | Alarm | uxAlmSIPSignalingGroupDNSFailure | 1.3.6.1.4.1.177.15.2.589835 | SIP Signaling Group: DNS Failure | Communication | SG;PodName;ContainerType | Major | | - Failed to resolve the FQDN entries in the SIP Signaling Group. [details].
|
9 | 12 | Event | uxAlmSIPSignalingGroupFQDNResolved | 1.3.6.1.4.1.177.15.2.589836 | SIP Signaling Group: FQDN Resolved | Communication | SG;PodName;ContainerType |
|
| - Successfully resolved the FQDN of the SIP Signaling group.
|
9 | 13 | Alarm | uxAlmSIPServerDNSFailure | 1.3.6.1.4.1.177.15.2.589837 | SIP Server: DNS Failure | Communication | SIPCluster;ServID;PodName;ContainerType | Major | | - Failed to resolve the SIP server FQDN entries in the SIP Server table. [details].
|
9 | 14 | Event | uxAlmSIPServerFQDNResolved | 1.3.6.1.4.1.177.15.2.589838 | SIP Server: FQDN Resolved | Communication | SIPCluster;ServID;PodName;ContainerType |
|
| - SIP Server config FQDN resolved.
|
9 | 15 | Alarm | uxAlmSIPCallSessionDNSFailure | 1.3.6.1.4.1.177.15.2.589839 | SIP call session DNS failure | Communication | SG;PodName;ContainerType | Major |
| - Failed to resolve an FQDN with DNS server during a SIP call session.
|
9 | 16 | Alarm | uxAlmAcquiringLicenseforRegisterFailed | 1.3.6.1.4.1.177.15.2.589840 | Acquiring license for Register failed | Communication | SG;PodName;ContainerType | Major |
| - Failed to acquire license from License Manager.
|
9 | 17 | Alarm | uxAlmSessionorOtherResourceLeak | 1.3.6.1.4.1.177.15.2.589841 | Session or other resource leak | Communication | SG;PodName;ContainerType | Major |
| - SIP performs self-check for leaks.
- Please enable logging for SIP and issue 'show resources' command.
|
9 | 18 | Alarm | uxAlmFailedtoBindtoNetworkInterface | 1.3.6.1.4.1.177.15.2.589842 | Failed to bind to network interface | Communication | SG;PodName;ContainerType | Minor |
| - Failed to bind to network interface due to dynamic IP address not available.
|
9 | 19 | Event | uxAlmSuccessfullyBoundtoNetworkInterface | 1.3.6.1.4.1.177.15.2.589843 | Successfully bound to network interface | Communication | SG;PodName;ContainerType |
|
| - Successfully bound to network interface.
- DHCP lease renewed.
|
9 | 20 | Alarm | uxAlmSIPRegisterServerNotResponding | 1.3.6.1.4.1.177.15.2.589844 | SIP Register Server not responding | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType | Major | | - SIP Register server has failed to respond.
- This alarm will be cleared by the event 'SIP Regular server became responsive'.
|
9 | 21 | Event | uxAlmSIPRegisterServerBecameResponsive | 1.3.6.1.4.1.177.15.2.589845 | SIP Register Server became responsive | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType |
|
| - SIP Register server came up.
|
9 | 22 | Alarm | uxAlmRegistrationNotValidReceivedstalefalse | 1.3.6.1.4.1.177.15.2.589846 | Registration not valid; received stale=false | Communication | SG;AorName;PodName;ContainerType | Major | | - Stale=false/Registration no longer valid due to incorrect credentials.
|
9 | 23 | Event | uxAlmConfigChangeforSIPEndpointThatReceivedstalefalse | 1.3.6.1.4.1.177.15.2.589847 | Config change for SIP endpoint that received stale=false | Communication | SG;AorName;PodName;ContainerType |
|
| - Config has changed, clear StaleIsFalse Alarm.
|
9 | 24 | Alarm | uxAlmQoENotifyMessageResponseWasNotSuccessful | 1.3.6.1.4.1.177.15.2.589848 | QoE Notify Message response was not successful | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType | Minor | | - QoE Notify Message received a no response or a failed response.
- This alarm will be cleared by the event 'QoE Notify Message received a successful response'.
|
9 | 25 | Event | uxAlmQoENotifyMessageResponseWasSuccessful | 1.3.6.1.4.1.177.15.2.589849 | QoE Notify Message Response was successful | Communication | SG;PodName;ContainerType |
| | - QOE Notify Message received a successful response.
|
9 | 26 | Alarm | uxAlmSystemOverloadDetected | 1.3.6.1.4.1.177.15.2.589850 | System overload detected | Communication | System;Service;PodName;ContainerType | Minor | | - System processing is overloaded.
|
9 | 27 | Event | uxAlmSystemOverloadCleared | 1.3.6.1.4.1.177.15.2.589851 | System overload cleared | Communication | System;Service;PodName;ContainerType |
|
| - System processing resumes standard operation, overload cleared.
|
9 | 28 | Alarm | uxAlmMaximumNumberofSIPSessionsReached | 1.3.6.1.4.1.177.15.2.589852 | Maximum Number of SIP Sessions Reached | Communication | SG;PodName;ContainerType | Minor | | - The maximum number of SIP sessions (calls/register/subscribe) has been reached on the signaling group.
- Increase the number of SIP Channels for the signaling group.
|
9 | 29 | Event | uxAlmMaximumNumberofSIPSessionsAlarmCleared | 1.3.6.1.4.1.177.15.2.589853 | Maximum Number of SIP Sessions Alarm Cleared | Communication | SG;PodName;ContainerType |
|
| - SIP sessions per signaling group is under the maximum limit.
|
9 | 30 | Alarm | uxAlmErrorresolvingSRVrecord | 1.3.6.1.4.1.177.15.2.589854 | Error resolving SRV record | Communication | SIPCluster;ServID;PodName;ContainerType | Major | | - Failed to run SRV record query.
- Suggested action - confirm that DNS server network is reachable, check SRV and DNS server configuration.
|
9 | 31 | Event | uxAlmSRVrecordresolved | 1.3.6.1.4.1.177.15.2.589855 | SRV record resolved | Communication | SIPCluster;ServID;PodName;ContainerType | None |
| - DNS server returned valid SRV record(s).
|
9 | 32 | Alarm | uxAlmSIPTLSHandshakeNegotiationStartFailure | 1.3.6.1.4.1.177.15.2.589856 | SIP-TLS Handshake Negotiation Start Failure | Security | TLSProfile;IPAddress;PodName;ContainerType | Critical | | - [server] handshake failed to start with invalid certificate; [connectionID], [portID].
- Action: confirm that both signed Ribbon SBC Edge Certificate and Trusted CA Certificate exist.
|
9 | 33 | Event | uxAlmSIPTLSHandshakeNegotiationStartSuccessful | 1.3.6.1.4.1.177.15.2.589857 | SIP-TLS Handshake Negotiation Start Successful | Security | TLSProfile;IPAddress;PodName;ContainerType | None | | - Handshake response was started with valid certificate on local and remote gateway.
- This event clears the 'SIP-TLS Handshake Negotiation Start Failure' alarm.
|
9 | 34 | Event | uxAlmMaximumsupportedSIPSGsreached | 1.3.6.1.4.1.177.15.2.589858 | Maximum supported SIP SGs reached | General | System;Service;PodName;ContainerType | Warning | | - SIP signaling group count reached maximum supported limit.
|
9 | 35 | Event | uxAlmMaximumsupportedSIPSGscleared | 1.3.6.1.4.1.177.15.2.589859 | Maximum supported SIP SGs cleared | General | System;Service;PodName;ContainerType | None |
| - SIP signaling group count is under the maximum supported.
|
9 | 36 | Alarm | uxAlmMaximumnonSIPCallSessionsreached | 1.3.6.1.4.1.177.15.2.589860 | Maximum non-SIP call sessions reached | General | System;Service;PodName;ContainerType | Warning | | - Number of SIP non-call sessions is over the system capacity.
|
9 | 37 | Event | uxAlmMaximumnonSIPCallSessionscleared | 1.3.6.1.4.1.177.15.2.589861 | Maximum non-SIP call sessions cleared | General | System;Service;PodName;ContainerType | None |
| - Number of SIP non-call sessions is under the system capacity.
|
9 | 38 | Alarm | uxAlmMaximumSIPCallSessionsreached | 1.3.6.1.4.1.177.15.2.589862 | Maximum SIP call sessions reached | General | System;Service;PodName;ContainerType | Warning | | - Number of SIP call sessions is over the system capacity.
|
9 | 39 | Event | uxAlmMaximumSIPCallSessionscleared | 1.3.6.1.4.1.177.15.2.589863 | Maximum SIP call sessions cleared | General | System;Service;PodName;ContainerType | None |
| - Number of SIP call sessions is under the system capacity.
|
9 | 40 | Alarm | uxAlmBroadsoftSIPCallrerouted | 1.3.6.1.4.1.177.15.2.589864 | Broadsoft SIP call re-routed | General | SG;PodName;ContainerType | Warning | | - Broadsoft SIP call re-routed.
|
9 | 41 | Event | uxAlmBroadsoftSIPCallReroutedcleared | 1.3.6.1.4.1.177.15.2.589865 | Broadsoft SIP Call re-routed cleared | General | SG;PodName;ContainerType | None |
| - Broadsoft SIP call re-routed cleared.
|
9 | 42 | Alarm | uxAlmSIPSGListenProtocolandSIPServerHostProtocolmismatch | 1.3.6.1.4.1.177.15.2.589866 | SIP SG Listen Protocol and SIP Server Host Protocol mismatch | Processing | SIPCluster;ServID;PodName;ContainerType | Minor |
| - Verify that the listen ports and protocols for the SG match those in the server table.
|
9 | 43 | Alarm | uxAlmConfigurationErrorSIPSGandServerProtocolMismatch | 1.3.6.1.4.1.177.15.2.589867 | Configuration Error: SIP SG and Server Protocol Mismatch | Processing | SIPCluster;ServerID or SIPCluster;ServID;PodName;ContainerType | Major |
| - Verify that the listen ports and protocols for the SG match those in the server table.
|
9 | 44 | Alarm | uxAlmSIPTLSClientHandshakeFailure | 1.3.6.1.4.1.177.15.2.589868 | SIP-TLS Client Handshake Failure | Security | TLSProfile;IPAddress;PodName;ContainerType | Minor | | - TLS client handshake failed with alert code.
- Action: Refer to Error Alerts in RFC 5246 for the problem.
|
9 | 45 | Event | uxAlmSIPTLSHandshakeInactivityTimeoutCleared | 1.3.6.1.4.1.177.15.2.589869 | SIP-TLS Handshake Inactivity Timeout Cleared | Security | TLSProfile;IPAddress;PodName;ContainerType |
|
| - Handshake response was received within specified timeout.
- This event clears the 'SIP-TLS Handshake Inactivity Timeout Failure' alarm.
|
9 | 46 | Event | uxAlmSIPTLSServerHandshakeFailureCleared | 1.3.6.1.4.1.177.15.2.589870 | SIP-TLS Server Handshake Failure Cleared | Security | TLSProfile;IPAddress;PodName;ContainerType |
|
| - Handshake failure error alert condition was cleared.
- This event clears the 'SIP-TLS Server Handshake Failure' alarm.
|
9 | 47 | Event | uxAlmSIPTLSClientHandshakeFailureCleared | 1.3.6.1.4.1.177.15.2.589871 | SIP-TLS Client Handshake Failure Cleared | Security | TLSProfile;IPAddress;PodName;ContainerType |
|
| - Handshake failure error alert condition was cleared.
- This event clears the 'SIP-TLS Client Handshake Failure' alarm.
|
9 | 48 | Alarm | uxAlmSkypeLyncPresenceServerResponseFailure | 1.3.6.1.4.1.177.15.2.589872 | Skype/Lync Presence Server Response Failure
| Communication | SIPCluster;PodName;ContainerType | Minor | | - A Presence Publish Request has been sent to the configured Lync Presence Front End and has received no response or a failed response.
|
9 | 49 | Alarm | uxAlmSkypeLyncPresenceServerResponseFailureCleared | 1.3.6.1.4.1.177.15.2.589873 | Skype/Lync Presence Server Response Failure Cleared | Communication | SIPCluster;PodName;ContainerType | Minor | | - A presence server that previously was unreachable has successfully sent a message that the SBC has received.
|
9 | 50 | Alarm | uxAlmSIPRequestfromUntrustedIP | 1.3.6.1.4.1.177.15.2.589874 | SIP Request from Untrusted IP | Security | IPAddress;PodName;ContainerType | Minor |
| - An INVITE message was received from a host without a matching Federated IP.
|
9 | 51 | Alarm | uxAlmSIPRequestfromUntrustedIPCleared | 1.3.6.1.4.1.177.15.2.589875 | SIP Request from Untrusted IP Cleared | General | IPAddress;PodName;ContainerType | Major |
| - Source IP is added to the list of federated IP addresses.
|
9 | 52 | Alarm | uxAlmReSyncmessagereceivedonSGnotselectedforAutoConfigtask | 1.3.6.1.4.1.177.15.2.589876 | Resync message received on SG, not selected for Auto Config task. | Processing | SG;PodName;ContainerType | Major |
| - Check Auto configuration Task settings and verify that the Signaling Group selected is correct.
|
9 | 53 | Alarm | uxAlmMaximumNumberofSkypeLyncPresenceSessionsReached | 1.3.6.1.4.1.177.15.2.589877 | Maximum Number of Skype/Lync Presence Sessions Reached | Communication | SG;PodName;ContainerType | Minor | | - The maximum number of 500 concurrent SIP Publish sessions for Presence has been reached.
- Skype/Lync Presence processing will be suspended until the number of concurrent sessions drops below 500 limit.
|
9 | 54 | Event | uxAlmMaximumNumberofS4BPresencePublishSessionsAlarmCleared | 1.3.6.1.4.1.177.15.2.589878 | Maximum Number of S4B Presence Publish Sessions Alarm Cleared | Communication | SG;PodName;ContainerType |
| | - SIP Publish sessions for S4B Presence is under the maximum limit.
|
9 | 55 | Alarm | uxAlmEnableMonitoringonSkypePresenceServerforbetterreliability | 1.3.6.1.4.1.177.15.2.589879 | Enable Monitoring on Skype Presence Server for better reliability | Communication | SIPCluster;PodName;ContainerType | Minor | | - Enable Monitoring on Skype Presence Server for better reliability.
|
9 | 56 | Event | uxAlmMonitoringonSkypePresenceServerhasbeenenabled | 1.3.6.1.4.1.177.15.2.589880 | Monitoring on Skype Presence Server has been enabled | Communication | SIPCluster;PodName;ContainerType |
|
| - Monitoring on Skype Presence Server has been enabled.
|
9 | 57 | Alarm | uxAlmTheSIPVoiceQualityServerConnectionisBroken | 1.3.6.1.4.1.177.15.2.589881 | The SIP Voice Quality Server Connection is Broken | Communication | Protocol;IPAddress;Port;PodName;ContainerType | Major | | - Suggested Action: Verifying the IP, Port, Protocol, and Certificate (if TLS) are Correct.
|
9 | 58 | Event | uxAlmTheSIPVoiceQualityServerConnectionisResumed | 1.3.6.1.4.1.177.15.2.589882 | The SIP Voice Quality Server Connection is Resumed | Communication | Protocol;IPAddress;Port;PodName;ContainerType |
|
| - The SIP Voice Quality Server Connection is Resumed.
|
9 | 59 | Alarm | uxAlmTheVoiceQualityNotifyRejectedbytheSIPVoiceQualityServer | 1.3.6.1.4.1.177.15.2.589883 | The Voice Quality Notify Rejected by the SIP Voice Quality Server | Communication | IPAddress;Port;PodName;ContainerType | Warning | | - Suggested Action: Examining the Notify Response Code and the Reason Header (if included) to understand why it was rejected.
|
9 | 60 | Alarm | uxAlmTheVoiceQualityNotifyAcceptbyTheSIPVoiceQualityServer | 1.3.6.1.4.1.177.15.2.589884 | The Voice Quality Notify Accept by the SIP Voice Quality Server | Communication | IPAddress;Port;PodName;ContainerType |
|
| - The Voice Quality Notify has been accepted by the SIP Voice Quality Server.
|
9 | 61 | Alarm | uxAlmFailedtoResolvetheFQDNoftheSIPVoiceQualityServer | 1.3.6.1.4.1.177.15.2.589885 | Failed to Resolve the FQDN of the SIP Voice Quality Server | Communication | IPAddress;PodName;ContainerType | Warning |
| - Failed to Resolve FQDN of the SIP Voice Quality Server.
- Suggested action - confirm the DNS access and FQDN.
|
9 | 62 | Event | uxAlmtheSIPVoiceQualityServerFQDNhasbeenResolved | 1.3.6.1.4.1.177.15.2.589886 | The SIP Voice Quality Server FQDN has been Resolved | Communication | IPAddress;PodName;ContainerType |
|
| - The SIP Voice Quality Server FQDN has been resolved.
|
9 | 63 | Alarm | uxAlmConfiguredRegistrationLimitreached | 1.3.6.1.4.1.177.15.2.589887 | Configured Registration Limit Reached | Communication | SIPRegistrarTable;PodName;ContainerType | Warning | | - Configured Registration Limit reached.
- New SIP Registrations will be rejected until the number of registered users drops below maximum number of users configured for the Registrar.
|
9 | 64 | Event | uxAlmConfiguredRegistrationLimitCleared | 1.3.6.1.4.1.177.15.2.589888 | Configured Registration Limit Cleared | Communication | SIPRegistrarTable;PodName;ContainerType |
|
| - Configured Registration Limit cleared.
|
9 | 65 | Alarm | uxAlmSignalingMediasourceIPissettoAuto | 1.3.6.1.4.1.177.15.2.589889 | Signaling/Media source IP is set to Auto | Communication | SG;PodName;ContainerType | Minor | | - Signaling/Media source IP is set to Auto and default route uses Admin interface.
|
9 | 66 | Event | uxAlmSignalingMediasourceIPissettoAutocleared | 1.3.6.1.4.1.177.15.2.589890 | Signaling/Media source IP is set to Auto cleared | Communication | SG;PodName;ContainerType |
|
| - Signaling/Media source IP is set to Auto cleared.
|
9 | 67 | Alarm | uxAlmSIPRecordingServerNotResponding | 1.3.6.1.4.1.177.15.2.589891 | SIP Recording Server Not Responding | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType | Major | | - SIP Recording server has failed to respond and has been taken out of service.
- This alarm will be cleared by the event 'SIP Recording server became responsive'.
|
9 | 68 | Event | uxAlmSIPRecordingServerBecameResponsive | 1.3.6.1.4.1.177.15.2.589892 | SIP Recording Server Became Responsive | Communication | SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType
|
|
| - SIP Recording server came up.
|
9 | 69 | Alarm | uxAlmSCSLBconnectionisdown | 1.3.6.1.4.1.177.15.2.589893 | SC-SLB connection is down | Communication | System;PodName;ContainerType | Critical | | - Signaling container connection with SLB container is down.
|
9 | 70 | Event | uxAlmSCSLBconnectionisup | 1.3.6.1.4.1.177.15.2.589894 | SC-SLB connection is up | Communication | System;PodName;ContainerType |
|
| - Signaling container connection with SLB container is up.
|
9 | 71 | Alarm | uxAlmSCCACconnectionisdown | 1.3.6.1.4.1.177.15.2.589895 | SC-CAC connection is down | Communication | System;PodName;ContainerType | Major | | - Signaling container connection with CAC Manager is Down.
- Node: [nodename].
- Login into CAC Manager Pod debug CLI to verify current operational status.
|
9 | 72 | Event | uxAlmSCCACconnectionisup | 1.3.6.1.4.1.177.15.2.589896 | SC-CAC connection is up | Communication | System;PodName;ContainerType |
|
| - Signaling container connection with CAC Manager is Up.
- Node: [nodename].
|
9 | 73 | Alarm | uxAlmCallAccessControlDenied | 1.3.6.1.4.1.177.15.2.589897 | Call Access Control Denied | Communication | SG;PodName;ContainerType | Warning | | - Call Access Control Denied Over [num] percent calls: Rejects: [num] Timeouts: [num] Sendfail: [num] Unknown: [num].
|
9 | 74 | Alarm | uxAlmSLBDiscoveryFailure | 1.3.6.1.4.1.177.15.2.589898 | SLB Discovery Failure | Communication | System;PodName;ContainerType | Critical | | - SLB discovery failure because of kubeapi failure.
|
9 | 75 | Event | uxAlmSLBDiscoverySuccess | 1.3.6.1.4.1.177.15.2.589899 | SLB Discovery Success | Communication | System;PodName;ContainerType | Major |
| |
9 | 76 | Alarm | uxAlmMediaIPAssociationfailed | 1.3.6.1.4.1.177.15.2.589900 | Media IP Associated failed | Communication | Interface;PodName;ContainerType | Major |
| - Public IP Association to SC failed.
|
9 | 77 | Event | uxAlmMediaIpAssociationsuccessful | 1.3.6.1.4.1.177.15.2.589901 | Media IP Association Successful | Communication | Interface;PodName;ContainerType |
|
| - Public IP Association to SC successful: [ip address].
|
9 | 78 | Alarm | uxAlmSignalingContainerMemoryreachedThreshold | 1.3.6.1.4.1.177.15.2.589902 | Signaling Container Memory reached Threshold | Communication | Interface;PodName;ContainerType | Major | | - Signaling container memory reached above [percent] percent threshold.
|
9 | 79 | Event | uxAlmSignalingContainerMemoryRechedBelowThreshold | 1.3.6.1.4.1.177.15.2.589903 | Signaling Container Memory Reched Below Threshold | Communication | Interface;PodName;ContainerType |
|
| - Signaling container memory reached below threshold.
|
9 | 80 | Event | uxAlmCallAccessControlDeniedCleared | 1.3.6.1.4.1.177.15.2.589904 | Call Access Control Denied Cleared | Communication | SG;PodName;ContainerType |
|
| - Call Access Control Denied condition cleared.
|