Enabling Traps For Remote-Shelf Events; Trap Optimization; Modified Traps To Include Shelf Numbers - Lucent Technologies Stinger Compact Remote Getting Started Manual

Enabling traps for remote-shelf events

When you have configured a trap profile to generate a trap protocol data unit (PDU)
on detection of a certain event, if the event occurs, the system sends a PDU to a
specified SNMP station. For hosted systems, the host sends trap PDUs generated by
any shelf in the system. For background information about traps, see the Stinger
Administration Guide.

Trap optimization

To streamline the number of traps generated by remote shelves, you can enable trap
optimization. Trap optimization behavior depends on the settings of the following
parameters, shown with default values:
[in TRAP/""]
trap-optimization-enabled = no
slot-enabled = no
linkdown-enabled = yes
linkup-enabled = yes
ascend-link-down-trap-enabled = no
ascend-link-up-trap-enabled = no
To fully enable trap optimization, set all these fields to yes. For example:
HOST> read trap dsl-snmp
HOST> set trap-optimization-enabled = yes
HOST> set slot-enabled = yes
HOST> set ascend-link-down-trap-enabled = yes
HOST> set ascend-link-up-trap-enabled = yes
HOST> write -f
The following trap optimizations are made:
LinkUp and LinkDown traps are not generated unless ascend-link-down-trap-
enabled and ascend-link-up-trap-enabled are set to no.
AscendLinkUp traps are not generated in the case of slots coming up and system
reset. In these cases, the ascendLinkUp trap will not be sent for 120 seconds after
the slot comes up.
AscendLinkDown traps are not generated in the case of slots going down.
The sysSlotStateChange trap is generated only for the slot status changes to
operStateDown or operStateUp. The trap is not sent for other intermediate states
such as operStateLoading and operStatePost.
If trap-optimization-enabled is set to yes but slot-enabled is set to no, the
system generates ascendLinkDown and ascendLinkUp traps for each line when a
slot changes state, and does not generate the sysSlotStateChange trap.

Modified traps to include shelf numbers

Several traps have been modified to include the value of the shelf number along with
the slot index for events such as a card reset, slot state change, system clock change,
flash state change, CAC failure, or ATM OAM loopback time-out. In addition, new
traps have been introduced for events and state changes on remote shelves.
The Stinger® Compact Remote ATM DSLAM Getting Started Guide
Hosted System Management
Monitoring the status of remote shelves
6-11