fg

Passport 6400, 7400, 15000, 20000

Alarms

241-5701-500

Passport 6400, 7400, 15000, 20000

Alarms

Publication: 241-5701-500Document status: StandardDocument version: 4.1S1Document date: February 2002

Copyright © 2002 Nortel Networks.All Rights Reserved.

Printed in Canada

NORTEL NETWORKS, the globemark design, the NORTEL NETWORKS corporate logo, DPN, DPN-100, andPASSPORT are trademarks of Nortel Networks.Advanced Peer-to-Peer Networking and APPN are trademarks of International Business Machines Corporation.VT100 is a trademark of Digital Equipment Corporation.

5

0,

Publication history

February 20024.1S1 StandardGeneral availability. Contains information on Passport 6400, 7400, 150020000 for the PCR 4.1 GA release.

Passport 6400, 7400, 15000, 20000 Alarms 4.1S1

6 Publication history

241-5701-500 4.1S1

7

Contents

About this document 11Who should read this document and why 11What you need to know 11How this document is organized 11Text conventions 12Related documents 13

Passport references 13ITU-T references 14

How to get more help 14

Chapter 1Alarms overview 15Passport alarm philosophy 15Alarm strategy 16

Alarms and customer identifiers 16What causes alarms 16How are alarms cleared? 17

What are state change notifications? 17How to interpret alarm information 18

Chapter 2Interpreting alarms 19Related documents 19Alarm screens 19

Alarm format on a text interface device 20Alarm format on the Alarm Display 20Example of an alarm on a text interface device 21Example of an alarm on the Alarm Display 22

Alarm fields 22


8 Contents

Alarm index 26Severity 27OSI states 27OSI status 29Summary of Passport OSI state and status attributes 32

Chapter 3Interpreting alarms in this book 35Related documents 35Software and engineering alarms 35

Internal software alarms 36Engineering alarms 36

Alarm format 36Alarm number 36Component field 40Severity field 40Status field 41Details field 42Remedial action field 42

Chapter 4Alarms 43

AppendixAlarm causes 885

241-5701-500 4.1S1

Contents 9


List of figures

Figure 1 Alarm format on a text interface device 20Figure 2 Alarm format using the Alarm Display tool 21Figure 3 Alarm on a text interface device 22Figure 4 Alarm on the Alarm Display tool 22

10 Contents

241-5701-500 4.1S1

List of tables

Table 1 Alarm fields of the text interface 23Table 2 OSI states and status attributes 33Table 3 Passport IndexGroups 37Table 4 Alarm causes 885

11

s.

400,

ill

,

About this document

This document describes Passport 6400, 7400, 15000, and 20000 alarm

The following topics are discussed in this section:

• “Who should read this document and why” (page 11)

• “What you need to know” (page 11)

• “How this document is organized” (page 11)

• “Text conventions” (page 12)

• “Related documents” (page 13)

• “How to get more help” (page 14)

Who should read this document and whyThis guide is for persons who operate and maintain the Passport 6400, 715000, and 20000 nodes.

What you need to knowFamiliarity with fundamental data communications concepts and terms wbe helpful in understanding the information in this document.

How this document is organized241-5701-500Passport 6400, 7400, 15000, 20000 Alarms contains thefollowing sections:

• “Alarms overview” (page 15) discusses the Passport alarm behaviorpotential causes of alarms and how they are cleared. State changenotifications (SCN) are also described in this chapter.


12 About this document

tois

s.

e

t or

ype

f a

and

• “Interpreting alarms” (page 19) explains how to interpret Passportalarms as they appear on your text interface device (for example, aVT100 terminal).

• “Interpreting alarms in this book” (page 35) provides details on how interpret the information provided in individual alarm descriptions in thbook.

• “Alarms” (page 43) contains a sequential listing of all Passport alarmEach alarm description provides details on the condition(s) thatgenerated the alarm, and the remedial action to be taken.

• “Alarm causes” (page 885) contains a listing of possible values for thcause field in a Passport alarm.

Text conventionsThis document uses the following text conventions:

• nonproportional spaced plain type

Nonproportional spaced plain type represents system generated textext that appears on your screen.

• nonproportional spaced bold type

Nonproportional spaced bold type represents words that you should tor that you should select on the screen.

• italics

Statements that appear in italics in a procedure explain the results oparticular step and appear immediately following the step.

Words that appear in italics in text are for naming.

• [optional_parameter ]

Words in square brackets represent optional parameters. The commcan be entered with or without the words in the square brackets.

241-5701-500 4.1S1

About this document 13

with

h thees)

o

ted

rting( / )int,

de:

is

• <general_term >

Words in angle brackets represent variables which are to be replacedspecific values.

• UPPERCASE,lowercase

Passport commands are not case-sensitive and do not have to matccommands and parameters exactly as shown in this document, withexception of string options values (for example, file and directory namand string attribute values.

• |

This symbol separates items from which you may select one; forexample, ON|OFF indicates that you may specify ON or OFF. If you dnot make a choice, a default ON is assumed.

• ...

Three dots in a command indicate that the parameter may be repeamore than once in succession.

The term absolute pathname refers to the full specification of a path stafrom the root directory. Absolute pathnames always begin with the slashsymbol. A relative pathname takes the current directory as its starting poand starts with any alphanumeric character (other than /).

Related documentsThe following sections list documents related to the information in this gui

• “Passport references” (page 13)

• “ITU-T references” (page 14)

Passport referencesRefer to the following Passport NTPs in conjunction with the material in thbook:

• 241-5701-005Passport 7400, 15000, 20000 List of Terms

• 241-5701-030Passport 7400, 15000, 20000 Overview


14 About this document

al

st

s

the

• 241-7401-210Passport 7400 Hardware Installation Guide

• 241-1501-210Passport 15000, 20000 Hardware Installation Guide

• 241-7401-215Passport 7400 Hardware Maintenance Guide

• 241-1501-215Passport 15000, 20000 Hardware Maintenance Guide

• 241-5701-520Passport 7400, 15000, 20000 Troubleshooting Guide

• 241-5701-600Passport 7400, 15000, 20000 Configuration Guide

• 241-5701-060Passport 7400, 15000, 20000 Components

ITU-T referencesThe following ITU-T references provide information related to the materiin this book:

• ITU-T Recommendation X.731, Information technology - Open SystemInterconnection - Systems Management - Part 2: State managemenfunction

• ITU-T Recommendation X.733, Information technology - Open SystemInterconnection - Systems Management - Part 4: Alarm reportingfunction

How to get more helpFor information on training, problem reporting, and technical support, see“Nortel Networks support services” section in the product overviewdocument.

241-5701-500 4.1S1

15

pter

nd

usly, a

re

l

Chapter 1Alarms overview

This chapter provides details on Passport alarms. After reading this chayou will understand:

• general alarm philosophy

• which conditions cause alarms

• what causes alarms to be cleared

The final section of this chapter is a pointer to other chapters in the book, ais intended to help you to find information quickly and easily.

Passport alarm philosophyPassport provides a method for components in the system to asynchronosignal events or alarms to an external management device (for exampleVT100 terminal or a network management workstation).

Passport alarms are based on an event-driven system (that is, alarms agenerated when certain events occur).

Common alarm situations include the following:

• a failure or fault occurs (this is asetalarm and is discussed in more detaion “Status field” (page 41))

• a fault or failure condition has been fixed (this is aclear alarm and isdiscussed in more detail on “Status field” (page 41))


16 Chapter 1 Alarms overview

d”

rm

thatarm

ot

ser

• cases where conditions are transient or cannot be repaired (amessagealarm may appear to inform you of the condition). Refer to “Status fiel(page 41) for more information on message alarms.

Alarm strategyPassport alarms are designed to minimize the occurrence of multiple alageneration in the event of a failure or error condition. In general, only thecomponent that fails or detects the failure generates the alarm, thuspreventing the generation of an entire chain of alarms from componentsassociated with the failed component.

Note: There are some cases when a fault or failure results in thegeneration of more than one alarm.

Using state change notifications, the component that fails notifies othercomponents above and below it on the component hierarchy to indicateit is no longer in service. The related components do not generate an albecause they have been notified of the change of state.

When the component is back in service, it clears its previous alarm andnotifies its subcomponents (as well as other components that may bedependent on it) of its new state.

Alarms and customer identifiersAll Passport alarms contain a customer identifier (CID). The CID does nappear on the interface, but is essential in determining which alarms aredisplayed to which users. Alarms are displayed based on the CID of the uId.

What causes alarmsGenerally speaking, alarms occur in the following situations:

• degradation/quality of service conditions (for example, the onset ofsevere congestion)

• processing errors (for example, protocol errors)

• engineering alarms (for example, insufficient memory for a requiredcomponent)

241-5701-500 4.1S1

Chapter 1 Alarms overview 17

in

ses,e

e

y.

mayns

ing

rk

• out-of-service conditions (for example, hardware failures such as afunctional processor or power supply failure)

• software errors (that is, an unexpected condition has been detectedsoftware)

• administrative conditions (such as using the lock command totemporarily lock a component)

• security violations (for example, successive invalid logon attempts)

How are alarms cleared?Clearing an alarm may involve taking one of several actions, or in some cano action at all. It may require that you act immediately to a condition in thnetwork, call for help, change a piece of hardware or simply wait until thcondition has cleared itself.

Note: You can report an alarm to Nortel Networks by opening acustomer service request (CSR).

The following list describes some general methods for clearing alarms:

• issuing operator commands (refer to NTP 241-5701-045Passport 7400,15000, 20000 Management System User Interface Guide for details onissuing common commands)

Note: Alarms can also be cleared using the Integrated Alarm DisplaHowever, it clears only the alarm logs in Preside Multiservice DataManager and not those at the Passport.

• replacing hardware (for example, a control processor)

• taking no action—in some cases such as threshold alarms, no actionbe required on the part of the user—the alarm clears itself if conditioreturn to normal

Note: These are only general remedial actions. For specifics on clearindividual alarms, refer to Chapter “Alarms” (page 43).

What are state change notifications?State change notifications (SCN) are intended primarily for use by netwomanagement systems for determining the impact of a certain failure.


18 Chapter 1 Alarms overview

lar

s,.

itas it

aceong

When the OSI operational state or the OSI procedural status of a particucomponent changes, the system automatically generates an SCN. Thisinformation is used to update the network model.

For more information on OSI operational state and OSI procedural staturefer to “Operational state” (page 28) and “Procedural status” (page 30),

How to interpret alarm informationDepending on your requirements, you may want to interpret an alarm asappears on the text interface, in Preside Multiservice Data Manager, or is documented in this book.

For information on interpreting alarms as they appear on your text interfdevice, refer to Chapter “Interpreting alarms” (page 19). For informationhow to read the specific alarms in this book, refer to Chapter “Interpretinalarms in this book” (page 35).

For information on specific alarms, refer to Chapter “Alarms” (page 43).

241-5701-500 4.1S1

19

textlnetrms

nge

ithevice

Chapter 2Interpreting alarms

This chapter will help you interpret Passport alarms as they appear on ainterface device (that is, an ASCII-based terminal such as a VT100 or a tesession). Included is an example to help you understand the fields and tediscussed in the chapter.

Familiarity with fundamental communications concepts will be helpful inunderstanding the information in this chapter and subsequent chapters.

Note: The format and contents of the user interface are subject to chaover time.

Related documentsRefer to the following documents for additional information:

• 241-5701-005Passport 7400, 15000, 20000 List of Terms





Alarm screensThe sample screens and paragraphs in this section will familiarize you wthe appearance of Passport alarms as they appear on a text interface dand the Alarm Display (AD) tool.


20 Chapter 2 Interpreting alarms

at

eger

The section “Alarm fields” (page 22) provides a description of the fields thappear in the alarm formats shown below.

Alarm format on a text interface deviceThe figure “Alarm format on a text interface device” (page 20) shows thePassport alarm format used on a text interface device.

Figure 1Alarm format on a text interface device

Alarm format on the Alarm DisplayThe figure “Alarm format using the Alarm Display tool” (page 21) shows thPassport alarm format used on the Nortel Preside Multiservice Data ManaAlarm Display (AD) tool.

<Component name>; <date> <time>

ADMIN: <admin> OPER: <oper> USAGE: <usage>AVAIL: <avail> PROC: <proc> CNTRL: <control>ALARM: <alarms> STBY <stdby> UNKNW: <unknown>Id: <notifId> Rel: [<relatedComp1>; <relatedComp2>; ...][Com: <commentData>][Op: <operatorData>]Int: <process id>; <filename>; <linenumber>; <version>

<status> <severity> <type> <cause> <alarm index>

[<internalData>]

PPT 0001 001 AA

241-5701-500 4.1S1

Chapter 2 Interpreting alarms 21

of

Figure 2Alarm format using the Alarm Display tool

The possible values for theRAW state are:

insv (in service)

oos (out of service)

trb (troubled)

unk (unknown)

nex (non-existent)

Example of an alarm on a text interface deviceThe figure “Alarm on a text interface device” (page 22) shows an examplean alarm as it would appear on a text interface device.

<severity> <status> <NTP index> <date> <time> <component name>ID: <notifId> TYPE: <type> CAUSE: <cause>[CO: <commentData>][OP: <operatorData>][EX: <internalData>]RAW: <raw> ADMIN: <admin> OPER: <oper> USAGE: <usage>

[REL COMP: <Related Component name>] <--one line per related componentINT: <process id>; <filename>; <line number>; <version>

AVAIL: <avail> PROC:<proc> CNTRL: <control>ALARM: <alarm> STBY:<stdby> UNKNW: <unknown>

PPT 0002 001 AA



le

ngThes

Figure 3Alarm on a text interface device

Example of an alarm on the Alarm DisplayThe figure “Alarm on the Alarm Display tool” (page 22) shows an exampof an alarm as it would appear on the Alarm Display (AD) for Passport.

Figure 4Alarm on the Alarm Display tool

Alarm fieldsAlarm fields are described below in table format to assist you in interpretialarms. The fields are listed in the order they appear on the text interface.third column of the table “Alarm fields of the text interface” (page 23) give

Shelf Card/1; 1993-05-11 18:30:08.99warning equipment processorProblemADMIN: unlocked OPER: disabled USAGE: idleAVAIL: dependency PROC: initializing CNTRL: SubjectToTestALARM: alrmOutstdng STBY: coldst UNKNW: falseId: 03 Rel: Shelf Card/13Com: This is a hypothetical alarm.Op: 596F7572206E616D65206973206D7564Int: 1/9/215; dcsTESTApRecord.cc;255; user1.23.7

CLR 11010001

PPT 0003 001 AA

WARNING SET 70116501 1995-11-23 20:39:52 EM/NODEY2C5 LP/2 X21/1ID: 02000001 TYPE: processing CAUSE: configurationErrorCO: Termination switch setting does not match provisioned. Check switch setting or provisioned data (lineTerminationRequired).RAW: oos ADMIN:unlocked OPER:disabled USAGE:idle AVAIL: PROC: CNTRL: ALARM: STBY: notSet UNKNW:INT: 2/0/3/32550;PmsHwProcessHandler_Actor.cc;598;;

PPT 0004 001 AA

241-5701-500 4.1S1


ay

tion

er

an example of each field taken from the figure “Alarm on a text interfacedevice” (page 22). Column 4 states whether the field is mandatory oroptional.

A mandatory field must be present in the display, while optional fields mnot be present.

Some fields are for internal use only and are noted as such in the descripcolumn of the table “Alarm fields of the text interface” (page 23).

Where necessary, subsections following the table describe fields in furthdetail (for example, the Alarm index field).

Table 1Alarm fields of the text interface

Field Description Example from “Alarmon a text interfacedevice” (page 22)

M/O

component name The full name of the component needingrepair, or detecting the fault. Thecomponent name can be used forhierarchically clearing alarms for itssubcomponents (since the subcomponentname is derived from the componentname).

Shelf Card/1 M

date and time The date and time the alarm was issued. 1993-05-11 18:30:08.99 M

status Indicates the status of an alarm. Thepossible values for this field includemessage (MSG), set (SET) or clear (CLR).

CLR M

severity Indicates the severity of the alarm. Thevalue will be one of, critical, major, minor,warning, indeterminate, cleared. See(“Severity field” (page 40))

For further details, refer to ITU-TRecommendation X.733.

warning M

(Sheet 1 of 4)



type This is a general explanation of why thealarm was generated. Possible values forthis field include communications, qualityof service, processing, equipment, orenvironmental, security, operator, debug,or unknown.

For further details, refer to “Type”(page 26).

equipment M

cause This provides another level of detail of whythe alarm was generated. It is informationgiven in addition to the general explanationgiven in the Type field.

For further details, refer to Appendix“Alarm causes” (page 885).

processorProblem M

Alarm index An eight-digit number which is the principalalarm identifier. It consists of anIndexGroup and SubIndex. For furtherdetails see “Alarm index” (page 26)

11010001 M

ADMIN, OPER,USAGE

These fields describe the possible OSIstates, that is, the administrative state,operational state, and usage state of thecomponent.

For information on OSI states, refer to “OSIstates” (page 27).

For component-specific OSI statecombinations, refer to the appropriateAppendix in 241-5701-520 Passport 7400,15000, 20000 Troubleshooting Guide.Some of this information is also included inthe user guides for the various services.

unlocked/disabled/idle M

Table 1 (continued)Alarm fields of the text interface


M/O

(Sheet 2 of 4)

241-5701-500 4.1S1


AVAIL, PROC,CNTRL, ALARM,STBY, UNKNW

These fields describe OSI status. Includedin this group are availability status,procedural status, control status, alarmstatus, standby status, and unknownstatus.

For information on OSI status, refer to “OSIstatus” (page 29).

dependency/initializing/subjectToTest/alrmOutstdng/coldSt/false

M

Id The system automatically inserts thenotification Identifier. Notificationidentifiers are unique within eachPassport.

03 M

Rel A list of known related components.Usually it is only the supporting hardwarename that the affected component resideson. For example the LP and possibly thecard number. This field may appear asblank if there are no related components.

Shelf Card/13 O

Com Comment data is additional data in ASCIIformat. It provides the operator with extrainformation in the form of a comment.Thetext appearing in this field is self-explanatory.

This is a hypotheticalalarm.

O

Op Operator data is hex-format data that anoperator can use for additional information.If operator data exists, it is explained in the“details” section of the individual alarms inChapter “Alarms” (page 43).

596F7572206E616... O

Int Internal data is additional information inHex-format that can be used by internalsupport personnel.

Contained within this field are theprocessId (Pid), filename, linenumber andversion.

1/9/215;dcsTESTApRecord.cc;255; user1.23.7

O



M/O

(Sheet 3 of 4)



e

r

n

ror

Type

The following explains the values that can appear in the Type field:

• communications alarm indicates a problem related to communication(for example protocol errors)

• qualityOfService alarm indicates a problem related to quality of servic(for example crossing thresholds)

• processing alarm indicates a problem related to processing data (forexample a memory problem)

• equipment alarm indicates a problem with the physical equipment (foexample a processor failure)

• security alarm indicates a problem related to security (for example aunauthorized access)

• operator alarm indicates that some event was caused by operator er(for example locking a component)

• debug alarm indicates that the event was for debugging purposes

• unknown alarm indicates that reason for the event is not known

Alarm indexThe Alarm index consists of eight BCD digits. The first four digits arecollectively known as the IndexGroup and the remaining four digits areknown as the SubIndex.

processId Used internally 1/9/215 O

filename Used internally dcsTESTApRecord.cc O

linenumber Used internally 255 O

version Used internally user1.23.7 O



M/O

(Sheet 4 of 4)

241-5701-500 4.1S1


tive

their

ds.oted.

rt 2:

The IndexGroup is a four-digit number representing logical groupings ofalarms. For example, it may represent:

• an application service

• an internal subsystem

• a component type

• a component class

• a software module

• a similarity of event

For a complete list of all alarm IndexGroups, refer to the table “PassportIndexGroups” (page 37).

The SubIndex is a four-digit number that has significance only within theIndexGroup.

SeverityFor a description of the severity level associated with this field, refer to“Severity field” (page 40).

This appendix provides information on OSI component states and statusattributes for Passport. In particular it provides the following:

• definitions of an operational state, a usage state, and an administrastate

• a list of OSI status attributes and possible values

• a table that summarizes all possible state and status attributes and values

OSI statesPassport uses component state definitions according to the OSI standarOSI states mays be exhibited by any application. Components that do nprovide any behavior do not require any component state variables defin

Further details are found in ITU-T Recommendation X.731, Informationtechnology - Open Systems Interconnection - Systems Management - PaState management function.



s

not

can, byth ae to

or

ly innal

o

y to

user

A component has three high-level state variables: anoperational state, ausage state, and anadministrative state. These states are the primary factoraffecting the management state of a component.

Operational stateThe operational state of a component indicates whether the resource isphysically installed and operational.

Not all types of components exhibit all possible states. For example, acomponent that has no visible dependencies on other components mayshow thedisabled operational state.

You cannot cause a component to change from one state to another. Youhowever, gather information about the operational state of a componentusing the appropriate operator command. Specific events associated wicomponent can cause specific transitions from one operational state valuanother.

The two possible values for this attribute are:

• enabled—the component is partially or fully operable and available fuse

• disabled—the resource is totally inoperable and unable to provideservice

Usage stateThe usage state of a component indicates whether the resource is activeuse at a specific time, and if so, whether it has spare capacity for additiousers.

The usage state can have one of the following values:

• idle—the component is not currently in use

• active—the component is in use, and has sufficient spare capacity tprovide for additional users simultaneously

• busy—the component is in use, but it has no spare operating capacitprovide for additional users at this instant. This is also used forcomponents that have only one user. A component that has only onetypically exhibits an idle or busy state value.

241-5701-500 4.1S1


t.

gem

m

totingay

rs

its

he

thin

are:

Note: Not all usage state values are applicable to every componen

Administrative stateAdministration specifies the permission to use or prohibition against usinthe resource. These permissions are imposed typically through the SystAdministrator.

The administration state can have one of the following values:

• locked—indicates that the component is administratively prohibited froperforming services for its users

• shutting down—use of the resource (or component is administrativelypermitted to existing instances only. While the system remains in theshutting down state, the manager may at any time cause the object revert to the unlocked state. This simply provides a state when shutdown a component (or service)—existing users of the component mstill be serviced, but any new users are denied the resource that thecomponent provides.

• unlocked—the component is permitted to perform services for its use

Note 1: The administration of a component operates independently ofoperability.

Note 2: Some classes of components may exhibit only a subset of tpossible administrative state values.

OSI statusIn addition to the three state attributes, six status attributes also exist wiOSI. The primary function of these attributes is to provide additionalinformation about a component’s operability and usage. These attributes

• alarm status

• procedural status

• availability status

• control status

• standby status

• unknown status



sible

n be

n be

ted

ted

e not

s

sible

nill

m

or

ingbled.

Alarm statusPassport implements this attribute as a read-only set-valued attribute. Posvalues for the alarms status attribute are:

• empty set—the attribute value appears as empty.

• under repair—the resource is being repaired. The operational state caeither enabled or disabled.

• critical—one or more critical alarms indicating a fault or failure havebeen detected and have not been cleared. The operational state caeither enabled or disabled.

• major—one or more major alarms indicating a fault have been detecand have not been cleared. These faults can be disabling.

• minor—one or more minor alarms indicating a fault, have been detecand have not been cleared. These faults can be disabling.

• alarm outstanding—one or more alarms have been detected and havbeen cleared. The condition may or may not be disabling. If theoperational state is enabled, additional component-specific attributemay indicate the nature and cause of the condition.

Procedural statusPassport implements this attribute as a read-only set-valued attribute. Posvalues for the alarms status attribute are:


• initialization required—the resource requires initialization before it caperform normal function and this has not been initiated. The operator winitiate it. The operational state is disabled.

• not initialized—the resource requires initialization before it can perfornormal functions and this has not been initiated. The resource willinitialize itself autonomously. The operational state is either disabledenabled.

• reporting—the resource has completed some operation and is notifythe results (for example, a test process) The operational state is ena

241-5701-500 4.1S1


es

twolytus

tiveing

ng.

oed.

ls, It

ource.

meains

ute.

• terminating—the resource is in termination phase. If the resource donot initialize itself autonomously, the operational state is disabled;otherwise, it can be either disabled or enabled.

Availability statusPassport implements this attribute as a read-only set-valued attribute. Themost common values are failed and dependency, both of which only appwhen the operational state is Disabled. Possible values for availability staare:


• in test—the resource is undergoing a test procedure. If the administrastate is locked or shutting down, normal users are precluded from usit and the control status is set to reserved for test.

• failed—the resource has an internal fault that prevents it from operatiThe operational state is disabled.

• power off—the resource requires power.

• off line—the resource requires a routine operation to be performed tplace it on-line and make it available. The operational state is disabl

• off duty—the resource has been made inactive by an internal controprocess in accordance with a time schedule. Under normal conditionshould come back into operation through the same mechanism. Theoperational state can be either enabled or disabled.

• dependency—the resource cannot operate because some other reson which it depends is unavailable. The operational state is disabled

• degraded—the service available from the resource is degraded in sorespect such as speed or operating capacity. However, the service remavailable for service. The operational state is enabled.

• not installed—the resource is not present or is incomplete.

• log full—indicates a log full condition as specified by ITU-TRecommendation X.735. Passport components do not use this attrib



he

y be

thee,

e it

The

eply.

ke

s

d bye ishe

Control statusPassport implements this attribute as a read-only, set-valued attribute. Tcontrol status may have the following values:


• subject to test—the resource is available to normal users but tests maconducted simultaneously, causing it to possibly exhibit unusualbehavior to users.

• part of services locked—a manager has restricted a particular part ofservice from users. The administrative state is unlocked (for examplincoming service barred).

• reserved for test—the resource is administratively unavailable becausis undergoing a test procedure. The administrative state is locked.

• suspended—service is administratively suspended to users.

Standby statusPassport implements this attribute as a read-only, single-valued attribute.standby status may have one of the following values:

• empty—this is a non-standard value which is used to indicate that thcomponent does not use the attribute or none of the other values ap

• hot standby—not providing service but operating in sync mode to taover immediately status.

• cold standby—not providing service and not synchronized. It requiresome initialization activity.

• providing service—the backup resource is providing service.

Unknown statusThis attribute is used to indicate that the state of the resource representethe managed object is unknown. When the unknown status attribute valutrue, the value of the state attributes may not reflect the actual state of tresource.

Summary of Passport OSI state and status attributesThe following table provides a summary of Passport state and statusattributes.

241-5701-500 4.1S1


Table 2OSI states and status attributes

Attribute Values

Operational state enabled, disabled

Usage state idle, active, busy

Administrative state unlocked, locked, shutting down

Alarm status empty, under repair, critical, major, minor, alarm,outstanding

Procedural status empty, initialization required, not initialized,initializing, reporting, terminating

Availability status empty, in text, failed, power off, off line, off duty,dependency, degraded, not installed, log full

Control status empty, subject to test, part of services locked,reserved for test, suspended.

Standby status not set, hot standby, cold standby, providingservice

Unknown status true or false



241-5701-500 4.1S1

35

s

r.

eferwell

ringby

0”.

Chapter 3Interpreting alarms in this book

After reading this chapter you will be able to read and interpret the alarmdocumented in this guide.

Familiarity with fundamental communications concepts will be helpful inunderstanding the information in this chapter and the proceeding chapte

In some cases, for a better understanding of the alarms in this book, we ryou to other documents, some in the Passport documentation library, asas some external documents.

Related documentsSee the following documents for additional information:





Software and engineering alarmsPassport “reuses” certain alarm indexes to indicate software or engineefault or error conditions. In these cases the system indicates the conditiona common alarm code. All common alarm codes have initial digits of “000


36 Chapter 3 Interpreting alarms in this book

002,ent.dial

apckas

in

will

rm.

Internal software alarmsFor internal software errors, the common alarms are 0000 9000, 0000 9and 0000 9003. The specifics of the alarm vary depending on the componInternal details appear on the text interface as part of the alarm. The remeaction is always to open a service request (SR).

Engineering alarmsFor engineering alarms there are two common alarms. For threshold/hememory availability, the alarm is 0000 3001. For threshold message bloavailability, the alarm is 0000 3002. Details appear on the text interface part of the alarm.

The specifics of the alarm vary depending on the component.

Alarm formatAlarm information in this document is divided into seven fields as shownthe following example:

xxxx xxxx

Component Severity StatusThe full component name One of: One of:or a statement critical, message,indicating that it is major, set, cleara common alarm minor, or set/clear:which applies to all warning,components. indeterminate

or cleared

LegendDescribes the possible values for anything in brackets in the component field.

DetailsProvides details on the cause of the alarm, and where applicable, the impacts the alarmhave on the system or on other components.

Remedial actionGives the suggested operator action for correcting the failure (if possible).

Alarm numberEach alarm heading consists of an eight-digit number identifying the ala

241-5701-500 4.1S1

Chapter 3 Interpreting alarms in this book 37

bys

a

of

t

in

.

The alarm number is the principal alarm identifier and provides the meanswhich you can find your alarm quickly. Alarms appear sequentially in thibook for easy access.

The alarm is made up of an Index Group (the first group of four digits) andSubIndex (the second group of four digits). This is also referred to as theNTPIndex.

• The IndexGroup is a four-digit number representing logical groupingsalarms. For example, it may represent:

— an application service

— an internal subsystem

— a component type

— a component class

— a software module

— a similarity of event

For a complete list of all alarm IndexGroups, refer to table “PassporIndexGroups” (page 37).

• The SubIndex is a four-digit number which has significance only withthe IndexGroup.

IndexGroupsThe following table provides a complete list of all Passport IndexGroups

Table 3Passport IndexGroups

IndexGroup Group

0000 Common alarms

0999 Preside Multiservice Data Manager-generated alarms

For information on Preside Multiservice Data Manager-generated alarms, see 241-6001-501 Preside MDM ProxyAlarms Reference Guide.

1100 Router IP information

(Sheet 1 of 4)



7000 Component administration system

7001 Virtual circuit

7002 Bus control system

7003 Data collection system

7004 Module interconnection link

7005 Module interconnection transport

7006 Network management interface system

7007 Frame relay service

7008 File system

7009 Routing

7011 Port management system

7012 Processor control system

7013 Traffic management

7014 Memory management

7015 Network time synchronization

7016 Destination call routing

7017 Network clock synchronization

7018 Path Oriented Routing Service

7019 Voice Transparent Data Service, including BitTransparent Data Service and HDLC Transparent DataService

7020 Virtual router

7021 Internet protocol (IP)

7022 Bridge

7023 Novell internetwork packet exchange (IPX)

7026 LAN port management system

Table 3 (continued)Passport IndexGroups

IndexGroup Group

(Sheet 2 of 4)

241-5701-500 4.1S1


7031 Point-to-point protocol

7032 Frame Relay DTE

7035 Statistics Management System

7036 APPN Protocol Code

7037 SNA Common Tools

7038 LLC2 Protocol Code

7039 ATM

7040 Source route end station

7041 ATM Networking

7042 ATM AAL1

7043 Trace

7044 SNA

7046 SNA GvcIf

7047 SNA

7048 Frame Relay ISDN

7049 Voice Networking

7050 Remote Service Agent (Rsa)

7052 LAN Emulation Client (Lec)

7053 Multiservice Cut Through Switching (Mcs)

7054 Sparing Management

7056 Voice Server Processor (VSP)/Narrowband Service Trunkover ATM (Nsta)

7057 Digital Circuit Multiplication Equipment voice service

7058 Hunt Group (Hg)

7059 Virtual Router IP information


IndexGroup Group

(Sheet 3 of 4)



ir or

ent

orby

Component fieldThe component field contains the name of the component needing repadetecting the fault.

The component field always contains the abbreviated form of the componname. To find out component abbreviations, refer to 241-5701-060Passport7400, 15000, 20000 Components.

Common component fieldsIn cases where the alarm is common to all or most components the fieldcontains <component_name> or <component_type>.

Severity fieldSeverity is always one of: indeterminate, critical, major, minor, warning, cleared. These values and their definitions correspond to those defined OSI in ITU-T X.733.

7060 Logical Processor Engineering

7062 WirelessPCU project

7063 DPRS (Routing Protocol Tracing Tool)

7064 MPLS

7065 Signaling Gateway Radio Network Control Interface

7066 Signaling ATM adaptation layer Network-to-Networkinterface

7067 Virtual Media Gateway Interface

7068 Serving GPRS support node

7070 Adjunct Processor (AP)


IndexGroup Group

(Sheet 4 of 4)

241-5701-500 4.1S1


0),ritynt

ult.

.nd

hat

e the with

be

or

ate of

Note: For Passport common alarms (alarms with an IndexGroup 000the severity is dependent on the component. To reflect this, the sevefield says <severity> to indicate that the value may change with differecomponents.

Following are explanations of the different types of severity:

• indeterminate—the system cannot determine the level of severity.

• critical—requires you to react immediately to the failure. Usually itimplies that the resource is completely disabled and that service isaffected.

• major—requires that you take immediate corrective measures. Theresource is severely disabled and service is affected.

• minor—corrective action should be taken to prevent a more serious faThe resource is partially disabled but service is not affected.

• warning—action should be taken to diagnose and correct a problemSome problem has been detected but the resource is not disabled aservice is not affected.

• cleared—all previous alarms on this component are cleared. Alarms thave a status of clear always have a severity of cleared.

Status fieldStatus is always one of message, set, clear or set/clear. In situations whersame alarm generates both a set and clear, this document represents itset/clear.

Following are explanations of the different types of status:

• message—a message alarm indicates a condition in which you mayinterested. All software alarms have the status of message.

• set—indicates that a fault or failure has occurred and that an operataction may be required to correct the problem.

• clear—when the fault is repaired, a clear alarm is generated to indicthat the condition has returned to normal. Alarms that have a statusclear always have a severity of cleared.



learoththe

or1).

ke

• set/clear—sometimes an alarm must be both set and cleared. In thissituation, the alarm is issued twice, once to set the alarm and once to cthe alarm. The alarm appears with the same alarm index number in bcases. This occurrence is indicated in this document by set/clear in status field.

Details fieldThe details field contains the following information:

• what has caused the alarm

• how the alarm impacts the network, service, and other components

Note: Alarm descriptions that include mention of the control process(CP) are generally applicable to a control and function processor (CFP

Remedial action fieldThe action field contains information telling the operator what actions to tato correct the problem. The remedial action might include one of thefollowing:

• issuing an operator command

• replacing hardware

• waiting until the alarm clears itself (no action is required)

• opening an service request (SR)

241-5701-500 4.1S1

43

400,to

d

Chapter 4Alarms

This section lists and describes all possible alarms for Passport 6400, 715000, and 20000. For details on how to interpret alarm information, refer“Interpreting alarms” (page 19).

Note:Bus technology refers to Passport 7400 and Passport 6400 anFabric refers to Passport 15000 and 20000.


44 Chapter 4 Alarms

arm

0000 0000

Legend<component_name> = any Passport component

DetailsA hierarchical clear has been issued.

This clears allset alarms for components hierarchically below this component.There is a special case when <component_name> is a logical processor (LP)component. In addition to the components hierarchically below the LP, this alclears all Set alarms for components which have specified the LP as a relatedcomponent in that set alarm.

Probable CauseProcessor problem, Underlying resource unavailable, Operational condition,Procedural error

TypeEquipment, Processing, Operator

Remedial actionNone.

Component Severity Status<component_name> clear clear

241-5701-500 4.1S1

Chapter 4 Alarms 45

tive

0000 1000

Legend<component_name> = any Passport component that supports thelock andunlockcommands<severity> = varies with component

DetailsWhen the status isset, the component has gone into a locked state or a shuttingdown state.

The locked component is no longer permitted to provide service. As a result,dependent components may be operationally disabled as well.

When the status isclear the component is unlocked.

The OSI administrative state attribute in the alarm specifies the new administrastate for the component.

Probable CauseDenial of service, Loss of signal, Operational condition

TypeOperator, Communication

Remedial actionWhen the status isset, issue theunlock command to attempt to unlock thecomponent.

When the status isclear, no remedial action is required.

Component Severity Status<component_name> <severity> set/clear


46 Chapter 4 Alarms

al

0000 1001

Legend<component_name> = any Passport component that maintains OSI operationstate<severity> = varies with the component

DetailsThe component has changed OSI operational state.

When the status isset, the operational state has changed to disabled.

When the status isclear, the operational state has changed to enabled.

Probable CauseProcessor problem

TypeEquipment

Remedial actionWhen the status isset, the remedial action is dependent on the component. Forinformation on individual components, refer to 241-5701-060Passport 7400,15000, 20000 Components. For information on resolving problems, refer to theTroubleshooting chapter in 241-5701-605Passport 7400, 15000, 20000 UserAccess Guide. When the status isclear, no remedial action is required.


241-5701-500 4.1S1

Chapter 4 Alarms 47

age

or

s

the

0000 3000

Legend<component_name> = any Passport component<severity> = varies with component

DetailsWhen the status isset, the component has exceeded a threshold for heap or messblocks.

When the status isclear, the component has dropped below a threshold for heapmessage blocks.

The impact on other components can vary.

Probable CauseTiming problem, Configuration error, Protocol error, Out of memory

TypeProcessing, Communication

Remedial actionWhen the component name is logical processor (LP), contact Nortel Networkglobal support.

If the component name is not LP then the remedial action is dependent upon component. For information on individual components, refer to 241-5701-060Passport 7400, 15000, 20000 Components. For information on resolving problems,refer to the Troubleshooting chapter in 241-5701-605Passport 7400, 15000, 20000User Access Guide



48 Chapter 4 Alarms

ory

p/

s

thes

0000 3001


<severity> = varies with component

DetailsWhen the status isset, the component has exceeded a threshold for heap/memavailability.

When the status isclear, the component has dropped below a threshold for heamemory availability.


Probable CauseOut of memory

TypeProcessing


If the component name is not LP then the remedial action is dependent upon component. Refer to the 241-5701-060Passport 7400, 15000, 20000 Component,for more information on individual components.


241-5701-500 4.1S1

Chapter 4 Alarms 49

ock

ge

s

thes

0000 3002


<severity> = varies with component

DetailsWhen the status isset, the component has exceeded a threshold for message blavailability.

When the status isclear, the component has dropped below a threshold for messablock availability.


Probable CauseUnderlying resource unavailable

TypeProcessing


If the component name is not LP then the remedial action is dependent upon component. Refer to the 241-5701-060Passport 7400, 15000, 20000 Component,for more information on individual components.



50 Chapter 4 Alarms

ex isf

ment

ct cant. In

this

0000 9000


DetailsAn internal software error has been detected by a component. This alarm indre-used by many subsystems upon detection of various types and severities ointernal errors. Thus, one instance of an alarm with this index may be totallyunrelated to another instance. In some cases, it is possible that the alarm comtext can give a hint about what has happened.

Because the circumstances which caused this event are unexpected, the impavary on a case-by-case basis from no impact at all to possibly a severe impacthe latter case, it may be accompanied by other alarms.

The problem may or may not be reproducible. If the circumstances are known,can greatly help the resolution of the problem.

Probable CauseSoftware error

TypeProcessing, Communications

Remedial actionContact your local Nortel Networks technical support group.

Component Severity Status<component_name> indeterminate message

241-5701-500 4.1S1

Chapter 4 Alarms 51

0000 9001

Legend<component_type> = any Passport component

DetailsAn internal software error (indicating a bad state) has been detected by acomponent.



TypeCommunications


Component Severity Status<component_type> indeterminate message


52 Chapter 4 Alarms

d by

0000 9002


DetailsAn internal software error (indicating a bad function number) has been detectea component.


Probable Cause

Type



241-5701-500 4.1S1

Chapter 4 Alarms 53

d by a

0000 9003


DetailsAn internal software error (indicating a bad message code) has been detectecomponent.



TypeCommunications




54 Chapter 4 Alarms

(the

its the

vice

It isice.

iceled

he

0999 0001

Legend<node name> = The provisioned node name of the Passport 6400, 7400, 15000nodeName attribute of theModuleData component).

DetailsWhen status isset, the Preside Multiservice Data Manager workstation has lostVC connection to the controlled device whose name and type is displayed byalarm. The cause of the failure is either problems in the communications linksconnecting Preside Multiservice Data Manager and the controlled device, or defailure on the remote end.

When status isclear, the connectivity has been restored.

This alarm is generated completely within Preside Multiservice Data Manager.never spooled to a Passport disk and never appears on the text interface dev

Probable Cause

Type

Remedial actionCheck the communication link connecting the node on which Preside MultiservData Manager resides and the controlled device. Also ensure that the controldevice has not failed.

If you cannot detect the problem in the communication link, or physical link, or tremote-end device, and the problem persists, contact your Nortel Networksrepresentative.

Component Severity StatusEM/<node name> major/cleared set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 55

tionansdings

theat it

m to

ved

It isice.

ssuedxysued

ing

0999 0012

Legend<component id> is the name of any Passport 6400, 7400, 15000 componentgenerating SCNs

DetailsThe state of the component has been changed due to a state change notifica(SCN) received from the network. When the status of the alarm is a set, it methat the SCN indicated that the component is down, and there are no corresponactive alarms (generated by the switch) on that component to indicate that it idown. Therefore Preside Multiservice Data Manager created a proxy alarm toreplace the missing alarm. Preside Multiservice Data Manager will mark thecomponent Out of service.

When the status of the alarm is a clear, it means that the SCN indicated that component is up, and there were active alarms on that component to indicate this down. Therefore Preside Multiservice Data Manager generates a proxy alarreplace the missing clear. Preside Multiservice Data Manager will mark thecomponent Inservice.

The comment text of this alarm contains information on the SCN that was receithat triggered Preside Multiservice Data Manager to create the proxy alarm.

This alarm is generated completely within Preside Multiservice Data Manager.never spooled to a Passport disk and never appears on the text interface dev

Probable Cause

Type

Remedial actionThis alarm is issued either because the SCN was received before the alarm iby the switch, which would put the component in the proper state (and the proalarm will be cleared when the real alarm is received) or because the alarm isby the switch has been lost.

Treat proxy alarms as you would treat regular alarms and use them in debuggnetwork problems.

Component Severity StatusEM/<component id> major/cleared set/clear


56 Chapter 4 Alarms

l to

f IP

1100 0001

LegendNone.

DetailsThe TimeToLive field in the IP header of the received VRRP packet is not equa255. This field is used to provide sanity check on the VRRP packet.

Probable Cause

Type


Warning: There are possibly multiple master VRRPs running for the same set oaddresses.

Component Severity StatusInwIpVrrp warning message

241-5701-500 4.1S1

Chapter 4 Alarms 57

ct.

1100 0002

Legend

DetailsThe Version field in the VRRP header of the received VRRP packet is not correThis could be caused by using an obsolete version of software.

Probable Cause

Type

Remedial actionUpgrade the switch with VRRP version 2 software.



58 Chapter 4 Alarms

me

1100 0003

Legend

DetailsThe advertisement interval timers are provisioned with different values for the saVRRP on different routers.

Probable Cause

Type

Remedial actionChange provisioning on the routers.


241-5701-500 4.1S1

Chapter 4 Alarms 59

1100 0004

Legend

DetailsChecksum of the received VRRP packet is incorrect. Network could be in anunstable state.

Probable Cause

Type


Notes: might have to take down the network if this repeatedly happens.



60 Chapter 4 Alarms

P)on

t be

a SR

rks

7000 0001

LegendNone.

DetailsInitial loading of the boot file failed because it is missing.

Initial loading and initial activation have been aborted. The control processor (Cwill still come up and allow operator login, however it has incomplete configuratidata and configured software/services have not been started.

The /system/commit file contains the name of the boot file. This boot file muspresent in the /provisioning directory. If all files are present, then either theindividual files or the complete file system is corrupt.

Probable CauseFile error, Corrupt Data

TypeProcessing

Remedial actionRun disk diagnostic tests in order to provide additional problem information.

On a dual-CP system, if a spare CP is present, replace the defective CP, raiseand return the defective CP to Nortel Networks.

If the alarm is generated on a single-CP system, contact your local Nortel Netwotechnical support group.

Component Severity StatusProv critical message

241-5701-500 4.1S1

Chapter 4 Alarms 61

n.

ndired

7000 0002

LegendNone.

DetailsA command from the boot file failed during initial loading.

Initial loading and initial activation are not aborted, they continue to completio

Probable CauseCorrupt data

TypeProcessing

Remedial actionAfter initial loading and initial activation completes, enter provisioning mode arun semantic checks on the target component of the failed command. Make requchanges, activate, and commit changes.

Component Severity StatusProv minor message


62 Chapter 4 Alarms

P)on

t be

n SR

rks

7000 0003

LegendNone.

DetailsInitial loading of the boot file failed because it is corrupt.

Initial loading and initial activation have been aborted. The control processor (Cwill still come up and allow operator login, however it has incomplete configuratidata and configured software/services have not been started.

The /system/commit file contains the name of the boot file. This boot file muspresent in the /provisioning directory. If however all files are present, then it islikely that the individual files or the complete file system are corrupt.

Probable CauseFile error

TypeProcessing


On a dual-CP system, if a spare CP is present, replace the defective CP, raise aand return the defective one to Nortel Networks.



241-5701-500 4.1S1

Chapter 4 Alarms 63

,s

n SR

rks

7000 0004

LegendNone.

DetailsA file system error has occurred while loading a provisioning file during initialloading.

If this occurs during initial booting, then initial loading and initial activation areaborted. The control processor (CP) will still come up and allow operator loginhowever it has incomplete configuration data and configured software/servicehave not been started.


TypeProcessing


On a dual-CP system, if a spare CP is present, replace the defective CP, raise aand return the defective one to Nortel Networks.




64 Chapter 4 Alarms

or

7000 0005

LegendNone.

DetailsA file system error occurred when attempting to close the provisioning afterloading.

This will not affect operation, unless it is occurring repeatedly, each time a loadsave command is performed.


TypeProcessing


Component Severity StatusProv warning message

241-5701-500 4.1S1

Chapter 4 Alarms 65

ing

he

7000 0006

LegendNone.

DetailsThe control processor (CP) is crashing because there is an internal softwarecorruption.

Usually there are related alarms (possibly software alarms) prior to this alarm begenerated, which may indicate how the data was corrupted.


TypeProcessing


If the CP repeatedly crashes due to this problem, replace the CP and return tdefective CP to Nortel Networks for post-mortem.



66 Chapter 4 Alarms

as

jor

7000 0007

Legend<severity> = warning, minor, major, critical and cleared.

DetailsWhen the status issetand severity iswarning, ProvisioningSystem(Prov) has justcompleted an activation of provisioning changes, and the confirmation timer hbeen set to 20 minutes.

This alarm will be generated every 5 minutes with increasing severity (minor, maand critical) to remind you to enter theconfirm prov command.

When the status isclear, either theconfirm prov has been entered orProvisioningSystem has just completed activating the provisioning view.

Note: it is possible toconfirm provbefore the alarm would have beenset, in whichcase thesetwould not occur and theclearwould simply indicate that activation hasfinished

Probable CauseOperational condition

TypeOperator

Remedial actionWhen the status isset, enterconfirm prov within 20 minutes of receiving the setalarm, to ensure rollback will not occur (validates connectivity).

Component Severity StatusProv <severity> set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 67

eenual

7000 0008

LegendNone.

DetailsThis alarm is generated when initial activation detects that the software has bpatched. A “migration” style of loading takes place that is much slower than usand as a result, the service outage times are much greater.


TypeProcessing

Remedial actionSimply re-check, re-save and re-commit the current view as required.

Component Severity StatusProv major message


68 Chapter 4 Alarms

a isnd

7000 0009

LegendNone.

DetailsThis alarm is generated when initial activation detects that the provisioning datmissing the commit format. The resulting activation is much slower than usual aas a result, the service outage times are much greater.

This scenario typically occurs when migrating to a new software version.


TypeProcessing

Remedial actionSimply re-check, re-save and re-commit the current view as required.

Component Severity StatusProv major message

241-5701-500 4.1S1

Chapter 4 Alarms 69

new

7000 0010

Legend<name> = any provisionable Passport component

DetailsThis alarm is generated when the reporting component cannot be updated withprovisioning data. This implies that the service provided by the reportingcomponent will either not be created or not be modified to behave with thecharacteristics described in the new provisioning data.

Probable CauseUnderlying resource unavailable, Software program error, Software Programtermination, Configuration Error

TypeProcessing

Remedial actionCheck the provisioning of the software for the specified component.

ThelogicalProcessorTypeattribute of theLpcomponent named in the alarm shouldbe provisioned to the properLpt component. ThisLpt component should have anynecessary features provisioned in thefeatureList attribute.

Correct any provisioning errors and attempt re-activation.

Otherwise, contact your local Nortel Networks technical support group.

Component Severity Status<name> minor/cleared set/clear


70 Chapter 4 Alarms

ing

7000 0011

Legend<name> = any provisionable Passport component

DetailsThis alarm is generated when an application is slow in responding to provisiondata. It should not be considered failed, until alarm 7000 0010 is generated.

Probable CauseDebugging

TypeDebug

Remedial actionNo action is required, this is only a warning.

Component Severity Status<name> warning message

241-5701-500 4.1S1

Chapter 4 Alarms 71

on is

7000 0012

LegendNone.

DetailsThis alarm is generated when a network management interface (NMIF) sessiforced off from the provisioning mode by the system administrator.


TypeOperator

Remedial actionContact your Nortel Networks technical support group.



72 Chapter 4 Alarms

ainical

d,

7000 0013

LegendNone.

DetailsThis alarm is generated during initial loading when a provisioned componentcontains a semantically incorrect hardware link. The data of the alarm will contthe component in error. This component will not be created on the proper logprocessor.


TypeProcessing

Remedial actionAfter initial loading and initial activation completes, enter provisioning data anrun semantic checks on the specified component. Make the required changesactivate, and commit the changes.


241-5701-500 4.1S1

Chapter 4 Alarms 73

ave

7000 0015

LegendNone.

DetailsThis alarm is generated during initial loading when a temporary file created to sthe current view data cannot be removed from the disk.


TypeProcessing




74 Chapter 4 Alarms

fast,and

7000 0016

LegendNone.

DetailsThis alarm is generated when a logical processor first becomes active and theboot-mode style of activation fails. The system will reset the logical processor,use an alternative activation style.

Probable Cause

Type



241-5701-500 4.1S1

Chapter 4 Alarms 75

7000 0029

LegendNone.

DetailsThis alarm is generated when an error is encountered while determining theProvisioningSystem component’snextFileSequenceNumber attribute.

If this alarm is generated, thenextFileSequenceNumber attribute is set to 1.

Probable Cause

Type


Contact your local Nortel Networks technical support group.



76 Chapter 4 Alarms

ning

7000 0030

LegendNone.

DetailsThis alarm is generated when a disk open error is encountered while determitheProvisioningSystem component’snextFileSequenceNumber attribute. If thisalarm is generated, thenextFileSequenceNumber is set to 1.

Probable Cause

Type




241-5701-500 4.1S1

Chapter 4 Alarms 77

is

.

7000 0031

LegendNone.

DetailsThe provisioningview file has been corrupted or contains inconsistent data. Thcould be due to a file system error or manual modification of the data.

The component information will be built as part of the slow boot sequence.


TypeProcessing

Remedial actionAfter the nextcheck prov, do asave prov to generate a new provisioning file.

If the problem persists, contact your Nortel Networks technical support group



78 Chapter 4 Alarms

ofion

h

.

7000 0032

LegendNone.

DetailsThis alarm is generated on an initial activation when the fast, boot-mode styleactivation cannot be used due to a problem saving commit-format files. Activatwill proceed, but with a slower style of activation.

Probable Cause

Type

Remedial actionCheck for alarms indicating a problem with saving of commit-format files or witthe disk.

If the problem persists, contact your Nortel Networks technical support group


241-5701-500 4.1S1

Chapter 4 Alarms 79

asny

7000 0033

LegendNone.

DetailsIf the status is set and the severity is critical, a software migration activation hpaused. A software migration activation pauses before Migration-Switchover if aof the following occurs:

• a software alarm is generated on the migration shelf

• an engineering alarm is generated on the migration shelf

Component Severity StatusProv Migration warning/critical/

clearedset/clear


80 Chapter 4 Alarms

ron

hasher

red.

le

akerm

p

• an application can not achieve its expected Migration-Switchoverbehavior.

A clear is issued after the operator enters the appropriate commands to eithecontinue with the software migration activation or to stop the software migratiactivation.

If the status is set and the severity is warning, a software migration activationstarted. A clear is issued after the software migration activation completes eitsuccessfully or unsuccessfully.


TypeOperator

Remedial actionIf the status is set and the severity is warning then no remedial action is requiBe aware that a software migration activation has begun on this switch.

If the status is set and the severity is critical, review the set of Migration VisibAlarms raised during the software migration activation and consult the newsoftware release documentation and/or Nortel Networks technical support to ma decision whether to continue with the software migration activation or to perfoa hitless recovery. To continue with the software migration activation use thecontinue provisioningSystem command from within provisioning mode. To stothe software migration activation through a hitless recovery use the stopprovisioningSystem command from within provisioning mode.

241-5701-500 4.1S1

Chapter 4 Alarms 81

ext is

tionhile

7000 0034

LegendNone.

DetailsThis alarm is generated when a fault condition occurs on the migration shelf. Tfrom the original alarm generated for the fault condition on the migration shelfembedded within this alarm. Typically, the fault conditions represent:

• a software alarm

• an engineering alarm

• a condition which indicates that an application can not achieve itsexpected Migration-Switchover behavior.

Probable CauseDebugging

TypeDebug

Remedial actionRefer to the alarm index within this alarm text in the new software releasedocumentation for more information. If deemed appropriate, the software migraactivation can be stopped by issuing the stop provisioningSystem command win provisioning mode.



82 Chapter 4 Alarms

ady.

and

edtop

7000 0035

Legend<name> = any provisionable Passport component.

DetailsThis alarm is raised against any component that fails to indicate whether it is refor a Migration-Switchover. This alarm will pause a hitless software migration

This message alarm is ONLY generated on the migration shelf; it is reformattedregenerated against the Prov Migration component.

Probable CauseUnknown

TypeUnknown

Remedial actionThe component <name> may not be ready for a migration-switchover. If deemappropriate, the software migration activation can be stopped by issuing the sprovisioningSystem command while in provisioning mode.

Component Severity Status<name> indeterminate message

241-5701-500 4.1S1

Chapter 4 Alarms 83

t

VC)

beVC

7001 2000

Legend<component_name> = component of system which is using the Virtual Circui(VC).

DetailsThe system was unable to establish the indicated permanent virtual circuit (Pdue to incompatible options.

The comment string associated with the alarm indicates what was detected toincompatible. Errors are due to options that do not match at either end or a Pmaster calling another master or slave calling a slave.

Probable Cause

Type

Remedial actionCorrect the options in the application so that the call may be established.

Component Severity Status<component_name> minor message


84 Chapter 4 Alarms

t

heiate

, thech

7001 2001


DetailsThe Virtual Circuit system has detected a protocol violation and has cleared tassociated call as a corrective action. The application is signalled with approprclear causes.

Expert data contains the state of the Virtual Circuit, the internal message codeITU-T protocol violation number and, optionally, 32 bytes of the data packet whicaused the protocol violation.

Comment text describes the cause of the protocol violation detected.

Probable Cause

Type

Remedial actionNo action is required since the call is cleared.

Component Severity Status<component_name> warning message

241-5701-500 4.1S1

Chapter 4 Alarms 85

t

edsary to

7001 2002


DetailsA VC could not be established due to resource limitations.

Probable Cause

Type

Remedial actionIf the alarm is isolated, then no action is required.

If this alarm appears with some frequency, then the engineering of this switch neto be re-examined because call requests are being dropped. It may be necessdisable the application to prevent repeated attempts to establish a call.

Component Severity Status<component_name> major message


86 Chapter 4 Alarms

t

withludes

ion

to re-

7001 2003


DetailsA data path error has been detected by the VC. The comment text associatedthis alarm indicates the exact cause of the problem. Some typical examples incframe or credit congestion, VC windows running to their upper limits, or variouinterrupt frame errors. Internal data associated with this alarm will allow detectof the exact error.

Probable Cause

Type

Remedial actionNo action is required if the alarm is isolated. Repeated alarms indicate a needexamine the engineering of the switch. It may be necessary to disable someapplications to reduce traffic on this processor.

Component Severity Status<component_name> warning message

241-5701-500 4.1S1

Chapter 4 Alarms 87

e far

as

ient

7001 5006

Legend<num1> = 1 - 15<type> = 1pE1V and 1pDS1V

DetailsIf the status is set, the voice application was unable to make a connection to thend.

A clear will be issued when the busy out condition is cleared by the link.

Probable Cause

Type

Remedial actionCheck the cabling between the far end port and the PBX. Look at the LogicalConnection (LCo) subcomponent of the voice application(s) on this LP for cluesto why the connection is not up. Verify that the Permanent Logical Connection(PLC) attributes are correct and compatible with the far end. Ensure that sufficbandwidth is available in the network for the connection to establish.

Component Severity StatusLp/<num1> <type>/0 major/cleared set/clear


88 Chapter 4 Alarms

nals

he

s

7002 0000

Legend<id> = X or Y

DetailsIf the status isset, the main source of clock signals for the bus is defective. Thereason is that one or more bus taps on the bus are unable to receive clock sigfrom the active control processor (CP).

If the status isclear, the alarm indicates that the main source of clock signals for tbus is no longer defective.

Probable Cause

Type

Remedial actionFollow the standard procedure for testing the bus and remove or replace thedefective unit(s). Refer to 241-5701-605Passport 7400, 15000, 20000 User AccesGuide for details on testing the bus.

Component Severity StatusBus/<id> warning/cleared set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 89

henals

ssor

r

sent the

7002 0001

Legend<id> = X or Y

DetailsIf the status isset, the standby source of clock signals for the bus is defective. Treason is that one or more bus taps on the bus are unable to receive clock sigfrom the card at the opposite end of the module from the active control proce(CP).

If the status isclear, the standby source of clock signals for the bus is no longedefective.

Probable Cause

Type

Remedial actionEnsure that the card at the opposite end of the module from the active CP is preand operational. If the alarm persists follow the standard procedure for testingbus and remove or replace the defective unit(s). Refer to 241-5701-605Passport7400, 15000, 20000 User Access Guide for details on testing the bus.

Component Severity StatusBus/<id> warning/cleared set/clear


90 Chapter 4 Alarms

dary

tional the

arye20

7002 0002

Legend<id> = X or Y

DetailsThis alarm is generated on fabric-based shelves when the fabric card’s seconcontrol bus (SCB) is no longer able to provide service. This can occur eitherbecause the SCB is not receiving a clock signal or because at least one operacard cannot access the SCB.The control processor (CP) gets its alarms fromfabrics over the bus.

When the status isclear, the fabric card’s SCB is no longer defective.

Probable CauseOverruns or underruns of bus data, corrupt data, or external noise such aselectromagnetic interference (EMI)

TypeProcessing

Remedial actionWhen the status isset, examine the operational attributes related to the secondcontrol bus of theFabricCardcomponent to determine the cause of the alarm. If thattributes do not satisfactorily explain the cause of the alarm, see 241-5701-5Passport 7400, 15000, 20000 Troubleshooting Guide for information ontroubleshooting control processor (CP) cards and the fabric card.

Component Severity StatusShelf FabricCard/<id> major/cleared set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 91

ent’segrees

l

f the

dle

ng

d.m’sP

7002 0003

Legend<id> = X or Y

DetailsThis alarm is generated on fabric-based shelves when the FabricCard compontemperature has increased above the accepted operating temperature of 65 dCelsius (149 Fahrenheit). If the temperature continues to rise, the FabricCardcomponent will be removed from service by the system to avoid damage.

When the status isclear, the FabricCard’s temperature has returned to a normaoperating temperature.

Probable CauseThe ambient temperature inside the shelf is too high because of one or more ofollowing:

• the ambient room temperature is too high for the cooling fans to han

• a stopped fan has reduced the effectiveness of the cooling unit

• one or more empty card slots that is missing a filler panel is interferiwith the airflow inside the shelf

• the air filter is too clogged and requires replacing

• the alarm/BITS module is faulty or removed

• the temperature sensor of a fan is faulty

• the temperature sensor cable assembly is faulty or disconnected

TypeProcessing

Remedial actionWhen the status isset, ensure that the cooling unit is powered and properly inserteEnsure that the ambient temperature in the room is not interfering with the systeability to cool itself. If the problem persists, follow the standard procedure in NT241-5701-520Passport 7400, 15000, 20000 Troubleshooting Guide to test thefabric card, and replace the defective cooling unit part or the fabric.

Component Severity StatusShelf FabricCard/<id> warning set/clear


92 Chapter 4 Alarms

ningnaln of

e,

7002 0005

Legend<instance> = X or Y

DetailsThis alarm is generated on fabric-based shelves when two fabric cards are rundifferent versions of firmware. Although this condition does not cause operatioproblems, Nortel Networks recommends that you always run the same versiofirmware on each fabric card, except during initial testing purposes.

When the status isclear, both fabric cards are running the same version of firmwaror the other fabric card has been removed.


TypeProcessing

Remedial actionWhen the status isset, install the software version indicated by therecommendedVersionToInstall attribute of theFabricCard component.

Component Severity StatusShelf FabricCard/<instance> major set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 93

7002 0006


DetailsThis alarm is generated on fabric-based shelves when the install command isinterrupted by a CP switchover or other disruptive event, causing fabric cardloading to be aborted.

When the status isclear, the firmware has been successfully loaded into thewriteable bank of the fabric card.


TypeProcessing

Remedial actionWhen the status isset, install the fabric card firmware again.



94 Chapter 4 Alarms

7002 0007


DetailsThis alarm is generated on fabric-based shelves when a fabric card is runningfirmware that is older than the latest available version.

When the status isclear, the fabric card is running the latest available firmwareversion.

Probable Cause

Type

Remedial actionWhen the status isset, install the software version indicated by therecommendedVersionToInstall attribute of theFabricCard component.


241-5701-500 4.1S1

Chapter 4 Alarms 95

lane

ing

7002 1000

Legend<instance> = 0-15

DetailsThis alarm indicates that the card is not communicating properly over the backpbuses.


Typeequipment

Remedial actionThe active control processor (CP) attempts to correct the problem by re-initializthe card. If the alarm is repeated, replace the card.

Component Severity StatusShelf Card/<instance> critical message


96 Chapter 4 Alarms

5%ded.rs fors.datarn,ot

5

useere full.

oune,

fed,non5

7003 0001

Legend<type> = accounting, alarm, log, scn, debug, trap, stats, rtStats

<cardnumber> = the card on which the Agent resides

DetailsIf the status isset, a data collection system (DCS) Agent’s queue has reached a 7full threshold. If the queue becomes full then subsequent records will be discarThere are three possible reasons for this to occur. First, if there are no requestothis particular DCS data type then the records will be held in the Agent queueSecond, the provisioned queue size may be insufficient for the amount of DCStraffic. Thirdly, a requestor of this particular DCS data type could be slowing oblocking the flow of DCS records. For example, if spooling is provisioned to oand the spooler is the only requestor of data then if the spooler is locked or nspooling because of a recoverable condition detected by the file system (forexample, disk full), data flow will be blocked and the Agent queues will fill up.

A clear will be issued when the queue size drops below 50% full and at least minutes has elapsed since theset was issued. This delay provides a throttlingmechanism so that bursts of records for relatively small queue sizes do not catoo many alarms within a short time. The clear will indicate how many records wdiscarded (if any) in the event that data arrived after the queue became 100%

Probable CauseThreshold crossed

TypeQuality of service

Remedial actionIf you do not wish to monitor or collect this particular type of DCS data, then ymay want to provision the queue size to be zero for this data type. If this is dothen all records of this type will be discarded.

Verify that the queue size is provisioned to an adequate size for the expectedamount of traffic.

Verify that there are no requestors of this DCS data type holding up the flow orecords. For example, if spooling is provisioned to on, and the spooler is lockthen unlock it. If the spooler is not spooling because of a recoverable conditiodetected by the file system, then clear the file system problem. For informationresolving such problems, refer to the Troubleshooting chapter in 241-5701-60Passport 7400, 15000, 20000 User Access Guide.

Component Severity StatusCollector/<type> Agent/<cardnumber> major/cleared set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 97

When the status isclear, no action is required.


98 Chapter 4 Alarms

filefilese.he

f a

ectedfter be

bem

P)

, but

7003 0002


DetailsIf the status isset, a DCS Spooler has stopped spooling records to the shadowedsystem. Typically, the reason is due to a recoverable condition detected by thesystem. The file system will have issued its own alarm(s) indicating the root cauThis DCS alarm is to indicate the effect of the file system being unavailable. Tcondition will likely affect other users of the file system as well. An example orecoverable condition isdisk full. The exact nature of the error will be displayed inthe comment data field of the alarm.

This alarm can also appear under certain abnormal conditions detected by thSpooler, usually accompanied by other alarms, likely indicating some unexpeinteraction with the file system. An example of such a condition is one where, amultiple CP switchover/failures, it is possible (but not guaranteed) for a file toduplicated in both the/spooled/opened/<type> and/spooled/closed/<type>directories, causing a Spooler to fail.

A clear will be issued after recovering from the condition.


TypeProcessing

Remedial actionIf the status isset, resolve the file system condition which caused this alarm to generated. You may be required to take different actions to resolve the probledepending on the state or status of the disk or file system.

If the file system is full, clean up some files.

If the file system is locked, unlock it by issuing theunlock command.

If the file system fails, try to copy unprocessed spool files (for example, using FTfrom the control processor and then replace the control processor.

When a recoverable condition is resolved, the Spooler is notified and itautomatically tries to continue spooling. Theclear is issued when the Spooler isagain able to spool data to the file system.

If you encounter an unexpected condition, the action may vary to some degree

Component Severity StatusCollector/<type> Spooler major/cleared set/clear

241-5701-500 4.1S1

Chapter 4 Alarms 99

, fileeor

most likely, at some point you will have to lock and then unlock theFileSystemcomponent. This causes all active and failed DCS Spoolers to reset. In additionsystem commands may be needed to clean up certain files. For example, if th“duplicate file” scenario mentioned above occurs, one would have to remove rename the file in the “closed” directory prior to locking/unlocking theFileSystemcomponent.

If you are unable to resolve the file system condition, contact Nortel Networkstechnical support.


100 Chapter 4 Alarms

es

oollue

a

n be

the

.

7003 0003


DetailsIf the status isset, then the DCS Spooler does not restrict the number of spool filto the value specified in the Spooler’smaximumNumberOfFiles attribute.

This condition occurs when there are more than 250 files in the associated spdirectory. At this point, it is no longer possible for the Spooler to enforce the vaspecified bymaximumNumberOfFiles attribute. The condition persists until thenumber of spool files for the associated <type> is less than 250, at which timeclear alarm is issued.

Note: This condition is only expected to occur in the case where themaximumNumberOfFiles attribute is provisioned from zero to a non-zero value.

A clear is issued after recovering from the condition.



Remedial actionReduce the number of spool files for the associated type to below 250. This cadone in one of following ways.

Ensure that MDP is configured to retrieve the spool files and remove them fromPassport.

Manually remove the spool files using theFilesystem component. The relevantdirectory to examine and from which to remove files is /spooled/closed/<type>

If you are unable to resolve file condition, contact Nortel Networks technicalsupport.

241-5701-500 4.1S1

Chapter 4 Alarms 101

ithecify

eds aices

tware

7003 0004


<cardnumber> = the card on which the Agent resides

DetailsThe purpose of this alarm is to indicate if software alarms (that is, those alarms windices 0000 9000, 0000 9001, and 0000 9002) have been discarded and to sphow many have been discarded.

Software alarms are discarded when the rate at which they are generated excesystem defined threshold. This throttling mechanism is in place to protect servagainst an excessive number of software alarms.



Remedial actionThere is no remedial action specific to this alarm.

The presence of this alarm, however, indicates that an excessive quantity ofsoftware alarms have been generated. The remedial action, when receiving sofalarms, is to contact your local Nortel Networks technical support group.



y

oneded

7004 0101

Legend<parent_name> = Trunk or DpnGateway

<instance> = a decimal value

<type> = Utp, Unacked, AtmAccess, or FrAccess

DetailsIf the status isset, a link quality degradation has been detected, and its parentcomponent is disabled. More specifically, the link error rate has exceeded theacceptable threshold as specified in the provisioning data of this component.

A clear will be issued after its parent component completes restaging.

Probable Cause

Type

Remedial actionDetermine why the link quality has degraded. Note that, for FrAccess, the onlquality parameter is the lost frames by the external frame relay network.If it isexhibiting the expected or a higher yet acceptable rate, then change the provisierror rate threshold to allow for a faultier connection. The amount of traffic allowto be routed through the link should also be reduced.

Component Severity Status<parent_name>/<instance> <type> critical/cleared set/clear

241-5701-500 4.1S1


tionPausedd to

ers

S1C/

E1C

7004 0102

Legend<parent_name> = Trunk or DpnGateway


<type> = Utp or Unacked

DetailsIf the status is set, it is indicative of an unsuccessful registration with the congesmanagement. An example is when the maximum number of DpnGateway/UTregistrations has been exceeded on a DS1C/E1C FP. Each DpnGateway that cthe maximum number of registrations to be exceeded is disabled and not allowecome up.

A clear will be issued for every Trunk or DpnGateway that successfully registwith the congestion management.

Probable Cause

Type

Remedial actionManual intervention by the user may be necessary as a remedial action. On DE1C cards the provisioning has to be modified such that the total number ofDpnGateways per card is less than or equal to the maximum of 23.

It is also possible to have more than 23 DpnGateways provisioned on a DS1C/card. In this case, theifAdminStatus attribute of the DpnGateways which haveexceeded the maximum number of registrations must be set to down.

Component Severity Status<parent_name>/<instance> <type> major/cleared set/clear



, or

ns.

er linkg

alr is

for

7004 0301

Legend<instance> = a decimal value

DetailsIf the status isset, the Utp has been disabled due to a protocol violation causedpossibly by (1) A loop check frame not being received within an expected time(2) Utp trying to enter Are-You-There at a wrong state as a result ofLastAckTimeout protocol violation.

See also alarms 7004 0305 and 7004 0306 for other types of protocol violatio

A clear will be issued after the Utp has successfully restaged.

All protocol violation conditions may arise due to problems with the physical layor due to a side effect of congestion recovery. Under congestion recovery thereceive buffers may be discarded to free up resources for the FP. The missinframes resulting from discarding this buffer could result in one of the protocolviolations if the loss were severe enough.

Probable Cause

Type

Remedial actionIssue thedisplay statisticscommand for the Framer subcomponent on both the locand remote ends of the connection. This is done to verify that the physical layegood. Also issue adisplay shelf card/n util command to determine if the FP isrunning at high CPU or memory utilization. Revisit the engineering guidelinesthis service if condition persists.

Component Severity StatusDpnGateway/<instance> Utp critical/cleared set/clear

241-5701-500 4.1S1


that

oned

7004 0302


DetailsIf the status isset, the Framer subcomponent has measured a transmit link speedexceeds 2 Mbit/s.

A clear will be issued after the link speed is less than or equal to 2 Mbit/s.

Probable Cause

Type

Remedial actionDetermine whether the link speed of the hardware component has been provisiincorrectly.

Component Severity StatusDpnGateway/<instance> Utp major/cleared set/clear



ghen

ndsping

7004 0303


DetailsIf the status isset, the Utp has experienced a staging time-out by not completinstaging within the expected time. This can occur if no frames are received or wthe remote end is too slow.

The component will attempt to restage. As a result, the parentDpnGatewaycomponent will take longer to stage with the remote. Aclearwill be issued after theUtp has successfully restaged.

Probable Cause

Type

Remedial actionVerify that the connection is valid and that the hardware components on both ehave been provisioned correctly. Perform a port and line test with manual looif possible to verify the physical layer.


241-5701-500 4.1S1


heion, or

tion.lso

on.

7004 0304


DetailsIf the status isset, the Utp has been disabled due to loss of communication with tfar end. It can occur when Utp has detected a Yes-I-Am Timeout. This conditmay arise due to far end disabling, problems with the underlying physical layera side effect of congestion recovery.


Probable Cause

Type

Remedial actionIssue thedisplay statistics command for Utp component and the Framersubcomponent on the local end and for the port on the remote end of the connecThis is done to verify that the connection is valid and physical layer is good. Aissue adisplay shelf card/n utilcommand to determine if the FP is running at highCPU or memory utilization. Issue adisplay statistics command for the PE on theremote DPN to determine if the PE is running at high CPU or memory utilizatiRevisit the engineering guidelines for this service if condition persists.




l

n.

no

er linkg

FPes

7004 0305


DetailsIf the status isset, the Utp has been disabled due to a LastAckTimeout protocoviolation.



This condition is related directly to the windowed protocol. It may arise when acknowledgment is received from the far end.


Probable Cause

Type

Remedial actionIssue the display statistics command for theFramer subcomponent on both thelocal and remote ends of the connection to verify that the physical layer isoperational. Also issue a display shelf card/n util command to determine if theis running at high CPU or memory utilization. Revisit the engineering guidelinfor this service if condition persists.


241-5701-500 4.1S1


ent

n.

st

er linkg

es

7004 0306


DetailsIf the status isset, the Utp has been disabled due to a large gap in acknowledgmprotocol violation.



This condition is related directly to the windowed protocol. It may arise due to loof excessive number of frames within an acknowledgment window.


Probable Cause

Type

Remedial actionIssue the display statistics command for theFramer subcomponent on both thelocal and remote ends of the connection to verify that the physical layer isoperational. Also issue adisplay shelf card/n util command to determine if the FPis running at high CPU or memory utilization. Revisit the engineering guidelinfor this service if condition persists.




d.

andlsoighif

7004 0401

Legend<instance> = a decimal value.

DetailsIf the status isset, theFrAccess component has been disabled due to a protocolviolation. A clear is issued after theFrAccesscomponent has successfully restage

Probable Cause

Type

Remedial actionIssue the display statistics command for the subcomponent on both the local remote ends of the connection to verify that the physical layer is operational. Aissue a display shelf card/n util command to determine if the FP is running at hCPU or memory utilization. Revisit the engineering guidelines for this service condition persists.

Component Severity StatusDpnGateway/<instance> FrAccess major set

241-5701-500 4.1S1


t/s.

7004 0402


DetailsIf the status isset, the provisioned CIR (committed information rate) exceeds 2Mbit/s.

A clear is issued when the CIR is reprovisioned to less than or equal to 2 Mbi

Probable Cause

Type

Remedial actionDetermine whether the CIR has been provisioned correctly.

Component Severity StatusDpnGateway/<instance> FrAccess major/cleared set/clear



byre

the

nds

7004 0403


DetailsIf the status isset, theFrAccess component has experienced a staging time-out not completing staging within the expected time. This can occur if no frames areceived or when the remote end is too slow.

The component will attempt to restage. As a result, the parentDpnGatewaycomponent will take longer to stage with the remote. A clear will be issued afterFrAccess component has successfully restaged.

Probable Cause

Type

Remedial actionVerify that the connection is valid and that the hardware components on both ehave been provisioned correctly. Verify that theFr Dlci components and the PVCsare provisioned correctly and operational.

Component Severity StatusDpnGateway/<instance> FrAccess critical/cleared set/clear

241-5701-500 4.1S1


,

theicaluxaorte

sit

7004 0404


DetailsIf the status isset, theFrAccess component has been disabled due to loss ofcommunication with the far end. This can occur when theFrAccess componentdetects a Yes-I--Am timeout. This condition can arise due to far-end disablingproblems with the underlying physical layer, or a sided effect of congestionrecovery.

A clear is issued after theFrAccess component has successfully restaged.

Probable Cause

Type

Remedial actionIssue the display statistics command for theFrAccess component and the FrMuxFramersubcomponent on the local end. Issue the pi n po m D stat command forport on the remote end to verify that the connection is valid and that the physlayer is operational. Also issue the d frmux/n dlci/m command and similar frmrelated commands to determine the status of the underlying PVC. Also issue display shelf card/n util command to determine if the FP is running at high CPUmemory utilization. Issue a PE n D statistics command for the PE on the remoDPN to determine if the PE is running at high CPU or memory utilization. Revithe engineering guidelines for this service if the condition persists.

Component Severity StatusDpnGateway/<instance> FrAccess critical/cleared set/clear



cted

ther

7005 0101

Legend<component_name> = Trunk or DpnGateway


DetailsIf the status isset, the component has experienced a staging time-out by notreceiving all the required packets from the remote component within the expetime.This can result from excessive congestion on the link.

The component will immediately attempt to restage, and aclear will be issued ifsuccess results.

Probable Cause

Type

Remedial actionVerify that the speeds on both ends of the connection are the same. Also, any ofacility error (or unavailability) may cause the generation of this alarm.

Component Severity Status<component_name>/<instance> critical/cleared set/clear

241-5701-500 4.1S1


se

7005 0102

Legend<component_name> = Trunk


DetailsIf the status isset, the Trunk has been unable to stage logical network numbers(LNN) with the remote component.

The component will attempt to restage in five minutes, and aclearwill be issued ifsuccess results.

Probable Cause

Type

Remedial actionVerify that the provisioned supported address plan subcomponents match thoprovisioned at the remote.




armery

are

areonS

ould

or

debled.

lso

7005 0103



DetailsIf the status isset, the routing system has not permitted theTrunk or DpnGatewaycomponent to stage with the remote for one of the following reasons:

- attempting to stage a fifth link in a link group.

- the Routing System is unable to communicate with the far end node. The alwill probably occur about 2.5 minutes after the Trunk goes online each and evtime that it does go online.

- attempting to stage a link between two nodes that have different region ids andin the same Rid subnet.

- there are multiple links in a link group and some are going down while the restcoming up. It is possible for all to be down at the same time for a small windowone side of the link group only. This is more likely to occur when there is PORtraffic on the Trunks. In this case the alarm should occur once, the Trunks shrestage and there should be no further problem.

- the node is a Passport cluster node and the remote node is a DPN-100 RM CSRM.

- both the local and remote nodes are Passport cluster nodes. Since multi-nocluster is not supported, any link between two Passport cluster nodes are disa

A clear will be issued when theTrunk or DpnGateway component is able tosuccessfully stage with the remote.

Probable Cause

Type

Remedial actionVerify that the number ofTrunkor DpnGatewaycomponents in the link group hasnot exceeded the maximum.

Check the region ids and Rids of the two nodes and verify that the Rids are adifferent if the region ids are non-zero and different.


241-5701-500 4.1S1


nCCs

the

e. Ifn the

Check that the traffic shaping is enabled on the NEP end (if UPC is enabled obackbone). Check that UPC and traffic shaping contracts are matching on all Vused for ATM logical trunks.

Verify the trunk end-to-end connectivity.

Check theclusterNodeattribute of the node. If it isyes, check the remote node andensure it is not also a cluster node or an RM or a CSRM. If the connection to RM or CSRM is required, the value forclusterNodeshould be configured asno, orthe connection to the RM should be established from another non-cluster nodthe remote end is also Passport cluster node, either disable the trunk betweetwo cluster nodes or provision one of the nodes to be a non-cluster node.



7005 0104



DetailsIf the status isset, theTrunk or DpnGateway component has not staged with theremote module/component as specified in the provisioning file.

A clear is issued when theTrunk or DpnGateway component stages with theexpected remote.

Probable Cause

Type

Remedial actionFor aTrunkcomponent, verify that theexpectedRemoteNodeIdattribute is either setproperly or left blank (that is, provisioned as “”). For aDpnGateway component,verify its expectedRemoteNamsId attribute in the same way.


241-5701-500 4.1S1


s

7005 0105



DetailsIf the status isset, theTrunkor DpnGatewaycomponent has failed to stage with theremote due to poor link quality.

A clear is issued when theTrunkor DpnGatewaycomponent successfully restagewith the remote.

Probable Cause

Type

Remedial actionInspect and repair the facility to provide better link quality.




r

s

7005 0106



DetailsIf the status isset, theTrunk or DpnGateway component must disable due to poolink quality (with permission from the Routing System).

A clear is issued when theTrunkor DpnGatewaycomponent successfully restagewith the remote.

Probable Cause

Type



241-5701-500 4.1S1


medue toer-

7005 0107



DetailsIf the round trip delay (calculated from the timestamps of a Propagation Delaypacket) exceeds the limit accepted by the Routing System (1500 ms), it is assuthat the Propagation Delay packet was lost at least once during transmission, da faulty link. The propagation delay reported to the Routing System is then ovwritten to 1500 ms, enabling theTrunkorDpnGatewaycomponent to come up. Themeasured round trip delay will still indicate to the user the actual value (whichexceeds 1500 ms).

Probable Cause

Type


Component Severity Status<component_name>/<instance> critical message



ot

rect

7005 0108



DetailsIf the status isset, theTrunk or DpnGatewaycomponent’soverrideRoundTripDelayattribute has been provisioned with a value that does nmatch the value that is provisioned on the remote.

A clear is issued when theTrunk or DpnGateway component detects that theprovisioned value on each end matches.

Probable Cause

Type

Remedial actionDetermine which end of the connection has not been provisioned with the coroverride value.

Component Severity Status<component_name>/<instance> critical set/clear

241-5701-500 4.1S1


t is

rect

7005 0109



DetailsIf the status isset, theTrunkor DpnGatewaycomponent’soverrideTransmitSpeedattribute has been provisioned with a value that does not match the value thaprovisioned on the remote.

A clear is issued when theTrunk or DpnGateway component detects that theprovisioned value on each end matches.

Probable Cause

Type

Remedial actionDetermine which end of the connection has not been provisioned with the coroverride value.

Component Severity Status<component_name>/<instance> critical set/clear



ver

d

lue

is the

theth

ly. If, inrm

s and

7005 0110



DetailsThis alarm is issued by Passport Unacknowledged Trunks, Passport Trunks oATM and Passport DpnGateways over UTP.

When the status isset, the total average link or ATM VCC utilization has exceedethe value of theminorLinkUtilAlarmThreshold attribute or the value of theminorVccUtilAlarmThreshold attribute, for a sustained period of time.

When the status isclear, the total average link or ATM VCC utilization hassubsequently fallen back to a level at or below the corresponding threshold vafor a sustained period of time.

For Framer-based trunks and DPN gateways, the total average link utilizationcalculated every minute based on comparing the number of bytes received bylink with the available bandwidth on the link. For ATM-based trunks, the totalaverage ATM VCC utilization is calculated every minute based on comparingnumber of cells received by the ATM VCC with the estimated available bandwidon the ATM VCC.

Probable Cause

Type

Remedial actionThe idea is that, with a proper threshold setting, a single instance of this alarmshould not require any special action. It would only be an early indication ofpossible link or ATM VCC congestion. If this alarm is repeated over a relativeshort period of time, it may be an indication that the threshold setting is too lowso, adjust the threshold accordingly. Otherwise, it could indicate bursty trafficwhich case, it could be the indicator that you want. The occurrences of the alamust be evaluated in the context of other parameters. For Framer-based trunk

Component Severity Status<component_name>/<instance> minor/cleared set/clear

241-5701-500 4.1S1


ing

ate

DpnGateways, examples include link speeds, availability of other links, androuting/loadsharing algorithms. For ATM-based trunks, examples include ATMVCC PCR, effective cell rate, availability of other VCCs, and routing/loadsharalgorithms. If the more severe alarms are also issued, you will likely need toconsider re-engineering the links or ATM VCCs on this node in order to allevithe congestion conditions.



ver

d

lue

is the

theth

onlyw.eters

erued,e

7005 0111




When the status isset, the total average link or ATM VCC utilization has exceedethe values of themajorLinkUtilAlarmThreshold or majorVccUtilAlarmThresholdattributes respectively, for a sustained period of time.


For Framer-based trunks and DpnGateways, the total average link utilization calculated every minute based on comparing the number of bytes received bylink with the available bandwidth on the link. For ATM-based trunks, the totalaverage ATM VCC utilization is calculated every minute based on comparingnumber of cells received by the ATM VCC with the estimated available bandwidon the ATM VCC.

Probable Cause

Type

Remedial actionThe idea is that, with a proper threshold setting, a single instance of this alarmshould not require any special action although it would likely be a good indicatiof pending link or ATM VCC congestion. If this alarm is repeated over a relativeshort period of time, it may be an indication that the threshold setting is too loThe occurrences of the alarm must be evaluated in the context of other paramFor Framer-based trunks and DpnGateways, examples include link speeds,availability of other links, and routing/loadsharing algorithms. For ATM-basedtrunks, examples include ATM VCC PCR, effective cell rate, availability of othVCCs, and routing/loadsharing algorithms. If the more severe alarm is also isslikely you will need to consider re-engineering the links or ATM VCCs on this nodin order to alleviate the congestion conditions.

Component Severity Status<component_name>/<instance> major/cleared set/clear

241-5701-500 4.1S1


ver

d

lue

is the

theth

how

f thedks,

7005 0112




When the status isset, the total average link or ATM VCC utilization has exceedethe values of thecriticalLinkUtilAlarmThresholdorcriticalVccUtilAlarmThresholdattributes respectively, for a sustained period of time.


For Framer-based trunks and DpnGateways, the total average link utilization calculated every minute based on comparing the number of bytes received bylink with the available bandwidth on the link. For ATM-based trunks, the totalaverage ATM VCC utilization is calculated every minute based on comparingnumber of cells received by the ATM VCC with the estimated available bandwidon the ATM VCC.

Probable Cause

Type

Remedial actionWith a proper threshold setting, this alarm should cause a serious evaluation ofto alleviate the congestion conditions. Most likely, many packets are beingdiscarded which is obviously undesirable over the long term. The occurrences oalarm must be evaluated in the context of other parameters. For Framer-baseTrunks and DpnGateways, examples include link speeds, availability of other linand routing/loadsharing algorithms. For ATM-based trunks, examples includeATM VCC PCR, effective cell rate, availability of other VCCs, and routing/loadsharing algorithms.




lue

up

rmckup

,ed byl

on.

7005 0113



DetailsWhen the status isset, the measured speed of the trunk has dropped below the vawhich is specified by the attributelowSpeedAlarmThreshold attribute.

When the status isclear, the measured speed of the trunk has returned to orexceeded thelowSpeedAlarmThreshold value.

Probable Cause

Type

Remedial action1) For an elastic ATM trunk on a Passport 8-port DS1/E1 ATM FP with IMAfeature, this alarm can indicate that the bandwidth allocated to Trunk on IMA grohas been reduced.This will generally result from the removal or failure of the IMA links.Check the IMA alarms.

2) For an HDLC based trunk using third party Dial Backup equipment, this alacan indicate that the Trunk is running at a decreased speed provided by the Balines. This will generally result from leased line failure and backup lines beingdialed up. Check the operational mode of the Dial Backup equipment and theleased line connection.

3) For an HDLC-based trunk using third party Inverse Multiplexing equipmentthis alarm can indicate that the Trunk is running at a decreased speed providthe Inverse Multiplexing equipment. This will generally result from the removaor failure of links between the Inverse Multiplexing equipment. Check theoperational mode of the Inverse Multiplexing equipment and the link connecti

Component Severity Status<component_name>/<instance> warning/cleared set/clear

241-5701-500 4.1S1


e

len

ent,

on

,edge

7005 0114



DetailsWhen the status isset, the measured speed of the trunk has exceeded the valuwhich is specified by the attributehighSpeedAlarmThreshold attribute.

When the status isclear, the measured speed of the trunk has returned to or falbelow thehighSpeedAlarmThreshold value.

Probable Cause

Type

Remedial action1) For an HDLC-based trunk using third party Bandwidth on Demand equipmthis alarm can indicate that the trunk is running at an increased speed whenBandwidth on Demand occurs. Check the operational mode of the BandwidthDemand equipment and the leased line connection.

2) For an HDLC-based trunk using third party Inverse Multiplexing equipmentthis alarm can indicate that the Trunk is running at an increased speed providby the Inverse Multiplexing equipment. This will generally result from the addinlinks between the Inverse Multiplexing equipment. Check the operational modof the Inverse Multiplexing equipment and the link connection.

Component Severity Status<component_name>/<instance> warning/cleared set/clear



ifiede

e).

7005 0115


DetailsThis alarm is generated when a dial-in link becomes active. The followinginformation is attached:

- own component ID

- Comment data containing the following 2 lines:

Link type: <DBNL or BWOD>

Remote id: <PM/<names mnemonic> PE/<#> PI/<#> PO/<#>.

Probable Cause

Type

Remedial actionFor a dbnl link, the cause of the link failure at the remote end should be identand dealt with. When the dedicated link comes into service, this DBNL link will bdisabled automatically (if the DBNL Auto-Disable feature is active on the remotFor a BWOD link, no action is necessary.

Component Severity StatusDpnGate/<instance> indeterminate message

241-5701-500 4.1S1


ole.

7005 0116


DetailsThis alarm is generated when a dial-in link is deactivated. This could be due tautomatic disabling (DBNL), automatic deactivation (BWOD), or manual disabThe following information is attached:

- own component ID

- Comment data containing the following 2 lines:

Link type: <DBNL or BWOD>

Remote id: <PM/<names mnemonic> PE/<#> PI/<#> PO/<#>.

Probable Cause

Type

Remedial actionNot applicable.

Component Severity StatusDpnGate/<instance> indeterminate message



ortededivedble.

ext.

7005 0117



DetailsThis alarm is generated when the link speed (provided by the underlying linkprotocol) has exceeded the maximum speed supported by theTrunkcomponent.The value of themeasuredSpeedToInterfaceattribute (under theTrunkcomponent)and the speed reported to the routing system is replaced by the maximum suppspeed value. Although the speed has been adjusted to the maximum supportvalue, statistics can roll over prematurely if an excessive burst of data is receby theTrunkcomponent. At this point the statistics should be considered unrelia

When the status isclear, the link speed has fallen to or below the maximumsupported link speed.

Probable Cause

Type

Remedial actionLower the link speed to or below the trunk speed limit displayed in the alarm t

Component Severity Status<component_name>/<instance> major set/clear

241-5701-500 4.1S1


been

ty.

7005 0201


DetailsIf the status isset, a problem with neighbor checking has been detected. Manyconsecutive neighbor checks are missing. Communication with the remote hasdisrupted due to congestion or faults.

A clearwill be issued when theDpnGatewaycomponent successfully restages withthe remote.

Probable Cause

Type

Remedial actionVerify that theDpnGatewaycomponent is neither overloaded, congested or faul

Component Severity StatusDpnGateway/<instance> critical/cleared set/clear



o

e

7005 0202


DetailsIf the status isset, theDpnGatewaycomponent has detected that it is attempting tstage with anotherDpnGateway component.

TheDpnGatewaycomponent will attempt to restage in five minutes at which timaclear will be issued if it was successful.

Probable Cause

Type

Remedial actionVerify that the connection is with theDpnGatewaycomponent that matches the onein the provisioning file.


241-5701-500 4.1S1


o

e

7005 0203


DetailsIf the status isset, theDpnGatewaycomponent has detected that it is attempting tstage with a DPN-100 AM that is in Trunk mode.


Probable Cause

Type

Remedial actionCorrect the remote’s provisioning data to reflect that it is a Network Link.




o

e

7005 0204


DetailsIf the status isset, theDpnGatewaycomponent has detected that it is attempting tstage with a DPN-100 RM that is in Network Link mode.


Probable Cause

Type

Remedial actionCorrect the remote’s provisioning data to reflect that it is a Trunk.


241-5701-500 4.1S1


o

e

)

7005 0205


DetailsIf the status isset, theDpnGatewaycomponent has detected that it is attempting tstage with a DPN-50.


Probable Cause

Type

Remedial actionVerify that the connection is with a non-DPN-50 (for example, DPN-100 RM/AMmodule as specified in the provisioning data.




o

e

d is

7005 0206


DetailsIf the status isset, theDpnGatewaycomponent has detected that it is attempting tstage with an AM/RM that is not supported by Passport.


Probable Cause

Type

Remedial actionVerify that the connection is with a module which is supported by Passport, anas specified in the provisioning data.


241-5701-500 4.1S1


ing link

e

ed

7005 0207


DetailsIf the status isset, a problem with neighbor checking has been detected. Accordto information in the neighbor check packets, the neighbor has changed. Thewill restage with the new neighbor.

A clearwill be issued whenDpnGatewaycomponent successfully restages with thremote.

Probable Cause

Type

Remedial actionVerify that theDpnGateway component is connected to the expected neighbor.Follow-up with an investigation to discover why the neighbor identifiers changin an unexpected manner.




ing

e

lty.

7005 0208


DetailsIf the status isset, a problem with neighbor checking has been detected. Accordto information in the neighbor check frames, theDpnGateway component is nowlooped back to itself, likely due to a loop at physical layer.

A clearwill be issued whenDpnGatewaycomponent successfully restages with thremote.

Probable Cause

Type

Remedial actionVerify that theDpnGatewaycomponent is neither overloaded, congested nor fau


241-5701-500 4.1S1


or

7005 0301


DetailsIf the status isset, communication with the remote is lost because of congestionfaults.

A clear will be issued when the Trunk successfully restages with the remote.

Probable Cause

Type

Remedial actionVerify that the Trunk is neither overloaded, congested or faulty.

Component Severity StatusTrunk/<instance> critical/cleared set/clear



that

has

7005 0302


DetailsIf the status isset, the Trunk has discovered that the remote identification isdifferent from the one discovered during staging.

The component will immediately attempt to restage. As a result, the connectionwas provided to the routing system is discontinued.

A clear will be issued when the Trunk successfully restages with the remote.

Probable Cause

Type

Remedial actionDetermine if the connection to the remote component has been changed. If itchanged then make sure to update it to the ones used during staging.


241-5701-500 4.1S1


edsto

uting

entsk’s

7005 0303


DetailsIf the status isset, the number of supported address plan subcomponents excethe number of logical network numbers (LNN) that the Trunk’s protocol is ablestage.

Staging of the excessive address plans will not be attempted. As a result, the rosystem may not be provided with as much LNN connectivity as expected.

A clearwill be issued when the number of supported address plan subcomponno longer exceeds the number of logical network numbers (LNN) that the Trunprotocol is able to stage.

Probable Cause

Type


Component Severity StatusTrunk/<instance> warning/cleared set/clear



me

7005 0304


DetailsIf the status isset, the Trunk has discovered that it is attempting to stage withanother Trunk from another Passport in the same topology region with the sanode ID.

The Trunk will attempt to restage in five minutes at which time aclear will beissued if it was successful.

Probable Cause

Type

Remedial actionModify the local Node Id or the remote passport node ID to be unique.


241-5701-500 4.1S1


ckedany

7005 0305


DetailsIf the status isset, the Trunk has discovered that the remote Trunks has eitherattempted to restage or has been disabled.

The Trunk will attempt to restage immediately at which time aclearwill be issuedif it was successful.

Probable Cause

Type

Remedial actionIf the Trunk does not restage, verify the remote Trunk as it may have been loby an operator or disabled by the Routing System. If it is not obvious, examinealarms issued by the remote Trunk.




notigits.

does

other

7005 0306


DetailsThe status issetwhen the Trunk component detects that the remote trunk doesrecognize a 5-Digit instance value and this component has an instance with 5 dIt indicates that the value inremoteComponentName attribute of the remote trunkis incorrect.

A clear is issued when the trunk re-stages and discovers that the remote endsupport 5-digit Trunk instance value.

Probable Cause

Type

Remedial actionEither change the Trunk instance value to be less than 5 digits, or upgrade theend to support 5-digit Trunk instance range.


241-5701-500 4.1S1


is

ationimply

kerd.ourthe

7006 0001

Legend<type> = Telnet, Fmip or Ftp

DetailsAn NMIS connection was attempted from an unauthorized IP address. Theattempted connection was blocked. The source IP address of the connection shown in the comment field.

Probable CauseUnauthorized access

TypeSecurity

Remedial actionThis alarm may appear in two general scenarios.

First, the unauthorized IP address may be a legitimate network management stwhose IP address has not yet been provisioned on the Passport. In this case, sprovision anAccessControlIpAccess component with the new IP address.

Second, the unauthorized IP address may represent a hostile attack by a hacattempting to penetrate the Passport. Your network security may be threateneVerify that the source IP address is not a friendly address, or refer the alarm to ysystem administrator for investigation. It may be possible to trace the attack tosource computer by using the source IP address.

Component Severity StatusNmis <type> major message



d, andpting

ssivelarm

tonutether,

ible in the

7006 0002

Legend<type> = Telnet, Fmip, Local or Ftp

<n> = session number

DetailsA network management interface system (NMIS) login failed after three invaliuserId and password attempts. The attempted session is frozen for two minutesthen terminated. The last userId entered and the IP address of the node attemthe login are shown in the comment field.

Probable CauseAuthentication failure

TypeSecurity

Remedial actionThis alarm may appear in two general scenarios.

First, a legitimate user may have incorrectly entered the password three succetimes. If you can determine that the alarm was caused by a legitimate user, the amay be ignored.

Second, a hostile password attack may be underway by a hacker attempting penetrate the Passport. Your network security may be threatened. The two-misession freeze will slow the password attempts. To frustrate the attack even furconsider issuing a Lock command on the interface used in the attack,or refer the alarm to your system administrator for investigation. It may be possto trace the attack back to its source by the userId and the IP address showncomment field.

Component Severity StatusNmis <type> Session/<n> warning message

241-5701-500 4.1S1


ctionle

it is00%esidethe

teredhuts

7006 0003

Legend<type> = Telnet, Fmip, or Ftp<n> = session number

DetailsA TCP connection into network management interface system (NMIS) failed,causing the session to terminate. It is possible to identify the node whose connefailed by the IP address shown in the comment field. There are several possibcauses for this situation, all relating to a TCP/IP read/write failure. Some are:

The NMIS session was killed without using the logoff command.

The remote site has crashed.

The IPIVC connection has failed, causing all sessions on that IPIVC to crash.

Preside Multiservice Data Manager checks the Passport continually to see if operational. Under severe congestion conditions, or if the Passport CPU is at 1capacity, it does not send a response to Preside Multiservice Data Manager. PrMultiservice Data Manager then closes its side of the connection, thus killing FMIP session.

If the Passport is isolated (no trunks connecting to it), the session is not regisfor alarms, and the workstation has the TCP/IP keep alive option, the session sdown after two hours.

Probable CauseLoss of Signal

TypeCommunications


Component Severity StatusNmis <type> Session/<n> major message



e

he

ks

7006 0004

Legend<severity> = one of major, minor or warning

DetailsAn FMIP protocol error has occurred. The alarm is typically associated with acommand and the response to that command contains further information.

The command may have failed completely, or have been partially executed.

A major severity indicates software errors, whileminor andwarning severity areindicative of Preside Multiservice Data Manager workstation/Passport softwarversion incompatibilities.

There may exist comment text with further information.

Probable Cause

Type

Remedial actionTypically, the Preside Multiservice Data Manager Workstation and Passportsoftware are running incompatible versions. It may be necessary to upgrade tsoftware on the Preside Multiservice Data Manager Workstation.

If upgrading the software does not eliminate the alarm, contact Nortel Networglobal support.

Component Severity StatusNmis Fmip <severity> message

241-5701-500 4.1S1


n IPn is

ninge

an

.n.nthe

ice.

pied,

re-

eral

7006 0005

LegendNone.

DetailsAn FTP connection to the Active CP has been attempted from a local 127.n.n.address on one of the FPs. The connection was blocked. The FTP connectiotypically established for an eprom firmware upgrade.

The FTP connection may be blocked for two reasons. The Passport may be runlow on memory needed to set up the FTP session, or the FTP interface may blocked (not the case for Migration CP) or busy. Refer to the comment field forindicated cause for blocking the connection.

Note that this alarm is generated only for FTP connections from a local 127.nIP address on the Passport itself, and not from general IP addresses outside Passport.


TypeProcessing

Remedial actionIf the FTP interface is locked, issue the Unlock command to enable FTP serv

If the FTP interface is busy because all allowable sessions are currently occutry to finish an FTP session, log off, and free it for reuse.

If CP heap memory is too low, the Passport may have to be re-engineered orprovisioned to free up more heap.

Note that the eprom upgrade mechanism will re-attempt the FTP connection sevtimes after the first alarm appears. Therefore, any attempt to unblock the FTPinterface as soon as possible is useful.

Component Severity StatusNmis Ftp Prov Migration major message



thathisnodets

7006 0006

LegendNone.

DetailsNine consecutive invalid login attempts have been made to establish an FMIPsession.

This is probably caused by a Preside Multiservice Data Manager workstation is continuously trying to establish a session with an invalid userid/password. Tslows down response time considerably on the switch. The IP address of the trying the login and userid for the last failed attempt are shown in the commenfield.

Probable CauseAuthentication failure

TypeSecurity

Remedial actionIdentify and stop the source attempting the continuous login. The IP addressincluded in the alarm’s comment field and the userid will help.

Component Severity StatusNmis Fmip major message

241-5701-500 4.1S1


ecordted

rk to

7006 0007

Legend<type> = Telnet, Fmip or Ftp

<n> = session number

DetailsAn NMIS session is automatically terminated, generating this alarm, when thesession is registered for a data stream (alarms, SCNs, logs, or debug) and the rcould not be output within 1 min 30 s.The IP address of the remote host is indicain the comment field.

Possible causes:

The Passport is isolated (no trunks connecting to it) and the connection notrecovered within 1 min 30s.

The network is extremely congested, causing the writing of data to the netwotake more than 1 min 30 s.


TypeCommunications


Component Severity StatusNmis <type> Session/<n> major message



ssionIP

7006 0008

Legend<type> = Fmip

DetailsThis alarm is generated if a corrupted message is sent to NMIS, causing the seto terminate. It is possible to identify the node whose connection failed from theaddress shown in the comment field.


TypeCommunications


Component Severity StatusNmis <type> major message

241-5701-500 4.1S1


tmble

the

led

d by

entator

y the

7007 0000


DetailsThis alarm is generated if there is a DLCI in a troubled condition under the FrAInterface. A troubled condition exists when there is not enough bandwidth availafor a DLCI on a FrAtm interface. This condition must be cleared before aconnection can be enabled. The alarm is set only once when the initial DLCI oninterface experiences this troubled condition.

The alarm is cleared when all the DLCIs on the interface are no longer in a troubcondition.

Probable Cause

Type

Remedial actionDetermine amount of bandwidth and the bandwidth pool that is being requestethe connection by displaying theequivalentBitRate andassignedBandwidthPoolattributes respectively, under the interworking function. Ensure there is sufficibandwidth to accommodate the request by displaying the Connection Administr(CA).

Increase the percentage of bandwidth allocated in the bandwidth pool used btroubled DLCI.

If CAC is not required, then it can be turned off.

Component Severity StatusFrAtm/<instance> minor/cleared set/clear



ne.

ns

ager for

ate.

7007 1000

Legend<FrameRelay>=FrUni or FrNni or FrMux or FrAtm


DetailsThis alarm isset when the number of frame relay Local Management Interface(LMI) procedure errors within the lasteventCount events has exceeded theerrorEventThreshold attribute. (Both theeventCount anderrorEventThresholdattributes are provisionable.) In this situation, the local interface is declared insaFor FrUni, FrNni andFrAtm components, both the local and remote userequipment are signalled by the LMI asynchronous status report message ifasynchronous notification is supported at their local interface. For theFrMuxcomponent, all local Applications are signalled. Data transfer for all connectioassociated with the local DLCIs is suspended.

A clear is issued after a fixed number (provisioning parameter) of correct messexchanges between the inter-operating LMI entities has occurred. Data transfeall connections associated with the local DLCIs is resumed.

Probable Cause

Type

Remedial actionVerify that the other side of the interface has the LMI protocol enabled. Verify ththe LMI parameters set on the other side are compatible with those on this sidTurn off the LMI protocol if the other side does not support the LMI protocol.

Component Severity Status<FrameRelay>/<instance> LMI critical/cleared set/clear

241-5701-500 4.1S1


e.

imalrmentitialnts

ing

7007 2000

Legend<x> = a decimal digit (0 to 9)

<FrameRelay> = FrUni or FrNni


DetailsThis alarm occurs when the frame relay Local Management Interface (LMI)receives a report from an adjacent network that a PVC(s) has become inactiv

The PVCs that are reported inactive by the adjacent network are listed in decformat by DLCI value as part of the comment for this alarm. Each 7007 200x alareports a maximum of 112 PVCs. If more than 112 PVCs on a single componbecome inactive, multiple 7007 200x alarms are issued. The value ‘x’ has an invalue of ‘0’ and is incremented by one for each alarm. FrUni or FrNni componeonly generate this alarm when the LMIpvcAlarmsReporting attribute is set toexternalor both. The default value for thepvcAlarmsReportingattribute isexternal.

Probable Cause

Type

Remedial actionCheck the PVC connection associated with the DLCI value reported in the warnmessage.



alrmentitialnts

7007 2010




DetailsThis alarm occurs when the frame relay Local Management Interface (LMI)receives a report from an adjacent network that a PVC(s) has become active.

The PVCs that are reported active by the adjacent network are listed in decimformat by DLCI value as part of the comment for this alarm. Each 7007 201x alareports a maximum of 112 PVCs. If more than 112 PVCs on a single componbecome active, multiple 7007 201x alarms are issued. The value ‘x’ has an invalue of ‘0’ and is incremented by one for each alarm. FrUni or FrNni componeonly generate this alarm when the LMIpvcAlarmsReporting attribute is set toexternalor both. The default value for thepvcAlarmsReportingattribute isexternal.

Probable Cause

Type


241-5701-500 4.1S1


rts

matortsomeof

y

d in

7007 2020




DetailsThis alarm occurs when the frame relay Local Management Interface (LMI) repothat a PVC(s) in the local network has become inactive.

The PVCs that are reported inactive in the local network are listed in decimal forby DLCI value as part of the comment for this alarm. Each 7007 202x alarm repa maximum of 112 PVCs. If more than 112 PVCs on a single component becinactive, multiple 7007 202x alarms are issued. The value ‘x’ has an initial value‘0’ and is incremented by one for each alarm. FrUni or FrNni components onlgenerate this alarm when the LMIpvcAlarmsReportingattribute is set tointernalorboth. The default value for thepvcAlarmsReporting attribute isexternal.

Probable Cause

Type

Remedial actionCheck both ends of the PVC connection associated with the DLCI value reportethe warning message in the local network.



rts

atortsome of

y

7007 2030




DetailsThis alarm occurs when the frame relay Local Management Interface (LMI) repothat a PVC(s) in the local network has become active.

The PVCs that are reported active in the local network are listed in decimal formby DLCI value as part of the comment for this alarm. Each 7007 203x alarm repa maximum of 112 PVCs. If more than 112 PVCs on a single component becactive, multiple 7007 203x alarms are issued. The value ‘x’ has an initial value‘0’ and is incremented by one for each alarm. FrUni or FrNni components onlgenerate this alarm when the LMIpvcAlarmsReportingattribute is set tointernalorboth. The default value for thepvcAlarmsReporting attribute isexternal.

Probable Cause

Type


241-5701-500 4.1S1


nse

theen

r use

d.

7007 2100


DetailsThis alarm is generated at the Frame Relay NNI after two attempts to send aRESTART message to the adjacent Frame Relay NNI fail to result in a respowith a RESTART ACKNOWLEDGE message.

A restart request is sent out under certain conditions. This alarm is required forinterface to realize that attempts to synchronize the adjacent NNI have not beacknowledged. In compliance with procedures for restarts defined in the X.76standard, the sender of the restart request can consider its interface available foat this point. However, since no response indicates a possible lack ofsynchronization between the two adjacent NNIs, this warning is provided.

Probable Cause

Type

Remedial actionEnsure that all switched DLCIs on the adjacent Frame Relay NNI are release

Component Severity StatusFrNni/<instance> minor message



tart.userI.

7007 2101


DetailsThis alarm is generated when the Frame Relay NNI is being requested to resSince a RESTART message can be received at any time, this alarm notifies thethat the FR NNI is being requested to restart by the adjacent Frame Relay NN

Probable Cause

Type

Remedial actionNo action required.


241-5701-500 4.1S1


larmT

itsdure.

7007 2102


DetailsThis alarm is generated when the Frame Relay NNI is being restarted. This anotifies the user that the FR NNI is being restarted after receiving a RESTARACKNOWLEDGE message from the adjacent Frame Relay NNI, in response toRESTART message. This alarm also indicates completion of the restart proce

Probable Cause

Type


Component Severity StatusFrNni/<instance> warning message



the

ageeRTtart

7007 2103


DetailsThis alarm is generated as a warning that the T317 timer has expired withoutFrame Relay NNI receiving indication that the internal clearing has beencompleted. Timer T317 is started when the FR NNI receives a RESTART messfrom the adjacent FR NNI, and it enters the Restart state. The indication of thinternal clearing prompts the FR NNI to stop the T317 timer and send a RESTAACKNOWLEDGE message to the adjacent FR NNI, thereby completing the resprocedure.

Probable Cause

Type



241-5701-500 4.1S1


the

notelay

Iteo

7007 2104


DetailsThis alarm is generated as a warning to indicate that a configured mismatch inDLCI range of adjacent Frame Relay NNIs could be the cause of calls beingrejected. This alarm indicates that the DLCI ranges on adjacent FR NNIs havebeen set according to the recommendations defined in the Passport Frame RNNI Switched Connection configuration procedures.

Probable Cause

Type

Remedial actionEnsure that thehighestPvcDlci attribute (under theFrNni Sig component) onadjacent FR NNIs is set to the same value. Furthermore, ensure that the DLCallocation strategies on adjacent NNIs are opposite. If one NNI is set to allocaswitched DLCIs from lowest-to-highest, its adjacent NNI must be configured tallocate switched DLCIs from highest-to-lowest.




rThe

re

7007 2200

Legend<n> = instance of FrUni or FrNni

DetailsThe status issetwhen a FrUni/FrNni fails registration with the frame relay IP serve(FRIP) because its associated IP address is already registered on that FRIP. correct configuration is that eachBnxProtocol component linked to a FRIP has aunique IP address under that FRIP.

A clear is issued when the operator redefines the IP addresses so that they aunique and activates the configuration view.

Remedial actionFor allBnxProtocol components linked to the same FrIpServer, verify that eachipAddress attribute defines a unique IP address.

Component Severity StatusFrUni/<n> BnxProtocolFrNni/<n> BnxProtocol

major/cleared set/clear

241-5701-500 4.1S1


nedtheeyen

7007 3000

Legend<FrameRelay> = FrUni or FrNni or FrMux or FrAtm


DetailsThis alarm is generated when the Frame Relay service fails to add a provisiodata link connection identifier (DLCI) subcomponent. This may happen when total number of provisioned DLCIs has exceeded the engineering limit, and thFrame Relay service cannot allocate the resources required. The Frame Relaservice itself does not explicitly check for whether the engineering limit has beexceeded.

Probable Cause

Type

Remedial actionRe-engineer the function processor (FP) by moving the affected Frame Relayservice to another access line and copy over the required DLCIs again. If theproblem persists contact Nortel Networks global support.

Component Severity Status<FrameRelay>/<instance> minor message



n isut of

7007 3001

Legend<FrameRelay> = FrMux


DetailsThis alarm occurs when the aggregated CIRs of current registered DLCIs aregreater than link speed.

Probable Cause

Type

Remedial actionIf running in oversubscribing mode is done on purpose, then no remedial actioneeded. In this case, however, the user should be aware that effective throughpany DLCI may be lower than the provisioned CIR.

Otherwise, re-configure the FP so as to avoid oversubscription.

Component Severity Status<FrameRelay>/<instance> minor message

241-5701-500 4.1S1


rn

ek

,

7007 4000

Legend<FrameRelay> = FrUni or Mpanl


<Signaling> = Sig, or when <FrameRelay> = Mpanl, SigMpanl

DetailsThis alarm issetif the Frame Relay Switched Virtual Circuit (SVC) data link layeis down and cannot be used for SVC signaling, or if MPANL data link layer is dowand cannot be used for MPANL signaling. If the port is enabled and the FramRelay or MPANL service is not locked it will attempt to bring up the SVC data linlayer continually.

A clear will be issued if the data link layer returns to state informationTransferwhere it will again be ready to process SVC or MPANL signaling.

Probable Cause

Type

Remedial actionVerify that the cabling to the port is correct. Verify that the Frame Relay orMPANL service and the port are both unlocked and enabled. Verify that theconnected device is operating correctly.

Component Severity Status<FrameRelay>/<instance> <Signaling> critical/cleared set/clear



hedh

orey.

7007 4001

Legend<FrameRelay> = FrUni or Mpanl



DetailsThis alarm is issued if the length of the transmit queue at the Frame Relay SwitcVirtual Circuit (SVC) or MPANL data link layer has exceeded the queue lengtthreshold. The queue is purged.

Probable Cause

Type

Remedial actionThe access data rate for the Frame Relay or MPANL service may not be highenough to support the Frame Relay traffic from the network as well as the SVCMPANL signaling traffic. Verify whether there is congestion for traffic going to thport. Traffic re-engineering may be necessary if this alarm is issued frequentl

Component Severity Status<FrameRelay>/<instance> <Signaling> major message

241-5701-500 4.1S1


tuallink

linked in

e hasect

ling

thece.

7007 4002

Legend<FrameRelay> = FrUni or SigMpanl



DetailsThis alarm is issued if one or more unacknowledged Frame Relay Switched VirCircuit (SVC) or MPANL signaling frames have been purged because the datalayer was reset by either the network or the user side. The reason for a user sidereset is because an unnumbered acknowledgment (UA) frame has been receivstate linkSetup, a set asynchronous balanced mode extended (SABME) frambeen received in state informationTransfer or state waitingAck, or a frame rejframe (FRMR) has been received. The reason for a network side link reset isbecause of invalid receive sequence number (NR) received or invalid framereceived in state informationTransfer.

This alarm is not issue after a link reset if there has been no loss of SVC signaframes.

Probable Cause

Type

Remedial actionFrequent issuance of this alarm indicates a possible configuration error. Verifydata link layer parameters (the timers in particular) at both sides of the interfa

Component Severity Status<FrameRelay>/<instance> <Signaling> minor message



ta

kvity,ive

tor

7007 5000

Legend<FrameRelay> = FrUni, FrNni, or Mpanl


DetailsThis alarm is issued when the Data Link Connection Identifier (DLCI) is set to DaLoopback state by an operator command issued on theloopBacksubcomponent ofthe DLCI. When the DLCI is in this state, traffic sent over this DLCI is looped bacto its source. This state is used for test purposes only: to test PVC/SVC connectipre-installation, and load testing. The DLCI must not be expected to support lproduction traffic in this state.

This alarm is cleared when the DLCI is out of Data Loopback state, by an operacommand issued on theloopBack subcomponent of the DLCI. Traffic over thisDLCI is now sent as normal.

Probable Cause

Type

Remedial actionNo action needed. The alarm simply provides a tracking mechanism, to allownetwork operators know what DLCI’s are currently in Data Loopback state.

Component Severity Status<FrameRelay>/<instance> Dlci/<instance> warning set/clear

241-5701-500 4.1S1


ne

7007 5100


DetailsThis alarm is issued when a subconnection is cleared by the Multiservice cut-through switching because the requested DLCI is already in use.

Probable Cause

Type

Remedial actionChange the provisioning to remove the duplicate use of the DLCI. To determiwhat access component is using the DLCI, display theaccessConnectionComponentattribute underMcs frf5Group/<instance> EndPoint<instance> DLCI/<instance> component.

Component Severity StatusFrAtm/<instance> Dlci/<instance> Niwf warning message



other

t be

7007 5101


DetailsThis alarm is generated when a Master end receives a setup message from anMaster.FrAtm/<instance> Dlci/<instance> Siwf SPvcis provisioned at both endsof the intended connection.

Probable cause

Type

Remedial actionOne end must be provisioned asFrAtm/<instance> Dlci/<instance> Siwf SPvcwhich makes that end the Master end. The remote end for this connection musprovisioned asFrAtm/<instance> Dlci/<instance> Siwf. This makes this end of theconnection the Slave end.

Component Severity StatusFrAtm/<instance> Dlci/<instance> Siwf warning message

241-5701-500 4.1S1


o notality

der

lues.

7007 5102


DetailsThis alarm is generated when quality of service parameters being negotiated dmatch the called end of a FR-ATM connection. There may be an unexpected quof service behavior observed.

Probable Cause

Type

Remedial actionCheck quality of service parameters on both sides of the FR-ATM connection unthe interworking function and verify that they are equivalent. If there is adiscrepancy, ensure that the connection is obtaining the correct provisioned va

Component Severity StatusFrAtm/<instance> Dlci/<instance> Siwf minor message



tion).

7007 5103


DetailsThis alarm is generated when an originating call is trying to establish a connecand fails due to a busy condition (connection already enabled and being used

Probable Cause

Type

Remedial actionCheck your FR-ATM connections to ensure that the correct values have beenprovisioned for theremoteAddressandremoteConnectionIdentifierattributes at theoriginating end. Choose aremoteConnectionIdentifier value (DLCI) that is notbeing used.

Component Severity StatusFrAtm/<instance> Dlci/<instance> Siwf minor message

241-5701-500 4.1S1


eenis

elay

7007 6000

Legend<FrameRelay> = FrMux


DetailsThis alarm occurs when FrMux Local Management Interface (LMI) receives areport from the Third Party Frame Relay network indicating a new PVC has badded for which no application is provisioned. The Dlci value for this new PVCindicated in decimal format as part of the comment for this alarm.

Probable Cause

Type

Remedial actionCheck the PVC connection indicated in this alarm in the Third Party Frame Rnetwork connected to the FrMux that raised this alarm.

Component Severity Status<FrameRelay>/<instance> warning message



meted

7007 7001


DetailsThis alarm is issued when the MPA signals an out of bounds maximum VoFr frasize and it is substituted by the closest valid limit value. Signalled and substituvalues appear in comment text.

Probable Cause

Type

Remedial actionThe alarm is likely indicative of incorrect provisioning on MPA. Correct theprovisioning and activate the Mpanl.

Component Severity StatusMpanl/<instance> VoFr warning message

241-5701-500 4.1S1


andes

7007 7002


DetailsThis alarm is issued when the MPA signals an out of bounds receive bandwidth,it is substituted by the closest valid limit value. Signalled and substituted valuappear in comment text.

Probable Cause

Type

Remedial actionThe alarm is likely indicative of incorrect provisioning on MPA. Correct theprovisioning and activate the Mpanl.

Component Severity StatusMpanl/<instance> VoFr warning message



n

d tom

e33

hedpe

7007 8000


DetailsThis alarm issetwhen the MPANL service has not received any Profile Associatiocommand from MPA since the LAPF layer on DLCI-16 has been established.Default values shall be assumed for this interface, and Q.933 calls are alloweproceed. Aclear is issued when the Profile Association command is received froMPA.

Thissetalarm may also be indicative that a prefix DNA previously issued from thMPA has been deregistered by the Passport MPANL service, resulting no Q.9calls to arrive at the MPA.

Probable Cause

Type

Remedial actionThe alarm is probably indicative that there are software problems with the attacMPA. If MPA is operating at a software level of deployment quality, then a scotrace may be needed to ascertain that a syntactically well-formatted ProfileAssociation command has actually been initiated by MPA.

Component Severity StatusMpanl/<instance> SigMpanl minor set/clear

241-5701-500 4.1S1


t to

was

7007 8001


DetailsThis alarm is generated when the MPANL service is unsuccessful in its attempderegister its prefix DNA with the FDCR agent.

Probable Cause

Type

Remedial actionThis alarm indicates that there may be a memory/engineering issue since heapnot available to deregister the prefix DNA.

Component Severity StatusMpanl/<instance> SigMpanl warning message



fterly.

to

7007 8002


DetailsThis alarm indicates that the MPA has attempted to associate a prefix DNA ahaving already successfully associated and registered a prefix DNA previous

Probable Cause

Type

Remedial actionThe MPA must first de-associate its registered prefix DNA before attempting associate an alternate prefix DNA.


241-5701-500 4.1S1


t isx

7007 8003


DetailsThis alarm indicates that the MPA has attempted to associate a prefix DNA thatoo long or too short (that is, greater than 15 digits, or with no digits). No prefiDNA will be registered.

Probable Cause

Type

Remedial actionThe MPA must send a prefix DNA association command, with a prefix DNAhaving at least one digit but no more than 14 digits long.




p

.

7008 1001

LegendNone.

DetailsThe file system disk space usage is above 85% of its total capacity.

Probable CauseStorage capacity problem

TypeProcessing

Remedial actionRemove some files from the disk immediately to prevent the file system frombecoming full to avoid the risk of lost data. The active disk must be cleaned uimmediately by doing one or more of the following:

- tidy the provisioning data

- tidy the software files

- off-load spooled data

A clear will be issued when the used space is below 75% of the disk capacity

Component Severity StatusFs warning/cleared set/clear

241-5701-500 4.1S1


k

7008 1002

LegendNone.

DetailsThe file system disk is 100% full. This will cause service to be affected.

Probable CauseStorage Capacity

TypeProcessing

Remedial actionThe active disk must be cleaned up immediately by doing one or more of thefollowing:

- tidy the provisioning data

- tidy the software files

- off-load spooled data

A clear will be issued when the disk space usage is below 90% of the total discapacity.

Component Severity StatusFs major/cleared set/clear



y

tory

7008 1003

LegendNone.

DetailsThe root directory “/” is full. The number of directories or files in the root director“/” has reached the maximum allowed (112 files and directories).


TypeProcessing

Remedial actionRemove some files or directories in the root directory. Nortel Networksrecommends that files be placed in subdirectories rather than in the root direc(The root directory should only contain directories).

Component Severity StatusFs major message

241-5701-500 4.1S1


be

st beost

7008 1004

LegendNone.

DetailsThe file system is disabled and therefore cannot be accessed. This alarm willcleared when the file system is accessible again. However, this is not likely tohappen until the control processor card is reset.

Probable CauseIO device error

TypeEquipment

Remedial actionReset the active control processor card. This action is service-affecting and mudone with caution. If the problem persists, return the card to manufacturer. The mlikely cause is a bad disk.




he

y

you

ith a

7008 1005

LegendNone.

DetailsThe synchronization of the standby disk to the active disk has failed. Among tpossible causes are:

- the disks have different volume names

- there is insufficient standby disk capacity

- the standby disk is locked or disabled

A clear will be issued when the synchronization succeeds.


TypeEquipment

Remedial actionDisplay the disk attributes and check if the volume names are the same. If thediffer re-synchronize the two disks manually.

If the standby disk is locked, unlock it and re-synchronize manually.

If the standby disk is disabled, reset the standby card.

If the standby disk capacity is less than the used disk space on the active disk,may have to remove files on the active disk by issuing atidy prov or atidy swcommand or alternatively you may have to upgrade your control processor wlarger disk.

Component Severity StatusFs minor/cleared set/clear

241-5701-500 4.1S1


7008 1006

LegendNone.

DetailsThe file system has too many open files.


TypeProcessing

Remedial actionContact Nortel Networks global support.




), the

7008 1008

Legend<instance> = 0, 15

DetailsA read/write has error occurred on the active disk causing the disk to becomeunavailable. If the system has a synchronized standby control processor (CPfaulty disk will have its CP rebooted.

Probable CauseEquipment failure

TypeEquipment


If this error occurs frequently, run the disk tests on the faulty disk. See241-5701-605Passport 7400, 15000, 20000 User Access Guide, for a descriptionof possible disk tests.

Component Severity StatusFs Disk/<instance> major/cleared set/clear

241-5701-500 4.1S1


7008 1009


DetailsA disk media error test has found a read/write error in the disk boot area.

A clear will be issued when the disk is replaced.


TypeEquipment

Remedial actionReturn the card to the manufacturer.




d the

7008 1010


DetailsA disk surface analysis test has found bad clusters. They were re-mapped anvolume has been re-initialized. This alarm clears after resetting the card.


TypeEquipment

Remedial actionReset the card. If the problem persists return the card to the manufacturer.


241-5701-500 4.1S1


ed.

7008 1011


DetailsA disk media test has found errors. This alarm will be cleared when the disk is fix


TypeEquipment

Remedial actionRun thefilesystemCheck teston the faulty disk. See 241-5701-605Passport 7400,15000, 20000 User Access Guide, for a description of thefilesystemCheck test.




. No

7008 1012


DetailsThe file system check test has found some integrity errors and corrected themdata is lost.


TypeEquipment

Remedial actionIf the file system has a standby control processor, synchronize the file systemimmediately.

Component Severity StatusFs Disk/<instance> major/cleared message

241-5701-500 4.1S1


ta

7008 1013


DetailsThefilesystemCheck testhas found some integrity errors and fixed them. Some dais lost.


TypeEquipment

Remedial actionIf the file system has a standby control processor, synchronize the file systemimmediately.

Component Severity StatusFs Disk/<instance> major message



to the

7008 1014


DetailsA disk test failed to complete and the cause is unknown.


TypeUnknown

Remedial actionReset the card and run the test again. If the problem persists return the card manufacturer.

Component Severity messageFs Disk/<instance> major message

241-5701-500 4.1S1


ntrol

7008 1015


DetailsAn operation on the standby disk did not complete as expected. The standby coprocessor is rebooted and synchronizes automatically.


TypeUnknown

Remedial actionNo action is required.

Component Severity StatusFs Disk/<instance> major message



d the

7008 1016


DetailsA communication error has occurred between the active control processor anstandby control processor. The standby control processor is rebooted andsynchronizes automatically.


TypeUnknown

Remedial actionNo action is required. If the problem persists, contact Nortel Networks globalsupport.

Component Severity StatusFs Disk/<instance> minor message

241-5701-500 4.1S1


7008 1017


DetailsThe Disk component is locked.

A clear will be issued when the disk is unlocked.

Probable Cause

Type

Remedial actionUnlock the Disk component.

Component Severity StatusFs Disk/<instance> minor/cleared set/clear



ntrol

7008 1018


DetailsThe periodic disk access test has not received a response from the disk. The coprocessor with the failed disk will be reset.


TypeOperator


Component Severity StatusFs Disk/<instance> minor message

241-5701-500 4.1S1


d,

ize

bal

7008 1019

LegendNone.

DetailsThe File system is no longer synchronized for one of the following reasons:

- the standby disk is locked

- one disk is full

- the standby disk has been reset

- device can not be opened or closed

- controlling functions can not be performed on device


TypeEquipment

Remedial actionDisplay the disk’s attributes and check if the standby disk is locked. If it is lockeunlock it using theunlock command, and re-synchronize the software.

If the disk is full, clean up the disk by issuing atidy sw(for software files) or atidyprov command (for provisioning data) and re-synchronize.

If the standby disk resets, no action is required. The filesystem will re-synchronautomatically when the active disk becomes available.

If the device can not be opened or closed, it should be changed.

If the controlling functions can not be performed, contact Nortel Networks glosupport.

Component Severity StatusFs minor/cleared set/clear



temly,f

tiate

7008 1020

LegendNone.

DetailsThis alarm indicates that disk synchronization has failed due to heavy file sysactivity. The system will attempt to re-initiate disk synchronization automaticalto a maximum of 3 attempts. The alarm message also indicates the number osynchronization attempts made.


TypeEquipment

Remedial actionIf all three automatic synchronization attempts are unsuccessful, you must inidisk synchronization manually.

Component Severity StatusFs minor message

241-5701-500 4.1S1


odeled.is

de.

7009 0202

LegendNone.

DetailsA neighbor node, in the host node’s routing area, is provisioned with the same nidentifier as the host node. The trunk between them will be automatically disabIf this alarm occurs, it could indicate a problem with the trunk system, since thsituation should be alarmed as 7005 0304.

Probable Cause

Type

Remedial actionReprovision either this node’s identifier or the node identifier of the remote no

Component Severity StatusRtg Top critical message



The

7009 0203

LegendNone.

DetailsThis component has received a routing control packet from a neighbor noderequesting a link state update for a node not in the host’s topological database.trunk will be automatically restaged and the databases re-synchronized.

Probable Cause

Type


Component Severity StatusRtg Top warning message

241-5701-500 4.1S1


n be

7009 0205

LegendNone.

DetailsThe Passport network has reached the maximum number of nodes, which caconfigured in a routing area.

No more nodes can be configured in this area.

Probable Cause

Type


Component Severity StatusRtg Top warning message



26

e

7009 0208

LegendNone

DetailsThe number of unique Logical Networks provisioned has exceeded the limit of 1per network.

This alarm indicates that routing within some of the logical networks will not breliable.

Probable Cause

Type

Remedial actionRemove Logical Networks until there are 126 or less in the network.

Component Severity StatusRtg Top major message

241-5701-500 4.1S1


been

one

ince

7009 0209

LegendNone.

DetailsAnother node which is using the same node id and/or the same node name hasdetected in the network. This situation will lead to faulty routing and increasedcontrol traffic throughout the network.

Probable Cause

Type

Remedial actionFind the other node in the network with the same id and/or name, and changeof the two.

Note that this is easy to do if all nodes are running software with this alarm, sthey will all be generating alarms for this condition.

Component Severity StatusRtg Top major message



sportenork its

be

7009 0210

LegendNone.

DetailsThe host node detects that there have already been maximum number of Pasnodes in a network while more Passport nodes still try to join in the network. Whthis alarm is seen, the host node may not have the complete view of the netwtopology because the host node can only store maximum number of nodes intopological database.

Probable Cause

Type

Remedial actionContact Nortel Networks global support, the Passport software may needs toupgraded.


241-5701-500 4.1S1


oupon.

7009 0211

LegendNone.

DetailsIf a node has been staging with a neighbour for more than 10 minutes, the link grto the neighbour is brought down and an alarm is raised to indicate the situati

Probable Cause

Type

Remedial actionIf the problem persists, contact Nortel Networks global support.




port

sent

7009 0302

LegendNone.

DetailsA trunk/gateway has been brought up which would exceed the capacity of TransResource. Up to 1023 trunks/gateways can be handled.

Probable Cause

Type

Remedial actionRemove a trunk/gateway running on an FP so that the total number that are preon active FPs is less than 1024.

Component Severity StatusTrm warning message

241-5701-500 4.1S1


so

7009 0303

LegendNone.

DetailsA trunk/gateway has been brought up to a new neighbor module which wouldexceed the 255 neighbor modules limit.

Probable Cause

Type

Remedial actionBring down a trunk/gateway to the new neighbor or an existing neighbor modulethat the total number of neighbors is less than 256.




oror 4

a.eateotn

7009 0304

LegendNone.

DetailsA trunk/gateway has been brought up which is the fifth link to an existing neighbmodule. Four other links exist and are active to that neighbor. Up to 4 trunks gateways can belong to the same link group.

Probable Cause

Type

Remedial actionDisable the trunk/gateway. If this link is really desired in the link group, issue ‘LIST trm lg <neighbor node name>’ to find out which links are in the link groupDisable one of them with the ‘LOCK’ command on the link component. Allow thnew trunk/gateway to come up. It is possible to keep a fifth link in an unlocked stbetween two modules, but it will not be admitted to the link group and thus will ncarry traffic. If an existing link in the link group then goes down, this idle link cabe admitted.


241-5701-500 4.1S1


ated

for

7009 0305

Legend<m> = linkGroup/mnemonic

<n> = 1 - 1023

DetailsIf the status is set, the specified link in the link group is detected to be neitherthroughput nor delay preferred for loadsharing and the link is not 100% dedicto pors.

A clear will be issued when this link goes down or the link becomes preferredloadsharing.

Probable Cause

Type

Remedial actionEngineering study is required to determine why the link is non-preferred, andwhether it is appropriate to add the link in the link group.

Component Severity StatusTrm linkGroup/<m> link/<n> minor/critical set/clear



ated

for

7009 0306

Legend<m> = 1 - 255

<n> = 1 - 1023

DetailsIf the status is set, the specified link in the link group is detected to be neitherthroughput nor delay preferred for loadspreading and the link is not 100% dedicto PORS.

A clear will be issued when this link goes down or the link becomes preferredloadspreading.

Probable Cause

Type

Remedial actionEngineering study is required to determine why the link is non-preferred, andwhether it is appropriate to add the link in the link group.

Component Severity StatusTrm linkGroup/<m> link/<n> minor/critical set/clear

241-5701-500 4.1S1


ging

rycur

7009 0307

LegendNone.

DetailsThis indicates a situation in which Transport Resource has received an LNN stapacket from an unknown neighbour node with the indicated node name.

Probable Cause

Type

Remedial actionThis alarm occurs infrequently under normal conditions. The node will recoveautomatically and the alarm should cease to occur. If these alarms start to ocfrequently, contact Nortel Networks global support.




toentries.

CP.

atus

7009 0310

LegendNone.

DetailsIn order for a Passport trunk to stage, the trmAgent process on the FP needsregister with the trmMaster process on the CP. This alarm is set when TRM Agon the FP is not able to register with TRM Master on the CP even after 10 retThis usually occurs during CP switchover when the CP is very busy.

A clear is issued after TRM Agent is able to register with TRM Master on the

Probable Cause

Type

Remedial actionThe alarm generally clears after some time. No action is required if the alarm stgets cleared.

Component Severity StatusTrm warning set/clear

241-5701-500 4.1S1


may

7009 0402

LegendNone.

DetailsA new broadcast packet received from a neighbor, has an LRC error. This errorbe due to transmission failures.

Probable Cause

Type

Remedial actionNo action is required. Contact Nortel Networks global support only if this alarmappears frequently.

Component Severity StatusRtg Dpn warning message



Dpnntrol

albly

7009 0403

LegendNone.

DetailsUpon the reception of a broadcast packet from a neighbor module (containingcontrol data), a shortage of shared memory was encountered. Dpn routing codata may be lost if this occurs.

Probable Cause

Type

Remedial actionNo action is required if this occurs infrequently. Contact Nortel Networks globsupport only if other events also indicated that the control processor is inexplicashort of memory.


241-5701-500 4.1S1


at is

7009 0404

LegendNone.

DetailsA new broadcast packet received from a neighbor module has an age field thzero. This indicates that there is a routing loop in the broadcast system. Suchconditions can occur temporarily.

Probable Cause

Type

Remedial actionNo action is required. Temporary looping may happen.

Contact Nortel Networks global support only if this alarm occurs frequently.




iches a

tbeay of

7009 0405

LegendNone.

DetailsA broadcast packet received from a neighbor module originated from a node whhas the same Node Id as this node. This alarm will also occur if a node receivbroadcast packet which it generated.

Probable Cause

Type

Remedial actionIf the alarm occurs infrequently, and only when the network’s topology has juschanged (if a trunk has just come up or gone down, for example), then it can ignored. If it occurs frequently, when the network topology is stable, then there mbe duplicate node Ids provisioned in the network. In this case, reprovision onethe modules with a unique node Id.

Component Severity StatusRtg Dpn major message

241-5701-500 4.1S1


error

7009 0406

LegendNone.

DetailsA new broadcast packet received from a neighbor, has a checksum error. Thismay be due to transmission failures.

Probable Cause

Type





ated the

7009 0407

LegendNone.

DetailsA broadcast packet received from a neighbor is corrupted. This alarm is generif the packet is too short or having a bad header length or data length value inpacket. This error may be due to transmission failures.

Probable Cause

Type



241-5701-500 4.1S1


r path

7009 0408

LegendNone.

DetailsBroadcast packets for one or more data types have not been received for anextensive period of time from one or more nodes in the RID subnet. Thosebroadcasts were received before and contained data that are required for propecalculations or call routing.

Probable Cause

Type





ith a

7009 0502

LegendNone.

DetailsBroadcast data received from a neighbor module is originated from a node wdifferent Rid value from this node.

Probable Cause

Type

Remedial actionReprovision the module with the Rid of the subnet.

Component Severity StatusRtg Dpn critical message

241-5701-500 4.1S1


hich

7009 0503

LegendNone.

DetailsBroadcast data received from a neighbor module is originated from a node whas the same Mid as this node.

Probable Cause

Type

Remedial actionReprovision one of the two nodes sharing the same Mid to use a unique Mid.




hich

7009 0504

LegendNone.

DetailsBroadcast data received from a neighbor module is originated from a node whas the same Node Id as this node.

Probable Cause

Type

Remedial actionReprovision the module with a unique node Id.


241-5701-500 4.1S1


ll

ver

7009 0505

LegendNone.

DetailsDpn external address plan (Eap) sets this alarm if it detects more than two caserver resource modules (CSRM) Rids in the subnet.

A clear will be issued after recovering from the condition. The alarm lists thevisible call server Rids. Only the two lowest call server Rids are used.

Probable Cause

Type

Remedial actionNo action is required, but you may want to reprovision one or more of the call serRids to not support the subnet Rid.

Component Severity StatusRtg Dpn warning/cleared set/clear



Inour Midwith

fifthns

re).

7009 0506

LegendNone.

DetailsThere can be a maximum of four nodes supporting gateways to any one Mid.other words, a cluster of access modules (AM) cannot connect to more than fdifferent Passport nodes. If a fifth path through a different Passport node to ain such a cluster is detected, this alarm occurs. The alarm should list all nodesconnections to the cluster. Dpn Eap’s view of the routes to the cluster may beinconsistent.

Probable Cause

Type

Remedial actionDisable one of the connections from the cluster to the subnet. If you disable theconnection no further action is required. If you disable one of the four connectiothat was originally up then you should also disable and re-enable the fifthconnection again (to force it to be made visible to all Passport nodes once mo


241-5701-500 4.1S1


ed 20

st of

s the

7009 0507

LegendNone.

DetailsA routing loop possibly exists in the network. A module in the network has issua Ping command (Path for DPN equipment) and the Ping packet has travelledhops. The alarm is issued on the 20th hop module. In the alarm comment, the limodules that the Ping packet has travelled through is displayed.

Probable Cause

Type

Remedial actionNo action is required. Temporary looping may happen.

Contact Nortel Networks global support only if there are no topology changesoccurring when the command is issued and repeating the command producesame results.




t no

whenhput

7009 0509

LegendNone.

DetailsThe node now has a delay path but no throughput path or a throughput path budelay path to the given Rid(s).

The alarm is re-issued whenever the list of affected Rids changes. Each newinstance of the alarm supersedes the preceding instance. The alarm is clearedthe node has either both delay and throughput paths or neither delay nor througpaths to each Rid.

Probable Cause

Type

Remedial actionAdjust provisioned delay or throughput metric cutoff values in the subnet.

Component Severity StatusRtg Dpn major/cleared set/clear

241-5701-500 4.1S1


tem.sedcan

re

7009 0510

LegendNone

DetailsAn LRC error has been detected in a packet received by the DPN PPATH sysThis error may be due to software error or due to trunk problems which have caupackets to be corrupted. Note that certain patterns of trunk packet corruption cause any DPN packet to be incorrectly sent to the PPATH system.

Probable Cause

Type

Remedial actionContact Nortel Networks global support only if it can be verified that the trunks anot causing the problem.




nionwillork

7009 0602

LegendNone.

DetailsThe DPN routing protocol interface (Rpi) has received a routing packet with aLRC error from a neighbor DPN Gateway. This error may be due to transmisserrors on links or due to software errors. The repeated occurrence of this alarmcause the DPN routing system knowledge to be out of date with the actual netwtopology.

Probable Cause

Type

Remedial actionContact Nortel Networks global support only if it can be verified that the linkfacilities are not causing the problem.


241-5701-500 4.1S1


rcein

ct

7009 0603

LegendNone.

DetailsThe RPI RID protocol has received a routing table update (RTU) from a resoumodule (RM) with invalid vintage value. The neighbor RM’s RID is displayed comment data.

Probable Cause

Type

Remedial actionContact Nortel Networks global support if the neighbor RM is running the correlevel of software.




n

ct

7009 0604

LegendNone.

DetailsThe routing protocol interface (RPI) logical MID (LMID) protocol has received aLMID status packet with invalid vintage value.The neighbor RM’s RID isdisplayed in comment data.

Probable Cause

Type

Remedial actionContact Nortel Networks global support if the neighbor RM is running the correlevel of software.


241-5701-500 4.1S1


le

ct

7009 0605

LegendNone.

DetailsThe routing protocol interface (RPI) MID protocol has received a MID routing tabupdate (MRTU) with invalid vintage value. The neighbor MID is displayed incomment data.

Probable Cause

Type

Remedial actionContact Nortel Networks global support if the neighbor AM is running the correlevel of software.




leof

7009 0606

LegendNone.

DetailsThe routing protocol interface (RPI) MID protocol has received a MID routing tabupdate (MRTU) with invalid cluster type. The invalid cluster types are either oneRM cluster, AM cluster, or NM cluster.

Probable Cause

Type



241-5701-500 4.1S1


r of

7009 0607

LegendNone.

DetailsThe routing protocol interface (RPI) MID Broadcaster has exhausted the numberetries of MID broadcasting before the response packets from all MIDs arereceived. The non-responding MID(s) are displayed in comment data.

Probable Cause

Type





tonetsor(s)t

ithnon-

s

7009 0608

LegendNone.

DetailsThe routing protocol interface (RPI) had been waiting long enough and failed receive routing table updates (RTUs) from its Passport neighbors in other subafter the hitless CP switchover occurred. The non-responding Passport neighbare identified by RID MID pairs and displayed in comment data. In order to leneighbor(s) send us RTUs, the link groups to the non-responding Passportneighbours are automatically taken down and brought up. Thereafter, along wthis alarm, the set and clear of alarm 7005 0103 should be seen as well for eachresponding Passport neighbors.

Probable Cause

Type

Remedial actionContact Nortel Networks global support if RPI is still not be able to receive RTUfrom its Passport neighbors.

Component Severity StatusRtg Dpn indeterminate message

241-5701-500 4.1S1


the

ion.

7009 0701

LegendNone.

DetailsThe Rtg routing table maintainer has detected the software error specified in alarm text.

Probable Cause

Type

Remedial actionContact Nortel Networks global support for frequent occurrences of this condit

Component Severity StatusRtg indeterminate message



Rtgtoified.ith

andult

7009 0703

LegendNone.

DetailsThe Rtg routing table manager has not received an acknowledgment to its lasttable update from the card specified in the alarm text. This error may be due severe message block exhaustion on the CP and/or a fault with the card specThe Rtg table manager will resynchronize the Rtg routing tables on the card wthose of the CP.

Probable Cause

Type

Remedial actionFrequent occurrences of this condition indicate a system fault between the CPcard. Contact Nortel Networks global support only if it can be verified that a faon either the CP and/or card is not causing the problem.

Component Severity StatusRtg minor message

241-5701-500 4.1S1


ble

7009 0704

LegendNone.

DetailsThe Rtg routing table manager has detected a corruption in the Rtg routing taspecified in the alarm text. The shelf may experience degraded congestionavoidance and/or routing performance. The fault may also manifest itself as arouting loop or, through a topology change, it may remedy itself.

Probable Cause

Type


Component Severity StatusRtg major message



f

t.

7009 0705

LegendNone.

DetailsThe Rtg routing table agent, specified in the alarm text, has detected an out osequence routing table update received from the CP. This alarm will beaccompanied by alarm 7009 0703. After which the Rtg table manager willresynchronize the Rtg routing tables on the card with those of the CP.

Probable Cause

Type

Remedial actionFor frequent occurrences of this alarm contact Nortel Networks global suppor

Component Severity StatusRtg warning message

241-5701-500 4.1S1


n inn, the CP.

t.

7009 0706

LegendNone.

DetailsThe Rtg routing table agent, specified in the alarm text, has detected a corruptiothe specified Rtg routing table. The card may experience degraded congestioavoidance and/or routing performance for up to 60 seconds. After which timeRtg routing table manager will resynchronize the card tables with those of the

Probable Cause

Type


Component Severity StatusRtg warning message



ion.

7009 0801

LegendNone.

DetailsThe DPN RID/MID System (Rms) routing table maintainer has detected thesoftware error specified in the alarm text.

Probable Cause

Type

Remedial actionContact Nortel Networks global support for frequent occurrences of this condit

Component Severity StatusRtg Dpn indeterminate message

241-5701-500 4.1S1


y berdthe

andult

7009 0803

LegendNone.

DetailsThe DPN RID/MID System (Rms) routing table manager has not received anacknowledgment to its last Rms table update from the specified card. This madue to severe message block exhaustion on the CP and/or a fault with the caspecified. The Rms table manager will resynchronize the Rms routing tables oncard with those of the CP.

Probable Cause

Type

Remedial actionFrequent occurrences of this condition indicate a system fault between the CPcard. Contact Nortel Networks global support only if it can be verified that a faon either the CP and/or card is not causing the problem.

Component Severity StatusRtg Dpn minor message



tion

lsoelf.

7009 0804

LegendNone.

DetailsThe DPN RID/MID System (Rms) routing table manager has detected a corrupin the Rms routing table specified in the alarm text. The shelf may experiencedegraded congestion avoidance and/or routing performance. The fault may amanifest itself as a routing loop or, through a topology change, it may remedy its

Probable Cause

Type



241-5701-500 4.1S1


xt,hisger

t.

7009 0805

LegendNone.

DetailsThe DPN RID/MID System (Rms) routing table agent, specified in the alarm tehas detected an out of sequence routing table update received from the CP. Talarm will be accompanied by alarm 7009 0803. After which the Rms table manawill resynchronize the Rms routing tables on the card with those of the CP.

Probable Cause

Type





xt,

to 60the

t.

7009 0806

LegendNone.

DetailsThe DPN RID/MID System (Rms) routing table agent, specified in the alarm tehas detected a corruption in the specified Rms routing table. The card mayexperience degraded congestion avoidance and/or routing performance for upseconds. After which time, the Rms routing table manager will resynchronize card tables with those of the CP.

Probable Cause

Type



241-5701-500 4.1S1


arelear.

useon

7011 1100

Legend<num1> = 1 - 15

<num2> = 0 - 7

DetailsIf the status isset, there are no links active in the IMA group. The IMA virtual linkis not capable of carrying any user traffic.

A clear will be issued when one or more links in the IMA group are activated.

Probable CauseProtocol error

TypeCommunications

Remedial actionThis condition is usually caused by incorrect connection of the links orconfiguration of the local and remote IMA groups. Check that the physical portsproperly connected at the local and remote ends, and that all port alarms are cExamine the alarm comment text and thefailureCause andremoteDefectoperational attributes of the IMA component to obtain an indication as to the caof the problem, and check the configuration of the IMA and LINK componentsthe local and remote ends.

Component Severity StatusLp/<num1> IMA/<num2> critical/cleared set/clear



ethethen

the

7011 1200


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, the link is not an active member of the IMA group. The link willnot be used by the IMA group for carrying any user traffic.

A clear will be issued when the link is activated in the IMA group.


TypeCommunications

Remedial actionThis condition is usually caused by incorrect connection or configuration of thlink. First check that the physical port used by this link is properly connected atlocal and remote ends, and that all port alarms are clear. If the problem persistsexamine thefailureCause andremoteDefect operational attributes of the LINKcomponent to obtain an indication as to the cause of the problem, and check configuration of the LINK components on the local and remote ends.

Component Severity StatusLp/<num1> IMA/<num2> LK/<num3> critical/cleared set/clear

241-5701-500 4.1S1


.link

e

e

mote

7011 1210


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, a loss of IMA frame (LIF) alarm condition has been declaredThe LIF alarm condition is declared when the a LIF defect has persisted on thefor 2.5± 0.5 seconds.

A clearwill be issued when the LIF defect has been absent for 10.0± 0.5 seconds.

A LIF defect is declared if IMA framing has not been recovered three IMA framperiods after the occurrence of an out of IMA frame (OIF) anomaly. An OIFanomaly is the occurrence of one of the following events:

- a missing ICP cell

- an invalid ICP cell

- two consecutive errored ICP cells

- a valid ICP cell at an unexpected position

A LIF defect is cleared if IMA framing has been maintained for two IMA frameperiods.


TypeCommunications

Remedial actionThis condition is usually caused by incorrect connection or configuration of thlink. Check thelastOifCauseoperational attribute of the link for an indication of thecause. Ensure that the physical port is properly connected at the local and reends, and check the configuration of thelink component on the local and remoteends.




on

heeddy

he

lis

foryt

7011 1211


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, a loss of delay synchronization (LODS) condition is present the link.

A clear will be issued once the LODS condition is no longer present.

A LODS condition is declared when the transit delay of a link being activated in tIMA group relative to the reference link in the IMA group exceeds the provisionmaximum acceptable differential delay, or when the transit delay of a link alreaactive in the IMA group relative to the reference link in the IMA group exceeds tprovisioned maximum acceptable differential delay plus one millisecond.

The LODS condition is cleared when the transit delay of the link relative to thereference link in the IMA group is within the provisioned maximum acceptabledifferential delay.


TypeCommunications

Remedial actionCheck therelativeDelayoperational attribute of the link to determine its differentiadelay. If an increase in the maximum differential delay across the IMA group acceptable, increase the setting of themaxDiffDelay attribute of the parent IMAcomponent. Alternatively, changing the setting of thelinkSelectionCriterionattribute of the parent IMA component may result in a different reference link the IMA group; however, be warned that this may result in the differential delabecoming unacceptable for other links in the group. If the above actions do nosolve the problem, replace the physical facility used by this link with one thatexhibits a transit delay closer to that of the reference link.


241-5701-500 4.1S1


n not

.

eeote

7011 1212


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, the link has been identified as being misconnected.

A clear will be issued once the misconnection is no longer present.

A link is tested for misconnection during the IMA group start-up and link additioprocedures. A link is identified as being misconnected if the remote end doesloop back a test pattern transmitted by the local end, or if the link belongs to adifferent IMA group than the one with which the local end has elected to stage


TypeCommunications

Remedial actionThis condition is usually caused by incorrect connection or configuration of thlink. Check that the physical port is properly connected at the local and remotends, and check the configuration of the LINK component on the local and remends.




DI)

is

tthe

7011 1213


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, a remote failure indicator (RFI) alarm condition has beendeclared. The RFI alarm condition is declared when a remote defect indicator (Rdefect has persisted on the link for 2.5± 0.5 seconds.

A clearwill be issued when the RDI defect has been absent for 10.0± 0.5 seconds.

An RDI defect is declared when one of the following remote defect indicators received for this link from the remote IMA:

- physical link defect

- loss of IMA frame (LIF)

- loss of delay synchronization (LODS)

The RDI defect is cleared when a remote defect indicator is no longer beingreceived for the link from the remote IMA.


TypeCommunications

Remedial actionCheck theremoteDefect operational attribute of the link to determine what defecindicator is being received from the far-end. Verify the operational attributes atremote end to determine why the defect indicator is being transmitted.


241-5701-500 4.1S1


-up

r

e

ectednts

7011 1214


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, a fault alarm condition has been declared on the link. A faultalarm condition is declared if no ICP cells are detected on the link during a startor link addition attempt or if an invalid IMA group ID, frame length, groupsymmetry or logical link ID is received on the link during IMA group start-up olink addition.

A clear will be issued when the fault alarm condition is not longer present.


TypeCommunications

Remedial actionThis condition is usually caused by incorrect connection or configuration of thlink. Check thefailureCauseoperational attribute of the link to obtain an indicationas to the cause of the problem. Ensure that the physical port is properly connat the local and remote ends, and check the configuration of the LINK componeon the local and remote ends.




e to

7011 1215


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, the remote link has gone to the Unusable state.

A clear will be issued once the remote link is no longer in the Unusable state.


TypeCommunications

Remedial actionCheck the operational attributes at the remote end to determine why it has gonthe Unusable state.


241-5701-500 4.1S1


A

nd

fy

7011 1216


<num2> = 0 - 7

<num3> = 0 - 31

DetailsIf the status isset, a protocol error alarm condition has been declared on the link.protocol error alarm condition is declared if, during IMA group start-up or linkaddition, the link could not be activated within the prescribed time-out period, ano other failure condition has been identified.

A clear will be issued when the protocol error condition is not longer present.


TypeCommunications

Remedial actionThis condition may be caused by incorrect configuration of the IMA group. Verithe linkRetryTimeout provisionable attribute of the IMA component at the localand remote ends, and check the operational attributes of the IMA and LINKcomponents at the local and remote ends.




7011 1400


<num2> = 0 - 111

DetailsIf the status isset, there is an insufficient number of links (determined byactivationClassandactivationThresholdattributes under theMultiLinkFrameRelaycomponent) in the up state.

A clear is issued when a sufficient number of links (determined byactivationClassandactivationThresholdattributes under theMultiLinkFrameRelaycomponent) arein the up state.

Remedial actionCheck the state of theMultiLinkFrameRelay andLink components on local andremote endpoints and, if necessary, add more links to the bundle.

Component Severity StatusLp/<num1> Mlfr/<num2> critical/cleared set/clear

241-5701-500 4.1S1


7011 1401


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, there is a bundle link configuration mismatch between theexpected and the received value for theremoteName attribute for the bundle.

A clear is issued when the expected value for theremoteName attribute for thebundle is received.

Remedial actionCheck theerrorCause andremoteName attributes and the configured data for theLink component. Lock and unlock theMultiLinkFrameRelay component to restartthe MLFR link integrity protocol.

Component Severity StatusLp/<num1> Mlfr/<num2>Link/<num3> critical/cleared set/clear



7011 1402


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, there is an unrecognized OUI in a received Vendor Specificinformation field.

A clear is issued when the expected OUI is received.

Remedial actionRemove the Link and add it again to Mlfr component.


241-5701-500 4.1S1


7011 1403


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, the link is inidle state.

A clear is issued when the link leaves theidle state.

Remedial actionCheck thecause attribute and the provisioned data for theLink component. Lockand unlock theMultiLinkFrameRelaycomponent to restart the MLFR link integrityprotocol.




7011 1404


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, the link is indown state.

A clear is issued when the link leaves thedown state.

Remedial actionCheck thecause attribute and the provisioned data for theLink component. Lockand unlock theMultiLinkFrameRelaycomponent to restart the MLFR link integrityprotocol.


241-5701-500 4.1S1


7011 1405


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, a loopback was detected.

A clear is issued when the loopback is removed.

Remedial actionCheck if the external loopback is installed.

Component Severity StatusLp<num1> Mlfr/<num2>Link/<num3> major/cleared set/clear



d.

een

7011 1406


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, the bundle link differential delay exceeds the maximum allowe

A clear is issued when the bundle link differential delay no longer exceeds themaximum allowed.

Remedial actionThe operator may consider the increasing of the value of themaxDiffDelayattributefor this bundle, based on the length of the wires and the size of the frames betwthe near and far end.


241-5701-500 4.1S1


ol

ed.

7011 1407


<num2> = 0 - 111

<num3> = 0 - 27

DetailsIf the status isset, there was detected an error in the MLFR link integrity protocbetween the near and far end.

A clear is issued when valid MLFR link integrity protocol messages are receiv

Remedial actionLock and unlock theMultiLinkFrameRelay component to restart the MLFR linkintegrity protocol.




A

type

ised

7011 2000


<type> = DS3, E3, SONET, SDH, DS1, E1, CHANNEL, V35, X21, HSSI and IM

<num2> = 0-n, where n is 1 less than the number of ports supported on the card

DetailsWhen a hardware failure has been found by port diagnostics, the port isautomatically locked and disabled by the system. Alarm code 70112000 is rawhen a user attempts to unlock the port before the failure is rectified.

A clear will be issued after running the diagnostics successfully.


TypeEquipment

Remedial actionReplace the defective hardware.

Component Severity StatusLp/<num1> <type>/<num2> critical/cleared set/clear

241-5701-500 4.1S1


type

ver

7011 2001


<type> = V35, X21 and HSSI

<num2> = 0-n, where n is 1 less than the number of ports supported on the cardused.

DetailsIf the status isset, the link is in a state that renders the portdisabled.

On a V35 or a X21 port, if the incoming line state is not consistent with thatdescribed in the provisionable attributereadyLineState, the port is disabled.

A clear will be issued when the condition has been cleared.

Probable CausedteDce interface error

TypeCommunications

Remedial actionIssue thedisplaycommand on the component that has issued the alarm to discothe cause of the problem.

For a V35 or X21 port, check if thereadyLineState attribute is set up as expectedand verify that the cable is connected properly.




type

hisCP

7011 2002


<type> = DS3, E3, SONET, and SDH

<num2> = 0-n, where n is 1 less than the number of ports supported on the card

DetailsThe card is unable to synchronize its transmit clock to the CP’s module clock. Tmay indicate an equipment failure on the FP, on the backplane, or on the activefrom which the module clock signal originates.


TypeEquipment

Remedial actionCheck for defective FP, backplane, or CP hardware.

Component Severity StatusLp/<num1> <type>/<num2> major/cleared message

241-5701-500 4.1S1


type

an

10

7011 5000


<type> = EDS1, EE1, DS1 and E1

<num2> = 0-n, where n is 1 less than the number of ports supported on the cardused.

<num3> = multiple indices 1-3, 1-7, 1-3

DetailsIf the status isset, the link has been in a Loss of Frame (LOF) state for greater th2 seconds.

A clear will be issued when the LOF condition has been cleared for more thanseconds.

Probable CauseLoss of frame

TypeCommunications

Remedial actionCheck the far end for proper configuration.

Component Severity StatusLp/<num1> <type>/<num2>

Lp/<num1> SDH/0 VC4/0 VC12/<num3> E1

critical/cleared set/clear



type

rs least

the

7011 5001



<num2> = 0-n, where n is 1 less than the number of ports supported on the cardused


DetailsIf the status isset, then the far end Remote Alarm Indication (RAI) defect indicatohave been received. This is indicated immediately and remains present for at1 second.

A clear will be indicated when no far end RAI defect indicators are detected.

Probable CauseLocal transmission error

TypeCommunications

Remedial actionThe far end is complaining about a Loss of Frame (LOF) condition. Check thatprovisioning data is consistent on both ends of the connection.



minor/cleared set/clear

241-5701-500 4.1S1


type

r

10

dersts

7011 5002


<type> = EDS1, EE1,DS1 and E1



DetailsIf the status isset, the link has been in an Alarm Indication Signal (AIS) state fogreater than 2 seconds.

A clear will be issued when the AIS condition has been cleared for more thanseconds.

Probable CauseRemote transmission error

TypeCommunications

Remedial actionThe far end is complaining about Loss of Signal (LOS) or the far end port is untest. Check the cabling between the two interfaces or check if there are any terunning on the far end interface.






type

an

10

7011 5003





DetailsIf the status isset, the link has been in an Loss of Signal (LOS) state for greater th2 seconds.

A clear will be issued when the LOS condition has been cleared for more thanseconds.


TypeCommunications

Remedial actionCheck the cabling between this port and the far end port.




241-5701-500 4.1S1


type

)

7011 5004




DetailsIf the status isset, the link has been in a Multiframe Remote Alarm Indication (RAIstate for greater than 2 seconds.

The far end interface is complaining that it has lost Multiframe alignment.

A clear will be issued when the Multiframe RAI condition has been cleared formore than 10 seconds.


TypeCommunications

Remedial actionCheck the configuration of both ports.

Component Severity StatusLp/<num1> E1/<num2>





type

r

7011 5005




DetailsIf the status isset, the link has been in a Multiframe Red state for greater than 2seconds.

A clear will be issued when the Multiframe Red condition has been cleared fomore than 10 seconds.

Probable CauseLoss of Frame

TypeCommunications

Remedial actionCheck the configuration of both ports.

Component Severity StatusLp/<num1> E1/<num2>



241-5701-500 4.1S1


isms

ort.s of

icestionalckedted

e

ice

7011 5006

Lp/<instance> E1/<Instance>

Legend<instance> = provisioned decimal digit 0-9

DetailsIf the status isset, a yellow alarm is being asserted on the port. The yellow alarmasserted because of voice services using this port, having connectivity problethrough the subnet, which could be caused by numerous reasons.

A clearwill be issued when the yellow alarm is no longer being asserted on the pThe yellow alarm is no longer being asserted because the connectivity problemthe voice services using this port have been re-established.

Probable CauseCommunications subsystem failure

TypeCommunications

Remedial actionThe yellow alarm was asserted due to connectivity problems of the voice servusing the port. This could be caused by two generic reasons. First, the operastate of the voice services using the port in yellow alarm state, should be cheto see if its enabled, as well as the remote voice service that they are connecto.

If not, maintenance action is required to restore the services on the DS1/E1interface. If they are all enabled, connectivity problems are occurring within thsubnet. Trunks that carry the voice traffic through the subnet should beinvestigated for problems and rectified in order to restore connectivity of the voservices.

Component Severity StatusLp/<instance> DS1/<Instance> major/cleared set/clear



type

tion

7011 5010


<type> = DS1 and E1



DetailsIf the status isset, the link has entered an Unavailable state. This condition isdeclared after 10 consecutive Severely Errored Seconds (SES).

A clear will be issued after 10 consecutive seconds during which no SES arecounted.

For DS1/E1, a Severely Errored Second is a second with 320 or more code violaerror events or one or more SEF (Severely Errored Frame) events.

Probable CauseDegraded signal

TypeCommunications

Remedial actionDetermine the cause of the errored seconds and fix the far end interface.



minor/cleared set/clear

241-5701-500 4.1S1


type

f aimeline

r the

7011 5011


<type> = DS1 and E1


DetailsIf the status isset, the transmit clock for the port has failed as a consequence ofailure of the locally generated asynchronous clock (Synchronous Residual TStamp (SRTS) mode. Under this condition the timing of the data on the DS1/E1may not conform to the appropriate standards.

If the status isclear, the alarm indicates that the transmit clock for the port is nolonger defective.

Probable Cause

Type

Remedial actionFollow the standard procedure for testing the FP, and if the alarm does not cleadefective unit has to be replaced.

Component Severity StatusLp/<num1> <type>/<num2> warning/cleared set/clear



t 2s

0

7011 5100


<num2> = 0 - 2

type = DS3 and E3

DetailsIf the status isset, a Loss Of Signal (LOS) condition has been present for at leasseconds on the incoming line. An LOS condition occurs when the port receiveneither negative nor positive pulses.

A clear will be issued when no LOS condition has been detected for at least 1seconds.


TypeCommunications



241-5701-500 4.1S1


astot

al

of

d

ent.

7011 5101


<num2> = 0 - 2

type = DS3 and E3

DetailsIf the status isset, an Loss Of Frame (LOF) condition has been present for at le2 seconds on the incoming line. An LOF condition occurs when this port cannframe to the incoming DS3 or E3 signal.

A clearwill be issued when this port has successfully framed the incoming signfor at least 10 seconds.

For DS3:

A DS3 far end SEF/AIS signal will be transmitted by this port for the duration the time the LOF condition is present.

For E3:

In ITU-T G.751 framing mode, an E3 far end SEF/AIS signal will be transmitteby this port for the duration of the time the LOF condition is present.

In ITU-T G.832 framing mode, an E3 far end receive failure (FERF) signal will btransmitted by this port for the duration of the time the LOF condition is prese


TypeCommunications

Remedial actionCheck the configuration of the far end port.




at

AIS.

of

tate.

d

ent.

7011 5102


<num2> = 0 - 2

type = DS3 and E3

DetailsIf the status isset, Alarm Indication Signal (AIS) defects have been detected forleast 2 seconds on the incoming line.

A clear will be issued when no AIS defects have been detected for at least 10seconds.

For DS3:

Receiving an AIS means that the far end port has detected a problem beyond it.could be generated by DS3 cross-connects located between Passport nodes

A DS3 far end SEF/AIS signal will be transmitted by this port for the duration the time that AIS defects are present.

For E3:

Receiving an AIS means that the far end port has been put in the LOCKED s

In ITU-T G.751 framing mode, an E3 far end SEF/AIS signal will be transmitteby this port for the duration of the time that AIS defects are present.

In ITU-T G.832 framing mode, an E3 far end receive failure (FERF) signal will btransmitted by this port for the duration of the time that AIS defects are prese


TypeCommunications

Remedial actionCheck the configuration and status of the far end port.


241-5701-500 4.1S1


nel.

st 10

/

andIT

7011 5103


<num2> = 0 - 2

type = DS3 and E3

DetailsFor DS3:

When running in C-Bit Parity mode, the status issetto indicate that a far end alarmhas been received over the Far End Alarm and Control (FEAC) channel. Aclearwill be issued when the alarm signal is no longer received over the FEAC chan

When not running C-Bit Parity mode, the status isset to indicate that far end SEF/AIS defect indicators have been received for at least 2 seconds. Aclear will beissued when no far end SEF/AIS defect indicators have been detected for the laseconds.

For E3:

In ITU-T G.751 framing mode, the status isset to indicate that an E3 far end SEFAIS signal has been received for at least 2 seconds. Aclearwill be issued when nofar end SEF/AIS signal has been received for at least 10 seconds.

In ITU-T G.832 framing mode, the status issetto indicate that an E3 far end receivefailure (FERF) signal has been received for at least 2 seconds. Aclearwill be issuedwhen no FERF signal has been received for at least 10 seconds.


TypeCommunications

Remedial actionCheck the cabling between this port and the far end port, and the configurationstatus of the far end port. If running in DS3 C-Bit Parity mode, also check the CBcomponent operational data.

Component Severity StatusLp/<num1> <type>/<num2> critical/minor/

clearedset/clear



the

al

onds.

7011 5104


<num2> = 0 - 2

DetailsIf the status isset, a DS3 Idle signal has been detected for at least 2 seconds onincoming line.

The far end port has been locked and is not currently being used in operationtesting.

A clear will be issued when no DS3 Idle has been detected for at least 10 sec


TypeCommunications

Remedial actionCheck the status of the far end port.

Component Severity StatusLp/<num1> DS3/<num2> critical/cleared set/clear

241-5701-500 4.1S1


the

topity

7011 5110


<num2> = 0 - 2

DetailsIf the status isset, this port has received a request from the far end to loopbackincoming DS3 signal. The far end port is currently under operational testing.Service on this port will be suspended.

A clearwill be issued when this port has received a request from the far end to slooping the incoming DS3 signal, or when the port is locked, or when CBIT parmode is turned off.


TypeCommunications


Component Severity StatusLp/<num1> DS3/<num2> critical/cleared set/clear



tod by

e

far

t tot the

en

7011 5111


DetailsIf the status isset, the DS3 component has received a request from the far endloopback an incoming DS1 tributary on the DS3. The loopback request is causethe initiation of a remoteLoopThisTrib test at the far end. This request can comfrom a C-bit Parity channel only. The affected DS1 component is taken out ofservice. This alarm will remain set as long as at least one DS1 tributary is inloopback state.

A clear will be issued when there are no more active DS1 loopbacks from theend.


TypeCommunications

Remedial actionIf the loopback is not expected, check the far end DS3/0 DS1/x Test componensee if a remoteLoopThisTrib test type is active. The loopback can be removed anear end by stopping the remoteLoopThisTrib test at the far end.

Alternatively, the loopback can be removed at the near end by Locking and thUnlocking the affected DS1 component.

Component Severity StatusLp/<num1> ds3/0 minor/cleared set/clear

241-5701-500 4.1S1


ed

7011 5112


DetailsThe DS3 component receives a tributary loopback request for an unprovisiontributary or is aborting an existing DS3 or DS1 cbit FEAC loopback.


TypeCommunications

Remedial actionThis alarm is provided for information only.

Component Severity StatusLp/<num1> ds3/0 minor message



tion

me

ath

athts.

7011 5120


<num2> = 0 - 2

type = DS3 and E3

DetailsIf the status isset, the near end path has entered an Unavailable state. This condiis declared after 10 consecutive Severely Errored Seconds (SESs).

A clear will be issued after 10 consecutive seconds with no SES.

For DS3:

A SES is a second interval with more than 44 Path Code Violations (parity/fraerrors) or one or more SEF/AIS defects.

For E3:

In ITU-T G.751 framing mode, a SES is a second interval with more than 22 PCode Violations (frame errors) or one or more SEF/AIS defects.

In ITU-T G.832 framing mode, a SES is a second interval with more than 34 PCode Violations (frame errors or BIP-8 errors) or one or more SEF/AIS defec


TypeCommunications

Remedial actionDetermine the cause of the errored seconds and fix the far end port.

Component Severity StatusLp/<num1> <type>/<num2> minor/cleared set/clear

241-5701-500 4.1S1


is

IT

7011 5121


<num2> = 0 - 2

DetailsIf the status isset, the link has entered a CBIT Unavailable state. This conditiondeclared after 10 consecutive CBIT Severely Errored Seconds (CSESs).

A clear will be issued after 10 consecutive seconds with no CSES.

A CSES is a second interval with more than 44 CBIT Path Code Violations (CBparity errors) or one or more SEF/AIS defects.


TypeCommunications


Component Severity StatusLp/<num1> DS3/<num2> minor/cleared set/clear



on) or

I.

Es)s that it.

e

7011 5122


<num2> = 0 - 2

DetailsIf the status isset, the link has entered a Far End Unavailable state. This conditiis declared after 10 consecutive Far End Severely Errored Seconds (FESESswhen a Remote Alarm Indicator (RAI) is declared.

A clear will be issued after 10 consecutive seconds with no FESES and no RA

A FESES is a second interval with more than 44 Far End Code Violations (FEBor one or more far end SEF/AIS defects. The occurrence of these events meanthe far end does not receive properly what the local interface is transmitting to


TypeCommunications

Remedial actionDetermine the cause of the far end errored seconds and fix this port or the linbetween it and the far end.

Component Severity StatusLp/<num1> DS3/<num2> minor/cleared set/clear

241-5701-500 4.1S1


s a

the

7011 5130


DetailsIf the status isset, one of the Multiport Aggregate Devices attached to the FP hafaulty power supply. This alarm will not beset again if the other MultiportAggregate Devices connected to the FP develops a power supply problem.

A clear is issued when neither of the Multiport Aggregate Devices attached toFP has a power supply problem.

Probable CausePower problem

TypeEquipment

Remedial actionCorrect the problem as documented for the Multiport Aggregate Devices.

Component Severity StatusLp/<num1> minor/cleared set/clear



s aived

the

7011 5131


DetailsIf the status isset, one of the Multiport Aggregate Devices attached to the FP halink problem. Possible causes could be Loss of signal, Loss of framing or a receRemote Alarm Indication in the signal. This alarm will not besetagain if the otherMultiport Aggregate Devices connected to the FP develops a link problem

A clear is issued when neither of the Multiport Aggregate Devices attached toFP has a link problem.

Probable CauseInput device error

TypeEquipment

Remedial actionCheck cabling between Multiport Aggregate Devices and FP.

Component Severity StatusLp/<num1> major/cleared set/clear

241-5701-500 4.1S1


t 2OFting

ith

h of

7011 5200


<num2> = 0 - 2

type = SONET and SDH

DetailsIf the status isset, a Loss Of Signal (LOS) condition has been present for at leasseconds on the incoming line, or the LOS defect is present when the criteria for Lfailure declaration have been met. Declaration of an LOS failure clears any exisLOF failure.

A clear will be issued when no LOS condition has been present for at least 10seconds. If an LOF condition exists when the LOS is cleared, the LOF will bedeclared immediately.

Note: An LOS condition can also be caused by saturating the optical receiver wtoo strong a signal.

Probable CauseLoss of signal

TypeCommunications

Remedial actionCheck the cabling between this port and the far end port. Verify that the strengtthe signal is within specifications.




astot

al

7011 5201


<num2> = 0 - 2


DetailsIf the status isset, an Loss Of Frame (LOF) condition has been present for at le2 seconds on the incoming line. An LOF condition occurs when this port cannframe to the incoming SONET or SDH signal.

A clearwill be issued when this port has successfully framed the incoming signfor at least 10 seconds. LOF is also cleared when an LOS defect is declared.


TypeCommunications

Remedial actionCheck the configuration of the far end port and the section statistics.


241-5701-500 4.1S1


d

itting

0

7011 5202


<num2> = 0 - 2


DetailsIf the status isset, Line Alarm Indication Signal (L-AIS) defects have been detectefor at least 2 seconds on the incoming line. The L-AIS alarm is used to alertdownstream equipment that a failure has been detected or that the port transmL-AIS has been locked.

A clear will be issued when no L-AIS defects have been detected for at least 1seconds.


TypeCommunications





.for

nds.

and

7011 5203


<num2> = 0 - 2


DetailsIf the status isset, this port is receiving the Line Remote Defect Indicator (L-RDI)L-RDI is transmitted by the far end when it has been detecting L-AIS defects some period of time.

A clear will be issued when no L-RDI defects have been detected for 10 seco


TypeCommunications

Remedial actionCheck the cabling between this port and the far end port, and the configurationstatus of the far end port.


241-5701-500 4.1S1


ce

mit

formit

e of

ecknt.

7011 5204


<num2> = 0 - 2


DetailsIf the status isset, a Sonet/Sdh port provisioned to act as a transmit clock referenhas received the code “do not use for synchronization” in the S1 byte (in theSONET/SDH line overhead) for 2.5 +/- 0.5 seconds. A port is acting as a transclock reference if:

• it is provisioned with aclockingSource of line, or

• it is provisioned with aclockingSource of module and is being used bytheNetworkSynchronization component as clock reference.

A clear is issued when the “do not use for synchronization” code is not received10 +/- 0.5 seconds, or when the port is no longer provisioned to act as a transclock reference.


TypeCommunications

Remedial actionThis alarm is caused by the far end Sonet/Sdh port is transmitting an S1 valu“do not use for synchronization”. This is most likely caused by a loss ofsynchronization to the far end port’s provisioned transmit clocking source. Chthe provisioning and operational state of the far end SONET or APS equipme




Ss).

7011 5210


<num2> = 0 - 2


DetailsIf the status isset, this port has entered an Unavailable state. This condition isdeclared at the onset of 10 consecutive Line Severely Errored Seconds (L-SE

A clear will be issued at the onset of 10 seconds with no L-SES.

A L-SES is a second interval with more than 32 Line Code Violations (BIP-24errors) or one or more L-AIS defects.

Probable Cause

Type



241-5701-500 4.1S1


red

nsts

e

7011 5211


<num2> = 0 - 2

<type> = SONET or SDH

DetailsIf the status isset, this port has entered a Far End Line Unavailable state. Thiscondition is declared at the onset of 10 consecutive Far End Line Severely ErroSeconds (FEL-SESs).

A clear will be issued at the onset of 10 seconds with no FEL-SES.

A FEL-SES is a second interval with more than 32 Far End Line Code Violatio(FEBE errors) or one or more line RDI defects. The occurrence of these evenmeans that the far end does not receive properly what the local interface istransmitting to it.


TypeCommunications





t 2

7011 5250


<num2> = 0 - n, where n is one less than the number of ports on the card.

<num3> = 0 - 15999

<type1> = SONET or SDH

<type2> = Path or STS or VC4

DetailsIf the status isset, a Loss Of Signal (LOP) condition has been present for at leasseconds on the incoming line. An LOP failure indicates that the interface is nolonger detecting valid STS Payload Envelope (SPE) pointers.

A clear will be issued when no LOP condition has been present for at least 10seconds, or when an incoming P-AIS defect is detected.


TypeCommunications


Component Severity StatusLp/<num1> <type1>/<num2> <type2>/0 critical/cleared set/clearLaps/<num3> <type2>/0

241-5701-500 4.1S1


7011 5251



<num3> = 0 - 15999



DetailsIf the status isset, a Path AIS (P-AIS) condition has been present for at least 2seconds on the incoming line. A P-AIS signal is used to alert downstreamequipment that a failure has been detected or that thePath/Sts/Vc4 componenttransmitting P-AIS has been locked.

A clear will be issued when no P-AIS signal is detected for 10 seconds.


TypeCommunications





ated of

10

7011 5252



<num3> = 0 - 15999



DetailsIf the status isset, Path RDI (P-RDI) defects have been detected for at least 2seconds on the incoming line. The P-RDI signal is used by the far end to indicthat LOP or P-AIS defects, or an LCD state have been detected for some periotime.

A clear will be issued when no P-RDI defects have been detected for at least seconds.


TypeCommunications


Component Severity StatusLp/<num1> <type1>/<num2> <type2>/0 minor/cleared set/clearLaps/<num3> <type2>/0

241-5701-500 4.1S1


athcted

r 10

7011 5253



<num3> = 0 - 15999



DetailsIf the status isset, this port is receiving an unexpected Path Signal Label. The PSignal Label is used to indicate the content and format of the STS SPE. ExpePath Signal Labels are 0x13, the code forATM Mapping , and 0x01, the code forEquipped.

A clearwill be issued when the correct Path Signal Label has been detected foseconds.

A Path Signal Label Mismatch is not reported when receiving P-AIS or LOPdefects.


TypeCommunications





ESs).

rs)

7011 5260



<num3> = 0 - 15999



DetailsIf the status isset, this port has entered an Unavailable state. This condition isdeclared at the onset of 10 consecutive Path Severely Errored Seconds (P-S

A clear will be issued at the onset of 10 seconds with no P-SES.

A P-SES is a second interval with more than 16 Path Code Violations (BIP-8 erroor one or more P-LOP or P-AIS defects.


TypeCommunications



241-5701-500 4.1S1


ored

ionsents

e

7011 5261



<num3> = 0 - 15999



DetailsIf the status isset, this port has entered a Far End Path Unavailable state. Thiscondition is declared at the onset of 10 consecutive Far End Path Severely ErrSeconds (FEP-SESs).

A clear will be issued at the onset of 10 seconds with no FEP-SES.

A FEP-SES is a second interval with more than 16 Far End Path Code Violat(path FEBE errors) or one or more path RDI defects. The occurrence of these evmeans that the far end does not receive properly what the local interface istransmitting to it.


TypeCommunications





- 0.5tentno

uslynidyteing

0.5

7011 5270

Legend<type> = Aps or Laps

<num> = 0 - 15999

DetailsIf the status is set, a Protection Switching Byte defect has persisted for 2.5 +/seconds. A Protection Switching Byte defect is declared when either an inconsisAPS byte or an invalid code is detected. An inconsistent APS byte occurs whenthree consecutive K1 bytes (in the SONET/SDH line overhead) in the last 12successive frames are identical, starting with the last frame containing a previoconsistent byte. An invalid code occurs when the incoming K1 byte contains aunused code, a code irrelevant to the specific switching operation, or an invalchannel number, in three consecutive frames. An APS Protection Switching BFailure is treated as a signal failure on the protection line, preventing it from beused for protection.

A clear is issued when the Protection Switching Byte defect is absent for 10 +/-seconds.


TypeCommunications

Remedial actionThis alarm indicates that the far end equipment may be defective. Check theprovisioning and operational state of the far end SONET or APS equipment.

Component Severity Status<type>/<num> major/cleared set/clear

241-5701-500 4.1S1


nds.the

ber

7011 5271


<num> = 0 - 15999

DetailsIf the status is set, a Channel Mismatch defect has persisted for 2.5 +/- 0.5 secoA Channel Mismatch defect is declared when the channel number transmitted inK1 byte (in the SONET/SDH line overhead) does not match the channel numreceived in the K2 byte for 50 ms.

A clear is issued when the Channel Mismatch defect is absent for 10 +/- 0.5seconds.


TypeCommunications

Remedial actionThis alarm indicates that the far end equipment may be defective. Check theprovisioning and operational state of the far end SONET or APS equipment.

Component Severity Status<type>/<num> minor/cleared set/clear



5

omed

ed

5

they

7011 5272


<num> = 0 - 15999

DetailsIf the status is set, an APS Mode Mismatch defect has persisted for 2.5 +/- 0.seconds. An APS Mode Mismatch defect is declared when either (1) anAps/Lapscomponent (which uses for 1+1 protection switching) receives an indication frthe far end in the received K2 byte (SONET line overhead only) that is provisionfor 1:n, or (2) when anAps/Lapscomponent provisioned for bidirectional switchingreceives an indication from the far end in the received K2 byte that it is provisionfor unidirectional switching (or vice versa).

A clear is issued when the APS Mode Mismatch defect is absent for 10 +/- 0.seconds.


TypeCommunications

Remedial actionCheck the provisioning of the near and far end APS systems and ensure thatboth use the same provisioned architecture (1+1) and mode (unidirectional orbidirectional).


241-5701-500 4.1S1


.5

ead)

0.5

7011 5273


<num> = 0 - 15999

DetailsIf the status is set, a Far-End Protection-Line defect has persisted for 2.5 +/- 0seconds. A Far-End Protection-Line defect is declared when theAps/Lapscomponent receives three consecutive K1 bytes (in the SONET/SDH line overhwith the code indicating Signal Fail on the protection line. This alarm is notapplicable when theAps/Laps component is provisioned for 1+1 unidirectionalswitching.

A clear is issued when the Far-End Protection-Line defect is absent for 10 +/-seconds.


TypeCommunications

Remedial actionCorrect the failure on the Sonet/Sdh component used as the protection line.




nd or

ill

r orvaluesued

near

ion

e

7011 5274


<num> = 0 - 15999

DetailsIf the status is set, an APS request other than doNotRevert or noRequest (orreverseRequest in bidirectional switching), has been sent by either the near ethe far end in the K1 byte (in the SONET/SDH line overhead). Note that if theAps/Lapscomponent is provisioned for unidirectional switching the far end request wnot be monitored and will not factor into this alarm.

The alarm’s text will indicate the highest priority request being sent by the neafar end. Thereafter, every time the highest priority request changes to a new (not one of doNotRevert, noRequest or reverseRequest) the alarm will be reisindicating the new request.

A clear is issued immediately when the APS requests being sent by both the and far end change to either doNotRevert or noRequest.


TypeCommunications

Remedial actionThis alarm is informational in nature, and indicates that there is activity on theSONET/SDH APS channel which may restrict theAps/Lapscomponent’s ability todeal with line failures. If the request is a signalFail or signalDegrade, the conditshould be corrected at the SONET/SDH level. If the request is an operatorcommand the Aps can be restored to full unrestricted operation by clearing thcommand.

Component Severity Status<type>/<num> warning/cleared set/clear

241-5701-500 4.1S1


.nd

farnes,endend

7011 5275


<num> = 0 - 15999

DetailsIf the status is set, theAps/Laps component’snearEndRxActiveChannel has beenexperiencing a signal failure (SF) for 2.5 +/- 0.5 seconds.

A clear is issued when SF has been absent from theAps/Laps component’snearEndRxActiveChannel for 10 +/- 0.5 seconds.


TypeCommunications

Remedial actionThis alarm indicates that both the working and protection line are unavailableCheck for failures of the Sonet/Sdh components provisioned as the working aprotection lines.

Display theAps/Lapscomponent’s operational attributes and check for near andend command requests which may be forcing the Aps to only use one of its lifor instance the lockoutOfProtection command. If the request is from the nearthe ‘clear’ verb can be used to clear the command. If the request is from the farthe command can only be cleared on the far end equipment.

Component Severity Status<type>/<num> critical/cleared set/clear



veused

t 10

7011 5290


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, Low Order Path Remote Error Indicator (LP-REI) defects habeen detected for at least 2 seconds on the incoming line. The LP-REI signal isby the far end to indicate that one or more BIP-2 errors have been detected.

A clear will be issued when no LP-REI defects have been detected for at leasseconds.

Probable Cause

Type

Remedial actionCheck the status of the cable. Also check the status of the far end port.

Component Severity StatusLp/<num1> Sdh/0 Vc4/0 Vc12/<k>,<l>,<m>minor/cleared set/clear

241-5701-500 4.1S1


signalthe

ast

7011 5291


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, Low Order Path Remote Failure Indicator (LP-RFI) conditionhave been detected for at least 2 seconds on the incoming line. The LP-RFI sis used by the far end to declare a failure, which is a defect that persists beyondmaximum time allocated to the transmission system protection mechanisms.

A clear will be issued when no LP-RFI conditions have been detected for at le10 seconds.

Probable Cause

Type





eused

),

t 10

7011 5292


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, Low Order Path Remote Defect Indicator (LP-RDI) defects havbeen detected for at least 2 seconds on the incoming line. The LP-RDI signal isby the far end to indicate that a connectivity defect such as Low Order PathUnequipped (LP-UNEQ) or Low Order Path Trace Identifier Mismatch (LP-TIMor a server defect such as Tributary Unit Alarm Indication Signal (TU-AIS) orTributary Unit Loss of Pointer (TU-LOP) has been detected.

A clear will be issued when no LP-RDI detects have been detected for at leasseconds.

Probable Cause

Type

Remedial actionCheck the configuration and the status of the far end port.


241-5701-500 4.1S1


t 10

7011 5293


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, Tributary Unit Alarm Indication Signal (TU-AIS) defects havebeen detected for at least 2 seconds on the incoming line. The TU-AIS signalindicates that an upstream defect has been detected.

A clear will be issued when no TU-AIS detects have been detected for at leasseconds.

Probable Cause

Type





n-22.

cted

7011 5294


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, Low Order Path Bit Interleaved Parity (BIP-2) defects have beedetected for at least 2 seconds on the incoming line. The Low Order Path BIPalarm is generated if the calculated BIP-2 does not equal to the received BIP-

A clear will be issued when no Low Order Path BIP-2 detects have been detefor at least 10 seconds.

Probable Cause

Type

Remedial actionCheck the status of the cable. Also check the status of the far end port.


241-5701-500 4.1S1


ntes

t 10

7011 5295


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, a Tributary Unit Loss of Pointer (TU-LOP) condition has beedetected for at least 2 seconds on the incoming line. The TU-LOP signal indicathat an invalid pointer state is detected in the TU pointer.

A clearwill be issued when no TU-LOP detects have been detected for at leasseconds.

Probable Cause

Type


Component Severity StatusLp/<num1> Sdh/0 Vc4/0 Vc12/<k>,<l>,<m>critical/cleared set/clear



ates

ast

7011 5296


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, a Tributary Unit Unequipped (TU-UNEQ) condition has beendetected for at least 2 seconds on the incoming line. The TU-UNEQ signal indicthat an unequipped defect has been detected.

A clear will be issued when no TU-UNEQ detects have been detected for at le10 seconds.

Probable Cause

Type



241-5701-500 4.1S1


TU-

10

heck

7011 5297


<k> = 1 - 3, <l> = 1 - 7, <m> = 1 - 3

DetailsIf the status isset, a Tributary Unit Trace Identification Mismatch (TU-TIM)condition has been detected for at least 2 seconds on the incoming line. The TIM signal indicates that the received trace identification does not match theprovisioned value.

A clearwill be issued when no TU-TIM detects have been detected for at leastseconds.

Probable Cause

Type

Remedial actionCheck the far end port to ensure that the correct equipment is connected. Also cif the provisioned value is correct.

Component Severity StatusLp/<num1> Sdh/0 Vc4/0 Vc12/<k>,<l>,<m>critical/cleared set/clear



t 2s

0

7011 5300


<num2> = 0 - 1

type = JT2

DetailsIf the status isset, a Loss Of Signal (LOS) condition has been present for at leasseconds on the incoming line. An LOS condition occurs when the port receiveneither negative nor positive pulses.

A clear will be issued when no LOS condition has been detected for at least 1seconds.


TypeCommunications



241-5701-500 4.1S1


astot

al

7011 5301


<num2> = 0 - 1

type = JT2

DetailsIf the status isset, an Loss Of Frame (LOF) condition has been present for at le2 seconds on the incoming line. An LOF condition occurs when this port cannsynchronize to the incoming JT2 frame.

A clearwill be issued when this port has successfully framed the incoming signfor at least 10 seconds.

Whilst the port is in the LOF alarm state, a far-end RAI defect indicator istransmitted on the outgoing JT2 line.


TypeCommunications





n

ast

alid

7011 5302


<num2> = 0 - 1

type = JT2

DetailsIf the status isset, Physical Alarm Indication Signal (AISPhys) defects have beedetected for at least 2 consecutive seconds on the incoming line.

A clearwill be issued when no Physical AIS defects have been detected for at le10 consecutive seconds.

Receiving an AIS means that the far end port has lost the capability to transmit vJT2 frames or is has entered anadminState of Locked.

Whilst the rxAisPhysicalAlarm isset, a far-end RAI defect indicator is transmittedon the outgoing JT2 line for the duration of the alarm condition.


TypeCommunications



241-5701-500 4.1S1


en

east

the

7011 5303


<num2> = 0 - 1

type = JT2

DetailsIf the status isset, Payload Alarm Indication Signal (AISPayld) defects have bedetected for at least 2 consecutive seconds on the incoming line.

A clearwill be issued when no Payload AIS defects have been detected for at l10 consecutive seconds.

Receiving a Payload AIS means that the far end port has lost the capability totransmit valid JT2 frame payloads. The Payload AIS is defined as a bit array offrame payload in which all binary bits are set to ‘1’.


TypeCommunications





rs least

and

7011 5304


<num2> = 0 - 1

type = JT2

DetailsIf the status isset, then the far end Remote Alarm Indication (RAI) defect indicatohave been received. This is indicated immediately and remains present for at1 second.

A clear will be indicated when no far end RAI defect indicators are detected.


TypeCommunications

Remedial actionCheck the cabling between this port and the far end port, and the configurationstatus of the far end port.


241-5701-500 4.1S1


ent

the

to

7011 5501



<num3> = 0 - 15999

<type1> = DS3, E3, DS1 and E1.

<type2> = SONET and SDH.


DetailsIf the status isset, this port has been in a Loss of Cell Delineation state for Tactseconds, where Tact is thealarmActDelay attribute of the CELL component.

A clearwill be issued when the Loss of Cell Delineation state has not been presfor 10 consecutive seconds.

For DS3 and E3, in direct mapping mode, Loss of Cell Delineation occurs wheninterface is no longer able to identify ATM cell boundaries. In PLCP mappingmode, a Loss of Cell Delineation occurs when the interface is no longer able identify PLCP frame boundaries.


TypeCommunications

Remedial actionCheck configuration of the far end port.

Component Severity StatusLp/<num1> <type1>/<num2> major/cleared set/clearLP/<num1> <type2>/<num2> <type3>/0Laps/<num3> <type3>/0



ighI bits

7011 5601


<type> = DS3 and E3

<num2> = 0 - 2

DetailsIf the status isset, the link has entered a PLCP Far End Unavailable state. Thiscondition is declared upon declaration of a PLCP RAI alarm state.

A clear will be issued when the PLCP RAI alarm state is exited.

A PLCP RAI alarm state is entered when a 10 consecutive PLCP RAI bits are hin the incoming PLCP data stream, and cleared when 10 consecutive PLCP RAare low on the incoming line, or when PLCP mode is disabled.


TypeCommunications

Remedial actionCheck the cabling and configuration of the far end port.


241-5701-500 4.1S1


is

ing

7011 5602


<type> = DS3 and E3

<num2> = 0 - 2

DetailsIf the status isset, the link has entered a PLCP Near End Unavailable state. Thcondition is declared upon declaration of a PLCP LOF alarm state.

A clear will be issued when the PLCP LOF alarm state is exited.

A PLCP LOF alarm state is entered when this port is not able to frame the incomPLCP signal for 2 seconds, and exited when the port successfully frames theincoming PLCP signal for 10 seconds, or when PLCP mode is disabled.


TypeCommunications

Remedial actionCheck configuration of far end port.




isds.

CP

7011 5603


<type> = DS3 and E3.

<num2> = 0 - 2

DetailsIf the status isset, this port has entered a PLCP LOF state. A PLCP LOF state entered when the port cannot frame to the incoming PLCP signal for 2 secon

A clear will be issued when PLCP LOF state is exited, which occurs when PLframing is recovered for 10 seconds or when PLCP is disabled.

A PLCP RAI signal will be transmitted by this port for the duration of the PLCPLOF state.


TypeCommunications

Remedial actionCheck configuration of this port and the far end port.

Component Severity StatusLp/<num1> <type>/<num2> major/cleared set/clear

241-5701-500 4.1S1


ing

then

P

7011 5604


<type> = DS3 and E3.

<num2> = 0 - 2

DetailsIf the status isset, this port has entered a PLCP RAI state. A PLCP RAI state isentered when the port receives ten consecutive high PLCP RAI bits on the incomline.

A clear will be issued when the PLCP RAI state is exited, which occurs when port receives ten consecutive low PLCP RAI bits on the incoming line, or whePLCP mode is disabled.

The PLCP RAI signal will be transmitted by the far end port while it is in a PLCLOF state.


TypeCommunications


Component Severity StatusLp/<num1> <type>/<num2> major/minor/

clearedset/clear



32erelyted

one

ch

7011 5701


<num2> = 0 - 2

DetailsIf the status isset, the far end port has entered a G832 Unavailable state. A G8Far End Unavailable state is entered after ten consecutive G832 Far End SevErrored Seconds. A G832 Far End Severely Errored Second (FESES) is counduring second intervals containing more than 34 Far End Coding Violations oror more FERF defects.

A clear will be issued when the G832 Far End Unavailable state is exited, whioccurs after 10 consecutive seconds where no FESES are counted.


TypeCommunications


Component Severity StatusLp/<num1> E3/<num2> minor/cleared set/clear

241-5701-500 4.1S1


. Aef 2

d,type

7011 5702


<num2> = 0 - 2

DetailsIf the status isset, this port has entered an G832 Unexpected Payload Type stateG832 Unexpected Payload Type state is entered when the payload type in threceived E3 signal fails to agree with the expected payload type for a period oseconds.

A clear will be issued when the G832 Unexpected Payload Type state is exitewhich occurs when the received payload type agrees with the expected payloadfor a period of 10 seconds.


TypeCommunications





32r in

ichcted

7011 5703


<num2> = 0 - 2

DetailsIf the status isset, this port has entered a G832 Trail Trace Mismatch state. A G8Trail Trace Mismatch state is entered when the trail trace access point identifiethe received E3 signal fails to agree with the expected trail trace access pointidentifier for a period of 2 seconds.

A clear will be issued when the G832 Trail Trace Mismatch state is exited, whoccurs when the received trail trace access point identifier agrees with the expetrail trace access point identifier for a period of 10 seconds.

Probable CauseConfiguration error

TypeCommunications



241-5701-500 4.1S1


type

7011 6500


<type> = V35, X21 and HSSI


DetailsIf the status isset, the link is in alinkMode different from the one provisioned.

A clear will be issued when thelinkMode is changed to be the same as thatprovisioned.


TypeProcessing

Remedial actionConnect the port to a patch panel that is configured for the expectedlinkMode.

Component Severity StatusLp/<num1> <type>/<num2> warning/cleared set/clear



nd

7011 6501


<num2> = 0 - 7

DetailsIf the status isset, the physical termination configuration of the V.11 port isdifferent from that specified in theterminationRequired field of the provisioningdata.

A clearwill be issued when theterminationRequiredattribute is changed to be thesame as that physically configured.

Note that the card will have to be removed from the shelf for the physicaltermination configuration to be changed.


TypeProcessing

Remedial actionCheck if the provisioning data is correct. If it is, remove the function processor acorrect the physical termination configuration.

Component Severity StatusLp/<num1> X21/<num2> warning/cleared set/clear

241-5701-500 4.1S1


mport

kdce

Theved.

7011 6600

Legend<num1>=1-15

<num2> = 0

DetailsIf the status isset, this end dce has received a Local Digital Loopback request frothe dte end and enabled the loopback properly. The service and control on thisdce will be suspended.

A clear will be issued when this end dce has received a Local Digital Loopbacrequest from the dte end and removed the loopback properly, or when this endhas been put into the Locked state while handling loopback request from dte.service and control on this port dce will be resumed after the loopback is remo


TypeCommunications


Component Severity StatusLp/<num1> hssi/<num2> critical clear



E

d,.

use

ion

7011 6601

Legend<num1>=1-15

<num2> = 0

DetailsIf the status isset, the on-board dip switch has been closed to convert from the DCto DTE interface, but the cable is improperly connected or of the wrong type.

A clearwill be issued when the right NT null cable is used or properly connecteor the on-board dip switch is opened (that is, the DCE interface is configured)


TypeProcessing

Remedial actionIf the DTE configuration is selected (that is, the on-board dip switch is closed),the NT null modem cable to connect with the dce properly.

If the DCE configuration is selected, set the on-board dip switch to open positand use the HSSI standard cable.

Component Severity StatusLp/<num1> hssi/<num2> major clear

241-5701-500 4.1S1


ally.

7011 7000

Legend<application> = Trunk/<instance> Unack, DpnGateway/<instance> Utp, Fruni/<instance>


DetailsIf the status isset, the value set in theflagsBetweenFramesattribute of theFramercomponent is not supported on this FP version. The attribute is set to 1 intern

A clear will be issued if theflagsBetweenFrames attribute is set to 1.


TypeProcessing

Remedial actionProvision theflagsBetweenFrames attribute to 1, or replace the FP. Consult yourNortel Networks technical support group.

Component Severity Status<application> Framer warning/cleared set/clear



ay

lt

7011 7001

Legend<application> = Trunk/<instance> Unack, DpnGateway/<instance> Utp, Frdte/<instance>, Fruni/<instance>


DetailsIf the status isset, the value (crc16) set in theframeCrcTypeattribute of thisFramercomponent is not recommended on this FP version. Excessive frame errors mresult.

A clear is issued if theframeCrcTypeattribute is set to crc32 or noCrc.


TypeProcessing

Remedial actionProvision theframeCrcTypeattribute to crc32 or noCrc, or replace the FP. Consuyour Nortel Networks technical support group.


241-5701-500 4.1S1


sult.

l

7011 7002

Legend<application> = Trunk/<instance> Unack


DetailsIf the status isset, the value (interrupting) set in theframingType attribute of thisFramercomponent is not supported on this FP version. Excessive error may re

A clear is issued if theframingTypeattribute is set to hdlc.


TypeProcessing

Remedial actionProvision theframingTypeattribute to hdlc, or replace the FP. Consult your NorteNetworks technical support group.




een

e

7011 7003

Legend<application> = Htds/<instance>


DetailsIf the status isset, then a Framer error for the current application/service has bdetected. Currently, the only service that sets this alarm is HTDS, but otherapplications/services may use this alarm as well in the future.

Both ends of a Transparent Data Service path must have thelineSignalTransportattribute turned on forlineSignalTransport to work. This alarm is set when the 2ends do not match in this respect.

Note that the transparent data portion of this feature is unaffected (only thetransparent modem status lead transport part is affected).

A clear is issued if the problem indicated has been resolved.


TypeCommunications

Remedial actionProvision thelineSignalTransportattribute to the same value as provisioned on thother end of the HTDS path.

Component Severity Status<application> Framer major/cleared set/clear

241-5701-500 4.1S1


een

of. If

7011 7004




Incompatible VPort pathend configuration is detected. The Transparent DataService path must be between a DCE-DTE pair forlineSignalTransportto work.This alarm is set when the 2 ends don’t match in this respect.




TypeCommunications

Remedial actionReconfigure the VPort so that the operational attributeactualLinkModeis differentfrom the value on the other end of the HTDS path. For example, if the other endthe path is configured as DCE, then the local end must be configured as DTEthe other end of the path is configured as DTE, then the local end must beconfigured as DCE.




een

rentV35

ills

type or

7011 7005




Incompatible VPort pathend configuration is detected. Both ends of the TranspaData Service path must be of the same cardType (for example, either both areor both are V11) forlineSignalTransport to work. Attempting to run this feature(lineSignalTransport) on a non-Vport card (for example, DS1, E1, and so on) walso generate this alarm. This alarm is set when the 2 ends don’t match in thirespect.




TypeCommunications

Remedial actionMake sure both ends of the Transparent Data Service path are of the same cardsupporting Transparent Modem Status Transport (that is, either both are V35both are V11).


241-5701-500 4.1S1


ges

ide.d to

AS

ce isamer

7011 7006

LegendNone.

DetailsFramer service error encountered. Too many ABCD Signal changes for VoiceService. More then 25 ABCD changes per second or more than 450 ABCD chanon a whole link basis.

ABCD Signal Interpreter is disabled.

The ABCD Idle signal is transmitted to the egress/nearend side.

2 seconds later, an ABCD Seize signal is transmitted to the egress/nearend sThis seize is sent for 5 seconds, to prevent further calls from being initiated anallow the LINK to settle down in case of a temporary noisy LINK.

Following the 5 second settle down period, the channel re-enables its’ ABCD Csignaling events.


TypeCommunications

Remedial actionAn excess of ABCD CAS Signaling changes emanating from an outside sourbeyond our control. The excessive signalling has been seen to be a result of FrSync errors or Bit errors occurring on the link. Correct link quality.

Component Severity StatusVs Framer major message



ges

side.rther

duersist.

e isamer

7011 7007

LegendNone.

DetailsFramer service error encountered. Too many ABCD Signal changes for VoiceService. More then 25 ABCD changes per second or more than 450 ABCD chanper second on a whole link basis.

ABCD Signal Interpreter is disabled.

The ABCD Idle signal is transmitted to the egress/near-end side.

2 seconds later, an ABCD Seize signal is transmitted to the egress/near-end This seize is sent for 5 seconds.This has a dual purpose, one is to prevent fucalls to be initiated and second to allow the LINK to settle down in case of atemporary noisy LINK.

This alarm will not re-enable the Signal Interpreter such as alarm 7006. This isto the fact that it has already gone through 2 re-enables and the problem still pe

To re-enable the Signal Interpreter, LOCK then UNLOCK the Voice ServiceFramer.


TypeCommunications

Remedial actionTo re-enable the Signal Interpreter, LOCK then UNLOCK the Voice ServiceFramer.

An excess of ABCD CAS Signalling changes emanating from an outside sourcbeyond our control. The excessive signalling has been seen to be a result of FrSync errors or Bit errors occurring on the link. Correct link quality.

Component Severity StatusVs Framer major message

241-5701-500 4.1S1


thatn the

7011 8000


<num2> = 0 - 2

<type> = DS3, E3, Sonet, Sdh

DetailsThis warning message is issued to let the user know that the provisioning datahas just been activated will only be put into use when the test is terminated ospecified component.

Probable CauseOperational Condition

TypeCommunications

Remedial actionStop the test to put the provisioning data in use.

Component Severity StatusLp/<num1> <type>/<num2> warning message



.

he

larm

ot

7012 0050

LegendNone.

DetailsOn bus-based shelves, this alarms indicates that a power converter has failed

On fabric-based shelves, this alarm indicates that one of the units related to tpower supply has failed. This may due to any of the following conditions:

- an external AC rectifier has failed

- a processor card has had a power feed failure

- a breaker module has failed

Once the status changes, it takes approximately 2 minutes for the set or clear ato appear.

When the status is clear, the power supplies function correctly.


Type

Remedial actionOn bus-based shelves, replace the defective power converter.

On fabric-based shelves, examine thehardwareFailure attribute of the Shelfcomponent to determine why the alarm was generated. If the attribute does nsatisfactorily explain the cause of the alarm, see 241-5701-605Passport 7400,15000, 20000 User Access Guide for details on troubleshooting a power supplyproblem.

Component Severity StatusShelf major set/clear

241-5701-500 4.1S1


iled.

turectly

larm

it.

7012 0051

LegendNone.

DetailsOn bus-based shelves, when the severity is set to major, the cooling unit has faWhen the status is clear, the cooling unit functions correctly.

On fabric-based shelves, when the severity is set to major, one or more of thecooling unit fans have failed. When the severity is set to warning, the temperais higher than normal. When the status is clear, the cooling unit functions correand the temperature is within the normal range.



Type

Remedial actionEnsure that the cooling unit is powered and properly inserted before replacing

Component Severity StatusShelf major/warning set/clear



d is

7012 0052

LegendNone.

DetailsOne or more processor cards have failed. Once the status changes, it takesapproximately 2 minutes for the set or clear alarm to appear.

Probable CauseProcessor problem, Equipment failure

TypeEquipment

Remedial actionReplace the defective processor cards (the light on a defective processor caralways red).


241-5701-500 4.1S1


r theif the

haso the

oup.

g the

7012 0053

LegendNone.

DetailsOn bus-based shelves, this alarm indicates that the terminator card has failed omessage sent from the terminator card to the CP is corrupted. A clear is issuedterminator card has sent the message to the CP successfully.

On fabric-based shelves, this alarm indicates that the shelf’s MAC address cardfailed or has been removed, or the message sent from the MAC address card tprocessor cards is corrupted. A clear is issued if the MAC address card hassuccessfully sent the message to the processor cards.

Once the status changes, the set alarm appears only after 24 hours.


Type

Remedial actionFor bus-based shelves, contact your local Nortel Networks technical support gr

For fabric-based shelves, follow the standard maintenance procedure for testinMAC address card and remove or replace the defective unit(s).




y the

d byas

CC

oup.

g the

7012 0054

LegendNone.

DetailsOn bus-based shelves, this alarm indicates that the MAC addresses provided bterminator card are corrupted.

On fabric-based shelves, this alarm indicates that the MAC addresses providethe shelf’s MAC address card are corrupted, or that the MAC address card wreplaced with another MAC address card that supplies a different range of MAaddresses. When the status is clear, the MAC addresses provided by the MAaddress card are no longer corrupted.

Probable CauseCorrupt data, Equipment failure

Type

Remedial actionFor bus-based shelves, contact your local Nortel Networks technical support gr

For fabric-based shelves, follow the standard maintenance procedure for testinMAC address card and remove or replace the defective unit(s).

Component Severity StatusShelf major message

241-5701-500 4.1S1


m ised if

g the

7012 0055

LegendNone.

DetailsThis alarm is generated when the MAC address is not available. A minor alargenerated if it is unavailable when the CP starts up. A major alarm is generatthe MAC address is still unavailable after 4 minutes.

Probable Cause

Type

Remedial actionOn bus-based shelves, replace the terminator card.

On fabric-based shelves, follow the standard maintenance procedure for testinMAC address card and remove or replace the defective unit(s).

Component Severity StatusShelf minor/major set



ardnd is

nd

7012 0056

LegendNone.

DetailsOn fabric-based shelves, this alarm indicates that a failure of the Alarm/BITS chas been detected. The Alarm/BITS card is located at the back of the shelf, aresponsible for the generation of audible and visual alarms.

When the status is clear, the Alarm/BITS card is functioning properly.

Probable Cause

Type

Remedial actionFollow the standard maintenance procedure for testing the Alarm/BITS card aremove or replace the defective unit(s).

Component Severity StatusShelf minor set/clear

241-5701-500 4.1S1


wer

er

ot

7012 0057

LegendNone.

DetailsOn bus-based shelves, this alarm indicates that a power converter has failed.

On fabric-based shelves, this alarm indicates that the switch related to the posupply Feed A has tripped. Once the status changes, it takes approximately 2minutes for the set or clear alarm to appear.When the status is clear, the powsupplies function correctly.

Probable Cause

Type






wer

er

ot

7012 0058

LegendNone.

DetailsOn bus-based shelves, this alarm indicates that a power converter has failed.

On fabric-based shelves, this alarm indicates that the switch related to the posupply Feed B has tripped. Once the status changes, it takes approximately 2minutes for the set or clear alarm to appear.When the status is clear, the powsupplies function correctly.

Probable Cause

Type




241-5701-500 4.1S1


ssorrd,ote

,

7012 0100

Legend<instance> = 0 - 15

DetailsThis alarm is generated when a card is not capable of running a logical proce(LP). A critical alarm is generated if an LP has been configured to run on the caor a minor alarm is generated if no LP has been configured to run on the card. Nthat no alarm is generated if the Card component’scardTypeattribute has not beenset.


TypeEquipment

Remedial actionNo remedial action is needed if this is just a temporary condition (for examplewhen the card is re-initializing itself). If the condition persists, check the Cardcomponent’savailabilityStatus andfailureCause attributes for a more specificproblem cause.

Component Severity StatusShelf Card/<instance> minor/critical set/clear



tion

n how

ote

7012 0101


DetailsThis alarm is generated after a card reboots. It holds some diagnostic informa(in the comment data field) that specifies why the card went down. Severalinstances of this alarm can be generated after the card reboots (depending omuch information needs to be displayed). This information is referred to asTrapData information.


TypeEquipment

Remedial actionRead theTrap Datainformation to determine why the card rebooted. If the reboreason in theTrap Datainformation does not satisfactorily explain the cause of threboot, see 241-5701-520Passport 7400, 15000, 20000 Troubleshooting Guidefordetails on troubleshooting a control processor or function processor crash.

Component Severity StatusShelf Card/<instance> indeterminate message

241-5701-500 4.1S1


d on

7012 0102


DetailsThis alarm is generated when a CP starts running as the active CP. It is issueinitial power up as well as after a CP switchover.

Probable CauseResponse time excessive



Component Severity StatusShelf Card/<instance> warning message



ly has

larm

7012 0103


DetailsWhen the status is set on a processor, one of the units related to power suppfailed. This may result from any of the following:

- the fed -48V falls to less than 39.5V

- a processor interface module has failed, or

- battery A feed failure


When the status is clear, the power supplies are functioning correctly.


TypeEquipment

Remedial actionExamine the alarm record or the hardwareAlarm attribute under theShelf Cardcomponent to determine which card is generating the alarm, and replace thedefective power converter.

Component Severity StatusShelf Card/<instance> major set/clear

241-5701-500 4.1S1


ly has

larm

7012 0104


DetailsWhen the status is set on a processor, one of the units related to power suppfailed. This may result from any of the following:

- the fed -48V falls to less than 39.5V, or

- a processor interface module has failed.

- battery B feed failure


When the status is clear, the power supplies are functioning correctly.


TypeEquipment

Remedial actionExamine the alarm record or the hardwareAlarm attribute under theShelf Cardcomponent to determine which card is generating the alarm, and replace thedefective power converter.

Component Severity StatusShelf Card/<instance> major set/clear



hese

ed:

hen,

7012 0105


DetailsThis alarm is generated when a card executes a special script while booting. Tscripts are usually not deployed in customer environments.

Probable Cause

Type

Remedial actionTo clear the alarm you must remove the related files and reset the card.

To do this:

Issue the following command to go the bin directory, where the files are locatcd -p(“system/bin”) fs

Issue the following command to know which script files are present:ls fs

To remove the script files, issue either or both of the following commands,according to the result of the previous command: remove -r -f -p(startup.card<instance>) fs or remove -r -f -p(startup.rom.card<instance>) fs treset the card that causes the alarm: reset shelf card/<instance>.

Component Severity StatusShelf Card/<instance> warning set

241-5701-500 4.1S1


d’s

ent’s

7012 0151


DetailsThe Card component’s provisioned card type does not match the inserted carcard type.


TypeProcessing

Remedial actionReplace the card with one of the appropriate type, or update the Card componcardType attribute.

Component Severity StatusShelf Card/<instance> major message



7012 0152


DetailsNo card is configured for this slot (the Card component’scardTypeattribute has notbeen set), but a card is present in the slot.


TypeProcessing

Remedial actionRemove the card, or set the Card component’scardType attribute.


241-5701-500 4.1S1


d is

7012 0153


DetailsThe card cannot load its software.


TypeProcessing

Remedial actionReplace the card or change the card’s software load. The card’s software loadetermined by thefeatureList attribute of the Logical Processor Type (LPT)component associated with the card’s LP.




7012 0154


DetailsThe card failed its self-test diagnostics.


TypeEquipment

Remedial actionReplace the card.


241-5701-500 4.1S1


7012 0155


DetailsExcept for enabling its access on the backplane, the card is not responding.


TypeEquipment





7012 0156


DetailsThe card has a backplane connectivity problem.


TypeEquipment



241-5701-500 4.1S1


t not is,

.

hennot the

7012 0200


DetailsThis alarm is generated when the logical processor (LP) is not running. Note thaalarm is generated if the LP is not configured to run on any processor card (thawhen the LP component’smainCard andspareCard attributes have not been set)


TypeProcessing

Remedial actionNo remedial action is needed if this is just a temporary condition, for example, wthe LP is re-initializing itself. If the condition persists, it is because the LP doeshave a working processor card to run on. Clear the problem that is preventingLP’s processor card from being able to run the LP.

Component Severity StatusLp/<instance> critical set



to

ed in

over

7012 0201


DetailsTraffic will be disrupted in {15,10 and 5} minutes caused by an LP switchoverthe spare card.

A deferred switchover has been scheduled for this LP. This message is displayorder to notify the operator that a traffic disruption will occur for this LP. Thismessage will appear three times, once at 15, 10 and 5 minutes, before switchoccurs. Each message will indicate the time remaining.

Probable CauseOperational condition, Underlying resource unavailable

TypeOperator, Processing

Remedial actionThe scheduled switchover may be cancelled.

Component Severity StatusLp/<instance> warning message

241-5701-500 4.1S1


7012 0202


DetailsThis alarm is generated when a scheduled LP switchover fails.

A switchover was attempted for this LP, but failed for the followingreason: A spare logical processor is not available.

A clear is issued when either one of the following occurs:- The switchover subsequently succeeds whether immediate or scheduled.- The active instance of the LP goes down and a switchover is forced.


TypeOperator

Remedial actionEnsure that the LPspareCardStatus attribute is set to “available.”

Component Severity StatusLp/<instance> major/cleared set/clear



was

tageisulervice.

Ared.

he

7012 0203

Legend<time>: time stamp before outage.

<type of outage>: CP, module, swMigration.

DetailsActive CP last time in service: <time> (<type of outage> outage).

This alarm is generated when an outage occurs. The last time that the active CPin service is displayed.

There are three types of outages: CP, module and software migration. A CP ouindicates that a CP switchover occurred and the FPs may have stayed up. Thhappens when the conditions for hot standby CP redundancy are met. A modoutage indicates that a CP went down and the entire module has gone out of seThis indicates that hot standby CP redundancy has been disabled or that thecorresponding conditions for hot standby CP redundancy have not been met.software migration outage indicates that a software migration switchover occur


TypeEquipment

Remedial actionNo remedial action is required. This information is used off-switch to calculate tduration of the outage.

Component Severity StatusLp/0 warning message

241-5701-500 4.1S1


rov

ingn.

onalportor the

uing

7012 0204

DetailsThis Lp can not achieve its expected Migration-Switchover behavior. Refer to PMigration alarm for more details.

At the start of a software migration activation a response is generated indicatwhich Lps do not support the reduced service outage during software migratioThis is based on operational and provisionable conditions.

This alarm is generated for an Lp not identified in the response, whose operaticonditions change during the software migration such that it can no longer supthe reduced service outage. This alarm is generated when the FPs destined fmigration shelf are chosen.


TypeOperator

Remedial actionIf deemed appropriate, the software migration activation can be stopped by issthe stop provisioningSystem command while in provisioning mode.

Component Severity StatusLp warning message



d has

erity

e.

rity

7012 0300

Legend

DetailsThis alarm indicates that one of the standby service instances on the parent Carencountered a condition which the user should be made aware of.

The standby service has likely encountered one of the following:

• a software error

• an engineering/resource limit reached

• an application-specific problem

If the standby service is unable to provide standby capability as a result, the sevis critical. This degrades the potential for a complete equipment protectionswitchover and a 7012 0301 alarm (also against SparedServices) tracks theoutstanding condition from the Preside Multiservice Data Manager perspectiv

If the condition does not affect the ability to provide standby capability, the seveis warning.

The comment text contains the following information about the service whichinitiated the alarm coming out:

• ComponentName

• DateAndTime

• ActiveListStatus

• PerceivedSeverity

• AlarmType

• ProbableCause

• NTPIndex

• NotificationId

• CommentData

Component Severity StatusShelf Card/n SparedServices warning/critical message

241-5701-500 4.1S1


.

• FileInformation

Probable Cause

Type

Remedial actionLook up the NTPIndex from the Comment text and perform its remedial action



t Cardr a

300

ovide

sly

7012 0301

Legend

DetailsIf the status is set, at least one of the standby service instances on the parenhas been unable to provide standby capability, thus degrading the potential focomplete equipment protection switchover. Look for a previously issued 7012 0alarm (also against SparedServices) which could indicate more details.

A clear is issued after all standby service instances are once again able to prstandby service.

Probable CauseApplication subsystem failure

TypeProcessing

Remedial actionIf the status is set, the action to take is really based on the information in previouissued 7012 0300 alarms.

Component Severity StatusShelf Card/n SparedServices warning/cleared set/clear

241-5701-500 4.1S1


et to

as

g ishe

7013 0000


DetailsIf the status isset, available shared memory for the logical processor (LP) hasdecreased below 12.5%. The LP is experiencing an unbalanced traffic flowresulting in high queueing delays and shared memory depletion. This alarm is swarn of impending shared memory exhaustion.

A clearwill be issued automatically when available shared memory for the LP hincreased above 18.75%.

Probable Cause

Type

Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired in order to balance the flow of traffic through this LP, thus reducing tamount of traffic congestion and length of queueing delays.

Component Severity StatusLp/<instance> minor/cleared set/clear



tion.rces

ove

inge

7013 0001


DetailsIf the status isset, available shared memory for the logical processor (LP) hasdecreased below 6.25%. The LP is experiencing an unbalanced traffic flowresulting in high queueing delays, and is approaching shared memory exhausIn the case of the control processor (that is, Lp/0), the alarm indicates that resouare being held up on the CP.

When this condition is detected, the largest shared memory traffic queues arepurged automatically until available shared memory for the LP has increased ab9.39%. Aclear is issued automatically at this point.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineermust be performed to balance the flow of traffic through this LP and reduce thamount of traffic congestion and length of queueing delays.


241-5701-500 4.1S1


P)ffic

e

25%

ute.

g is

7013 0002

Legend<instance>=0-15

DetailsIf the status isset, the available ingress cell-blocks from the logical processor (Lhave decreased below 20% of total ingress cell-blocks. Under this condition, traflowing across this FP may encounter high queueing delays.

When this condition is detected, the less priority traffic will be discarded first. If thcongestion still persists, even higher priority traffic will be discarded. Thiscontinues until available ingress cell-blocks for the LP have increased above of total ingress cell-blocks. Aclear will be issued automatically at this point. Afiltering mechanism is implemented such that a set/clear is issued by one min



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired to balance the flow of traffic through this card in order to reduce theamount of traffic and the length of queues.

Component Severity StatusLP/<instance> warning/cleared set/clear



rtion,

e

25%

ute.

g is

7013 0003


DetailsIf the status isset, the available ingress frame-blocks from the logical processo(LP) have decreased below 20% of total ingress frame-blocks. Under this conditraffic flowing across this FP may encounter high queueing delays.

When this condition is detected, the less priority traffic will be discarded first. If thcongestion still persists, even higher priority traffic will be discarded. Thiscontinues until available ingress frame-blocks for the LP have increased aboveof total ingress frame-blocks. Aclear will be issued automatically at this point. Afiltering mechanism is implemented such that a set/clear is issued by one min



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired to balance the flow of traffic through this card in order to reduce theamount of traffic and the length of queues.


241-5701-500 4.1S1


P)ffic

e

% of

g isf

7013 0004


DetailsIf the status isset, the available egress cell-blocks from the logical processor (Lhave decreased below 20% of total egress cell-blocks. Under this condition, traflowing across this FP may encounter high queueing delays.

When this condition is detected, the less priority traffic will be discarded first. If thcongestion still persists, even higher priority traffic will be discarded. Thiscontinues until available egress cell-blocks for the LP have increased above 25total egress cell-blocks. Aclearwill be issued automatically at this point. A filteringmechanism is implemented such that a set/clear is issued by one minute.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired to balance the flow of traffic through this card-reducing the amount otraffic and length of queues.




P),

e

25%

ute.

g isf

7013 0005


DetailsIf the status isset, the available egress frame-blocks from the logical processor (Lhave decreased below 20% of total egress frame-blocks. Under this conditiontraffic flowing across this FP may encounter high queueing delays.

When this condition is detected, the less priority traffic will be discarded first. If thcongestion still persists, even higher priority traffic will be discarded. Thiscontinues until available egress frame-blocks for the LP have increased aboveof total egress frame-blocks. Aclear will be issued automatically at this point. Afiltering mechanism is implemented such that a set/clear is issued by one min



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired to balance the flow of traffic through this card-reducing the amount otraffic and length of queues.


241-5701-500 4.1S1


enhI bitgged

that

g ishecard

7013 0011


DetailsIf the status isset, available shared memory for the logical processor (LP) has fallbelow 25%. The LP is experiencing an unbalanced traffic flow resulting in higqueueing delays and shared memory depletion. This alarm is set to warn of FCsetting in packet header of data traffic and possible discard of data packets taas low, medium and high discard priority. in the case of the control processor (is, Lp/0), this alarms indicates that resources are being held up on the CP.

A clear is issued automatically when available shared memory for the LP hasexceeded 25% after 1 minute.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired in order to balance the flow of traffic through this LP, thus reducing tamount of traffic congestion and length of queueing delays, and preventing disof data traffic. In the case of the CP, determine which services are holding upresources on t he CP, and take appropriate action.




r localll

uent.

f the

g isary.

7013 0021


DetailsIf the status is set, available message blocks in local memory for the logicalprocessor (LP) has decreased below 6.25%. Local message blocks are used focontrol messaging on the card. The LP is experiencing an unbalanced contromessage traffic flow resulting in high queuing delays, and is approaching locamemory exhaustion.

As long as this level of congestion persists, some of the lower priority subseqcontrol activities on the LP will not be performed due to insufficient resources

One minute after the set alarm was issued, a clear will be issued automatically iavailable message blocks in local memory have increase above 6.25%.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired. Contact your local Nortel Networks technical support group, if necess


241-5701-500 4.1S1


locall

uent.

lly if

g isary.

7013 0022


DetailsIf the status is set, available message blocks in local memory for the logicalprocessor (LP) has decreased below 60%. Local message blocks are used forcontrol messaging on the card. The LP is experiencing an unbalanced contromessage traffic flow resulting in high queuing delays.

As long as this level of congestion persists, some of the lower priority subseqcontrol activities on the LP will not be performed due to insufficient resources

Five minutes after the set alarm was issued, a clear will be issued automaticathe available message blocks in local memory have increase above 60%.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired. Contact your local Nortel Networks technical support group, if necess




ed

d

r and

g isLP.

7014 0000


DetailsIf the status isset, available memory for the logical processor (LP) has decreasbelow a threshold of 960 Kbytes of the memory on a control processor and160 Kbytes of the memory on a function processor. Various systems will avoiallocating memory.

A clear will be issued automatically when available memory for the LP hasincreased above the clear threshold which is 1010 Kbytes on a control processo180 Kbytes on a function processor.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired in order to balance the memory consumption of the applications on thisContact your local Nortel Networks technical support group for assistance ifnecessary.


241-5701-500 4.1S1


ed

ateof

the a

intact

y.

7014 0001


DetailsIf the status isset, available memory for the logical processor (LP) has decreasbelow a threshold of 400 Kbytes of the memory on a control processor and 40Kbytes of the memory on a function processor. Only critical systems will allocmemory. This condition must be resolved quickly because a total exhaustion memory will result in the automatic resetting of the card.

A clear will be issued when available memory for the LP has increased aboveclear threshold which is 480 Kbytes on a control processor and 60 Kbytes onfunction processor.



Remedial actionFrequent occurrences of this condition indicate that re-engineering is requiredorder to balance the memory consumption of the applications on this LP. Conyour local Nortel Networks technical support group for assistance if necessar




ous

g isLP.

7014 0010


DetailsIf the status isset, availablehigh-speedmemory for the logical processor (LP) hasdecreased below a threshold of 8 Kbytes of the memory on a processor. Varisystems will avoid allocatinghigh-speed memory.

A clearwill be issued when availablehigh-speedmemory for the LP has increasedabove the clear threshold which is 10 Kbytes of thehigh-speed memory on theprocessor.



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired in order to balance the memory consumption of the applications on thisContact your local Nortel Networks technical support group for assistance ifnecessary.

Component Severity StatusLp/<instance> minor/cleared message

241-5701-500 4.1S1


intact

y.

7014 0011


DetailsIf the status isset, availablehigh-speedmemory for the logical processor (LP) hasdecreased below a threshold of 4 Kbytes of thehigh-speedmemory on a processor.Only critical systems will allocate additional memory. This condition should beresolved quickly because a total exhaustion of memory will result in degradedservice.

A clearwill be issued automatically when availablehigh-speedmemory for the LPhas increased above the clear threshold which is 6 Kbytes of thehigh-speedmemory.

Probable Cause

Type

Remedial actionFrequent occurrences of this condition indicate that re-engineering is requiredorder to balance the memory consumption of the applications on this LP. Conyour local Nortel Networks technical support group for assistance if necessar

Component Severity StatusLp/<instance> major/cleared message



time

ver,

and

7015 0000

Component Severity StatusTime major/cleared set/clear

LegendNone

DetailsModule stops time synchronization with network time server

This alarm is generated when Passport loses synchronization with the networkserver. This happens when the network time server is not responding to thePassport’s XNTP request.

Module starts time synchronization with network time server

A clear is issued when Passport starts synchronizing with the network time serbecause Passport is now getting XNTP responses from the time server.


TypeEnvironmental

Remedial actionEnsure that the network time server is running as a proper stratum time serverthat the time server is reachable from the Passport.

241-5701-500 4.1S1


e

7015 0001

LegendNone.

DetailsThis alarm is generated when the network time has changed by more than onminute. The network time may change after synchronizing the module to thenetwork or when the operator sets the time manually.

Probable CauseOperational condition, Network server intervention, Unknown

TypeOperator, Environmental, Unknown


Component Severity StatusTime warning message



d theing

the

andfter.

7015 0002

LegendNone.

DetailsThis alarm is generated when the time difference between the Passport UTC(moduleTime minus offset) and the network time server is greater than 1000seconds.

The synchronization status of Passport XNTP is changed to unsynchronized anmain server is set to NULL. This allows the operator to correct the time by settthe moduleTime manually.

A clear is issued when the network time is corrected to within 1000 seconds ofnetwork time server.


TypeEnvironmental

Remedial actionCheck the time of the network time servers and the time of Passport module,correct the time manually by setting the moduleTime of the Passport module. Aa few minutes, the Passport XNTP synchronizes with the network time server

Component Severity StatusTime Major/cleared set/clear

241-5701-500 4.1S1


DPP

Ip,n

port

s if

7015 0010

LegendNone.

DetailsThe Server is disabled.

This alarm is generated when the Passport XNTP fails to register an XNTP Uport with vrIP at start up time. When Passport XNTP fails to register an XNTP UDport with vrIP, and the ipStack of the network time server is provisioned to be vrthe network time server is disabled. Passport XNTP stops time synchronizatiowith the network time server.

The Server is enabled

A clear is issued when Passport XNTP successfully registers an XNTP UDP with vrIp. Passport XNTP starts to synchronize with the network time server.


TypeCommunications

Remedial actionCheck the status of vrIp, to see if they are running correctly. Correct the errorfound. Passport XNTP will try to register with vrIp every 10 minutes until itsucceeds.

Component Severity StatusTime Sever/n minor/clear set/clear



they be

rver.

ith

NTP

7015 0011

LegendNone.

DetailsNo response from the time server, the server is idle.

This alarm is generated if Passport XNTP does not receive any packets fromnetwork time server after it sends 8 packets to the network time server. This madue to one of the following reasons:

1.Network error

The provisioned network time server does not exist, or a network error occursprevents Passport XNTP from receiving any packets from the network time se

2.Server configuration error

The network time server’s configuration prevents this module from acting as aclient to synchronize its time with the network time server.

3.Protocol error

The version of the XNTP running on the network time server is not compatible wPassport XNTP version, so that the network time server does not reply to thePassport XNTP time synchronization request.

Get response from the server, the Server is active.

A clear is issued when the error(s) listed above are corrected, and Passport Xreceives responses from the network time server.


TypeCommunications

Remedial actionCheck the existence and connectivity of the network time server and take theappropriate action.


241-5701-500 4.1S1


of the

er is

7015 0012

LegendNone.

DetailsModule does not communicate with this network time server correctly.

This alarm is generated when the network time server is not selected as one network time synchronization sources, although its OSI state is “unlocked”,“enabled” and “active”. This may be due to one of the following reasons:

- The network time server itself is not synchronized.

- The network time server’s stratum is higher than Passport XNTP’s stratum.

Module starts to communicate with this network time server correctly.

A clear is issued when the above errors are corrected and the network time servselected as one of the time synchronization sources of this module.


TypeEnvironmental

Remedial actionCheck the status, stratum, leap and other XNTP protocol information of XNTPrunning on the network time server, correct any errors if found.




ready

of

7016 1000

LegendNone.

DetailsThis alarm is generated if the FDCR cannot register a dynamic or static DNArequested by an application process, because another application process aleither statically owns a DNA which is the subset/superset/same DNA of thespecified DNA or dynamically owns a DNA which is the subset/superset DNAthe specified DNA.

Probable Cause

Type

Remedial actionVerify that the DNA statically provisioned for one of the Passport applicationprocesses does not clash with the DNA dynamically configured at the otherapplication process.

Component Severity StatusFdcr minor message

241-5701-500 4.1S1


zed

ree

otnd a

7017 1000

LegendNone.

DetailsIf the status isset, a reference has been provisioned and the CP is not synchronito the reference.

A clearwill be issued if no references are provisioned and the CP is currently frunning or if the CP is synchronized to the incoming reference.


TypeCommunications

Remedial actionThe PLL algorithm should resynchronize the clock. However, if the alarm is ncleared after an hour of being set, the clocking source is probably unreliable anew clocking source should be provisioned.

Component Severity StatusNS minor/cleared set/clear



seen

7018 0001

Legend<num> = 1 - 255

DetailsThisPath Administrator component has been provisioned with amaxLc valuewhich is less than the value provisioned on the adjacentPath Administratorcomponent running on the neighbor module. The neighbouringPath Administratorcomponent will generate alarm 7018 0002.

Probable Cause

Type

Remedial actionInitially none because thePath Administratorcomponents will resolve this conflictby choosing the smaller of the two provisionedmaxLcvalues. Since bothPathAdministrator components resolve the conflict in the same manner, the maxLcvalues actually used will be the same at both ends. The resulting value can bein thenegotiatedMaxLc operational attribute.

Some time in the future, reprovision one of thePath Administratorcomponents sothat itsmaxLc attribute agrees with its neighborPath Administrator component.

Component Severity StatusTrk/<num> Pa warning message

241-5701-500 4.1S1


seen

7018 0002


DetailsThis Path Administrator component has been provisioned with amaxLc valuewhich is greater than the value provisioned on the adjacentPath Administratorcomponent running on the neighbor module. The neighbouringPath Administratorcomponent will generate alarm 7018 0001.

Probable Cause

Type

Remedial actionInitially none because thePath Administratorcomponents will resolve this conflictby choosing the smaller of the two provisionedmaxLc values. Since bothPathAdministrator components resolve the conflict in the same manner, the maxLcvalues actually used will be the same at both ends. The resulting value can bein thenegotiatedMaxLc operational attribute.

Some time in the future, reprovision one of thePath Administratorcomponents sothat itsmaxLc attribute agrees with its neighbor Path Administrator component.

Component Severity StatusTrk/<num> Pa warning message



ns

ryin

7018 0003


DetailsThePath Administrator component is unable to allocate enough high speedmemory for all of the logical channels it is being asked to support. This happewhen the value of themaxLc attribute for one or more of the Path Administratorcomponents on a particular card is excessively large.

Probable Cause

Type

Remedial actionIf the operator does not change the value of themaxLcattribute, thePathAdministratorcomponent will place all of the logical channels into slower memowhere they will work, albeit more slowly. This will cause a noticeable reductiontrunk throughput.

Review the value of themaxLcattribute for eachPath Administratorcomponent onthe card and make sure that none is larger than necessary.

Component Severity StatusTrk/<num> Pa minor message

241-5701-500 4.1S1


eedns

avee of

7018 0004


DetailsThe Path Administrator component is unable to allocate enough high or low spmemory for all of the logical channels it is being asked to support. This happewhen the value of themaxLc attribute for one or more of thePath Administratorcomponents on a particular card is excessively large.

As a result of this problem thisPath Administratorcomponent will not come up andhence will be unable to support path-oriented traffic.

Probable Cause

Type

Remedial actionReview the value of themaxLcattribute for eachPath Administratorcomponent onthe card and make sure that none is larger than necessary. If you still find you hinsufficient memory to support the number of channels you require, one or morthe trunks may have to be moved to a separate card.

Component Severity StatusTrk/<num> Pa critical/cleared set/clear



A. Therrythiseer

y toe

PA

ededthe

7018 0007

Legend<instance> = 0

DetailsIf the status isset, the PA subcomponent of this Trk/<instance> is not up. The Pwas unable to stage with it’s peer PA due to excessive retries and has given upTrk will go up and be able to carry connectionless traffic but will be unable to capath oriented traffic until the alarm is cleared. There are two common causes ofalarm. Either there is no PA component provisioned under the peer Trk or the ptrunk was lock forced and unlocked very rapidly. A rapid lock force/unlock cancause the PA to be unable to stage with its peer. For this reason it is best onlissue an unlock on a Trk after the Trk has responded to the lock force with thlockedset alarm.

A clearwill be issued when the PA is able to restage with its peer or when theand/or Trk component are deleted.

Probable Cause

Type

Remedial actionCheck to ensure that a PA is provisioned at the far end under the peer Trkcomponent. If this is not the problem then it is likely that the trunk was lock forcand unlocked in rapid succession. A rapid lock force/unlock is not recommendand the operator should wait until the trunk sets its locked alarm before issuingunlock. (We plan to remove this restriction in a later release).

Component Severity Statustrk/<instance> major/cleared set/clear

241-5701-500 4.1S1


gffic

ed

7018 0009


DetailsThis Path Administrator component has been provisioned with an AtmAccesssubcomponent which is provisioned for a mode that is different than the PathAdministrator’s peer AtmAccess subcomponent. One Path Administrator wasprovisioned for mapped mode and the other for multiplexed mode.

Probable Cause

Type

Remedial actionInitially none because the Path Administrators will resolve this conflict by ignorinthe fact they were provisioned with an AtmAccess subcomponent. That is, all trawill be routed over the parent trunk’s AAL5 VCC.

Some time in the future, one of the Path Administrators should be reprovisionsuch that it’s mode agrees with its peer’s mode.

Component Severity StatusTrk/<num> Pa minor/cleared set/clear



7018 0010


DetailsThePath Administrator component has been provisioned with anAtmAccesssubcomponent which is connected to anotherPath Administrator’s AtmAccesssubcomponent, but thatPath Administrator component is not thisPathAdministratorcomponent’s peer. That is, the twoPath Administratorcomponentsdo not belong to the same parent trunk.

Probable Cause

Type

Remedial actionInitially none because thisPath Administratorcomponent will resolve the problemby ignoring the fact it was provisioned with anAtmAccesssubcomponent. That is,all traffic will be routed over the parent trunk’s AAL5 VCC.

Reprovision thisPath Administrator component or its peerPath Administratorcomponent such that theirAtmAccess subcomponents can connect.


241-5701-500 4.1S1


7018 0011


DetailsThisPath Administrator component has been provisioned with anAtmAccesssubcomponent which is not connected to the peerPath Administratorcomponent’sAtmAccess subcomponent.

Probable Cause

Type

Remedial actionInitially none because thePath Administratorcomponents will resolve the problemby ignoring the fact it was provisioned with anAtmAccesssubcomponent. That is,all traffic will be routed over the parent trunk’s AAL5 VCC.

Reprovision thisPath Administrator component or its peerPath Administratorcomponent such that theirAtmAccess subcomponents can connect.




bleal

er

ortsh

gffic

ed to

7018 0012


DetailsThisPath Administrator component is provisioned with anAtmAccesssubcomponent which is in mapped mode but there are insufficient VCCs availain the VP of the parent trunk’s VCC to support the negotiated number of logicchannels.

When thePa component comes up it will look at theAtmIf/n Ca andAtmIf/nConnMap components to determine the size and offset of the auto selected(dynamic) VCC space for this VP. It then exchanges this information with its pePacomponent. The twoPa components then compute the overlap in the tworectangles and restrict their allocation of VCC’s to this rectangle. This alarmindicates that the computed overlapping rectangle is not large enough to suppmaxLc+10 channels. (The extra 10 channels are required for bumping and claresolution).

Probable Cause

Type

Remedial actionInitially none because the Path Administrators will resolve this conflict by ignorinthe fact they were provisioned with an AtmAccess subcomponent. That is, all trawill be routed over the parent trunk’s AAL5 VCC.

Some time in the future either the VCC space for this VP needs to be increassupport maxLc+10 VCIs past theminAutoSelect (dynamic) threshold or maxLcneeds to be decreased to fit.


241-5701-500 4.1S1


vel

.

m isk,ed

isthe

to

7018 0013

Legend<num> = a decimal value

DetailsThis alarm is issued by aTrunk/nwith aPathAdmincomponent. The alarm can beset only if themaxAdaptationLevel of Trunk/n PathAdminhas a non-zero value.

If the status isset, the trunk utilization has exceeded thelevel1 value specified byadaptationThreshold for the period of time specified by the set value ofadaptationHoldOffTime, and PORS adaptation is now active, whereby calls areprevented from being established over the trunk.

A clear is issued, when the trunk utilization has subsequently fallen back to a leat or below thelevel1value specified byadaptationThresholdfor the period of timespecified by theclear value of adaptationHoldOffTime, PORS adaptation is nolonger active, whereby new calls are allowed to be established over the trunk

Probable Cause

Type

Remedial actionThe alarm indicates that the trunk has sustained high utilization. When the alarissued, PORS prevents new connections from being established over the trunwhich helps to prevent the trunk getting more highly utilized. If the alarm is issuover a relatively short period of time, it may be an indication that the thresholdsetting is too low. If so, adjust the threshold accordingly. If the threshold settingalready high, the alarm is also issued, and it takes a relatively long time to clearalarm, re-engineering the links or VCCs on this node may be needed in orderalleviate the high utilization condition.




otentent

lict

sonebor

7018 0014


DetailsThisPath Administratorcomponent has been provisioned with a value that does nmatch with the value provisioned on the adjacent Path Administrator componrunning on the neighbor module. The neighboring Path Administrator componwill generate the same alarm.

Probable Cause

Type

Remedial actionInitially none because the Path Administrator components will resolve this confby choosing the correct value of the two provisioned values. Since both PathAdministrator components resolve the conflict in the same manner, the valueactually used will be the same at both ends. Some time in the future, reprovisionof the Path Administrator components so that its attribute agrees with its neighPath Administrator component.


241-5701-500 4.1S1


nthe

e you

7018 1001

Legend<component_name> = component of system which is using the path orientedrouting virtual circuit


DetailsThePermanentLogicalConnection subcomponent of this service componentspecifies aremoteNameattribute which does not match the name of the componewhich is attempting to establish a connection with it. This results in rejection of tcall request and the service failing to come up.

Probable Cause

Type

Remedial actionVerify that the remoteName attribute of the PLC of this service matches the namof the component that is trying to connect to it and vice versa. Make sure thatuse short forms for the names of the components in theremoteNameattribute string.

Component Severity Status<component_name>/<instance> LCo critical message



to

mee

7018 1002



DetailsThePermanentLogicalConnection subcomponent of this service componentspecifies aremoteName attribute which refers to the same parent servicecomponent. This results in rejection of the call request and the service failing come up.

Probable Cause

Type

Remedial actionYou must reprovision the service component’s PLC subcomponent to have aremoteNamethat does not refer to the parent service. Remember, the remoteNagives the full name of the component that you want to connect to including thmodule name on which that component resides.

Component Severity Status<component_name>/<instance> LCo critical message

241-5701-500 4.1S1


tiond of

s

s the canm

7018 1003



DetailsTheLogicalConnection (LCo) subcomponent of this service component hasdetected that one or more provisional attributes at the called end of the connecdiffers in value from the calling end. This alarm only appears on the called enthe connection. The calling end values will be used until the connection isterminated. When this alarm occurs it indicates that theLCooperational attributeswould differ depending on which end established the connection. This alarm isuppressed when a PLC does not have aremoteName attribute specified on bothends of the connection.

Probable Cause

Type

Remedial actionYou must reprovision the service component’sPLC subcomponent to haveidentical attributes at both ends. This ensures that for whichever end establisheconnection, the operational attribute will be consistent and that re-connectionoccur from both ends of theLCo. This makes re-connection more robust. The alarindicates all attributes that require reprovisioning.

Component Severity Status<component_name>/<instance> LCo warning message



7018 1004



DetailsTheLogicalConnection (LCo) subcomponent of this service has received a setoverrideRemoteName command while theremoteName component of the PLC isnon-blank. This prevents accidental overriding.

Probable Cause

Type

Remedial actionYou must reprovision the service component’sPLC remoteNameattribute to blankto use the overrideRemoteName set command.

Component Severity Status<component_name>/<instance> LCo minor message

241-5701-500 4.1S1


acketough

isther

reat aot a

ckedthatP is

7018 1005



DetailsTheLogicalConnection (LCo) subcomponent of this service attempted to send packet through its data path to measure the round trip delay of the path. The paexperienced a problem somewhere along the data path and never made it thrthe path. After several attempts to resend the packet, theLCo subcomponent wasforced to bring the control path and data path down. The data path’s integrity considered compromised if a round trip delay packet cannot get through, and odata packets will also be affected.

The problem experienced by the path gather packet is most likely due to sevecongestion somewhere along the control path. It could also be due to the fact thhop along the data path is in mapped mode and using VP = 0, but this VP is npoint-to-point connection.

Probable Cause

Type

Remedial actionAfter the control path and data path go down, theLCocomponent will automaticallytry to reestablish the paths. If the problem recurs, the data path should be chefor congestion, hop by hop. If there is no congestion along the data path, ensurefor any hop along the data path that is in mapped mode and using VP = 0, the Va point-to-point connection.




a the

nd

ntrol

reat anot

ckedure

= 0,

7018 1006



DetailsTheLogical Connection (LCo) subcomponent of this service attempted to send packet through its control path to gather the names of nodes and trunks alongpath. The packet experienced a problem somewhere along the control path anever made it through the path. After several attempts to resend the packet, theLCosubcomponent was forced to bring the control path and data path down. The copath’s integrity is considered compromised if a path gather packet cannot getthrough, as other control packets such as path clear will also be affected.

The problem experienced by the path gather packet is most likely due to sevecongestion somewhere along the control path. It could also be due to the fact thhop along the control path is in mapped mode and using VP = 0, but this VP isa point-to-point connection.

Probable Cause

Type

Remedial actionAfter the control path and data path go down, theLCocomponent will automaticallytry to reestablish the paths. If the problem recurs, the control path should be chefor congestion, hop by hop. If there is no congestion along the control path, ensthat for any hop along the control path that is in mapped mode and using VP the VP is a point-to-point connection.


241-5701-500 4.1S1


ted

.

7018 2001

Legend<component_name> = Trk or component of system which is using the path orienrouting virtual circuit.


<LCOorPa> = LCO or Pa

DetailsPORS detects an incorrect LRC value in one of its received control messages

Probable Cause

Type


Component Severity Status<component_name>/<instance> <LCOorPa>warning message



7018 2002

Legend<component_name> = Btds, Htds or Vs.


<LCOorPa> = LCO or Pa

DetailsThis happens when the attribute localAddress under subcomponent Plc isprovisioned, but porsApi is deleted from the Sw Lpt’s featureList.

Probable Cause

Type

Remedial actionAdd porsApi to the feature list of the appropriate Sw Lpt.

Nortel Networks

Component Severity Status<component_name>/<instance> <LCOorPa>Critical message

241-5701-500 4.1S1


t

at.

7019 0001

Legend<component name> = A Vs, Btds or Htds component.


DetailsTheLogicalConnection (LCo) subcomponent of the service is not up so that theservice can not transmit or receive data across the network. The service is noproviding service to the subscriber.

Probable Cause

Type

Remedial actionLook at the LogicalConnection (LCo) subcomponent for clues as to why theconnection is not up. Verify that thePermanent Logical Connection (PLC)component’s attributes are correct and compatible with the far end. Ensure thsufficient bandwidth is available in the network for the connection to establish

Component Severity Status<component_name>/<instance> major/cleared set/clear



rd.

7019 0002

Legend< instance> = 0-15

DetailsA feature is provisioned which is not supported by the vintage of this voice ca

Probable Cause

Type

Remedial actionContact your Nortel Networks technical support group.

Component Severity Status<Shelf_Card>/<instance> critical message

241-5701-500 4.1S1


diaIPfor

toand/al

7020 0001

Legend< Vr_name> = name of the VirtualRouter component

<Pp_name> = name of the ProtocolPort component

DetailsThis alarm indicates that IP Accounting data could not be retrieved from the mespecified in the alarm text within the expected time interval. This implies that Accounting records will not be generated for this protocolPort (Pp) componentthe current collection period.

Probable CauseThere may be message block congestion or heap exhaustion on:

• the CP

• LPs forwarding traffic for this Pp

Typeprocessing

Remedial actionFrequent occurrences of this condition indicate that re-engineering is requiredbalance the memory block and/or heap consumption of applications on the CPor LPs forwarding traffic for this Pp. Contact your local Nortel Networks technicsupport group for assistance, if necessary.

Component Severity StatusVr/<Vr_name> Pp/<Pp_name> warning message



rethe

re,

7021 0000

Legend<string> = Instance string identifier of the VirtualRouter component

DetailsLp is out of memory. Ip service is restarted with all the provisioned data. If momemory is not allocated for Ip, the problem may repeat. The comment data andoperator data contains the virtual router identifier that owns this IP service.

Probable Cause

Type

Remedial actionIP has restarted because of lack of memory. To avoid similar problems in futuallocate more memory for IP from Vr.

Component Severity StatusVr/<string> Ip warning message

241-5701-500 4.1S1


n

/

ize

ms

7021 0006


<instance> = an Lp number

DetailsThe IP cache table of theVr component has failed to allocate/deallocate memory olp/<instance>.

This alarm is set when the IP cache table of theVr component has failed to allocatedeallocate memory inlp/<instance>. The cache table size is specified by thecacheTableSize attribute.

A clear is issued after the cache table size is changed to be as same as the sspecified in thecacheTableSize attribute.

Probable Cause

Type

Remedial actionIP service is not affected if the OSI usage state is not idle. To avoid similar problein future, allocate more memory for IP. A retry timer is created to allocate thememory for every minute.

Component Severity StatusVr/<string> Ip cache/<instance> major set/clear



n onnerly

ver isute

7021 100C


<address> = IP address of the BGP peer

DetailsThis alarm is generated when a BGP speaker is configured to support ipv4Vpthe peer, but determines that its peer supports common capabilities other thaipv4Vpn. It indicates that auto discovery information will not be exchanged ovthis backbone peer session although the session is established with commonsupported capabilities.


TypeProcessing

Remedial actionIf exchange of IP VPN auto discovery information is desired across VPN sites othis backbone peer session, make sure the BGP software on the remote peerupgraded to support Multiprotocol Extensions Capability. Moreover, the attribaddressFamily under theDescriptor component of the remote Peer must beprovisioned to include ipv4Vpn.

Component Severity StatusVr/<string> Ip Bgp Peer/<address> warning message

241-5701-500 4.1S1


ls thepointther

r

theyrfaces.

if,colon

7021 100D


DetailsThis alarm is generated when a BGP speaker has discovered a private tunneendpoint IP address, through auto-discovery, which is not on the same subnet alocal tunnel endpoint or it happens to be the same as another private tunnel endthat is already discovered. As a result, the invalid private tunnel address, togewith its corresponding public tunnel address, will not be populated to both theMultipointStaticEndPoint and ARP. Also, no corresponding dynamic BGP peewill be created.


TypeProcessing

Remedial actionCheck the local and remote interface of the tunnel protocol ports and ensure are on the same subnet and no duplicate IP addresses are assigned to the inte

Note: Auto-discovery will rediscover remote customer information if, and onlythe duplicate address/netmask is fixed on the local interface of the tunnel protoport (i.e. linked to the VCG that generated the alarm). If the problem is resolveda remote interface, a lock/unlock of the local customerVr Ip Tunnelcomponent isrequired to restart auto-discovery.

Component Severity StatusVr/<string> Ip Bgp warning message



r hasr

the.

not

7021 100E



DetailsThis alarm is generated when a BGP speaker on a shared domain virtual routedetected that the same VPN ID is being used by multiple associated customevirtual routers. As a result, only one of the customer virtual routers that isprovisioned with this VPN ID participates in auto-discovery.


TypeProcessing

Remedial actionAll customer virtual routers that participate in IP VPN auto-discovery and usesame shared domain virtual router have to have unique VPN IDs provisionedProvision unique VPN IDs for those that are duplicates.

Note: The VPN ID change should be done on the customer Vr that is currentlyparticipating in auto-discovery.


241-5701-500 4.1S1


oseue

a has

ed

,

sas all

7021 1000


DetailsAn OSPF packet has been received on a non-virtual interface from a router whconfiguration parameters conflict with this router’s configuration parameters. Dto this, adjacency cannot be formed. The comment data and the operator datrelevant information to resolve the error. The alarm provides the followinginformation:

ospfRouterId - the originator of the alarm

ospfIfIpAddress- the IP Address of the interface on which the packet was receiv

ospfAddressLessIf- the IfIndex of the interface if it is an addressless interface

ospfConfigErrorType- type of error. Could be one of the following: badVersion(1)areaMisMatch(2), unknownNbmaNbr(3), unknownVirtualNbr(4),authTypeMismatch(5), authFailure(6), netMaskMismatch(7),helloIntervalMismatch(8), deadIntervalMismatch(9), optionMisMatch(10)

ospfPacketType - Type of OSPF Packet


TypeProcessing

Remedial actionCheck the configuration of this router and the router from which the packet wareceived and solve any mismatch. The comment data and the operator data hthe necessary information to correct this problem.

Component Severity StatusVr/<string> Ip Ospf warning message



uea has

,

sas all

7021 1001


DetailsAn OSPF packet has been received on a virtual interface from a router whoseconfiguration parameters conflict with this router’s configuration parameters. Dto this, adjacency cannot be formed. The comment data and the operator datrelevant information to resolve the error. The alarm provides the followinginformation:

ospfRouterId - the originator of the Alarm

ospfVirtIfAreaId - the area to which this virtual interface belongs to

ospfVirtIfNeighbor - the IP address of the neighbor who generated this packet

ospfConfigErrorType- type of error. Could be one of the following: badVersion(1)areaMisMatch(2), unknownNbmaNbr(3), unknownVirtualNbr(4),authTypeMismatch(5), authFailure(6), netMaskMismatch(7),helloIntervalMismatch(8), deadIntervalMismatch(9), optionMisMatch(10)

ospfPacketType - type of OSPF Packet


TypeProcessing

Remedial actionCheck the configuration of this router and the router from which the packet wareceived and solve any mismatch. The comment data and the operator data hthe necessary information to correct this problem.


241-5701-500 4.1S1


oseionvant

ed.

d

d the

7021 1002


DetailsAn OSPF packet has been received on a non-virtual interface from a router whauthentication key or authentication type conflict with this router’s authenticatkey or authentication type. The comment data and the operator data has releinformation to resolve the error. The information provided are:


ospfIfIpAddress- the IP address of the interface on which the packet was receiv

ospfAddressLessIf - the ifIndex of the interface if it is an addressless interface.

ospfConfigErrorType- type of error could be one of the following: authFailure anauthTypeMismatch.


Probable CauseUnexpected information

TypeSecurity

Remedial actionCheck if the source is an authenticated user of the net. The comment data anoperator data has relevant information to resolve the error.




ionvant

d

d the

7021 1003


DetailsAn OSPF packet has been received on a virtual interface from a router whoseauthentication key or authentication type conflict with this router’s authenticatkey or authentication type. The comment data and the operator data has releinformation to resolve the error. The information provided are:


ospfVirtIfAreaId - the area to which this virtual interface belongs to

ospfVirtIfNeighbor- the IP address of the neighbor who generated this packet

ospfConfigErrorType- type of error. Could be one of the following: authFailure anauthTypeMismatch.


Probable CauseUnexpected information

TypeSecurity

Remedial actionCheck if the source is an authenticated user of the net. The comment data anoperator data has relevant information to resolve the error.


241-5701-500 4.1S1


ms tillntlarm

d.

ed

lded

7021 1004


DetailsNumber of LSAs in the router’s link-state database has exceeded the maximunumber of external link-state entries that can be stored. Cannot add more LSA’LSDB limit is increased. Till then all the new LSAs are discarded. The commedata and the operator data has relevant information to resolve the error. The aprovides the following information:

VrId - the virtual router to which the OSPF belongs


ospfExtLsdbLimit - the current value of the maximum number of entries allowe

Note that theospfExtLsdbLimitattribute is of criticality component level. Changingthis attribute will restart OSPF with the provisioned values. This alarm is clearwhen a larger value is assigned to theospfExtLsdbLimit attribute.

Probable CauseStorage Capacity Problem

TypeProcessing

Remedial actionSet theextLsdbLimitattribute of the component given in the component name fieto a larger value. Till then all the new LSA’s will be discarded. This alarm is clearwhen a larger value is assigned to theospfExtLsdbLimitattribute.

Component Severity StatusVr/<string> Ip Ospf minor set/clear



nt ofatoring

d.

ld

7021 1005


DetailsNumber of LSAs in the router’s link-state database has exceeded ninety perceexternal link-state entries that can be stored. The comment data and the operdata has relevant information to resolve the error. The alarm provides the followinformation:


ospfExtLsdbLimit - the current value of the maximum number of entries allowe

Note that theospfExtLsdbLimitattribute is of criticality component level. Changingthis attribute will restart OSPF with the provisioned values.


TypeProcessing

Remedial actionSet theextLsdbLimitattribute of the component given in the component name fieto a larger value.


241-5701-500 4.1S1


a. Ifataice.

ure,

7021 1006


DetailsOSPF is out of memory. OSPF service is restarted with all the provisioned datmore memory is not allocated for IP, the problem may repeat. The comment dand the operator data contains the virtual router identifier that owns this IP serv


TypeProcessing

Remedial actionOSPF has restarted because of lack of memory. To avoid similar problems in futallocate more memory for IP from Vr.




on

but

by

7021 1007


DetailsWhen the status isset, BGP has failed to establish a transport protocol listen portwell known TCP port 179. Either Vr or TCP may be out of memory.

BGP will still be able to initiate transport connections to configured BGP peers,will not be able to accept transport connections from configured BGP peers.

The router identification number of the local BGP application is included in thealarm text.

When the status isclear, BGP has successfully established a transport protocollisten port on well known TCP port 179.

Probable Cause

Type

Remedial actionWhen the status isset, BGP will attempt to establish the transport protocol listenport continually (every 30 seconds). If the status does not change toclearover time,memory may need to be made free through provisioning changes (either byallocating more memory for Vr or by reducing the number of services being runthis or other instances of Vr). Disabling BGP will also change the status toclear.


Component Severity StatusVr/<string> Ip Bgp minor set/clear

241-5701-500 4.1S1


to

s of

erlyling

7021 1008



DetailsWhen the status isset, BGP has failed to initiate a transport protocol connectiona configured BGP peer.

The router identification number of the local BGP application and the IP addresthe peer to which BGP cannot connect is included in the alarm text.

When the status isclear, BGP has successfully established a transport protocolconnection to a configured BGP peer.

Probable Cause

Type

Remedial actionWhen the status isset, BGP will attempt to establish the transport protocolconnection continually (every 120 seconds). If the status does not change toclearover time, ensure that the BGP peer identified in the alarm is provisioned propand that the remote BGP application is enabled and configured properly. Disaba BGP peer will also change the status toclear.


Component Severity StatusVr/<string> Ip Bgp Peer/<address> minor set/clear



s ofxt.ge

error

may

7021 1009



DetailsBGP has sent a NOTIFICATION message to a BGP peer. This BGP peer istransitioning to theidle state. To display the state of a BGP peer display theconnectionState attribute of thePeer sub-component.

The router identification number of the local BGP application and the IP addresthe peer to which BGP is sending the NOTIFICATION is included in the alarm teAlso, the error code and error subcode included in the NOTIFICATION messaare displayed.

Probable Cause

Type

Remedial actionThe BGP peering session has reset due to some error or event (indicated by thecode and error subcode of the NOTIFICATION message). The BGP peeringsession will attempt to re-establish every 120 seconds. Operator intervention be required.


241-5701-500 4.1S1


r is

s ofhe

error

may

7021 100A



DetailsBGP has received a NOTIFICATION message from a BGP peer. This BGP peetransitioning to theidle state. To display the state of a BGP peer display theconnectionState attribute of thePeer sub-component.

The router identification number of the local BGP application and the IP addresthe peer which has sent the NOTIFICATION is included in the alarm text. Also, terror code and error subcode included in the NOTIFICATION message aredisplayed.

Probable Cause

Type

Remedial actionThe BGP peering session has reset due to some error or event (indicated by thecode and error subcode of the NOTIFICATION message). The BGP peeringsession will attempt to re-establish every 120 seconds. Operator intervention be required.




ionediateable

ed.

the

on.

7021 100B


DetailsTwo OSPF routers located in the same area have the same IP address provisfor their OSPF interfaces. The provisioned interfaces can be up or down. Immedaction should be taken to fix the situation as some OSPF routes will not be reachand extra traffic generated.

The information provided is as follows:

Duplicate IP Address - The duplicate IP address to be fixed.

Found on RouterId - The first router having the duplicate IP address.

Found on RouterId - The second router having the duplicate IP address.

Note that this alarm will be generated every few minutes until the problem is fix


TypeProcessing

Remedial actionUse the RouterId values displayed in the alarm to identify the routers that havesame provisioned IP address. To display therouterId value of an OSPF router,display the “routerId” attribute under the Ospf sub-component. Change theprovisioned IP address on one of the routers to eliminate IP address duplicati


241-5701-500 4.1S1


cantate.

rm

het this

7021 1100


DetailsA change occurred in the state of the OSPF non-virtual neighbor. This changeeither be due to a neighbor state regressing or progressing to the Full terminal s

In the case of the broadcast or non-broadcast multi-access networks, this alashould be generated by the designated router. The information provided is:

ospfRouterId - the originator of the alarm.

ospfNbrIpAddr - the IP address of the neighbor's interface.

ospfNbrAddressLessIndex - the IfIndex of the interface.

ospfNbrRtrId - the router id of the neighbor.

ospfNbrState - the new state of the neighbor.


TypeCommunications

Remedial actionVerify the running status of the router corresponding to this OSPF neighbor. Tcomment data and the operator data has all the necessary information to correcproblem.

Component Severity StatusOSPF <string> warning message



orethe

re,

7021 2000


DetailsRIP is out of memory. RIP service is restarted with all the provisioned data. If mmemory is not allocated for IP, the problem may repeat. The comment data andoperator data contains the virtual router identifier that owns this IP service.

Probable Cause

Type

Remedial actionRIP has restarted because of lack of memory. To avoid similar problems in futuallocate more memory for IP from Vr.

Component Severity StatusVr/<string> Ip Rip warning message

241-5701-500 4.1S1


rce

7021 2500


<num> = 0 - 1

DetailsDuplicate Tunnel MultipointStaticEndPoint source IP addresses have beenprovisioned.

Probable Cause

Type

Remedial actionReprovision the Tunnel MultipointStaticEndPoints so that they have unique souIP addresses.

Component Severity StatusVr/<string> Ip Tunnel Msep/<num> warning message



ad

7021 2501


<num> = 0 - 1, numeric Msep instance

DetailsThis alarm is generated when an IP TunnelMultipointStaticEndPoint attemptsdiscovered Tunnel destination IP address (DA) that is equal to the provisioneMultipointStaticEndPoint source IP address (SA).


TypeProcessing

Remedial actionVerify that all IP Tunnel MultipointStaticEndPoints within the same VPN haveunique source IP addresses.

Component Severity StatusVr/<string> Ip Tunnel Msep/<num> warning message

241-5701-500 4.1S1


ains.

were

e

7021 2503

LegendN/A

DetailsThis alarm indicates that an IP tunnel endpoint could not be fully initialized inhardware due to hardware resource unavailability. The IP tunnel endpoint remin software, resulting in a performance degradation restricted to this endpoint

Probable CauseHardware sources required for the setup of the IP tunnel in hardware on the FPexhausted.

TypequalityOfService

Remedial actionFrequent occurrences of this condition indicate that the number of IP tunnelendpoints requested to be setup in hardware on this FP exceeds the hardwarresources available on this FP. Contact your local Nortel Networks technicalsupport group for assistance if necessary.

Component Severity Statuswarning message



Ifataice.

ure,

7021 3000


DetailsEGP is out of memory. EGP service is restarted with all the provisioned data.more memory is not allocated for IP, the problem may repeat. The comment dand the operator data contains the virtual router identifier that owns this IP serv

Probable Cause

Type

Remedial actionEGP has restarted because of lack of memory. To avoid similar problems in futallocate more memory for IP from Vr.

Component Severity StatusVr/<string> Ip Egp warning message

241-5701-500 4.1S1


ta.ataice.

7021 4000


DetailsIP Rtm is out of memory. IP Rtm service is restarted with all the provisioned daIf more memory is not allocated for Ip, the problem may repeat. The comment dand the operator data contains the virtual router identifier that owns this IP serv

Probable Cause

Type

Remedial actionIp Rtm has restarted because of lack of memory. To avoid similar problems infuture, allocate more memory for IP from Vr.

Component Severity StatusVr/<string> Ip warning message



mit.

,

7022 0000

Legend<string> = Instance string identifier of the VirtualRouter component.

DetailsA Bridge component’s attempt to allocate working memory has failed.

Memory allocation failed. Reason: Exceeded Memory Manager provisioned li

Probable Cause

Type

Remedial actionIf sufficient resources remain, allocate additional memory for Bridge use.

If not, re-evaluate bridge network design. (Maximum number of allowed hostsnumber of spanning tree’s, etc.)

Component Severity StatusVr/<string> Br critical message

241-5701-500 4.1S1


notred

the

7023 0001


DetailsThe routing protocol provisioned for the routers at both the ends of the link domatch. Valid routing options supported on a Wan link for release 2.0 are numbeand unnumbered rip protocols.

Probable Cause

Type

Remedial actionReprovision one or both the routers for running the same routing protocol on link.

Component Severity StatusVr/<string> Ipx minor message



senter

7023 0002


DetailsIpxWan Timer Request Packet received after an Information Request packet isor after IpxWan negotiations are complete. This indicates that the IpxWan pewishes to restart negotiations.

Probable Cause

Type

Remedial actionInform the peer router’s service representative of the error.


241-5701-500 4.1S1


g

1)

7023 0003


Details Invalid IpxWan negotiation packet received from the peer. One of the followinscenarios causes this alarm.

1) An IpxWan Timer Response packet received from the peer a) before a Timer Request packet is received (state 0; event 1) b) after a Timer response is sent to the peer (state 1; event 1) c) after an Information Request Packet is sent to the peer (state 4; event or d) after IpxWan negotiations are complete. (state 5, event 1)

2) An Information Request packet is received a) before a Timer Request packet is received (state 0; event 2) b) after a Timer Request packet is sent out (state 1; event 2) c) after an Information Request packet is sent out (state 4, event 2) or d) after IpxWan negotiations are complete. (state 5; event 2)

3) An Information Response Packet is received a) before a Timer Request packet is received (state 0; event 3) b) before a Timer Request packet is sent out (state 2; event 3) c) before a Timer Response packet is sent out (state 3; event 3) or d) before a Timer Request packet is received (state 4; event 3).

Probable Cause

Type





s anlink

7023 0004


DetailsAlthough IpxWan negotiations determine that the peer router is a slave; it sendInformation request packet to us. The peer router thus considers itself to be themaster.

Probable Cause

Type



241-5701-500 4.1S1


an

7023 0005


DetailsInternal Network Number for both the IpxWan peers are the same. Thus IpxWcannot determine the master or the slave using the internal network number.

Probable Cause

Type

Remedial actionReprovision the routers so that their internal network numbers are different.

Component Severity StatusVr/<string> Ipx major message



ice.

tive

7023 0006


DetailsWhen the status isset, the component has been administratively disabled.

The Administratively disabled component is no longer permitted to provide servAs a result, dependent components may be operationally disabled as well.

When the status isclear the component is administratively enabled.


Probable Cause

Type

Remedial actionWhen the status isset, set thesnmpAdminState attribute to up to attempt to enablethe component.


Component Severity StatusVr/<string> Ipx minor set/clear

241-5701-500 4.1S1


tive

7023 0007


DetailsWhen the status isset, the component has been locked.

The locked component is no longer permitted to provide service. As a result,dependent components may be operationally disabled as well.



Probable Cause

Type

Remedial actionWhen the status isset, use the unlock verb to attempt to unlock the component.When the status isclear, no remedial action is required.

Component Severity StatusVr/<string> Ipx critical set/clear



ent.

7023 0008


DetailsAn Ipx component’s attempt to allocate memory has failed. Reason: Exceeded Memory Manager provisioned limit.

Probable Cause

Type

Remedial actionIf sufficient resources remain, allocate additional memory for the Ipx ComponIf not, re-evaluate the ipx network design.

Component Severity StatusVr/<string> Ipx major message

241-5701-500 4.1S1


ice.

tive

7023 0009

Legend<string1> = Instance string identifier of the VirtualRouter component<string2> = Instance string identifier of the Protocol Port component.<encap> = Encapsulation type for the Ipx Port component.

DetailsWhen the status isset, the component has been administratively disabled.

The Administratively disabled component is no longer permitted to provide serv

When the status isclear the component is administratively enabled.


Probable Cause

Type

Remedial actionWhen the status isset, set thesnmpAdminState to up to attempt to enable thecomponent.


Component Severity StatusVr/<string1> Pp/<string2> IpxPort/<encap> minor set/clear



tive

7023 0010

Legend<string1> = Instance string identifier of the VirtualRouter component<string2> = Instance string identifier of the Protocol Port component.<encap> = Encapsulation type for the Ipx Port component.

DetailsWhen the status isset, the component has been locked.

The locked component is no longer permitted to provide service.



Probable Cause

Type

Remedial actionWhen the status isset, use the unlock verb to attempt to unlock thecomponent.When the status isclear, no remedial action is required.

Component Severity StatusVr/<string1> Pp/<string2> IpxPort/<encap> critical set/clear

241-5701-500 4.1S1


oflt.

rt,

7026 1000


<type> = Enet and Fi

<num2> = 0 - 5

DetailsWhen the status isset, diagnostics have detected a fault with the hardwareassociated with this port. The comment text of the alarm will indicate the naturethe fault. The port will remain out of service until action is taken to correct the fauDiagnostics can be re-executed by locking and unlocking the component.

A clear will be issued when diagnostics have executed successfully.


TypeEquipment

Remedial actionWhen the status isset, discontinue the use of the port. Provision and alternate poactivate the standby card, or replace the card if possible.

When the status isclear, no remedial action is necessary.




on of

ntil and

7026 1001



<num2> = 0 - 5

DetailsWhen the status isset, diagnostics have detected a fault with the hardware commto all ports on this card. The comment text of the alarm will indicate the naturethe fault. This port (and any others on the same Lp) will remain out of service uaction is taken to correct the fault. Diagnostics can be re-executed by lockingunlocking the component.



TypeEquipment

Remedial actionWhen the status isset, discontinue the use of all ports on this Lp. Activate thestandby card, or replace the card if possible.



241-5701-500 4.1S1


hereiceing

the

ing,

7026 1002



<num2> = 0 - 5

DetailsWhen the status isset, diagnostics have detected an error in the hardware orsoftware configuration of this card. The comment text of the alarm will indicate tnature of the fault. This can include a missing FPGA file, or a missing hardwacomponent. The port (and any others on the same Lp) will remain out of servuntil action is taken to correct the fault. Diagnostics can be re-executed by lockand unlocking the component.



TypeEquipment

Remedial actionWhen the status isset, discontinue the use of all ports on this Lp.

If the alarm comment text indicates that a required file is missing, ensure thatcorrect revision of the file is present in the correct directory on the CP disk.

If the alarm comment text indicates that a required hardware component is missactivate the standby card, or replace the card if possible.





thee

7026 2000



<num2> = 0 - 5

DetailsThis alarm is generated if a fundamental internal operation fails during initialprovisioning of the component. The comment text of the alarm should indicatenature of the failed operation. The alarm may be preceded by related softwaralarms.

Probable Cause

Type



241-5701-500 4.1S1


thee

7026 2002



<num2> = 0 - 5

DetailsThis alarm is generated if a fundamental internal operation fails during initialprovisioning of the component. The comment text of the alarm should indicatenature of the failed operation. The alarm may be preceded by related softwaralarms.


TypeProcessing


Component Severity StatusLp/<num1> <type>/<num2> critical message



, or

e

.

7026 2003



<num2> = 0 - 5

DetailsWhen the status isset, an attempt to put this component into service has failedbecause the LanTest subcomponent is in a manufacturing, design verificationproduct integrity test mode.

This mode can only be entered if all ports on the FP are out of service, and thLanTest subcomponent associated with one of the ports is placed in theManufacturing/DVT/PI test mode. This mode is not intended for end-user use

When the status isclear, the component may be placed into service.

Probable CauseProcedural error

TypeOperator

Remedial actionWhen the status isset,reset the Lp associated with the component.



241-5701-500 4.1S1


iluree

larm

7026 2004



<num2> = 0 - 5

DetailsThis alarm is generated during initial provisioning of the component if a MACaddress is not available for the component. This can be caused by a hardware fathat interferes with the distribution of MAC addresses to the Lp. It could also bcaused if another component is using the MAC address designated for thiscomponent. If this is the case, this alarm should be preceded by a software aindicating that a requested MAC address ID is already in use.


TypeProcessing


Component Severity StatusLp/<num1> <type>/<num2> critical message



beate ory a

7026 3000


<num2> = 0 - 5

DetailsWhen the status isset, the Ethernet component has detected the absence of heartpulses on the twisted pair medium. The port is out of service and cannot receivtransmit packets until this condition is cleared. This condition can be caused bbad connection to the ethernet cable, or a bad ethernet cable.

A clear will be issued when heartbeat pulses are detected on the twisted pairmedium.

Probable CauseCableTamper,IOdevice error

TypeCommunications, Equipment

Remedial actionWhen the status isset, check the connection between the ethernet port and theethernet cable. Also check for a faulty cable.


Component Severity StatusLp/<num1> Enet/<num2> critical/cleared set/clear

241-5701-500 4.1S1


ile inilure.

rmber

RCthe

y arror

7026 3001


<num2> = 0 - 5

DetailsWhen the status isset, the Ethernet component has detected an LRC error in apacket being transmitted. This indicates that the packet has been corrupted whthe data path and discarded. This could be caused by a hardware or software fa

Since this error could potentially occur in many frames, the rate at which the alais generated may be throttled to avoid flooding the system with alarms. The numof packets discarded because of LRC errors is included in the count of outputpackets discarded. The port is not taken out of service due to this event but if Lerrors occur in sufficient number, performance will be adversely affected due tonumber of packets being discarded.


TypeProcessing

Remedial actionNormally there is no remedial action to be taken. The error could be caused bhardware failure, so running diagnostics may help isolate the problem. If the eoccurs frequently or for prolonged periods of time, contact your local NortelNetworks technical support group.

Component Severity StatusLp/<num1> Enet/<num2> indeterminate message



e ofekedle

7026 3002

Legend<num> = 0

DetailsThis alarm indicates that a CP switchover event is about to occur due to a failurone of the initial tests performed on the OamEthernet port. The initial tests arperformed on the OamEthernet port prior to it being put into an open and unlocstate. This alarm, and the subsequent switchover, depend on the provisionabattribute switchoverOnFailure being set to enabled.

Probable Cause

Type

Remedial actionCheck all cables leading from the affected CP Ethernet port for breaks or animproper connection. If the problem persists the affected CP card should beremoved and replaced with one whose Ethernet port is fully functional.

Component Severity StatusLp/0 OamEthernet/0 indeterminate message

241-5701-500 4.1S1


ort orstate

the

7026 3003

Legend<num> = 0

DetailsThis alarm indicates that a CP switchover event is about to occur due to a shbreak in the line or attached to the CP Ethernet port as detected by the steadylink test. The steady state link test is performed on the link connected to theOamEthernet port once every minute to determine its status. This alarm, andsubsequent switchover, depend on the provisionable attributeswitchoverOnFailurebeing set to enabled.

Probable CauseIOdevice error

TypeEquipment

Remedial actionCheck all cables leading from the affected CP Ethernet port for breaks or animproper connection.

Component Severity StatusLp/0 OamEthernet/0 indeterminate message



ased

7026 3004

Legend<num> = 0

DetailsThis alarm is generated when the OamEthernet port is provisioned on a PM1 bCP card.

Probable Cause

Type

Remedial actionDelete the provisioned OamEthernet port.

Component Severity StatusLp/0 OamEthernet/0 warning message

241-5701-500 4.1S1


beaty CP

le orhe

7026 3005


<num2> = 0 - 5

DetailsWhen the status isset, the Ethernet component has detected the absence of heartpulses on the twisted pair medium for the standby CP. The port in the standbis out of service and cannot receive or transmit packets until this condition iscleared. This condition can be caused by a bad connection to the Ethernet cabfaulty Ethernet cable. Aclear is issued when heartbeat pulses are detected on ttwisted pair medium for the standby CP.

Probable Cause

Type

Remedial actionWhen the status isset, check the connection between the Ethernet port and theEthernet cable. Also check for a faulty cable.


Component Severity StatusLp/<num1> Enet/<num2> critical/cleared set/clear



:

sary

lure

7026 3006

Legend<num> = 0

DetailsThis alarm indicates that a CP switchover attempt, due to an OamEnet failurecondition, has been suspended due to one of the following system conditions

File system is synchronizedCIT is loaded on the standbyStandby port is availableFPs run committed viewSoftware upgrade is not in progressStandby CP is available

A CP switchover with one of the above system conditions may cause unnecesservice outages.

Probable Cause

Type

Remedial actionClear the system condition so that the CP switchover due to the OamEnet faican proceed. Alternatively, you can perform a manual switchover,switchover -force lp/0, if the outages are acceptable.

Component Severity StatusLp/<0> OamEthernet/<0> indeterminate message

241-5701-500 4.1S1


sn’t

hen

7026 4002

Legend<instance> = decimal zero for current FDDI products

DetailsWhen issued a connection established by this station possesses the unusualcharacteristic of connecting two PHY’s of the same type. The connection doeviolate the connection policy on both stations involved so it was accepted.

Probable Cause

Type

Remedial actionNo remedial action necessary unless the condition occurred unintentionally, tchange cabling to correct the condition.

Component Severity StatusFddi/<instance> warning message



ans

esI

AI

7026 4004


DetailsWhen this alarm is issued, a connection policy violation has occurred. This methat the connection policy for this station doesn’t allow a connection to theneighbors PHY type. The connection will ultimately be established or rejecteddepending on the neighbors connection policy.

Probable Cause

Type

Remedial actionWhen this condition occurs verify cabling of this station to its neighbors compliwith standard FDDI convention. If the intention is to violate the standard FDDconvention for dual attach stations then modify the default connection policyattribute(s) to allow the desired connection, (e.i. if a PHY type A to PHY type connection is desired modify the provisioning attribute “acceptAA” in the FDDcomponent to enable this connection.)


241-5701-500 4.1S1


oneringillis

esI

AIng

7026 4005


DetailsWhen this alarm is issued, a connection policy violation has been signalled byof this stations neighbors. This means that the connection policy for the neighbostation doesn’t allow a connection to this station PHY type. The connection wultimately be established or rejected depending on the connection policy of thstation.

Probable Cause

Type

Remedial actionWhen this condition occurs verify cabling of this station to it’s neighbors compliwith standard FDDI convention. If the intention is to violate the standard FDDconvention for dual attach stations then modify the default connection policyattribute(s) to allow the desired connection, (e.i. if a PHY type A to PHY type connection is desired modify the provisioning attribute “acceptAA” in the FDDcomponent to enable this connection.). To eliminate the alarm the neighboristations connection policy must also be modified to accept the non-standardconnection.




d is

7026 4006


DetailsAlarm issued when PCM state machine for a PHY connection that was withhelrestarted.

Probable Cause

Type

Remedial actionNo remedial action required.


241-5701-500 4.1S1


to

hisin a

p.

7026 4007


DetailsIssued when the FDDI SMT’s PCM state machine for a particular PHY is unableestablish a connection to its neighboring station.

Probable Cause

Type

Remedial actionVerify that the PHY is question is properly connected to another active station. Talarm can be ignored if the users has intentionally elected to run the FDDI ringwrapped configuration, where only one PHY is being utilized

If difficulties persist contact your local Nortel Networks technical support grou




m isbeening.aveing

7026 4008


DetailsIssued after the FDDI MAC claim process, and beacon process fail. This alarused to signify the stuck beacon fault recovery trace process in the SMT has started. This alarm is issued when a fault condition has occurred on the FDDI rIf this station does not return to an active state it may mean that its neighbors hisolated this station as the source of the fault and removed it from the ring by gointo a wrapped configuration.

Probable Cause

Type



241-5701-500 4.1S1


nand

7026 4009


DetailsIssued when the FDDI SMT’s PCM state machine receives a trace propagationotification from its upstream neighbor. See alarm 7026-4008 for description scenario that would cause the occurrence of this alarm.

Probable Cause

Type





n.rtause

7026 400A


DetailsIssued as notification of successful completion of the FDDI SMT trace functioThis alarm will normally be followed by the alarm 7026-000B to indicate the staof the path test. See alarm 7026-4008 for description and scenario that would cthe occurrence of this alarm.

Probable Cause

Type



241-5701-500 4.1S1


ns

sn’t6-

7026 400B


DetailsNotification of the start of the PATH test. The path test is used to verify this statioH/W for any problems that might effect the operation of the FDDI ring.

Probable Cause

Type

Remedial actionContact your local Nortel Networks technical support group, if the station doereturn to an active operational state, or if this alarm is follow by the alarm 702400D.




lem

7026 400C


DetailsNotification that the path test passed on this station. It is an indication that a probon the FDDI ring is not being caused by this station See alarm 7026-400B foradditional information on the path test.

Probable Cause

Type



241-5701-500 4.1S1


em

7026 400D


DetailsNotification that the path test failed on this station. It is an indication that a problon the FDDI ring could be caused by this station. See alarm 7026-400B foradditional information on the path test.

Probable Cause

Type





ltthe

your

7026 400E


DetailsNotification that this station is invoking the FDDI SMT trace function. This fauisolation procedure is initiated if the claim and beacon process performed by MAC are unsuccessful.

Probable Cause

Type

Remedial actionIf the station returns to an active state no action is necessary, otherwise, consultlocal service representative for assistance.


241-5701-500 4.1S1


rorf the

7026 400F


DetailsNotification the link error rate has exceeded the warning threshold. Link errormonitoring detects FDDI symbol errors in a given sample period. A rise in the errate above the warning threshold may result in slightly degraded performance oFDDI ring.

Probable Cause

Type





ror’sn ofink

rtel

7026 4010


DetailsNotification the link error rate has exceeded the cutoff threshold. When the errate reaches this level it is sufficiently critical that the link between the two PHYexperiencing the errors is terminated to avoid severe performance degradatiothe entire ring due to a single link. The connection will be restored provided the lconfidence test is passed during the physical connection signalling process.

Probable Cause

Type

Remedial actionIf condition persists or the connection remains disabled contact your local NoNetworks technical support group.


241-5701-500 4.1S1


ato

DI

our

7026 4011


DetailsNotification the link confidence test has failed during the attempt to establish connection with the neighboring station. The link confidence test (LCT) is usedverify the connection quality prior to allowing a station to participate in the FDring.

Probable Cause

Type

Remedial actionVerify the cable quality and connection cleanliness. If problems persist contact ylocal Nortel Networks technical support group.




tact

7026 4012


DetailsA duplicate address condition has been detected on the FDDI ring.

Probable Cause

Type

Remedial actionThis condition is usually caused by local administration of MAC addresses. Conyour local Nortel Networks technical support group if problems persists.


241-5701-500 4.1S1


than and

nder

l

7026 4013


DetailsA condition occurred in the SMT process where more events where generatedcould be handled by the process. This alarm may be appear when connectingdisconnecting cables on an active FDDI station.

Probable Cause

Type

Remedial actionIf the FDDI station fails to achieve a connection delete the FDDI component athen reactivate the port. Under normal conditions the FDDI SMT should recovfrom this condition without intervention. Contact your local Nortel Networkstechnical support group if problems persist since there are numerous potentiacauses for this alarm including hardware, or signal integrity problems.




d by

bles

uedionsttic

7026 4014


DetailsWhen one of the PHY’s experiences an unusual condition that generates anexcessive number of interrupts it may be disable to prevent side effects causeto much processing time being consumed to service this condition. Severalconditions may cause this alarm, one would be disconnecting or connecting caon an active FDDI station.

Probable Cause

Type

Remedial actionIf the FDDI station fails to establish a connection after this alarm has been issdelete the FDDI component and then reactivate the port. Under normal conditthe FDDI SMT should recover from this condition without intervention. Contacyour local Nortel Networks technical support group if problems persist with a stacable configuration since there are numerous additional conditions that couldgenerate this alarm including hardware, or signal integrity problems.


241-5701-500 4.1S1


euch

mayive

uedionsttic

7026 4015


DetailsWhen the MAC experiences an unusual condition that generates an excessivnumber of interrupts it may be disabled to prevent side effects caused by to mprocessing time being consumed to service this condition. Several conditionscause this alarm, one would be disconnecting or connecting cables on an actFDDI station.

Probable Cause

Type

Remedial actionIf the FDDI station fails to establish a connection after this alarm has been issdelete the FDDI component and then reactivate the port. Under normal conditthe FDDI SMT should recover from this condition without intervention. Contacyour local Nortel Networks technical support group if problems persist with a stacable configuration since there are numerous additional conditions that couldgenerate this alarm including hardware, or signal integrity problems.




isratecal

7026 5000


<num2> = 0 - 5

DetailsIssued when an unrecoverable error is encountered by the TMS 380.

Probable CauseAdaptor error

TypeEquipment

Remedial actionIf this condition is not caused by a hardware failure the port will recover from thwithout intervention. There are numerous additional conditions that could genethis alarm including a hardware fault. Contact your local Nortel Networks technisupport group if problems persist with a static cable configuration.

Component Severity StatusLp/<num1> Tr/<num2> warning message

241-5701-500 4.1S1


d but

al

your

7026 5001


<num2> = 0 - 5

DetailsIssued when an LRC error detected by the token ring transmit hardware. Thisinterrupt implies that a frame has been corrupted some time after being receiveprior to transmission.


TypeProcessing

Remedial actionThis error will cause the port to be off line for a period of time, but under normconditions it will recover without intervention. There are numerous additionalconditions that could generate this alarm including a hardware fault. Contact local Nortel Networks technical support group if problems persist.




380.

ate

7026 5002


<num2> = 0 - 5

DetailsIssued when an invalid system request block (SRB) is encountered by the TMS


TypeEquipment

Remedial actionThis error is not expected under normal conditions. Contact your local NortelNetworks technical support group if problems persist since this error may indica hardware failure.


241-5701-500 4.1S1


he

ton

7026 5003


<num2> = 0 - 5

DetailsIssued when the station has received a removed request MAC frame fromconfiguration report server, that has resulted in this station withdrawing from tring.

Probable Causelan error

TypeCommunications

Remedial actionModify the configuration report server to allow this station on the ring. Attempinsertion of this station back into the ring by performing a lock/unlock sequencethe port.




ns

7026 5004


<num2> = 0 - 5

DetailsWhen the status isset, the token ring component has detected that no other statioare present on the ring.

A clear will be issued when another station is detected on the ring.

Probable Causelan error

TypeCommunications

Remedial actionWhen the status isset, verify the connection of other cables to the MAU, and theconnection of the MAU to other MAU’s. This alarm may also occur if all otherstations on the ring are powered down, or off-line for some other reason.


Component Severity StatusLp/<num1> Tr/<num2> critical/cleared set/clear

241-5701-500 4.1S1


tor

7026 5005


<num2> = 0 - 5

DetailsWhen the status isset, the token ring component has detected an open or shortcircuit in the cable between the adapter and the MAU.

A clear will be issued when the condition is no longer present.

Probable CauseCableTamper

TypeCommunications

Remedial actionWhen the status isset, verify the cable from the port to the MAU is securelyattached to the MAU. If condition persists verify that the cable and/or the connecon the MAU is not defective.





fhe

n

7026 5006


<num2> = 0 - 5

DetailsWhen the status isset, the token ring adapter has detected a loss or absence osignal, and was unable to transmit to itself while wrapped through its lobe at twiring concentrator.

A clear will be issued when the condition is no longer present.

Probable CauseCableTamper

TypeCommunications

Remedial actionWhen the status isset, verify the cable is securely connected to the card. If conditiopersists verify that the cable is not defective.



241-5701-500 4.1S1


This

rver

epting

ring

/port

7026 5007


<num2> = 0 - 5

DetailsIssued when an error has been detected during the open phase of initialization.alarm will be issued when conditions such as signal loss, beaconing, insertionfailure, active monitor ring purge time out, duplicate address, ring parameter senot responding, or remove ring station MAC frame received are present.

Probable Causelan error, Software error

TypeCommunications, Processing

Remedial actionThe remedial action for this alarm is dependent on the specifics provided in thalarm message. The duplicate address condition must be resolved before attemanother insertion into the ring. If a remove MAC frame is received it must beaddressed as described in alarm 7026 5003. A beacon MAC frame received duthe physical insertion phase could indicate a ring speed mismatch is present.Another attempt to insert the station into the ring can be attempted with a lockunlock sequence on the port. Contact your local Nortel Networks technical supgroup if problems persist since this error may indicate a hardware failure.




tus

ort.s

t

7026 5008


<num2> = 0 - 5

DetailsIssued when an interrupt request from the adapter fails to provide a stable stavalue within the allotted time window.


TypeEquipment

Remedial actionThe remedial action for this alarm to perform a lock/unlock sequence on the pThis will allow the diagnostics to verify the integrity of the hardware. If diagnosticare successful another attempt will be made to insert the station into the ring.Contact your local Nortel Networks technical support group if problems persissince this error may indicate a hardware failure.


241-5701-500 4.1S1


rate

tacthisthe

7026 5009


<num2> = 0 - 5

DetailsIssued when the interrupt rate from the TMS 380 is faster than the processingfor these interrupts. This message would indicate a ring that is unstable, orexperiencing a large number or exceptions.


TypeEquipment

Remedial actionNo remedial action is required, however it is recommended that a lock/unlocksequence on the port be performed to verify the integrity of the hardware. Conyour local Nortel Networks technical support group if problems persist since terror may indicate a hardware failure on this station or some other station on ring.




st.

tacthis

7026 500A


<num2> = 0 - 5

DetailsIssued when a failure occurs during the TMS 380 bring up diagnostics (BUD) teThe details of the specific problem are provided in the alarm message.

Probable CauseAdapter error

TypeEquipment

Remedial actionPerform a lock/unlock sequence on the port to verify a consistent failure. Conyour local Nortel Networks technical support group if problems persist since terror may indicate a hardware failure.


241-5701-500 4.1S1


or

tive

7031 2000


DetailsWhen the status isset, thePppcomponent has been taken out of service due to poline quality.

When the status isclear, good line quality has been restored and thePppcomponentwill resume providing service.

The OSI administrative state attribute in the alarm specifies the new administrastate for thePpp component.

Probable Cause

Type

Remedial actionWhen the status isset, the condition can be cleared by correcting the poor linequality condition, changing the quality threshold (Ppp/<instance>LinkQualityThreshold), or by disabling link quality monitoring (Ppp/<instance>LinkQualityMonitor configStatus).


Component Severity StatusPpp/<instance> critical/cleared set/clear



a

e

tive

ck

7031 2001


DetailsWhen the status isset, thePpp component has been taken out of service due to looped back line. This condition has been detected because thePppcomponent hasreceived the same Magic Number it sent out.

When the status isclear, the looped back line condition has been cleared and thPpp component will resume providing service.


Probable Cause

Type

Remedial actionWhen the status isset, the condition can be cleared by correcting the looped baline condition or by disabling Magic Number (Ppp/<instance> LinkconfigMagicNumber) and locking and unlockingPpp component.



241-5701-500 4.1S1


he

tive

his

7031 2002


DetailsWhen the status isset, thePppcomponent has been taken out of service due to tPpp Link Control Protocol (Lcp) leaving the Open state.

When the status isclear, Lcp has entered the Open state and thePppcomponent willresume providing service.

When the status isclear, Lcp has entered the Open state and thePppcomponent willresume providing service.


Probable Cause

Type

Remedial actionWhen the status isset, viewing ofPpp/<instance> and related component’soperational attributes will help to further isolate the actual cause of the failure. Tcondition has occurred for one or more of the following reasons: - Physical link connection is unavailable - Peer PPP connection has been terminated - PPP connection has been rejected - Link Continuity Monitor has detected loss of connection





a

the

7032 0001


DetailsWhen the status isset, theFrDte component has been taken out of service due toservice-affecting condition detected by LMI at the user-network interface.

When the status isclear, service has been restored.

The OSI state attributes in the alarm specifies the OSI states for theFrDtecomponent at the time of the alarm.

Probable Cause

Type

Remedial actionWhen the status isset, viewing of theFrDte/<instance> and relatedDlcicomponent operational attributes will help to further isolate the actual cause offailure. This condition has occurred for one or more of the following reasons: - The DCE is not responding to Status Enquiry polls. - The DTE/DCE are running different LMI procedures.


Component Severity StatusFrDte/<instance> critical/cleared set/clear

241-5701-500 4.1S1


e pollarmeingromlarm

ics

7035 0001

Legend<node name> = name of Passport node

DetailsThe Statistics Management System has detected that regular statistics updatfor one of the applications whose name is shown in the comment data of the alrecord was not successful after two consecutive attempts. The result of not bable to poll is that some of the statistics data is not collected properly on CP fLP’s. Upon LP failures, statistics data may be lost forever. The cause of the amay be message excessive congestion on the module.

Probable Cause

Type

Remedial actionNo action is required. The module will automatically attempt to poll same statistagain in 15 minutes. If the problem persists contact Nortel Networks support.

Component Severity StatusEM/<node name> warning message



ion

ed

icsrt.

7035 0002

Legend<node name> = name of Passport node

DetailsThe Statistics Management System has detected that more than one applicatregular statistics polls were not successful within last poll cycle. The result ofmultiple application poll failures is that the regular poll time duration had increasfrom fifteen minutes to some larger value. The cause of the alarm may becontinuous excessive message congestion on the module.

Probable Cause

Type

Remedial actionNo action is required. The module will automatically attempt to poll same statistagain in next poll cycle. If the problem persists contact Nortel Networks suppo

Component Severity StatusEM/<node name> warning message

241-5701-500 4.1S1


e

ation

TE,

E,

sult

byPN

fails.

eelays

e

7036 0005

Legendname - component name of the APPN router

DetailsAPPN Resources Manager memory shortage. The operator data describes thproblem in more detail.

0005 - Insufficient storage to start a transaction program instance and conversrequested by a received Attach (FMH5).

0008 - Insufficient storage to start a new conversation requested by ALLOCAMC_ALLOCATE or CMALLC.

0019 - Deactivating session because of insufficient storage.

0020 - Insufficient storage to initiate session activation requested by ALLOCATMC_ALLOCATE or CMALLC.

0028 - Insufficient storage to deactivate a limited resource session. This could rein a limited resource link being kept active while they are not required.

0048 - Insufficient storage to start the transaction program instance requestedTP_STARTED. If other instances of the same transaction program are active APqueues the request waiting for one of them to become free. Otherwise the verb

0049 - Insufficient storage to initiate automatic session activation. Fewer activsessions are available on the specified mode, which may cause application dor failures.

0050 - Insufficient storage to initiate session activation requested byACTIVATE_SESSION verb.

Probable Cause

Type

Remedial actionAttention: Local Admin

Investigate memory shortage. Re-engineer FP with less functionality to reducmemory usage.

Operator Data

Component Severity StatusAPPN/name minor message



DCL Problem Determination IndexLocal LU AliasPartner LU AliasMode NameSession IdentifierTransaction Program name {optional)

241-5701-500 4.1S1


hes

7036 0027


DetailsAPPN Resources Manager has failed to verify security on an LU-LU session.

Effect: The LU fails the session.

Probable Cause

Type


Check that the password defined for the specified local LU and partner LU matcthat defined at the partner LU.

Operator DataLocal LU

Partner LU

Mode name

Session ID




.

7036 0042


DetailsLU-LU verification protocol error. This may indicate an interoperability problem

The session is deactivated with the specified sense code.

Probable Cause

Type

Remedial actionContact support with details of the problem.

Operator DataSNA sense code

Local LU (Alias)

Partner LU (Alias)

Mode name

Session Identifier


241-5701-500 4.1S1


ee

7036 0047


DetailsAPPN Resources Manager was unable to activate a new session because thmaximum session limit specified for the session mode or the local LU would bexceeded.

Effect:ALLOCATE , MC_ALLOCATE , or CMALLC verbs either failor hang waiting for a session to become free.

Probable Cause

Type

Remedial actionThe mode session limit can be increased usingDEFINE_MODE parametermode_max_neg_sess_limit. The LU session limit can be increased usingDEFINE_LOCAL_LU .

These resources are not currently accessible through the CAS or PresideMultiservice Data Manager interfaces.


Partner LU

Mode name




lem

om a

nd

7036 0051


DetailsTransaction program (APPC) bracket protocol error. This may indicate a probin the partner LU. The sense codes are as follows:

2008 0000 - partner LU attempted to start bracket after sending BIS.

2003 0000 - partner LU attempted to start bracket after local LU hand BID forsession successfully, unexpected RTR request received.

2010 0000 - received negative response to BID with sense code 088B0000 frpartner LU who supports parallel sessions, or BIS protocol error.

The session is deactivated with the specified sense code reported to the far e

Probable Cause

Type

Remedial actionThis may indicate a configuration error at either end of the connection or anincorrectly implemented transaction program. Contact technical support.

Operator DataSense Code

Local LU (Alias)

Partner LU (Alias)

Mode name

Session identifier

Request code


241-5701-500 4.1S1


in

not

nd.

7036 0052


DetailsTransaction program (APPC) attach protocol error. This may indicate a problemthe partner LU. The sense codes are as follows:

080F6051 - Attach security protocol violation

1008 6011 - Logical unit of work (LUW) identifier format error, or LUW identifiernot specified when synchronization level is syncpt.

1008 6040 - synchronization level not supported by session, or already-verifiedaccepted from partner LU.

1008 6031 - APPC program initialization parameters (PIP) not allowed bytransaction program.

The session is deactivated with the specified sense code reported to the far e

Probable Cause

Type

Remedial actionThis may indicate a configuration error at either end of the connection or anincorrectly implemented transaction program. Contact technical support.


Local LU (Alias)

Partner LU (Alias)

Mode name

Session identifier

Attach request unit




s ann user

7036 0053


DetailsAttach conversation rejected because security information invalid. This indicateattempt to access a secure transaction program by an unknown user, or a knowwho has specified an incorrect password.

Effect: The LU fails the session.

Probable Cause

Type

Remedial actionUse the operator data to locate the attempted security violation.


Local LU

Partner LU

Mode name

Session ID

Transaction Program name

User identifier

supplied password


241-5701-500 4.1S1


note

tion

7036 0054


DetailsAn APPC transaction attach was rejected because the specified sync level issupported by the specified transaction program. This may be a mismatch in thcapabilities of the originating transaction program and the destination transacprogram, or it may simply be a configuration error.

Effect: the attach will be rejected.

Probable Cause

Type

Remedial actionCheck the sync level supported by the specified transaction program.


Local LU (Alias)

Partner LU (Alias)

Mode name

Session Identifier


Sync Level




gram

m

7036 0056


DetailsAn APPC transaction attach was rejected because the specified transaction prois permanently disabled. This should only occur if the operator has explicitlydisabled the transaction program by issuing a Lock on the Transaction Progracomponent.

Note: The Transaction Program component is not currently visible through theCAS/Preside Multiservice Data Manager interface.

Probable Cause

Type

Remedial actionIf the transaction program should not be disabled issue an Unlock on theTransaction Program component.


Local LU (Alias)

Partner LU (Alias)

Mode name

Session Identifier



241-5701-500 4.1S1


me

7036 0057


DetailsThe APPN node was unable to activate a new session because the mode naspecified was not recognized.

Probable Cause

Type

Remedial actionCheck the mode name.

Operator DataLocal LU (Alias)

Partner LU (Alias)

Mode name




otuser

7036 0058


DetailsAn APPC transaction attach was rejected because security information was nspecified. This indicates an attempt to access a secure TP without specifying aidentification or a password.

Effect: The attach will be rejected.

Probable Cause

Type

Remedial actionLocate the security mismatch.


Local LU (Alias)

Partner LU (Alias)

Mode name

Session Identifier



241-5701-500 4.1S1


ode

7036 0059


DetailsBIS protocol error. This may indicate a problem in the partner LU. The sense cis always set to 20100000.

Effect: The session is deactivated with the specified sense code.

Probable Cause

Type


Operator DataSense code

Local LU (Alias)

Partner LU (Alias)

Mode name

Session identifier

Reply




7036 0060


DetailsA type 3 XID containing an XID Negotiation Error (0x22) control vector wasreceived from a remote node.

Probable Cause

Type

Remedial actionUse the sense data contained in the alarm to determine the cause of the XIDnegotiation error.


XID containing the error control vector.


241-5701-500 4.1S1


S/

7036 0061


portname - component name of the logical Port

DetailsThe number of XID frames received during link activation exceeded the limitdefined for the port. This could indicate an XID protocol error by an attachedstation, or an excessively unreliable physical medium.

Effect: Link activation fails.

Probable Cause

Type

Remedial actionAttention: User/Local Admin/Remote Admin

Increase the XID frame exchange limit on the Port. If APPN is still unable toactivate the link station, trace the link station or port to isolate the problem.

Note: The XID frame exchange limit is not currently modifiable through the CAPreside Multiservice Data Manager interface.

Operator DataPort name

Link station name

Adjacent CP name

XID frame count

Port XID frame limit

Sense code

Component Severity StatusAPPN/name Port/portname minor message



that

7036 0062


portname - component name of the logical Port

DetailsThe number of XID frames received during non-activation exchange exceededdefined for the port. This could indicate an XID protocol error by an attachedstation, or an excessively unreliable physical medium.

Effect: Non-activation XID frame exchange fails and the link is deactivated.

Probable Cause

Type


Note: The XID frame exchange limit is not currently modifiable through the

CAS/Preside Multiservice Data Manager interface.

Operator DataLink station name

Adjacent CP name

non-activation XID frame count

Port non-activation XID frame limit


241-5701-500 4.1S1


an

an

ion.

rk

load

7036 0063


linkstationname - component name of the link station

DetailsAPPN Configuration Services was unable to perform some function due to amemory shortage. The operator data provides more details.

0063 Insufficient storage to activate a link. Activation fails.

0072 Insufficient storage to perform orderly link deactivation, performingimmediate deactivation instead.

0074 Insufficient storage to update ANR routing tables following deactivation ofHPR-capable link.

0075 Insufficient storage to update ANR routing tables following activation of HPR-capable link

0079 Insufficient storage to forward Alert generated by DLC.

0111 Insufficient storage to end intra-node sessions properly.

0114 Insufficient storage to generate link Alert.

0122 A DCL could not be started either because of insufficient resources, orbecause the specified DLC type is not supported.

0127 Insufficient storage to update topology database with link station informat

0128 Insufficient storage to update topology database with connection netwoinformation.

0129 Insufficient storage to enable intra-node sessions.

Probable Cause

Type

Remedial actionAttention: User/Local Admin

Investigate resource shortage. Re-engineer FP with less functionality or systemto reduce memory usage.

Component Severity StatusAPPN/name LS/linkstationname minor message



Operator DataDCL Problem Determination Index

other fields dependent upon DCL Problem Determination Index

241-5701-500 4.1S1


ENred

7036 0064



DetailsThis alarm is generated when an XID3 is received from an adjacent back-level Lnode (not carrying a network name control vector) but there is no link configuto that back-level LEN node. An implicit link cannot be activated because theadjacent node’s CP name is not known.

Effect: Inbound link activation fails.

Probable Cause

Type


Define a link station (using DEFINE_LS) with adj_cp_type set toNAP_BACK_LEVEL_LEN_NODE.


Port name

LS name




is,

7036 0065



DetailsThis alarm is generated when the link to host is not configured properly (that when it is configured as a link to a Type 2.1 node).


Probable Cause

Type


Define or redefine link station (using DEFINE_LS) with adj_cp_type set toNAP_HOST_XID3 or NAP_HOST_XID0.


Port name

LS name


241-5701-500 4.1S1


the

as no

se of

ed.

ID

ed or

ted.

ors in

nge

7036 0066



DetailsThis alarm is generated when there is an error in link activation, as described byoperator data. The sense codes have the following interpretation:

0801-0012 - an APPN connection cannot be established because the node havailable integers to represent a new TG.

0806-002C - the adjacent node has changed its network name during the couran XID exchange

0809-003A - a null XID was received when an activation XID3 was expected.

0809-003B - a null XID was received when a non-activation XID3 was expect

0809-003C - a prenegotiation XID was received when not expected.

0809-003D - a non-activation XID was received when a null XID or activation XIDwas expected.

0809-003E - an activation XID was received when a non-activation XID wasexpected.

0809-003F - adjacent node initiated a secondary-initiated non-activation XIDexchange on a link that does not support secondary-initiated non-activation Xexchanges.

0809-0040 - a mode-setting command was received and was either not expectinvalid for the receiving node

0809-0042 - a non-activation exchange initiation indicator not set when expec

0809-0045 - the adjacent node has stopped supporting exchange state indicatthe middle of an XID exchange.

0809-0046 - the adjacent node had previously indicated it did not support exchastate indicators, but has sent a XID with exchange state indicators set.

0809-0047 - received XID after receiving mode setting command.

0809-0048 - received unsolicited XID from NRM secondary link station.

0809-0049 - the adjacent node sent an XID error control vector (x’22’).




n

t set

trol

rk

k

e.

.

eive

than

s not

and

ents

0809-004E - a non-null XID was received from a secondary NRM link station whea null XID was expected.

0809-0055 - invalid VRN in TG descriptor CV of XID3.

086F-0000 - XID3 control vector length error.

088C-1000 - the adjacent node is a network node, but did not include a producidentifier control vector in the XID3.

088C-0EF1 - the adjacent node is type 4 or 5, but did not include a PU name convector.

088C-0EF4 - the adjacent node has no been inconsistent in including a netwoname control vector.

088C-4680 - an XID was received on an ATM port, but did not include a TGidentifier TG descriptor subfield.

0891-0004 - the network name control vector does not contain a valid networidentifier.

0891-0005 - the network name control vector does not contain a valid CP nam

0895-xxyy - XID3 control vector error (xx indicates key of first control vector inerror, yy indicates offset of error within control vector).

0896-0000 - control vector too long.

0896-0001 - network name control vector is too long.

1015-0001 - received XID3 is too short (less than 29 bytes).

1015-0002 - length of received XID3 does not match length indicated in XID3

1016-0000 - the adjacent node indicated an invalid BIND pacing setting.

1016-0001 - the maximum number of I-frames that the adjacent node can recbefore sending an acknowledgement is set to zero.

1016-0002 - adjacent node has been inconsistent in its setting of ACTPUsuppression indicator.

1016-0003 - the maximum BTU size the adjacent node can receive is set to less99 bytes.

1016-0004 - unexpected XID format.

1016-0005 - the adjacent end node supports receipt of BIND segments, but doesupport BIND segment generation.

1016-0006 - the adjacent end node does not support receipt of BIND segmentshas a maximum BTU size less than 265 bytes.

1016-0007 - the adjacent network node does not support receipt of BIND segmand has a maximum BTU size less than 521 bytes.

1016-0008 - adjacent node has been inconsistent in its setting of networking

241-5701-500 4.1S1


ot

ation

se

ent.

d

P

t

dary

CP-

tor

toran

did

capabilities.

1016-0009 - the adjacent network node supports CP-CP sessions but does nprovide CP services.

1016-000B - the adjacent node has selected zero as the TG number (which isinvalid).

1016-000C - the adjacent network node does not support BIND segment generand has a maximum BTU size less than 521 bytes.

1016-000D - the adjacent node does not support the SDLC command/responprofile (which is the only profile supported by APPN and LEN nodes).

1016-000E - product set identifier on XID3 has changed.

1016-0010 - the ABM support indicated in sent and received XID3s is inconsist

1016-0013 - the DLC type in sent and received XIDs are not in agreement.

1016-0014 - adjacent node changed role from non-negotiable to negotiable.

1016-0015 - the adjacent node supports BIND pacing as sender only.

1016-0017 - after two exchanges, randomized node IDs sent by this node anadjacent node are still identical.

1016-0019 - adjacent node has attempted to change its CP name when CP-Csessions supported on link station, or link station not quiesced.

1016-001A - the adjacent node is inconsistent in its support for parallel TGs.

1016-001B - the adjacent node provides or requests CP services but does nosupport CP-CP sessions.

1016-001C - the adjacent node indicated an LS role that was not primary, seconor negotiable.

1016-001E - the adjacent node did not send its CP name in XID3 but requestedCP sessions on this link.

1016-0020 - adjacent node is not type 2, 4 or 5.

1016-0022 - the adjacent node included an HPR Capabilities [X’61’] control vecin its XID3 but specified a maximum BTU size less than 768.

1016-0023 - the adjacent node included an HPR Capabilities [X’61’] control vecin its XID3 but specified an invalid ANR label length (i.e. less than 1 or greater th8).

1016-0026 - NCE field lengths in the HPR Control Flows [X’81’] subfield areinconsistent with the length of the HPR Capabilities [X’61’] control vector.

1016-0027 - the adjacent node indicated support for control flows over RTP, butnot include a HPR Control Flows [X’81’] subfield.

1016-0028 - adjacent node has specified an invalid error mode in its HPR



nly

LC

the

Capabilities CV.

1016-0034 - adjacent node indicated no support for LDLC, but the local node osupports LDLC.

1016-0044 - adjacent node indicated support for LDLC, but did not include an LSAP subfield in the HPR Capabilities CV.


Probable Cause

Type


Run a trace on the link station or port to obtain more diagnostic information onproblem. Contact support with details of the problem.


Port name

LS name

Adjacent CP name

Byte offset

Bit offset

XID frame

241-5701-500 4.1S1


thisady

ode

7036 0067



DetailsThis alarm is generated when there are no free TG numbers available betweennode and the specified adjacent node. This should only occur if there are alre236 parallel TGs between this node and the adjacent node.


Probable Cause

Type

Remedial actionReconfigure the network to reduce the number of parallel TGs between this nand the specified adjacent node.


Port Name

Linkstation Name

Adjacent CP Name




tly.

7036 0069



DetailsThere was an error in link activation, the link to a host is not configured correc


Probable Cause

Type

Remedial actionReconfigure the linkstation with the correct adjacent CP type.


Port Name

Linkstation Name


241-5701-500 4.1S1


does

7036 0071



DetailsThere was an attempt to activate more than one TG to an adjacent node thatnot support parallel TGs.


Probable Cause

Type

Remedial actionModify the configuration so that there is only one link station defined to thespecified adjacent node.


Port Name

Linkstation Name

Adjacent CP Name




7036 0082


portname - component name of the port

DetailsPort deactivation has failed.

Effect: Port may not restart successfully.

Probable Cause

Type

Remedial actionVerify that the virtual circuit is connected.

Operator DataDLC Name

Port Name

Component Severity StatusAPPN/name PORT/portname minor message

241-5701-500 4.1S1


). If and

7036 0084



DetailsA DLC has ended abnormally or there is an unrecoverable DLC failure.

Effect: All ports and link stations defined on the DLC are inoperative.

Probable Cause

Type

Remedial actionRestart the DLC and ports (using START_DLC and START_PORT commandsthe problem persists, run a trace on the DLC and contact support with the logtrace information.

Operator DataDLC Name

Component Severity StatusAPPN/name PORT/portname minor message



n

re

cluderchy,

7036 0088



DetailsAPPN Configuration Services was requested to activate a link for a ConnectioNetwork it received an ACTIVATE_ROUTE) but was unable to perform thisbecause the link-activation limit for the port had been reached.

Effect: The link is not activated and is not until other links serviced by the port adeactivated.

Developer note. When the alarms consolidated under 0065 are updated to inthe LS name, and when the CN component is added to the management hierathen this alarm will be consolidated with them.

Probable Cause

Type


Contact technical support.

Operator DataCN name

[Port name moved to component name]

Sense code 0850-0001

Component Severity StatusAPPN/name Port/name minor message

241-5701-500 4.1S1


n

7036 0089


DetailsAPPN Configuration Services was requested to activate a link for a ConnectioNetwork (it received an ACTIVATE_ROUTE) that was unknown to it.

Effect: The link is not activated, and this may indicate a serious internal error.

Probable Cause

Type


Investigate why SS sent ACTIVATE_ROUTE.

Operator DataVRN name

Sense code 0806-002B




for

7036 0090



DetailsAPPN Configuration Services was requested to activate an outbound link (itreceived a CONNECT_IN) but was unable to because the link activation limitthe port had been reached.

Effect: The link is not activated.

Probable Cause

Type


Contact technical support.

Operator DataPort name


241-5701-500 4.1S1


han

7036 0091



DetailsThe format 3 XID received from an adjacent node indicates different parameter tare expected.


Probable Cause

Type

Remedial actionCheck that the parameters defined for this linkstation are correct.


Port Name

Linkstation Name




ner

7036 0112


vrnname - name of the adjacent node

tgnum - TG number of this TG

DetailsAPPN Configuration Services was requested to activate a link for a ConnectioNetwork (it received an ACTIVATE_ROUTE) for a Transmission Group numbthat was unknown to it.

Effect: The link is not activated. APPN Configuration Services discards theACTIVATE_ROUTE but this may indicate an internal error.

Probable Cause

Type


Investigate why SS sent ACTIVATE_ROUTE.

Operator DataVRN name

Transmission Group number

Sense code 0806002B

Component Severity StatusAPPN/name LocTg/vrnname,tgnum minor message

241-5701-500 4.1S1


link

7036 0121



DetailsRequested APPN Control Point CP-CP sessions could not be established on asince the remote system did not support them.

Effect: CP-CP sessions are not established.

Probable Cause

Type

Remedial actionAttention: Remote Admin

Investigate configuration mismatch.

Operator DataLink Station name

Adjacent APPN Control Point name

Component Severity StatusAPPN/name Ls/name minor message



7036 0133


DetailsConversation ended.

Probable Cause

Type

Remedial actionAttention: Local/Remote Admin

Investigate cause of protocol error.


APPN Transaction Program name

APPN Transaction Program ID

Conversation ID

Partner LU name

Local LU name

Mode name

Session ID


241-5701-500 4.1S1


ession

7036 0134


DetailsThe session being used by a conversation has been deactivated because of a soutage, causing the conversation to fail.

Probable Cause

Type


Investigate the cause of the outage.




Conversation ID

Partner LU name

Local LU name

Mode name

Session ID




E

a

rking

7036 0137


DetailsThe local TP or partner TP issued a [MC_]SEND_ERROR verb or DEALLOCATverb. The operator data provides more details.

137 The partner TP issued the verb.

138 The local TP issued the verb.

Effect: A new conversation will fail to begin, or an existing one will experienceproblem. Subsequent recovery or termination of the conversation will bedetermined by the applications.

Probable Cause

Type


Check that both transaction programs exist, are correctly named, and are woproperly.




Conversation ID

Partner LU name

Local LU name

Mode name

Session ID

Error Data


241-5701-500 4.1S1


ata

PVnot

duen-to

7036 0141


DetailsThis alarm indicates that there is insufficient memory storage. The operator dprovides more details.

141 The local LU failed to add an entry to the signed-on-to list when sending asign-on Attach (FMH-5) due to resource shortage. The Attach is sent, but doescontain the sign-on request.

142 The local LU was unable to process a Sign-Off verb issued by a local TPto resource shortage. The Sign-Off request fails, and any entries in the signed-oand sign-on-from lists remain valid.

159 Insufficient storage to initialize the half session. The half session fails toactivate with the specified sense code.

Probable Cause

Type

Remedial actionReduce the system load or make more storage available to SNAP APPN.


other fields dependent upon DCL Problem Determination IndexLocal




on

on log

7036 0143


DetailsThis alarm indicates that an error has been detected on an APPC mappedconversation. The operator data provides more details.

143 SNAP APPN detected a mapped conversation protocol error on an APPCmapped conversation.

144 SNAP APPN received an error data GDS variable on an APPC mappedconversation.

Effect: The conversation is terminated, either by an APPC primary_rc ofNAP_CONV_FAILURE_NO_RETRY, or a CPI-C return-code ofCM_RESOURCE_FAILURE_NO_RETRY. The partner TP fails the conversatiwith an APPC primary_rc of NAP_DEALLOCATE_ABEND or a CPI-Creturn_code of CM_DEALLOCATE_ABEND. The session is not deactivated.

Probable Cause

Type

Remedial actionReport the protocol error to partner LU support. If additional diagnostic informatiis required, run a link trace (the session identifier can be used to correlate thisto other logs which contain the appropriate link station name).


TP name

TP identifier

Conversation identifier

Local LU

Partner LU

Mode name

Session identifier


241-5701-500 4.1S1


.

ater

7036 0145


DetailsAn LU received an aping with data length greater than the maximum allowed.

Effect: The conversation is terminated with primary_rc of DEALLOC_ABEND

Probable Cause

Type

Remedial actionReport the error. SNAP APPN LUs should not be apinged with a data size grethan the defined maximum.

Operator DataLocal LU (Alias)

Partner LU(Alias)

Mode name

Max aping size allowed




d at

7036 0150


DetailsThe CRV exchange has failed, indicating that the cryptography keys configurethis LU and the partner LU are inconsistent.

Effect: Session is deactivated.

Probable Cause

Type

Remedial actionCorrect the mismatch in cryptography keys.


other fields dependent upon DCL Problem Determination Index


241-5701-500 4.1S1


an

not

ived

e, or

ious

EB

7036 0151



DetailsLU6.2 session error or protocol error during CRV exchange. This may indicateinteroperability problem. Sense codes are as follows:

080F-6051 - security error

1002-0000 - CRV RU too short

1003-0000 - function not supported (unrecognized request code)

1005-0000 - SIGNAL or LUSTAT request too short

1008-4001 - invalid FM header type

2002-0000 - chaining sequence error

2003-0000 - bracket state error

2004-0000 - received normal flow request when half-duplex flip-flop state wasreceive

2009-0000 - CRV request received from secondary LU, or CRV response recefrom primary LU, or CRV not received when expected.

200A-0000 - immediate request mode violated by partner LU

200B-0000 - queued response indicator invalid

200E-0000 - unexpected SIGNAL response, or uncorrelated positive responsuncorrelated RTR response

200F-0000 - received unexpected response or received EXPD RU before prevEXPD RU has been acknowledged

2012-0000 - unexpected sense code on negative response

4003-0000 - BB not allowed

4004-0000 - received RQE, BB, CEB chain from contention loser, or CEB or not allowed

4008-0000 - CRV with PI set

4007-0000 - definite response not allowed




DE1

DI

calact

4009-0000 - CD not allowed

400B-0000 - chaining error or EC,RQE1/2,CD RU received on full-duplexconversation, or CRV chain indicators not set to BC,EC

400C-0000 - bracket error, or CRV request with BBI, EBI or CEB1 set

400D-0000 - CRV request with CDI set

400F-0000 - incorrect use of format indicator (FI), or CRV with FI not set

4010-0000 - alternate code not supported, or CRV request with CSI set to CO

4011-0000 - RU category of response does not match request, or incorrectspecification of RU category, or CRV not expedited

4012-0000 - request code of response does not match request, or incorrectspecification of request code

4013-0000 - incorrect specification of SDI and RTI, or CRV response RTI and Sinconsistent

4014-0000 - incorrect use of DR1I, DR2I and ERI, or CRV not RQD1

4015-0000 - incorrect use of QRI, or CRV with QRI not set

4016-0000 - incorrect use of EDI, or CRV request with EDI set

4017-0000 - incorrect use of PDI, or CRV request with PDI set

4018-0000 - incorrect setting of QRI with bidder’s BB

4019-0000 - incorrect indications with last-in-chain request

4021-0000 - QRI setting on response does not match request

Probable Cause

Type

Remedial actionUse information on the session deactivated problem log (271) to identify the loLU and partner LU. If required, run a trace on the specified link station and contsupport with the log and trace.


Linkstation Name

LFSID

FQPCID

241-5701-500 4.1S1


e

7036 0155


DetailsLU6.2 session ended abnormally because of insufficient storage.

Effect: session will be deactivated.

Probable Cause

Type

Remedial actionInvestigate resource shortage. Re-engineer FP with less functionality to reducmemory usage.


Linkstation Name

LFSID

FQPCID




ore

n.

to be00).

7036 0157


DetailsA SIGNAL RU or EXPD RU has been received. The operator data provides mdetails.

157 An incoming SIGNAL RU has been received on a full-duplex conversatioThe session is deactivated with the specified sense code (10030004).

158 An EXPD RU has been received while previous expedited data remains processed. The session is deactivated with the specified sense code (200F00

Probable Cause

Type



Sense code

Linkstation Name

LFSID

FQPCID


241-5701-500 4.1S1


.ollows:

ow

hend

7036 0170


DetailsSession error or RU length error. This may indicate an interoperability problemThe session is deactivated with the specified sense code. Sense codes are as f

2011-0000 - sender has overrun pacing window, or PI not set on first RU of wind

2011-0001 - unexpected IPM

2011-0002 - PI set on other than first RU in window

2011-0003 - invalid pacing response

1001-0003 - invalid IPM format

8007-0000 - segmenting error

8007-0001 - segmentation not supported on this link

1002-0000 - RU length error

Probable Cause

Type

Remedial actionUse the information on the session deactivated problem log (271) to identify tlocal LU and partner LU. If required, run a trace on the specified link station acontact support with the log and trace.


Sense code

Linkstation Name

LFSID

Max RU length (optional)

TH




RH

RU

241-5701-500 4.1S1


ata

not

t

ed.fail

isl

ality

7036 0184


DetailsThis alarm indicates that there is insufficient memory storage. The operator dprovides more details.

184 Insufficient storage to generate Alert to report invalid received data. Alert isgenerated.

190 Insufficient storage to start link-inactivity timer. Limited resource link is noautomatically deactivated. If the link is idle, deactivate it using STOP_LS.

191 Insufficient storage to forward HPR Network Layer Packet. NLP is discardIf this error occurs frequently, it may cause RTP connections to path-switch oraltogether.

192 Insufficient storage to register ANR label. HPR traffic using this ANR labelnot routed correctly, which may cause RTP connections to path-switch, or faialtogether.

Probable Cause

Type


Investigate memory shortage. Re-engineer FP with less system load or functionto reduce memory usage.


Other fields dependent upon DCL Problem Determination Index




is

ng

7036 0195


DetailsUnable to correlate DLC credit for MLTG link

This alarm occurs during a window condition in normal link deactivation.

Probable Cause

Type

Remedial actionIf several instances of this log appear and poor RTP connection performanceobserved, investigate further by querying link stations which are members ofMLTGs. Unexpectedly low quantities of data sent over a link may indicateproblems with DLC credit. Contact support with details of the problem, includitrace of signals sent to and from the DLCs underlying the affected links.

Operator DataMLTG name

PC process ID


241-5701-500 4.1S1


ry

be.

7036 0253


DetailsNode Operator Facility (NOF) failed to perform some function due to a memoshortage.The operator data provides more details.

253 Insufficient storage to start SNAP APPN. SNAP APPN was not started.

260 Insufficient storage to process received ACTLU. LU-SSCP session will notstarted. (an ACTLU negative response with the specified sense code is sent)

Probable Cause

Type


Investigate memory shortage. Re-engineer FP to reduce memory usage.


Other fields dependent upon DCL Problem Determination Index




on

7036 0262


DetailsRequired downstream PU template does not exist while activating implicit linka port specifying implicit PU concentration.

Effect: Implicit link is not activated.

Probable Cause

Type

Remedial actionDefine the downstream PU template (using DEFINE_DSPUJ_TEMPLATE) orchange the port configuration (using DEFINE_PORT) to disable implicit PUconcentration or specify an existing downstream PU template.

Operator DataTemplate name

Link name


241-5701-500 4.1S1


late

7036 0263


DetailsThis alarm indicates that the limit on the number of active downstream PU tempinstances has been reached while activating implicit link on a port specifyingimplicit PU concentration.


Probable Cause

Type

Remedial actionRaise the instance limit (using DEFINE_DSPU_TEMPLATE) or deactivate anexisting link which uses the same template.


Link name

Instance limit




LU

7036 0264


DetailsHost LU specified on downstream PU template was found to be a downstreamwhile activating implicit link on a port specifying implicit PU concentration.


Probable Cause

Type

Remedial actionCorrect the definition of the downstream PU template (usingDEFINE_DSPU_TEMPLATE).


Link name

Host LU name


241-5701-500 4.1S1


ifier

7036 0265


DetailsAn ACTLU was received for an LU from the wrong SSCP.

Effect: The ACTLU is rejected with sense code 084B0000 (that is, the LUactivation attempt fails).

Probable Cause

Type

Remedial actionIf the LU must accept the ACTLU for the activation attempt to succeed, the LUdefinition must be changed so that the LU requires the particular SSCP Identthat is actually received from the SSCP or accepts any SSCP Identifier.

Operator DataLU name

PU name

NAU address

Sense code




he

ith

ith

7036 0270


DetailsSession Manager failed to perform some function due to memory shortage. Toperator data provides more details.

270 Insufficient storage to define a new LU type 6.2. DEFINE_LU orSTART_NODE will fail.

275 Insufficient storage to activate LU6.2 session. Session activation will fail wthe specified sense code.

301 Insufficient storage to activate LU-SSCP session. ACTLU will be rejected wspecified sense code.

Probable Cause

Type




Other fields depending upon DCL Problem Determination Index


241-5701-500 4.1S1


7036 0271


DetailsFatal error detected on LU6.2 session.

Effect: Session is deactivated with specified sense code.

Probable Cause

Type


This log gives additional information on the failed session, but is preceded byanother alarm (150, 151, 153, 154, 155, 156 or 157) giving more specificinformation about the fatal error.


Local LU name

Partner LU name

Mode name

LS name

LFSID

Session ID




teUs.

7036 0272


DetailsAn incoming BIND or +RSP(BIND) has specified a duplex support for the remoLU which is inconsistent with that for existing sessions between the partner L

Effect: The BIND or +RSP(BIND) is rejected.

Probable Cause

Type


Contact support with details of the problem.


New duplex support

Existing duplex support

Local LU (Alias)

Partner LU (Alias)

Mode name

Session ID


241-5701-500 4.1S1


r a

een

ls of

7036 0276


DetailsAbnormal UNBIND request received. This may indicate a configuration error, oprotocol error.

Effect: The session fails with the specified sense code.

Probable Cause

Type


If the sense code indicates a configuration error, check for inconsistencies betwthe configuration at the local LU and the configuration at the partner LU. If theconfiguration is consistent and the problem persists, contact support with detaithe problem.


Local LU name

Partner LU name

Mode name

UNBIND RU




7036 0302


DetailsSession limit exceeded.

Effect: Session is brought down or BIND rejected (though if a BIND race isoccurring the other session may lose).

Probable Cause

Type


Raise the session limits.

Operator DataLU name

Mode name

Polarity

FSP count

Bidder count

Total limit

FSP limit

Bidder limit

Sense code


241-5701-500 4.1S1


7036 0306


DetailsFound other active mode for partner LU (no parallel sessions).

Effect: This session is not activated.

Probable Cause

Type


Investigate the configuration. It is probably mismatched.

Operator DataLocal LU name

Partner LU name

This Mode

Active Mode

Sense code




7036 0315


DetailsLU-LU verification failed. This is either configuration problem, a migrationproblem or evidence of a security attack.

Effect: session activation fails.

Probable Cause

Type

Remedial actionVerify the identity of the partner LU and correct any configuration, software orsecurity problems.


Partner LU

Sense Code


241-5701-500 4.1S1


ayh

een

7036 0318


DetailsA BIND or BIND-RSP has been received in response to a BIND request. This mindicate a configuration error, or a protocol error. Common sense codes whictypically indicate a configuration error or a normal race condition include:

0806-0014 - the partner LU is not known

0806-xxxx - the BIND specified a resource which is not known

080F-xxxx - security authorization failed

0821-xxxx - the BIND supplied an invalid session parameter

0835-xxxx - parameter error in BIND RU at offset xxxx

Other sense codes include:

0812-xxxx - invalid PCID in BIND RU

0852-xxxx - duplicate session activation request

0861-xxxx - invalid COS name in BIND RU

088C-xxxx - control vector or subfield missing from BIND RU

0895-xxxx - BIND RU contained in control vector that was in error

0896-xxxx - BIND RU contained a control vector that was too long

Effect: session activation will fail

Probable Cause

Type

Remedial actionIf the sense code indicates a configuration error, check for inconsistencies betwthe configuration of the local LU and the configuration at the partner LU.





Local LU name

Partner LU name

Mode name

BIND RU

241-5701-500 4.1S1


al

ave

ode

7036 0319


DetailsAn UNBIND request was received in response to a BIND request. This mayindicate a configuration error or a protocol error.

Common sense codes which typically indicate a configuration error or a normrace condition include:

0805xxxx - the session could not be activated since session activation limits hbeen reached

0806-0014 - the partner LU is not known

0806-xxxx - the BIND specified a resource which is not known

080F-xxxx - security authorization failed

0821-xxxx - the BIND supplied an invalid session parameter

0835-xxxx - parameter error in BIND RU at offset xxxx

Other sense codes include:

0812-xxxx - session activation failed due to resource shortage at the remote n

083B-xxxx - invalid PCID in BIND RU

0852-xxxx - duplicate session activation request

0861-xxxx - invalid COS name in BIND RU

088C-xxxx - control vector or subfield missing from BIND RU

0895-xxxx - BIND RU contained a control vector that was in error

0896-xxxx - BIND RU contained a control vector that was too long

Effect: session activation will fail.

Probable Cause

Type

Remedial action




een
If the sense code indicates a configuration error, check for inconsistencies betwthe configuration at the local LU and the configuration at the partner LU.

Local LU name

Partner LU name

Mode name

BIND RU

UNBIND RU

241-5701-500 4.1S1


tion

ill

7036 0322


DetailsInsufficient memory storage. The operator data provides more details.

322 There is insufficient storage to generate an Alert to report a BIND segmentaor pacing error. The Alert will not be sent.

323 There is insufficient storage to process received BIND request. The BIND wbe rejected with the specified sense code.

Probable Cause

Type

Remedial actionInvestigate resource shortage. Re-engineer FP to reduce memory usage.






t

7036 0324


DetailsACTPU, ACTLU, DACTPU or DACTLU received over a link on which dependenLUs are not supported. This may indicate an interoperability problem.

Effect: Request is rejected with the specified sense code.

Probable Cause

Type




Link Station name

LFSID

RU


241-5701-500 4.1S1


d

n

7036 0325


DetailsAn interoperability problem. The operator data provides more details.

325 A Branch Network Node has received a BIND request with a badly-formeRSCV. Session activation will fail.

326 SNAP APPN received and rejected a badly-formed BIND request. Sessioactivation will fail.

Probable Cause

Type








form

e

7036 0335


DetailsAPPN Address Space Manager or APPN Address Space Instance failed to persome function due to memory shortage.

Probable Cause

Type






241-5701-500 4.1S1


ace

e

7036 0339


linkstationname - component name of the linkstation

DetailsReceived BIND using LFSID that is already in use. This is usually caused by a rcondition

Effect: BIND will be rejected with specified sense code.

Probable Cause

Type


If problem is persistent, or occurs frequently, contact support with details of thproblem.


Linkstation name

LFSID

BIND RU




tage.

e

7036 0353


DetailsManagement Services failed to perform some function due to a memory shor

Effect: The MU is returned to the sender noting the resource shortage error.

Probable Cause

Type



Operator DataDCL Problem Determination index

Other fields dependent upon DCL Problem Determination index.


241-5701-500 4.1S1


lertseing

ot

7036 0368


DetailsThe system was unable to correlate an error received on an alert send with the astored in the send alert queue. The send alert queue is either too small and thoriginal alert has been deleted or a previous error prevented the alert from beheld on the queue.

Effect: The alert is not sent to the SNA management focal point.

Probable Cause

Type


Investigate definition of send alert queue size (configurable in theAppncomponentattributemdsTxAlertQueueSize) or whether prior memory shortage caused alert nto be held on the queue.




e

7036 0458


DetailsThere was insufficient storage to report RTM statistics to the host

Effect: RTM statistics displayed by host will be inconsistent.

Probable Cause

Type

Remedial actionInvestigate resource shortage. Re-engineer FP with less functionality to reducmemory usage.

Operator DataNAU address


241-5701-500 4.1S1


e

7036 0460


Details APPN could not allocate necessary resource.

Effect: Some operation may fail. See other logs.

Probable Cause

Type







iven

nt,k

de

7036 0462


DetailsA call from SNAP APPN to perform a cryptographic operation failed.

Effect: Session activation fails, or an active session ends abnormally with the gsense code.

Probable Cause

Type

Remedial actionCheck the following logs for evidence of failed session activation. If this is evidecheck MODE, LS, or INTERNAL PU definitions for cryptographic support. Checthat any passwords necessary have been defined. If this problem occursintermittently or with sessions already active with the same PLU, SLU and mothen make more storage available to SNAP APPN.



241-5701-500 4.1S1


iated

7036 0470


DetailsA Class of Service name specified for a session activation could not be assocwith a valid COS.

Effect: A session activation may fail.

Probable Cause

Type


This may indicate a configuration error. If so, the administrator should add therequiredClassOfService component.

Operator DataUnknown COS Name

Origin node

Destination node

Sense Code




lert.

7036 0483


DetailsInsufficient Memory was available to send an Alert.

Effect: The host does not see an Alert. The alert number below identifies the a1 - CPDB001, 2 - CPDB002, 3 - CPDB003, 4,6 - CPDB004, 5,7 - CPDB005. Thealerts are detailed in the Management Services Reference (C30-3346).

Probable Cause

Type



Operator DataTRS Alert Number


241-5701-500 4.1S1


de.

lertis

7036 0484


DetailsAn incorrectly formatted TDU has been received from an adjacent network noThis may indicate an interoperability problem.

Effect: CP-CP sessions with the adjacent network node are deactivated. An anumbered CPBD001 is generated. See subsequent logs for other effects of therror.

Probable Cause

Type



Operator DataAdjacent CP name

Sense Code

CV in error

Offset of error

TDU GDS variable




ry is

se to

t

7036 0490


DetailsUnable to register resource owned by a served end node because the directofull.

Effect: The specified resource is not registered (and the registration request irejected). Network searches for the resource may fail if the end node is unablregister it.

Probable Cause

Type


Investigate configuration. If desirable, increase the value ofmaximumDirectorySizeunder theAppncomponent. Note that this is a process-critical attribute, and thasetting it causes the network node to restart.


Maximum entries

Adjacent CP name

Resource name

Resource type


241-5701-500 4.1S1


f

e

7036 0491


DetailsNetwork search not started because it would exceed the maximum number oconcurrent locates supported by this node.

Effect: Session activation will fail with the specified sense code.

Probable Cause

Type


Investigate setup. If desirable change the value ofmaximumLocates in theAppncomponent. Note that this is a process critical attribute so setting it causes thnetwork node to restart.


Origin CP name

Origin LU name

Destination LU name

Maximum locates




e

7036 0494


DetailsDirectory Services had insufficient memory to perform some function.

Effect: Sessions are deactivated.

Probable Cause

Type


Investigate resource shortage. Re-engineer FP with less functionality to reducmemory usage.


other data depending upon DCL Problem Determination Index.


241-5701-500 4.1S1


rror.

by

7036 0523


adjnode - component name of the adjacent APPN node

DetailsAPPN Control Point Capabilities exchange has failed due to remote protocol e

Effect: CP-CP sessions are deactivated.

Probable Cause

Type

Remedial actionInvestigate the protocol problem with the owner of the remote node identifiedthe operator data. If necessary reproduce the problem and trace the line.



Resource name

Resource type

Component Severity StatusAPPN/name ADJNN/adjnode minor message



PN

7036 0524


adjnode - component name of the adjacent APPN node

DetailsAPPN Control Point Capabilities exchange has failed due to protocol error in APControl Point Capabilities GDS variable.

Effect: CP-CP sessions are deactivated.

Probable Cause

Type

Remedial actionAttention: Local / Remote Admin

Investigate protocol error.



Resource name

Resource type


241-5701-500 4.1S1


o, therk.

ive.

7036 0533


DetailsA network search (originated by this node) or the network node server failed tlocate the target LU. This may be caused by the target LU name being incorrecttarget system being inoperative, or by link errors in the backbone of the netwo

Effect: Session activation fails with the specified sense code.

Probable Cause

Type


If the target LU name is correct, check that the system the LU is defined on is actIf the system is active, check the topology of the network (using theQUERY_NN_TOPOLOGY_* verbs) to ensure that the target system (or itsnetwork node server) is reachable from this node.


Origin CP name

Origin LU name

Destination LU name




es are

ary

ow

ified

7036 0536


DetailsSNAP APPN detected a protocol error in an PIU received on an intermediatesession. This typically indicates a problem on an adjacent node. The sense codas follows.

1001-0003 - invalid IPM format

1002-0000 - RU length error

1003-0000 - CLEAR request on secondary stage, or CLEAR response on primstage

2011-0000 - sender has overrun pacing window, or PI not set on first RU of wind

2011-0001 - unexpected IPM

2011-0002 - PI set on other than first RU in window

2011-0003 - invalid pacing response

8007-0000 - segment error

Effect: The intermediate session will be deactivated.

Probable Cause

Type


Report the problem in the adjacent node to support (running a trace on the speclink if more diagnostics are required).


FQPCID

LS name

TH


241-5701-500 4.1S1


BIU



se of

7036 0537


DetailsThis alarm indicates that the intermediate session is being deactivated becauinsufficient storage.

Probable Cause

Type




FQPCID


241-5701-500 4.1S1


ses

7036 0540


DetailsNo more intermediate sessions could be supported.

Effect: Session activation fails. See log.

Probable Cause

Type


Investigate configuration. If desirable change the value ofmaximumIsrSessionsintheAppncomponent. Note that this is a process critical attribute so setting it cauthe network node to restart.


Active ISR sessions

Link Station name

Primary LU name

Secondary LU name

BIND RU




ny

7036 0564


DetailsLU Manager is unable to perform some function, for example Dynamic Definitioof Dependent Logical Units (DDDLU) because of a lack of memory. ACTLU manot be sent by host.

Probable Cause

Type


Investigate memory shortage. If possible, reduce system load by reducing thenumber of active sessions.

Operator DataPU name

NAU address

LU name


241-5701-500 4.1S1


rerror

7036 0575


DetailsA BIND request was received by an LU type 0, 1, 2, or 3 that failed parametechecks. The sense code that applies to this condition is 0835xxxx, parameterat offset xxxx in BIND RU, The offsets that apply to this sense code are:

0002 - invalid FM profile

0003 - invalid TS profile

0004 - invalid primary FM usage

0005 - invalid secondary FM usage

0006 - invalid common FM usage

0007 - invalid common FM usage

0008 - invalid secondary send pacing

0009 - invalid secondary receive pacing

000A - invalid secondary send RU size

000B - invalid secondary receive RU size

000E - invalid PS profile (that is, invalid session type)

000F - invalid PS usage (applies to RJE BIND only)

0010 - invalid primary half-session PS usage (applies to RJE BIND only)

0014 - invalid default screen or buffer size: rows

0015 - invalid default screen or buffer size: columns

0016 - invalid alternate screen or buffer size: rows

0017 - invalid alternate screen or buffer size: columns

Effect: BIND request will be rejected, PLU-SLU session is not activated.

Probable Cause

Type




Remedial actionCorrect the configuration error on the system sending the BIND.


PU name

NAU address

LU name

BIND RU

241-5701-500 4.1S1


is

7036 0582

Legendname - component name of the APPN router.

dlusname - name of the DLUS pipe.

DetailsDLUS rejects REQACTPU with given sense code.

An SSCP-PU session with the given DLUS is not activated. If a backup DLUSconfigured for the PU, DLUR attempts to activate the PU through the backupDLUS.

Probable Cause

Type

Remedial actionExamine the sense code and, retry activation if appropriate.


DLUS name

PU name

Component Severity StatusAPPN/name DLUS/dlusname minor message



7036 0585



DetailsCPSVRMGR pipe failed to specified DLUS.

Any PUs using the specified DLUS are deactivated (that is, DACTPU (cold) issent.). DLUR may attempt to contact a backup DLUS, if configured.

Probable Cause

Type

Remedial actionIf a pipe with backup DLUS is not initiated automatically, you must restart anyrequired PUs manually.

Operator DataDLUS partner

Sense code


241-5701-500 4.1S1


s

7036 0589



DetailsProtocol Error from DLUS. Received a RU too large for SSCP Session. This itypically due to the SSCP sending too large a LOGON Screen.

The data is discarded.

Probable Cause

Type

Remedial actionIf expecting a SSCP LOGON screen, enter the LOGON command as usual.




Ss

ount

7036 0590


DetailsThe DLUR has failed to contact either the DLUS or the backup or default DLUafter the configured number of retries

Effect: Contact is not made with the DLUS

Probable Cause

Type

Remedial actionResolve any connectivity problems to the host, or increase the timeout or retry cand try again.



241-5701-500 4.1S1


7036 0591


DetailsReceived PLU-SLU BIND request with duplicate FQPCID.

Effect: Session activation fails with the specified sense code (083B0002).

Probable Cause

Type

Remedial actionReport the problem to support (running a trace on the specified link if morediagnostics are required).


Primary LU name

Secondary LU name

FQPCID




7036 0630


adjnode - name of the adjacent node.

DetailsAn HPR Route Setup RU has been received with format errors.

The message cannot be processed, and will be discarded.

Probable Cause

Type

Remedial actionCheck the remote end.


TG number

Adjacent Node Name


241-5701-500 4.1S1


7036 0631


DetailsUnable to correlate HPR Route Setup Reply.


Probable Cause

Type

Remedial actionCheck the remote end.

Operator DataFQPCID




7036 0632


DetailsUnable to activate RTP Connection.

In certain situations, the origin may retry activation.

Probable Cause

Type

Remedial actionExamine sense code and retry activation if appropriate.


Partner Node name

COS name


241-5701-500 4.1S1


k

7036 0633


linkstationname - name of the linkstation

DetailsLink failure between this node and source of Route Setup request.

The route setup request is dropped by this node. The partner node on that linshould generate negative reply.

Probable Cause

Type

Remedial actionInvestigate link failure.

Operator DataFQPCID

Link Station Name




7036 0634


DetailsHPR manager failed to get memory to send a RTP indication.

Probable Cause

Type

Remedial actionCheck memory shortage.


241-5701-500 4.1S1


7036 0635



DetailsA NLP has been received with format errors.


Probable Cause

Type

Remedial actionCheck remote end.


Link Station name

TG number

Adjacent Node name




tocol

7036 0636



DetailsA NLP has been received, but this node does not support the HPR transport prostack.


Probable Cause

Type




241-5701-500 4.1S1


f thisoute

7036 0638


DetailsA connection setup NLP has been received, specifying a previous instance oNCE. The NCE must have been shut down and restarted since processing the RSetup request.

No RTP connection can be started, the NLP will be discarded.

Probable Cause

Type


Operator DataTarget NCE

Current NCE

Partner Node name




HPRand

7036 0639


DetailsThe local node has received a HPR Route Setup RU which it cannot forwardbecause the next hop in the route is not HPR capable. If the local node supportit can act as the destination, otherwise it replies with the backout sense code HPR may not be used by the session.

Probable Cause

Type


Operator DataFQPCID

Next hop CP name

Next hop TG number

Sense code


241-5701-500 4.1S1


ute

outection.

7036 0646


DetailsUnable to activate a Route Setup RTP Connection, during processing of a RoSetup request.

Effect: The Route Setup request fails with the sense code shown. The next RSetup request triggers another attempt to activate the Route Setup RTP Conne

Probable Cause

Type


Investigate memory shortage. If possible, reduce system load by reducing thenumber of active sessions.


Partner node name

TG number




n ortrol

ode

7036 0647


DetailsA connection Setup NLP was rejected because it specified the CP-CP sessioRoute Setup Topic ID, but was received on a TG that does not support the ConFlows over RTP Tower.

Effect: The CP-CP session or Route Setup RTP Connection fails with sense cHA0010017.

Probable Cause

Type



Partner node name

Topic ID

TG Number


241-5701-500 4.1S1


n

7036 0648


DetailsAn HPR Route Setup RU has been received with an FQPCID that matches aexisting route.

Effect: The message is rejected and the route is not established.

Probable Cause

Type

Remedial actionReport error to remote end.

Operator DataFQPCID

Sense code




7036 0662


rtpname - name of the RTP Pipe.

DetailsThe RTP connection has disconnected due to an external error.

Sessions through the connection will fail.

Probable Cause

Type

Remedial actionInvestigate the cause of error.


Connection name

Component Severity StatusAPPN/name RtpPipe/rtpname minor message

241-5701-500 4.1S1


7036 0664



DetailsThe RTP connection has disconnected due to a time out.

The RTP connection will attempt to re-route the pipe.

Probable Cause

Type

Remedial actionInvestigate the cause of error based on the details given above.

Operator DataConnection name

COS name

Remote Node name

Local TCID

Remote TCID




7036 0665

Legend name - component name of the APPN router.


DetailsThe RTP connection has been disconnected by a local link failure.

The RTP connection will attempt to re-route the pipe.

Probable Cause

Type



COS name

Remote Node name

Local TCID

Remote TCID

Link name


241-5701-500 4.1S1


7036 0667



DetailsThe RTP connection could not be re-routed.

Sessions through the connection will fail.

Probable Cause

Type



COS name

Remote Node name

Local TCID

Remote TCID




LPs.

7036 0668



DetailsA Route Setup RTP Connection RTP process received a segmented NLP. All Nreceived should contain Route Setup GDS data, which cannot be segmented

Effect: The NLP is dropped.

Probable Cause

Type



Remote Node name

Local TCID

Remote TCID


241-5701-500 4.1S1


ent

7036 0669



DetailsA Route Setup RTP Connection has timed out waiting for status from the adjacnode.

Effect: The RTP Connection fails.

Probable Cause

Type

Remedial actionInvestigate the cause of the error at the adjacent node.


Remote Node name

Local TCID

Remote TCID




a

is

colow.

col too

r is

Y

IT

r the

7036 0676


DetailsTimer expired before the Discovery request was completed. The operator datprovides more details.

676 Find processing not complete on timer expiry. No retry of FIND frame on thtimer expiry.

677 Invalid correlator on received FOUND frame. This may be due to a protoerror at a Discovery server, or may be caused by the FIND timer being set too lFrame discarded.

678 Invalid correlator on received NOTIFY frame. This may be due to a protoerror at a Discovery server, or may be caused by the QUERY timer being setlow. Frame discarded.

680 Unexpected FIND frame response received, indicating that the FIND timeset too low. Response discarded.

681 Unexpected QUERY frame response received, indicating that the QUERtimer is set too low. Response discarded.

682 Unexpected SOLICIT frame response received, indicating that the SOLICtimer is set too low. Response discarded.

Probable Cause

Type

Remedial actionIf possible, increase the FIND, QUERY or SOLICIT timer value to allow time fothe Discovery request to complete. Otherwise, contact support with details ofproblem.



241-5701-500 4.1S1


e

ing

isntly.

by

o

7036 0679


DetailsInsufficient memory storage. The operator data provides more details.

679 Insufficient storage to start Discovery application. Discovery fails to initializapplication.

688 Insufficient storage to process an incoming Discovery frame. Frame parsabandoned and frame discarded.

693 Insufficient storage to send an Advertise frame for the given resource. Thframe may be resent on a timer, so no effect unless this alarm is seen freque

694 Insufficient storage to send an Notify frame. Information about the givenresource will not reach the requesting Discovery Client.

722 Insufficient storage to generate Alert CPSS003 (protocol error in receivedBIND or LOCATE). Alert will not be sent.

742 Insufficient storage to send RTM statistics to host. RTM statistics displayedhost will be inconsistent.

760 Insufficient storage to process CPI-C function. CPI-C function will fail withreturn_code of CM_PRODUCT_SPECIFIC_ERROR.

822 Insufficient storage to initialize the half session. The half session will fail tactivate with the specified sense code.

Probable Cause

Type


Investigate memory shortage. If possible reduce system load by reducing thenumber of active sessions.





7036 0684


DetailsSubvector of unexpected length in frame. This protocol error may indicate aninteroperability problem.

Effect: Subvector is ignored.

Probable Cause

Type


Operator DataFrame


241-5701-500 4.1S1


7036 0687


DetailsError reported on adapter. Possible error types are as follows.

0x04 - All SAPs for this device must be closed down

0x07 - This SAP must be closed down

0x11 - General device open/lan insertion failure

0x12 - Ring close-down due to excessive Beaconing

0x13 - Hardware/microcode error in adapter

0x14 - PC Network failure

0x15 - Forced off ring during insertion process

0x16 - Error detected during wrap test

0x17 - Forced off ring

0x18 - Error detected in lobe wiring

0x19 - Beaconing error on insertion to the network

0x1A - Another adapter on the network with same address

0x1B - Network hardware error

0x1C - Adapter has been reset

0x30 - SAP has failed

Effect: Adapter is no longer used by Discovery.

Probable Cause

Type

Remedial actionInvestigate the cause of the adapter failure.

Operator Data




Error type

Error code

241-5701-500 4.1S1


rame.

will

ocess

ery

7036 0690


DetailsAn error frame was received. The operator data provides more details.

690 A request frame containing duplicate subvectors has been received. The fwill not be rejected for this reason alone, so possibly no effect. See other logs

691 A request frame of inconsistent total length has been received. The framenot be rejected for this reason alone, so possibly no effect. See other logs.

692 A received request frame does not contain the subvectors necessary to prit. The frame will be ignored.

Probable Cause

Type

Remedial actionThe origin and target of the frame are supplied if known. Check that the DiscovClient being used by the originator is operating correctly. Contact support withdetails.





7036 0719


DetailsCP-CP sessions not supported to adjacent node.

Probable Cause

Type


Ensure that CP-CP sessions are allowed from both ends of the TG.


Lu Name

Mode Name

Conversation Group Identifier


241-5701-500 4.1S1


dex

iteCP-

therlink

7036 0720


DetailsCP capabilities exchange failed because of contention loser (DCL problem in720) or contention winner (problem index 731) CP-CP session failure.

The contention winner/loser CP-CP session (that is, the session in the opposdirection to the one which failed) is deactivated. APPN attempts to reactivate CP sessions with this adjacent CP.

Probable Cause

Type

Remedial actionThis alarm flags the fact that a CP-CP session has failed. Other alarms give furdetails on the reason for the session failure (for example, insufficient resources,failure). Remedial actions indicated for those alarms should be taken.

Operator DataDCL Problem Index

Sense code

Adjacent CP name




e ane as

ode.

ed.

does

me

7036 0723


DetailsCP capabilities exchange failed because of a protocol error. This may indicatinteroperability problem. Sense codes describing the problem in more detail arfollows:

08060030 - CP capabilities requested by an unknown CP

08210002 - CP capabilities requested on other than the CPSVCMG session m

08150007 - CP capabilities requested when CP-CP session already establish

08B60000 - CP-CP sessions not supported by adjacent node.

08090039 - CP transaction error.

10101000 - CP capabilities length error

10101002 - Unexpected GDS identifier (not CP capabilities).

The CP-CP sessions with the specified adjacent node are deactivated. APPNnot attempt to reactivate CP-CP sessions with this adjacent CP.

Probable Cause

Type

Remedial actionReport this problem to the owner of the node identified by the Adjacent CP nain the operator data.


Adjacent CP name

[CP Capabilities vector]


241-5701-500 4.1S1


eee

orkeent

ithtoryons.

redent

7036 0732


DetailsA CP-CP session was established between two network nodes in differentnetworks, that is with different network identifiers. This is not supported by thecurrent published APPN architecture.

The CP-CP sessions are deactivated.

Probable Cause

Type

Remedial actionConnections between APPN networks require a border node. The border nodspecification is not yet part of the published APPN architecture. There are thrchoices to deal with this:

1)Connect the networks through the DPN T2.1 router. This provides a LEN netwimage which permits independent LU sessions to flow across the border betwthe networks, but requires manual definition of directory entries in the adjacennodes.

2)Connect the networks using an AS/400 with the basic Border Node feature. Wthis feature the AS/400 behaves as an APPN End Node and exchanges direcinformation, but no topology information. This supports independent LU sessi

3)Connect the networks using VTAM V4.2 with Extended Border Node. This featuprovides full Network Node support across the border, and supports both depenand independent LU sessions. This requires that VTAM V4.2 be onboth sides ofthe connection.


Adjacent CP name




s to

ality

7036 0742


DetailsAPPN Physical Unit Manager is unable to send response time monitor statisticthe host because of a lack of memory.

Effect: RTM stats may be reported incorrectly to host

Probable Cause

Type


Investigate memory shortage. Re-engineer FP with less system load or functionto reduce memory usage.


NAU address


241-5701-500 4.1S1


ned.

7036 0762


DetailsA CPI-C application specified an unknown symbolic destination name on aCMINIT call.

Effect: The CMINIT call will fail with CM_PARAMETER_CHECK.

Probable Cause

Type


Define the symbolic destination name (using DEFINE_CPIC_SIDE_INFO), ormodify the application to use a symbolic destination name that is already defi

Operator DataSymbolic destination name




7036 0765


DetailsCPI-C application attempted to start more than 64 concurrent conversations.

Effect: CMACCP, CMINIT, or CMINIC verb will fail withCM_PRODUCT_SPECIFIC_ERROR.

Probable Cause

Type


Modify TP to use 64 or fewer concurrent conversations.

Operator Dataconversations


241-5701-500 4.1S1


fined

7036 0776


DetailsThe adjacent node is a back level LEN node but no adj_cp_name has been defor the link.

Effect: The link activation fails.

Probable Cause

Type


Correct the link station configuration by using DEFINE_LS to define anadj_cp_name.


Port name

LS name




es

islink

e isV,

nk

7036 0777


DetailsA link activation race was detected on an ATM port. The operator data providmore details.

777 A link activation race has been detected on an ATM port. The local noderesponsible for resolving this race, and disconnects its link. The remote node’sactivation request succeeds.

778 A link activation race has been detected on an ATM port. The remote nodresponsible for resolving this race. The local node sends a negotiation error Cindicating that the remote link activation request should fail. The local node’s liactivation request succeeds.

Probable Cause

Type

Remedial actionThis is a normal race condition - no action is required.


Sense code

Port name

LS name

TG Number

Adjacent CP name


241-5701-500 4.1S1


ta

n

on-

.ingich

7036 0779


DetailsA PORT_BANDWIDTH_UPDATE signal has been received. The operator daprovides more details.

779 A PORT_BANDWIDTH_UPDATE signal (status = QUIESCING) has beereceived. Any Connection Network TGs on this port will be advertised asquiescing. Any TGs that can be activated automatically will be advertised as noperational.

780 A PORT_BANDWIDTH_UPDATE signal (status = OK) has been receivedAny Connection Network TGs on this port which had been advertised as quiescwill be advertised as active. Any TGs that can be activated automatically and whhad been advertised as non-operational will be advertised as operational.

Probable Cause

Type


If possible, increase the bandwidth available to the local port.


Port name




en ainks

set

7036 0781



DetailsA link station (LS) has been configured to assume a role incompatible with thunderlying DLC. For example, DSPU services have been configured for a LS oport over a Channel DLC. (SNAP APPN always assumes a secondary role on lover a channel DLC, but the role must be primary to provide DSPU services.)

Effect: The link activation fails.

Probable Cause

Type


Correct the configuration of the LS. In the example case, issue DEFINE_LS todspu_services to NAP_NONE, and ls_role to NAP_LS_SEC.

Operator DataDLC name

Port name

LS name

LS role


241-5701-500 4.1S1


ides

ored

).

7036 0782


DetailsSNAP APPN has been unable to locate a link station. The operator data provmore details.

782 SNAP APPN has been unable to locate a defined ANYNET link station. Fany net routing to succeed a link station with the name $ANYNET$ must be definon an ANYNET DLC.

783 SNAP APPN has been unable to locate a link station configured withDEFINE_LS_ROUTING.

Effect: The session activation request fails, with the specified sense code.

Probable Cause

Type


Check the local configuration (link definitions can be viewed using theQUERY_LS verb and routing definitions with the QUERY_LS_ROUTING verb


[LS name]

Sense code




C

n.

7036 0784


DetailsThe DLC has returned inconsistent data during creation.

Effect: The DLC is destroyed, and all ports and link stations defined on the DLare inoperative.

Probable Cause

Type


Run a trace on the DLC and contact support with the log and trace informatio

Operator DataDLC name

DLC capabilities


241-5701-500 4.1S1


er

e

he

7036 0785



DetailsAn automatic retry link station is still inactive after the maximum allowed numbof retries.

Effect: The link station will remain inactive awaiting operator intervention. In thmean time, the activation of any sessions relying on this link station will fail.

Probable Cause

Type


Check surrounding logs for link activation failures. Check the configuration of tlink station. Check the state of the adjacent node. Issue START_LS to retryactivation.

Operator DataLS name




TG.

ork

ork

7036 0786


DetailsSNAP APPN cannot start a link to an adjacent node over a connection networkThe operator data provides more details.

786 SNAP APPN cannot start a link to an adjacent node over a connection netwTG because the link address on the local node is not compatible with the linkaddress on the adjacent node.

787 SNAP APPN cannot start a link to an adjacent node over a connection netwTG because the DLC does not support multiple links between the local anddestination addresses.

Effect: The session will fail, with the specified sense code.

Probable Cause

Type


Check the local and destination link addresses.


Sense code

CN name

Port name

DLC name

TG number

Local link address

Destination link address


241-5701-500 4.1S1


s to

7036 0788


DetailsTG characteristics mismatch for MLTG link.


Probable Cause

Type


Check the link station definitions (or port definitions, if they are implicit). Thesecurity, visibility, and user-defined parameters must be the same for two linkbe added to the same MLTG. If the defined values differ, alter them to match.


Adjacent CP name

Adjacent CP type

Failed LS name

Port name

TG number

Conflicting LS name

Port name

TG number

Sense code




a

7036 0789


DetailsActivation of a Multi-Link TG (MLTG) link has failed due to conflict with anexisting active or defined link.

Probable Cause

Type


If activation of the failing link station is desired, perform one of the followingactions and retry activation.

o Deactivate the link station with which conflict occurs.

o Reconfigure the failing link station to remove the conflict.

o Reconfigure the conflicting link station.

The most likely causes of conflict are

o identical TG numbers (unless both links are MLTG links)

o the adjacent node is not configured to allow the activation of MLTG links, solink configured as MLTG has been activated as a Singly-Linked TG (SLTG)

o different Maximum Send BTU sizes

o different Maximum Receive BTU sizes

o different TG security characteristics

o different TG user-defined characteristics

o different defined visibility.


Adjacent CP name


241-5701-500 4.1S1


Adjacent CP type

Failed LS name

Port name

TG number

Conflicting LS name

Port name

TG number

Sense code



s

s of

7036 0790


DetailsThe remote node has negotiated MLTG support on a link to this node, but harequested SNA function not supported for MLTGs.

Effect: If activating, link activation fails. If active, the link may fail. Checkfollowing audit logs.

Probable Cause

Type


Investigate the illegal behavior of the remote node. Contact support with tracethe illegal behavior.


Adjacent CP name

Adjacent CP type

Failed LS name

Port name

TG number

Sense code


241-5701-500 4.1S1


in

sing

7036 0798


DetailsMLTG link speed disparity. Two links of very different speeds have been placedthe same MLTG.

Effect: The transmission rate which can be achieved on RTP connections pasover this MLTG may be reduced.

Probable Cause

Type


Use QUERY_RTP_CONNECTION to determine the send rate for an RTPconnection passing over the MLTG. Remove the slowest link from the MLTG(issue STOP_LS) and see if the send rate improves.


Adjacent CP name

Adjacent CP type

High-speed LS name

Port name

Low-speed LS name

Port name

TG number




.

7036 0799


DetailsNon-activation XID received on MLTG link.

Effect: The link may fail. See surrounding logs.

Probable Cause

Type


Non-activation XIDs are prohibited by the architectural definition of MLTG linksIdentify the remote node and notify support of this anomalous behavior.


Adjacent CP name

Adjacent CP type

LS name

TG number


241-5701-500 4.1S1


cent

nt,

g

e the

7036 0800


DetailsBranch Network node has insufficient resources to register or deregister an adjaLEN node.

Effect: The directory of this node and/or that of its NNS may become inconsistein that the LEN CP will still be there when it should not be, or vice versa. Thussession activation to the LEN may fail when a link to it is active, or neighborinnodes may believe that the LEN is reachable when the link to it is down.

Probable Cause

Type


Ensure that there are sufficient resources available to SNAP APPN and re-cycllink to the required state.

Operator DataAdjacent LEN name




t-level

velsugh

7036 0840


DetailsA bind response was received that accepted session compression, but did nospecify the compression levels required (because the response is from a backnode or because the bind request was shortened).

Effect: The compression level negotiation fails and the standard compression leare used - this means that compression will be used in both directions even thoit may have been configured for one direction only.

Probable Cause

Type

Remedial actionNone



241-5701-500 4.1S1


t as

7036 0841


DetailsThe desired number of buffers could not be reserved for a buffer pool.

Effect: The receive pacing window size for the session will not increase as fasconfigured.

Probable Cause

Type

Remedial actionInvestigate memory shortage. Re-engineer FP to reduce memory usage.


Partner LU name

Mode name

Session identifier




h.

ckets

7036 0880


DetailsAn RTP connection is path-switching to a much longer path than it started witMuch more room is needed in each packet for routing information than wasoriginally planned.

Effect: Performance across this RTP connection may degrade, since some pamay have to be segmented.

Probable Cause

Type


If performance degradation is noticed, reactivate failed links then issue the‘PATH_SWITCH’ verb.



241-5701-500 4.1S1


get

ly.

7037 0242


DetailsThe space for implicit aliases has wrapped.

Effect: There is a small possibility of APPN generating duplicate aliases. (To this log you have used one million different aliases).

Probable Cause

Type


Shut down and restart the node to avoid possibility of conflict. Check theconfiguration to ensure that you have not introduced alias names inadvertent

Operator Dataalias name




ausech

7038 0005

Legend<nodeName> = component name of the APPN router

<string1> = Instance string identifier of the Virtual Router component

<string2> = Instance string identifier of the Protocol Port component

DetailsThe identified LAN adapter has terminated due to an error it detected.

Effect: All links using this adapter are aborted

Note that this alarm cannot occur in the current release for APPN service becthe LAN adapter is emulated by the Frame-Relay Virtual Circuit termination, whicannot fail.

Probable Cause

Type

Remedial actionAttention: User, Network Support

Correct the problem with the identified adapter.

Operator DataLAN adapter id

Error code

Component Severity StatusAPPN/<nodeName>or Vr/<string1> Pp/<string2> SnaPort

minor message

241-5701-500 4.1S1


ptero

7038 0054

Legend

<nodeName> = component name of the APPN router



DetailsThe LAN adapter failed to activate.

Effect: LLC2 cannot gain network access via this device.

This cannot occur in the current version for APPN service because the LAN adais emulated by the Frame-Relay Virtual Circuit termination, which cannot fail tactivate because it has no associated hardware resources.

Probable Cause

Type


Check cabling and adapter installation. Check device configuration.

Operator DataLAN Adapter id.

return code from device activation


minor message



7038 0060




DetailsThe identified LLC device (LAN adapter) failed to activate.

Effect: LLC2 cannot gain network access via this device.

Probable Cause

Type


Check cabling and adapter installation. Check device configuration.

Operator DataLLC device id

Return code from device activation.


minor message

241-5701-500 4.1S1


give

7038 0065




DetailsThe named link has failed.

Effect: A SNA alert with the specified id is sent to the management servicescomponent. The link itself is closed.

Probable Cause

Type

Remedial actionAttention: User/Network Support

Determine reason for link failure (other messages logged at the same time mayfurther information) and attempt to correct it.

Operator DataLink Failure code

Remote Station MAC address

Remote Station SAP

Local Station MAC address

Local Station SAP


minor message



ent.

give

7038 0066




DetailsThe identified port has failed.

Effect: An alert with the specified id is sent to the management services componThe port itself and any links using this port are closed.

Probable Cause

Type


Determine reason for port failure (other messages logged at the same time mayfurther information) and attempt to correct it.

Operator DataLLC device adapter id

Port address

device failure code

Alert id


minor message

241-5701-500 4.1S1


that

link

7038 0071




DetailsAn attempt has been made to open a link connection to an adjacent link stationis not responding to TEST frames

Effect: The link activation request fails.

Probable Cause

Type


Check the local configuration and/or the hardware and wiring on the adjacentstation.

Operator DataRemote Station MAC address

Remote Station SAP

Local Station MAC address

Local Station SAP


minor message



the

t

7038 0072




DetailsAn attempt to activate a port has failed because the MAC device specified forport is currently resetting.

Effect: The port activation request fails.

Probable Cause

Type

Remedial actionAttention: User

Retry the port activation request, if problem persists, contact Network Suppor


minor message

241-5701-500 4.1S1


e

7038 0075




DetailsLLC2 was unable to perform some function due to a lack of memory.

Probable Cause

Type


Investigate resource shortage. Re-engineer FP with less functionality to reducmemory usage.


minor message



7038 0083




DetailsAn attempt was made to activate a link to the local MAC and SAP address.

Effect: The activation attempt is rejected.

Probable Cause

Type


Change the configuration of the link station to have the correct remote MACaddress.

Operator DataRemote Station MAC address

Remote Station SAP


minor message

241-5701-500 4.1S1


ofange

the

7039 1000

Legend<num1> =1 - 1024

DetailsIf the status is set, theAtmIf component in question has detected that the count associated troubled connections has changed from zero to a non-zero. This chin state signifies that at least one of the connections associated with thisAtmIfcomponent has become troubled, where none were before. Aclear is issued whenthe count of troubled connections associated with thisAtmIf component returns tozero.

Probable CauseFraming error

TypeCommunications

Remedial actionDisplay all of theVpc, Vpt, andVcc components associated with theAtmIfcomponent to determine which ones are troubled. Troubleshoot the problem inusual manner. See 241-5701-715Passport 7400, 15000, 20000 ATM Monitoringand Troubleshooting Guide for details on troubleshooting ATM connections.

Component Severity StatusAtmIf/<num1> minor set/clear



or

all

s

one

7039 2000


<num2> = 0 - 4095

<num3> = 0 - 65535

<num4> = 1 - 4095

<num5> = 0 - 4095

DetailsIf the status isset, the amount of bandwidth provisioned for the indicatedconnection exceeds the amount of bandwidth currently available.

A clearwill be issued when the connection is able to get the bandwidth it needsis deleted.


TypeProcessing

Remedial actionBandwidth is provisioned in theVcd Tmor Vpd Tmsubcomponent of theVpc, Vpt,or Vcccomponents. If the alarm is caused by a connection associated with anAtmIfcomponent, re-configure the bandwidth until the total provisioned bandwidth ofconnections on this interface falls within the maximum bandwidth limit that theinterface can support.

If the alarm is caused by a connection associated with aVpt component, re-configure the bandwidth until the total provisioned bandwidth of all connectionassociated with thisVptcomponent falls within the maximum bandwidth limit thatthe VPT can support.

You can reduce the provisioned bandwidth of one or more connections, deleteor more connections, or increase the available bandwidth of theVpt component.

Component Severity StatusAtmIf/<num1> Vcc/<num2>.<num3>AtmIf/<num1> Vpc/<num4>AtmIf/<num1> Vpt/<num5>AtmIf/<num1> Vpt/<num5> Vcc/<num2>

minor set/clear

241-5701-500 4.1S1


ory

aceever.

e (or

7039 2001


<num2> = 0 - 4095

<num3> = 0 - 65535

<num4> = 1 - 4095

<num5> = 0 - 4095

DetailsThis alarm indicates that more connections have been created under this ATMinterface than the interface is able to accept. The alarm is caused either by memexhaustion or by exceeding the provisioned values of themaxVpcs, ormaxVccsattributes of theCacomponent. TheCacomponent can be associated with anAtmIfor aVpt component.

If the ATM interface is on a spared port, one or more connections on the interfmay not be spared. If an FP switchover occurs in this state, one or more of thconnections may go down. This may or may not come back up after the switcho

Probable CauseStorage capacity problem or configuration error

TypeProcessing

Remedial actionIf provisioned values of themaxVpcs, ormaxVccs attributes have been exceededthen either reprovision theCacomponent or delete one or more connections. If thalarm was raised due to memory exhaustion, delete one or more connectionsother components) to increase available memory.


minor message



r ons

ds

is

BR

7039 2003


<num2> = 0 - 4095

<num3> = 0 - 65535

<num4> = 1 - 4095

<num5> = 0 - 4095

DetailsDue to semantic checks, the conditions that give rise to this alarm cannot occuPassport nodes. As a result, this alarm is temporarily obsolete and the entry imaintained as historical.

This alarm indicates that more connections have been created under the UBRservice category than the service category is able to accept (themaxVpcs andmaxVccs attributes of theUbr component). The UBR service category can beassociated with the ATM interface or a virtual path terminator (VPT).

If the status isset, the unspecified bit rate (UBR) connection provisioned exceethe number of UBR connections currently available.

A clear will be issued when the connection is able to get the ticket it needs or deleted.


TypeProcessing

Remedial actionCheck the value of themaxVpcs andmaxVccs attributes of theUbr component. Ifthe UBR connection is associated with the ATM interface (AtmIf Ca Ubr), thevalues of these attributes control the UBR connections for that interface. If the Uconnection is associated with a virtual path terminator (AtmIf Vpt Ca Ubr), thevalues of these attributes control the UBR connections for that VPT.

Reprovision theUbr component or delete one or more connections.


minor set/clear

241-5701-500 4.1S1


(OC-

to

ortion

7039 2004


<num2> = 0 - 4095

<num3> = 0 - 65535

<num4> = 0 - 4095

DetailsIf the status isset, the amount of bandwidth provisioned for the indicatedconnection under the 1pOC48SmSrPos FP exceeds 1,198,080 kbits/second 24).

A clearwill be issued when the connection reduces its provisionable bandwidthbe equal to or less than 1,198,080 kbits/second (OC-24) or is deleted.


TypeProcessing

Remedial actionBandwidth is provisioned in the Vcd Tm or Vpd Tm subcomponent of the VpcVcc components. If the alarm is raised, reconfigure the bandwidth of the connecto be equal to or less than 1,198,080 kbits/second (OC-24).

Component Severity StatusAtmIf/<num1> Vcc/<num2>.<num3>AtmIf/<num1> Vpc/<num4>

minor set/clear



is

ornder

fallsort.

7039 2005


<num2> = 0 - 4095

<num3> = 0 - 65535

<num4> = 0 - 4095

DetailsIf the status isset, the amount of bandwidth provisioned for the indicatedconnection under the 1pOC48SmSrPos FP exceeds the amount of bandwidthcurrently available at the selected ingress card datapath.

A clear is issued when the connection is able to get the bandwidth it needs ordeleted.


TypeProcessing

Remedial actionBandwidth is provisioned in the Vcd Tm or Vpd Tm subcomponent of the VpcVcc components. If the alarm is raised, re-configure the receive service labels uVr Mpls LspGroup AtmSap ConnId Lbls from either odd to even or even to oddvalues if enough bandwidth is available to admit this connection on the otheringress card datapath. Or you could re-configure the bandwidth until the totalprovisioned bandwidth of all connections on the selected ingress card datapathwithin the maximum bandwidth limit that each ingress card datapath can supp


minor set/clear

241-5701-500 4.1S1


or

orls

ther

fallsort.

7039 2006


<num2> = 0 - 4095

<num3> = 0 - 65535

<num4> = 0 - 4095

DetailsIf the status isset, the amount of bandwidth provisioned for the indicatedconnection under the 1pOC48SmSrPos FP exceeds the amount of bandwidthcurrently available at the selected egress card datapath.

A clearwill be issued when the connection is able to get the bandwidth it needsis deleted.


TypeProcessing

Remedial actionBandwidth is provisioned in the Vcd Tm or Vpd Tm subcomponent of the VpcVcc components. If the alarm is raised, re-configure the transmit service labeunderVr Mpls LspGroup AtmSap ConnId Lbls from either odd to even or even toodd values if enough bandwidth is available to admit this connection on the oegress card datapath. Or you could re-configure the bandwidth until the totalprovisioned bandwidth of all connections on the selected egress card datapathwithin the maximum bandwidth limit that each egress card datapath can supp


minor set/clear



ange

g

7039 3000


<num2> = 0 - 4095

DetailsIf the status is set, theVpt component in question has detected that the count ofassociated troubled connections has changed from zero to a non-zero. This chin state signifies that at least one of the connections associated with thisVpt hasbecome troubled, where none were before. Aclear is issued when the count oftroubled connections associated with thisVpt component returns to zero.


TypeCommunications

Remedial actionDisplay all of theVcccomponents associated with theVptcomponent to determinewhich ones are troubled. Troubleshoot the problem in the usual manner. See241-5701-715Passport 7400, 15000, 20000 ATM Monitoring and TroubleshootinGuide for details on troubleshooting ATM connections.

Component Severity StatusAtmIf/<num1> Vpt/<num2> minor/cleared set/clear

241-5701-500 4.1S1


rval.

d in

ork,

lingn.is

7039 4000


DetailsThe ATM interface has detected one or more LRC errors over a one second inteEach LRC error signifies that a potentially corrupted frame was passed to theinterface for transmission. The number of LRC errors that occurred is includethe alarm text.


TypeCommunications

Remedial actionLRC errors may be caused either by defective hardware somewhere in the networ by transient network conditions, such as the removal or insertion of a card,resetting of a card, enabling or disabling of a bus, running of a bus test, or enabor disabling of an ATM connection. Check to see if any such transient conditiooccurred around the time of the alarm; if so, correct the destabilizing conditionContinue to monitor the situation to see if additional LRC error alarms occur; if thalarm continues to appear, or if major alarm 7039 4001 is raised, apply theDiagnosing LRC Errors procedure documented in 241-5701-715Passport 7400,15000, 20000 ATM Monitoring and Troubleshooting Guide.

Component Severity StatusAtmIf/<num1> minor message



riodted

xt.

for

7039 4001


DetailsIf the status is set, the ATM interface has detected multiple LRC errors over a peof several seconds or more. Each LRC error signifies that a potentially corrupframe was passed to the interface for transmission. Information describing thenumber of LRC errors detected by the ATM interface is included in the alarm te

A clear is issued when no LRC errors have been detected by the ATM interfaceat least 2.5 minutes. Information describing the number of LRC errors and theperiod over which they occurred is included in the alarm text.


TypeCommunications

Remedial actionConsult the Diagnosing LRC Errors procedure documented in 241-5701-715Passport 7400, 15000, 20000 ATM Monitoring and Troubleshooting Guide.

Component Severity StatusAtmIf/<num1> major/cleared set/clear

241-5701-500 4.1S1


niod.

the

t be

7039 5000

Legend<num1> = 1 - 1024

DetailsThis alarm is issued by a Passport AtmInterface (AtmIf). When the status isset, thetotal average link TxUtilization has exceeded the value of thecriticalTxUtilAlarmThresholdattribute for a 3-minute period.

When the status isclear, the total average link TxUtilization has subsequently falleback to a level at or below the corresponding threshold value for a 3-minute perFor the ATM interface, the total average link TxUtilization is calculated everyminute based on comparing the number of cells transmitted by the interface withavailable link bandwidth.

Probable cause

Type

Remedial actionWith a proper threshold setting, this alarm should cause an evaluation of thethreshold or potential congestion conditions. The occurrences of the alarm musevaluated in the context of other parameters, for example, effective cell rate,availability of other atmInterfaces, and routing/loadsharing algorithms.

Component Severity StatusAtmIf/<num1> critical/cleared set/clear



ry for

7040 0000

LegendNone.

DetailsThe identifiedSourceRouteEndStation (Sres) application was unable to obtainsufficient memory to create its forwarding table object.

Effect: SourceRouteEndStation will not function.

Probable Cause

Type

Remedial actionThe problem can be corrected by allocate more memory for theSresprocess. Thisis done by provisioning theMm sresMaxHeapSpace attribute under theVrcomponent to a higher value.

Another way to fix this problem would be to make the Sres RouteEntry tablesmaller. This is done by provisioning theSres routeTableNumEntries attributeunder theVr component to a smaller value.

Changes could also be made in other parts of the system to leave more memoSourceRouteEndStation to use.

Component Severity StatusVr/<string> Sres critical/cleared set/clear

241-5701-500 4.1S1


one

ry for

7040 0001

LegendNone.

DetailsThe identifiedSourceRouteEndStation (Sres) application was unable to obtainmemory while in operation.

Effect:SourceRouteEndStationwill continue to operate but will not be able to learnas many routes as it was provisioned to be able to learn.

Probable Cause

Type

Remedial actionThe problem can be corrected by allocate more memory for theSresprocess. Thisis done by provisioning theMm sresMaxHeapSpace attribute under theVrcomponent to a higher value.

Another solution would be to make the Sres RouteEntry table smaller. This is dby provisioning theSres routeTableNumEntries attribute under theVr componentto a smaller value.

Changes could also be made in other parts of the system to leave more memoSourceRouteEndStation to use.

Component Severity StatusVr/<string> Sres minor/cleared set/clear



w

arm.

7040 0002

LegendNone

DetailsWhen the SRES feature is enabled on a certain protocol port(s), it should beincluded in the software feature list of all LAN LPs on the shelf, in order to alloproper routing of traffic directed to and from it.

This alarm is generated for all LAN LPs that do not haveSres included in theirsoftware feature list.

Probable Cause

Type

Remedial actionAdd the SRES feature to the software feature list of the LP indicated in the al

Component Severity StatusEM/<shelf name> minor message

241-5701-500 4.1S1


the

added

7041 0000

Legend<num1> = 1 - 1024

DetailsThis alarm is generated when there is an address provisioned on the Uni andsame address is registered through ILMI. The provisioned index (primary oralternate) takes precedence over the registered value. (A registered address isto the primary list.)


TypeOperator

Remedial actionDelete the provisioned address.

Component Severity StatusAtmif/<num1> Uni warning msg



rd.

ged.

s or

7041 0001

Legend<num1> = 1 - 1024

DetailsIf the status ismsg, the alarm that there is no MAC address available for the ca

If the status isclear, the alarm indicates that the Ilmi channel is up and has sta


TypeEquipment

Remedial actionThe shelf that the card is on may be too old and does not have a MAC addresthe termination card is faulty.

Component Severity StatusAtmif/<num1> Uni Minor/Cleared msg

241-5701-500 4.1S1


ed.

rror,

atedendsing

7041 0050

Legend<num1> = 1 - 1024

DetailsIf the status isset, the alarm indicates that the ILMI channel is down.

If the status isclear, the alarm indicates that the ILMI channel is up and has stag

Probable CauseProcessor problem, Loss of signal

TypeEquipment, Communications

Remedial actionThe alarm may be generated if the VCC cannot come up, if there is a protocol eif the other side issues a cold start, if the provisioning is mismatched, or ifcommunication on the link is bad.

Check the provisioning on both ends of the Uni and ensure one end is designthe user side and the other end is designated the network side. Check that bothof the link are provisioned as addressEnabled. Check that the link is transmittproperly.

Component Severity StatusAtmif/<num1> Uni Ilmi major/cleared set/clear



as

ated

7041 0051

Legend<num1> = 1 - 1024

DetailsThe alarm indicates that the local Uni and its peer are either both configured Network or are both configured as User.


TypeCommunications

Remedial actionCheck the provisioning on both ends of the Uni and ensure one end is designthe user side and the other end is designated the network side.

Component Severity StatusAtmif/<num1> Uni Ilmi major message

241-5701-500 4.1S1


ork).d. be

7041 0150

Legend<num1> = 1 - 1024

<num2> = 0 - 4095

<atmif type> = Uni “or” Iisp “or” Pnni

DetailsIf the status isset, the alarm indicates that the signalling channel is down.

If the status isclear, the alarm indicates that the signalling channel is up.


TypeCommunications

Remedial actionIf the alarm is on during the system start up, it is possible that

- the “side” attributes for both ends of the Signalling channel may not be setproperly (i.e. both ends may have been set to user-to-user or network-to-netw- the vpi/vci value for the Signalling channel for both ends may not be matche- one end of the Signalling channel was down and the switch may required torestarted.

If the <atmif type> is Pnni, it is possible that the Rcc channel is not up.

Component Severity StatusAtmif/<num1> <atmif type>Atmif/<num1> Vpt/<num2> <atmif type>




ls

c

ck tock to

ent

7041 0200

Legend<num1> = 1 - 1024

<num2> = 0 - 4095


DetailsIf the status isset, the alarm indicates that the Ilmi, Signalling or Rcc channel faito obtain a vcc in the local switch due to insufficient bandwidth.

If the status isclear, the alarm indicates that the vcc for the Ilmi, Signalling or Rcchannel is created successfully.


TypeCommunications

Remedial actionUser can de-provision some existing PVC/SPVC to release the bandwidth bathe bandwidth pool. Or else, user can clear SVC and return the bandwidth bathe pool. SVC call setup is done by the customer equipment. Issuing “clear”command may not be a permanent solution. Reprovisioning of end-point equipmmay be necessary.



241-5701-500 4.1S1


dd.

he

7041 0250

Legend<num1> = 1 - 1024

<num2> = 0 - 4095

DetailsIf the status isset, the alarm indicates that the Rcc channel fails to reachtwoWayInside state.

If the status isclear, the alarm indicates that the Rcc channel has either reachetwoWayInside state or that a provisioning change it has caused it to be delete


TypeCommunications

Remedial actionVerify that the Vcc for the Rcc channel is up. Verify that the far end node is in tsame peer group.

Component Severity StatusAtmif/<num1> Pnni RccAtmif/<num1> Vpt/<num2> Pnni Rcc




c.

7041 0251

Legend<num1> = 1 - 1024

<num2> = 0 - 4095

DetailsThe Vcc used for the Rcc channel has gone down.


TypeCommunications

Remedial actionCheck that both ends of the connection are using the same Vpi.Vci for the Rc


major message

241-5701-500 4.1S1


up.

7041 0252

Legend<num1> = 1 - 1024

<num2> = 0 - 4095

DetailsThe Hello FSM has left the twoWayInside state.


TypeCommunications

Remedial actionVerify that the Rcc channel is up.Verify that the neighbor is in the same peer gro


major message



borng.

he

to

7041 0253

Legend<num1> = 1 - 1024

<num2> = 0 - 4095

DetailsIf the status isset, the alarm indicates that the Hello FSM has detected a neighin a different peer group. This prevents the link from being used for PNNI routi

If the status isclear, the alarm indicates that the Hello FSM has detected that tneighbor is now in the same peer group. The link will now be used for PNNIrouting.


TypeCommunications

Remedial actionThe peer group of this node and/or its neighbor needs to be changed in ordermake them be the same value.



241-5701-500 4.1S1


meup

.

7041 0300

DetailsIf the status isset, the alarm indicates that the configured node is experiencing somemory congestion. It will no longer be included in route calculations for call setrequests.

If the status isclear, the alarm indicates that the configured node is no longerexperiencing memory congestion. It will once again be included in routecalculations for call setup requests.


TypeCommunications

Remedial actionThe configured node will periodically attempt to allocate the required memoryOnce it is successful, the condition will be cleared.

Component Severity StatusArtg Pnni major/cleared set/clear



ilure

7041 0301

DetailsThis alarm is generated during initial provisioning of the component if a MACaddress is not available for the component. This can be caused by a hardware fathat interferes with the distribution of MAC addresses.


TypeCommunications


Component Severity StatusArtg Pnni major/cleared set/clear

241-5701-500 4.1S1


er

n).

t

tingr

he

7041 0302

Legend<level> = level in the hierarchy

DetailsThis alarm is set when one of the following conditions occur:

• The node is the one initiating the SVC and the SVC integrity timexpires or the Hello state goes out of 2-way inside

• The node is the one terminating the SVC and the SVCCestablishment timer expires or the Hello state goes out of 2-wayinside.

This alarm is cleared when one of the following conditions occur:

• The alarm was previously set and the SVCC RCC Hello FSMreaches 2-way inside

• The RCC component to the neighbour no longer exists (i.e. whethere are no longer any inducing uplinks between the two nodes

Probable Cause

Type

Remedial action

To determine what condition is causing the alarm, display the Rcc componenhelloState and the svcState attributes.

If the svcState is inactive, one of the following conditions may be present:

• The SVC cannot be successfully established. There may be a rouproblem or a delay in the notification of uplink removal from lowelevels.ACTION: Look at the lastFailureCauseCode to determine why tSVC is failing

Component Severity StatusArtg Pnni CfgNode/<level> Rcc major set/clear



e

the

s

rs.

• The SVCC RCC SVC was torn down due to a network failure.ACTION: Look at the lastFailureCauseCode to determine why thSVC was torn down.

If the svcState is active and the helloState is Attempt or 1-Way Inside, one offollowing conditions may be present:

• The SVC is up but the Hello protocol running over the channel istuck in Attempt state or 1-way inside state. If this is the nodeterminating the SVCC RCC and the svcState is Attempt, it ispossible that the node is waiting for an inducing uplink beforestarting the Hello protocol over the channel.ACTION: If this is the node terminating the SVCC RCC and thesvcState is Attempt, then wait a minute to see if the condition clea

241-5701-500 4.1S1


bled

pvc

7041 0400

Legend<num1> = 1 - 1024

<num2> = 0 - 4095


DetailsThis alarm is generated when one or more Spvc or Spvp connections are in troucondition.


TypeCommunications

Remedial actionAt end of each Spvc or Spvp retry period, this alarm is cleared if none of the Sand Spvp connections are in troubled condition.


warning/cleared set/clear



nd atm is.

not

e

7041 0401

Legend<num1> = 1 - 1024

DetailsA major alarm is generated when a specified path connection as change state aleast one specified path connection is not using the primary path. A clear alargenerated when all the specified path connections are using the primary path

Probable Cause

Type

Remedial actionThe network operator should poll the switch to determine which connection ison the primary path.

If the connection is using a different path than the primary path, the networkoperator can use the reconnect command to re-establish the connection to thprimary path.

Component Severity StatusAtmif/<num1> major/cleared set/clear

241-5701-500 4.1S1


ve

ion

7041 0500

Legend<num1> = 1 - 1024

<num2> = 0 - 4095


DetailsIf the status isset, one or more connections under the given signalling interface haundergone a successful connection recovery. The alarm is only set if theseconnections are also subscribed to path optimization.

A clear is issued when the connections have been optimized or released.

Probable Cause

Type

Remedial actionThe OPTIMIZE verb can be applied to the Ebr component to trigger anoptimization of the connections at that interface. The triggering of an optimizatresults in an attempt to optimize the connection. The connection will only bererouted if a better route is available.


warning/cleared set/clear



n thearm039

o

ainssfullyeted.

7041 0600

Legend<num1> = 1 - 1024


DetailsIf the status isset, one or more of the switched connections under this ATMinterface are not currently spared, due to a failure to create the connections ostandby port. If alarm 7039 2001 is seen shortly before this alarm occurs, this almay be due to a configuration error. If this alarm is not accompanied by alarm 72001, it may be due to a software error.

If an FP switchover occurs in this state, one or more of the connections may gdown. They may or may not come back up after the switchover.

A clear is issued when all switched connections under this ATM interface are agspared. This may be because the unspared connections have now been succecreated on the standby, or because the unspared connections have been del


TypeProcessing

Remedial actionIf the provisioned values of themaxVpcsor maxVccsattributes have been exceeded(see alarm 7039 2001), either reprovision theCacomponent or delete one or moreconnections. Otherwise, contact Nortel Networks global support.

Component Severity StatusAtmif/<num1> <atmif type> minor/cleared set/clear

241-5701-500 4.1S1


isnelare

y go

owns

maynnotme

7041 0601

Legend<num1> = 1 - 1024


DetailsIf the status isset, at least one control channel (Ilmi, Signalling, or Rcc) under thATM interface is not currently spared, due to a failure to create the control chanon the standby port. This alarm may be due to a configuration error or a softwerror.

If an FP switchover occurs in this state, one or more of the control channels madown. They may or may not come back up after the switchover.

A clear is issued when all control channels under this ATM interface are againspared. This may be because the unspared control channel has now beensuccessfully created on the standby, or because the signalling component thatthe unspared control channels has been deleted.


TypeProcessing

Remedial actionIf the available bandwidth for the ATM interface (Atmif/<num1> CapoolAvailabilityBandwidth) is not sufficient to meet the requirements of allprovisioned connections and the control channels, the provisioned connectionsconsume all the bandwidth on the standby card so that the control channels cabe created. In this case, either increase the configured bandwidth or delete soprovisioned connections. Otherwise, contact Nortel Networks support.

Component Severity StatusAtmif/<num1> <atmif type> minor/cleared set/clear



r a

itsn

rei.e.aresrm

aIk thee

7042 0001

Legend<num1> = 1 - 16383

DetailsWhen dummy data has been inserted continuously due to buffer underflow foperiod equal to thecellLossIntegrationPeriod, a loss of cells alarm will be raised.The alarm will be cleared when the buffer has been re-initialized (i.e. filled to nominal level with valid AAL1 cells), and the service has subsequently been ioperation for a continuous period equal to ten times thecellLossIntegrationPeriodwithout experiencing further buffer underflow.

Probable CausethresholdCrossedCause

TypequalityOfServiceType

Remedial actionBuffer underflow indicates that cells are arriving more slowly than expected, abeing lost in the network, or are of the wrong type to be allowed into the buffer (do not conform to the AAL1 protocol). Ensure that both ends of the connectionprovisioned to have the same traffic rate and that every hop in the network haenough bandwidth to carry the traffic. Ensure that cells which are arriving confoto the AAL1 protocol.

The AAL1 cells arriving at the module from the ATM network are managed byVcccomponent under a particularAtmIfcomponent on an ATM FP. Check the OSstates of these components to ensure they are functioning appropriately. ChecrxCellcount of theVcccomponent to ensure that cells are actually arriving from thnetwork. For more information refer to the Troubleshooting section of the ATMCore Services document.

Component Severity StatusAal1Ces/<num1> major set/clear

241-5701-500 4.1S1


L1t allvedconds.

that

nge

dule.

error

7042 0002

Legend<num1> = 1 - 16383

DetailsWhen AAL1 processing of received cells fails for 2 consecutive seconds, an AAlayer alarm will be raised (note that this includes the scenario where no cells ahave been received). The alarm will be cleared when AAL1 processing of receicells resumes, and has been in synchronous operation for 10 consecutive se

Probable CausecorruptDataCause

TypeprocessingType

Remedial actionEnsure that cells are being received (check therxCells attribute is incrementing).

Ensure that the remote end system is configured to generate AAL1 cells, andtheAal1Cesis associated with the relevantVccwhich is managing the AAL1 cellsarriving from the network.

Ensure the remote end system is generating valid AAL1 data. For example, arrato have local diagnostics run at the far end.

Ensure that received cells are not being discarded due to congestion on the moCheck therxDiscard attribute of the relevantVcc.

Ensure that cells are not being discarded due to noise on the line. Check the statistics for the physical port associated with the relevantAtmIf on the ATM FP.




oned

7042 0003

Legend<num1> = 1 - 16383

DetailsWhen theAep subcomponent of anAal1Ces component has initiated a number ofconsecutive unsuccessful call setup attempts equal to the value of the provisiretryLimit, no further setups are attempted and this alarm is raised.

Probable CausecallEstablishmentErrorCause

TypecommunicationsType

Remedial actionCheck thelastSetupFailureCausein theAepsubcomponent of theAal1Cesand takeappropriate management action, such as reprovisioning.

When the appropriate management action has been taken, issue arestartagainst therelevantAep subcomponent to restart the automatic connection procedure.


241-5701-500 4.1S1


noot.

red.

7043 0001

Legend

DetailsThe Trace Manager was deleted while a trace session was active. Tracing is longer possible on this module until the ‘Trace’ component is provisioned off ro

Probable CausesoftwareProgramTerminationCause

TypeprocessingType

Remedial actionProvision the ‘Trace’ component and receiver list and restart the trace if requi

Component Severity StatusTrace warning message



7043 0002

Legend<component_name> = The service component running the trace.

DetailsTrace was stopped due to the specified duration limit being reached.

Probable CauseoutOfServiceCause

TypeoperatorType

Remedial actionIncrease the trace duration limit and restart the trace if required.

Component Severity Status<component_name> Trace warning message

241-5701-500 4.1S1


ion ishile

7043 0003


DetailsThe trace audit message which is issued every 60 minutes while a Trace Sessactive to remind the operator that the traced service performance is impacted wthe trace is running.

Probable CauseperformanceDegradedCause






ed

trace

e

size

7043 0004


DetailsThe trace queue is 50%, 75% or 100% full. At 100% full trace data will be discarduntil the queue empties to 75% full.

The trace queue fills up because trace data is being generated faster than theVC to the receiver can carry it.

Probable CausequeueSizeExceededCause


Remedial actionReduce the amount of trace data generated by applying filters or truncating thtraced data.

It may also be possible to prevent trace data loss by increasing the trace queueor increasing the trace VC carrying capacity.


241-5701-500 4.1S1


clear

iver.

.

7043 0005


DetailsThe trace call to the receiver has disconnected and tracing has stopped. Thecause and diagnostic code for the failure is given.

Possible causes for this alarm include a failure along the VC path or at the rece

Probable CausecommSubsystemFailureCause


Remedial actionDetermine why the call to the receiver cleared and restart the trace if required




7044 0005

Legend<string1> = Instance string identifier of theVirtualRouter component<string2> = Instance string identifier of theProtocolPort component.

DetailsWhen the status isset, thesnmpAdminStatus attribute has been set to DOWN.

The SnaPort component is administratively disabled.

When the status isclear thesnmpAdminStatus attribute has been set to UP.

Probable Cause

Type

Remedial actionWhen the status isset, use the set verb to set thesnmpAdminStatus attribute toUP.When the status isclear, no remedial action is required.

Component Severity StatusVr/<string1> Pp/<string2> SnaPort minor set/clear

241-5701-500 4.1S1


7044 0006

Legend<string1> = Instance string identifier of the VirtualRouter component

DetailsWhen the status isset, thesnmpAdminStatusattribute has been set to DOWN.

TheSna component is administratively disabled.

When the status isclear thesnmpAdminStatus attribute has been set to UP.

Probable Cause

Type

Remedial actionWhen the status isset, use the set verb to set thesnmpAdminStatus attribute toUP.When the status isclear, no remedial action is required.

Component Severity StatusVr/<string1> Sna minor set/clear



7044 0007


DetailsWhen the status isset, theSna component has been locked.

When the status isclear theSna component has been unlocked.

Probable Cause

Type

Remedial actionWhen the status isset, use the unlock verb to unlock the virtual router’sSnasubcomponent.When the status isclear, no remedial action is required.

Component Severity StatusVr/<string1> Sna critical set/clear

241-5701-500 4.1S1


7044 0008


DetailsThe range ofsnaMaxHeapSpaceattribute is 0 to 100. When this attribute is set toolow, there will be no memory available under the virtual router for theSnacomponent.

Probable Cause

Type

Remedial actionUse the set verb to set thesnaMaxHeapSpace attribute to a higher number.

Component Severity StatusVr/<string1> Mm major message



ed

)

7044 0009


DetailsWhen the status isset, an error has been detected in the provisioning data deliverto data link routing (DLR).

When the status isclear,the provisioning data delivered to data link routing (DLRhas been accepted.

Probable Cause

Type

Remedial actionWhen the status isset, verify that the provisioning data defined for theSna andSnaPortcomponents is correct, then re-apply. When the status isclear, no remedialaction is required.

Component Severity StatusVr/<string1> Sna minor set/clear

241-5701-500 4.1S1


7044 0010

Legend<string1> = Instance string identifier of the VirtualRouter component<string2> = Instance string identifier of the Protocol Port component.

DetailsWhen the status isset, theSnaPortcomponent has been locked.

When the status isclear theSnaPort component has been unlocked.

Probable Cause

Type

Remedial actionWhen the status isset, use the unlock verb to unlock theSnaPortsubcomponent.When the status isclear, no remedial action is required.

Component Severity StatusVr/<string1> Pp/<string2> SnaPort critical set/clear



7044 0011


DetailsAn SnaPort component can only be added to aProtocolPortcomponent for whichthe media application is DLR media.

Probable Cause

Type

Remedial actionTheProtocolPortcomponent under which theSnaPortcomponent is defined musthave alinkToMedia attribute provisioned as a validGvcIf Rg component.

Component Severity StatusVr/<string1> Sna major message

241-5701-500 4.1S1


t

sonthe

Portource

e of

hy

7046 0001

LegendSubComponent = none or Lcn/<n>

<num1> = Decimal [0-15]. Instance identifier of the GVC Interface componen

<n> = Decimal [1-4095]. Instance identifier of the LCN component.

DetailsThis alarm is issued when theissueLcnClearAlarmattribute of theGvcIfcomponentis set to allowed and a call is cleared.

The alarm is used for debugging purposes. It contains information about the reafor clearing the call as well as information about related components affected bycall clear.

If present, the related component information contains the Vr/n Pp/name SnaCircuit/mac,sap,mac,sap where the mac and sap information are those of the sand destination devices of the call.

The Com field contains an explanation about the clear reason. This could be onthe following:

- incoming call refused. Interface locked- incoming call refused. No LCNs available- requested application not registered

Probable Cause

Type

Remedial actionNo operator intervention is required. Examining the alarm data gives a hint of wthe call has been cleared.

Component Severity StatusGvcIf/<num1> SubComponent warning message



t

7046 0002

LegendSubComponent = none or Bnn (if PVC)


<num2> = Decimal [16-4095]. Instance identifier of the DLCI component.

DetailsThis alarm indicates that a frame is received on a BNN DLCI VC containing a(lSap,rSap) pair which is not recognized on this BNN connection.

Probable Cause

Type

Remedial actionVerify that both end-devices are using RFC1490 BNN encoding on this DLCI.

Component Severity StatusGvcIf/<num1> Dlci/<num2> SubComponentwarning message

241-5701-500 4.1S1


t

lede

7046 1000

LegendSubComponent = Dna/<n> Ddm or

Dna/<n> Sdm/<dna> or

RemoteDnaMap/<npi>,<dna>


<n> = Decimal [0-99].

<npi> = Enumeration(x121, e164)

<dna> = BCD(1 to 15 decimal digits).

DetailsThe most probable cause of this problem is the presence of aRemoteDnaMapcomponent with an instance equivalent to that of theDna attribute of aDnacomponent which has aDefaultDnaMapcomponent defined, or it is equivalent to asubDna for which aSubDnaMap component exists.

Provisioning data for the component referred to by this alarm could not be handproperly by the switch. The service still activates without the functionality of thincorrect component.

Probable Cause

Type

Remedial actionDelete either theRemoteDnaMap, theDefaultDnaMap or theSubDnaMapcomponent.

Component Severity StatusGvcIf/<num1> SubComponent indeterminate message



t

7046 3000

Legend<num1> = Decimal [0-15]. Instance identifier of the GVC Interface componen

DetailsThe service cannot be created due to lack of memory.

Probable Cause

Type

Remedial actionRe-engineer the mix of services on the card.

Component Severity StatusGvcIf/<num1> indeterminate message

241-5701-500 4.1S1


7047 0000


DetailsThe system has insufficient resources to allow SNA DLR to start

Probable Cause

Type

Remedial actionRe-engineer the services on the card.

Component Severity StatusVr/<string1> Pp/<string2> SnaPort minor message



7047 0002


DetailsThe DLC provider was not created.

No circuit can be activated through the DLC provider.

Probable Cause

Type

Remedial actionRefer to DLC provider-specific logs for details of the error.


241-5701-500 4.1S1


ote

the

7047 0003


DetailsSNA DLR has insufficient resources to establish a connection initiated by a remend.

Circuits cannot be activated.

Probable Cause

Type

Remedial actionIf further attempts by the remote end to establish a connection fail, re-engineerservices on the card.




n theeer

7047 0006


DetailsA DLR circuit for SNA has failed because of insufficient resources.

The DLR circuit is not established, or is deactivated.

Probable Cause

Type

Remedial actionTry to activate the circuit again. If this fails, reduce the load on SNA DLR byclosing unnecessary circuits and connections, or decrease the system load oDLR machine (for example, by stopping one or more applications), or re-enginthe services on the card.


241-5701-500 4.1S1


n theeer

7047 0008


DetailsA DLR circuit for SNA has failed because of insufficient resources.

The DLR circuit is not established, or is deactivated.

Probable Cause

Type

Remedial actionTry to activate the circuit again. If this fails: reduce the load on SNA DLR byclosing unnecessary circuits and connections, or decrease the system load oDLR machine (for example, by stopping one or more applications), or re-enginthe services on the card.




cal

7047 0010


DetailsA DLR circuit has been idle for the configured timeout period.

The circuit is disconnected.

Probable Cause

Type

Remedial actionThe cause could be a timing problem. Check that the SNA DLR user on the loLAN and remote end are functioning correctly.

Retry the operation, or restart the circuit.


241-5701-500 4.1S1


mpts

7047 0011


DetailsA timer could not be started due to resource shortage.

One or more inactive circuits may not time out. This may cause subsequent atteto activate the circuit to fail.

Probable Cause

Type

Remedial actionRestart SNA DLR.




or re-

7047 0014


DetailsSNA DLR has failed because it has insufficient resources.

All circuits are disconnected and SNA DLR stops.

Probable Cause

Type

Remedial actionDecrease the system load (for example, by stopping one or more applications)engineer the service on the card and restart SNA DLR.


241-5701-500 4.1S1


nal.

s, or or

7047 0015


DetailsSNA DLR has experienced a critical resource failure while processing a data sig

The circuit is deactivated.

Probable Cause

Type

Remedial actionReduce the load on SNA DLR by closing unnecessary circuits and connectiondecrease the system load on the DLR machine (for example, by stopping onemore applications), or re-engineer the service on the card.




7047 0016


DetailsA DLC provider has abended.

Links established through the provider are deactivated.

Probable Cause

Type

Remedial actionRefer to DLC provider-specific logs for details of the problem.


241-5701-500 4.1S1


7047 0017


DetailsA major SNA DLR subcomponent has failed.

All circuits are disconnected and SNA DLR terminates.

Probable Cause

Type

Remedial actionCheck log file for supporting information and notify your Nortel Networkstechnical support group.




erb.

s, orone

7047 0021


DetailsSNA DLR has experienced a critical resource failure while processing a SOF v

The verb has been returned with bad return codes.

Probable Cause

Type

Remedial actionReduce the load on SNA DLR by closing unnecessary circuits and connectiondecrease the system load on the SNA DLR machine (for example, by stoppingor more applications), or make more storage (for example, machine memory)available to SNA DLR, and restart SNA DLR then retry the verb.


241-5701-500 4.1S1


port

7047 0022


DetailsSNA DLR has abended because the component providing local switching suphas abended.

All circuits are disconnected and SNA DLR stops.

Probable Cause

Type





7047 0051


DetailsAn unrecognized or unexpected signal was received from a remote end of thecircuit.

The signal is ignored.

Probable Cause

Type



241-5701-500 4.1S1


cuit.

7047 0052


DetailsAn unrecognized or unexpected signal was received from a local end of the cir

The signal is ignored.

Probable Cause

Type





is

7047 0056


DetailsAn ENTER_BUSY signal was received from a remote end for a circuit which already in Busy state.

The ENTER_BUSY signal is treated as a duplicate and ignored.

Probable Cause

Type



241-5701-500 4.1S1


ot

7047 0057


<string2> = Instance string identifier of the Protocol Port component.

DetailsAn EXIT_BUSY signal was received from a remote end for a circuit which is nin Busy state.

The EXIT_BUSY signal is treated as a duplicate and ignored.

Probable Cause

Type





N,ffic size

ill

g. by

7047 0059


DetailsSNA DLR has failed to add a MAC cache entry due to a non-critical resourcefailure.

The number of circuit set-up messages sent to all partner switches on the WArather than to one specific partner, will increase. The amount of extra WAN tragenerated will depend on the number of partners compared to the configuredof the cache.

SNA DLR will recover from the condition. If this log is repeated, performance wsuffer and WAN traffic will increase.

Probable Cause

Type

Remedial actionIf the problem persists: reduce the load on SNA DLR by closing unnecessarycircuits and connections, or decrease the system load on the DLR machine (e.stopping one or more applications), or re-engineer the service on the card.


241-5701-500 4.1S1


y

g. by

7047 0062


DetailsSNA DLR has experienced a non-critical resource failure.

SNA DLR will recover from the condition. If this log is repeated, performance masuffer.

Probable Cause

Type

Remedial actionIf the problem persists: reduce the load on SNA DLR by closing unnecessarycircuits and connections, or decrease the system load on the DLR machine (e.stopping one or more applications), or re-engineer the service on the card.




fer

s, orone

7047 0063


DetailsSNA DLR has experienced a severe resource failure.

The activation or deactivation of a circuit or connection may fail, or data transmay stop.

Probable Cause

Type

Remedial actionReduce the load on SNA DLR by closing unnecessary circuits and connectiondecrease the system load on the SNA DLR machine (for example, by stoppingor more applications), or re-engineer the service on the card.


241-5701-500 4.1S1


a

7047 0064


DetailsSNA DLR has insufficient resources to establish a connection immediately topartner DLR.

Circuits cannot currently be activated.

Probable Cause

Type

Remedial actionRe-engineer the service on the card.




7048 2001

Cgpn<instance>


DetailsA Cgpn component has already been created under anotherCallingGroupcomponent f the sameCallControl component.

Probable CauseduplicateInfoCause

TypesecurityType

Remedial actionChange the provisioning to remove duplication of theCgpn component under theCallControl component.

Component Severity StatusDataSigChan/<instance> Cc Cg/<instance>warning message

241-5701-500 4.1S1


7048 2002


DetailsThechannelListattribute of theCallingGroup component includes a channelgreater than 23 on a DS1C card.


TypesecurityType

Remedial actionRemove all channels greater than 23 from thechannelList attribute.

Component Severity StatusDataSigChan/<instance> Cc Cg/<instance>warning message



ne

p/x

.

7049 0000

DataSigChan/<instance> critical set/clear


DetailsIf the status isset, the alarm indicates that the Signalling channel is disabled for oof the following reasons: 1) the sigchan or DataSigChan is being created 2) the sigchan or DataSigChan is locked 3) the sigchan or DataSigChan’s framer is disabled 4) the peer or DataSigChan’s d-channel is down

If the status isclear, the alarm indicates that the Signalling channel is back inservice

Probable CauseunderlyingResourceUnavailableCause


Remedial actionIf the alarm status is set for a long period of time:

1) Check the cabling.2) Verify that the physical layer of the Signaling channel is up (for example, LDs1/y and Lp/x rDs1/y Chan/z).3) Check the state of the external equipment connected to the Passport node4) Verify that the attached external equipment of the SigChan is properlyconfigured (one must be master, the other must be slave).5) Lock and unlock the SigChan component.


Component Severity StatussigChan/<instance>

241-5701-500 4.1S1


forally

7049 0001

Legend<num1> = 1 - 15<type> = e1 or ds1<num2>= 0 - 3

DetailsThis alarm indicates that all Uipe debug tracing activity on this port is disabledone minute due to resource exhaustion. Tracing will be re-enabled automaticafter one minute.

Probable CauseatOrNearCapacityCause

TypedebugType

Remedial actionCheck the amount of traffic on this port.Contact your local Nortel Networks technical support group

Component Severity StatusLp/<num1> <type>/<num2> warning message



ld

7049 0002


DetailsIf the status isset, the alarm indicates that the Uipe’s queue to port is full. This coucause many calls to fail on this port.

If the status isclear, the alarm indicates that the queue is no longer full.



Remedial actionCheck the amount of traffic on this port.Contact your local Nortel Networks technical support group.

Component Severity StatusLp/<num1> <type>/<num2> warning set/clear

241-5701-500 4.1S1


s

7049 0003


DetailsIf the status isset, the alarm indicates that the Uipe’s queue to Q921 is full. Thicould cause many calls to fail on this port.








s

7049 0004


DetailsIf the status isset, the alarm indicates that the Uipe’s queue to Q931 is full. Thicould cause many calls to fail on this port.






241-5701-500 4.1S1


7049 0005


DetailsIf the status isset, the alarm indicates that the Uipe’s queue to APC is full. Thiscould cause many calls to fail on this port.








d

7049 0006


DetailsIf the status isset, the alarm indicates that the Uipe’s ISDN buffer is full. This coulcause many calls to fail on this port

If the status isclear, the alarm indicates that the buffer is no longer full





241-5701-500 4.1S1


6.

7049 0007


DetailsThis alarm indicates that a B-channel is out of service because no RESTARTACKNOWLEDGE message is received prior to the second expiry of timer T31



Remedial actionEnsure that the attached B-channel is properly configured.


Component Severity StatussigChan/<instance> critical message



of

7049 0008


DetailsThis alarm indicates that a signalling channel is out of service because noRESTART ACKNOWLEDGE message is received prior to the second expiry timer T316.



Remedial actionEnsure that the attached signalling channel is properly configured.


Component Severity StatussigChan/<instance> critical message

241-5701-500 4.1S1


usyurces

PPomeal

at

rks

7049 0009


DetailsThis alarm indicates that all of the resources required to maintain call states of bchannels are in use. No new calls are accepted by this subroute until these resoare released.

Probable CauseunderlyingResourceUnavailableType


Remedial actionThis alarm may appear during very busy conditions due to congestions in thesubnet and heavy use of non-call associated signalling (signalling required for sPBX features without the use of B-channel). It simply indicates that the internresources are used to maximum capacity.

If this alarm is repeated consistently for every new call attempt, it indicates thresources are not being released.

If there is a frequent recurrence of this alarm, contact your local Nortel Netwotechnical support group.

Component Severity StatusVoiceSubroute/<instance> critical message



r faxsd 5

7049 0010


DetailsThis alarm indicates that the call failed because no compatible voice, modem ocapability was found during end-to-end negotiation. DNA routing information idisplayed if available to aid in the remedial action. This alarm is only generatetimes per hour per voiceSubRoute.



Remedial actionTo correct the problem the user must do one or more of the following:

• make provisioning changes to the selected Voice Profile• modify the features available on the source card• modify the features available on the destination card

Component Severity StatusVoiceSubroute/<instance> warning message

241-5701-500 4.1S1


oing a

romannel

or

7049 0011


DetailsThis alarm may appear on a PP provisioned as the network side, when an outgcall tries to seize a channel which is not available for service on the PBX or inglare situation.

The alarm indicates that the channel is marked unavailable for outgoing calls fthe PP.The marking is done to prevent repetitive attempts to seize the same chwhich is not available on the PBX.

The channel is put back in an available state by an incoming call from the PBXby a midnight maintenance routine performed by the PP.



Remedial actionTo clear the alarm immediately, lock/unlock the channel.

Component Severity StatusVoiceSubroute/<instance> warning message



e

nedble.

rm

7050 0001

Legend<instance> = a string value

DetailsIf the status isset, the Remote Server Agent is unable to forward requests to thVoice Networking Call Server. While this alarm isset, all requests for the serverare discarded.

Possible causes for this alarm are either the VNCS application is not provisioon the CP or the CP is in the process of a switchover and VNCS is not yet availa

A clear is issued when the first request is successfully forwarded to the VNCSserver.



Probable CauseconfigurationErrorCause

TypeprocessingType

Remedial actionVerify that the VNCS application is provisioned on the CP.

If the cause is determined to be CP switchover, no action is required. The alawill clear when VNCS begins accepting requests.

Component Severity StatusRsa/<instance> VncsAccess critical/cleared set/clear

241-5701-500 4.1S1


e of

raffic

7050 0002

Legend<instance> = a string value<n> = a decimal value interpreted as the logical channel number

DetailsThe LAPF transmit queue for this connection has exceeded its maximum valu300 frames and has been purged.

This alarm is caused by congestion along the connection path.

Probable CausequeueSizeExceededCause


Remedial actionThe Remote Server Agent should be re-engineered to decrease the combined tfrom its connections. This could involve configuring an additional RSA in thenetwork and re-homing some of the connections to this new RSA.

Component Severity StatusRsa/<instance> Connection/<n> warning message



ueue

h or

e re-

the

7050 0003

Legend<instance> = a string value<n> = a decimal value interpreted as the logical channel number

DetailsThe LAPF connection has been reset by the peer causing the LAPF transmit qto be purged.

Possible causes for this alarm are either congestion along the connection pata software error.



Remedial actionIf the cause is determined to be congestion, the Remote Server Agent should bengineered to decrease the combined traffic from its connections. This couldinvolve configuring an additional RSA in the network and re-homing some of connections to this new RSA.

If a software error is suspected, contact your local Nortel Networks technicalsupport group.

Component Severity StatusRsa/<instance> Connection/<n> warning message

241-5701-500 4.1S1


eed in

7050 0004

Legend<instance> = a string value

DetailsThe Remote Server Agent has received a request for an unknown server. Thunknown server type and the connection which received the request are reportthe alarm. The request is discarded.

This alarm is caused by a software error.

Probable CauseprotocolErrorCause



Component Severity StatusRsa/<instance> warning message



.

7052 0000


DetailsWhen the status isset, the number of SVCs used by this LAN Emulation Client(LEC) is greater than 95% of the provisioned maximum.

If the maximum is reached, the system automatically releases the oldest 10%

A clear will be issued when the number of SVCs used drops below 85% of theprovisioned maximum, after aset has been issued.

Probable Cause

Type

Remedial actionThe LEC should be provisioned with a largermaxDataSvcs value.

Component Severity StatusLec/<instance> major/clear set/clear

241-5701-500 4.1S1


.

%

7052 0001


DetailsWhen the status isset, the number of LE ARP entries used by this LAN EmulationClient (LEC) is greater than 95% of the provisioned maximum.

If the maximum is reached, the system automatically releases the oldest 10%

A clearwill be issued when the number of LE ARP entries used drops below 85of the provisioned maximum, after aset has been issued.

Probable Cause

Type

Remedial actionThe LEC should be provisioned with a largermaxArpEntries value.

Component Severity StatusLec/<instance> major/clear set/clear



ANisC

nsy are

S).

7052 0002


DetailsWhen the status isset, the LAN Emulation Client (LEC) is unable to join theEmulated LAN (ELAN).

A clearwill be issued when the LEC is able to join the ELAN. The LEC will nowbe operational.

Probable Cause

Type

Remedial actionThe LEC may be provisioned with incorrect values than those provided by the LEmulation Server (LES) or LAN Emulation Configuration Server (LECS). In thcase, the LES or LECS should either be changed or the provisioning of the LEshould be changed.

The LEC may be unable to contact the LES or LECS. The physical connectioshould be checked and the LES and LECS should be checked to ensure that theoperational

The LEC may be unable to register with the Broadcast and Unknown Server (BUThe BUS should be checked to ensure that it is operational and the physicalconnections should be checked.

The LEC will not be operational until this is resolved.

Component Severity StatusLec/<instance> critical/clear set/clear

241-5701-500 4.1S1


and

7053 0000

LegendNone.

DetailsThis alarm is a hierarchical alarm used to clear all outstanding alarms for theMcsMgrcomponent and its subcomponents. This alarm is used when theMcsMgrcomponent is coming up or being deleted to clear any alarms that may be activeare no longer valid. Note that there is no corresponding set for this alarm.


TypeprocessingType


Component Severity StatusMcsMgr clear set/clear



ces

e

e upr

7053 0002

LegendNone.

DetailsThis alarm issetwhen a critical error has occurred in the provisioning of theMcsMgrcomponent. This includes situations were there are insufficient resouravailable to continue.

Probable CauseunderlyingResourceUnavailabeType

TypeprocessingType

Remedial actionAttempt to re-activate provisioning to determine if resource utilization hasimproved such that theMcsMgrcomponent may not become active. If this fails, thMcsMgrcomponent should either be provisioned on a new LP that has morememory available, or the services on the existing LP should be reduced to frememory for theMcsMgrcomponent. Note this alarm will be cleared by the McsMghierarchical clear once theMcsMgr component becomes active.

Component Severity StatusMcsMgr critical set/clear

241-5701-500 4.1S1


it

7053 0003

LegendNone.

DetailsThis alarm issetwhen the number of end points under theMcsMgr componentexceeds the limit specified by themaxEps attribute. No new end points will beallowed until the alarm is cleared



Remedial actionThis alarm is cleared either when the number of end points falls below the limspecified by themaxEps attribute or when the value of themaxEps attribute isincreased.

Component Severity StatusMcsMgr major set/clear



y

fiedr

7053 0004

Legendnone.

DetailsThis alarm issetwhen the number of end points exceeds the value specified bepAlarmThreshold attribute.



Remedial actionThis alarm is cleared when the number of end points falls below the value speciby theepAlarmThreshold attribute. The number of end points may be reduced othe value of theepAlarmThreshold attribute may be increased.

Component Severity StatusMcsMgr minor set/clear

241-5701-500 4.1S1


end

7053 0005

LegendNone.

DetailsThis alarm indicates that there was insufficient memory for theMcsMgrcomponentto bring up an end point.

Probable CauseunderlyingResourceUnavailabeCause

TypeprocessingType

Remedial actionAttempt to reactivate the provisioning. If this fails again, either move theMcsMgrcomponent to a new LP with more available memory or reduce the number ofpoints.

Component Severity StatusMcsMgr minor message



7053 0006

LegendNone.

DetailsThis alarm indicates a provisioning error where an address prefix has beenassociated to more than oneFrf5EpG component.


TypesecurityType

Remedial actionCorrect the provisioning to remove the duplication of theaddressPrefix attribute.This attribute is located under the componentMcsMgr Frf5EpG Addr component.

Component Severity StatusMcsMgr minor message

241-5701-500 4.1S1


call

ster

7053 0100


DetailsThis alarm indicates that an Frf5 End Point provisioned as ‘master’ received arequest from the ATM network.


TypeprocessingType

Remedial actionVerify the provisioning of the two side of the connection. One side should be maand the other should be slave.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>warning message



inged

7053 0101


DetailsThis alarm indicates that an Frf5 End Point received a call request with invalidTraffic Management parameters. This is probably caused by an invalid provisionof the Transfer Priority under one of the Frf5 end points. This attribute is locatunder McsMgr Frf5EpG/<instance> Ep/<instance> Epd


TypeprocessingType

Remedial actionModify the provisioning of the two Frf5 End Point so their transfer priority ismapped into the same ATM service category.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>warning message

241-5701-500 4.1S1


r

7053 0102


DetailsThis alarm is issued when an FRF.5 end point attempts to call its own McsMgcomponent. This configuration is not supported.


TypeprocessingType

Remedial actionRe-provision the value of theremoteAddressattribute under theMcsMgr Frf5EpGAddr component.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>major message



ed a.

one

7053 0103


DetailsThis alarm indicates that an FRF.5 end point provisioned as a slave has receivcall request from the ATM network when there was already a call in progress


TypeprocessingType

Remedial actionVerify the provisioning at the master end of the connection. There can only bemaster end point attempting to connect to a slave end point.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>minor message

241-5701-500 4.1S1


ed a

7053 0104


DetailsThis alarm indicates that an FRF.5 end point provisioned as a slave has receivcall request from the ATM network, from a calling address not matching theMcsMgr Frf5EpG/<instance> Address remoteAddressattribute value.


TypeprocessingType

Remedial actionVerify the provisioning at the master end of the connection, and/or theMcsMgrFrf5EpG/<instance Address remoteAddress attribute value.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>minor message



CIable

for

7053 0105


DetailsThis alarm indicates that an Frf5 End Point was not capable of allocating a DLsubconnection. This is typically caused by the exhaustion of subcontexts availon an ATM FP.


TypeprocessingType

Remedial actionVerify that the number of Dlci components under all McsMgr Frf5EpG Epinstances is within the supported limit as stated in the Engineering GuidelinesFR-ATM network interworking.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>major message

241-5701-500 4.1S1


e

.

all

ate.

7053 0150


DetailsThis alarm issetwhen the number of Frf5 End Point Local Management Interfac(LMI) procedure errors within the lasteventCount events has exceeded thethresholderrorEventThreshold. (Both eventCount and errorEventThreshold areprovisionable attributes) In this situation, the local interface is declared insane

A clear will be issued after a fixed number (provisioning parameter) of correctmessage exchanges between the inter-operating LMI entities. Data transfer inconnections associated with the local DLCIs is resumed.



Remedial actionVerify that the other side of the interface has the LMI protocol enabled. Verify ththe LMI parameters set on the other side are compatible with those on this sidTurn off the LMI protocol if the other side does not support the LMI protocol.

Component Severity StatusMcsMgr Frf5EpG/<instance> Ep/<instance>LMI




)) has

d in

11253ted

ised

7053 020x


DetailsThis alarm occurs when the Frf5 End Point Local Management Interface (LMIreceives a report from the remote end point that a PVC (at the remote end pointbecome inactive. Data transfer to the external network is suspended, for thereported connections associated with a local DLCI.

The PVCs that have just been reported inactive by the remote end point are listedecimal format as part of the comment for this alarm.

Each 7053 020x alarm reports a maximum of 112 PVCs. If there are more thanPVCs on a single component it will become inactive. There may be multiple 70020x alarms generated. The value ‘x’ has an initial value of ‘0’ and it is incremenby one for each alarm.

Probable CausevcActiveCause


Remedial actionCheck the PVC connections listed in this alarm, in the remote end point that rathis alarm.


241-5701-500 4.1S1


use

fast

7053 0300

DetailsThis alarm occurs when the forwarding table for the MCS Agent cannot bedynamically allocated into fast memory. Degraded performance will occur becaforwarding table is in normal memory instead of fast memory.



Remedial actionVerify that the dprsMcsAgent feature has been provisioned first in the sw lptfeatureList of the given lp. Otherwise, the lp must be engineered to make morememory available.

Component Severity StatusMcsMgr warning message



n

7053 0301

DetailsThis alarm occurs when the forwarding table for the MCS Agent cannot add aMCS Ep.

Probable CausesoftwareProgramErrorCause

TypeprocessingType

Remedial actionContact Nortel Networks Global Support.

Component Severity StatusMcsMgr major message

241-5701-500 4.1S1


ing

e ahis

7053 0302

DetailsThis alarm occurs when a CRC check failure occurs on the MCS Agent forwardtable.

Probable CausecorruptDataCause

TypeprocessingType

Remedial actionNo action is required as MCS forwarding will recover eventually. There may btemporary loss and/or re-route of traffic along the DPRS MCS switched path. If talarm persists, contact Nortel Networks Global Support.

Component Severity StatusMcsMgr major message



ory.ataet upis in

sureave

ast

7053 0400


DetailsThis alarm occurs when intercept cannot be dynamically allocated in fast memThe intercept is the software entity on the trunk card responsible for forwarding dpackets onto the Frame Relay access card for a DPRS MCS Switched Path sover a PORS Trunk. Degraded performance will occur because the intercept normal memory instead of fast memory.


TypeprocessingType

Remedial actionEnsure that the total number of DPRS MCS Ups provisioned and/or createddynamically at the node are at or below the recommended engineering limit. Enthat valid feature combinations are supported on this transport FP. The Lp may hto be re-engineered, or additional components re-provisioned to make more fmemory available.

Component Severity StatusMcsMgr DprsEpG/<instance> Ep/<instance>warning message

241-5701-500 4.1S1


ain ahe

oled

tion for

rifyr

faultyour

7053 0401


DetailsThis alarm occurs when the intercept located on the transport card cannot obtlocal message block to send the statistics record to its corresponding Ep on tMcsMgr card when the underlying PORS VC or ATM SPVC, establisheddynamically, is cleared either by the user or the network.

Statistics are polled from the intercept by the Ep at intervals equal to the SpoStatistics poll duration or when a CAS display command is issued. Therefore,inability to send the statistics record when the transport connection is clearedtranslates to a loss of DPRS MCS Switched Path statistics for a maximum duraequal to the polling period. Frequent occurrences of this lead to statistics lossmultiple poll durations.

Probable CauseoutOfMemoryCause

TypeprocessingType

Remedial actionVerify that the total number of DPRS MCS Eps provisioned and/or createddynamically at the node are at or below the recommended engineering limit. Vethat valid feature combinations are supported on this transport FP. Frequent oprolonged occurrences of this condition indicate that either there is a system causing local message block exhaustion or re-engineering is required. Contactlocal Nortel Networks technical support group, if necessary.




ortingard

n

as

ortel

7053 0402


DetailsThis alarm issetwhen the CAC bandwidth usage percentage exceeds the minalarm threshold percentage for this Ep. This value is provisioned on the originaEp in the Cac Cacd component. There are thresholds for both directions (forwand reverse) of the switched path.

This alarm iscleared when the bandwidth usage percentage has dropped to tepercent below the provisioned threshold value.


TypeprocessingType

Remedial actionThis alarm informs the operator that a specific bandwidth usage percentage hbeen reached on the switched path. Re-engineering may be required if thisbandwidth usage percentage is not intended to be reached. Contact your local NNetworks technical support group, if necessary.

Component Severity StatusMcsMgr DprsEpG/<instance> Ep/<instance>minor set/clear

241-5701-500 4.1S1


ortingard

n

as

ortel

7053 0403


DetailsThis alarm isset when the CAC bandwidth usage percentage exceeds the majalarm threshold percentage for this Ep. This value is provisioned on the originaEp in the Cac Cacd component. There are thresholds for both directions (forwand reverse) of the switched path.

This alarm isclearedwhen the bandwidth usage percentage has dropped to tepercent below the provisioned threshold value.


TypeprocessingType


Component Severity StatusMcsMgr DprsEpG/<instance> Ep/<instance>major set/clear



eeions

n

as

ortel

7053 0404


DetailsThis alarm isset when the MCS CAC bandwidth usage percentage exceeds thcritical alarm threshold percentage for this Ep. This value is provisioned on thoriginating Ep in the Cac Cacd component. There are thresholds for both direct(forward and reverse) of the switched path.

This alarm iscleared when the bandwidth usage percentage has dropped to tepercent below the provisioned threshold value.


TypeprocessingType


Component Severity StatusMcsMgr DprsEpG/<instance> Ep/<instance>critical set/clear

241-5701-500 4.1S1


tted

gary.

7053 0405


DetailsThis alarm issetwhen the Ep rejects a CAC request because it has already admithe maximum number (512)of connections.

This alarm iscleared under the following conditions (condition must persist formore than 90 seconds):

• when the Ep has less than 512 connections admitted,

• when the Ep is locked, or

• when Cac is deleted from the Ep.

Probable CausecallEstablishmentErrorCause


Remedial actionRe-engineering is required to admit the frame relay connections that are beinrejected. Contact your local Nortel Networks technical support group, if necess

Component Severity StatusMcsMgr DprsEpG/<instance> Ep/<instance>warning set/clear



on aauseeen

edp,

7053 0406


DetailsThis alarm is generated when there are more than 512 frame relay connectionsswitched path after CAC has been provisioned on the Ep. This can occur becconnections are always admitted onto the switched path if CAC has not yet bprovisioned.

The Ep can only track and display 512 of the connections.



Remedial actionThis situation exists until the number of frame relay connections on the switchpath falls below 512. Contact your local Nortel Networks technical support grouif necessary.


241-5701-500 4.1S1


ablesring

faultFP

ouldthat

7054 0100


DetailsCard is not connected to a sparing panel.

The FP has been unable to connect to the sparing panel either because the chave been incorrectly connected or a cable fault or due to a problem with the spapanel.

Sets the status to major.

A clear is issued when the FP successfully connects to the sparing panel, (cablefixed or connectivity resolved) or the provisioning has been changed so that thedoes not need to register.


TypeequipmentType

Remedial actionCheck the cable for faults or check the provisioning is correct and that the FP shbe connected to this sparing panel. Check the connectivity of the cables. Checkthere are no problems with the sparing panel itself.

Component Severity StatusShelf card/<instance> major/cleared set/clear



tere is

t allare

if

anel,r is

ring

7054 0101


DetailsCard is connected to the wrong sparing panel.HSM will not work with a 1ForN Sparing panelif the sparingconnections are not set.

The FP has successfully connected to a sparing panel, but it is not the correcsparing panel either because the cables have been incorrectly connected or tha provisioning error.


Note: The spare card and each main card sharing this spare card musbe connected to the same sparing panel. This alarm warns you if youusing a 1ForN sparing panel and thesh ca sparingconnectionattribute isset to NotApplicable. Hitless software migration (HSM) does not workthesparingconnection attributes are set to NotApplicable.

A clear is generated when the FP successfully connects to the correct sparing p(connectivity resolved) or the provisioning has been changed so that the erroresolved.


TypeequipmentType

Remedial actionCheck the provisioning is correct and that the FP is connected to the same spapanel as its spare card. Check the connectivity of the cables.


241-5701-500 4.1S1


was

ring

nedt for

7054 0102


DetailsCard is connected to the wrong sparing panel port.

The card was connected to an incorrect port on the sparing panel.

NOTE: The card must be connected to the same sparing panel port for which itprovisioned.


A clear is issued when the FP registers with the correct connection on the spapanel.


TypeequipmentType

Remedial actionEnsure the card is cabled to the same sparing panel port for which it is provisioor change the provisioned sparing connection to match the sparing panel porwhich it is cabled.




t the, a

o

o

gets

e

7054 0103


DetailsSparing panel not responding.

This alarm is used to indicate when an FP is connected to a sparing panel busparing panel is not responding. This can be due to a faulty cable connectionfirmware or hardware fault in the sparing panel itself.

This alarm will be raised when either of the following occur:

1. During sparing panel monitoring, a sparing panel was detected, but failed tprovide any information to the FP.

2. The sparing panel did not provide an acknowledgment of an FP’s attempt t‘grab’ a relay.

Sets the status to “major”.

A clear is issued when the FP receives information from the sparing panel or an acknowledgment of the FP’s attempt to ‘grab’ a relay.


TypeequipmentType

Remedial actionCheck the sparing panel to ensure that it is working correctly. Check the cablconnectivity between this shelf card and the sparing panel.


241-5701-500 4.1S1


t be

7054 0104


DetailsSpare card is in use.

A main FP had failed and the spare FP took over its failure. Sets the status to“major”.

A clear is issued when the spare FP is released.


TypeequipmentType

Remedial actionReplace the main FP if failure is due to a hardware problem. A switchover musissued to release the spare FP.




shelf.

d byck up.

7054 0105


DetailsSpare card is unavailable.

The spare card went down or was removed from the shelf. This breaks thesparing functionality of all LPs sharing this spare card.

Sets the status to “major”.

A clear is generated when the spare FP comes back up or is re-inserted in the


TypeequipmentType

Remedial actionRe-insert the spare card in the shelf if it was removed. This can also be resolveprovisioning a new spare card. Replace the spare card if it does not come ba


241-5701-500 4.1S1


the

le.

7056 0001


DetailsThere has been a severe failure on the VSP card. This may be as a result of failure of a hardware device on the card which affects the transportation of alltraffic. Any traffic still flowing through the card cannot be guaranteed to be reliab

Probable CauseequipmentFailureCause

TypeequipmentType

Remedial actionRestart the card. If a card failure is still raised, a new VSP card is required.

Component Severity StatusLp/<num1> Vsp major set/clear



7056 0002

Legend<num1> = 0 - 15<num2> = 1 - 12

DetailsThe physical module on the VSP card does not match the provisionedmoduleTypein the correspondingPModule component.

Probable CauseproceduralErrorCause

TypeoperatorType

Remedial actionRe-provision themoduleTypeattribute ofPModuleto match the module present onthe VSP card and activate provisioning. If the problem persists andPModule hasbeen provisioned correctly, a new hardware module is required

Component Severity StatusLp/<num1> Vsp PModule/<num2> major set/clear

241-5701-500 4.1S1


7056 0003

Legend<num1> = 0 - 15<num2> = 1 - 12<num3> = 1 - 2

DetailsThere has been a failure of a hardware component on the VSP card duringdiagnostic tests.


TypeequipmentType

Remedial actionRe-run the diagnostic check by unlocking theVsp component. If this fails, rebootthe card. If a failure is still raised, a new hardware module is required.

Component Severity StatusLp/<num1> Vsp PModule/<num2> PBlock/<num3>

critical set/clear



rd

ule

.

7056 0004


DetailsThis alarm is generated when there is a failure of a component on the VSP caduring a provisioning activity.

The comment data includes information to identify the specific hardware modwhich is defective.


TypeequipmentType

Remedial actionReboot the card. If a failure is still raised, a new hardware module is required

Component Severity StatusLp/<num1> Vsp PModule/<num2> PBlock/<num3>

critical message

241-5701-500 4.1S1


ed

isOSFutive

7056 1000

Legend<num1> = 0 - 15999<num2> = 0 - 47

DetailsThis AAL2 CPS Layer alarm is raised when more than 20% of ATM cells receivover the ATM VCC for two consecutive seconds do not yield any AAL2 CPSpackets. An ATM cell will not yield an AAL2 packet when an STF parity error detected or the first packet pointed to by the OSF exhibits an HEC error and thevalue is not equal to the expected value. The alarm is cleared when ten consecseconds pass with no more than 5% of cells with any such errors.

Probable Cause

Type

Remedial actionCheck the VPI/VCI values of all ATM links making up the end-to-end VCC. AnATM VCC carrying non-AAL2 cells will also trigger this alarm.

Component Severity StatusNsta/<num1> Conn/<num2> major set/clear



eenforede

ckTMand

7056 1100


DetailsThis signalling link layer alarm is raised when layer 2 of the CCS stream has bdown for two consecutive seconds. It will be cleared when layer 2 has been upten consecutive seconds. When this alarm is set, all B channels will be assumto be idle and they will not be transported over the AAL2 link. This alarm will braised only when signalling monitoring is enabled.

Probable Cause

Type

Remedial actionLook at theCcst component’s operational attributes to check whether HDLCframes are received error free and transmitted over the ATM link. Similarly, chethe reverse direction as well. If ATM cells or packets are transported over the Aconnection without any errors, check the status of the link layer in the narrowbdevice connected to the PVG service interface (DS1 TDM interface).

Component Severity StatusNsta/<num1> Conn/<num2> Brag/<num3>Ccst

major set/clear

241-5701-500 4.1S1


aturentify

ifiedvice

7056 1101


DetailsThis signalling alarm is generated when an unexpected or an unsupported feis indicated or requested through the CCS stream. The comment data will idethe feature.

Probable Cause

Type

Remedial actionCheck the external devices using the narrowband services trunk for the identfeature. The feature identified should be removed from the external device’s serinterface as a facility.

Component Severity StatusNsta/<num1> Conn/<num2> Brag/<num3>Ccst

warning message



feroents

7056 1200

Legend<num1> = 0 - 15999

DetailsIf the status isset, theNsta/<num1> Vgscomponent has detected that the count oassociated disabled AtmTCon connections has changed from zero to a non-zvalue. This change in state signifies that at least one of the AtmTCon componassociated with thisNsta/<num1> Vgscomponent has become disabled. Aclear isissued when the count of disabled AtmTCon components associated with thisNsta/<num1> Vgs component returns to zero.

Probable Cause

Type

Remedial actionDisplay all of the AtmTCon components associated with theNsta/<num1> Vgscomponent to determine which ones are troubled.

See 241-5701-715Passport 7400, 15000, 20000 ATM Monitoring andTroubleshooting Guide for details on troubleshooting ATM connections.

Component Severity StatusNsta/<num1> Vgs minor set/clear

241-5701-500 4.1S1


r ants

7056 1201

Legend<num1> = 0 - 15999

<num2> = 0 - 21

DetailsIf the status isset, theNsta/<num1> Vgs IpMConn/<num2>component hasbecome disabled and can no longer carry any traffic. Aclear is issued when theNsta/<num1> Vgs IpMConn/<num2> becomes enabled and can carry traffic.

Probable Cause

Type

Remedial actionEach IpMConn is connected to the ATM network via a VCC component undeparticular AtmIf component on an ATM FP. Check the status of these componeto ensure they are functioning appropriately.


Component Severity StatusNsta/<num1> Vgs IpMConn/<num2> major set/clear



ent

7056 1202

Legend<num1> = 0 - 15999

<num2> = mg or sg

DetailsIf the status isset, theNsta/<num1> Vgs Ctrl/<num2>component has becomedisabled and can no longer carry any traffic. Aclear is issued when theNsta/<num1> Vgs Ctrl/<num2> becomes enabled and can carry traffic.

Probable Cause

Type

Remedial actionEachCtrl is connected to the ATM network via a VCC component under aparticular AtmIf component on an ATM FP. Check the status of these componto ensure they are functioning appropriately.


Component Severity StatusNsta/<num1> Vgs Ctrl/<num2> major set/clear

241-5701-500 4.1S1


, no

t

nst the

7056 1203

Legend<num1> = 0 - 15999

<num2> = 1 - 2

<num3> = 0 -21

<num4> = 1 - 1024

DetailsWhen anAap or SpvcAp subcomponent has initiated a number of consecutiveunsuccessful call setup attempts equal to the value of the provisioned retryLimitfurther setups are attempted and this alarm is raised.

Probable Cause

Type

Remedial actionCheck thelastSetupFailureCausein theAaporSpvcApsubcomponent managemenaction, such as reprovisioning.

When the appropriate management action has been taken, issue a restart agairelevantAap or SpvcAp subcomponent to restart the automatic connectionprocedure.

Component Severity StatusNsta/<num1> Vgs Ctrl/<num2> AapNsta/<num1> Vgs Ctrl/<num2> SpvcApNsta/<num1> Vgs IpMConn/<num3> AapNsta/<num1> Vgs IpMConn/<num3> SpvcApNsta/<num1> Vgs AtmTConn/<num4> AapNsta/<num1> Vgs AtmTConn/<num4>SpvcAp

major set/clear



thatued

nis a

r oroot

en

7056 1204

Legend<num1> = 0 - 15999

DetailsIf the status is set, the Nsta/<num1> Vgs component in question has detectedthe connectivity to the MF remote signalling device has been lost. A clear is isswhen the connectivity is restored.Connectivity can be lost for the following reasons. Either the control connectiothat uses an ATM VCC to connect to the nearest IP router is disabled, or thereconnectivity problem somewhere in the IP network that prevents the PVG fromcommunicating with the MF remote signalling device.

Probable Cause

Type

Remedial actionDisplay the ControlConnection subcomponent of the Vgs to determine whethenot the associated ATM connection is troubled. If it is troubled then troubleshthe problem in the usual manner (see 241-5701-715Passport 7400, 15000, 20000ATM Monitoring and Troubleshooting Guide for details on troubleshooting ATMconnections). If the ATM connection is nottroubled then there will be an IP connectivity problem within the network betwethe PVG and the MF remote signalling device.

Component Severity StatusNsta/<num1> Vgs minor set/clear

241-5701-500 4.1S1


oontlear,

set isd a and

hedr is

setm

ait.

7056 1208

Legend<num1>=0 - 15999

DetailsIf the status is set, the Nsta/<num1> Vgs LocalAnnouncements component inquestion has detected that the configured announcement file set is missing, tlarge, incompatible with the Announcement feature, or that the Announecemefeature does not have a valid announcement file loaded. When the status is Cthe component has detected that the currently configured announcement file present, of the correct size, is compatible with the Announcement feature, anvalid announcement file (not necessarily the latest configured one) is presentactive in the FP.

Probable Cause

Type

Remedial actionCheck attribute Nsta/n Vgs LocalAnnouncements fileTransferStatus.

If this attribute has value “missing,” ensure both file types (.ind and .aud) with tconfigured name are present in the configured location. Update the configurefilename or rename or copy files to the correct location, as appropriate. Transfeautomatic.

If this attribute has value “fileTooLong,” reload the announcement files with a with a combined length of <16MB. Reexport the new announcement fileset froUAS APS as required. Transfer is automatic.

If this attribute has value “fileError,” ensure both file types (.ind and .aud) arecompatible with the file formats defined in this document.Reexport the newannouncement fileset from UAS APS as required. Transfer is automatic.

If this attribute has value “inProgress,” check attribute Nsta/n VgsLocalAnnouncements currentFileName. If this attribute returns a null string, wThis alarm should clear in approximately 1 (one) minute under quiescentconditions. On a heavily loaded system, however, clearing may take longer.

If this attribute has value “cpNotResponding,” check that the CP disks are notlocked. If they are not locked, the alarm should clear after a period of time.

Component Severity StatusNsta/<num1> VgsLocalAnnouncements

minor set/clear



s, or ifur,

tatusbyent

orset.

7056 1209

Legend<num1> = 0 - 15<num2> = 1 - 12

DetailsIf the status isset, the SSM, as indicated by Lp/<num1> Vsp Pmod/<num2>, haundergone a failure as detected by the FP. Reset was tried once. If reset failsit is apparently successful but there is a failure of the SSM again within the hothe VSP FP will be reset. This may cause VSP protection switch. When the sis Clear, the SSM is functional. The functionality of individual tasks carried outthe SSM may be indicated by specific alarms associated with feature dependcomponents.


TypeequipmentType

Remedial actionNone. Either this is alarm will reset (within a minute), and full recovery hasoccurred, or the VSP will reset. At this point, the Pmod alarm will reset. This priindication of a Pmod alarm may be used to indicate the reason for the VSP re

Component Severity StatusLp/<num1> Vsp PModule/<num2> minor set/clear

241-5701-500 4.1S1


ice.

7056 1210

Legend<x>= 0 - 15999<y>= 0- 15999<z>= 1- 31<w>= 1 - 31

DetailsIf the status isset, there has been a layer 2 failure of the PRI D-channel link. Aclearis issued when the D-channel layer 2 failure has cleared.

Probable Cause

Type

Remedial actionCheck cabling.

Check for transmission problems; for example, error bursts, slips, etc.

Check for disabling of the D-channel by an operator at the PRI-controlled dev

Component Severity StatusNsta/x Vgs Brag/y Q921/z major set/clear



ut

an

7056 1211

Legend<x>= 0 - 15999

DetailsIf the status isset, the SG is fully operational (i.e. there are no internal errors) ball the backhaul links between the SG and any MGCs are down.

A clear is issued when at least one of the backhaul links between the SG andMGC has moved to theup or active state.

Probable Cause

Type

Remedial actionThe operator can monitor theNsta/x Vgs Control/sg SctpPort/z SctpLink/wcomponents to determine the status of the SCTP links.

Component Severity StatusNsta/x Vgs Iua major set/clear

241-5701-500 4.1S1


aof a

7056 1212

Legend<x>= 0 - 15999

DetailsThis message alarm is issued when a switchover between MGCs occurs (i.e.standby MGC takes over from a primary). This may occur as a consequence failure condition or an operator initiated action, such as taking an MGC out ofservice.

Probable Cause

Type

Remedial actionThe operator can examine theNsta/x Vgs Iua Asp/ycomponent to determine thestatus of the associated ASPs. This will indicate which MGC has gone down.

The operator can monitor theNsta/x Vgs Control/y SctpPort/z SctpLink/wcomponent to determine the status of the STCP links.

Component Severity StatusNsta/x Vgs Iua warning message



vice.

7056 1213

Legend<num1> = 0 - 15999

<num2> = 0 - 127

<num3> = 15, 16, or 31

DetailsIf the status isset, there has been a layer 2 failure of the V5.2 C-channel link. Aclear is issued when the C-channel layer 2 failure has cleared.

Probable Cause

Type

Remedial actionCheck cabling.

Check for transmission problems; for example, error bursts, slips, etc.

Check for disabling of the C-channel by an operator at the V5.2-controlled de

Component Severity StatusNsta/<num1> vgs brag/<num2> v5Link lapV5/<num3>

major set/clear

241-5701-500 4.1S1


nedrval

tion,

e

.

7057 0001

Legend<instance> = instance of the DcmeLink (1-14)

DetailsIf the status is set, the number of rejected speech calls has reached a predefithreshold over a predefined time interval. The threshold value and the time inteare provisionable attributes under the correspondingDcme component.

A clear is issued when the number of rejected speech calls drops below thethreshold over the subsequent time interval.



Remedial actionA large number of rejected speech calls indicates that there were no networkresources available to handle these calls. This may be due to network congesfailure of network resources, or misconfiguration of thepreestablishedConnectionsattribute under the correspondingDcme component.

Verify the availability of network resources. The network may require re-engineering to handle higher traffic loads.

If network resources are available and the alarm is not cleared, the value of thpreestablishedConnectionsattribute is too low for the actual call rate received fromthe ISC equipment.

If you set thespeechAlarmThresholdattribute to 0, this alarm will not be generated

Component Severity StatusDcmeLink/<instance> major/cleared set/clear



ined

tion,

e

.

7057 0002


DetailsIf the status is set, the number of rejected 3.1 kHz calls has reached a predefthreshold within a predefined time interval. The threshold value and the timeinterval are provisionable attributes under the correspondingDcme component.

A clear is issued when the number of rejected 3.1 kHz calls drops below thethreshold in the subsequent time interval.



Remedial actionA large number of rejected 3.1 kHz calls indicates that there were no networkresources available to handle these calls. This may be due to network congesfailure of network resources, or misconfiguration of thepreestablishedConnectionsattribute under the correspondingDcme component.


If network resources are available and the alarm is not cleared, the value of thpreestablishedConnectionsattribute is too low for the actual call rate received fromthe ISC equipment.

If you set the3kHzAlarmThresholdattribute to 0, this alarm will not be generated


241-5701-500 4.1S1


finedrval

e

rkon or

7057 0003


DetailsIf the status is set, the number of rejected 64 Kbits/s calls has reached a predethreshold over a predefined time interval. The threshold value and the time inteare provisionable attributes of the correspondingDcme component.

A clear is issued when the number of rejected 64 Kbits/s calls drops below ththreshold in the subsequent time interval.



Remedial actionA large number of rejected 64 Kbits/s calls indicates that there were no networesources available to handle these calls. This may be due to network congestifailure of network resources.


If you set the unrestricted64kAlarmThresholdattribute to 0, this alarm will not begenerated.




ct.

nd.

7057 0004


DetailsIf the status is set, the DcmeLink negotiation with the far endDcmeLinkcomponenthas failed.

Either the remote and local profile attributes are different or the DNAs are incorre

A clear is issued when the negotiation with the far end is successful.

Probable CauseversionMismatchCause


Remedial actionVerify the profile attributes values and the DNAs at the local and the remote e

Component Severity StatusDcmeLink/<instance> critical/cleared set/clear

241-5701-500 4.1S1


7057 0005


DetailsThis message indicates that an attempt to lock theDcmeLink component wasunsuccessful, because thevsTypeattribute of at least one of theVssubcomponentswas provisioned to permanent64kVs.

Locking of this DcmeLink disables all of theVs subcomponents, including thepermanent64kVs type. By definition, this type ofVs component is permanent andit should not be disabled accidentally.

If you need to lock theDcmeLinkcomponent after the warning is issued, follow thesteps described in the Remedial action section.

Probable CauseproceduralErrorCause

TypeoperatingType

Remedial actionDisable allVs components withvsType of permanent64kVs through the LOCKDcmeLink/<instance> Vs/<vsInstance>, then lock theDcmeLink componentthrough the LOCK DcmeLink/<instance> command.

Component Severity StatusDcmeLink/<instance> minor message



ityThe

thece is

nt the

7058 0001

Legend<num1> = the hunt group instance (1-65535)

DetailsIf the status isset, this alarm indicates that the hunt group received an availabilupdate from a service that was not configured as a member of the hunt group.availability update is discarded and thebadPackets attribute is incremented.

This occurs due to a provisioning inconsistency between the hunt group and service. Either the hunt group is missing this service as a member; or the servireporting availability to the wrong hunt group.

A clear is issued after a provisioning change is made to theHuntGroupMembercomponents of the hunt group.


TypeprocessingType

Remedial actionUse the address reported in the alarm to identify the service reporting theavailability update and determine if this service should be a member of the hugroup. If it should, add the member to the hunt group. If not, correct or deleteHuntGroupAddress component of the service.

A manual clear of this alarm is required if the provisioning is corrected on theservice and not on the hunt group.

Component Severity StatusHg/<num1> warning/cleared set/clear

241-5701-500 4.1S1


s the

7059 0000

Legend<string> = Instance string identifier of the VirtualRouter component.

DetailsWhen the status isset, this alarm indicates that the number ofResCacheEntryentries used by thisNhrp component is greater than 95% of the provisionedmaximum.

If the maximum number of entries is reached, the system automatically releaseoldest 10% of the entries.

A clearwill be issued when the number ofResCacheEntryentries used drops below85% of the provisioned maximum, after aset has been issued.

Probable Cause

Type

Remedial actionTheNhrp component should be provisioned with a largermaxResCacheEntriesvalue.

Component Severity StatusVr/<string> Ip Nhrp major/cleared set/clear



ount

rm

7060 1000

Legend<instance> = The LP instance number

DetailsIP routes/subconnections overbookings

The number of IP routing entries and/or subconnections has exhausted the amof memory available. Since theLp/<instance> Eng Fcrc Pqc OvattributeipRoutesPoolCapacity and theLP/<instance> Eng Fcrc Ov attributesubConnectionPoolCapacity share the same pool of memory, it is not alwayspossible to guarantee the maximum value of both of these attributes. The alaindicates the actual number of subconnections and/or IP routes allocated.



Remedial actionDecrease the number of IP routing entries in theLp/<instance> Eng Fcrc Pqc OvattributeipRoutesPoolCapacity and/or the number of subconnections in theLp/<instance> Eng Fcrc Ov attribute subConnectionPoolCapacity.

Warning: This will cause the cards associated with the Lp to reset.

Component Severity StatusLp/<instance> Eng Fcrc major set

241-5701-500 4.1S1


’s

ng

ove. Aute.

g isf

7060 1100


<aqmInstance>=0-3

DetailsrxCellMemoryAvailable resources reaching a low level.

If the status is set, the available egress cell-blocks from the logical processorspecified AQM have fallen below 20% of total egress cell-blocks. Under thiscondition, traffic flowing across this AQM on this FP may encounter high queueidelays.

When this condition is detected, lower priority traffic is discarded first. Ifcongestion persists, higher priority traffic is discarded. This continues untilavailable egress cell-blocks for the logical processor’s AQM have increased ab25% of the total egress cell-blocks. A clear is issued automatically at this pointfiltering mechanism is implemented such that a set/clear is issued by one min



Remedial actionFrequent or prolonged occurrences of this condition indicate that re-engineerinrequired to balance the flow of traffic through this card to reduce the amount otraffic and the length of queues.

Lower the connection pool capacity for this AQM.

Warning: This will cause the card associated with the Lp to reset.

Component Severity StatusLP/<instance> Eng Arc Aqm/<aqmInstance>warning/cleared set/clear



eflect

Arc

7060 1200


DetailsThe provisioned connection capacity, the sum of theconnectionPoolCapacity,protectedConnectionPoolCapacity, multicastBranchesCapacity andprotectedMcastBranchesCapacityattributes, for theArc Ov component is higherthan what this particular card can handle.

No serious damage occurs on the card, however the operational values do not rprovisioned values.


TypeprocessingType

Remedial actionDetermine the total connection capacity the card can support by checking thecomponent and reduce the provisioned connection capacity in the Arc Ovcomponent accordingly.

Warning : This will cause the card associated with the Lp to reset.

Component Severity StatusLP/<instance> Eng Arc Ov warning message

241-5701-500 4.1S1


of

ee ism

7060 1300

Legend<x>= 1 - 15

DetailsHardware forwarding resource usage for incoming IP/MPLS connections at 85%maximum.

Probable CauseResource exhaustion


Remedial actionContact first level support for help with re-engineering the network to allow thresource usage to move below a critical level. Hardware forwarding performancdegraded when the hardware forwarding resource usage reaches the maximuvalue.

Component Severity StatusLP/<x> Eng critical message



of

ee ism

7060 1400

Legend<x>= 1 - 15

DetailsHardware forwarding resource usage for outgoing IP/MPLS connections at 85%maximum.

Probable CauseResource exhaustion


Remedial actionContact first level support for help with re-engineering the network to allow thresource usage to move below a critical level. Hardware forwarding performancdegraded when the hardware forwarding resource usage reaches the maximuvalue.

Component Severity StatusLP/<x> Eng critical message

241-5701-500 4.1S1


of the

le.

.

7062 0001


DetailsThere has been a severe failure on the PCUSP card. This may be as a resultfailure of a hardware device on the card which affects the transportation of alltraffic. Any traffic still flowing through the card cannot be guaranteed to be reliab

Probable Cause

Type

Remedial actionRestart the card. If a card failure is still raised, a new PCUSP card is required

Component Severity StatusLp/<num1> Pcusp major set/clear



7062 0002

Legend<num1> = 0 - 15<num2> = 1 - 12

DetailsThe physical module on the PCUSP card does not match the provisionedmoduleType in the correspondingPModule component.

Probable Cause

Type

Remedial actionRe-provision themoduleTypeattribute ofPModuleto match the module present onthe PCUSP card and activate provisioning. If the problem persists andPModulehasbeen provisioned correctly, a new hardware module is required

Component Severity StatusLp/<num1> Pcusp PModule/<num2> major set/clear

241-5701-500 4.1S1


g

7062 0003

Legend<num1> = 0 - 15<num2> = 1 - 12<num3> = 1

DetailsThere has been a failure of a hardware component on the PCUSP card durindiagnostic tests.

Probable Cause

Type

Remedial actionRe-run the diagnostic check by unlocking thePcuspcomponent. If this fails, rebootthe card. If a failure is still raised, a new hardware module is required.

Component Severity StatusLp/<num1> Pcusp PModule/<num2> PBlock/<num3>

critical set/clear



ding

ule

7062 0004

Legend<num1> = 0 - 15<num2> = 1 - 12<num3> = 1

DetailsThis alarm is generated when a SPM module on the PCUSP card is not responto supervision heartbeat message.

The comment data includes information to identify the specific hardware modwhich is defective.

Probable Cause

Type

Remedial actionNo action needed. The SPM module is being reset.

Component Severity StatusLp/<num1> Pcusp PModule/<num2> PBlock/<num3>

critical message

241-5701-500 4.1S1


e.

,

7062 0005

Legend<num1> = 0 - 15<num2> = 1 - 12

DetailsThis alarm is generated when a PModule is not capable of running its softwar

Probable Cause

Type

Remedial actionNo remedial action is needed if this is just a temporary condition (for examplewhen the SPM is being reset). If the condition persists, check thePModcomponent’sosiOperationalStatusandfailureCauseattributes for a more specificproblem cause.




tion

ence.

7062 0010

Legend<num1> = 0 - 15<num2> = 1 - 12

DetailsThis alarm is generated when a SPM reboots. It hold some diagnostic informa(in the comment data field) that specifies why the SPM went down.

Several instances of this alarm can be generated depending on how muchinformation needs to be displayed. This information is referred asTrap Datainformation.

Probable Cause

Type

Remedial actionRead theTrap Datainformation to determine why thePModrebooted. If the rebootreason in theTrap Datainformation does not satisfactorily explain the cause of threboot, contact your local Nortel Networks technical support group for assista

Component Severity StatusLp/<num1> Pcusp PModule/<num2> critical message

241-5701-500 4.1S1


eds

7062 0011

Legend<num1> = 0 - 15<num2> = 1 - 12

DetailsThis alarm is generated when aPModis running out of ressource for memory or cpuusage.

Probable Cause

Type

Remedial actionIf this alarm appears with some frequency, then the engineering of this PCU neto be re-examined.




not

ederate

t and

RS

SP

SP

fdby7062are

7062 0012

Legend<x> = 0 - 15

DetailsThis alarm is set when theLp/x Pcusp is in a degraded redundancy condition.

A number of PModules (SPMs) located on the active or standby PCUSP are available for sparing and cannot be used to process GPRS traffic.

A SPM on an active PCUSP is not available for sparing if it cannot be downloadsuccessfully. Note that a single SPM reset on the active PCUSP does not genthis alarm, but sets alarm 7062 0005 instead.

A SPM on a standby PCUSP is not available for sparing when it has been reseis downloading or if it cannot be successfully downloaded.

A PCUSP switchover occurring when this alarm is set may have impacts on GPservices.

This alarm is cleared when theLp/x Pcusp is in full redundancy conditions:

1 PCUSP card is in standby mode

12 SPMs are processing traffic, or ready to process traffic, on the active PCU

12 SPMs are ready to process traffic on the standby PCUSP if the active PCUswitchovers.


TypeEquipment

Remedial actionWhen this alarm isset, no remedial action is needed if this is just a temporarycondition. For example, this happens just after aLp/x Pcusp switchover occurs. Ifthe condition persists, it means that theLp/x Pcusp is in degraded redundancyconditions. In that case, check the content of alarm 7062 0013 to get the list oimpacted PCUSP cards and PModules (SPMs) cards on both active and stanPCUSP. Check also if there are any 7062 0001, 7062 0003, 7062 0004, and 0005 alarms for the related Lp. If any, this indicates that some faulty PModuleslocated on the active PCUSP card. Clear the problem that is preventing theLp/xPcusp from being in full redundancy conditions by replacing the faulty PCUSPcard.

Component Severity StatusLp/<x> Pcusp critical/cleared set/clear

241-5701-500 4.1S1


ules

7062 0013

Legend<x> = 0 - 15

DetailsThis alarm is issued when the status of alarm 7062 0012 is set. It lists the PMod(SPMs) that are not available on both active and standby PCUSP.

If the list of unavailable SPMs evolves at runtime, this alarm is sent again andcontains the full list of unavailable SPMs for thisLp Pcusp component.


TypeEquipment

Remedial actionRefer to the remedial action described for alarm 7062 0012.

Component Severity StatusLp/<x> Pcusp warning message



ee

7062 0020

Legend<num1> = 0 - 15999<num2> = 1 - 256<num3> = 0 - 47<num4> = 0 - 31

DetailsThis signalling link layer alarm is raised when layer 2 has been down. It will bcleared when layer 2 has been reestablished. This alarm is not generated if thPcmLink is not established.

Probable Cause

Type

Remedial actionCheck the status of the link layer on the BSC.

Component Severity StatusPcusa/<num1> Conn/<num2> PcmLink/<num3> Lapd/<num4>

major set/clear

241-5701-500 4.1S1


eds

7062 0021

Legend<num1> = 0 - 15999<num2> = 1 - 256<num3> = 0 - 47<num4> = 0 - 31

DetailsLapd component overload.

The process that is running theLapd component is running out of ressource formemory or cpu usage.

Probable Cause

Type

Remedial actionIf this alarm appears with some frequency, then the engineering of this PCU neto be re-examined.

Component Severity StatusPcusa/<num1> Conn/<num2> PcmLink/<num3> Lapd/<num4>

major message



e

t theg

7062 0023


DetailsThe Bsc connected to thePcmLinkcomponent is not the same as provisioned on thConn component.

Probable Cause

Type

Remedial actionCorrect the connection between the Pcm card of the Pcu and the Bsc. Or correcprovisioning of theConn component on the Passport. Or correct the provisioninon the Bsc side.

Component Severity StatusPcusa/<num1> Conn/<num2> PcmLink/<num3>

major message

241-5701-500 4.1S1


rnald.

ct cant. In

this

7062 0024


DetailsAn internal software error has been detected by thePcmLinkcomponent. This alarmindex is used by the PCU upon detection of various types and severities of inteerrors. Refer to the alarm comment text to get a hint about what has happene

Because the circumstances which caused this event are unexpected, the impavary on a case-by-case basis from no impact at all to possibly a severe impacthe latter case, it may be accompanied by other alarms.

The problem may or may not be reproductible. If the circumstances are known,can greatly help the resolution of the problem.

Probable Cause

Type



indeterminate message



uit

ut, a

ully

.

the

or

TS

7062 0025

Legend<k> = 0 - 15999<l> = 1 - 256<m> = 0 - 47<n> = 0 - 65535 (Cell Location Area Code)<o> = 0 - 65535 (Cell Global Identifier)<p> = a decimal value

DetailsThis alarm is raised when the SGSN is not responding to a BSSGP protocolmessage for this cell instance. The GPRS service is not available for this cellinstance. If NMO1 is activated, this fault induces some heavy impacts on circservices (Mobile Terminated calls failing).

The reset procedure of the signaling BVC has been successfully completed; bPTP procedure related to this cell has failed.

This alarm is cleared when the PTP procedure is initiated again and successfcompleted.


TypeCommunications

Remedial actionThe alarm comment text contains more information on the cause of the failure

If the non acknowledged message is a BVC-RESET, perform a lock/unlock ofrelated cell instance.

If the non acknowledged message is either a BVC-UNBLOCK, a BVC-BLOCK,a BVC-FLOW-CTRL:

1 Deactivate and then reactivate the GPRS service for this cell using Bflag gprsCellActivation

Component Severity StatusPcusa/<k> Conn/<l> PcmLink/<m> CgiCell/<n>, <o>

Pcusa/<k> Conn/<l> PcmLink/<m> Cell/<p>

major set/clear

241-5701-500 4.1S1


ce

the

2 If the problem persists, perform a lock/unlock of the related cell instan

If the remedial action is unsuccessful and NMO1 is activated, then deactivateGPRS service for this cell.



fullyonnuit

fully

eC

then

7062 0027

Legend<num1> = 0 - 15999<num2> = 1 - 256<num3> = 0 - 47<num4> = 0

DetailsThis alarm is raised when the reset of the signaling BVC has not been successcompleted. GPRS service is not available for the related BSC identified by the Cinstance. If NMO1 is activated, this fault induces some heavy impacts on circservices (Mobile Terminated calls failing).

This alarm is cleared when the reset procedure is initiated again and successcompleted.


TypeCommunications

Remedial actionCheck the SGSN status and/or the FR cloud.

If SGSN status is OK, lock/unlock all theFrAtm/xinstances used by the related Nsinstance to force a GbDown/GbUp transition. This should trigger a signalling BVreset procedure. If the remedial action is unsuccessful and NMO1 is activated,deactivate the GPRS service for this BSC.

Component Severity StatusPcusa/<num1> Conn/<num2> PcmLink/<num3> Bvc/<num4>

critical set/clear

241-5701-500 4.1S1


.ce.

s

1C

d, an

l

7062 0028

Legend<num1> = 0 - 15999<num2> = 1 - 256

DetailsThis alarm is raised upon system failure of the Gb underlying network serviceGPRS service is not available for the related BSC identified by the Conn instanIf NMO1 is activated, this fault induces some heavy impacts on circuit service(Mobile Terminated calls failing).

This alarm is cleared upon recovery of the Gb underlying network service.

Probable CauseSubsystem failure

TypeCommunications

Remedial actionCheck Gb physical layer by displaying theFrAtm/x FramerosiState of each BearerChannel used by this Nse. If it is not enabled (busy), check the cabling, thefratmprovisioning, or the adjacent node in the frame relay network. Also display FR Eport statuslp/m e1/n.

Check the frame relay level by displaying theFrAtm/x Lmi osiState. If it is notenabled (busy) or the protocolStatus is not equal tonormalCondition, check theLmiprovisioning on both SGSN and PCUSN sides.

DisplayFrAtm/x Dlci/y Siwf AtmConnstate. If it is not connected, check the DLCIprovisioning. Check that the remote address betweenfratmandPcGtl/x Nse/y Nsvc/z components are consistent.

Check all thePcGtl/x Nse/y Nsvc/zstates for this Nse instance. If no one isunBlocked, find out on which side (PCUSN or SGSN) these Nsvcs have beenblocked, and unblock these NSVCs or unblock the corresponding DLCIs.

If SGSN and FR clouds datafill are consistent, and corresponding status enableNS Reset Procedure can be forced by locking/unlocking correspondingFrAtm/xrelated component instances orlp/x El/yports. If the remedial action is unsuccessfuand NMO1 is activated, then deactivate the GPRS service for this BSC.

Component Severity StatusPcusa/<num1> Conn/<num2> critical set/clear



e is

ded. the

7062 0029


DetailsThis alarm is raised when the PCU has sent a CELL_GPRS_OPEN or aCELL_GPRS_CLOSE message to the BTS and no acknowledgment messagreceived from the BTS. GPRS service is not available for this cell instance. IfNMO1 is activated, this fault induces some heavy impacts on circuit services(Mobile Terminated calls failing). Contact with BTS has been lost.

It is cleared when the BTS acknowledges this message.


TypeCommunications

Remedial actionCheck the BTS status, then lock/unlock the corresponding cell instance if neeIf the remedial action is unsuccessful and NMO1 is activated, then deactivateGPRS service for this cell.



major set/clear

241-5701-500 4.1S1


s

.

7062 0030


DetailsThis alarm is raised when aPcmLink instance cannot be processed. This happenwhen processing resources are lacking on a Pcusp card.

This alarm is cleared when enough processing resources have been retrieved


TypeProcessing

Remedial actionCheck if there are any 7062 0005 alarms for the relatedLp.

If the condition persists, check the relatedPMod’s osiOperationalStatus andfailureCause attributes.


major set/clear



nse

rtingeel.

llY

7062 0031


DetailsThis alarm is related to the CCCH management at the BTS level feature.

It is raised after two consecutive PDCH Assignment procedure failures: no respofrom BTS to PDCH ASSIGN PARAM message or receipt of PDCH ASSIGNPARAM NACK message.

CCCH at BTS level is disabled.


TypeCommunications

Remedial actionCheck hardware and software compatibility (the feature is only supported stafrom v13.3). In case of compatibility problems, you must deactivate the featurmanually at OMC-R level: disable the feature activation flag CcchGprsAtBtsLev

When this alarm is raised, the feature is deactivated at the PCU side while stiactivated at the OMC-R side. To reactivate it at PCU side, trigger a CELL MODIFREQ with the activation flag enabled at the OMC-R level.



major message

241-5701-500 4.1S1


PRS

userand/er

:n

anund

lem.

e a

be

thiseen

ed

ute

7063 0100

Legend

DetailsThisset alarm is issued by a node (specifically, by the DPRS routing systemAutomatic Route Tester on that node) that has detected a problem along its Dpath to a certain RID or MID destination.

This alarm indicates a suspected DPRS routing system problem. As a result, traffic on certain network path(s) may be experiencing excessively long delayor having difficulty routing to certain destination(s). If this situation persists, ustraffic carried over DPRS in the network could be congested/discarded on thereported path(s).

Any of the following DPRS route errors can cause this alarm to be generatedTimeout error : Repeated timeout encountered testing the route to a destinatio

Max Hops Reached: There is an upper limit on how many hops a DPRS packet cgo in a Passport/DPN network before reaching its destination. If a packet is foto have reached this limit, it is normally suspected that there is a routing prob

Loop problem: Based on the path information collected in the returned testingpacket, the DPRS path chosen to reach the destination is in question becausspecific node appears more than once on the path. Normally a routing loop issuspected.

More info about this error can be found underRtg Dpn Artcomponent on the nodethat raised this alarm.

When multiple errors are detected, only the first error will cause this alarm to generated. However, all the detected errors will be recorded underRtg Dpn Artcomponent. A maximum of ten (10) simultaneous error destinations can berecorded and kept track of.

ART keeps re-testing all outstanding error routes regularly. A route error to adestination is considered to be no longer exist if a re-test indicates no error, ordestination has become unreachable. However, there is a waiting period betwtwo successive re-tests (determined by theRtg Dpn Art testIntervalattribute), as aresult, a route error that recovered during this waiting period will NOT be declaras recovered until the next re-test is conducted.

A clearalarm is issued by the node that raised this alarm when all outstanding roerrors are found to be no long exist by ART during its regular re-testing.

Component Severity StatusRtg Dpn Art major/cleard set/clear



ue,ping

ifyised-rtd

d by

ay isel.

d touop-

ture

on-

ues arm

tingyou

-).

Probable CauseapplSubsystemFailCause

TypeprocessingType

Remedial actionThe actions depend on what type of DPRS route error is detected.

Case 1:

If it’s an occasional “timeout” with a short duration (less than a few times the valof Rtg Dpn Art testIntervalattribute value), there’s probably nothing really wrongmight just be a peak of traffic jammed the route. No action is needed except keethis in system log for possible future reference.

Case 2:

If this is a long duration “timeout” error, network operator is recommended to verthe round-trip-delay of the DPRS path between the pair of nodes (the one that rathe alarm and the one to which the error is detected). This is done by issuing Ping command(s) from one node to the other. If the round-trip-delay is withinacceptable limit, handle it the same way as Case 1. This alarm should be cleareitself shortly.

In case the alarm persists and the network operator is sure the round-trip-delnormal, you should collect all relevant on-switch information and contact NortThere could be a defect with this testing feature if this happens.

In case the round-trip-delay is indeed abnormal, the network operator is advisetreat it the same way as a link problem and/or traffic congestion. Normally, yowould verify the links and the round-trip-delay, segment-by-segment and/or hby-hop among the nodes along the path between this pair of nodes.

Case 3:

If this is a “loop” error, your action also depends on the duration of this alarm.

For short duration ones (less than ten times the value of theRtg Dpn Art testIntervalattribute), no action is needed except keeping this in system log for possible fureference.

For those that lasts longer, get onto the node that raised the alarm, check theswitch componentRtg Dpn Art ErrRid/*and/orRtg Dpn Art ErrMid/*.You shouldbe able to see the error path based on which the loop error was detected. IssPing command (without the -rtd or -all options) from the node that raised the alato the node that the error is detected. You should get the path information (lisall the tandem nodes, hop-by-hop). Compare what you get here with the one saw by displayingRtg Dpn Art ErrRid/*and/orRtg Dpn Art ErrMid/*component.

If you observe no abnormality from what you get after issuing the Pingcommand(s), there’s probably nothing wrong. However, collect all relevant onswitch information and contact Nortel at your first convenient time (office hours

241-5701-500 4.1S1


see

icemayitch

iallyngient

t all

There could be a defect with this testing feature.

If you can see no less than 18 hops in the path information, especially when youthis from both sources, please verify if the network traffic is going through okbetween the pair of nodes. If yes, contact Nortel at your first convenient time (offhours). Otherwise, depend on the impact this may cause on your network, youneed to call Nortel as soon as possible. Remember to collect all relevant on-swinformation.

If you can see a node appears more than once in the path information, especwhen you see this from both sources, please verify if the network traffic is goithrough ok between the pair of nodes. If yes, contact Nortel at your first conventime (office hours). Otherwise, depend on the impact this may cause on yournetwork, you may need to call Nortel as soon as possible. Remember to collecrelevant on-switch information.



7064 0200

Component Severity StatusVr/<vrId> Mpls LspGroup/<lsp_group_name>Lsp/<lspId>

<severity> set/clear/message

241-5701-500 4.1S1


n

35)

are

et up

sible

am.

d

as

otk the

theus of

ase

ted

tion

.

Note:Generation of this alarm is controlled on a per-LSP basis byprovisioning. By default, the alarm is not generated; the operator caenable alarm generation by provisioning the desired severity of thealarm.

Legend<vrId> = the name assigned to the Virtual Router (an alphanumeric value)

<lsp_group_name> = the name assigned to the LSP Group instance (1 to 655

<lspId> = the name assigned to the LSP instance (a numeric value)

<severity> = user configurable to critical or major; clear and message severitiesprovided by the system

DetailsIf the status is set, this alarm indicates that a failure has either prevented LSP sor resulted in tear down of an established LSP.

The comment field of the set alarm describes the cause of the LSP failure. Poscauses are listed and explained below.

“Notification message received--LDP status code 0x%X” indicates that whileawaiting the label mapping message, a notification was received from downstreThe status codes are defined in the MPLS LDP IETF standard.

“Withdraw message received” indicates that a withdraw message was receivefrom downstream, tearing down the LSP. The operator should follow the routedownstream to find the culprit node/segment.

“LDP peer down” indicates that the LDP peer session on which the LSP relies wdisabled. There should be an accompanying 7064 0400 alarm.

“Failed to send label request -- no resources” indicates that signalling could nallocate a label between the node and its LDP peer. The operator should checlabel range through the attributes under componentvr pp mplsport ldpif andpossibly extend it.

“Failed to send label request -- no route” indicates that signalling could not sendlabel request downstream to its LDP peer. The operator should check the statthe associatedvr pp mplsport ldpif.

“Release message received,” on interworking LSPs only, indicates that a relemessage was received from upstream. The operator should follow the routeupstream to find the culprit node/segment/LSP.

“LSP TE locked” indicates that the vr mpls lspg lsp te subcomponent, associawith the LSP, was locked by the operator.

A clear alarm is generated to report the successful setup of an LSP on initial creaor on recovery from a failure.

“LSP successfully established” indicates that the LSP was successfully setup



SP.

sd

xtl

Probable CauseOperational condition: the operator has locked the Te subcomponent of the L

Call establishment error: a problem on the LSR or along the path of the LSP ipreventing its setup. Examples include failures under the associated Vr Pp anAtmIf components.

TypeOperator type: used with operational condition cause.

Communications type: used with call establishment error cause.

Remedial actionThe LSP remains in the down state for automatic reattempt of setup on the necycle. Refer to the 241-5701-445Passport 7400, 15000, 20000 Multiprotocol LabeSwitching Guide for recommendations on analyzing LSP failures.

241-5701-500 4.1S1


eric

d

ce

der

t of

on is

rror

7064 0400

Legend<vrId> = The name assigned to the Virtual Router (an alphanumeric value).

<pp_name> = The name assigned to the Protocol Port instance (an alphanumvalue).

<card_x> = The card number that the Ldp Port is running.

<card_y> = The physical port number on card_x that the Ldp Port is associatewith.

<logIfSelf> = The IP logical interface of the IP port under the Pp. It is the instanvalue of the Vr/<vrId> Pp/<pp_name> IpPort LogicalIf/<logIfSelf>.

<logIfPeer> = The IP logical interface port of the peer. This value has beensignalled to this Ldp Port by the peer.

<keep_tmr> = The provisioned value of the Vr/<vrId> Mpls LdpkeepAliveHoldTimer attribute.

<hello_tmr> = The provisioned value of the Vr/<vrId> Mpls Ldp helloTimerattribute.

<self_lblRange> = The provisioned values of the label range for the Ldp Port unthe Vr/<vrId> Pp/<pp_name> MplsPort LdpIf.

<peer_lblRange> = The provisioned values of the label range for the Ldp Porthe peer. This values have been signalled to this Ldp Port by the peer.

DetailsA message alarm is generated, with an unknown severity, when the LDP sessisuccessfully established on the first attempt. The comment area of the alarmprovides the following information:

card/<card_x> port/<port_y> LDP <logIfSelf>=><logIfPeer> : UPkeepAlive=<keep_tmr>s, hello=<hello_tmr>s

If the session fails a set alarm is generated with a critical severity. The possible econditions are:

Component Severity StatusVr/<vrId> Pp/<pp_name> MplsPort LdpIf unknown/critical/

clearedset/clear/message



the

the

n:

ablish.

• UDP hold time is exceeded. The comment area of the alarm providesfollowing information:

card/<card_x> port/<port_y> LDP <logIfSelf>=><logIfPeer> :exceeded UDP hold time, resetting

• TCP hold time is exceeded. The comment area of the alarm providesfollowing information:

card/<card_x> port/<port_y> LDP <logIfSelf>=><logIfPeer> :exceeded TCP hold time, resetting

• The provisioned label ranges between the two peers mismatch. Thecomment area of the alarm provides the following information:

card/<card_x> port/<port_y> LDP <logIfSelf>=><logIfPeer> : labelrange <self_lblRange> no overlap with peer <peer_lblRange>

A clear alarm is generated, with a cleared severity, when the LDP session isrestablished.The comment area of the alarm provides the following informatio

card/<card_x> port/<port_y> LDP <logIfSelf>=><logIfPeer> : UPkeepAlive=<keep_tmr>s, hello=<hello_tmr>s

Probable Cause

Type

Remedial actionFor set critical alarms, the system terminates the session and attempts to reest

241-5701-500 4.1S1


S,ionsentareingnd,ping

7065 0000

Legend<x> = instance identifier of the Signaling Gateway

DetailsThe Mapping Table Full alarm is generated by Signaling Gateway’s RANAP-Pwhen the mapping table storing the context data for ongoing signaling connecthas reached a full threshold. If the mapping table completely fills up, subsequconnection requests from either SCCP or GPRS Mobility Management (GMM)rejected. There are two possible reasons for this. First, the provisioned mapptable size may be insufficient for the network’s demand for connections. A secoand less likely, reason is that stale signaling connections may stay in the maptable because of the loss of disconnect requests from either SCCP or GMM.


TypeProcessing

Remedial actionVerify that the mapping table size is provisioned to an adequate size.

Component Severity Status<Sg/<x> RncIf PsDomain> major message



inCCP,ns are

CCPntil

ns

in and

7066 0000

Legend<x> = instance identifier of the SCCP

DetailsWhen the status isset, all of the provisioned connections are consumed and areuse. This results in the connections exhausted alarm being generated by the Sbecause an SCCP user requested a connection but was denied. The connectiofrom the local SCCP to the remote SCCP. The connection request is failed by Sand the connection is not established. All future connection requests will fail uan adequate number of in-use connections are relinquished.

When the status isclear, a low water mark has been reached for in-use connectioproviding an adequate pool of connections available for use.

Probable CauseAt or near capacity

TypeOperator

Remedial actionWhen the status isset, increase the number of available connections provisionedSCCP or determine why an excessive number of connections are being useddecrease the number of connection requests by SCCP users.


Component Severity StatusSccp/<x> major/cleared message

241-5701-500 4.1S1


7066 0100

Legend<x> = MTP3 instance identifier

<y> = linkset instance identifier

<z> = link instance identifier; z = 0 - 15

DetailsThe signaling link test failed alarm is generated by an MTP3 Link when theSignaling Link Test (SLT) fails. This indicates that the Signaling Link TestController (SLTC) detected a bad link. Once the bad link is detected, it will berestarted.

Probable CauseCall establishment error

TypeCommunications

Remedial actionMonitor the bad link to ensure that the link comes back into service.

Component Severity StatusMtp3/<x> Linkset/<y> Link/<z> major message



lle all

ueible, or

d,

into

7066 0101

Legend<x> = MTP3 instance identifier

<y> = linkset instance identifier

DetailsWhen the status isset, a destination (i.e. remote MTP3) is inaccessible due to alinks in the linkset being inaccessible. The destination is inaccessible becauslinks in the linkset are either inhibited, locked, or disabled.

When the status isclear, a destination (i.e. remote MTP3) becomes accessible dto one or more links in the linkset being accessible. The destination is accessbecause an inhibited link becomes uninhibited, a locked link becomes unlockeda disabled link becomes enabled.


TypeCommunications

Remedial actionWhen the status isset, the destination is inaccessible due to links being inhibitelocked, or disabled. For links inhibited or locked, uninhibit or unlock links asappropriate. Disabled links should be monitored to ensure the links come backservice.


Component Severity StatusMtp3/<x> Linkset/<y> critical/cleared set/clear

241-5701-500 4.1S1


eeical

7066 0200

Legend<x> = Nsta instance identifier

<y> = Brag instance identifier

DetailsThe TDM link failure alarm is generated by MTP2 when an error occurs on thTDM link resulting in the link being taken out of service. The link failure could bdue to an error in the provisioning of the link, such as a bad timeslot, or to a physconnectivity problem.


TypeCommunications

Remedial actionConfirm provisioning is correct for the link. Verify the health of the physicalconnectivity of the link.

Component Severity StatusNsta/<x> Vgs Brag/<y> Mtp2 major message



nk

ofnds.

ical

7066 0300

Legend<x> = Saal-Nni instance identifier

DetailsWhen the status isset, a condition exists on the link to the peer that preventsalignment from completing successfully. As a result, the link will not come intoservice. Alignment failure could be due to insufficient bandwidth to support the lior an error rate on the link that is outside acceptable bounds.

When the status isclear, alignment on the link completes successfully as a resultincreased bandwidth or the error rate on the link comes within acceptable bouAs a result, the link comes into service.


TypeCommunications

Remedial actionWhen the status isset, verify the bandwidth is sufficient to support the link andincrease it if necessary. Verify the health of the physical connectivity (e.g. optlink or interface).


Component Severity StatusSaalNni/<x> major/cleared set/clear

241-5701-500 4.1S1


Nnier

ults

er

7066 0301

Legend<x> = Saal-Nni instance identifier

DetailsThe layer 2 peer disconnect alarm is generated by SaalNni when a peer Saalreleases the link and disconnects. The disconnect occurs as a result of the peSaalNni sending a release indication to the local SaalNni, which ultimately resin the link being taken out of service.


TypeCommunications

Remedial actionDetermine what incompatibility or engineering change has occurred at the peSaalNni to cause it to generate a release indication.

Component Severity StatusSaalNni/<x> major message



nnon

ndeway

he

7067 0000

Legend<x> = Virtual Media Gateway instance identifier

<y> = Media Gateway interface identifier

DetailsWhen the status isset, the Virtual Media Gateway has lost the signaling connectiowith the Media Gateway indicated by failed heartbeat messages. As a result, Aspen messaging to or from the Media Gateway will occur. While the conditiopersists, the Virtual Media Gateway will discard any unsendable messages areject any new calls. Possible causes for the loss of heartbeat is a Media Gatreset or a loss of physical connectivity with the Media Gateway.

When the status isclear, the component has reestablished its connection with tMedia Gateway indicated by the success of heartbeat messages.


TypeCommunications

Remedial actionWhen the status isset, verify the Media Gateway is available and connectivity iscorrect.


Component Severity StatusVmg/<x> MgIf/<y> major/cleared set/clear

241-5701-500 4.1S1


n the ality

thedrk

g

7068 1000

Legend<x> = instance identifier of the SGSN Accounting Server (SAS)

Details

The SAS disk almost full alarm is generated by the SAS when critical usagethresholds are crossed on the SAS hard disk. A minor alarm is generated whedisk usage reaches a level (for example, 70% full) that indicates there may beproblem sending the collected information to the Charging Gateway Functiona(CGF). A critical alarm is generated when the disk usage reaches a level (forexample, 90%) that indicates a danger of running out of disk space, renderingSAS inoperable. Since the disk will fill up if the SAS is unable to offload collectecharging information to the CGF, the likely cause is a problem with the netwopath to the CGF or the CGF itself.


TypeMessage

Remedial actionVerify the health of the network path to the CGF. Verify that the CGF is functioninproperly.

Component Severity StatusSas/<x> minor message



arege

lity

thedrk

g

7068 1001


DetailsThe SAS disk full alarm is generated by the SAS when critical usage thresholdscrossed on the SAS hard disk. A minor alarm is generated when the disk usareaches a level (for example, 70% full) that indicates there may be a problemsending the collected charging information to the Charging Gateway Functiona(CGF). A critical alarm is generated when the disk usage reaches a level (forexample, 90%) that indicates a danger of running out of disk space, renderingSAS inoperable. Since the disk will fill up if the SAS is unable to offload collectecharging information to the CGF, the likely cause is a problem with the netwopath to the CGF or the CGF itself.


TypeMessage

Remedial actionVerify the health of the network path to the CGF. Verify that the CGF is functioninproperly.

Component Severity StatusSas/<x> critical message

241-5701-500 4.1S1


(i.e. isay

7068 1002


DetailsThe SAS disk failure alarm is generated by the SAS when a hard disk failure crash) is detected, rendering the hard disk inaccessible. As a result, the SASunable to save collected charging information or to send the Charging GatewFunctionality (CGF) any collected charging information already saved to disk.


TypeMessage

Remedial actionReplace the disk drive or the entire FP card.

Component Severity StatusSas/<x> major message



d totedto

ry

7068 1003


DetailsThe primary CGF link failure alarm is generated by the SAS when a loss ofcommunication is detected with the primary Charging Gateway Functionality(CGF). The communication link problem is detected by the SAS when a GTPprotocol message is not acknowledged by the CGF or if the CGF fails to respona heartbeat message from the SAS. When a communication problem is detecwith the primary CGF, the SAS will start to send collected charging informationthe secondary CGF.

Probable CauseunderlyingResourceUnavailableCause.

TypeMessage

Remedial actionVerify the health of the network path to the primary CGF. Verify that the primaCGF is functioning properly.

Component Severity StatusSas/<x> warning message

241-5701-500 4.1S1


fity

d tog

7068 1004


DetailsThe secondary CGF link failure alarm is generated by the SAS when a loss ocommunication is detected with the secondary Charging Gateway Functional(CGF). The communication link problem is detected by the SAS when a GTPprotocol message is not acknowledged by the CGF or if the CGF fails to respona heartbeat message from the SAS. If this communication link is lost, all billincapability is lost.


TypeMessage

Remedial actionVerify the health of the network path to the secondary CGF. Verify that thesecondary CGF is functioning properly.

Component Severity StatusSas/<x> major message



ory.

f

7068 1005

Legend<x> = instance identifier of the GSC

DetailsThe alarm is generated by the GSC when it is unable to acquire any more mem

Probable Causememory resources are exhausted.

Typemessage

Remedial actionverify and lower values of the GSC provisioned attributes since the amount omemory needed is derived from them.

Component Severity StatusGsc/<x> major message

241-5701-500 4.1S1


SC

SC

e the

7068 1006


DetailsThe alarm is caused by GMM when the number of attached subscribers on Greaches its provisioned limit on the number of attached subscribers.

Probable CauseThe alarm is caused by GMM when the number of attached subscribers on Greaches its provisioned limit on the number of attached subscribers.

TypeMessage

Remedial actionVerify that the provisioned attribute for the maximum number of attachedsubscribers is sufficient to handle the level of subscriber demand and increasmaximum (which in itself is limited) if necessary.

Component Severity StatusGsc/<x> major message



ory.

m

7068 1008

Legend<x> = instance identifier of the GSD

DetailsThe alarm is generated by the GSD when it is unable to acquire any more mem

Probable CauseMemory resources are exhausted.

TypeMessage

Remedial actionVerify and lower values of the GSD and of its subcomponents’ provisionedattributes for MaxAttachedSubscribers,maxRfc144Entities, maxV42bisEntitiesandv42bisCompressionDirections, since the amount of memory needed is derived frothem.

Component Severity StatusGsd/<x> major message

241-5701-500 4.1S1


has

has

elf

7068 1009


DetailsThe alarm is generated by the GSD when the number of subscribers on GSDreached its limit on the number of attached subscribers.

Probable CauseThe alarm is generated by the GSD when the number of subscribers on GSDreached its limit on the number of attached subscribers.

TypeMessage

Remedial actionVerify that the provisioned attribute for the maximum number of subscribers issufficient to handle the level of demand and increase the maximum (which in itsis limited) if necessary.




n anted

7068 1011

Legend<x> = 1 - 15

DetailsThe mobility management portion of the SGSN received a message a mobile irouting area that has not been provisioned on the SGSN. The alarm is generaevery fifth time this condition is encountered.


TypeprocessingType

Remedial actionProvision thesgsn mcc/x mnc/x lac/x rac/xfor the new routing area as specified inthe alarm text.

Component Severity StatusGsc/<x> minor message

241-5701-500 4.1S1


nt

7068 1012

Legend<x> = 1 - 15

DetailsAs Gprs data calls are made and disconnected, software components calledlogicalLinkEntities are allocated and deallocated. If the number oflogicalLinkEntities reaches 100% capacity of the number of allocatedlogicalLinkEntities, thegsdMaxAllocatedLle alarm will be generated.


TypeprocessingType

Remedial actionVerify that the number of maximum attached subscribers in the Gsd compone(attribute maxAttachedSubscribers) is adequate for the maximum number ofexpected mobile Pdp ContextslLi.




arecard

7068 1014

Legend

DetailsThis is a message alarm for GSC to inform the user that all the initializations done and the GSC application is ready. The alarm is generated every time theor shelf is reset.

Probable Cause

Typeunknown

Remedial actionNo remedial action.

Component Severity StatusGSC clearedSeverity_cmessage

241-5701-500 4.1S1


arecard

7068 1015

Legend

DetailsThis is a message alarm for GSD to inform the user that all the initializations done and the GSD application is ready. The alarm is generated every time theor shelf is reset.

Probable Cause

Typeunknown


Component Severity StatusGSD clearedSeverity_cmessage



recard

7068 1016

Legend

DetailsThis is a message alarm for SAS to inform the user that all the initializations adone and the SAS application is ready. The alarm is generated every time theor shelf is reset.

Probable Cause

Typeunknown


Component Severity StatusSAS clearedSeverity_cmessage

241-5701-500 4.1S1


recard

7068 1017

Legend

DetailsThis is a message alarm for GTL to inform the user that all the initializations adone and the GTL application is ready. The alarm is generated every time theor shelf is reset.

Probable Cause

Typeunknown


Component Severity StatusGTL clearedSeverity_cmessage



SC

7068 1018


DetailsThis is a set alarm for GSC to inform the user that initialization failed and the Gapplication is not ready. This in turn may lead to a card reset.

This alarm replaces the Initialization Done message alarm (7068 1014).

Probable CauseProbable causes include initialization failures due to memory availability,provisioning errors, and connectivity errors.

TypeProcessing

Remedial actionReset the card and ensure that the pre-allocated memory is appropriate withprovisionable parameters.

Component Severity StatusGsc/<x> major set

241-5701-500 4.1S1


D

7068 1019


DetailsThis is a set alarm for GSD to inform the user that initialization failed and the GSapplication is not ready. This in turn may lead to a card reset.

This alarm replaces the Initialization Done message alarm (7068 1015).

Probable CauseProbable causes include initialization errors due to memory availability,provisioning errors, and connectivity errors.

TypeProcessing

Remedial actionReset the card and ensure that the pre-allocated memory is appropriate withprovisionable parameters.

Component Severity StatusGsd/<x> major set



eory

SC

e the

7068 1500

Legend<x> = instance identifier of the USC

DetailsWhen the status isset, the context memory exhausted alarm is generated by thUSC caused by the Context Manager being unable to acquire any more memfrom the Pool Manager.

When the status isclear, sufficient memory resources have been freed and the Uhas available Pool Management capacity.


TypeProcessing

Remedial actionWhen the status isset, verify the USC’s provisioned attributes for the maximumnumber of attached subscribers and maximum number of active sessions sincamount of memory allocated is derived from these provisioned attributes.


Component Severity StatusUsc/<x> major set/clear

241-5701-500 4.1S1


SCbere

er

fd

7068 1501


DetailsWhen the status isset, the max attaches exceeded alarm is generated by the Ucaused by the GPRS Mobility Management (GMM) function receiving a subscriattach request when the USC has reached its limit on the number of allowablattached subscribers.

When the status isclear, a low water mark has been reached for the current numbof subscribers and the USC has available capacity.


TypeGMM Max Attaches Exceeded --- set

Low watermark number of attaches reached --- clear

Remedial actionWhen the status isset, verify the provisioned attribute for the maximum number oattached subscribers is sufficient to handle the level of subscriber demand anincrease the maximum if necessary.





the

able

er

f

7068 1502


DetailsWhen the status isset, the max active sessions exceeded alarm is generated byUSC caused by the Session Management (SM) function receiving a sessionactivation request because the USC has reached its limit on the number of allowactive sessions.

When the status isclear, a low water mark has been reached for the current numbof active sessions and the USC has available capacity.


TypeSM Max active sessions Exceeded --- set

Low water mark number of active sessions reached --- clear

Remedial actionWhen the status isset, verify the provisioned attribute for the maximum number oactive sessions is sufficient to handle the level of demand and increase themaximum if necessary.



241-5701-500 4.1S1


e the

D

om

7068 1503

Legend<x> = instance identifier of the USD

DetailsWhen the status isset, the context memory exhausted alarm is generated by thUSD when the Context Manager is unable to acquire any more memory fromPool Manager.

When the status isclear, sufficient memory resources have been freed and the UShas available Pool Manager capacity.


TypeProcessing

Remedial actionWhen the status isset, verify the USD’s provisioned attributes for the maximumnumber of active sessions since the amount of memory allocated is derived frthis provisioned attribute.


Component Severity StatusUsd/<x> major set/clear



SDit on

er

r,

7068 1504


DetailsWhen the status isset, max active sessions exceeded alarm is generated by the Ubecause it received a session activation request when the USD reached its limthe number of allowable active sessions.

When the status isclear, a low water mark has been reached for the current numbof active sessions and the USD has available capacity.


Type

Remedial actionWhen the status isset, verify that the provisioned attribute for the maximum numbeof active sessions is sufficient to handle the level of demand and, if necessaryincrease the maximum.


Component Severity StatusUsd/<x> major set/clear

241-5701-500 4.1S1


MAP

r of

rAP

ed

7068 1506

Legend<x> = instance identifier of the TCAP

DetailsWhen the status isset, all of the provisioned transactions for the SGSN MAPsubsystem are consumed and are in use. This results in the max SGSN MAPTransactions exceeded alarm being generated by the MAP Stack because a Client, HLR, or VLR requested a MAP dialogue but was denied. No new MAPtransactions will be established by the MAP Stack once the maximum numbeconcurrent transactions is exceeded. All future attempts to establish a MAPdialogue will fail until in-use dialogues are relinquished.

When the status isclear, a low water mark has been reached for in-use MAPdialogues, which provides an adequate pool of dialogues available for use.

Probable CauseResource not available

TypeProcessing

Remedial actionWhen the status isset, verify that the maxTransactionsBySubsystem attribute fothe SGSN subsystem is provisioned to an adequate value. If more than one MStack is being used, verify that MAP Clients are evenly distributed across theavailable MAP Stacks. Some of the alarming MAP Stack’s MAP Clients may neto be redistributed to a different MAP Stack.


Component Severity StatusTcap/<x> MapStack major/cleared set/clear



,

7068 1507


DetailsThe USC or one of its subcomponents failed to initialize or provision properlywhich resulted in the USC’s inability to operate correctly.


Type

Remedial actionReinitialize the USC by resetting the card or replace the FP.

Component Severity StatusUsc/<x> major set

241-5701-500 4.1S1


,

7068 1508


DetailsThe USD or one of its subcomponents failed to initialize or provision properlywhich resulted in the USD’s inability to operate correctly.


Type

Remedial actionReinitialize the USD by resetting the card or replace the FP.

Component Severity StatusUsd/<x> major set



me in

C

nceed.

l

k’s

nsable

r

7068 1509


DetailsWhen the status isset, all of the provisioned transactions for the MSC subsyste(when the MapClient is running in MSC Emulation mode) are consumed and aruse. This results in the max MSC MAP transactions exceeded alarm beinggenerated by the MAP Stack because a TCAP invoke was required for an MSsubsystem, but was denied.

No new invokes will be established by the MAP Stack for the MSC subsystem othe maximum number of concurrent transactions for that subsystem is exceedAll future attempts to establish a TCAP invoke for the MSC subsystem will faiuntil in-use invokes are relinquished.

If more than one MAP Stack is being used, verify that MAP Clients are evenlydistributed across the available MAP Stacks. Some of the alarming MAP StacMAP Clients may need to be redistributed to a different MAP Stack.

When the status isclear, a low water mark has been reached for in-use transactiofor the MSC subsystem, which provides an adequate pool of transactions availfor use.


TypeProcessing

Remedial actionWhen the status isset, verify that the maxTransactionsBySubsystem attribute fothe MSC subsystem is provisioned to an adequate value.


Component Severity StatusTcap/<x> MapClient major/cleared set/clear

241-5701-500 4.1S1


ctionsn was

the tons

r

7068 1510


DetailsWhen the status isset, all of the provisioned TCAP invokes for use by the CAPsubsystem are consumed and are in use. This results in the max CAP transaexceeded alarm being generated by the Tcap Stack because a TCAP transactiorequired for the CAP subsystem, but was denied.

No new TCAP transaction will be established by the TCAP Stack for CAP oncemaximum number of concurrent transactions is exceeded. All future attemptsestablish a TCAP invoke for the CAP subsystem will fail until in-use transactioare relinquished.

When the status isclear, a low water mark has been reached for in-use TCAPinvokes for the CAP subsystem, which provides an adequate pool of invokesavailable for use.


TypeProcessing

Remedial actionWhen the status isset, verify that the maxTransactionsBySubsystem attribute fothe CAP subsystem is provisioned to an adequate value.


Component Severity StatusTcap/<x> major/cleared set/clear



ofbe

entare

to

7068 1511

Legend<x> = instance identifier of the USC or GSC

DetailsWhen the status isset, the number of map dialogues reaches the high water markthe static maximum number of dialogues allowed. Additional map dialogues canestablished until the maximum limit (1024) is reached, at which time the MapClistarts failing requests from the MapClient or MapStack until in-use dialogues relinquished.

When the status isclear, a low water mark has been reached for in-use MAPdialogues, which provides an adequate pool of dialogues available for use.

Probable CauseatOrNearCapacityCause_c

TypeMax MAP Client Dialogues Exceeded Alarm

Remedial actionWhen the status isset, verify whether MapClient has enough memory allocatedhandle the traffic. If not, you can add another USC/GSC card to alleviate thebottleneck.


Component Severity StatusUsc or Gsc/<x> MapClient major set/clear

241-5701-500 4.1S1


lient,

cetoes

for

rifye ofnt

7068 1512


DetailsWhen the status isset, all of the provisioned MAP invokes for use by the SGSNsubsystem are consumed and are in use. This results in the max SGSN MAPinvokes exceeded alarm being generated by the MAP Stack because a MAP CHLR, or VLR requested a MAP dialogue, but was denied.

No new TCAP invokes for SGSN MAP will be established by the MAP Stack onthe maximum number of concurrent invokes is exceeded. All future attempts send a TCAP invokes for a SGSN MAP subsystem will fail until in-use dialoguare relinquished.

When the status isclear, a low water mark has been reached for in-use TCAPinvokes for SGSN MAP, which provides an adequate pool of invokes availableuse.


TypeProcessing

Remedial actionWhen the status isset, verify that the maxInvokesBySubsystem attribute isprovisioned to an adequate value. If more than one MAP Stack is being used, vethat MAP Clients are evenly distributed across the available MAP Stacks. Somthe alarming MAP Stack’s MAP Clients may need to be redistributed to a differeMAP STACK.





nse.y thewas

ncetore

7068 1513


DetailsWhen the status isset, all of the provisioned invokes for the MSC subsystem (whethe MapClient is running in MSC Emulation mode) are consumed and are in uThis results in the max MSC Map invokes exceeded alarm being generated bMAP Stack because a TCAP invoke was required for the MSC subsystem, butdenied.

No new invokes will be established by the MAP Stack for the MSC subsystem othe maximum number of concurrent invokes is exceeded. All future attempts establish a TCAP invoke for the MSC subsystem will fail until in-use invokes arelinquished.

When the status isclear, a low water mark has been reached for in-use TCAPinvokes for the MSC subsystem, which provides an adequate pool of invokesavailable for use.


TypeProcessing

Remedial actionWhen the status isset, verify that the maxInvokesBySubsystem attribute for theMSC subsystem is provisioned to an adequate value.



241-5701-500 4.1S1


s was

Prese

7068 1514


DetailsWhen the status isset, all of the provisioned TCAP invokes for use by the CAPsubsystem are consumed and are in use. This results in the max CAP invokeexceeded alarm being generated by the Tcap Stack because a TCAP invokerequired for the CAP subsystem, but was denied.

No new TCAP invokes will be established for the CAP subsystem by the TCAStack once the maximum number of concurrent invokes is exceeded. All futuattempts to establish a TCAP invoke for the CAP subsystem will fail until in-uinvokes are relinquished.

When the status isclear, a low water mark has been reached for in-use TCAPinvokes for the CAP subsystem, which provides an adequate pool of invokesavailable for use.


TypeProcessing

Remedial actionWhen the status isset, verify that the maxInvokesBySubsystem attribute for theCAP subsystem is provisioned to an adequate value.


Component Severity StatusTcap/<x> major/cleared set/clear



n.theuallyhat

7068 1515


DetailsWhen the status isset, the SGSN subsystem cannot be used and hence all theMapClients trying to register the SGSN subsystem get registration failures.


TypeProcessing

Remedial actionWhen the status isset, there might be an unusual situation like memory corruptioResetting the card might help bring up the MapStack with a successful bind toSGSN subsystem. If the SGSN subsystem is not needed, the operator can manclear the alarm and have the MapStack continue working for the MapClients tregister with the MSC subsystem.


Component Severity StatusTcap/<x> MapStack minor set

241-5701-500 4.1S1


n.the

uallyhat

7068 1516


DetailsWhen the status isset, the MSC subsystem cannot be used and hence all theMapClients trying to register the MSC subsystem get registration failures.


TypeProcessing

Remedial actionWhen the status isset, there might be an unusual situation like memory corruptioResetting the card might help bring up the MapStack with a successful bind toMSC subsystem. If the MSC subsystem is not needed, the operator can manclear the alarm and have the MapStack continue working for the MapClients tregister with the SGSN subsystem.


Component Severity StatusTcap/<x> MapStack minor set



SFs

n.theually

7068 1517


DetailsWhen the status isset, the CAP subsystem cannot be used and hence all the Strying to register the CAP subsystem get registration failures.

Probable CauseSoftware program error

TypeProcessing

Remedial actionWhen the status isset, there might be an unusual situation like memory corruptioResetting the card might help bring up the TcapStack with a successful bind toCAP subsystem. If an SSF is not needed on this Passport, the operator can manclear the alarm and have the TcapStack and MapStack continue working.


Component Severity StatusTcap/<x> minor set

241-5701-500 4.1S1


SCtiond outldP or

7068 1518


DetailsThe SCP communication failure alarm is generated by the USC SSF when the USSF is no longer able to communicate with the specified SCP. The communicafailure is detected by the USC SSF because a cap dialogue with the SCP timeduring each of the provisioned retries. If this communication link is lost, it couindicate a temporary or permanent link failure between the SGSN and the SCindicate that the SCP is down.

Probable CauselocalTransmissionErrorCause_c

TypecommunicationType_c

Remedial actionVerify the health of the network path to the SCP. Verify the SCP is functioningproperly.

Component Severity StatusUsc/<x> Ssf major message



reed byo newer ofgue

dre

7068 1519


DetailsWhen the status isset, all of the provisioned camel dialogues are consumed and ain use. This results in the max camel dialogues exceeded alarm being generatthe USC SSF because a SCP requested a camel dialogue but was denied. Ncamel dialogues will be established by the USC SSF once the maximum numbconcurrent dialogues is exceeded. All future attempts to establish a camel dialowill fail until in-use dialogues are relinquished.

When the status isclear, a low water mark has been reached for in-use cameldialogues, which provides an adequate pool of dialogues available for use.

Probable CauseatOrNearCapacityCause_c

TypequalityOfServiceType_c

Remedial actionWhen the status isset, verify that the maximum number of dialogues is provisioneto an adequate value. If more than one USC is being used, verify that SCPs aevenly distributed across the available USCs.


Component Severity StatusUsc/<x> Ssf major message

241-5701-500 4.1S1


(LP)

(FP)

7070 0100

Legend<x> = 0 - 15

<y> = 0 - 31

DetailsThis alarm is generated when an adjunct processor (AP) of a logical processoris not running.

Probable CauseA software or hardware problem has occurred.

Type

Remedial actionNo remedial action is needed. If the problem persists, the functional processorshould be replaced.

Component Severity StatusLp/<x> Ap/<y> major set



241-5701-500 4.1S1

885

AppendixAlarm causes

This appendix details the possible values for the alarmcause field thatappears in Passport alarms.

ITU-T Recommendation X.733 provides the basis for this appendix.

Table 4Alarm causes

Cause Description

Adapter error Dependent on component issuing the alarm.

Application subsystem A failure in an application subsystem hasoccurred (an application subsystem may includesoftware to support the Session, Presentation,or Application layers).

Bandwidth reduced The available transmission bandwidth hasdecreased.

Call establishment error An error occurred while attempting to establish aconnection.

Communications protocolerror

A communication protocol has been violated.

Communicationsubsystem failure

A failure in a subsystem that supportscommunications over telecommunications links.These may be implemented through leasedtelephone lines, by X.25 networks or in otherways.

(Sheet 1 of 4)


886 Appendix Alarm causes

Configuration orcustomization error

A system or device generation or customizationparameter has been specified incorrectly, or isinconsistent with the actual configuration.

Congestion A system or network component has reached itscapacity or is approaching it.

Corrupt data An error has caused data to be incorrect andthus unreliable.

CPU cycles limit exceeded A central processing unit has issued anunacceptable number of instructions toaccomplish a task.

Dataset or modem error An internal error has occurred on a dataset ormodem.

Degraded signal The quality or reliability of transmitted data hasdecreased.

DTE-DCE interface error A problem in a DTE-DCE interface, whichincludes the interface between the DTE andDCE, any protocol used to communicatebetween the DTE and DCE and informationprovided by the DCE about the circuit.

Equipment malfunction An internal machine error has occurred forwhich no more specific probable cause hasbeen identified.

Excessive vibration Vibratory or seismic limits have been exceeded.

File error The format of a file (or set of files) is incorrectand thus cannot be used reliably in processing.

Framing error An error in the information that delimits the bitgroups within a continuous stream of bits.

Inactive virtual circuit A virtual circuit has become inactive.

Input device error An error has occurred on the input device.

I/O device error An error has occurred on the I/O device.

Table 4 (continued)Alarm causes

Cause Description

(Sheet 2 of 4)

241-5701-500 4.1S1

Appendix Alarm causes 887

LAN error An error has been detected on a local areanetwork.

Local node transmissionerror

An error occurred on a communication channelbetween.

Loss of frame An inability to locate the information that delimitsthe bit grouping within a continuous stream ofbits.

Loss of signal An error condition in which no data is present ona communications circuit or channel.

Material supply exhausted A supply of needed material has beenexhausted.

Multiplexor problem An error has occurred while multiplexingcommunications signals.

Network serverintervention

A network server (for example, for network timesynchronization) has caused the event reportedby the alarm.

Out of memory There is no program-addressable storageavailable.

Output device error An error has occurred on the output device.

Performance degraded Service agreements or service limits are outsideof acceptable limits.

Power problem There is a problem with the power supply for oneor more resources.

Processor problem An internal machine error has occurred on acentral processing unit.

Queue size exceeded The number of items to be processed(configurable or not) has exceeded themaximum allowable.

Receive failure Dependent on component issuing the alarm.

Receiver failure Dependent on component issuing the alarm.


Cause Description

(Sheet 3 of 4)


888 Appendix Alarm causes

Remote nodetransmission error

An error occurred on a communication channelbeyond the adjacent node.

Resource at or nearingcapacity

The usage of a resource is at or nearing themaximum allowable capacity.

Response time excessive The elapsed time between the end of an inquiryand beginning of the answer to that inquiry isoutside of acceptable limits.

Retransmission rateexcessive

The number of repeat transmissions is outsideof acceptable limits.

Software error A software error has occurred for which no morespecific probable cause can be identified.

Software programabnormally terminated

A software program has abnormally terminateddue to some unrecoverable error condition.

Software program error An error has occurred within a software programthat has caused incorrect results.

Storage capacity problem A storage device has very little or no spaceavailable to store additional data.

Threshold crossed. A limit (configurable or not) has been exceeded.

Timing problem A process that requires timed execution and/orcoordination cannot complete, or has completedbut cannot be considered reliable.

Transmit failure Dependent on component issuing the alarm.

Transmitter failure Dependent on component issuing the alarm.

Underlying resourceunavailable

An entity upon which the reporting objectdepends has become unavailable.

Version mismatch There is a conflict in the functionality of versionsof two or more communicating entities whichmay affect any processing involving thoseentities.


Cause Description

(Sheet 4 of 4)

241-5701-500 4.1S1

Passport 6400, 7400, 15000, 20000

Alarms

Release 4.1

Copyright © 2002 Nortel Networks.All Rights Reserved.

NORTEL NETWORKS, the globemark design, the NORTELNETWORKS corporate logo, DPN, DPN-100, and PASSPORT aretrademarks of Nortel Networks. Advanced Peer-to-Peer Networkingand APPN are trademarks of International Business MachinesCorporation. VT100 is a trademark of Digital EquipmentCorporation.

Publication: 241-5701-500Document status: StandardDocument version: 4.1S1Document date: February 2002Printed in Canada

fg

Documents

open systems

osi operational

text interface

osi procedural

state change

alarm display

passport alarm

chapter interpreting