Table 30: remote mep priority levels, Table 31: mep defect descriptions – LevelOne GTL-2691 User Manual

Page 483

Advertising
background image

C

HAPTER

14

| Basic Administration Protocols

Connectivity Fault Management

– 483 –

The MIP creation method defined for an MA (see

"Configuring CFM

Maintenance Associations"

) takes precedence over the method defined

on the CFM Domain List.

Configuring Fault Notification

A fault alarm can generate an SNMP notification. It is issued when the

MEP fault notification generator state machine detects that the

configured time period (MEP Fault Notify Alarm Time) has passed with

one or more defects indicated, and fault alarms are enabled at or above

the specified priority level (MEP Fault Notify Lowest Priority). The state

machine transmits no further fault alarms until it is reset by the

passage of a configured time period (MEP Fault Notify Reset Time)
without a defect indication. The normal procedure upon receiving a

fault alarm is to inspect the reporting MEP’s managed objects using an

appropriate SNMP software tool, diagnose the fault, correct it, re-

examine the MEP’s managed objects to see whether the MEP fault

notification generator state machine has been reset, and repeat those

steps until the fault is resolved.

Only the highest priority defect currently detected is reported in the

fault alarm.

Priority levels include the following options:

Table 30: Remote MEP Priority Levels

Priority Level

Level Name

Description

1

allDef

All defects.

2

macRemErrXcon

DefMACstatus, DefRemoteCCM, DefErrorCCM, or

DefXconCCM.

3

remErrXcon

DefErrorCCM, DefXconCCM or DefRemoteCCM.

4

errXcon

DefErrorCCM or DefXconCCM.

5

xcon

DefXconCCM

6

noXcon

No defects DefXconCCM or lower are to be reported.

Table 31: MEP Defect Descriptions

Defect

Description

DefMACstatus

Either some remote MEP is reporting its Interface Status TLV as not isUp,

or all remote MEPs are reporting a Port Status TLV that contains some value

other than psUp.

DefRemoteCCM

The MEP is not receiving valid CCMs from at least one of the remote MEPs.

DefErrorCCM

The MEP has received at least one invalid CCM whose CCM Interval has not

yet timed out.

DefXconCCM

The MEP has received at least one CCM from either another MAID or a lower

MD Level whose CCM Interval has not yet timed out.

Advertising