The following sections describe the new, optional configuration tasks for the CT3IP.
CISCO RECEIVER HAS REMOTE ALARM SERIES
Cisco 7000 series routers with the RSP7000 and RSP7000CI Configuration Tasks.This feature is supported on these platforms: Wherever you see a description of a feature of the CT3IP, the feature is also available in the PA-CT3/4T1. However, the term CT3IP also applies to the PA-CT3/4T1. Note Throughout this document are references to the CT3IP.
![cisco receiver has remote alarm cisco receiver has remote alarm](https://manuals.paessler.com/s_cisco_ip_sla_zoom67.png)
Support SNMP MIB per RFC 1406 and RFC 1407.Generate bit error rate testing (BERT) test patterns.Enable performance monitoring via Facility Data Link (FDL) per ANSI T1.403.Configure Maintenance Data Link (MDL) messages.You can also perform these tasks on the Channelized T3 dual-wide port adapter (PA-CT3/4T1), which can be used in Cisco 7200 series routers: You can now perform the following new tasks on the Channelized T3 Interface Processor (CT3IP) available on Cisco 7500 series routers, and on Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). This cell then sends a message back to the near end.Channelized T3 Interface Processor and Port Adapter (DS3) A FEBE in C-bit parity is a parity violation detected at the far-end terminal and transmitted back to the near-end terminal.Ī maintenance cell indicates that an error occurred with a data block at the far end of the link. ( all rights reserved)Īn indication sent to a transmitting node that a flawed block has been detected at the receiving node. An ATM interface reports detected C-bit parity errors back to the source via a far-end block error (FEBE). The M-subframe uses C bits in a format called C-bit parity, which copies the result of the P bits at the source and checks the result at the destination. The DS-3 M-frame uses P bits to check the line parity. Any other value is interpreted as zero errors. The legal range for the 4-bit field is between 00, representing zero to eight errors. This specific setup of error reporting is what causes the confusion between many technicians trying to perform repairs.Īn error detected by extracting the 4-bit FEBE field from the path status byte (G1). So, errors are generated on the incoming side of the loop, the device terminating that end picks up the errors, and transmits a 'FEBE errors' message on the outgoing side. The terminating device then sends the 'FEBE' error signal outbound to alert further devices there were problems. The errors are being generated by a device in the central office, and being detected by the terminating device (a NID, M13 Mux or router). If you have a DS3 running from New York to Atlanta, and there's a problem within one of the central offices in Virginia. Network monitoring equipment located anywhere along the path then measures these FEBEs in each direction to gauge the quality of the circuit while in service. If an error is detected on the incoming DS3, the terminating elements transmit a FEBE bit on the outgoing direction of the DS3. REI or FEBE errors are mostly seen on DS3 circuits, however they are known to be present on other types (SONET/T1s etc.).Įach terminating device ( router or otherwise) monitors the incoming signal for CP-bit path errors. It indicates to the transmitting node that the receiver has detected a block error. Remote error indication ( REI) or formerly far end block error (FEBE) is an alarm signal used in synchronous optical networking (SONET).
![cisco receiver has remote alarm cisco receiver has remote alarm](https://www.cisco.com/en/US/i/Other/Cisco_Press/ITG/10-19-01/TR891508.jpg)
( Learn how and when to remove this template message) WikiProject Telecommunications may be able to help recruit an expert. Please add a reason or a talk parameter to this template to explain the issue with the article. This article needs attention from an expert in Telecommunications.