Cisco PXM Version 1.1 Guide de l'utilisateur Page 660

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 972
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 659
C-46
Cisco Media Gateway Manager 5.0 User Guide
OL-5461-02
Appendix C Troubleshooting
Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems
Figure C-4 XML annotation can be read as follows. A CorrelatedBmRule can have any of the following:
0 or more ClearAlarmCondIds
1 New Alarm (which consists of NewAlarmConditionID, NewAlarmServAffect, etc.)
3. Transient Alarm Rule Type
The Transient Alarm rule type is used to distinguish events vs. alarms. Alarm List does show some
events. Events are normally associated with the NMS itself. Examples of events are 'Process restarted'
or 'Primary Gateway disconnected'. These are NMS events that are not correlated, but are displayed in
the alarm list. Another example of a transient event that is not related to the NMS is a card switchover.
If APS is enabled on a card and there is an APS switchover, an event will be displayed in the alarm list.
The primary distinction between 'Transient' Events and 'Correlated' Alarms is Transient events are not
cleared by the network, whereas correlated alarms are. See Figure C-5.
Figure C-5 Transient Alarm Rule Diagram
Figure C-5 XML annotation can be read as follows. A Transient can only one a New Alarm associated
with it. Note, there are no 'ClearAlarmCondID' associated with a Transient rule. Transient alarms are
either manually cleared by the user, cleared by the same transient alarm occurring twice, or purged by
NMServer when a high threshold is hit.
C.6.5.3 Alarm Severity and Object Severity
There are two severities assigned to every alarm in alarm rules XML file. The two severities are called
'Object' and 'Alarm' severity. These severities do match for most alarms. There are some cases however,
where these severities are different. Below is an example of XML alarm rule where object and alarm
severity do not match:
<CorrelatedRule State="1 -1">
<ClearAlarmCondID>10302</ClearAlarmCondID>
<ClearAlarmCondID>10303</ClearAlarmCondID>
<ClearAlarmCondID>10304</ClearAlarmCondID>
<NewAlarmCondID>10301</NewAlarmCondID>
<NewAlarmServAffect>0</NewAlarmServAffect>
<NewAlarmTransient>0</NewAlarmTransient>
<NewAlarmDbPersistent>0</NewAlarmDbPersistent>
Vue de la page 659
1 2 ... 655 656 657 658 659 660 661 662 663 664 665 ... 971 972

Commentaires sur ces manuels

Pas de commentaire