Bay Networks 5000 Spécifications Page 134

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 185
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 133
9031398 E3 Event and Alarm Messages
6-17
Token Ring NMM Agent Events and Alarms
CsEvFormat/Event01020003
{d “%w- %d %m-, %Y - %T”} DCE {O 4}
on ring {I 3} (ring ID {I 1}) whose last
NAUN is {X 5} has detected a
beaconing station. The beacon type is
{T S5TRBeaconType 7}. {t} (name -
{m}). (Trap type: 0x01020003) - (event
[{e}])
CsPCause/Prob01020003
TR STATION BEACONING
PROBABLE CAUSES:
1) The beacon type indicates the reason for
the beacon. If reconfiguration, the ring will
recover. If signal loss, the beaconing station
is no longer receiving a valid signal. If
bitstreaming, the beaconing station is no
longer receiving a valid token or frame but is
receiving a valid signal. If contention
streaming, the station is indicating that
monitor contention could not be resolved
within one second.
RECOMMENDED ACTIONS:
1) For signal loss and bit streaming, locate
and inspect the cabling between the
reporting station and its upstream neighbor,
including any stations which may have
recently inserted.
2) If monitor contention, isolate the
problem by removing all concentrators in the
ring until the ring recovers. Then remove
stations one by one on the suspect
concentrator.
CsEvFormat/Event01020004
{d “%w- %d %m-, %Y - %T”} DCE {O 4}
has detected a splitter on ring {I 3}
(ring ID {I 1}). {t} (name - {m}). (Trap
type: 0x08) - (event [{e}])
CsPCause/Prob01020004
TR SPLITTER DETECTED
PROBABLE CAUSE:
1) A Splitter has been detected on the ring.
Table 6-4. Token Ring NMM Agent Events and Alarms (Continued)
Message in the Event Log
Alarm Manager Probable Cause
Message
Vue de la page 133
1 2 ... 129 130 131 132 133 134 135 136 137 138 139 ... 184 185

Commentaires sur ces manuels

Pas de commentaire