Reference Guide

SONET/SDH | 949

SONET Syslog Example

Syslog messages are generated for Critical, Major, and Minor alarm conditions detected on a SONET

interface according to the alarm hierarchy. For example, if a critical alarm condition is detected, a Syslog

message is reported for the critical condition, but not for any major and minor alarms that may also be

found. If a minor alarm condition is detected, a major or critical condition may also be reported.

The following output text shows an example of the Syslog messages generated for SONET alarms:

• Line Alarm Indication Signal (lais)

• Path Remote Defect Indication (prdi)

• Section Loss of Frame (slof)

Oct 6 04:46:51: %EXW4PF:13 %SONETAGT-5-ALARM: Interface Te 13/1 is out of alarm LAIS

Oct 6 04:46:42: %EXW4PF:13 %SONETAGT-6-ALARM: Interface Te 13/1 is out of alarm PRDI

Oct 6 04:46:44: %EXW4PF:13 %SONETAGT-4-ALARM: Interface Te 13/1 is in alarm SLOF

Events that Bring Down a SONET Interface

Down State configuration is supported on E-Series TeraScale e

platforms.

You can configure the SONET interface to change to a “down state” when certain SONET events are

reported. When the event (or trigger) occurs, FTOS brings down the SONET interface. You can use the

delay triggers command to indicate a 100ms delay in bringing down the SONET interface once the event

or trigger is detected.

By default, certain alarms (LOS, LOF, LAIS, PLOP) bring the line protocol down immediately. Use this

command, with the

line option, to delay that trigger event by 100ms.

By default, path alarms (AIS, RDI, LOP) do not cause (or trigger) the interface line protocol to go down.

The

delay triggers command, used with the path option, can be used to trigger this action.

Task Command Syntax Command Mode

Delay triggering the line or path alarms

with a 100ms delay.

delay triggers {line [lrdi | sd-ber | sf-ber]

| path [pais | prdi]

}

INTERFACE

Note: FTOS does not support configurable thresholds; delay triggers uses a default value of 100 ms.