IMG 1010 - Supported MIBs
- Kelli Higdon
Â
The IMG SNMP solution supports the following standard MIBs below. The MIB libraries are loaded into the GCEMS Linux Server when installing the GCEMS application. The MIB libraries are located in the /opt/dialogic/common/snmp directory on the GCEMS server, or can be located at the following web site: http://www.rfc-editor.org/rfc.html
There are currently no Enterprise MIBs for the IMG.
RFC 1213- Management Information Base for Network Management of TCP/IP-based internets:MIB-II. A collection of managed objects used to define SNMP entities within the SNMP architecture.
RFC 3895- Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types. Defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects used for managing DS1, E1, DS2 and E2 interfaces.
RFC 3896- Definitions of Managed Objects for the DS3/E3 Interface Type. Industry Standard MIB which enables monitoring of a DS3 trunk on the IMG.
RFC 2571- An Architecture for Describing SNMP Management Frameworks. A collection of managed objects used to define SNMP entities.
RFC 1907- Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2)
RFC 2494- Definitions of Managed Objects for the DS0 and DS0 Bundle Interface Type.
RFC 2863- The Interfaces Group MIB. Support for this MIB provides several benefits:
A view of control, signalling, and data ports.
Descriptive information about these ports.
Measurements of the flow of traffic including number of packets in and out.
Recording of errors such as numbers of packets dropped.
Managers used to query the switch should update their list of compiled MIBs to include RFC 2863. ÂRFC 3877- Alarm Management Information Base (MIB). Support for the alarm MIB offers these major benefits:
The ability to inspect the alarm tables and find out what is currently wrong with the system.
The ability to model alarms in a generic way.
The ability to send out generic traps when alarms are raised.
Alarm Traps:
AlarmActiveState- This trap is sent out when an alarm is raised. It contains the alarmModelTable number of the alarm as well as a resource ID which identifies specifically what the alarm refers to (for instance for a link down alarm you would indicate which link it is).
AlarmClearState- This is sent to the snmp manager when an alarm is cleared.
Below is a screen capture displaying the traps sent to the SNMP manager after an event happens. Within these traps the alarms that are set are displayed. The SNMP manager will have a trap sent to it for each alarm that is set. In screen capture the alarmModelTable portion will give an indication of which alarm was sent in each trap. The two numbers after the alarmModelTable indicate the alarm index and state. The first number is the Index and second number is the state. Once the number of each alarm is acquired, you can look up the description of the alarm by opening up the Alarm Model Entry pane in the SNMP manager. The Alarm Model Entry Table is shown in second screen capture below.
Traps sent to SNMP Manager
Alarm Model Entry Table displaying description of each alarm
 Received Trap/Alarm Description
Received Trap | Alarm Model Description: | Â Alarm Model Description from RFC |
1.3.6.1.2.1.118.1.1.2.1.3 | Ethernet Link Failure | 1.3.6.1.2.1.118.1.1.2.1.6.1.3 |
1.3.6.1.2.1.118.1.1.2.2.3 | System Busy Condition  | 1.3.6.1.2.1.118.1.1.2.1.6.2.3 |
1.3.6.1.2.1.118.1.1.2.3.3 | System Busy Warning | 1.3.6.1.2.1.118.1.1.2.1.6.3.3 |
1.3.6.1.2.1.118.1.1.2.4.3 | System Memory Low | 1.3.6.1.2.1.118.1.1.2.1.6.4.3 |
1.3.6.1.2.1.118.1.1.2.5.3 | NFS Minor Traffic | 1.3.6.1.2.1.118.1.1.2.1.6.5.3 |
1.3.6.1.2.1.118.1.1.2.6.3 | NFS Major Traffic | 1.3.6.1.2.1.118.1.1.2.1.6.6.3 |
1.3.6.1.2.1.118.1.1.2.7.3 | Remote ISUP Unavailable | 1.3.6.1.2.1.118.1.1.2.1.6.7.3 |
1.3.6.1.2.1.118.1.1.2.8.3 | SS7 Signaling Stack Busy | 1.3.6.1.2.1.118.1.1.2.1.6.8.3 |
1.3.6.1.2.1.118.1.1.2.9.3 | Signaling Link Congestion | 1.3.6.1.2.1.118.1.1.2.1.6.9.3 |
1.3.6.1.2.1.118.1.1.2.10.3 | Radius Server No Access | 1.3.6.1.2.1.118.1.1.2.1.6.10.3 |
1.3.6.1.2.1.118.1.1.2.11.3 | Approaching Busy | 1.3.6.1.2.1.118.1.1.2.1.6.11.3 |
1.3.6.1.2.1.118.1.1.2.12.3 | Busy | 1.3.6.1.2.1.118.1.1.2.1.6.12.3 |
1.3.6.1.2.1.118.1.1.2.13.3 | Span Dead | 1.3.6.1.2.1.118.1.1.2.1.6.13.3 |
1.3.6.1.2.1.118.1.1.2.14.3 | VMOD OOS | 1.3.6.1.2.1.118.1.1.2.1.6.14.3 |
1.3.6.1.2.1.118.1.1.2.15.3 | VMOD Dead | 1.3.6.1.2.1.118.1.1.2.1.6.15.3 |
 Supported SNMP Alarms:
Index Number | State Number | Alarm Description | Data / Troubleshooting |
1 | 3 | Ethernet Link Failure | Alarm is sent if any ethernet port loses connection and alarm is cleared when connection is re-established. Trace the network cable between the port and the remote ethernet switch. Replace ethernet cable or connector as necessary. |
2 | 3 | System Busy Condition | The system ignores any incoming calls until the alarm is cleared. By Ignoring incoming calls the traffic load decreases and eventually the alarm will clear. Ensure that System Busy Warning messages are no longer seen. Return traffic to normal levels and resume normal operation. |
3 | 3 | System Busy Warning | This notification indicates that the traffic volume is approaching its capacity. This message is only a warning. It does not mean a System Busy condition will occur. The System Busy Warning does not have a clearing Alarm. It continues to occur every few seconds, until the CPU utilization reduces. The System Busy Warning messages can be between 2 and 20 seconds apart, depending on system load. The CPU has exceeded the "System Busy Warning" threshold. This condition can happen due to traffic congestion or by having Debug printing enabled. When a System Busy Warning is generated, the user should reduce the number of new calls until the System Busy Warning messages cease. Whenever possible, ramp call rates up slowly and evenly to prevent an initial System Busy. Do not re-configure, and do not enable additional diagnostics. |
4 | 3 | System Memory Low | System memory has dropped below the minimum level of performance. When the system is in this condition, it is also in a System Busy condition and will send a System Busy Alarm to the host. Check for other error messages that would indicate a network or system condition leading to this problem. |
5 | 3 | NFS Minor traffic | NFS Traffic Minor Threshold Alarm |
6 | 3 | NFS Major traffic | NFS Traffic Threshold Major Alarm |
7 | 3 | SS7 Remote ISUP | The address information represents the SS7 stack and Destination Point Code (DPC). Check the status of the Links and see if they are 'in service'. If they are not 'in service', attempt to determine why the links are Out Of Service. Verify they are marked 'in service' from a host perspective. Check the status of layer 1, the T1/E1 span. On the span also check for any slips or framing errors. |
8 | 3 | SS7 Signaling Stack Busy Congestion | Decrease the ISDN/SS7 load. Â Consult Sangoma Customer Technical Support. |
9 | 3 | SS7 Signaling Link Congestion | When a link is congested, the IMG sends this alarm to the host. If the system has not decreased a call to this DPC and this symptom persists, check the network engineering plan to possibly create another link in the link set. |
10 | 3 | Radius Server No Access | This alarm is sent when the IMG is not able to access the radius server. Check that the IP address of the Radius server is correct. Check that the Radius server is accessible and the service is running. |
11 | 3 | Card Approaching Busy | This alarm is sent when the IMG E1/T1, SS7, ISDN, SIP, or H.323 systems start to become busy. No action required at this time. If load continues, subsequent alarms and recovery action will be initiated. |
12 | 3 | Card Busy | This alarm is sent when the IMG E1/T1, SS7, ISDN, SIP, or H.323 systems become busy. If the system has not decreased call load and this symptom persists, check network engineering for proper load balancing. |
13 | 3 | Span Dead | This alarm is generated when the IMG detects a carrier group alarm for more than the allowed time. Either the clock source was lost or the physical connection to the network was broken. Check that the physical connection has not been compromised. Check that a loop timing source has been configured. |
14 | 3 | VMOD OOS | This alarm is sent when a VoIP module becomes inaccessible. Contact Sangoma support for assistance. |
15 | 3 | VMOD Dead | This alarm is sent when a VoIP module becomes inaccessible. Contact Sangoma support for assistance. |
Related Topics:
Â