IP Backbone Alarms

8/18/2019 IP Backbone Alarms

http://slidepdf.com/reader/full/ip-backbone-alarms 1/36

Central Management StationTM

2.1

Monitoring Guide

Document Version: 2.5Document Status: PROPOSEDDocument Release Date: August 2007

IP-Backbone



Copyright © Acision BV 2006-2007

All rights reserved. This document is protected by international copyright law and may not be reprinted, reproduced, copied or utilised in whole orin part by any means including electronic, mechanical, or other means without the prior written consent of Acision BV.

Whilst reasonable care has been taken by Acision BV to ensure the information contained herein is reasonably accurate, Acision BV shall not,under any circumstances be liable for any loss or damage (direct or consequential) suffered by any party as a result of the contents of thispublication or the reliance of any party thereon or any inaccuracy or omission therein. The information in this document is therefore provided onan “as is” basis without warranty and is subject to change without further notice and cannot be construed as a commitment by Acision BV.

The products mentioned in this document are identified by the names, trademarks, service marks and logos of their respective companies ororganisations and may not be used in any advertising or publicity or in any other way whatsoever without the prior written consent of thosecompanies or organisations and Acision BV.



The distribution of this document is restricted and the contents of this document should be treated as confidential information.It will only be provided to customers under a signed Non-Disclosure Agreement.

iii

Table of Contents

Preface .......................................................................................................................v

1 Monitoring Hardware/ Interface Level ...............................................................1

1.1 ME Hardware Overview.........................................................................................................1

1.2 Hardware/ Interface Alarms and Traps..................................................................................1

1.3

Monitoring Interface Status....................................................................................................9

1.4 Interface Events.....................................................................................................................9

2 Monitoring Connect ivity Level ......................................................................... 10

3 Monitoring Process/ Application Level ...........................................................11

3.1 Process/ Application Level Alarms and Traps .....................................................................11

4 Monitoring Quality Of Service Level ...............................................................19

4.1 Key Components .................................................................................................................19

4.1.1

Host (Platform) KPIs.............................................................................................19

4.1.2 Services (Application) KPIs ..................................................................................19

5 Monitoring On Overload Situations................................................................. 20

5.1 Key Components .................................................................................................................20

5.2 Hardware/ Interface Capacity Alarms..................................................................................20

6 Active Alarm Viewing for IP-Backbone........................................................... 21

Appendix A. Cisco IP-BB Standard Reports ...................................................23

Appendix B.

Cisco Specific Performance Indicators ..................................... 25

Appendix C. Appl icat ion Performance Ind icators .......................................... 26

Abbreviations .......................................................................................................... 28

References ...............................................................................................................29




iv

List of Tables

Table P-1-1: Typographic Conventions .................................................................................................. vi

Table 1-1: chass i smgrext MIB (For ME 11501 Only)..........................................................................1

Table 1-2: snmpext MIB (For ME 11501 Only).......................................................................................2

Table 1-3: svcext MIB (For ME 11501 Only).........................................................................................2

Table 1-4: t er mi nal mgmt MIB (For ME 11501 Only)............................................................................2

Table 1-5: CISCO-ENVMON MIB............................................................................................................3

Table 1-6: CISCO-FLASH MIB ................................................................................................................7

Table 1-7: IF MIB .....................................................................................................................................8

Table 3-1: CISCO-CONFIG-MAN MIB...................................................................................................12

Table 3-2: CISCO-HSRP MIB................................................................................................................12

Table 3-3: CISCO-ISDN MIB .................................................................................................................12

Table 3-4: CISCO-ISDNU-IF-MIB ..........................................................................................................13

Table 3-5: CISCO-STP-EXTENSIONS MIB ..........................................................................................14

Table 3-6: CISCO-VLAN-MEMBERSHIP MIB.......................................................................................15

Table 3-7: CISCO-VTP MIB...................................................................................................................15

Table 3-8: apIpv4 MIB (For ME 11501 Only).........................................................................................17

Table 3-9: apIpv4Redundancy MIB (For ME 11501 Only).....................................................................17

Table 5-1: CISCO-PROCESS-MIB (cpmCPUTotal1minRev)................................................................20

Table 6-1: AAV Counters for IP-Backbone............................................................................................21

Table 6-2: Cisco IP-BB Standard Reports .............................................................................................23

Table 6-3: ARROWPOINT-CHASSISMGREXT-MIB (chassi smgr ext . mi b) ....................................25

Table 6-4: CISCO-PROCESS-MIB........................................................................................................25

Table 6-5: IP-MIB...................................................................................................................................26

Table 6-6: IF-MIB ...................................................................................................................................26




v

Preface

Purpose

The purpose of this document is to provide a Monitoring Guide for IP-Backbone ManagedElements (MEs). The IP-Backbone Monitoring Guide provides operational information onalarms (traps), Key Performance Indicators (KPIs), and Threshold Crossing Alarms (TCAs)on KPIs that are used by the CMS Central Management System to monitor theIP-Backbone.

This Monitoring Guides is for Cisco IP Backbone: 2950, 3550, 3750, 3560, 2611XM, 2811and 11501.

Audience

The target audience of this document is users of a monitoring solution consisting of theIP-Backbone ME and the CMS.

Scope

The scope of the document is to provide the following information:

• Components of the ME that require monitoring:− On hardware/interface level,

− On connectivity level,

− On process/application level,

− On quality of service level,

− In overload situations.

• Alarms to monitor a specific component on the hardware/interface, connectivity andprocess/application levels. For each alarm:

− Management Information Base (MIB) in which the alarm is defined,

− Corresponding message text,

− Corresponding proposed severity,

− Additional explanation if appropriate,

− Recommended remedial user action,

− Correlated alarm (the alarm that clears).

• For the components on quality of service level and overload situations:

− Key Performance Indicators (KPIs) that measure QoS and capacity overload alongwith a description of that KPI and the MIB in which that KPI is defined,

vi

− Quality of Service and capacity threshold alarms that may be generated. Such alarmsare generated by the CMS when the corresponding KPI crosses a pre-definedthreshold:

KPI on which this TCA may be generated,

Corresponding message text (including the 'raise' threshold),

Corresponding proposed severity,

Additional explanation if appropriate,

Recommended remedial user action,

Correlated alarm (the 'clear' threshold).

Typographic Conventions

In this document, the typographic conventions listed in Table P-1-1 are used.

Table P-1-1: Typographic Conventions

Typeface or Symbol Meaning/Used for Example

Cour i er Refers to a keyboard key, systemcommand, label, button, filename,window, or other computer componentor output.

The directory data contains…

Click the Cl ose button to…

<cour i er > Serves as a placeholder for variabletext that the user will replace asappropriate to its context.

Use the file name <ent i t y>. cf g for...

[ ] Refers the user to externaldocumentation listed in the References

section.

[ETSI 03.38]

Italic Emphasises a new word or term ofsignificance.

Jumpstart, the install procedure on aSUN T1,

% Denotes a Unix regular-user prompt forC shell.

% l s

# Denotes a Unix super-user prompt forany shell.

# l s

$ Denotes an OpenVMS DigitalCommand Language prompt.

$ di r

\ (Unix)or

– (OpenVMS)

Denotes line continuation; thecharacter should be ignored as the

user types the example, and Ent er should only be pressed after the lastline.

% gr ep sear chf ort hi s \dat a/ *. dat

$ sear ch [ . data] *. dat -sear chf ort hi s

- Bridges two keystrokes that should bepressed simultaneously.

If Ct rl - C does not work, use Ct r l - Al t - Del .

Denotes a “note”, a piece of textalongside the normal text requiringextra attention.

Note that the system is usually...

1

1 Monitoring Hardware/ Interface Level

1.1 ME Hardware Overview

The IP-Backbone consists of the following ME types: Cisco 2950, Cisco 3550, Cisco 3560,Cisco 2611XM and Cisco 11501.

1.2 Hardware/ Interface Alarms and Traps

Hardware interface alarms/traps may be generated, depending on the actual MIB support ofparticular IP-backbone ME types, for the following entities:

• Ethernet Interface Cards

• Power-Supply

• Fan

• CPU Threshold alarms may be generated. Please refer to Section 5.2.

In the following Tables the presentation of traps in the alarm browser is described. In thecorrelation field it is indicated with what alarms the alarm under consideration correlates,where correlation means that the existing alarm is replaced with the newly arriving alarm.The existing alarm is then moved to the History Alarm Browser. I.e. the existing alarm isacknowledged.For some alarms a clear alarm exists. A clear alarm acknowledges an existing alarm and isitself moved to the history alarm browser as well. Clear alarms always have severityNORMAL. All alarms with severity NORMAL are clear alarms.Not all alarms have corresponding clear alarms. It may be necessary to manuallyacknowledge such alarms (to move them to the history alarm browser).

In the Message Text and correlation fields of the alarm description Tables reference is madeto <$1>, <$2>etc. These references refer to variable bindings of the underlying trap, where<$1>refers to the value of the first variable binding, <$2>to the value of the secondvariable binding etc.

In the following Table the presentation of traps specified in the chass i smgrext MIBmodule in the alarm browser is described. This MIB module describes the Cisco CSSChassis Module objects.

Table 1-1: chassismgrext MIB (For ME 11501 Only)

Signal Message Text Severity Explanation User Action

Correlation

apChassi sMgr Ext PsTr ap

Power supply state changedon <$A>, description: <$1>.

Major This trap is generatedwhen the powersupply state changes.

CheckPowerSupply

Same signalfor samenode.

apChassi sMgr Ext Modul eTr ap

Chassis Manager modulestate changed on <$A>,

description: <$1>.

Major This trap is generatedwhen the module

state changes.

Checkchassis

Same signalfor same

node.

2

In the following Table the presentation of traps specified in the snmpext MIB module in thealarm browser is described. This MIB module describes the Cisco CSS SNMP extensions.

Table 1-2: snmpext MIB (For ME 11501 Only)


Correlation

apSnmpExt Rel oadTr ap

System is gettingrebooted, CauseDescription: <$1>.

Critical This Reload trap is generatedwhen a reboot of the system isperformed."

Note: This trap may beenabled/disabled viaapSnmpExt Rel oadTr aps (SeeCisco documentation)

Checkreason forreload


In the following Table the presentation of traps specified in the svcext MIB module in thealarm browser is described. This MIB module describes the Cisco CSS (Content ServiceSwitch) Services.

Table 1-3: svcext MIB (For ME 11501 Only)


Correlation

apSvcTransit i onTrap

Service statetransition occurred,service trap event:<$1>.

Major A service transition trap isgenerated whenever the servicestate transitions from ACTIVE ->DEAD, or DEAD -> ACTIVE."

Checkreason fortransition


In the following Table the presentation of traps specified in the svcext MIB module in thealarm browser is described. This module describes the MIB support for the CSSTer mi nal Management Options

Table 1-4: terminalmgmt MIB (For ME 11501 Only)

Signal Message Text Severity Explanation Correlation

apTermSessLogi nFai l ure Tr ap

Failure during login,description: <$1>.

Warning This trap is generated when a login failureoccurs at one of the following access points;Console, FTP, or TELNET. A description of thelogin failure accompanies this trap, whichindicates the IP address of the source that

attempted the login, the user name that wasused, and the access point


In the following Table the presentation of traps specified in the CISCO-ENVMON MIBmodule in the alarm browser is described. The CISCO-ENVMON MIB describes the statusof the Environmental Monitor.

The distribution of this document is restricted and the contents of this document should be treated as confidential informatioIt will only be provided to customers under a signed Non-Disclosure Agreement.

3

Table 1-5: CISCO-ENVMON MIB

Signal Message Text Severity Explanation U

ci scoEnvMonShut downNot i f i cat i on

Shutdown initiated byenvironment monitor.

Critical A ci scoEnvMonShutdownNot i f i cat i on is sent if theenvironmental monitor detects a test point reaching a critical stateand is about to initiate a shutdown. This notification contains noobjects so that it may be encoded and sent in the shortest amount oftime possible. Even so, management applications should not relyon receiving such a notification as it may not be sent before theshutdown completes.

Rprpe A

ci scoEnvMonRedundantSuppl yNot i f icat i on

Starting post processing ofci scoEnvMonRedundant Suppl yNot i f i cat i on.

Note: This event is stored inthe History Alarm Browser

immediately for each of thenext five notifications

Normal A ci s coEnvMonRedundant Suppl yNot i f i cat i on is sent if theredundant power supply (where extant) fails.

-

ci scoEnvMonRedundantSuppl yNot i f icati on -notFunct i oni ng

Redundant Power Supplystatus changed to"notFunct i oni ng" for<description>.

Critical A ci s coEnvMonRedundant Suppl yNot i f i cat i on is sent if theredundant power supply (where extant) fails.

-

ci scoEnvMonRedundantSuppl yNot i f icati on -cr i t i cal

Redundant Power Supplystatus changed to "critical"for <description>.


-

ci scoEnvMonRedundantSuppl yNot i f icati on -shut down

Redundant Power Supplystatus changed to\"shutdown\" for<description>.


-

ci scoEnvMonRedundantSuppl yNot i f icat i on - warni ng

Redundant Power Supplystatus changed to "warning"for <description>.

Warning A ci s coEnvMonRedundant Suppl yNot i f i cat i on is sent if theredundant power supply (where extant) fails.

-

5


ci scoEnvMonVol t St at usChangeNot i f

Starting post processing ofci scoEnvMonVol tSt at usChangeNot i f .

Note: This event is stored inthe History Alarm Browserimmediately for each of thenext five notifications

Normal A ci scoEnvMonVol t St at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonVol tageSt at e.

-

ci scoEnvMonVol t St at usChangeNot i f- shutdown

Voltage status changed to"shutdown" for<description>. The systemshould be shutdownimmediately. Measuredvalue <value> millivolts.

Critical A ci scoEnvMonVol t St at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonVol tageSt at e.

-

ci scoEnvMonVol t St at usChangeNot i f- cr i t i cal

Voltage status changed to"critical" for <description>.Measured value <value>millivolts.

Critical A ci scoEnvMonVol t St at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonVol tageSt at e.

-

ci scoEnvMonVol t St at usChangeNot i f- mal f unct i on

Voltage status changed to"notFunct i oni ng" for<description>. Measuredvalue <value> millivolts.

Major A ci scoEnvMonVol t St at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonVol tageSt at e.

-

ci scoEnvMonVol t St at usChangeNot i f- war ni ng

Voltage status changed to"warning" for <description>.Measured value <value>millivolts.

Warning A ci scoEnvMonVol t St at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonVol tageSt at e.

-

ci scoEnvMonVol t St at usChangeNot i f- normal

Voltage status changed to"normal" for <description>.Measured value <value>millivolts.

Normal A ci scoEnvMonVol t St at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonVol tageSt at e.

-

7


ci scoEnvMonFanStat usChangeNot i f

Starting post processing ofci scoEnvMonFanSt at usChangeNot i f .

Normal A ci scoEnvMonFanSt at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonFanStat e.

-

ci scoEnvMonFanStat usChangeNot i f- shutdown

Fan status changed to"shutdown" for<description>. The systemshould be shutdownimmediately.

Critical A ci scoEnvMonFanSt at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonFanStat e.

-

ci scoEnvMonFanStat usChangeNot i f- cr i t i cal

Fan status changed to"critical" for <description>.

Critical A ci scoEnvMonFanSt at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonFanStat e.

-

ci scoEnvMonFanStat usChangeNot i f- mal f unct i on

Fan status changed to"notFunct i oni ng" for

<description>.

Major A ci scoEnvMonFanSt at usChangeNot i f is sent if there ischange in the state of a device being monitored by

ci scoEnvMonFanStat e.

-

ci scoEnvMonFanStat usChangeNot i f- war ni ng

Fan status changed to"warning" for <description>.

Warning A ci scoEnvMonFanSt at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonFanStat e.

-

ci scoEnvMonFanStat usChangeNot i f- normal

Fan status changed to\"normal\" for <description>.

Normal A ci scoEnvMonFanSt at usChangeNot i f is sent if there ischange in the state of a device being monitored byci scoEnvMonFanStat e.

-

In the following Table the presentation of traps specified in the CISCO-FLASH MIB module is described. The the status of the Flash operations.

Table 1-6: CISCO-FLASH MIB

Signal Message Text Severity Explanation

8


ci scoFl ashDevi ceI nsert edNot i f

Flash device <$2>inserted. Minimumpartition size <$1>

bytes.

Warning ci scoFl ashDevi ceI nser t edNot i f notification is sent whenever a removainserted.

Note: This trap may be enabled/ disabled via ci scoFl ashCf gDevI nsNot i fi s di sabl ed ( See Ci sco documentat i on)

ci scoFl ashDevi ceRemovedNot i f

Flash device <$2>removed.

Warning A ci scoFl ashDevi ceRemovedNot i f notification is sent whenever a removremoved.

Note: This trap may be enabled/ disabled via ci scoFl ashCf gDevRemNot i fi s di sabl ed ( See Ci sco documentat i on)

In the following Table the presentation of traps specified in the IF MIB moduler is described. The IF MIB specinterface sub-layers

Table 1-7: IF MIB

Signal MessageText Severity Explanation

l i nkDown Interfaceisdown.

Minor The i f OperSt atus object for one of the communication links is about to enter the down state

Note: This trap may be enabled/ disabled. By default, this object should have the value enabledinterfaces which do not operate on 'top' of any other interface (as defined in the i f StackTabl disabled (2) otherwise.

l i nkUp Interfaceis up.

Normal The i f OperSt atus object for one of the communication links left the down state.

Note: This trap may be enabled/ disabled. By default, this object should have the value enabledinterfaces which do not operate on 'top' of any other interface (as defined in the i f StackTabl disabled(2) otherwise.

9

1.3 Monitoring Interface Status

The status of the network interfaces are polled every minute by CMS the CMSLi nkMoni t or

program. The interfaces are polled with a snmpwal k with the following OID:

.1.3.6.1.2.1.2.2.1.8 (i nt er f aces. i f Tabl e. i f Ent r y. i f Oper St at us)

The interface description is collected as well with the following OID:

.1.3.6.1.2.1.2.2.1.2 (i nt er f aces. i f Tabl e. i f Ent r y. i f Descr )

The interface description is used in the message browser message text instead of theinterface number. The CMS software will issue an event when an interface change statefrom up to down or from down to up. The down to up for a particular interface will clear thedown event from the event browser.. The way the events are represented in the alarmbrowser is described in the following Table.

1.4 Interface Events

The following events are displayed when an interface state change has been detected:

Signal ComponentName

Message Text Severity Explanation User Action

Correlation

i f OperSt atus (up)

Li nkMoni tor Link up of interface: <t extualdescr i pt i on oft he i nter f ace>.

Normal An interfacechanged statefrom down toup.

None i f Oper Status (up) andi f Oper Status (down)

i f Oper

St atus (down)

Li nkMoni tor Link down of interface

: <t extualdescr i pt i on oft he i nter f ace>.

Major An interface

changed statefrom up todown.

Check the

interfaceinquestion

i f Oper Status

(up) andi f Oper Status (down)




10

2 Monitoring Connectivity Level

Please refer to the traps raised for interface cards described to the Sections 1.2, 1.1 and 1.4




11

3 Monitoring Process/ Application Level

3.1 Process/ Appl ication Level Alarms and Traps

In the following Tables the presentation of application alarms and traps in the alarm browseris described.

In the following Table the presentation of traps specified in the CISCO-CONFIG-MAN MIBmodule is described. This MIB represents a model of configuration data that exists in

various locations: running: in use by the running systemterminal: operator's mind or attached hardwarelocal : saved locally in NVRAM or flashremote: saved to some server on the network

Although some of the system functions that relate here can be used for general file storageand transfer, this MIB intends to include only such operations as clearly relate toconfiguration. Its primary emphasis is to track changes and saves of the runningconfiguration.

12

Table 3-1: CISCO-CONFIG-MAN MIB


ci s coConf i gManEvent Configuration change, Source of command :<$1>, Config datasource :<$2>, Config data destination :<$3>.

Warning Notification of a configuration man

In the following Table the presentation of traps specified in the CISCO-HSRP MIB module is described. This Mmonitor and configure the Cisco IOS proprietary Hot Standby Router Protocol (HSRP).

Table 3-2: CISCO-HSRP MIB


cHsr pSt ateChange_standby

HSRP state of group changed on <node>to standby. Minor Notification of a configuration management

cHsr pSt ateChange_act i ve

HSRP state of group changed on <node>to active. Normal Notification of a configuration management

In the following Table the presentation of traps specified in the CISCO-ISDN MIB module is described. This Mof the ISDN Interfaces on the routers.

Table 3-3: CISCO-ISDN MIB


demandNbrCal l I nf or mat i on

Neighbour successful call on <node>is cleared orcall attempt failed. Reason last call wasterminated :<$4>, Reason last call was torn down

::<$5>, NBR interface :<$1>.

Warning This trap/inform is sent to the manager whenever a suclears, or a failed call attempt is determined to have ulIn the event that call retry is active, then this is after al

have failed. However, only one such trap is sent in betsuccessful call attempts; subsequent call attempts res

15

In the following Table the presentation of traps specified in the CISCO-VLAN-MEMBERSHIP MIB module is dinformation on VLAN Membership Policy Servers used by a device and VLAN membership assignments of nodevice.

Table 3-6: CISCO-VLAN-MEMBERSHIP MIB


vmVmpsChange VLAN Membership Policy Serveris changed on <node>, IP Address of new VMPS :<$1>.

Warning A VMPS change notification is generated whenevervmVmpsChanges is incremented. The IP address of the newVMPS is sent."

NOTE: This trap can be disabled/ enabled viavmNot i f i cat i onsEnabl ed. See Cisco documentation

N

In the following Table the presentation of traps specified in the CISCO-VTP MIB module is described. This Mentities implementing the VTP protocol and VLAN management.

Table 3-7: CISCO-VTP MIB


vt pConf i gRevNumberError

VTP advertisement caused aconfiguration revision numbererror on <node>, device'sconfiguration revision number inthis domain :<$1>.

Minor A configuration revision number error notification signifies that adevice has incremented its vt pConf i gRevNumberEr r or s counter.

NOTE: This trap can be disabled/ enabled viavt pNot i f i cat i onsEnabl ed. See Cisco documentation

vt pConf i gDi gest Er ror

VTP advertisement received bydevice caused a configurationdigest error to occur on <$A>,device's configuration revisionnumber in this domain :<$1>.

Minor A configuration digest error notification signifies that a device hasincremented its vt pConf i gDi gest Err ors counter.

NOTE: All traps can be disabled/ enabled via appropriate read-write object. See Cisco documentation

vt pServerDi sabl ed

System cannot act as VTP Serveron <node>because the numberof defined VLANs is greater than<$2>, config revision number:<$1>.

Critical A VTP Server disabled notification is generated when the localsystem is no longer able to function as a VTP Server because thenumber of defined VLANs is greater than vt pMaxVl anSt or age.

17


vt pVl anRi ngNumber Conf l i ct

VTP ring number configurationconflict on <node>, VTP VLANring number: <$1>, interface :

<$2>.

Major A VTP ring number configuration conflict notification is generatedif, and only at the time when, a device learns of a conflict between:a) The ring number (vt pVl anPor t Local Segment ) being used

on a token ring segment attached to the port identified byi f I ndex, b) the VTP-obtained ringnumber (vt pVl anRi ngNumber ) for the VLAN identified byvt pVl anI ndex. When such a conflict occurs, the bridge port isput into an administrative down position until the conflict isresolved through local/network management intervention.

In the following Table the presentation of traps specified in the apIpv4 MIB module is described. This MIB moIPv4 objects.

Table 3-8: apIpv4 MIB (For ME 11501 Only)


apI pv4Redundancy Tr ap Redundancy state changed to <$2>, description: <$1>, IPaddress of redundant link: <$3>,IP address of redundant master:<$4>.

Warning This trap is generated when the state of Redundancy changes:State changes to: init or backUp.

apI pv4Redundancy Tr ap

" Critical This trap is generated when the state of Redundancy changes:State changes to: down.

apI pv4Redundancy Tr ap

' Normal This trap is generated when the state of Redundancy changes:State changes to: master.

In the following Table the presentation of traps specified in the apIpv4Redundancy MIB module is described. Cisco CSS IPv4 redundancy objects.

Table 3-9: apIpv4Redundancy MIB (For ME 11501 Only)

18


apI pv4RedundancySt ateTransi t i on

Virtual router state changed to<$4>, description: <$1>, Virtualrouter IP address: <$2>, Failure

reason: <$5>, Master Virtualrouter IP address: <$6>.

Critical Notification of a virtual router state change. Virtual router statechanged to: down.


" Warning Notification of a virtual router state change. Virtual router statechanged to: backup.


" Minor Notification of a virtual router state change. Virtual router statechanged to: idle.


' Normal Notification of a virtual router state change. Virtual router statechanged to: master or mast erRepor t erbackup.




19

4 Monitoring Quality Of Service Level

Monitoring at Quality of Service level applies to the overall quality and way of functioning ofthe application that is implemented by the ME.

4.1 Key Components

Quality of service monitoring is based on the key performance indicators (KPIs). The KPIsare provided by the IP-Backbone.

4.1.1 Host (Platform) KPIs

Please refer to section 5.

4.1.2 Services (Application) KPIs

Not defined.

Performance Indicators that can be provided by the ME are listed in Appendix A.

20

5 Monitoring On Overload Situations

Monitoring on overload situations applies to capacity constraints of the ME.

5.1 Key Components

Monitoring on overload situations is performed on the following components:

Hardware/ Interface

• CPU

5.2 Hardware/ Interface Capacity Alarms

Table 5-1: CISCO-PROCESS-MIB (cpmCPUTotal1minRev)

Signal Message Text Severity Explanation Correlation

CPU Threshold Alarm

Threshold violation: I PBackbone_CPU_MAXCPU , Value: <val ue>Threshold 60

Warning CPU LoadThreshold Crossing Alert

Reset atload 55

CPU Threshold

Alarm

Threshold violation: I PBackbone_CPU_MAX

CPU , Value: <val ue>Threshold 70

Minor CPU Load

Threshold Crossing Alert

Reset at

load 65

CPU Threshold Alarm


Major CPU LoadThreshold Crossing Alert

Reset atload 75

CPU Threshold Alarm


Critical CPU LoadThreshold Crossing Alert

Reset atload 85




21

6 Active Alarm Viewing for IP-Backbone

To always have the most actual status of an ME a framework exists to retrieve statusinformation from an ME. This framework is called Active Alarm Viewing (AAV).

When an ME gets disconnected from the CMS the actual status of the ME is not known bythe CMS. The ME could have sent traps which will not be received by the CMS. Such trapscould have been new traps indicating new malfunctioning of the ME, or could have beenclear traps clearing a previous event.

By means of AAV the current status of the ME can be retrieved. AAV is triggered by anodeUp event. AAV essentially retrieves the value of a fixed set of objects. For counters thevalue against pre-defined thresholds is measured. An alarm is raised when the threshold isexceeded.

For more information on the AAV scheme please refer to the CMS Operator Manual.

Using AAV for IP-Backbone the following objects are retrieved.

Table 6-1: AAV Counters for IP-Backbone

PI Description Thres.

apChass i sMgr Ext ModuleOpSt at us This object specifies the module's operational status within thechassis -

apI pv4RedundancySt ate

The current redundancy state -

apI pv4RedundancyVROper St at e

This object will be used as the current virtual router's state idle -the virtual router is idledown - the virtual router is downmaster - the virtual router is a masterbackup - the virtual router is a backupmast erRepor t erBkup - the virtual router is master but heldbackup by reporter.

-

apSvcState The current service state -

envMonFanStat e The current state of the fan being instrumented -

envMonSuppl ySt at e The current state of the power supply being instrumented -

envMonTempSt at e The current state of the test point being instrumented -

Hsr pGr pSt ate The current HSRP state of this group on this interface. -

envMonFanStat e The current state of the fan being instrumented -

envMonSuppl ySt at e The current state of the power supply being instrumented -

22

PI Description Thres.

i sdnLapdOper Stat us The operational status of this interface:

inactive all layers are inactivel1Active layer 1 is activated,layer 2 data link not establishedl2Active layer 1 is activated,layer 2 data link established.

-

ci uI f LoopStatus Current ISDN BRI integrated U interface Loop status andNT maintenance mode.

-

ci uI f St atus This object contains the operation status of the ISDNBRI integrated U interface

-

envMonVol t St at e The current state of the test point being instrumented -

st pxLoopI nconsi st encySt ate

Indicates whether the port on a particular SpanningTree instance is currently in loop-inconsistent

state or not.

-

st pxRootI nconsi s t encySt ate

Indicates whether the port on a particular SpanningTree instance is currently in root-inconsistentstate or not

-

chassi sSubModCPU This object specifies the average CPU utilization

CPU_Load > 90 CriticalCPU_Load > 80 MajorCPU_Load > 70 MinorCPU_Load <70 >0 Clear

√1

cpmCPUTotal1minRev The overall CPU busy percentage in the last 1 minuteperiod. This object deprecates the object cpmCPUTotal1minand increases the value range to (0...100).

√ (See Table5-1)

1 Only in AAV (CMS EXTM Threshold Templates)




23

Appendix A. Cisco IP-BB Standard Reports

For the IP Backbone the following reports are provided at installation:

Table 6-2: Cisco IP-BB Standard Reports

Reports Description

I PBB_cpu_usage_per _hour. r pt This report displays the average CPU usage per minuteof the last hour. If multiple CPU's are available data from

the separate CPU's is displayed.

I PBB_over al l _cpu_usage_per _day. r pt This report displays the average CPU usage per hour ofthe last day. If multiple CPU's are available data from theseparate CPU's is displayed.

I PBB_t otal _i n_out _oct ets_per _day. r pt This report displays the average number of octets (in andoutput) per hour of the last day. Data is summed for allthe interfaces for which the interface description contains"Ethernet".

I PBB_t otal _i n_out _oct ets_per _day_pr ompt _i nt erf ace. r pt

This report displays the average number of octets (in andoutput) per hour of the last day. This report allows theuser to select 4 interfaces. For selecting an interface onemust enter the name of the interface of interest, likeFastEthernet0/1. If less then four interfaces must be

selected, in the remainder selection boxes enter a dummystring like "abcd".

I PBB_t otal _i n_out _oct ets_per _hour . rpt This report displays the average number of octets (in andoutput) per minute of the last hour. Data is summed for allthe interfaces for which the interface description contains"Ethernet".

I PBB_t otal _i n_out _oct ets_per _hour _prompt_ i nter f ace. r pt

This report displays the average number of octets (in andoutput) per minute of the last hour. This report allows theuser to select 4 interfaces. For selecting an interface onemust enter the name of the interface of interest, likeFastEthernet0/1.If less then four interfaces must beselected, in the remainder selection boxes enter a dummystring like "abcd ".

I PBB_t otal _i p_st ati st i cs_per _day. r pt This report displays the average number of IPpackets per hour of the last day. The following four IPpackets are included: i pI nRecei ves , i pOut Request s,i pI nDi scar ded, i pOutDi scar ds.

I PBB_t otal _i p_st ati st i cs_per_hour . r pt This report displays the average number of IPpackets per minute of the last hour. The following four IPpackets are included: i pI nRecei ves , i pOut Request s,i pI nDi scar ded, i pOutDi scar ds.

I PBB_CSS_cpu_usage_per_day. r pt This report displays the average CPU usage per hour ofone day.

I PBB_CSS_cpu_usage_per _hour This report displays the average CPU usage per minuteof the last hour.




24

Reports Description

I PBB_t otal _i f _er r ors _di scards_per _day. rpt

This report displays the average per hour of errors anddiscards of the device in question of all its interfaces of

the last day.

I PBB_t otal _i f _er r ors _di scards_per _hour. rpt

This report displays the average per minute of errors anddiscards of the device in question of all its interfaces ofthe last hour.

25

Appendix B. Cisco Specific Performance Indicators

Following host related QoS PIs are provided by the ME. In the Tables it is indicated whetherfor a specific object a report is prepared and/or a TCA threshold is defined.

Table 6-3: ARROWPOINT-CHASSISMGREXT-MIB (chassismgrext.mib)

PI Description Prep.Rep.

Thres.

apChassi sMgrExt SubModul eCPU

This object specifies the average CPU utilization.

CPU_Load > 90 CriticalCPU_Load > 80 MajorCPU_Load > 70 MinorCPU_Load <70 >0 Clear

√ √2

Table 6-4: CISCO-PROCESS-MIB


Thres.

cpmCPUTot al 1mi nRev The overall CPU busy percentage in the last 1 minuteperiod. This object deprecates the object

cpmCPUTotal1min and increases the value range to(0...100).

√ √ See Table

5-1)

2 Only in AAV (CMS EXTM Threshold Templates)




26

Appendix C. Application Performance Indicators

Following application related QoS PIs are provided by the ME.

Table 6-5: IP-MIB


Thres.

i pI nRecei ves The total number of input datagrams received from interfaces,

including those received in error

√ -

i pI nDi scar ds The number of input IP datagrams for which no problems wereencountered to prevent their continued processing, but which werediscarded (e.g., for lack of buffer space). Note that this counterdoes not include any datagrams discarded while awaiting re-assembly

√ -

i pOut Request s The total number of IP datagrams which local IP user-protocols(including ICMP) supplied to IP in requests for transmission. Notethat this counter does not include any datagrams counted ini pFor wDat agr ams .

√ -

i pOut Di scards The number of output IP datagrams for which no problem wasencountered to prevent their transmission to their destination, butwhich were discarded (e.g., for lack of buffer space). Note that this

counter would include datagrams counted in i pFor wDat agr ams ifany such packets met this (discretionary) discard criterion

√ -

Table 6-6: IF-MIB


Thres.

i f I nOct ets The total number of octets received on the interface, includingframing characters. Discontinuities in the value of this counter canoccur at re-initialization of the management system, and at othertimes as indicated by the value ofi f Count erDi scont i nui t yTi me.

√ -

i f I nDi scar ds The number of inbound packets which were chosen to bediscarded even though no errors had been detected to preventtheir being deliverable to a higher-layer protocol. One possiblereason for discarding such a packet could be to free up bufferspace. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times asindicated by the value of i f Count erDi sconti nui t yTi me.

√ -

i f I nEr r or s For packet-oriented interfaces, the number of inbound packets thatcontained errors preventing them from being deliverable to ahigher-layer protocol. For character- oriented or fixed-lengthinterfaces, the number of inbound transmission units thatcontained errors preventing them from being deliverable to ahigher-layer protocol. Discontinuities in the value of this countercan occur at re-initialization of the management system, and atother times as indicated by the value ofi f Count er Di scont i nui t yTi me.

√ -




27


Thres.

i f OutOct ets The total number of octets transmitted out of the interface,

including framing characters. Discontinuities in the value of thiscounter can occur at re-initialization of the management system,and at other times as indicated by the value ofi f Count er Di scont i nui t yTi me.

√ -

i f OutDi scards The number of outbound packets which were chosen to bediscarded even though no errors had been detected to preventtheir being transmitted. One possible reason for discarding such apacket could be to free up buffer space. Discontinuities in thevalue of this counter can occur at re-initialization of themanagement system, and at other times as indicated by the valueof i f Count er Di scont i nui t yTi me.

√ -

i f Out Er r ors For packet-oriented interfaces, the number of outbound packetsthat could not be transmitted because of errors. For character-oriented or fixed-length interfaces, the number of outbound

transmission units that could not be transmitted because of errors.Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times asindicated by the value of i f Count erDi sconti nui t yTi me.

√ -

i f Descr A textual string containing information about the interface. Thisstring should include the name of the manufacturer, the productname and the version of the interface hardware/software.

√3 -

3

Not to be used in templates.The ifDescr is solely used in reports to display a textual representation of an interface instead of a number.




28

Abbreviations

CMS Central Management Station

ME Managed Element

MIB Management Information Base

KPI Key Performance Indicator

PI Performance Indicator

QoS Quality of Service

TCA Threshold Crossing Alert




29

References

CMS Operator manual Acision, November 2006

Cisco IP Transfer Point Cisco documentation



Version History

Version Status Date Details of Changes Autho r(s)

1.0 DRAFT September 2006 Initial version Harrie Buiting

1.1 PROPOSED October 2006 TW review Sibel Köksal

1.2 DRAFT March 2007 PM Review Harrie Buiting

2.1 PROPOSED May 2007 PM Review Harrie Buiting

2.2 PROPOSED June 2007 Acision Re-branding Sibel Köksal

2.3 PROPOSED July 2007 Add Cisco 3750 & 2811 Harrie Buiting

2.4 PROPOSED August 2007 Added supported reportsdescription

Harrie Buiting

2.5 PROPOSED August 2007 TW review Sibel Köksal

Approval

Version Date Appro ved by Signature

IP Backbone Alarms

Documents

Transcript of IP Backbone Alarms