ID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
1 | 1 | alarm | AD caching failed | communication | System;Service;IPAddress | minor | 
| - Failed to cache attributes from AD in memory.
- Suggested action - try again later.
- This alarm will be cleared by event AD caching successful.
| 1 | 2 | event | Online AD query failed | communication | System;Service |
| |
|
| - Failed to execute AD query.
- Suggested action - confirm that AD is network reachable, check the AD configuration as well as AD access credentials.
| 1 | 4 | event | User logged in | security | Username;IPAddress |
| |
|
| - New user [username] logged in from [ip address] at [time].
| 1 | 5 | alarm | User login failed | security | Username;IPAddress | major |
| - User [username] login failed from [ip address] at [time].
- This alarm will be cleared by event User logged in.
| 1 | 6 | alarm | AD Unreachable | communication | System:Service;IPAddress; DCType | major |
| - Either AD is network unreachable, or the AD credentials are invalid.
- DCType will be either Authentication or Call Route
- This alarm will be cleared by 'AD Reachable' event.
| 1 | 7 | event | AD Reachable | communication | System:Service;IPAddress; DCType |
| |
|
| - Active directory is now reachable.
- DCType will be either Authentication or Call Route
| 1 | 8 | event | AD caching successful | communication | System:Service;IPAddress |
|
|
| - AD caching was successful.
| 1 | 9 | alarm | AD backup failed | equipment | System:Service;IPAddress | minor |
| - Failed to backup cached values from AD to storage device.
- Either the storage device is not present, or it is full.
- Contact Ribbon for further assistance.
| 1 | 10 | event | AD successfully backed up | equipment | System:Service;IPAddress |
|
|
| - Successful backup of cached values from AD to storage device.
| 1 | 11 | alarm | AD cache truncated | equipment | System:Service | minor |
|
| - AD Cache is truncated, AD cache results have exceeded the maximum cache size.
- Consider caching only the required attributes.
- If the query is not found in cache, Online query will be performed, while affecting performance.
| 1 | 12 | alarm | RADIUS Server Unreachable | communication | System:Service;IPAddress | major |
| - Either the RADIUS server is network unreachable, or the configuration is incorrect.
- Suggested action - check shared secret, listening port, RADIUS server IP.
- This alarm will be cleared by 'RADIUS Reachable' event.
| 1 | 13 | event | RADIUS Reachable | communication | System:Service;IPAddress |
| |
|
| | 1 | 14 | alarm | CDR logging failed | communication | System:Service;IPAddress | major |
|
| - SBC 1000/2000 failed to send CDR to RADIUS based accounting server.
- Either the RADIUS server is network unreachable, or the configuration is incorrect.
- Suggested action - check shared secret, listening port, RADIUS server IP.
| 1 | 15 | alarm | CDR backup failed | communication | System:Service;IPAddress | major |
|
| - SBC 1000/2000 failed to backup CDR in local file.
- Either running with low disk space or CDR backup maximum limit is crossed.
- Suggested action - Free up the disk space or save the CDR Queued file for future reference.
| 1 | 17 | event | User password changed successfully | Security | Username |
| | If | Info |
|---|
| 1 | 18 | alarm | User password change failed | Security | Username | warning |
| |
| Info |
|---|
| 1 | 19 | event | User account disabled | Security | Username |
| |
|
| - Event Text: User 'username' account has been disabled by 'username' from 'IP address'.
| 1 | 20 | event | User account activated | Security | Username |
| |
|
| - Event Text: User 'username' account has been activated by 'username' from 'IP address'.
| 1 | 21 | event | Global Security Options Changed | Security | Username;IPAddress |
| |
|
| - Event Text: Global security options changed by 'username' from 'IP address'.
| 1 | 22 | alarm | User login blocked | Security | Username | major |
| - Event Text: User 'username' blocked from login due to excessive incorrect login attempts.
- Cleared by event 1.23 - User login unblocked.
| 1 | 23 | event | User login unblocked | Security | Username |
| |
|
| - Event Text: User 'username' unblocked.
| | 1 | 24 | event | User password expired | Security | Username;IPAddress |
| |
|
| | | 1 | 25 | alarm | AD: Maximum Threads Exceeded | Processing | System;Service | major |
|
| - AD has reached maximum threads. Please inform your service representative.
| | 1 | 26 | alarm | AD caching timed out | Communication | System;Service;IPAddress | minor |
|
| Timed out caching attributes due to lack of response from AD. Suggested action - try again later. The SBC will attempt to load the last successful cache from backup. | | 1 | 27 | alarm | AD Cache Encryption Failed | System | System;Service;IPAddress | major | | AD Cache encryption failed. Cache will not be saved. Cleared by event 1.28 | | 1 | 28 | event | AD Cache Encryption Successful | System | System;Service;IPAddress |
| |
|
| AD Cache encryption successful. Cleared alarm 1.27 (AD Cache Encryption Failed) |
Resource ManagerID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
2 | 1 | alarm | Invalid Card ID EEPROM Data | equipment | System;Card | critical |
|
| - A Card was detected with invalid Card ID EEPROM contents (failed CRC-CCITT check).
- Suggested action - provide the entire alarm message including the numbers at the end to Ribbon Support for further assistance.
| 2 | 2 | alarm | Card Health Check Failed | equipment | System;Card | critical |
|
| - During Line Card activation, a Card Fault was detected after power was applied to the card.
- The Card will remain out-of-service.
- Suggested action - reboot system.
- If issue persists, contact Ribbon Support with the alarm information.
| 2 | 3 | alarm | Card not Supported | equipment | System;Card | major |
|
| - A Card was detected which can be identified, but the SBC 1000/2000 system software is unable to support.
- The Card will remain out-of-service.
- Suggested action - reboot system.
- If issue persists, contact Ribbon with the alarm information.
| 2 | 4 | alarm | Power Supply input failure | equipment | System;PSU | major |
| - A Power supply module has indicated a failure of input power.
- The SBC 1000/2000 System has lost Power Supply redundancy.
- Suggested action - Verify that the power cable is connected and that the PS is functioning properly.
| 2 | 5 | event | Power Supply input restored | equipment | System;PSU |
|
|
| - A Power Supply module has indicated that input power has been restored.
- This event clears the "Power Supply Input Failure" Alarm.
| 2 | 6 | alarm | Power Supply output failure | equipment | System;PSU | major |
|
| - A Power Supply module has indicated a failure of output power.
- The SBC 1000/2000 System has lost Power Supply redundancy.
- Suggested action - Verify that the PS is functioning properly.
| 2 | 7 | alarm | Single Fan failure | equipment | System;Fan | major |
|
| - Check the System tab to find the Fan ID of the failed fan.
- Contact Ribbon Support with this information.
| 2 | 8 | alarm | Multiple Fan Failures | equipment | System;Fans | critical |
|
| - Check the System tab to find the Fan ID's of the failed fans.
- Contact Ribbon with this information.
| 2 | 9 | alarm | System Temperature Warm | equipment | System | minor |
| - The temperature sensors have indicated that the system is running warm (65°C threshold).
| 2 | 10 | event | System Temperature Warm Cleared | equipment | System |
| |
|
| - The temperature sensors have indicated that the system is NO LONGER running warm (55°C threshold).
- This event clears the "System Temperature Warm" Alarm.
| 2 | 11 | alarm | System Temperature Hot | equipment | System | critical |
| - The temperature sensors have indicated that system is running hot.
| 2 | 12 | event | System Temperature Hot Cleared | equipment | System |
| |
|
| - The temperature sensors have indicated that the system is NO LONGER running hot (65°C threshold).
- This event clears the "System Temperature Hot" Alarm.
|
LicensingID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
3 | 1 | alarm | Licenses expired. | general | System;Service | critical |
| - License of the node has expired, all the licensed features would fail to work.
- Contact Ribbon.
| 3 | 2 | alarm | License expires in 2 weeks. | general | System;Service | major |
| - License of the node will expire in 2 weeks.
| 3 | 3 | event | New License applied. | general | System;Service |
| |
|
| - New License is applied on the node.
| 3 | 4 | alarm | Failed to Apply License. | general | System;Service | critical |
|
| - Either an invalid key is used, or the license key applies to a different node, or the license key expiry is past the present date.
- Contact Ribbon Sales to obtain a new license.
| 3 | 5 | alarm |
Failed to acquire licenseLicense(s) for 'license type' has been exhausted, or is not licensed. | general | System;Service |
critical |
| - The alarm is generated when the required license is not available.
- Check the number of licensed SIP or TDM channels, the number of SIP registrations, SBA, Transcoding or AD.
- Suggested action - obtain license for missing functionality.
- NOTE: The alarm is throttled to at most every 5 minutes per feature.
| | 3 | 6 | alarm | Licensed DS1 ports exceed installed ports. | general | System;Service | critical |
|
| - This alarm is generated when the license key applied has more TDM ports licensed than are installed in the system. As a fix, obtain license with correct number of TDM ports.
| | 3 | 7 | alarm | Licensed BRI ports exceeds installed ports. | general | System;Service | minor |
|
| - The alarm is generated when the license key applied has more BRI ports licensed than are installed in the system. The number of BRI ports installed will get activated. As a fix, obtain a license with the correct number of BRI ports.
| | 3 | 8 | alarm | Licensed FXS ports exceeds installed ports. | general | System;Service | minor |
|
| - The alarm is generated when the license key applied has more FXS ports licensed than are installed in the system. The number of FXS ports installed will get activated. As a fix, obtain a license with the correct number of FXS ports.
| | 3 | 9 | alarm | Licensed FXO ports exceeds installed ports. | general | System;Service | minor |
|
| - The alarm is generated when the license key applied has more FXO ports licensed than are installed in the system. the number of FXO ports installed will get activated. As a fix, obtain a license with the correct number of FXO ports.
|
Microsoft Survivable Branch Appliance Support| 3 | 10 | alarm | Failed to get key for License generation | general | System;Service | critical |
| - Failed to get key for license generation.
| | 3 | 11 | alarm | Licensed SIP Signaling Sessions exceeds system capacity | general | System;Service | minor |
| - The alarm is generated when the license key applied has more SIP Signaling Sessions licensed than the system is capable of. Extra licenses will not be used. As a fix, obtain a license with correct number of SIP Signaling Sessions.
| | 3 | 12 | alarm | Licensed SIP Registrations exceeds system capability. | general | System;Service | minor |
| - The alarm is generated when the license key applied has more SIP Registrations licensed than the system is capable of. Extra licenses will not be used. As a fix, obtain a license with correct number of SIP Registrations.
| | 3 | 13 | alarm | Enhanced Media Sessions with Transcoding exceeds system capability. | general | System;Service | minor |
| | | 3 | 14 | alarm | Enhanced Media Sessions w/o Transcoding exceeds system capability. | general | System;Service | minor |
| - The alarm is generated when the license key applied has more Enhanced Media Sessions without Transcoding licensed than the system is capable of. Extra licenses will not be used. As a fix, obtain a license with correct number of Enhanced Media Sessions without Transcoding.
| | 3 | 16 | alarm | Licensed Video sessions exceed system capability. | general | System;Service | minor |
| - SIP Video Sessions of 'number' licenses exceeds the capability of the system of 'number' licenses. As a fix, obtain a license with correct number of SIP Video Sessions.
| | 3 | 17 | alarm | Licensed High Capacity (250+) sessions exceed system capacity | general | System;Service | minor |
| - SIP High Capacity (250+) Sessions of 'number' licenses exceeds the capability of the system of 'number' licenses. As a fix, obtain a license with correct number of SIP High Capacity Sessions.
| | 3 | 18 | alarm | SIP High Capacity (250+) License required. | general | System;Service | minor |
| - The SIP Signal Sessions of 'number' licenses exceeds the SIP High Capability (250+) Sessions of 'number' licenses. As a fix, obtain a license with correct number of SIP High Capacity Sessions.
| | 3 | 19 | alarm | Non-Azure VM License Rejected | general | System;Service | critical | | - Submitted license key does not include Azure enablement flag. Azure-related enablement flag must be included for an Azure-based SBC SWe Lite instance to accept and enable newly acquired features. Please consult product documentation for rectification.
| | 3 | 20 | event | Azure License Installed | general | System;Service |
|
| - An Azure-enabled license has been successfully installed.
| | 3 | 21 | alarm | Trial License Expired | general | System;Service | critical | | - The Trial License period has expired for the SBC Swe Lite. Please install the Production licenses to enable and accept features on the SWe Lite.
| | 3 | 22 | alarm | Obsolete Version 2 License Present | general | System;Service | critical | | - License Version 2 is unsupported. Please immediately contact Ribbon Support for a free feature equivalent License Version 3. Roll back to the previous partition until this license is available.
- Cleared by event 3.3.
|
Microsoft Survivable Branch Appliance SupportID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
5 | 1 | alarm | ASM Unreachable | communication | SBA Instance | critical |
| - ASM system can not be reached, system is down.
- Check whether the ASM is rebooting.
| 5 | 2 | event | Clear ASM Unreachable | communication | SBA Instance |
| |
|
| - Clears alarm 'ASM Unreachable'.
| 5 | 3 | alarm | ASM Failure Recovered | equipment | SBA Instance |
minor | warning |
| - ASM system was previously unreachable, but has come up.
- This alarm doesn't autoclear so the user can investigate the cause, but the system should be working correctly now.
| 5 | 4 | alarm | ASM Services Not Running | processing | SBA Instance | critical |
| - ASM services are not running, calls through the ASM cannot be placed.
| 5 | 5 | event | Clear ASM Services Not Running | processing | SBA Instance |
| |
|
| - Clears alarm 'ASM Services Not Running'.
| 5 | 6 | alarm | ASM Services Restarted | processing | SBA Instance |
minor | warning |
| - ASM Services was previously stopped, but has started. This alarm doesn't autoclear so the user can investigate the cause, but ASM Services should be working correctly now.
| 5 | 7 | alarm | ASM Service Restart Failed | processing | SBA Instance | critical |
|
| - The system attempted to restart a failed service on the ASM, service did not start successfully.
- User interaction is required.
| 5 | 8 | event | ASM System Started | processing | SBA Instance |
|
|
| - This event is set when the SBA communication system is first established, and usually indicates that the Application Solution Module (ASM) has finished booting.
- It should come up at system startup, it may come again if the ASM hardware is rebooted.
| 5 | 9 | event | ASM System Shutting down | processing | SBA Instance |
|
|
| - A planned or deliberate shut down is taking place on the Application Solution Module (ASM).
| 5 | 10 | alarm | Ethernet Link Down | equipment | SBA Instance;Port | major |
| - Ethernet port specified has lost link.
- Source Instance: Eth0/Eth1 via SBA Monitor.
| 5 | 11 | event | Ethernet Link Up | equipment | SBA Instance |
| |
|
| - Ethernet port specific has recovered link.
| 5 | 12 | alarm | ASM-SBC IP Subnet Mismatch | equipment | SBA Instance | critical |
| - The ASM and Ribbon SBC IP interfaces are in different subnets and cannot communicate.
| 5 | 13 | event | ASM-SBC IP Subnet Match | equipment | SBA Instance |
| |
|
| - The ASM and Ribbon SBC IP interfaces are in the same subnet and can now communicate.
| | 5 | 14 | alarm | ASM-QoE SQL database is unreachable | communication | SBA Instance | major | | - The QoE database is unreachable from ASM, make sure the Lync Server 2013 is deployed and Monitoring database is running.
| | 5 | 15 | event | Clear ASM-QoE SQL database is unreachable | equipment | SBA Instance |
| |
|
| - The QoE database is now reachable from ASM.
| | 5 | 16 | alarm | ASM-failed to store QoE information | equipment | SBA Instance |
critical | | major |
| - Failed to store the QoE information from ASM.
| | 5 | 17 | alarm | ASM-SBC CAC Update Failed | equipment | SBA Instance | major | | - The ASM hasn't been able to apply the CAC update.
| | 5 | 18 | event | ASM-SBC CAC Update Applied | equipment | SBA Instance |
| |
|
| - ASM-SBC CAC Update applied.
| | 5 | 19 | alarm | This copy of ASM Operating System is not genuine | equipment | SBA Instance | critical |
|
| - ASM Windows Server is not able to activate as genuine Microsoft product.
| | 5 | 20 | alarm | ASM drive NFS mount failure | equipment | SBA Instance | major | | | | 5 | 21 | event | Clear ASM drive NFS mount failure | equipment | SBA instance |
| |
|
| | | 5 | 22 | event | ASM Operating System Successfully Activated | equipment | SBA instance |
| |
|
| - ASM Windows Server is activated as genuine Microsoft product.
| 5 | 23 | alarm | ASM IP Address conflict | SBA | SBA Instance | critical |
| - The configured ASM IP was not applied due to conflict with other device(s) on the network.
| 5 | 24 | event | Clear ASM IP address conflict | SBA | SBA Instance |
|
|
| - ASM IP address conflict cleared.
| | 5 | 25 | alarm | ASM Ethernet Port Down | equipment | SBA instance | critical | | - ASM Etherent Port has been detected down.
| | 5 | 26 | event | Clear ASM Ethernet Port Down | equipment | SBA instance |
| |
|
| - ASM Ethernet Port has been detected down is cleared.
| | 5 | 27 | alarm | Active CCE Maintenance Mode | equipment | SBA instance | critical | | - Cloud Connector Edition entered in Maintenance mode.
| | 5 | 28 | event | Clear Active CCE Maintenance Mode | equipment | SBA instance |
|
|
| - Cloud Connector Edition exited maintenance mode.
| | 5 | 29 | alarm | CCE Windows Product Key is missing | equipment | SBA instance | major | | - Cloud Connector Edition Windows Product Key is missing.
| | 5 | 30 | event | Clear CCE Windows Product Key is missing or failed to activate
| equipment | SBC instance |
|
|
| - Cloud Connector Edition Windows Product Key has been found.
| | 5 | 31 | alarm | CCE Windows Product Failed to Activate | equipment | SBA instance | major | | - Cloud Connector Edition Windows Product Failed to Activate.
| | 5 | 32 | alarm | ASM and SBC Firmware Mismatch | equipment | SBA instance | major | | - ASM and SBC firmware version does not match.
| | 5 | 33 | event | Clear ASM and SBC Firmware mismatch | equipment | SBA instance |
| |
|
| - ASM and SBC firmware does not match is cleared.
| | 5 | 34 | alarm | Failed to increase the CCE mediation VM resource | equipment | SBA instance | major |
|
| - From the ASM Hyper-V manager, assign 9 vCPU to the CE Mediation Server VM
|
Call RoutingID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
7 | 1 | event | Configuration change occurred on Action Set | general | ActSetTble |
| |
|
| - There is an action set table number/name that should be printed with this event.
| 7 | 2 | event | Configuration change occurred on Normalization Table | general | NormTble |
| |
|
| - There is a normalization table number/name that should be printed with this event.
| 7 | 3 | event | Configuration change occurred on Route Table | general | RtTble |
|
|
| - There is a route table number/name that should be printed with this event.
| 7 | 4 | event | Configuration change occurred on Transformation Tables | general | TransTble |
| |
|
| - There is a transformation table number/name that should be printed with this event.
| 7 | 5 | alarm | Route temporarily disabled | communication | RtTble | warning |
| - This alarm is set if a link is down or some other event has occured to take a route entry out of service.
| 7 | 6 | event | Route enabled | communication | RtTble |
|
|
| | 7 | 7 | alarm | A Call exceeded the limit for number of destinations | communication | CallDest | warning |
|
| - A call with destination of X tried to be forked more than the limit allows (currently 8).
| 7 | 8 | alarm | Call forking used with no forking license | communication | CallDest | warning |
|
| - A call with a destination of X was forked with no forking license available.
| 7 | 9 | alarm | Invocation of InvokeActionSet exceeded the maximum nesting limit | communication | CallDest | warning |
|
| - A call with with destination of X tried to execute InvokeActionSet more the the limit allows (currently 10).
| 7 | 10 | event | Configuration change occurred on Callback Tables | general | CallbackTble |
| |
|
| - There is a PSAP Callback table number/name that should be printed with this event.
|
Common Call ControlID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
8 | 1 | event | Channel is in service | communication | Card;Port;Channel |
| |
|
| - Channel is up and is in service.
- This clears the 'Channel out of service' alarm.
| 8 | 2 | alarm | Channel is out of service | communication | Card;Port;Channel | minor |
| - Channel Out Of Service Alarm.
- This alarm is automatically cleared when Channel is in service.
| 8 | 3 | alarm | Emergency Call Attempted | communication | Number;Extension;IPAddress | minor |
| - Emergency Call is Attempted from Calling Number, Calling Extension, Caller IP address.
| 8 | 4 | event | Emergency Call Attempted | communication | Number;Extension;IPAddress |
| |
|
| - Emergency Call Alarm will be cleared after expiry time in emergency status table.
| | 8 | 5 | alarm | QoE report not sent due to RTCP Media List | communication | SG | minor |
|
| - Generated when the Media List does not have RTCP-XR configuration enabled.
| | 8 | 6 | event | Call Transfer failed due to call not being in RTP mode | communication | Card;Port;Channel |
|
|
| - The call is not in RTP mode hence the call transfer could not be honored.
| | 8 | 7 | event | Call Attempt failed due to Media Mode mismatch | communication | Card;Port;Channel |
| |
|
| - The call failed due to Media Mode mismatch across SG and Call Route configuration.
| | 8 | 8 | alarm | All calls have been drained on this Signaling Group | communication | SG | Warning |
|
|
| | 8 | 9 | alarm | Non-Emergency Call Preempted due to an Emergency Call Attempt | communication | Card;Port;Channel | minor |
|
| - Non-Emergency Call Preempted due to an Emergency Call Attempt.
| | 8 | 12 | alarm | No AMR Wideband license | communication | System | minor |
|
| - AMR Wideband call attempted but not licensed.
| | 8 | 13 | alarm | Maximum Call Duration Exceeded | communication | CallID | minorc |
| - Maximum call duration exceeded for call and call has been disconnected
|
AMR Wideband call attempted but not licensedSIPID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
9 | 1 | alarm | SIP Server not responding | communication | SIPCluster;ServID;Protocol;IPAddress;Port | 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 | Signaling Group taken out of service | communication | SG | critical |
| - All servers in SG have failed.
- This alarm will be cleared by 'SIP Signaling group enabled' event.
| 9 | 3 | event | Signaling Group disabled | communication | SG |
| |
|
| - Configuration action has changed this Signaling Group from Enabled to Disabled.
| 9 | 4 | alarm | SIP-TLS Server Handshake Failure | security | TLSProfile;IPAddress | minor |
|
| - TLS server handshake failed with alert code. Action: Refer to Error Alerts in RFC 5246 for the problem.
| 9 | 5 | alarm | SIP-TLS Handshake Inactivity Timeout Failure | security | TLSProfile;IPAddress | minor |
|
|
| 9 | 6 | alarm | Configured port number mismatch | processing | SG;IPAddress;Port | 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 | SIP Server became responsive | communication | SIPCluster;ServID;Protocol;IPAddress;Port |
| |
|
| | 9 | 8 | alarm | SIP cluster went down | communication | SIPCluster | major |
| - SIP cluster went down.
- This is due to all the servers in the clusters are not responsive.
- This alarm will be cleared by the event 'Sip cluster enabled'.
| 9 | 9 | event | SIP Cluster enabled | communication | SIPCluster |
| |
|
| | 9 | 10 | event | SIP Signaling group enabled | communication | SG |
| |
|
| - SIP Signaling group enabled.
| 9 | 11 | alarm | SIP Signaling group: DNS failure | communication | SG | major |
| - Failed to resolve the FQDN entries in the SIP Signaling Group. Suggested action - confirm the FQDNs, and confirm DNS access.
| 9 | 12 | event | SIP Signaling Group; FQDN resolved | communication | SG |
| |
|
| - Successfully resolved the FQDN of the SIP Signaling group.
| 9 | 13 | alarm | SIP Server; DNS failure. | communication | SIPCluster;ServID | major |
| - Failed to resolve the SIP server FQDN entries in the SIP Server table.
- Suggested action - check the FQDN syntax.
| 9 | 14 | event | SIP Server; FQDN resolved | communication | SIPCluster;ServID |
| |
|
| - SIP Server config FQDN resolved.
| 9 | 15 | alarm | SIP call session DNS failure | communication | SG | major |
|
| - Failed to resolve an FQDN with DNS server during a SIP call session.
| 9 | 16 | alarm | Acquiring license for Register failed | communication | SG | major |
|
| - Failed to acquire license from License Manager.
| | 9 | 17 | alarm | Session leak or some other resource leak | communication | SG | major |
|
| - SIP performs self-check for leaks. Please enable logging for sip and issue "show resources" command.
| | 9 | 18 | alarm | Failed to bind to network interface | communication | SG | minor |
|
| - Failed to bind to network interface due to dynamic IP address not available.
| | 9 | 19 | event | Successfully bound to network interface | communication | SG |
| |
|
| - Successfully bound to network interface. DHCP lease renewed.
| | 9 | 20 | alarm | SIP Register Server not responding | communication | SIPCluster;ServID;Protocol;IPAddress;Port | major |
| - SIP Register server has failed to respond. This alarm will be cleared by the event "SIP Regular server became responsive".
| | 9 | 21 | event | SIP Register Server became unresponsive | communication | SIPCluster;ServID;Protocol;IPAddress;Port |
| |
|
| - SIP Register server came up.
| 9 | 22 | alarm | Registration not valid; received stale=false | communication | SIPCluster;ServID;Protocol;IPAddress;Port | major |
| - Server has sent stale=false. Contact is not Registered.
| 9 | 23 | event | Config change for SIP endpoint that received stale=false | communication | SG;AorName |
| |
|
| - Endpoint which had Stale is False has config change.
| 9 | 24 | alarm | QoE Notify Message was not successful | communication | SIPCluster;ServID;Protocol;IPAddress;Port | minor |
| | 9 | 25 | event | QoE Notify Message Response was successful | communication | SG |
|
|
| - QOE Notify Message received a successful response.
| 9 | 26 | alarm | System overload detected | communication | System;Service | minor |
| - SIP application session processing is overloaded.
| 9 | 27 | event | System overload cleared | communication | System;Service |
| |
|
| - SIP application session processing resumes to normal operation, overload cleared.
| 9 | 28 | alarm | Maximum Number of SIP Sessions Reached | communication | SG | 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 | Maximum Number of SIP Sessions Alarm Cleared | communication | SG |
| |
|
| - SIP sessions per signaling group is under the maximum limit.
| 9 | 30 | alarm | Error resolving SRV record | communication | SIPCluster;ServID | major |
| - Failed to execute SRV record query. Suggested action - confirm that DNS server network is reachable, check SRV and DNS server configuration.
| 9 | 31 | event | SRV record resolved | communication | SIPCluster;ServID | none |
|
| - DNS server returned valid SRV record(s).
| | 9 | 32 | alarm | SIP-TLS Handshake Negotiation Start Failure | security | TLSProfile;IPAddress | critical | |
Handshake - 'server' handshake failed
|
due - to start with invalid certificate; 'connection ID', 'port ID'. Action:
|
Import a valid - confirm that both signed Ribbon SBC Edge Certificate
|
on local and/or remote gateway- and Trusted CA Certificate exist.
| | 9 | 33 | event | SIP-TLS Handshake Negotiation Start Successful | security | TLSProfile;IPAddress | 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 | Maximum supported SIP SGs reached | General | System;Service | warning | | - SIP signaling group count reached maximum supported limit.
| | 9 | 35 | event | Maximum supported SIP SGs cleared | General | System;Service | none |
|
| - SIP signaling group count is under the maximum supported
| | 9 | 36 | alarm | Maximum non-SIP call sessions reached | General | System; Service | warning | | - Number of SIP non-call sessions is over the system capacity
| | 9 | 37 | event | Maximum non-SIP call Sessions cleared | General | System:Service | none |
|
| - Number of SIP non-call sessions is under the system capacity
| | 9 | 38 | alarm | Maximum SIP call sessions reached | General | System;Service | warning | | - Number of SIP call sessions is over the system capacity
| | 9 | 39 | event | Maximum SIP call sessions cleared | General | System.Service | none |
|
| - Number of SIP call sessions is under the system capacity
| | 9 | 40 | Alarm | Broadsoft SIP call re-routed | General | SG | warning | | - Broadsoft SIP call re-routed
| | 9 | 41 | event | Broadsoft SIP Call Re-routed cleared | General | SG | none |
|
| - Number of SIP Call Sessions is under the system capacity.
| | 9 | 42 | alarm | SIP SG Listen Protocol and SIP Server Host Protocol mismatch | Processing | SIPCluster;ServerID | minor |
|
| - Verify that the listen ports and protocols for the SG match those in the server table.
| | 9 | 43 | alarm | Configuration Error: SIP SG and Server Protocol Mismatch | Processing | SIPCluster;ServerID | major |
|
| - Verify that the listen ports and protocols for the SG match those in the server table.
| | 9 | 44 | alarm | SIP-TLS Client Handshake Failure | Security | TLSProfile;IPAddress | minor | | - TLS client handshake failed with alert code. Action: Refer to Error Alerts in RFC 5246 for the problem.
| | 9 | 45 | event | SIP-TLS Handshake Inactivity Timeout Cleared | Security | TLSProfile;IPAddress |
| |
|
| - Handshake response was received within specified timeout. This event clears the 'SIP-TLS Handshake Inactivity Timeout Failure' alarm.
| | 9 | 46 | event | SIP-TLS Server Handshake Failure Cleared | Security | TLSProfile; |
IPAddress | | IPAddress |
|
| - Handshake failure error alert condition was cleared. This event clears the 'SIP-TLS Server Handshake Failure' alarm.
| | 9 | 47 | event | SIP-TLS Client Handshake Failure Cleared | Security | TLSProfile;IPAddress |
| |
|
| - Handshake failure error alert condition was cleared. This event clears the 'SIP-TLS Client Handshake Failure' alarm.
| | 9 | 48 | alarm | Skype/Lync Presence Response Failure | communication | SIPCluster; ServId | minor | | A Presence Publish Request has been sent to the configured Skype/Lync Presence Front End and either: - no response has been received, or
- the response failed.
Only one alarm is raised at any time. The alarm is cleared when the SIP presence entity receives a successful response to a Publish message. | | 9 | 49 | alarm | Skype/Lync Presence Server Response Failure Cleared | communication | SIPCluster; ServId | minor |  | A presence server that previously was unreachable has successfully sent a message that the SBC has received. | | 9 | 50 | alarm | SIP Request from Untrusted IP | Security | IPAddress | minor |
|
| - An INVITE message was received from a host without a matching Federated IP.
| | 9 | 51 | alarm | (no longer used) |
| | | |
|
|
|
|
| | 9 | 52 | alarm | Resync message received on SG, not selected for Auto Configuration task. | Processing | SG | major |
|
| - Check Auto configuration Task settings and verify that the Signaling Group selected is correct.
| | 9 | 53 | alarm | Maximum Number of Skype/Lync Presence Sessions Reached | communication | SG | 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. This alarm is raised if: - The connection to Nectar UCD server is broken
- VQ Notify is rejected by Nectar UCD server.
- The Nectar UCD's FQDN is not resolved by DNS server.
The active alarm gets cleared when NOTIFY is accepted by Nectar UCD successfully. | | 9 | 54 | event | Maximum Number of S4B Presence Publish Sessions Alarms Cleared | communication | SG |
|
| | - SIP Publish sessions for S4B Presence is under the maximum limit.
| | 9 | 55 | alarm | Enable Monitoring on Skype Presence Server for better reliability | communication | SIPCluster | minor | | - Enable Monitoring on Skype Presence Server for better reliability.
| | 9 | 56 | event | Monitoring on Skype Presence Server has been enabled | communication | SIPCluster |
| |
|
| - Monitoring the Skype Presence Server has been enabled.
| | 9 | 57 | alarm | The SIP voice Quality Server Connection is Broken | communication | Protocol;IPAddress;Port | major | | - Suggested Action: Verifying the IP, Port, Protocol, and Certificate (if TLS) are Correct.
| | 9 | 58 | event | The SIP Voice Quality Server Connection is Resumed | communication | Protocol;IPAddress;Port |
| |
|
| - The SIP Voice Quality Server Connection is Resumed
| | 9 | 59 | alarm | The Voice Quality Nofiy Rejected by the SIP Voice Quality Server | communication | IPAddress;Port | warning | | - Suggested Action: Examining the Notify Response Code and the Reason Header (if included) to understand why it was rejected.
| | 9 | 60 | alarm | The Voice Quality Notify Accept by the SIP Voice Quality Server | communication | IPAddress;Port |
| |
|
| - The Voice Quality Notify has been Accept by The SIP Voice Quality Server.
| | 9 | 61 | alarm | Failed to Resolve the FQDN of the SIP Voice Quality Server | communication | IPAddress | warning |
|
| - Failed to Resolve FQDN of the SIP Voice Quality Server. Suggested action - confirm the DNS access and FQDN.
| | 9 | 62 | event | The SIP Boice Quality Server FQDN has been Resolved | communication | IPAddress |
| |
|
| - The SIP Boice Quality Server FQDN has been Resolved
| | 9 | 63 | alarm | Configured Registration Limit Reached | communication | SIPRegistrarTable | 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 | Configured Registration Limit Cleared | communication | SIPRegistrarTable |
| |
|
| - Configured Registration Limit Cleared
|
ISDNID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
10 | 1 | alarm | D-Channel down | communication | Card;Port | critical |
| - The data link layer of the port has come down.
| 10 | 2 | event | D-Channel up | communication | Card;Port |
| |
|
| - The data link layer of the port has come back up.
| 10 | 3 | alarm | Call released due to channel restart by far end | communication | Card;Port;Channel | minor |
|
| - Call released as the ISDN channel has been restarted by far end.
|
Telco Interface ProcessID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
11 | 1 | alarm | Port disabled by operator | communication | Card;Port |
majorwarning |
| - The physical layer of the port has been brought down by the operator.
| 11 | 2 | event | Port enabled by operator | communication | Card;Port |
| |
|
| - The physical layer of the port has been brought back up by the operator.
| 11 | 3 | alarm | DS1 Loopback Enter | communication | Card;Port | critical |
| - The DS1 has been put into a loopback state by the operator.
| 11 | 4 | event | DS1 Loopback Exit | communication | Card;Port |
| |
|
| - The DS1 has been taken out of the loopback state by the operator.
| 11 | 5 | alarm | Red Alarm - Loss of Signal | communication | Card;Port | critical |
| - The physical layer has detected a Red (LOS) alarm.
| 11 | 6 | event | Red Alarm - Loss of Signal cleared | communication | Card;Port |
| |
|
| - The physical layer has detected a Red (LOS) alarm clearing.
| 11 | 7 | alarm | Red Alarm - Loss of Frame | communication | Card;Port | critical |
| - The physical layer has detected a Red (LOF) alarm.
| 11 | 8 | event | Red Alarm - Loss of Frame cleared | communication | Card;Port |
| |
|
| - The physical layer has detected a Red (LOF) alarm clearing.
| 11 | 9 | alarm | Blue Alarm | communication | Card;Port | critical |
| - The physical layer has detected a blue alarm.
| 11 | 10 | event | Blue Alarm Cleared | communication | Card;Port |
| |
|
| - The physical layer has detected an alarm clearing.
| 11 | 11 | alarm | Yellow Alarm | communication | Card;Port | critical |
| - The physical layer has detected an yellow alarm.
- This can be originated because of an alarm assert issued by operator or a detection of alarm condition from far end.
| 11 | 12 | event | Yellow Alarm Cleared | communication | Card;Port |
|
|
| - The physical layer has detected an yellow alarm clear.
| 11 | 13 | alarm | Port disabled as port not found on DS1 | communication | Card;Port | critical |
|
| - This alarm is generated to indicate that a port which was present in the UI is now marked as disabled because the corresponding port was not present on the DS1 physical hardware.
| 11 | 14 | alarm | Clock recovery switched to port configured as secondary | communication | System | critical |
| - This alarm is generated to indicate that the primary port from which clock was being recovered has gone down and so clock recovery is now being performed on the secondary port.
| 11 | 15 | event | Clock recovery switchover to secondary port cleared | communication | System |
| |
|
| - This event is generated to indicate that the primary port from which clock was being recovered is back in operation and so clock recovery is now being performed on the primary port.
| 11 | 16 | alarm | Clock recovery switched to freerun clock | communication | System | critical |
| - This alarm is generated to indicate that the primary and secondary ports from which clock was being recovered have gone down and so clock recovery is now being performed internally from oscillator holdover clock.
| 11 | 17 | event | Clock recovery switchover to freerun clock cleared | communication | System |
| |
|
| - This event is generated to indicate that either the primary or secondary port from which clock was being recovered is back in-service, so clock will be recovered from the in-service port instead of the oscillator holdover clock.
| 11 | 18 | alarm | Line card not detected | communication | Card | warning |
| | 11 | 19 | event | Line card detected | communication | Card |
| |
|
| | 11 | 20 | alarm | Port disabled for relay passthrough state activation | communication | Card;Port | warning |
| - Port disabled because the corresponding port is activated for relay passthrough state.
| 11 | 21 | event | Port enabled for relay online state activation | communication | Card;Port |
| |
|
| - Port enabled because the corresponding port is re-activated for relay online state.
| 11 | 22 | alarm | Layer 1 down | communication | Card;Port | critical |
| - The physical layer has detected layer 1 down due to state conditions that results in non-operational state of the BRI port.
- The physical layer state as per I.
- 430 specification can be found in the UI Port View for troubleshooting.
| 11 | 23 | event | Layer 1 up | communication | Card;Port |
| |
|
| - The physical layer 1 down alarm is cleared with operational state of the BRI port.
| 11 | 24 | alarm | Port disabled as port not found on analog card | communication | Card;Port | critical |
|
| - Port is now marked as disabled because the corresponding port was not present on the analog physical hardware.
| 11 | 25 | alarm | Ports disabled for relay pass through state change on analog relay card pairs | communication | System;Card;Card | warning |
| - Ports are now marked as disabled for activated relay passthrough state on analog FXS/FXO card pair.
| 11 | 26 | event | Ports enabled for relay online state change on analog relay card pairs | communication | System;Card;Card |
|
|
| - Ports are now marked as enabled for activated relay passthrough state on analog FXS/FXO card pair.
| 11 | 27 | alarm | Port status down detected | communication | Card;Port | warning |
| - Line down condition detected.
| 11 | 28 | event | Port status up | communication | Card;Port |
| |
|
| - Line down condition cleared.
| 11 | 29 | alarm | Port disabled as port not found on BRI | communication | Card;Port | critical |
|
| - This alarm is generated to indicate that a port which was present in the UI is now marked as disabled because the corresponding port was not present on the BRI physical hardware.
| 11 | 30 | alarm | System not operational | communication | System | critical |
|
| - System not operational because DSP cannot be initialized.
- Contact Ribbon with the information in this alarm.
| | 11 | 31 | alarm | DS1 sync failure | communication | Card;Port | critical | | DS1 sync failure could be due to mismatching line configuration. Suggested Action: Disable "Admin State" of unused ports to avoid performance impact. | | 11 | 32 | event | DS1 sync failure cleared | communication | Card;Port |
| |
|
| DS1 sync failure cleared. |
ID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
12 | 1 | alarm | DSP not coming up | equipment | DSP | critical |
| - This alarm will be generated if a DSP cannot be initialized.
- If the DSP does not come up, contact Ribbon with the information in this alarm.
| 12 | 2 | alarm | DSP reset | equipment | DSP | major |
| - This alarm will be generated if a DSP encounters a fatal error condition and has to be reinitialized.
| 12 | 3 | event | DSP Card is UP | equipment | Card |
| |
|
| - This event will clear the 'DSP not coming up' and 'DSP reset' alarms.
| 12 | 4 | event | DSP Event Failure | processing | Card;Port;Channel |
| |
|
| - This event will be generated if a DSP channel encounters a fatal error condition and has to be closed.
| | 12 | 5 | alarm | RTP/RTCP Port Range Invalid | equipment | System | critical | | - This alarm is generated if a RTP/RTCP port is found to be invalid. The conflicting port is skipped, however, this condition should be resolved by reconfiguring the RTP/RTCP Port Range under Media System Configuration.
| | 12 | 6 | event | RTP/RTCP Port Range Invalid Cleared | equipment | System |
| |
|
| - This event will clear the "RTP/RTCP Port Range Invalid" alarm.
| | 12 | 7 | alarm | MSC Media Stream Mode Mismatch | general | System;Service | minor |
|
| - This alarm is generated when there is a mismatch in media stream mode of the two call legs. Suggested action: match "Audio/Fax Stream Mode" settings and clear alarm.
| | 12 | 8 | alarm | Music-On-Hold failed due to improperly configured source. | communication | System;Service | minor |
|
| - Music-On-Hold enabled; source is not properly configured. If source is set to file: upload a file, disable music on hold or switch source to an FXS port.
| | 12 | 9 | alarm | Failed to allocate RTP Ports | communication | System;Service | major |
|
| - This alarm is generated if we exceed the configured number of RTP/RTCP port pairs. This condition should be resolved by increasing the "Number of Port Pairs" in Media System Configuration.
|
12| 12 | 10 | alarm | Virt DSP event failure | communication | System;Service | minor |
| - Virt DSP Command Failure: Conf='conf' Type='type' Error='error'
| | 12 | 11 | alarm | MSC-DTLS Server Handshake Failure | Security | DTLSProfile;IPAddress |
Minor| minor | | - DTLS server handshake failed with alert code. Action: Refer to Error Alerts in RFC 5246 for the problem.
| | 12 |
11Event| event | MSC-DTLS Server Handshake Failure Cleared | Security | DTLSProfile;IPAddress |
| |
|
| - Handshake failure error alert condition was cleared. This event clears the 'MSC-DTLS Server Handshake Failure alarm.
| | 12 |
12| 13 | Alarm | MSC-DTLS Handshake Inactivity Timeout Failure | Security | DTLSProfile;IPAddress |
Minor | minor | | - DTLS handshake failed due to no response from peer within specified timeout. Action: Increase the Handshake Inactivity Timeout in DTLS Profile.
| | 12 |
13Event| event | MSC-DTLS Handshake Inactivity Timeout Cleared | Security | DTLSProfile;IPAddress |
| |
|
| - Handshake response was received within specified timeout. This event clears the 'MSC-DTLS Handshake Inactivity Timeout Failure' alarm.
| | 12 |
14Alarm| alarm | MSC-DTLS Handshake Negotiation Start Failure | Security | DTLSProfile;IPAddress |
Major| critical | |
DTLS Handshake failed due - 'server' handshake failed to start with invalid certificate; 'connection ID', 'port ID'. Action:
|
Import a valid signed Sonus SBC Certificate on local and/or remote gateway- confirm that both signed Ribbon SBC Edge Certificate and Trusted CA Certificate exist.
| | 12 |
15Event| event | MSC-DTLS Handshake Negotiation Start Successful | Security | DTLSProfile;IPAddress |
| |
|
| - DTLS Handshake response was started with valid certificate on local and remote gateway. This event clears the 'MSC-DTLS Handshake Negotiation Start Failure' alarm.
| | 12 |
16Alarm| alarm | MSC-DTLS Client Handshake Failure | Security | DTLSProfile;IPAddress |
Minor| minor | | - DTLS client handshake failed with alert code. Action: Refer to Error Alerts in RFC 5246 for the problem.
| | 12 |
17Event| event | MSC-DTLS Client Handshake Failure Cleared | Security | DTLSProfile;IPAddress |
| |
|
| - Handshake failure error alert condition was cleared. This event clears the 'MSC-DTLS Client Handshake Failure' alarm.
|
Certificate Security ManagerID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
13 | 1 | alarm | TLS Own Server Certificate will Expire | security | CertificateCommonName | major |
| - The Server certificate will expire in a window time.
- Suggested Action: Generate, Export CSR and Import a new signed certificate.
| 13 | 2 | alarm | TLS Own Server Certificate has Expired | security | CertificateCommonName | critical |
| - The Server certificate has expired.
- Suggested Action.
- Generate, Export CSR and Import a new signed certificate.
| | 13 | 3 | alarm | TLS Own Server Certificate is missing | secrurity | CertificateCommonName | critical | | - This Server certificate is found to be missing or has failed validations. Suggestion Action. Generate, Export CSR and Import a new signed certificate.
| 13 | 4 | alarm | TLS Self Sign Certificate Generation Failed | security | CertificateCommonName | critical |
|
| - Failed to create a default self signed certificate on the system.
| 13 | 5 | event | New and Valid TLS Own Server Certificate Detected | security | CertificateCommonName |
| |
|
| - The Server certificate was uploaded, validated, and good to use in successfully establishing a TLS connection.
| 13 | 6 | alarm | TLS Trusted Certificate Authority will Expire | security | CertificateCommonName | major |
| - The Trusted CA Certificate will expire in a window time. Suggested Action: Import a new trusted CA certificate.
| 13 | 7 | alarm | TLS Trusted Certificate Authority has Expired | security | CertificateCommonName | critical |
| - The Trusted CA Certificate has expired. Import a new trusted CA certificate.
| 13 | 8 | event | TLS Trusted Certificate Authority was Deleted | security | CertificateCommonName |
| |
|
| - The Trusted Certificate Authority is successfully deleted due to the expired or expiring soon validity status.
| | 13 | 9 | alarm | TLS Own Server Certificate Expiry Notice | security | CertificateCommonName | minor | | - The Server certificate will expire in a window time. Suggestion Action: Generate, Export CSR and Import a new signed certificate.
| | 13 | 10 | alarm | TLS Trusted Certificate Authority Expiry Notice | security | CertificateCommonName | minor | | - The Trusted CA certificate will expire in a window time. Suggestion Action: Import a new trusted CA certificate.
|
BMPID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
14 | 1 | alarm | Invalid Session for attempted realtime connection | security | IPAddress |
| |
|
| - Invalid Session for attempted realtime connection.
| 14 | 2 | alarm | BMP-TLS Handshake Alert Failure | security | IPAddress | minor |
|
| - This alarm will be generated if TLS Connection failed with an Alert.
- The connection associated with a TLS Connection ID is aborted.
| 14 | 3 | alarm | BMP-TLS Handshake Inactivity Timeout Failure | security | IPAddress | minor |
|
| - This alarm will be generated if there was long period of inactivity during exchange of handshake messages for an associated TLS Connection ID.
|
Network ServicesID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
15 | 1 | alarm | Interface oper down | communication | Port | major |
| - Occurs when an Ethernet port (of ports 1, 2, 3 and 4) is operationally down (e.g. cable unplugged, mismatched speed/duplexity settings) and if admin-status is ADMIN_UP.
- The alarm is automatically cleared when the interface returns to working condition or when the admin-status is configured to be ADMIN-DOWN.
- Is generated only on SBC 2000 platform.
- This alarm is not generated on the SBC 1000 platform (See ID: 15, Sub-ID: 7 in this table).
- The operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on SBC 1000/2000 and on the device connected to the other end of the Ethernet cable.
- If the alarm is reported on an unused port, the admin-status of the unused port should be configured as "ADMIN-DOWN".
| 15 | 2 | event | Interface oper up | communication | Port |
|
|
| - Is generated when an Ethernet port (of ports 1, 2, 3 and 4) becomes operationally up.
- This event automatically clears the "Interface oper down" alarm.
| 15 | 3 | event | Interface admin up | communication | LogicalInterface |
| |
|
| - Is generated when the admin-status of the Port or Logical Interface is configured to be ADMIN-UP.
- Is applicable to SBC 2000 platform only.
| 15 | 4 | event | Interface admin down | communication | LogicalInterface |
| |
|
| - Is generated when the admin-status of the Port or Logical Interface is configured to be ADMIN-DOWN.
- Is applicable to SBC 2000 platform only.
| 15 | 5 | event | Admin Port oper down | communication | Port |
| |
|
| - Is generated when the Admin Port is operationally down (e.g. cable unplugged, mismatched duplex/speed settings).
- Is applicable to SBC 2000 platform only.
- The operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on SBC 1000/2000 and on the device connected to the other end of the Ethernet cable.
- It is very common and typical for SBC 2000 to leave the ADMIN-PORT unconnected and hence this condition is reported as an event and not an alarm.
| 15 | 6 | event | Admin Port oper up | communication | Port |
| |
|
| - Is generated with the port becomes operational after being in an *Admin port oper down* state.
- Is applicable to SBC 2000 platform only.
| 15 | 7 | event | Port oper down | communication | Port |
| |
|
| - Occurs when an Ethernet port (of ports 1 and 2) is operationally down (e.g. cable unplugged, mismatched speed/duplexity settings).
- Is generated only on the SBC 1000 platform.
- The same conditions are reported as alarm (ID: 15, Sub-ID: 1) on the SBC 2000 platform.
- When this event occurs (noticed as a trap), operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on SBC 1000/2000 and on the device connected to the other end of the Ethernet cable.
| 15 | 8 | event | RIP license not enabled | communication | System |
| |
|
| - RIP feature license is not enabled.
| 15 | 9 | event | OSPF license not enabled | communication | System |
| |
|
| - OSPF feature license is not enabled.
| 15 | 10 | alarm | Link Monitor Peer down | communication | IPAddress | major |
| - Generated when a Gateway or host is declared down.
| 15 | 11 | event | Link Monitor Peer ready | communication | IPAddress | event |
| - Is generated when a gateway or host is ceclared to be ready for service. It clears the Peer Down alarm.
| 15 | 12 | event | Tunnel connection disabled by operator | communication |
NetworkName | NetworkName |
|
| - Tunnel connection is placed Out of Service by operator.
| 15 | 13 | event | Tunnel connection enabled by operator | communication | NetworkName |
| |
|
| - Tunnel connection is placed Back in Service by operator.
| 15 | 14 | alarm | Tunnel Link Lost | communication | NetworkName | critical |
| - Tunnel lost communication with the peer. This alarm will be cleared by the "Tunnel link restored" event.
| 15 | 15 | event | Tunnel Link Restored | communication | NetworkName |
| |
|
| - Tunnel is successfully re-established with the peer.
| 15 | 16 | event | IPsec license not enabled | communication | System |
| |
|
| - IPsec license is not enabled.
| 15 | 17 | alarm | Negotiated Duplexity Half | communication | Port | warning |
| - Port negotiated duplexity is half. This degrades the performance.
| 15 | 18 | event | Negotiated Duplexity Full | communication | Port |
| |
|
| - Port negotiation duplexity is back to full.
| 15 | 19 | alarm | Preferred Link down | communication | IP address | critical |
| - Is generated when the preferred Link is down.
| 15 | 20 | event | Preferred Link Ready | communication | IP address | event |
|
| - Is generated when the preferred link is ready for service. This clears the Preferred Link down alarm.
| 15 | 21 | alarm | Tunnel Notification failure | communication | NetworkName | critical |
|
| - Is generated when Tunnel negotiation failed.
| 15 | 22 | event | Tunnel local subnet(s) are non-negotiable | communication | NetworkName | event |
|
| - Is generated when one or more local subnet(s) failed negotiation as a result of peer config mismatch.
| 15 | 23 | event | Tunnel remote subnet(s) are non-negotiable | communication | NetworkName | event |
|
| - Is generated when one or more remote subnet(s) failed negotiation as a result of peer config mismatch.
| | 15 | 24 | event | Port State Learning | communication | MSTPInstance;Port | event |
|
| - Is generated when a Port State is Learning in a Multiple Spanning Tree Instance.
| | 15 | 25 | event | Port State Forwarding | communication | MSTPInstance;Port | event |
|
| - Is generated when a Port State is Forwarding in a Mulitple Spanning Tree Instance.
| | 15 | 26 | event | Port State Discarding | communication | MSTPinstance;Port | event |
|
| - Is generated when a Port State is Discarding in a Multiple Spanning Tree Instance.
| | 15 | 27 | alarm | Packet Capture Started | general | System | warning |
|
| - Packet capture has started.
| | 15 | 28 | event | Packet Capture Stopped | general | System |
| |
|
| - Packet capture has stopped due to 'reason'.
| | 15 | 29 | alarm | Duplicate IPv6 address detected | communication | Interface;IPAddress | critical |
|
| - Is generated when duplicate address detection fails for a configured IPv6 address.
| | 15 | 30 | event | IP address configured | communication | Interface;IPaddress |
| |
|
| - Is generated when an IP address is configured on the node.
| | 15 | 31 | event | IP address removed | communication | Interface;IPaddress |
|
|
| - Is generated when an IP address is removed from the node.
| | 15 | 32 | alarm | Link failover detected | communication | Port | minor |
|
| - Link failover detected, the indicated Ethernet port became active.
| | 15 | 33 | alarm | MAC addresses have changed | general | System | major |
| - Some MAC addresses have changed since the last time the system was up. It is recommended to log into console as 'netconfig' user and remap the interfaces as desired.
| | 15 | 34 | alarm | Domain Name Empty | communication | System | major |
|
| - Domain Name for Split DNS should not be empty.
|
System Health MonitorID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
16 | 1 | alarm | Application Service restarted | processing | Service | major |
|
| - A SBC 1000/2000 Application service was restarted.
| 16 | 2 | alarm | Active partition switched | processing | Partition | 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 | Failed to mount partition | processing | Partition | major |
|
| - While booting, one of the partition could not be mounted.
- Likely a eUSB corruption.
- Contact Ribbon with the information in this alarm.
| 16 | 4 | alarm | Failed to set active partition | processing | Partition | major |
|
| - Failed to set active partition.
- Contact Ribbon with the information in this alarm.
| 16 | 5 | alarm | Attempt to repair boot parameter mismatch failed. | processing | Partition | major |
|
| - Attempt to auto repair boot parmeters failed.
- Contact Ribbon with the information in this alarm.
| 16 | 6 | alarm | Failed to mount partition | processing | Partition | major |
|
| - Boot parameter mismatch was detected.
- Attempting to auto repair.
| 16 | 7 | alarm | Failed Power-on memory self test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 8 | alarm | Failed Power-on Core Switch test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 9 | alarm | Failed Power-on Secondary Switch test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 10 | alarm | Failed Power-on external Quad PHY test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 11 | alarm | Failed Power-on external Single PHY test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 12 | alarm | Failed Power-on CPU PHY test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 13 | alarm | Failed Power-on TSI test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 14 | alarm | Failed Power-on internal 5-Port PHY test | equipment | Partition | critical |
|
| - Power-on self test failure.
| 16 | 15 | event | System Up After Planned Restart | equipment | System |
| |
|
| - System up after planned restart
| 16 | 16 | alarm | System Up After Unplanned Restart | equipment | System | major |
|
| - System up after unplanned restart.
| | 16 | 17 | alarm | Entered password recovery mode | security | System | major |
|
| - SBC has entered password recovery mode.
| | 16 | 18 | event | Exited password recovery mode | security | system |
| |
|
| - SBC has exited password recovery mode.
| | 16 | 19 | alarm | Failed to mount USB storage device | equipment | System;Service | major |
|
| - SBC discovered USB storage. SBC can mount flash drives formatted with FAT32 file system only.
| | 16 | 20 | event | USB storage device connected | equipment | System;Service |
| |
|
| - USB storge device is connected.
| | 16 | 21 |
Alarm| alarm | USB storage device disconnected | equipment | System;Service | warning |
|
| - USB storge device is disconnected. This alarm is cleared when USB drive is connected.
| | 16 | 22 |
Alarm| alarm | Critical application crash | almProcessing | Service | critical |
|
| - A Critical SBC application has crashed, system will be restarted. Contact Ribbon with the information in this alarm and all core files present on the system. Core files can be found in Diagnostics->Restart Report under the 'Core Files' tab.
| | 16 | 23 |
Alarm| alarm | Older firmware detected | processing | System;Service | critical |
|
| - A USB firmware update is available. To perform upgrade, please first load SW release v4.1.1.
| | 16 | 24 |
Event| event | Auto Configuration successful | equipment | System;Service |
| |
|
| - Auto Configuration successful after receiving SIP NOTIFY message.
| | 16 | 25 |
Alarm| alarm | Auto Configuration failed | processing | System;Service | major |
|
| - Failed to perform Auto Configuration after receiving SIP NOTIFY message.
| | 16 | 26 |
Alarm| alarm | Software Update in progress | processing | System;Service | major |
|
| - Current SIP NOTIFY message cannot be processed as software update is in progress.
| | 16 | 27 |
Alarm| alarm | Node Reboot | equipment | Service | minor |
|
| - Node Reboot requested by user "Username" from "IP Address
|
" | | 16 | 28 | alarm | Factory Default | equipment | Service | major |
| - Full factory default requested by user "Username" from "IP Address".
| | 16 | 29 | alarm | Invalid System Memory | equipment | System;Service | major |
| - Unexpected memory size for virtual CPU detected. Please consult documentation for memory requirement.
| | 16 |
28Alarm| alarm | Reset Button Factory Default | equipment | Service | major |
|
| - Full factory default requested
|
by user "Username" from "IP Address"- via hardware reset button.
|
CASID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
17 | 1 | alarm | No response | communication | Card;Port;Channel | major |
| | 17 | 2 | alarm | Remote end did not back off in glare | communication | Card;Port;Channel | minor |
|
| - Remote end did not back off in glare.
| 17 | 3 | alarm | Wink expected, did not arrive | communication | Card;Port;Channel | major |
| - Wink expected, did not arrive.
| 17 | 4 | alarm | No dial tone | communication | Card;Port;Channel | major |
| - Event of off-hook did not produce dial tone as expected.
| 17 | 5 | event | CAS signaling group disabled | communication | SG |
|
|
| - CAS signaling group disabled.
| 17 | 6 | alarm | CAS license not enabled | general | System;Service | major |
| - Call attempted but CAS feature is not enabled.
- This alarm is cleared by CAS license enabled event.
| 17 | 7 | event | CAS license enabled | general | System;Service |
| |
|
| - License manager notify CAS that license is enabled.
| 17 | 8 | event | Wink Received | communication | Card;Port;Channel |
| |
|
| - Wink failure had occurred, but wink is received now.
| 17 | 9 | event | Dial Tone Received | communication | Card;Port;Channel |
| |
|
| - No Dial Tone was received, but Dial Tone is received now.
| 17 | 10 | event | Response Received | communication | Card;Port;Channel |
| |
|
| - No Response to seizure was received, but Response is received now.
| 17 | 11 | alarm | Invalid character(s) in calling number | communication | Calling | warning |
|
| - Invalid character(s) removed, correct issue and delete warning.
| 17 | 12 | alarm | Invalid character(s) in called number | communication | Called | warning |
|
| - Invalid character(s) removed, correct issue and delete warning.
| 17 | 13 | event | CAS signaling group enabled | communication | SG |
| |
|
| - CAS signaling group enabled.
| 17 | 14 | alarm | CAS-R2 CD Bit error | communication | Card;Port | minor |
| - CAS-R2 CD Bits are mismatched.
| 17 | 15 | event | CAS-R2 CD Bit error clear | communication | Card;Port |
| |
|
| - CAS-R2 CD Bits are now matching.
| 17 | 16 | alarm | Network Glare occured | communication | Card;Port;Channel | minor |
|
| - Network glare occured on this interface.
|
ConfigurationID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
18 | 1 | event | Config validation failure | general | System;Service | warning |
|
| - Config validation failure during startup.
- Please check the configuration.
| | 18 | 2 | alarm | Newer Config loaded | general | System;Service |
warning |
| - Configuration loaded from newer release than currently running release.
| | 18 | 3 | event | Password decryption failed | general | System;Service | event |
|
| - Password decryption failed on configuration import operation.
| | 18 | 4 | event | Partial factory default | equipment | System;Service | event |
|
| - Partial "factory default or confiugration import" requested by "Username" from "IP address".
| | 18 | 5 | event | Configuration Restore | equipment | System;Service | event |
|
| - Configuration restore requested by "Username" from "IP Address".
|
TCA Thresholds| ID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
| 19 | 1 | alarm | SG Channel Usage exceeded TCA threshold | communication | SG | major | | - Signaling Group channel usage exceeded configured TCA threshold.
| | 19 | 2 | event | SG Channel Usage below TCA threshold | communication | SG |
| |
|
| - Signaling Group channel usage fell below configured TCA threshold.
| | 19 | 3 | alarm | SIP Call License Usage exceeded TCA threshold | communication | System;Service | major | | - SIP Call license usage exceeded configured TCA threshold.
| | 19 | 4 | event | SIP Call License Usage below TCA threshold | communication | System;Service |
| |
|
| - SIP Call license usage fell below configured TCA threshold.
| | 19 | 5 | alarm | SIP Registration Usage exceeded TCA threshold | communication | SIPRegistrarTable | major | | - SIP Registration usage exceeded configured TCA threshold.
| | 19 | 6 | event | SIP Registration Usage below TCA threshold | communication | SIPRegistrarTable |
| |
|
| - SIP Registration usage fell below configured TCA threshold.
| | 19 | 7 | alarm | DSP Usage exceeded TCA threshold | communication | System | major | | - DSP usage exceeded configured TCA threshold.
| | 19 | 8 | event | DSP Usage below TCA threshold | communication | System |
| |
|
| - DSP usage fell below configured TCA threshold.
| | 19 | 9 | alarm | CPU Usage exceeded TCA threshold | communication | System | major | | - CPU usage exceeded configured TCA threshold.
| | 19 | 10 | event | CPU Usage below TCA threshold | communication | System |
| |
|
| - CPU usage fell below configured TCA threshold.
| | 19 | 11 | alarm | Memory Usage exceeded TCA threshold | communication | System | major | | - Memory usage exceeded configured TCA threshold.
| | 19 | 12 | event | Memory Usage below TCA threshold | communication | System |
| |
|
| - Memory usage fell below configured TCA threshold.
| | 19 | 13 | alarm | File Descriptor Usage exceeded TCA threshold | communication | System | major | | - File Descriptor Usage exceeded TCA threshold.
| | 19 | 14 | event | File Descriptor Usage below TCA threshold | communication | System |
| |
|
| - File Descriptor Usage fell below TCA threshold.
| | 19 | 15 | alarm | CPU load average in past 1 minute exceeded TCA threshold | communication | System | major | | - CPU load average in past 1 minute exceeded TCA threshold.
| | 19 | 16 | event | CPU load average in past 1 minute fell below TCA threshold | communication | System |
| |
|
| - CPU load average in past 1 minute fell below TCA threshold.
| | 19 | 17 | alarm | CPU load average in past 5 minutes exceeded TCA threshold | communication | System | major | | - CPU load average in past 5 minutes exceeded TCA threshold.
| | 19 | 18 | event | CPU load average in past 5 minutes fell belowTCA threshold | communication | System |
| |
|
| - CPU load average in past 5 minutes exceeded TCA threshold.
| | 19 | 19 | alarm | CPU load average in past 15 minutes exceeded TCA threshold | communication | System | major | | - CPU load average in past 15 minutes exceeded TCA threshold.
| | 19 | 20 | event | CPU load average in past 15 minutes fell belowTCA threshold | communication | System |
| |
|
| - CPU load average in past 15 minutes fell below TCA threshold.
| | 19 | 21 | alarm | Temporary partition usage exceeded TCA threshold | communication | System | major | | - Temporary partition usage exceeded TCA threshold.
| | 19 | 22 | event | Temporary partition usage fell below TCA threshold | communication | System |
| |
|
| - Temporary partition usage exceeded TCA threshold.
| | 19 | 23 | alarm | Logging partition usage exceeded TCA threshold | communication | System | major | | - Logging partition usage exceeded TCA threshold.
| | 19 | 24 | event | Logging partition usage fell below TCA threshold | communication | System |
|
|
| - Logging partition usage fell below TCA threshold.
|
FQDN| ID | Sub-ID | Type | Default Condition | Category | Decode Key | Default Severity | Auto Clear | Notes/Description |
|---|
| 20 | 1 | alarm | Failed to resolve FQDN | communication | SNMP;IPAddress | minor | | - Failed to resolve IP Address. Ensure that FQDN and DNS server is configured properly.
| | 20 | 2 | event | FQDN resolved | communication | SNMP;IPAddress |
|
|
| - IP Address successfully resolved.
|
Decode Key TableFollowing tables defines the decode key types used through out the system Alarms and Events system in the SBC 1000/2000. Decode Key | Description |
|---|
System | By default it will be the SBC 1000/2000 system | Service | Service in which this alarm/event belongs to, for ex. ISDN, SIP etc.. | Username | Username responsible for the generation of the alarm/event, mostly related to the User Authentication Service | IP address | IP address of the system responsible for generation of this alarm/even. | Frame | Frame responsible, at which the data transmission has failed/generated an error | Card/Slot | Card /Slot involved in generating the alarm For ex. TI DSP etc.. | ActSetTble | Action set table number responsible for the alarm/event | NormTble | Normalization table number responsible for this alarm | RtTble | Route table number responsible for this alarm/event | | TLSProfile | TLS Profile (ID of the TLS Profile) | TransTble | Translation table number responsible for this alarm/event | Call Dest | Call destination (address) responsible for this alarm/event | Conference ID | Conference ID involved in the alarm generation. It will be an integer starting from 1 to FFFFFFFF | Codec | Media codec like G711, used when this alarm is generated | SG/Signaling Group | Signaling Group on which this alarm occurred | Channel | Channel number that involved in generating this alarm | CallID | Call ID of the call failed/is responsible for generating this alarm | Port | Port number on which this alarm is generated | Interface | Name/Number of the interface involved in generating this alarm. For ex. ETH1, T1 etc.. | Server | Server responsible for this alarm. for Ex. SIP server which is not responding | CertificateCommonName | Server certificate common name for ex:"VeriSign Trial Secure Server CA - G2 " | SBAInstance | Its the SBA monitor involved in generating the alarm | Interface | By default it will be the Ethernet interface card | SIPCluster | Name of the SIP cluster associated with a set of SIP servers | ServID | ID of the SIP server | Protocol | Protocol involved in generating this alarm/event | Fan_No | Fan number |
|