![]() Note: In order to capture granular timestamps on log messages, configure the service timestamps log datetime msec command.Ī router with ATM over SONET interfaces also reports active alarms with these log messages: Feb 18 16:34:22.309: %SONET-4-ALARM: ATM5/0: ~SLOF SLOS LAIS ~LRDI PAIS PRDI ~PLOP ![]() Aug 7 05:14:37 BST: %LINK-3-UPDOWN: Interface POS4/7, changed stateĪug 7 05:14:38 BST: %LINEPROTO-5-UPDOWN: Line protocol on InterfaceĪug 7 05:14:49 BST: %SONET-4-ALARM: POS4/7: LRDI clearedĪug 7 05:14:52 BST: %SONET-4-ALARM: POS4/7: LRDIĪug 7 05:15:02 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface The LINEPROTO-5-UPDOWN message indicates that the line protocol is up the line protocol on POS interfaces is Frame Relay, High-Level Data Link Control (HDLC) or Point-to-Point Protocol (PPP). The LINK-3-UPDOWN message indicates that the physical-layer is up and that all active alarms are now clear. This sample output was also captured from a GSR. RTR12410-1# show controller pos 1/0Īctive Defects: SLOF SLOS B1-TCA LAIS PAIS PRDI B3-TCA Active Alarms: SLOS B1-TCA B3-TCAĪlarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA The Active Alarms section indicates what the upstream device reports. The Active Defects section indicates what the local interface sees. This output was captured on a Gigabit Switch Router (GSR). The show controllers command displays the number of times that an alarm is declared and whether any alarms are active on a POS and ATM over SONET interface. Sf-ber LBIP BER in excess of SF threshold ![]() Sd-ber LBIP BER in excess of SD threshold Issue the pos report command in order to configure the alarms that the packet over SONET (POS) interface can activate. Typically, a SONET device sends alarms both upstream and downstream in order to notify other devices of the problem condition. SONET equipment detects events and alarms at each of SONET's three layers - section, line and path. Refer to Cisco Technical Tips Conventions for more information on document conventions. If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. This document is not restricted to specific software and hardware versions. There are no specific requirements for this document. The process used to troubleshoot down/down SONET interfaces is similar to that for digital interfaces, such as T1 and T3. This document discusses the alarm indication signal (AIS), remote defect indicator (RDI), and far end receive failure (FERF) indications.Īctive alarms or defects keep an interface in the down/down state. This indicates the presence of a condition. Indication-Prompted by a change of state. This document discusses the loss of signal (LOS) and loss of frame (LOF) states. A SONET device exits that state when the device no longer detects the event. A SONET device enters a state when the device detects the occurrence of an event. State-Condition that is reported or detected. ![]() This document explains common SONET alarms and how to troubleshoot them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |