IMG 1010 - Configuring SNMP

1 Related Topics:
2 Miscellaneous Information:
3 Configure SNMP Manager
4 Configure SNMP Agent
5 Filtering Examples:
- 5.1 Example 1:
- 5.2 Example 2:
- 5.3 Example 3:
- 5.4 Example 4:
- 5.5 Example 5:

Miscellaneous Information:

The IMG SNMP solution supports the following standard MIBs.

RFC 1213	RFC 2494	RFC 2863	RFC 3896
RFC 1907	RFC 2571	RFC 3877	RFC 3895

There are currently no Dialogic Enterprise MIBs for the IMG1010 or IMG1004.

These MIB libraries should be included with your GCEMS, however, should you need to compile a standard MIB you can access them at the following web site: http://www.rfc-editor.org/rfc.html.

When configuring both SNMP managers and SNMP agents, configure the SNMP managers first. Once all SNMP managers are configured, the SNMP agents can be created. If adding an SNMP Manager to an existing configuration, any SNMP agents configured will need to be removed and re-added after the new SNMP Managers are created.

Configure SNMP Manager

GCEMS will support configuring up to three SNMP Managers.

Right-click External Network Elements and select New SNMP Managers. An SNMP Managers screen will appear. The SNMP managers screen is basically a placeholder where multiple SNMP Managers can get configured.
Right Click on SNMP Managers object and select New SNMP Manager.
The SNMP Manager Screen will be displayed.

Engine ID: The local engine ID is defined as the unique identifier of an SNMPv3 engine, and is used for identification and not addressing. The IMG does not support SNMPv3 so any number entered into this field will work. To enter the Engine ID, click in the Engine ID field and an Enter Value screen will appear. Enter the Engine ID in this screen.

SNMP Username: Enter a username that identifies this SNMP Manager. Click in the SNMP Username field and enter the name.

SNMP Community Name: The SNMP Agent could require that an SNMP Manager send a particular password with each message. The SNMP Agent would then verify whether the SNMP Manager is authorized to access MIB information. This is used for security in SNMPv2. Most often there is one community string which is used for read-only access to an SNMP Agent. The default value for this community string is often "public". Using this community string like a password, the NMS can retrieve data from network elements. Click in the SNMP Community Name field and enter the name.

SNMP Manager IP Address: Enter the IP address of the SNMP Manager. Click in the SNMP Manager IP address field and an Enter IP address box will appear. Enter IP address here

SNMP Trap Port: The port that SNMP traps are received on. By Default port 162 is displayed as per standard RFCs for SNMP. To change the port click in the SNMP Trap port field and enter the new trap port number.

SNMP Version: The version of SNMP is displayed here. Click in the SNMP version field and a drop down menu will display the two versions of SNMP the IMG supports. The IMG supports

SNMPv1
SNMPv2c

SNMP Timeout: The time to wait for an ACK from an SNMP Manager before timing out. The value entered will be in milliseconds. The default is set to 1500 ms (1.5 seconds). If value needs to be changed, click in the SNMP Timeout field and enter the new value

Trap Retries: The number of times to resend a trap to the SNMP manager. The Default is three. To change, click in the Trap Retries field and select from drop down menu 0-5

The next three fields (Trap Notify Type, Trap Subtree, and Trap Notify Filter) are used for filtering of traps sent from the SNMP Agent. The IMG can be configured to not send a specific set of traps or can also be configured to only send a specific set of traps. This is all done to limit the amount of messages being sent between the SNMP Agent and the SNMP Manager. Below is a short description of each field and also examples of how the filtering works

Trap Notify Type: This field has to do with the filtering of specific traps. The IMG can filter which traps to send or not send to each of the SNMP managers configured. This is done in the Trap Notify Filter field. The two selections from the drop down menu are:

Inclusive - Include traps that match the filtering configured. (Default)
Exclusive - Exclude traps that match the filtering configured.

Trap Subtree: In this field,enter the OID to be filtered. If the set of OID's you would like to either Include or Exclude is 1.3.6.1.2.1.x.x.x. then enter 1.3.6.1.2.1 in this field.

Trap Notify Filter: Use this field to filter out specific OID's. Use this field as a bit mask with a 1 indicating an exact match and a 0 indicating a "wildcard" or a don't care. For example: If the Trap Subtree field has 1.3.6.1.0.6 and the bit mask is 1.1.1.1.0.1 then 1.3.6.1.0.6, 1.3.6.1.1.6, 1.3.6.1.2.6 all the way up through 1.3.6.1.9.6 are filtered and will be either included or excluded depending on the Trap Notify Type field. OID 1.3.6.1.6.7 is not filtered and will be sent.

Configure SNMP Agent

Configure the SNMP Agent for all Physical IMG's in your network. Configure an SNMP agent for each IMG that will be monitored using SNMP. In ClientView, right click on each Physical IMG that will be monitored and select New SNMP Agent. A pane like below will appear.

Engine ID: The local engine ID is defined as the unique identifier of an SNMPv3 engine, and is used for identification and not addressing. The IMG does not support SNMPv3 so any number entered into this field will work. To enter the Engine ID, click in the Engine ID field and an Enter Value screen will appear. Enter the Engine ID in this screen.

SNMP System Name: The name that identifies the SNMP agent. The default name that appears is the name given the Physical IMG. This can be changed to any name by clicking in the SNMP System Name field and typing the new name. This will be printed in any traps that may occur.

System Location: Enter a location for the SNMP Agent. Click in the System Location field and enter the location. This will be printed in any traps that may occur.

System Contact: Enter a contact name to alert people who to contact in the case of an SNMP Trap being sent. This will be printed in any traps that may occur

SNMP Agent Network Interface: Click in this field and a drop down menu displaying all interfaces configured on rear of IMG will appear. Select which interface the SNMP agent will be configured to communicate through.

Repeat above step for each Physical IMG that an SNMP Agent will get configured on.

Filtering Examples:

Example 1:

Trap Notify Type:	Exclusive	Exclude Trap Subtree OID from sending to SNMPManager
Trap Subtree:	1.3.6.1.6.3.1.1.5.4	The OID or range of OID's to exclude
Trap Notify Filter:	1.1.1.1.1.1.1.1.1.1	Each 1 excludes that number in the Trap Subtree

Result: Exclude only Object ID 1.3.6.1.6.3.1.1.5.4 when sending traps to SNMP Manager. Send all other traps.

Example 2:

Trap Notify Type:	Exclusive	Exclude Trap Subtree OID from sending traps to the SNMP Manager
Trap Subtree:	1.3.6.1.6.3.1.1.5	The OID or range of OID's to exclude
Trap Notify Filter:	1.1.1.1.1.1.0.1.1	Each 1 excludes that number in the Trap Subtree

Result: The following Object ID's will not be sent to the SNMP Manager:

1.3.6.1.6.3.1.1.5

1.3.6.1.6.3.2.1.5

1.3.6.1.6.3.3.1.5

1.3.6.1.6.3.4.1.5

1.3.6.1.6.3.5.1.5

1.3.6.1.6.3.6.1.5

1.3.6.1.6.3.7.1.5

1.3.6.1.6.3.8.1.5

1.3.6.1.6.3.9.1.5

1.3.6.1.6.3.0.1.5

Example 3:

Trap Notify Type:	Inclusive	Include Trap Subtree OID when sending traps to the SNMP Manager
Trap Subtree:	1.3.6.1.6.3.1.1.5.3	The OID or range of OID's to include
Trap Notify Filter:	1.1.1.1.1.1.1.1.1.1	Each 1 includes that number in the Trap Subtree

Result: Include only Object ID 1.3.6.1.6.3.1.1.5.3 when sending traps to SNMP Manager. Do not sent any other traps.

Example 4:

Trap Notify Type:	Inclusive	Include Trap Subtree OID when sending traps to the SNMP Manager
Trap Subtree:	1.3.6.1.6.3.1.1.5	The OID or range of OID's to include
Trap Notify Filter:	1.1.1.1.1.1.1.0.1	Each 1 includes that number in the Trap Subtree

Result: The following object ID's will be sent to the SNMP Manager. All others will be filtered out.