Paradyne 9123 manual Standards Compliance for Snmp Traps, Examples

SNMP MIBs and Traps, and RMON Alarm Defaults

Standards Compliance for SNMP Traps

This section describes the FrameSaver unit's compliance with SNMP format standards and with its special operational trap features.

All traps have an associated string to help you decipher the meaning of the trap. Strings associated with an interface with a substring containing $ifString have the following format:

`DLCI $dlciNumber ª$circuitIdº of $ifName frame relay link ª$linkNameº.'

Ð$dlciNumber is the DLCI number. DLCI $dlciNumber ª$circuitIdº only appears when a DLCI is associated with the trap.

Ð$circuitId is the name given to the circuit. It can be an empty string, or a 1± 64 byte string within quotes (e.g., ªChicago to New Yorkº), and only appears when a DLCI with ªcircuitIDº is associated with the trap.

Ð$linkName is the name given to the link. Frame relay $linkName only appears when a frame relay link has been named and is associated with the trap.

Ð$ifName is the string returned for the SNMP ifName variable.

Examples:

`DLCI 100 ªChicago to New Yorkº of Network T1 frame relay link'

In this example, a DLCI and a frame relay link are associated with the trap.

Typically, the $circuitId is a coded string encoded by the network service provider. The following shows an example.

`DLCI 100 ªcc0402±dec0704.RG21º of Network T1 frame relay link'

The unit supports the following traps:

HwarmStart

HauthenticationFailure

HlinkUp and linkDown

Henterprise-Specific

HRMON-Specific

These traps are listed in alphabetical order within each table.

B-6 July 2000 9123-A2-GB20-10