76 8600 50115i 8600 smart routers fault management configuration guide

BSD Berkeley Software Distribution CDC Control and DC Power Card used in 8630 Smart Router and 8660 Smart Router CPU Central Processor Unit CU Control functionality used in 8615 Smart Ro

Trang 1

8600 Smart Routers Fault Management Configuration Guide

76.8600-50115I 12.05.2015

Trang 2

Document Information

Revision History

76.8600-50115I 12.05.2015 SP7.0 updates for the following network elements:

• 8609 Smart Router and 8611 Smart Router FP2.0

• 8615 Smart Router FP1.0

• 8630 Smart Router and 8660 Smart Router FP5.0Interface list updated in1.1.1 Fault Source Grouping.76.8600-50115G 26.05.2014 Updates added for:

• 8602 Smart Router FP1.0

• 8609 Smart Router and 8611 Smart Router FP1.3Clarification on fault severity classification added to1.1.2 FaultSeverity

Trang 3

This manual documents the following network elements:

This manual is protected by U.S and international copyright laws, conventions and treaties Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws Unauthorized reproduction, modification,

distribution, display or other use of this manual may result in criminal and civil penalties.

The specifications and information regarding the products in this manual are subject to change without notice All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,

express or implied Users must take full responsibility for their application of any products.

Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

3

Trang 5

Terms and Abbreviations

ADSL Asymmetric Digital Subscriber Line

ARP Address Resolution Protocol

BMP Broadband Management Protocol A communication protocol which is used between

8600 network elements and 8000 intelligent network manager

BSD Berkeley Software Distribution

CDC Control and DC Power Card (used in 8630 Smart Router and 8660 Smart Router)

CPU Central Processor Unit

CU Control functionality (used in 8615 Smart Router and 8665 Smart Router)DHCP Dynamic Host Configuration Protocol

ELC1 Ethernet Line Card (used in 8630 Smart Router and 8660 Smart Router)elink Internal resources used to receive traffic streams

ELP Ethernet Link Protection

Eq swi Switching unit equipment protection

IFC Interface Module Concentrator is a line card baseboard and it can be equipped with

one or two IFMs There are three variants available: IFC1-A, IFC1-B and IFC2-B(used in 8630 Smart Router and 8660 Smart Router)

IFM Interface Module A specific term of the module which can be placed on the IFC line

card or 8620 Smart Router baseboard and which consists of the physical interfaces(used in 8620 Smart Router, 8630 Smart Router and 8660 Smart Router)

5

Trang 6

IMA Inverse Multiplexing for ATM

Ip iw IP interworkingIRB Integrated Routing and BridgingLACP Link Aggregation Control Protocol

LDP Label Distribution Protocol

Line card The line card in the 8600 system consists of an Ethernet Line Card (ELC1), Interface

Module Concentrator (IFC) and up to two Interface Modules (IFMs) (used in 8630Smart Router and 8660 Smart Router) In 8000 Intelligent Network Manager andCLI referred to as unit

llink Internal resources used to transmit traffic streams

LSA Link-State Advertisement

LU Traffic functionality (used in 8615 Smart Router and 8665 Smart Router)LU1 Line unit used in 8665 Smart Router

MAC Ethernet Media Access Control

MPLS Multiprotocol Label SwitchingMPLS-TP Multiprotocol Label Switching -Transport ProfileMTU Maximum Transfer/Transmission Unit

Node In CLI refers to an NE

OAM Operation, Administration and MaintenanceOSPF Open Shortest Path First

PPP Point-to-Point Protocol

Trang 7

RDI Remote Error Indicator/Indication

RSVP-TE Resource Reservation Protocol - Traffic EngineeringSDH Synchronous Digital Hierarchy

SFP Small Form-Factor PluggableSLP Service Location ProtocolSHDSL Single-Line High-bit-rate Digital Subscriber Line

SNMP Simple Network Management Protocol

SU1 Switch unit used in 8665 Smart Router

TCP Transmission Control ProtocolTIM Trace Identifier MismatchTTSI Trail Termination Source IdentifierUnit In CLI refers to a card

VPLS Virtual Private LAN ServiceVPN Virtual Private Network

VRRP Virtual Router Redundancy Protocol

7

Trang 9

Table of Contents

Table of Contents

About This Manual 10

Objectives 10

Audience 10

8600 Smart Routers Technical Documentation 10

Document Conventions 14

Interface Numbering Conventions 14

Documentation Feedback 14

8600 Smart Routers Discontinued Products 15

1 8600 Network Element Faults 16

1.1 Overview 16

1.1.1 Fault Source Grouping 17

1.1.2 Fault Severity 20

1.1.3 Service Affected Flag 21

1.1.4 Alarm Type 21

1.1.5 LED 21

1.1.6 Fault Status 21

1.1.7 External Alarm Relays 22

1.1.8 System Message Logging 22

1.1.9 References 22

1.2 Configuration Examples 23

1.3 Fault Tables 24

9

Trang 10

About This Manual

About This Manual

This chapter discusses the objectives and intended audience of this manual, 8600 Smart Routers

Fault Management Configuration Guide and consists of the following sections:

This manual provides an overview of the 8600 Smart Routers fault management and instructions

on how to configure it using command line interface (CLI) and ASCII textual commands with arouter's console or remote terminal (Telnet)

Audience

This manual is designed for administration personnel for configuring 8600 Smart Routers functionswith CLI On the other hand, 8000 Intelligent Network Manager provides access to equal

functionality for administration personnel with a graphical user interface

It is assumed that you have a basic understanding of networks and network interfaces of differenttechnologies (SDH, Ethernet)

8600 Smart Routers Technical Documentation

The document numbering scheme consists of the document ID, indicated by numbers, and thedocument revision, indicated by a letter The references in the Related Documentation table beloware generic and include only the document ID To make sure the references point to the latestavailable document versions, please refer to the relevant product document program on the Tellabsand Coriant Portal by navigating towww.portal.tellabs.com> Product Documentation & Software

> Data Networking > 8600 Smart Routers > Technical Documentation

The table below reflects the customer document content planned for SR7.0 GA, and is subject tochange Before General Availability of SR7.0, the configuration guides have the status of draft, andthey do not always describe the full functionality

Trang 11

About This Manual

8600 Smart RoutersATM and TDM Configuration Guide(76.8600-50110)

Provides an overview of 8600 NEs PWE3 applications,including types, Single-Segment and Multi-Segment; PWE3Redundancy; ATM applications, including PWE3 tunnelling,Traffic Management, Fault Management OAM, protection andTDM applications as well as instructions on how to configurethem with CLI

8600 Smart RoutersBoot and Mini-ApplicationsEmbedded Software Release Notes(76.8600-50108)

Provides information related to the boot and mini-applicationssoftware of 8605 Smart Router, 8607 Smart Router, 8609Smart Router, 8611 Smart Router, 8620 Smart Router, 8630Smart Router and 8660 Smart Router as well as the installationinstructions

8600 Smart RoutersCLI Commands Manual(76.8600-50117)

Provides commands available to configure, monitor and maintain

8600 system with CLI

8600 Smart RoutersEmbedded Software Release Notes

8600 Smart Routers SR7.0 Embedded Software Release Notes(76.8670-50177) for the following products:

Provides an overview of 8600 system HW inventory, softwaremanagement, equipment protection 1+1 (CDC and SCM) as well

as instructions on how to configure them with CLI

8600 Smart RoutersEthernet Configuration Guide (76

8600-50133)

Provides an overview of 8600 system Ethernet applications,including interfaces; Ethernet forwarding (MAC Switching,Ethernet PWE3, IRB, VLAN, VPLS); Ethernet OAM; LAG;ELP as well as instructions on how to configure them with CLI

8600 Smart Routers Smart RoutersFault Management ConfigurationGuide (76.8600-50115)

Provides an overview of 8600 system fault management,including fault source, types and status as well as instructions onhow to configure it with CLI

8600 Smart RoutersFrame Relay Configuration Guide(76.8600-50120)

Provides an overview of 8600 system Frame Relay applications,including interfaces; Performance Monitoring; protection; TrafficManagement as well as instructions on how to configure themwith CLI

8600 Smart RoutersHardware Installation Guide(76.8600-40039)

Provides guidance on mechanical installation, cooling,grounding, powering, cabling, maintenance, commissioning andESW downloading

11

Trang 12

About This Manual

8600 Smart RoutersInterface Configuration Guides The Interface Configuration Guides provides an overview of the8600 NEs interface functions, including NE supported interface

types and equipping; interface features; configuration options andoperating modes; fault management; performance monitoring;interface configuration layers and port protocols as well asinstructions on how to configure them with CLI The followinginterface configuration guides are available:

• 8600 Smart Routers Network Interfaces ConfigurationGuide (76.8600-50161) (for 8602 Smart Router, 8615 SmartRouter and 8665 Smart Router)

• 8609 Smart Router and 8611 Smart Router FP7.0 InterfaceConfiguration Guide (76.8670-50179)

• 8600 Smart Routers FP7.0 Interface Configuration Guide(76.8670-50180) (for 8630 Smart Router and 8660 SmartRouter)

8600 Smart Routers

IP Forwarding and TrafficManagement Configuration Guide(76.8600-50122)

Provides an overview of 8600 NEs IP, forwarding and trafficmanagement functionality, including: IP addressing; IP hosting(ARP, DHCP); IP routing (static); ACL; Differentiated Services(Policing, Queue Management, Shaping) as well as instructions

on how to configure them with CLI

8600 Smart RoutersManagement CommunicationsConfiguration Guide

(76.8600-50125)

Provides an overview of 8600 system managementcommunications functions, including communication protocols:BMP; FTP; RADIUS; SNMP; SSH; TELNET as well asinstructions for configuring them with CLI

8600 Smart RoutersMobile Optimization ConfigurationGuide (76.8600-50100)

Provides an overview of 8600 system Mobile Optimizationapplications as well as instructions on how to configure themwith CLI

8600 Smart RoutersMPLS Applications ConfigurationGuide (76.8600-50123)

Provides an overview of 8600 NEs MPLS applications (includingFRR (one-to-one and facility backup); LDP; protection andTraffic Engineering), MPLS-TP applications (including OAM,linear protection), S-MPLS applications as well as instructions

on how to configure them with CLI

8600 Smart RoutersPerformance Counters ReferenceGuide (76.8600-50143)

Provides an overview of 8600 system supported performancecounters

Trang 13

About This Manual

8600 Smart RoutersReference Manuals The reference manuals describe the 8600 network elementfeatures including:

• NE enclosure, baseboard, power supply modules, andinterfaces in 8602 Smart Router FP7.0 Reference Manual(76.8670-40130)

• NE enclosure, baseboard, power supply modules, interfacesand physical LM types in 8609 Smart Router FP7.0 Refer-ence Manual

• NE enclosure, baseboard, power supply modules, SCMs, HMand LM types in 8611 Smart Router FP7.0 Reference Manual

• NE enclosure, baseboard, power supply modules, and terfaces in 8615 Smart Router FP7.0 Reference Manual(76.8670-40132)

in-• NE subrack, fan modules, CDCs, line cards and IFMs in 8630Smart Router FP7.0 Reference Manual

• NE subrack, fan modules, CDCs, line cards and IFMs in 8660Smart Router FP7.0 Reference Manual

• NE subrack, fan modules, line unit and switch unit in 8665Smart Router FP7.0 Reference Manual (76.8670-40128)

8600 Smart RoutersRouting Protocols ConfigurationGuide (76.8600-50121)

Provides an overview of 8600 NEs routing protocols, includingBFD; BGP; BGP MP; ECMP; IS-IS; OSPF and VRRP as well asinstructions on how to configure them with CLI

8600 Smart RoutersScalability Reference Manual(76.8600-50160)

Provide a summary of tested scalability limits of the 8600 SmartRouters

8600 Smart RoutersSNMP MIB Support(76.8600-50116)

Describes SNMP MIB support by the 8600 NEs and providesinformation on the supported objects and traps For furtherinformation on SNMP MIBs, see the related RFCs

8600 Smart RoutersStatistic Counters Reference Guide(76.8600-50142)

Provides an overview of 8600 system supported statistic counters

8600 Smart RoutersSynchronization ConfigurationGuide (76.8600-50114)

Provides an overview of 8600 NEs synchronization functionality,including physical layer Frequency Synchronization (SEC, EEC);PTP Frequency Synchronization; Phase-Time Synchronization(L2 and L3 applications) as well as instructions on how toconfigure them with CLI

8600 Smart RoutersTest and Measurement ConfigurationGuide (76.8600-50124)

Provides an overview of 8600 NEs measurement and connectivityverification tools, including Ethernet loopback; IP ping andtraceroute; MAC swap loopback; MPLS ping and traceroute;PLT; PWE3 loopback; VCCV (BFD, LSP ping) as well asinstructions on how to configure them with CLI

8600 Smart RoutersVPNs Configuration Guide(76.8600-50128)

Provides an overview of 8600 system virtual private network(VPN) layer 3 applications as well as instructions on how toconfigure them with CLI

8000 Intelligent Network ManagerOnline Help Provides instructions on how different operations are performedwith the 8000 Intelligent Network Manager Describes also

different parameters and controls of the 8000 Intelligent NetworkManager dialogs and windows

Note that the Online Help is not available on the Portal but it isincorporated in the 8000 Intelligent Network Manager

13

Trang 14

About This Manual

Document Conventions

This is a note symbol It emphasizes or supplements information in the document.

This is a caution symbol It indicates that damage to equipment is possible if the instructions are not followed.

This is a warning symbol It indicates that bodily injury is possible if the instructions are not followed.

Interface Numbering Conventions

To be able to follow more easily the feature descriptions and configuration examples given in this

document, see also the 8600 system interface numbering and related figures described in 8600

Smart Routers CLI Commands Manual.

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: fi-documentation@tellabs.com

Trang 15

8600 Smart Routers Discontinued Products

8600 Smart Routers Discontinued Products

8600 Smart Routers Manufacture Discontinued (MD) notifications are available on the Tellabsand Coriant Portal,www.portal.tellabs.com > Product Documentation & Software > Data Networking > [8600 Smart Router product name] > Product Notifications.

15

Trang 16

1 8600 Network Element Faults

1 8600 Network Element Faults

1.1 Overview

The figure below shows the fault management processing in a network element (NE)

Fig 1 Generic Fault Management Processing in 8600 NE

The network element management model can be presented as Managed Object Classes (MOC),Instances and their attribute values with related operations Logically the fault and event information

is able to map to the management model

In CLI faults are mapped to fault groups and inside the groups to specific sources.

The CLI fault management is based on query commands and logged fault and event information

In an NE the fault information is constructed from a fault description, source, severity, type andfault status

Trang 17

1.1.1 Fault Source Grouping

Faults are mapped to the card slot (only in 8630 Smart Router, 8660 Smart Router and 8665 SmartRouter), fault groups and inside groups to specific sources

Here are some examples of the CLI fault groups/sources:

NODE

• NodeHW-INVENTORY

• Unit

• IF Module <slot>/<module>/*

• Timing Module Primary

• Timing Module Backup

• Cooling Fan <FAN number>

• IF Conn Module <slot>/<module>/<interface>

• ATM so <if id>

• ATM VP so <if id>

• ATM VC so <if id>

17

Trang 18

• ATM AAL5 so <if id>

The table below shows examples of the names of the interfaces

• Ext Input <Input line number>

• <user given source if user definable fault>

TCP

• TcpICMP

• IcmpARP

• fe <slot>/<module>/<interface>.<vlanId>

BGP

• Bgp <AS number>

• Neighbor <neighbor address>

• Neighbor <neighbor address> Vrf <vrf name>

• Neighbor <neighbor address> ipv4 unicast

Trang 19

• Neighbor <neighbor address> ipv4 multicast

• Neighbor <neighbor address> vpnv4 unicastOSPF

• fe <slot>/<module>/<interface>.<vlanId>

• Ospf <processid>

RSVP-TE

• Primary <tunnel name>

• Secondary <tunnel name>

• Unit Prot <group name>

• Unit Prot <group name> Primary <slot>

• Unit Prot <group name> Backup <slot>

• IF Prot <group name>

• IF Prot <group name> Primary

• IF Prot <group name> Backup

• LSP Prot <group name> Primary

• LSP Prot <group name> BackupNTP

• Ntp

19

Trang 20

• Node

• Clock Selector

• Fallback List <slot>/<module>/<interface>

• Sync Input <slot>/<module>/<interface>

• Sync Output <slot>/<module>/<interface>

Trang 21

Telecordia GR-474 has only thee severity levels for alarms (minor, major,critical) ITU-T modelhas more severity levels and the mapping cannot be 1:1 ITU-T warning and minor alarms can beconsidered to be GR-474 minor alarms if mapping is needed

1.1.3 Service Affected Flag

Some faults are “service affected”, that is they break traffic or have major impact on service quality

Each fault has a predefined alarm type in one of the following categories:

• com = communication alarm type

• qos = quality of service alarm type

• pro = processing error alarm type

• equ = equipment alarm

• env = environmental alarm

• int = integrity violation

• ope = operational violation

• phy = physical violation

• sec = security service or mechanism violation

A fault might light a card state and/or interface state LED The possible consequents are:

• No led

• Yellow led (error detected but fault cause not in this card or NE)

• Red led (error detected in this card)

In 8630 Smart Router and 8660 Smart Router, also the NE state LEDs in CDC might be lit, seechapter1.1.2 Fault Severity

1.1.6 Fault Status

The fault status (or fault state) is one of the following:

• On (fault is active)

• Off (fault is not active)

• Delta; for some faults, no specific on and off time can be defined This describes some event.After a delta event, the fault state is off

21

Trang 22

1.1.7 External Alarm Relays

8630 Smart Router and 8660 Smart Router have 4 fixed and 2 programmable external output relaysand 8 (per CDC) external input relays

The external line status can be:

• Open - not connected to GND (ground)

• Closed - connected to GND (ground)The fixed external outputs are:

• If Critical output is closed, the Critical NE alarm is ON

• If Major output is closed, the Major NE alarm is ON

• If Minor/Warning output is closed, the Minor/Warning NE alarm is ON

• If power voltage output is on, power voltage (+48 V battery in CDC) is OK

The first three outputs act like NE state alarm LEDs

The programmable output line status and non-volatile behavior can be set by the user

Each of the external input lines can be associated to the user-defined fault or pre-defined faults

8605 Smart Router, 8607 Smart Router, 8609 Smart Router, 8611 Smart Router and 8615 SmartRouter have one fixed and one programmable external output relays and 4 external input relays.The fixed external outputs are:

• If output is closed, the Critical NE alarm is ON

The programmable output line status and non-volatile behavior can be set by the user

Each of the external input lines can be associated to the user-defined fault or pre-defined faults

1.1.8 System Message Logging

Faults and other events cause corresponding human readable system messages The messages can

be stored into:

• CLI console (optional)

• Logging server using syslog protocol [RFC3164] (optional)

1.1.9 References

Trang 23

1.2 Configuration Examples

Step 1 Show all currently active faults in the NE

Step 2 Show the fault history of card 14 (fault history is card-specific)

Step 3 You can filter active and history faults e.g by card, fault group, severity, time, etc

Step 4 You can also use the output filter; in this example only the faults related to interface ge8/0/1 are

shown

router# show faults history slot 8 | block "ge8/0/1"

Step 5 Activate the system message logging in the CLI terminal

Step 6 Define the lowest event severity that will be logged (events with lower severity will not be shown)

Step 7 Define the address for the syslog server and the lowest event severity to be sent to the server

Step 8 Enable the syslog feature

23

Trang 24

1.3 Fault Tables

In the following tables there are presented possible faults that can be emitted by the 8600 products.The faults are categorized to several groups to highlight related faults

The Fault/Spt column identifies the fault name and specific problem type (ID of the fault) as

hexadecimal and decimal number

The Fault Type column specifies the fault type The value can be:

• Communication alarm This fault type is used to report when the object detects a communicationserror

• Environmental alarm This fault type is used to report a problem in the environment

• Equipment alarm This fault type is used to report a failure in the equipment

• Integrity violation This fault is used to report that a potential interruption in the information flowhas occurred in a way that information may have been illegally modified, inserted or deleted

• Operational violation This fault is used to report that the provision of the requested service wasnot possible due to the unavailability, malfunction or incorrect invocation of the service

• Physical violation This fault is used to report that a physical resource has been violated in a waythat indicates a potential security attack

• Processing error alarm This fault type is used to report an internal processing failure

• Quality of service alarm This fault type is used to report a failure in the quality of service

• Security service or mechanism violation This fault type is used to report that a security attackhas been detected by a security service or mechanism

• ANY Any of the above Depends on the user definition

The Severity, Serv Aff, Led column describes the severity of the fault, whether the data service

is affected or not, and the unit/IF LED color

• Severity can be:

• Critical The fault is preventing some service from working

• Major The fault lowers the quality of the service but does not prevent it

• Minor The fault is minor or consequence of a fault emitted in somewhere else, e.g AIS

• Warning The fault is not actually a fault but a warning of something, e.g equipment loop

• ANY Any of the above Depends on the user definition

• Serv Aff can be:

• Service affecting Data service is affected when the fault is on

• - (dash) Data service is not affected when the fault is on

• Led can be:

• Red Red led is lit

• Yellow Yellow led is lit

• None No led is lit

Trang 25

The Description column describes the fault.

The Resource Associated ([8660,8630 CDC1 / CDC2 / IFC1 / IFC2 / ELC1] / 8620 / 8602 / 8605

/ 8607 / 8609 / 8611 / 8615 / [8665 vCU1 / LU1 / SU1]) column identifies the resource capable of

emitting the fault One fault can be associated to one or more resources In parenthesis there areFeature Pack (FP) numbers indicating the first release the resource can emit the fault, separated byslashes (/) Dash (-) means that the product does not support the fault

• The first FP number relates to 8630 Smart Router and 8660 Smart Router

• The second FP number relates to 8620 Smart Router

• The third FP number relates to 8602 Smart Router

• The fourth FP number relates to 8605 Smart Router

• The fifth FP number relates to 8607 Smart Router

• The sixth FP number relates to 8609 Smart Router

• The seventh FP number relates to 8611 Smart Router

• The eighth FP number relates to 8615 Smart Router

• The ninth FP number relates to 8665 Smart Router

25

Trang 26

Interface Synchronization Specific Faults

Aff, Led Description Resource Associated ([8660,8630 CDC1 / CDC2 /

IFC1 / IFC2 / ELC1] / 8620 / 8602 / 8605 / 8607 / 8609 / 8611 / 8615 / [8665 vCU / LU1 / SU1])

1588 loss announce0x16000D (hex)

sync1588SlaveMasterEntry(FP [-/4.1/-/-/-]

Warning,-,Yellow

The clock suffers low packet rate Either Mastersends too few packets or excessive packet loss innetwork

sync1588SlaveMasterEntry(FP [-/4.1/-/-/-]

/-/1.0/1.4/1.1/1.0/1.1/1.0/

[-/-/-])

1588 low quality0x160009 (hex)

1441806 (dec)

Quality of servicealarm

Warning,-,Yellow

Monitored IEEE 1588 Precision ClockSynchronization Protocol clock crosses referencemask

sync1588ClockMonitoring (FP[-/-/-/-/-] /-/1.0/1.5/-/1.0/1.1/-/

Red

The 1588 Master is not receiving any proper clock

as input Master do not sent any 1588 messages

to Slave

sync1588Master (FP[-/4.1/-/-/-] /-/1.0/-/-/1.2/-/1.0/

[-/-/-])

Excessive frequencyoffset

0x160001 (hex)

1441793 (dec)

Minor,-,Yellow

Frequency of the clock is out of PLL lockingrange

syncFallbackListEntry(FP [1.0/4.1/-/-/-]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[7.0/-/-])syncScoFallbackListEntry(FP [2.5 GA/-/-/-/-] /2.5GA/-/-/-/-/-/-/ [-/-/-])

Trang 27

Excessive jitter0x160008 (hex)

used0x160002 (hex)

1441794 (dec)

Warning,-,Yellow

The 2nd highest priority clock in the fallback list

is currently used as reference for node clock

syncNeClockSelector(FP [1.0/4.1/-/-/-]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[7.0/-/-])syncScoClockSelector (FP[2.5/-/-/-/-] /2.5/-/-/-/-/-/-/

[-/-/-])Fallback list 3rd priority

used0x160003 (hex)

1441795 (dec)

Quality of service

Yellow

The 3rd highest priority clock in the fallback list

is currently used as reference for node clock syncNeClockSelector(FP [1.0/4.1/-/-/-]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/-/-])Fallback list 4th priority

used0x160004 (hex)

1441796 (dec)

Warning,-,Yellow

The 4th highest priority clock in the fallback list iscurrently used as reference for node clock

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/-/-])Fallback list 5th priority

used0x160005 (hex)

Trang 28

Forced clock selection0x160006 (hex)

[-/-/-])Gnss accuracy degraded

0x160011 (hex)

1441809 (dec)

Major,Service affecting,Yellow

The time accuracy achieved by the GNSS receiver

is insufficient (eg due to poor satellite reception

Red

The clock selection process is not receiving anyproper clock signal (due to empty fallback list orall clocks in fallback list are failed) Thereforeholdover clock is used

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/-/-])Pps protocol failure

0x16000F (hex)

1441807 (dec)

Major,-,Yellow

The protocol in PPS interface is not workingproperly

syncPpsClockInput (FP[-/4.1/-/-/-] /-/-/-/-/1.2/-/1.0/

Trang 29

IP Basic Specific Faults

Configuration locked0x82207 (hex)

532999 (dec)

Processing erroralarm Critical,Service affecting,

Red

IP configurations are locked i.e they are notupdated to flash This may be because someinternal IP services (eg ISIS, BGP, OSPF etc)are no more available or because errors wereencountered when configuration was read fromthe flash Recovery may need reboot, switching toother software or use of debug command In lattercase Coriant representative should be contacted

Associated ACL contains unsupported actions

ELC1 does not support policer action ipInterfaceAccessListStat(FP [-/-/-/-/4.1] /-/-/-/-/-/-/1.0/

[-/7.0/-])Track object down

0x80002 (hex)

524290 (dec)

Communicationsalarm

Warning,Service affecting,None

/3.1/-/-/-/-/-/1.0/ [7.0/-/-])

Vrrp advertisementconflict

0x80003 (hex)

524291 (dec)

Communicationsalarm Major,Service affecting,

None

VRRP group has conflicting advertisementintervals This may lead to wrong mastershiptransition

ipVrrp (FP [-/-/-/3.1/4.0]

/-/-/-/-/-/-/1.0/ [-/7.0/-])

Vrrp mastership transition0x80001 (hex)

524289 (dec)

Communicationsalarm

Minor,Service affecting,None

Delta fault to indicate mastership transition fromone node to an another node This may disrupttransmission for a short period

Trang 30

IP Hosting Specific Faults

Arp dynamic request forpermanent entry0x81001 (hex)

528385 (dec)

Security service

or mechanismviolation

Warning,-,None

Dynamic ARP (request from other node or replywithout request) tries to modify static ARP entry

Possible security attack

ipArpInterface (FP[1.0/-/1.0/3.0/4.0]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/7.0/-])Arp ip address duplicate

with me0x81002 (hex)

528386 (dec)

Security service

Major,Service affecting,None

Dynamic ARP (request from other node or replywithout request) uses IP address configured to thisnode Possible security attack

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/7.0/-])Arp mac changing for ip

address0x81003 (hex)

528387 (dec)

Security service

Warning,-,None

Dynamic ARP (reply without request) tries tochange MAC address for IP address in ARP table ipArpInterface (FP[1.0/-/1.0/3.0/4.0]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/7.0/-])Arp reply interface

conflict0x81004 (hex)

528388 (dec)

Security service

Warning,-,None

Dynamic ARP reply received from unexpectedinterface Possible security attack

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[-/7.0/-])Dhcp address conflict

0x81009 (hex)

528393 (dec)

Communicationsalarm

Major,Service affecting,Red

IP address received via DHCP protocol do notmatch with expected one

ipDhcpClientInterface(FP [-/-/2.7/3.0/4.0]

/2.7/1.0/1.2/1.0A/1.0/1.1/1.0/

[-/-/-])Dhcp autoconfiguration

scan0x8100C (hex)

528396 (dec)

Equipment alarm Warning,

-,None

Router autoconfiguration is scanning to findDHCP server for IP address

ipDhcpClient (FP [-/-/-/-/-]

/-/1.0/1.6/-/1.2/1.2/-/ [-/-/-])

Dhcp invalid address0x8100B (hex)

528395 (dec)

Communicationsalarm

Critical,Service affecting,Red

IP address received via DHCP protocol cannot betaken into use due to it conflicts with interface IPaddress rules

ipDhcpClientInterface (FP[-/-/-/-/-] /-/1.0/1.6/-/1.2/1.2/-/

[-/-/-])Dhcp no address

0x8100A (hex)

Communicationsalarm

Critical,Service affecting,

IP address is not received from DHCP serverwithin expected time

ipDhcpClientInterface (FP[-/-/-/-/-] /-/1.0/1.6/-/1.2/1.2/-/

Trang 31

Icmp excessive nbr ofecho requests0x81005 (hex)

528389 (dec)

Security service

Warning,-,None

Excessive number of ICMP Echo Requests (mostlikely ping) Possible security attack ipIcmpV4 (FP [1.0/4.1/-/-/-]/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[7.0/-/-])

Icmp excessive nbr of sentunreachable destinations0x81006 (hex)

528390 (dec)

Security service

Warning,-,None

Excessive number of Unreachable Destinationssent Possible security attack ipIcmpV4 (FP [1.0/4.1/-/-/-]/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[7.0/-/-])

Icmp excessive nbr oftimestamp requests0x81007 (hex)

528391 (dec)

Security service

Warning,-,None

Excessive number of ICMP Timestamp Requests ipIcmpV4 (FP [1.0/4.1/-/-/-]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[7.0/-/-])

Tcp excessive nbr of rst onclosed connection0x81008 (hex)

528392 (dec)

Security service

Warning,-,None

Excessive number of Reset (RST) messages onclosed TCP connection Possible security attack

Trang 32

IP Routing BGP Specific Faults

Bgp route limit exceeded0x82206 (hex)

532998 (dec)

Communicationsalarm Critical,Service affecting,

None

Maximum number of BGP routes reached ipBgp (FP [1.0/4.1/-/-/-]

/1.0/1.0/1.0/1.1/1.0/1.1/1.0/

[7.0/-/-])Bgp route limit threshold

crossed0x82205 (hex)

532997 (dec)

Communicationsalarm

Warning,-,None

Warning level of number of BGP routes reached ipBgp (FP [1.0/4.1/-/-/-]

Trang 33

IP Routing OSPF Specific Faults

Ospf external lsa databaseoverflow

0x82201 (hex)

532993 (dec)

None

External Link State Advertisments (LSA) databaseoverflow Too much external routes Someexternal routes ignored

Critical,Service affecting,None

Neighbor MTU size is different than in thisinterface Ospf not started

ipOspfInterface(FP [-/-/1.0/3.0/4.0]

Trang 34

Layer 2 Tunneling Specific Faults

Psn tunnel not found0x1B0003 (hex)

1769475 (dec)

1769476 (dec)

Equipment alarm Major,

Service affecting,None

No pseudowires of the PW redundancy are able toparticipate in redundancy All PWs are down l2tPwe3Circuit (FP[4.0/4.1/-/-/-] /4.0/-/-/-/-/-/-/

[-/-/-])

Rx circuit down0x1B0001 (hex)

1769473 (dec)

Communicationsalarm

Circuit is down in receive direction The reasonmay be that the LDP signalling is not successfullyexecuted

l2tPwe3Circuit(FP [1.0/4.1/-/-/-]

/1.0/1.0/1.0/1.0A/1.0/1.1/1.0/

[7.0/-/-])

Tx circuit down0x1B0002 (hex)

1769474 (dec)

Communicationsalarm

Circuit is down in transmit direction The reasonmay be that the LDP signalling is not successfullyexecuted

l2tPwe3Circuit(FP [1.0/4.1/-/-/-]

Trang 35

Ldp session down0xB0005 (hex)

720901 (dec)

0xB0010 (hex)

720912 (dec)

None

No operational session for LDP targeted peer

Fault is raised when configuration is present fortargeted peer that does not have correspondingLDP session that is either in operational state

or in graceful restart Correlation from targetedpeers is based on adjacencies, and their mapping

to targeted peer (witch is preferentially troughtransport address and secondarily trough hellosource address, but not both at same time forsame adjacency Configuring two targeted peersfor same node will likely report fault) Followingsuppression filters are used to avoid false positivesduring graceful restart and due to dynamic nature

mplsLdpTargetedPeerReport(FP [4.0/4.1/-/-/-]

[-/-/-])Oam loss of connectivity

Trail Termination Source Identifier mismatch due

to unexpected Ttsi value observed in incoming

CV OAM packets (cTtsi)

mplsOamLspSink (FP[2.8/4.1/-/-/-] /2.8/-/-/-/-/-/-/

Trang 36

Oam rx ttsi mismerge0xB0004 (hex)

0xB0008 (hex)

720904 (dec)

Communicationsalarm

Major,-,None

Some part of primary LSP uses detour or bypass mplsRsvpTunnelPrimarySrc

(FP [2.11/4.1/-/-/-]

/2.11/1.0/1.4/1.1/1.0/1.1/-/

[-/-/-])Primary lsp not fully

protected0xB0007 (hex)

720903 (dec)

Communicationsalarm

Warning,-,None

At least one hop is not protected or link protection

is used when node protection was desired

mplsRsvpTunnelPrimarySrc(FP [2.11/4.1/-/-/-]

/2.11/1.0/1.4/1.1/1.0/1.1/1.0/

[7.0/-/-])Rsvp neighbor down

protected0xB000A (hex)

720906 (dec)

Communications

None

At least one hop is not protected or link protection

is used when node protection was desired mplsRsvpTunnelSecondarySrc(FP [2.11/4.1/-/-/-]

/2.11/1.0/1.4/1.1/1.0/1.1/1.0/

[7.0/-/-])

Tp loss of continuity0xB000B (hex)

720907 (dec)

None

The local MEP has not received CC-V OAMpacket(s) from the source MEP within expectedinterval

mplsTpTunnel (FP[4.1/4.1/-/-/-] /-/-/-/-/1.2/1.2/-/

[-/-/-])

Tp misconnection0xB000D (hex)

720909 (dec)

Communicationsalarm

The local MEP has received CC-V OAM packet(s)with an unexpected globally unique source MEPidentifier (globalId+nodeId+tunnelId+lspId) orwith an unexpected encapsulation

mplsTpTunnel (FP[4.1/4.1/-/-/-] /-/-/-/-/1.2/1.2/-/

Trang 37

Tp remote defect indicator0xB000C (hex)

720908 (dec)

Communicationsalarm Major,Service affecting,

None

The remote defect indication is received fromthe source MEP to indicate that it has detected asignal fail condition

mplsTpTunnel (FP[4.1/4.1/-/-/-] /-/-/-/-/1.2/1.2/-/

[-/-/-])

Tp tunnel down0xB000E (hex)

720910 (dec)

Communicationsalarm

The tunnel is down i.e not operational mplsTpTunnel (FP

Trang 38

Node Equipment Management Specific Faults

Application sw init failed0x4000E (hex)

262158 (dec)

Processing erroralarm Critical,Service affecting,

Red

Application software initialization failed and it isnot working properly Most probably this ESWversion is not reliable and should be changed

eqmInventoryUnitReport(FP [2.7/4.1/2.7/3.0/4.0]

Stacking cable present but stacked system notconfigured eqmInventoryStackingCable(FP [-/-/-/-/-] /-/-/-/-/-/-/7.0/

[-/-/-])

Ch stacking cable remotemember not detected0x40027 (hex)

262183 (dec)

Communicationsalarm

Critical,Service affecting,Red

Remote member chassis is not detected visstacking cable

eqmInventoryStackingCable(FP [-/-/-/-/-] /-/-/-/-/-/-/7.0/

The expected cooling FAN module is differentfrom the one physically present and it does notproduce enough cooling The ELC1 units requiremore powerful FANs Please, upgrade coolingFAN module

eqmModuleIdentification (FP[4.0/4.1/-/-/-] /-/-/-/-/-/-/-/

[7.0/-/-])

Conflicting module0x40004 (hex)

262148 (dec)

Equipment alarm Critical,

Service affecting,Red

The activated module is different from the onephysically present

cation (FP [-/-/3.0/3.0/4.0]

eqmIfConnModuleIdentifi-/3.0/1.0/-/1.0A/1.0/1.1/1.0/

[-/7.0/-])eqmOptionalModule(FP [1.0/4.1/1.0/3.0/-]

/1.0/-/-/1.0A/1.0/1.1/1.0/

[7.0/-/-])Expected module not

activated0x40005 (hex)

262149 (dec)

-,Yellow

New expected module configured, but notactivated (typically requires resetting the unit)

eqmOptionalModule(FP [1.0/4.1/1.0/3.0/-]

/1.0/-/-/1.0A/1.0/1.1/1.0/

[7.0/-/-])Extra module

Trang 39

Extra unit0x40001 (hex)

262145 (dec)

-,Yellow

A unit is present but it is not part of the expectedconfiguration eqmInventoryReport (FP[1.0/4.1/-/-/-] /-/-/-/-/-/1.1/1.0/

SFP Received Power exceeds high alarm levelset in SFP

cation (FP [-/-/2.11/3.0/4.0]

SFP Received Power is below low alarm levelset in SFP eqmIfConnModuleIdentifi-cation (FP [-/-/2.11/3.0/4.0]

SFP internal supply voltage exceeds high alarmlevel set in SFP eqmIfConnModuleIdentifi-cation (FP [-/-/2.11/3.0/4.0]

SFP internal supply voltage is below low alarmlevel set in SFP eqmIfConnModuleIdentifi-cation (FP [-/-/2.11/3.0/4.0]

SFP internal temperature exceeds high alarm levelset in SFP eqmIfConnModuleIdentifi-cation (FP [-/-/2.11/3.0/4.0]

SFP internal temperature is below low alarm levelset in SFP

cation (FP [-/-/2.11/3.0/4.0]

SFP TX Bias current exceeds high alarm levelset in SFP

cation (FP [-/-/2.11/3.0/4.0]

Trang 40

If conn tx bias current toolow

0x40019 (hex)

262169 (dec)

SFP TX Bias current is below low alarm levelset in SFP eqmIfConnModuleIdentifi-cation (FP [-/-/2.11/3.0/4.0]

SFP TX output power exceeds high alarm levelset in SFP eqmIfConnModuleIdentifi-cation (FP [-/-/2.11/3.0/4.0]

SFP TX output power is below low alarm levelset in SFP

cation (FP [-/-/2.11/3.0/4.0]

eqmIfConnModuleIdentifi-/2.11/1.0/1.3/1.1/1.0/1.1/1.0/

[-/7.0/-])Incompatible hw version

0x4000F (hex)

262159 (dec)

The unit has incompatible HW version withexpected one Unit with newer HW version isrequired

/-/-/-/-/-/-/-/ [7.0/7.0/7.0])Incompatible sw version

0x40009 (hex)

262153 (dec)

Service affecting,None

This unit has incompatible SW version withreferred unit Either this or referred unit SWshould be updated

/-/-/-/-/-/-/1.0/ [7.0/7.0/7.0])Inventory installation

error0x40006 (hex)

262150 (dec)

The expected configuration is not specified Atminimum it must contain at least one control unit,which can be added e.g by re-creating inventory

eqmInventory (FP[1.0/4.1/-/-/-] /-/-/-/-/-/-/-/

[7.0/-/-])

License abis license about

to expire0x40010 (hex)

262160 (dec)

-,None

Abis is configured in use but the license is about

to expire Please, renew the license soon to keepservice running

eqmLicenseInterface(FP [2.9A/4.1/-/-/-]

Abis is configured in use but the license is expired

or not found The resource is blocked from use (orwill be) Please, renew the license immediately

eqmLicenseInterface(FP [2.9A/4.1/-/-/-]

Định dạng
Số trang	102
Dung lượng	916,47 KB