. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-40
Administration and Management
Writer:
Chris Seiter
Project:
Netelligent 2008/2016 10Base-T Repeater User Guide
Comments:
185814-003
File Name:
2000_4.doc
Last Saved On:
8/21/96 10:42 AM
❏
Group Map Change Trap (rptrGroupMapChange)
signifies
that this repeater recognizes that the stack map has changed (i.e.,
one or more repeaters have been added or removed). This trap,
which is sent by the logical bottom repeater (note that a physical
stack may have more than 1 logical bottom repeater; see section
3.11.5), occurs each time that the repeater's power is cycled and for
each event that causes the stack map to change (e.g., hot swapping,
repeater failure). This trap will return a 16 bit value (maximum of
10 bits used; 1 bit per repeater) that contains a bit map of the
available repeaters (LSB is repeater 1).
❏
Health State Trap (rptrHealth)
signifies that the health of this
repeater has changed. A specific message will be returned. Health
state traps include:
Port Autopartition Trap
indicates that a port has been
autopartitioned as a result of 32 consecutive collisions or
because the DTE was jabbering.
Backup Port Activated Trap
a backup port has taken over
for a failed port.
Intrusion Port Trap
an intruder was detected and the port
was disabled.
❏
Reset Trap (rptrReset) signifies that the repeater has completed a
reset action triggered by a management command.
The logical bottom repeater transmits the Group Map Change Trap. The
repeater that flags the trap condition sends all other traps.
To receive a trap, the SNMP network management station must place its IP
and/or IPX address into the repeater's trap table (nws2IPTrapReceiverTable for
IP traps or nws2IPXTrapReceiverTable for IPX traps). The IP and IPX trap
tables can each contain 10 entries. To receive traps from each repeater in a
stack, the the SNMP network manager must enter trap table entries into
each repeater.