Specifications

Token Ring NMM Agent Events and Alarms
Event and Alarm Messages
6-18
SynOptics Series 5000
Management Module Guide
CsEvFormat/Event01020005
{d “%w- %d %m-, %Y - %T”} DCE {O 4}
has detected a new active monitor
(MAC address - {X 7}) on ring {I 1}. The
last Nearest Upstream Neighbor
Address (NAUN) is {X 5}. {t} (name -
{m}). (Trap type: 0x08) - (event [{e}])
CsPCause/Prob01020005
DUPLICATE CHASSIS MODEL EXISTS
PROBABLE CAUSES:
1) This model was created with a Network
Address that is contained in a SynOptics
5000 chassis that has already been modeled.
RECOMMENDED ACTIONS:
1) Destroy this HubSyn5xxx chassis model.
2) Use the Find View to locate a model with
the same Network Address used to create
this model. Then use Navigate to go up the
modeling hierarchy to the HubSyn5xxx
chassis model.
CsEvFormat/Event01020006
{d “%w- %d %m-, %Y - %T”} DCE {O 4}
(MAC Address - {X 5}) has detected a
bridge deinserting from ring {I 3} (ring
ID {I 1}). {t} (name - {m}). (Trap type:
0x01020006) - (event [{e}])
CsPCause/Prob01020006
NMM MODULE REMOVED FROM THE
CHASSIS
PROBABLE CAUSES:
1) The NMM that this NMM Agent model
is associated with has been removed from the
chassis.
2) The NMM is rebooting during a
reconfiguration of the chassis model. The
NMM module will not appear in the chassis’
module list when the NMM is rebooting and
the chassis model intelligence considers the
module as pulled.
RECOMMENDED ACTIONS:
1) Check the chassis to see if this was done
intentionally.
2) Open the HubSyn5xxx’s Chassis Group
view and double click the Board Group entry.
Check to see if the module’s entry is in the
table. Open the Chassis Modeling
Information View off the HubSyn5xxx press
the Reconfigure Chassis Models button.
Table 6-4. Token Ring NMM Agent Events and Alarms (Continued)
Message in the Event Log
Alarm Manager Probable Cause
Message