Specifications

9031111 E7 Event and Alarm Messages
4-3
Device Events and Alarms
CsEvFormat/Event00010402
{d “%w- %d %m-, %Y - %T”} - Device
{m} of type {t} is created with a
physical (Mac) address already
used by another model. (event [{e}])
CsPCause/Prob00010402
DUPLICATE PHYSICAL ADDRESS
The model has the same Physical
address (Mac address) as that of some
other model.
CsEvFormat/Event00010702
{d “%w- %d %m-, %Y - %T”} - Alarm
number {I 0x700} cleared for device
{m} of type {t}. (event [{e}])
No Probable Cause Message
CsEvFormat/Event000d0001
{d “%w- %d %m-, %Y - %T”} - Bridge
{m} of type (t) has reported a root
change. (event [{e}])
CsPCause/Prob000d0001
This bridge has become the new root of
the Spanning Tree.
CsEvFormat/Event000d0002
{d “%w- %d %m-, %Y - %T”} - Bridge
{m} of type (t) has reported a
network topology change. (event
[{e}])
CsPCause/Prob000d0002
A port has transitioned from the
Learning state to the Forwarding state,
or from the Forwarding state to the
Blocking state.
CsEvFormat/Event000d0101
{d “%w- %d %m-, %Y - %T”} - Port {I
3} on module in slot {I 1} of {m} ({t}),
has segmented.
CsPCause/Prob000d0101
The port has made 32 consecutive
attempts to transmit which resulted in
a collision each time or the port collision
detector was turned on for longer than
2.4 milliseconds. Each of these collision
occurrences are caused by a cabling
problem of extremely high rates of
traffic on the segment the port is
attached to.
CsEvFormat/Event000d0102
{d “%w- %d %m-, %Y - %T”} - Port {I
3} on module in slot {I 1} of {m} ({t}),
has unsegmented.
CsPCause/Prob000d0102
The port has transmitted or received a
valid packet. This can occur when a
cabling or termination fault has been
corrected. Unsegmenting can also occur
on a port that previously was not in use.
Table 4-1. EMME/EMM-E6 Events and Alarms (Continued)
Message in the Event Log Alarm View Probable Cause
Message