B. SNMP MIBs, Traps, and RMON Alarm Defaults

Table B-7. enterprise-Specific Traps and Variable-Bindings (3 of 3)

Trap

Variable-Bindings

Possible Cause

 

 

 

enterpriseTest-

For physical interfaces and

At least one test has been started

Start(5)

frame relay links:

on an interface or virtual circuit.

 

ifIndex (RFC 1573)

String:

 

.0.0 (placeholder)

‘$testString test started on

 

$ifString.’

 

 

 

￿devLastTrapString

(e.g., ‘DTE Loopback test started

 

(devHealthAndStatus.mib)

on Sync Data Port S01P1.’)

 

For virtual circuits (DLCIs):

 

enterpriseTest-

All tests have been halted on an

Stop(105)

devFrExtDlciIfIndex

interface or virtual circuit.

 

 

 

(devFrExt.mib)

String:

 

devFrExtDlciDlci

‘$testString test stopped on

 

$ifString.’ (e.g., ‘Disruptive PVC

 

￿(devFrExt.mib)

 

 

Loopback test stopped on

 

devLastTrapString

DLCI 100 of Sync Data Port

 

(devHealthAndStatus.mib)

S01P1 frame relay.’)

 

 

 

Trap: RMON-Specific

Two traps are defined to support the Alarm and Events Groups of RMON. See RMON Alarm and Event Defaults on page B-14for the default values that will generate RMON-specific traps.

Table B-8. RMON-Specific Traps and Variable-Bindings

Trap

Variable-Bindings

Possible Cause

 

 

 

 

risingAlarm

 

alarmIndex (RFC 1757)

Object being monitored has risen

 

 

alarmVariable (RFC 1757)

above the set threshold.

 

 

 

 

 

alarmSampleType

String:

 

 

‘Change in $variableName

 

 

(RFC 1757)

 

 

$typeString threshold of

 

 

 

 

 

alarmValue (RFC 1757)

$alarmRisingThreshold by $

 

 

alarmRisingThreshold or

(alarmValue –

 

 

AlarmRisingThreshold.’)

 

 

alarmFalling Threshold

 

 

 

 

 

(RFC 1757)

 

 

 

devLastTrapString

 

 

 

(devHealthAndStatus.mib)

 

 

 

 

 

fallingAlarm

 

alarmIndex (RFC 1757)

Object being monitored has fallen

 

 

alarmVariable (RFC 1757)

below the set threshold.

 

 

 

 

 

alarmSampleType

String:

 

 

‘Change in $variableName

 

 

(RFC 1757)

 

 

$typeString threshold of

 

 

 

 

 

alarmValue (RFC 1757)

$alarmRisingThreshold by $

 

 

alarmFallingThreshold

(alarmValue –

 

 

AlarmRisingThreshold.’)

 

 

(RFC 1757)

 

 

 

 

￿

devLastTrapString

 

 

 

(devHealthAndStatus.mib)

 

 

 

 

 

9700-A2-GB20-20

December 2002

B-13

Page 253
Image 253
Paradyne 9720, 9788 manual Trap RMON-Specific

9720, 9788 specifications

The Paradyne 9820-8M, 9788, 9128 standalone, 9128 carrier-mount, and 9820-2M are critical components in telecommunications networks, designed to enhance data transmission and improve connectivity. Each model offers unique features and capabilities that cater to various requirements in both enterprise and service provider environments.

The Paradyne 9820-8M is a multi-service access platform that provides high-speed connectivity for voice, video, and data transmission. It supports multiple protocols, enabling seamless integration into existing infrastructures. Key features include a modular design that allows for scalability and easy upgrades, ensuring that organizations can adapt to evolving demands. Its advanced error correction and QoS (Quality of Service) features ensure reliable performance, even in challenging network conditions.

The Paradyne 9788 serves as a versatile platform for both digital and analog communications. It excels in the delivery of broadband services, supporting T1/E1 lines and providing robust mechanisms for data transmission. This model emphasizes redundancy and resilience, with built-in protection switching capabilities that maintain service continuity during faults or maintenance activities. Its compact design makes it an ideal solution for environments with space constraints.

The 9128 standalone model is aimed at customers requiring an easy-to-deploy solution for point-to-point connections. This model offers critical features such as an intuitive user interface, comprehensive diagnostics, and monitoring capabilities that facilitate system management. It also supports diverse network topologies, making it suitable for various deployment scenarios.

In contrast, the 9128 carrier-mount version is engineered for organizations needing to manage multiple connections within a central office or remote site. This model is specifically designed to be mounted in standard telecom racks, optimizing space utilization while maintaining high performance. Its robust hardware allows for excellent thermal management and environmental resilience.

Lastly, the Paradyne 9820-2M combines versatility with high-performance capabilities, making it a reliable choice for service providers. It features dual-channel support, enabling simultaneous transmission and providing a cost-effective solution for high-capacity data needs. With enhanced security features, including encryption capabilities, the 9820-2M ensures that sensitive information transmitted across networks is protected against unauthorized access.

Collectively, these Paradyne models exemplify advanced telecommunications technology, offering scalability, resilience, and high performance. Their diverse features cater to the unique demands of various users, from enterprise networks to service providers, facilitating the continual evolution of communication technologies.