Table Of Contents
Packet-over-SONET User Interface and SONET Layer 1 Commands on Cisco IOS XR Software
ais-shut (SONET)
ais-shut (SONET path)
clear counters sonet
clock source (SONET)
controller
crc
delay trigger
framing (SONET)
loopback (SONET)
overhead (SONET)
overhead (SONET path)
path (SONET)
pos
pos transmit-delay
report (SONET)
report (SONET path)
scrambling (SONET path)
show controllers pos
show controllers sonet
shutdown (SONET)
threshold (SONET)
threshold (SONET path)
uneq-shut (SONET path)
Packet-over-SONET User Interface and SONET Layer 1 Commands on Cisco IOS XR Software
This module describes the Cisco IOS XR commands used to configure, monitor, and troubleshoot packet-over-SONET (POS). It also describes the Cisco IOS XR software commands used to configure the SONET operation on a router port using Layer 1 SONET transport technology.
All SONET-related configurations of a SONET-based physical port are grouped under the SONET controller configuration submode. The SONET path-related configuration commands are grouped under the SONET path submode.
POS provides a method for efficiently carrying data packets in SONET or Synchronous Digital Hierarchy (SDH) frames. High-bandwidth capacity and efficient link utilization are characteristics that make POS largely preferred for building the core of data networks. POS uses PPP in High-Level Data Link Control (HDLC)-like framing for data encapsulation at Layer 2 (data link) of the Open System Interconnection (OSI) stack. This method provides efficient packet delineation and error control.
In addition to high-bandwidth efficiency, POS offers secure and reliable transmission for data. Reliable data transfer depends on timing integrity.
The real-time POS functionality is performed in hardware, according to the hardware configuration setup. Configured hardware events are detected by the framer application-specific integrated circuits (ASICs) and the control is passed to the software. The generic POS driver is responsible for providing a mechanism to configure the hardware on a per-interface basis, to handle interface state transitions, and to collect POS-related statistics.
ais-shut (SONET)
To enable automatic insertion of a line alarm indication signal (LAIS) in the sent SONET signal whenever the SONET port enters the administrative shutdown state, use the ais-shut command in SONET configuration mode. To disable automatic insertion of a LAIS, use the no form of this command.
ais-shut
no ais-shut
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default; no AIS is sent.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
When the line is placed in administrative shutdown state, use the ais-shut command to send a signal to downstream equipment that indicates that there is a problem with the line.
The ais-shut command is ignored if automatic protection switching (APS) is running for the corresponding port, because the setting must be enabled for proper APS operation.
For SONET ports that do not have hardware support for LAIS insertion, the ais-shut command is disabled.
Examples
In the following example, the alarm indication is forced on the SONET OC-3 controller:
RP/0/RP0/CPU0:router(config)# controller sonet 0/1/0/0
RP/0/RP0/CPU0:router(config-sonet)# ais-shut
ais-shut (SONET path)
To enable automatic insertion of path alarm indication signal (PAIS) in the sent SONET signal whenever the SONET path enters the administratively down state, use the ais-shut command in SONET path configuration mode. To disable automatic insertion of PAIS in the SONET signal, use the no form of this command.
ais-shut
no ais-shut
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default; no AIS is sent.
Command Modes
SONET path configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the ais-shut command to enable automatic insertion of PAIS in the appropriate sent SONET path overhead whenever the corresponding SONET path enters the administratively down state.
Examples
The following example enables the alarm indication on all paths:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# path
RP/0/RP0/CPU0:router(config-sonet-path)# ais-shut
clear counters sonet
To clear SONET counters for a specific SONET controller, use the clear counters sonet command in EXEC mode.
clear counters sonet interface-type interface-instance
Syntax Description
interface-type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a Route Processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range will vary depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clear counters sonet command to clear SONET counters for a specific SONET controller.
Examples
The following example clears the SONET counters on the SONET interface:
RP/0/RP0/CPU0:router# clear counters ?
Loopback Loopback interface(s)
MgmtEth Ethernet/IEEE 802.3 interface(s)
POS Packet over SONET network interface(s)
SONET SONET/SDH Port controller(s)
all Clear counters on all interfaces
tunnel-te MPLS Traffic Engineering Tunnel interface(s)
RP/0/RP0/CPU0:router# clear counters sonet ?
0/1/0/0 SONET Interface Instance
0/1/0/1 SONET Interface Instance
0/1/0/2 SONET Interface Instance
0/1/0/3 SONET Interface Instance
0/2/0/0 SONET Interface Instance
0/2/0/1 SONET Interface Instance
0/2/0/2 SONET Interface Instance
0/2/0/3 SONET Interface Instance
RP/0/RP0/CPU0:router# clear counters sonet 0/1/0/0
clock source (SONET)
To set the clock source of the sent signal on SONET ports, use the clock source command in SONET configuration mode. To cancel a clock source setting, use the no form of this command.
clock source {internal | line}
no clock source {internal | line}
Syntax Description
internal
|
Specifies that the controller will clock its sent data from its internal clock.
|
line
|
Specifies that the controller will clock its sent data from a clock recovered from the receive data stream of the line. This is the default value.
|
Defaults
The default clock source for the controller is the line clock.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the clock source command to configure which reference clock is used by the sender.
Examples
In the following example, the SONET controller is configured to clock its sent data from its internal clock:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# clock source internal
controller
To configure a SONET controller, use the controller command in global configuration mode. To return to the default state, use the no form of this command.
controller {sonet | preconfigure} interface-type interface-instance
no controller {sonet | preconfigure} interface-type interface-instance
Syntax Description
sonet
|
Configures SONET port controllers.
|
preconfigure
|
Specifies a SONET preconfiguration. This keyword is only used when a line card in not physically installed in a slot
|
interface-type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a Route Processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range will vary depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
Command Modes
Global configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
The following example shows how to specify that the configured SONET controller is in slot number 2:
RP/0/RP0/CPU0:router(config)# controller SONET 0/2/0/1
RP/0/RP0/CPU0:router(config-sonet)#
The following example shows how to specify that the SONET controller you want to preconfigure is in slot number 3, which does not have a line card installed:
RP/0/RP0/CPU0:router(config)# controller preconfigure SONET 0/3/0/1
RP/0/RP0/CPU0:router(config-sonet)#
crc
To set the length of the cyclic redundancy check (CRC) on a packet-over-SONET (POS) interface, use the crc command in POS interface configuration mode. To return the CRC setting on a POS interface to the 16-bit default setting for OC-3 cards, use the no form of this command.
crc {16 | 32}
no crc {16 | 32}
Syntax Description
16
|
Sets 16-bit CRC mode (default on OC-3 cards). The default is 16 bits.
|
32
|
Sets 32-bit CRC mode (default on OC-12 cards and higher). The default is 32 bits.
|
Defaults
The default is 16 bits for OC-3/Synchronous Transport Module (STM)-1 and 32 bits for OC-12/STM-4 and OC-48/STM-16 POS interfaces.
Command Modes
POS interface configuration
Command History
Releases
|
Modifications
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Default CRC for interfaces depends on the type of POS interface: OC-3/STM-1 uses a 16-bit CRC; OC-12/STM-4 and OC-48/STM-16 POS interfaces use a 32-bit CRC. All interfaces also support a 32-bit CRC.
CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The designators 16 and 32 indicate the length (in bits) of the frame check sequence (FCS). A CRC of 32 bits provides more powerful error detection, but adds overhead. Both the sender and receiver must use the same setting.
CRC-16, the most widely used error checking method throughout the United States and Europe, is used extensively with WANs. CRC-32 is specified by Electrical and Electronics Engineers (IEEE) 802 and as an option by some point-to-point transmission standards. It is often used on Switched Multimegabit Data Service (SMDS) networks and LANs.
Examples
In the following example, the 32-bit CRC on POS interface 0/1/0/2 is enabled:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/2
RP/0/RP0/CPU0:router(config-if)# POS
RP/0/RP0/CPU0:router(config-if-pos)# crc 32
Related Commands
Command
|
Description
|
pos transmit-delay
|
Specifies a number of flag sequences to be inserted between the packets.
|
delay trigger
To configure SONET line delay trigger values, use the delay trigger command in SONET configuration mode. To cancel the line delay trigger value and return to the default, use the no form of this command.
delay trigger line value
no delay trigger line value
Syntax Description
line value
|
Sets the SONET line delay trigger value in milliseconds. The range is from 0 to 511. The default is 0 (no delay).
|
Defaults
value: 0 milliseconds
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
In the following example, the SONET line delay trigger value is set to 5:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# delay trigger line 5
framing (SONET)
To specify the framing used on the SONET controller, use the framing command in SONET configuration mode. To disable framing on the SONET controller, use the no form of this command.
framing {sdh | sonet}
no framing {sdh | sonet}
Syntax Description
sdh
|
Selects Synchronous Digital Hierarchy (SDH) framing. This framing mode is typically used in Europe.
|
sonet
|
Selects SONET framing. This is the default.
|
Defaults
SONET framing.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the framing command to select either SONET or SDH framing on the selected physical port, if supported. For physical ports that do not support either of these two options, the framing command is disabled.
Use the no form of this command to disable SONET or SDH framing on the SONET controller.
Examples
In the following example, the SONET controller is configured for SDH framing:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# framing sdh
loopback (SONET)
To configure the SONET controller for loopback mode, use the loopback command in SONET configuration mode. To remove the loopback SONET command from the configuration file, use the no form of this command.
loopback {internal | line}
no loopback {internal | line}
Syntax Description
internal
|
Specifies that all the packets be looped back from the source.
|
line
|
Specifies that the incoming network packets be looped back to the SONET network.
|
Defaults
This command is disabled by default.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The SONET and Synchronous Digital Hierarchy (SDH) transport layers support two loopback operation modes for diagnostic purposes: internal and line. In the terminal (internal) loopback, the sent signal is looped back to the receiver. While in the facility (line) loopback, the signal received from the far end is looped back and sent on the line. The two loopback modes cannot be active at the same time. In normal operation mode, neither of the two loopback modes is enabled.
Examples
In the following example, all packets are looped back to the SONET controller:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# loopback internal
overhead (SONET)
To set the SONET overhead bytes in the frame header to a specific standards requirement or to ensure interoperability with equipment from another vendor, use the overhead command in SONET configuration mode. To remove the setting of the SONET overhead bytes from the configuration file and restore the default condition, use the no form of this command.
overhead {j0 | s1s0} byte value
no overhead {j0 | s1s0} byte value
Syntax Description
j0
|
Sets the J0/C1 byte value in the SONET section overhead. For interoperability with Synchronous Digital Hierarchy (SDH) equipment in Japan, use the value 0x1. The default j0 value is 0xcc
|
s1s0
|
Sets the SS bits value of the H1 byte in the SONET line overhead.
Use the following values to tell the SONET transmission equipment the S1and S0 bit:
• For SONET mode, use 0 (this is the default).
• For SDH mode, use 2.
The values for the S1 and S0 bits can be from 0 to 3. The default sls0 value is 0. Values 1 and 3 are undefined.
|
byte value
|
The byte value to which the j1 or s1s0 keyword should be set. The range is from 0 to 255.
|
Defaults
The default j0 value is 0xcc; the default sls0 value is 0.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the overhead command to set the SONET overhead bytes in the frame header to a specific standards requirement.
Use the no form of this command to remove the setting of the SONET overhead bytes from the configuration file and restore the default condition.
For the j0 keyword, the value that you use for the trace byte depends on the type of equipment being used. For the s1s0 keyword, the value that you use depends on whether you are using the SONET or SDH mode. For SONET mode, use the value 0 (this is the default). For SDH mode, use the value 2.
Examples
In the following example, the s1s0 keyword value is set to 2 for SDH:
RP/0/RP0/CPU0:router(config)# controller sonet 0/1/0/1
RP/0/RP0/CPU0:router(config-sonet)# overhead sls0 2
overhead (SONET path)
To set the SONET path overhead bytes in the frame header to a specific standards requirement or to ensure interoperability with equipment from another vendor, use the overhead command in SONET path configuration mode. To remove the setting of the SONET path overhead bytes from the configuration file and restore the system to its default condition, use the no form of this command.
overhead {c2 | j1} byte value
no overhead {c2 | j1} byte value
Syntax Description
c2
|
Specifies Synchronous Transport Signal (STS) synchronous payload envelope (SPE) content (C2) byte. The transmitted c2 value is automatically set to 0xCF for unscrambled payload and 0x16 for scrambled payload. If c2 is configured to a user specified value, this value is always applied regardless of scrambling.
|
j1
|
Configures the SONET path trace (j1) buffer. Default is a 64-byte path trace ASCII message, which includes default information such as router name, (Layer 2—POS) interface name, and IP address, if applicable.
|
byte value
|
The byte value to which the c2 keyword should be set. The range is from 0 to 255. For the j1 keyword, ASCII text message can have a maximum of 62 characters. The default value for the j1 keyword is 0.
|
Defaults
The default c2 value is 0xCF; the default j1 value is 0.
Command Modes
SONET path configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The SONET standards permit or require user access for configuration of some bytes or bits in the SONET path overhead. Use the overhead command to set the SONET path overhead bytes in the frame header to a specific standards requirement. Use the no form of this command to remove the setting of the SONET path overhead bytes from the configuration file and restore the system to its default condition.
Use the c2 keyword to configure the desired C2 byte value in the SONET path overhead.
Use the j1 keyword to configure a user-defined path trace message in the j1 bytes of the SONET path overhead. For the j1 keyword, use the default message or insert your own message that has a maximum of 62 characters. If no user-defined message is configured, a default message will be automatically generated, containing the router name, the controller name, its IP address, and the values of the sent and received K1 and K2 bytes in the SONET line overhead.
Examples
In the following example, the c2 value is set:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# path
RP/0/RP0/CPU0:router(config-sonet-path)# overhead c2 0x13
Related Commands
path (SONET)
To enter the SONET path configuration submode, use the path command in SONET controller configuration mode.
path
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
SONET controller configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the path command to access SONET path configuration submode. The following commands are available in SONET path configuration submode:
•
ais-shut—Configure sending path alarm indication signal (PAIS) when shut down
•
default—Set a command to its defaults
•
describe—Describe a command without taking real actions
•
do—Run an EXEC command
•
exit—Exit from this submode
•
no—Negate a command or set its defaults
•
overhead—Configure SONET Path OverHead (POH) byte or bit values
•
report—Configure SONET path alarm reporting
•
scrambling—Configure Synchronous Payload Envelope (SPE) scrambling
•
threshold—Configure SONET path bit-error rate (BER) threshold values
•
uneq-shut—Configure sending "Unequipped" (UNEQ) when shut down
Examples
In the following example, the SONET path submode is accessed:
RP/0/RP0/CPU0:router(config)# controller sonet 0/1/0/0
RP/0/RP0/CPU0:router(config-sonet)# path
pos
To access the POS interface configuration submode, use the pos command in interface configuration mode.
pos
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default behavior or values.
Command Modes
Interface configuration
Command History
Releases
|
Modifications
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Examples
In the following example, POS configuration submode is accessed from POS interface configuration submode:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/2
RP/0/RP0/CPU0:router(config-if)# POS
RP/0/RP0/CPU0:router(config-if-pos)#
Related Commands
Command
|
Description
|
crc
|
Sets the length of the CRC on a POS interface.
|
pos transmit-delay
|
Specifies a number of flag sequences to be inserted between the packets.
|
pos transmit-delay
To specify a number of flag sequences to be inserted between the packets, use the pos transmit-delay command in interface configuration mode. To restore the default, use the no form of this command.
pos transmit-delay microseconds
no pos transmit-delay microseconds
Syntax Description
microseconds
|
The number of microseconds of minimum delay after sending a packet. The valid range is from 0 to 1023. The default value is 0 (disabled).
|
Defaults
The default is 0 (disabled).
Command Modes
Interface configuration
Command History
Releases
|
Modifications
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The pos transmit-delay command is especially useful for serial interfaces that can send back-to-back data packets over interfaces faster than some hosts can receive them.
Examples
In the following example, a delay of 2 microseconds is specified on POS interface 0/1/0/2:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/2
RP/0/RP0/CPU0:router(config-if)# POS transmit-delay 2
In the following example, the transmit delay on POS interface 0/1/0/2 is disabled:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface POS 0/1/0/2
RP/0/RP0/CPU0:router(config-if)# no POS transmit-delay
report (SONET)
To permit selected SONET alarms to be logged to the console for a SONET controller, use the report command in SONET configuration mode. To disable logging of select SONET alarms, use the no form of this command.
report [b1-tca | b2-tca | lais | lrdi | sd-ber | sf-ber | slof | slos]
no report [b1-tca | b2-tca | lais | lrdi | sd-ber | sf-ber | slof | slos]
Syntax Description
b1-tca
|
(Optional) Reports bit 1 (B1) bit-error rate (BER) threshold crossing alert (TCA) errors.
|
b2-tca
|
(Optional) Reports bit 2 (B2) BER TCA errors.
|
lais
|
(Optional) Reports Line Alarm Indication Signal (LAIS) errors.
|
lrdi
|
(Optional) Reports line remote defect indication errors.
|
sd-ber
|
(Optional) Reports signal degradation BER errors.
|
sf-ber
|
(Optional) Reports signal failure BER errors.
|
slof
|
(Optional) Reports section loss of frame (SLOF) errors.
|
slos
|
(Optional) Reports section loss of signal (SLOS) errors.
|
Defaults
Alarms from the following keywords are reported by default:
•
b1-tca
•
b2-tca
•
sd-ber
•
sf-ber
•
slof
•
slos
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Reporting an alarm means that the alarm can be logged to the console. Just because an alarm is permitted to be logged does not guarantee that it is logged. SONET alarm hierarchy rules dictate that only the most severe alarm of an alarm group is reported. Whether an alarm is reported or not, you can check the current state of masked alarm, a problem indication that is a candidate for an alarm, by displaying the "Masked Alarms" line in the show controllers sonet command output.
For B1, the bit interleaved parity (BIP) error report is calculated by comparing the BIP-8 code with the BIP-8 code that is extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
For B2, the BIP error report is calculated by comparing the BIP-8/24 code with the BIP-8 code that is extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
Path AIS is sent by line terminating equipment to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.
Path loss of pointer (LOP) is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag enabled indications.
SLOF is detected when an error framing defect on the incoming SONET signal persists for 3 microseconds.
SLOS is detected when an all-zeros pattern on the incoming SONET signal is observed. This defect might also be reported if the received signal level drops below the specified threshold.
To determine the alarms that are reported on the controller, use the show controllers sonet command.
Examples
In the following example, the reporting of line AIS alarms is enabled on the path controller:
RP/0/RP0/CPU0:router(config)# controller sonet 0/1/0/1
RP/0/RP0/CPU0:router(config-sonet)# report lais
Related Commands
report (SONET path)
To permit selected SONET alarms to be logged to the console for a SONET path controller, use the report command in SONET path configuration mode. To disable logging of select SONET alarms, use the no form of this command.
report [b3-tca | pais | plop | prdi | puneq]
no report [b3-tca | pais | plop | prdi | puneq]
Syntax Description
b3-tca
|
(Optional) Reports bit 3 (B3) bit-error rate (BER) threshold crossing alert (TCA) errors.
|
pais
|
(Optional) Reports path alarm indication signal (PAIS) errors.
|
plop
|
(Optional) Reports path loss of pointer (LOP) errors.
|
prdi
|
(Optional) Reports path remote defect indication (PRDI) errors.
|
puneq
|
(Optional) Reports path unequipped defect indication reporting status.
|
Defaults
Alarms from the following keywords are reported by default:
•
b3-tca
•
plop
Command Modes
SONET path configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Reporting an alarm means that the alarm can be logged to the console. Just because an alarm is permitted to be logged does not guarantee that it is logged. SONET alarm hierarchy rules dictate that only the most severe alarm of an alarm group is reported. Whether an alarm is reported or not, you can view the current state of an masked alarm, a problem indication that is a candidate for an alarm, by inspecting the "Masked Alarms" line displayed in the show controllers sonet command output.
For B3, the bit interleaved parity (BIP) error report is calculated by comparing the BIP-8 code with the BIP-8 code that is extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
Path AIS is sent by line terminating equipment to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.
Path LOP is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag enabled indications.
To determine the alarms that are reported on the controller, use the show controllers sonet command.
All report commands accept the default option. The default reporting values are determined based upon the SONET standards specifications and are clearly identified in the corresponding command's help string.
Examples
In the following example, reporting of path PAIS alarms is enabled:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# path
RP/0/RP0/CPU0:router(config-sonet-path)# report pais
Related Commands
scrambling (SONET path)
To enable SONET payload scrambling on a SONET path, use the scrambling command in SONET path configuration mode. To disable payload scrambling, use the no form of this command.
scrambling {enable | disable}
no scrambling
Syntax Description
enable
|
Enables the functionality of the command.
|
disable
|
Disables the functionality of the command.
|
Defaults
The default is enable (SONET payload scrambling is on).
Command Modes
SONET path configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the scrambling command in SONET path configuration mode to enable SONET payload scrambling on a SONET path. Use the no form of this command to disable payload scrambling.
SONET payload scrambling applies a self-synchronous scrambler (x43+1) to the Synchronous Payload Envelope (SPE) of the controller to ensure sufficient bit transition density. Both ends of the connection must be configured using SONET path scrambling.
If the hardware payload scrambling support is not user-configurable, or is not supported, the scrambling command may be disabled or may be rejected.
Examples
In the following example, scrambling is enabled for the path:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# path
RP/0/RP0/CPU0:router(config-sonet-path)# scrambling enable
show controllers pos
To display information on the packet-over-SONET (POS) controllers, use the show controllers pos command in EXEC mode.
show controllers pos interface-instance [{all | details | queues | registers | stats} | {{rxfifo | txfifo}
address}]
Syntax Description
interface-type
|
Interface type. For more information, use the question mark (?) online help function.
|
interface-instance
|
Either a physical interface instance or a virtual interface instance:
• Physical interface instance. Naming notation is rack/slot/module/port and a slash mark between values is required as part of the notation.
– rack: Chassis number of the rack.
– slot: Physical slot number of the line card.
– module: Module number. A physical layer interface module (PLIM) is always 0.
– port: Physical port number of the interface.
Note In references to a Management Ethernet interface located on a Route Processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0.
• Virtual interface instance. Number range will vary depending on interface type.
For more information about the syntax for the router, use the question mark (?) online help function.
|
all
|
(Optional) Displays information for all POS interface controllers.
|
details
|
(Optional) Displays all SONET details for the specified interface.
|
queues
|
(Optional) Displays POS queue information.
|
registers
|
(Optional) Displays the POS application-specific integrated circuit (ASIC) registers for the specified controller.
|
stats
|
(Optional) Displays cumulative ASIC counters.
|
rxfifo
|
(Optional) Displays the receive first in, first out (FIFO) stack.
|
txfifo
|
(Optional) Displays the transmit FIFO stack.
|
address
|
(Optional) The starting address relative to the beginning of the FIFO stack.
|
Command Modes
EXEC
Command History
Releases
|
Modifications
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
Examples
The following is sample output from the show controllers pos command:
RP/0/RP0/CPU0:router# show controllers POS 0/3/0/2
Port Bandwidth Kbps : 2488320
RP/0/RP0/CPU0:router# show controllers POS 0/3/0/2 all
Port Bandwidth Kbps : 2488320
POS Driver Internal Cooked Stats Values for port 2
===================================================
Rx Statistics Tx Statistics
------------- -------------
Total Bytes: 1200 Total Bytes: 0
Good Bytes: 1200 Good Bytes: 0
Good Packets: 25 Good Packets: 0
FCS Errors: 0 Min-len errors: 0
Runts: 0 Max-len errors: 0
FIFO Overflows: 0 FIFO Underruns: 0
Sky4402 asic #2 registers:
0x002 sys_intf_cntrl_1 0x06
0x003 sys_intf_cntrl_2 0x00
0x011 gpio_port_mode 0x01
0x012 gpio_port_fault 0x00
0x013 gpio_port_data 0x58
0x015 gpio_port_cntrl 0x3f
0x017 gpio_port_transition 0x00
0x019 gpio_port_intr_mask 0xff
0x01b gpio_port_intr 0x3f
0x01c master_intr_status 0x00
0x02d link_state_cntrl 0x80
0x043 short_frame_cntrl 0x00
0x18a rtop_deb_s1_ovrhd 0x00
0x18c rtop_b1_mismatch_cnt_u 0x00
0x18d rtop_b1_mismatch_cnt_l 0x00
0x190 rtop_b2_mismatch_cnt_u 0x00
0x191 rtop_b2_mismatch_cnt_l 0x00
0x194 rtop_rei_l_cnt_u 0x00
0x195 rtop_rei_l_cnt_l 0x00
0x198 rtop_ber_thresh_u 0x00
0x199 rtop_ber_thresh_l 0x00
0x19a rtop_ber_leak_u 0x00
0x19b rtop_ber_leak_l 0x00
0x19c rtop_ber_delay_u 0x00
0x19d rtop_ber_delay_l 0x00
0x1c0 rpop_signal_lbl_c2 0x16
0x1c2 rpop_valid_ptr_u 0x02
0x1c3 rpop_valid_ptr_l 0x0a
0x1c4 rpop_b3_mismatch_cnt_u 0x00
0x1c5 rpop_b3_mismatch_cnt_l 0x00
0x1c8 rpop_rei_p_cnt_u 0x00
0x1c9 rpop_rei_p_cnt_l 0x00
0x1cc rpop_ber_thresh_u 0x00
0x1cd rpop_ber_thresh_l 0x00
0x1ce rpop_ber_leak_u 0x00
0x1cf rpop_ber_leak_l 0x00
0x1d0 rpop_ber_delay_u 0x00
0x1d1 rpop_ber_delay_l 0x00
0x208 rpp_max_pkt_len_u 0x08
0x209 rpp_max_pkt_len_l 0xbd
0x20a rpp_min_pkt_len 0x04
0x244 tpp_inter_pkt_u 0x00
0x245 tpp_inter_pkt_l 0x00
0x246 tpp_idle_cell_hdr 0x00
0x247 tpp_idle_cell_filldata 0x00
0x2c2 ttog_ovrhd_src_1 0x00
0x2c3 ttog_ovrhd_src_2 0x00
0x2c9 ttog_ovrhd_fill 0x00
Table 34 describes the significant fields shown in the display.
Table 34 show controllers pos Field Descriptions
Field
|
Description
|
Cisco POS ASIC Register Dump (Receive)
|
The header for display of the contents of the receive application-specific integrated circuit (ASIC) register log.
|
asic mode
|
The address in hex of the ASIC mode flag.
|
error source
|
The address in hex of the error source flag.
|
error mask
|
The address in hex of the error mask flag.
|
error detail 1
|
The address in hex of the error detail 1 flag.
|
error detail 2
|
The address in hex of the error detail 2 flag.
|
rx offset
|
The address in hex of the receive offset.
|
Channel Modes
|
Location in hex of the channel mode flag
|
Port 0:
|
Port 0 (the first port) statistics display.
|
Port 1:
|
Port 1 (the second port) statistics display.
|
Port 2:
|
Port 2 (the third port) statistics display.
|
Port 3:
|
Port 3 (the fourth port) statistics display.
|
Runt Threshold
|
The limit in packets set for runts on the specified port.
|
Tx Delay
|
The transmit delay that has been set for the specified port.
|
Cisco POS ASIC Register Dump (Transmit)
|
The header for display of the contents of the transmit ASIC register log.
|
POS Driver Internal Cooked Stats Values for port 0
|
Statistics relating to the specified PoS port (PoS port 0).
|
Rx Statistics
|
Receive statistics for the indicated PoS port.
|
Total Bytes
|
Total number of bytes, including data and MAC encapsulation, received by the system.
|
Good Bytes
|
The number of bytes received without errors.
|
Good Packets
|
The number of packets received without errors.
|
Aborts
|
Number of receive bytes that have been aborted
|
FCS Errors
|
The number of frame check sequence (FCS) errors that have been received.
|
Runts
|
Number of received packets that are discarded because they are smaller than the minimum packet size of the medium.
|
FIFO Overflows
|
Number of received packets that exceeded the first in, first out (FIFO) stack limit.
|
Giants
|
Number of received packets that are discarded because they exceed the maximum packet size of the medium.
|
Drops
|
The number of received packets that have been dropped from the system.
|
Tx Statistics
|
Transmit statistics for the indicated PoS port.
|
Total Bytes
|
Total number of bytes, including data and MAC encapsulation, sent by the system.
|
Good Bytes
|
The number of bytes sent without errors.
|
Good Packets
|
The number of packets sent without errors.
|
Aborts
|
Number of sent bytes that have been aborted.
|
Min-len errors
|
Minimum queue length violations.
|
Max-len errors
|
Maximum queue length violations.
|
FIFO Underruns
|
First-in, first-out, a buffering scheme where the first byte of data entering the buffer is the first byte retrieved by the CPU. FIFO underruns reports the number of times that the transmitter has been running faster than the router can handle.
|
show controllers sonet
To display information about the operational status of SONET layers, use the show controllers sonet command in EXEC mode.
show controllers sonet {all | framers | internal-state}
Syntax Description
all
|
Displays all information.
|
framers
|
Displays framer information.
|
internal-state
|
Displays internal SONET state.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the show controllers sonet command to display information about the operational status of SONET layers on a particular SONET port.
Examples
The following is sample output from the show controllers sonet command:
RP/0/RP0/CPU0:router# show controllers sonet 0/1/0/2
LOF = 0 LOS = 1 BIP(B1) = 0
AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0
AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0
LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0
Mask for Detected->Asserted: SLOF LAIS SF_BER SD_BER LRDI PLOP PAIS PRDI
Mask for Detected->Reported: B1-TCA B2-TCA B3-TCA
Alarm reporting enabled for: SLOS SLOF SF_BER PLOP
Alert reporting enabled for: B1-TCA B2-TCA B3-TCA
C2 State: Unstable C2_rx = 0x0 (0) C2_tx = 0xCF (207)
PATH TRACE BUFFER : UNSTABLE
Remote Rx(K1/K2): / Remote Tx(K1/K2): /
BER thresholds: SF = 10e-3 SD = 10e-6
TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6
Clock source: internal (actual) internal (configured)
Optical Power Monitoring (accuracy: +/- 1dB)
Rx power = 0.0 mW, n/a dBm
Tx power = 0.2 mW, -6.7 dBm
Tx laser current bias = 14.1 mA
The following is sample output from the show controllers sonet framers command:
RP/0/RP0/CPU0:router# show controllers sonet 0/1/0/2 framers
PM 5355 asic #0 registers:
0x02 master_intr_sts 0x00
0x80 suni_master_test 0xc0
The following is sample output from the show controllers sonet internal-state command:
RP/0/RP0/CPU0:router# show controllers sonet 0/1/0/2 internal-state
controller(layer) admin_up if_state
----------------------------------------
Table 35 describes the significant fields shown in the display.
Table 35 show controllers sonet Field Descriptions
Field
|
Description
|
Port
|
Slot number of the POS interface.
|
LOF
|
Section loss of frame is detected when a severely error framing (SEF) defect on the incoming SONET signal persist for 3 milliseconds.
|
LOS
|
Section loss of signal is detected when an all-zeros pattern on the incoming SONET signal lasts 19(+-3) microseconds or longer. This defect might also be reported if the received signal level drops below the specified threshold.
|
BIP
|
Bit interleaved parity error reported.
• For B1, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
• For B2, the bit interleaved parity error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
• For B3, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
|
AIS
|
Alarm indication signal.
• Line alarm indication signal is sent by the section terminating equipment (STE) to alert the downstream line terminating equipment (LTE) that a LOS or LOF defect has been detected on the incoming SONET section.
• Path alarm indication signal is sent by the LTE to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.
|
RDI
|
Remote defect indication.
• Line remote defect indication is reported by the downstream LTE when it detects LOF, LOS, or AIS.
• Path remote defect indication is reported by the downstream PTE when it detects a defect on the incoming signal.
|
FEBE
|
Far end block errors.
• Line far end block error (accumulated from the M0 or M1 byte) is reported when the downstream LTE detects BIP(B2) errors.
• Path far end block error (accumulated from the G1 byte) is reported when the downstream PTE detects BIP(B3) errors.
|
LOP
|
Path loss of pointer is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag (NDF) enabled indications.
|
NEWPTR
|
An inexact count of the number of times the SONET framer has validated a new SONET pointer value (H1, H2).
|
PSE
|
An inexact count of the number of times the SONET framer has detected a positive stuff event in the received pointer (H1, H2).
|
NSE
|
An inexact count of the number of times the SONET framer has detected a negative stuff event in the received pointer (H1, H2).
|
Detected/Asserted/Reported Alarms
|
Any alarms detected by the controller are displayed here. Alarms are as follows:
• Transmitter is sending remote alarm.
• Transmitter is sending AIS.
• Receiver has loss of signal.
• Receiver is getting AIS.
• Receiver has loss of frame.
• Receiver has remote alarm.
• Receiver has no alarms.
|
Alarm reporting enabled for
|
Types of alarms that generate an alarm message.
|
Alert reporting enabled for
|
Types of alarms that generate an alert message.
|
Framing
|
Type of framing enabled on the controller.
|
SPE Scrambling
|
Status of synchronous payload envelope (SPE) scrambling: Enabled, Disabled.
|
C2 State
|
The value extracted from the SONET path signal label byte (C2).
|
S1S0(tx)
|
The two S bits received in the last H1 byte.
|
PATH TRACE BUFFER
|
SONET path trace buffer is used to communicate information regarding the remote hostname, interface name/number, and IP address. This is a Cisco-proprietary use of the J1 (path trace) byte.
|
Remote hostname
|
Name of the remote host.
|
Remote interface
|
Interface of the remote host.
|
Remote IP addr
|
IP address of the remote host.
|
Remote Rx(K1/K2)/Tx(K1/K2)
|
Contents of the received and transmitted K1 and K2 bytes.
|
BER thresholds
|
List of the bit error rate (BER) thresholds you configured with the threshold (SONET) command.
|
TCA thresholds
|
List of threshold crossing alarms (TCA) you configured with the threshold (SONET) command.
|
Clock source
|
Actual and configured clock source.
|
Optical Power Monitoring
|
Power status of the SONET controller.
|
PM 5355 asic #0 registers
|
Header for framer register data.
|
shutdown (SONET)
To disable SONET controller processing, use the shutdown command in SONET configuration mode. To bring back up a SONET controller and enable SONET controller processing, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
The SONET controller is up, and SONET controller processing is enabled.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the shutdown command to shut down a SONET controller and disable SONET controller processing. Use the no shutdown command to bring back up a SONET controller and enable SONET controller processing.
The SONET controller must be brought up for the proper operation of the Layer 2 interface. The Layer 2 interface has a separate shutdown command available, which does not operate on the SONET controller's administrative state.
Examples
In the following example, the SONET controller is brought down and SONET controller processing is disabled:
RP/0/RP0/CPU0:router(config)# controller sonet 0/1/0/2
RP/0/RP0/CPU0:router(config-sonet)# shutdown
threshold (SONET)
To set the bit-error rate (BER) threshold values of the specified alarms for a SONET controller, use the threshold command in SONET configuration mode. To remove the setting of the threshold from the configuration file and restore the default condition, use the no form of this command.
threshold {b1-tca | b2-tca | sd-ber | sf-ber} bit-error-rate
no threshold {b1-tca | b2-tca | sd-ber | sf-ber} bit-error-rate
Syntax Description
b1-tca
|
Sets the B1 BER threshold crossing alarm (TCA). Default is 10e-6.
|
b2-tca
|
Sets the B2 BER threshold crossing alarm (TCA). Default is 10e-6.
|
sd-ber
|
Sets the signal degrade BER threshold. Default is 10e-6.
|
sf-ber
|
Sets the signal failure BER threshold. Default is 10e-3.
|
bit-error-rate
|
BER from 3 to 9 (10 to the minus x).
|
Defaults
The default bit-error rate is 10e-6 for b1-tca, b2-tca, and sd-ber.
The default bit-error rate is 10e-3 for sf-ber.
Command Modes
SONET configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For B1, the bit interleaved parity (BIP) error report is calculated by comparing the BIP-8 code with the BIP-8 code that is extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
For B2, the BIP error report is calculated by comparing the BIP-8/24 code with the BIP-8 code that is extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
Signal failure BER and signal degrade BER are sourced from B2 BIP-8 error counts (as is B2-TCA). The b1-tca and b2-tca keywords print only a log message to the console (if reports for them are enabled).
To determine the BER thresholds configured on the controller, use the show controllers sonet command.
Examples
In the following example, thresholds on the SONET controller are configured:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# threshold sd-ber 8
RP/0/RP0/CPU0:router(config-sonet)# threshold sf-ber 4
RP/0/RP0/CPU0:router(config-sonet)# threshold b1-tca 4
Related Commands
Command
|
Description
|
report (SONET)
|
Permits selected SONET alarms to be logged to the console for a SONET controller.
|
show controllers sonet
|
Displays information about the operational status of SONET layers.
|
threshold (SONET path)
To set the bit-error rate (BER) threshold values of the specified alarms for a SONET path, use the threshold command in SONET path configuration mode. To remove the setting of the SONET path threshold from the configuration file and restore the default condition, use the no form of this command.
threshold b3-tca bit-error-rate
no threshold b3-tca bit-error-rate
Syntax Description
b3-tca
|
Sets the B3 BER threshold crossing alarm (TCA). The default BER is 6.
|
bit-error-rate
|
BER from 3 to 9 (10 to the minus x).
|
Defaults
The default BER is 6 for b3-tca.
Command Modes
SONET path configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
For B3, the bit interleaved parity (BIP) error report is calculated by comparing the BIP-8 code with the BIP-8 code that is extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
In addition to BIP errors detected at the local end in the receive direction, B3 error counts detected in the G1 byte (P-REI or P-FEBE) by the far-end SONET equipment are returned.
The b3-tca keyword prints only a log message to the console (if reports for them are enabled).
Examples
In the following example, the BER is set to 4:
RP/0/RP0/CPU0:router(config)# controller sonet 0/1/0/1
RP/0/RP0/CPU0:router(config-sonet)# path
RP/0/RP0/CPU0:router(config-sonet-path)# threshold b3-tca 4
Related Commands
Command
|
Description
|
show controllers sonet
|
Displays information that is specific to SONET controllers.
|
report (SONET)
|
Permits selected SONET alarms to be logged to the console for a SONET controller.
|
uneq-shut (SONET path)
To enable automatic insertion of P-UNEQ code (0x00) in the sent SONET path overhead C2 byte, use the uneq-shut command in SONET path configuration mode. To disable this feature, use the no form of this command.
uneq-shut
no uneq-shut
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
SONET path configuration
Command History
Release
|
Modification
|
Release 2.0
|
This command was introduced.
|
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.
Use the uneq-shut command to disable automatic insertion of P-UNEQ code in the sent SONET path overhead C2 byte whenever the SONET path enters the administratively down state.
Examples
In the following example, automatic insertion of P-UNEQ code is disabled in the sent SONET path overhead C2 byte:
RP/0/RP0/CPU0:router(config)# controller sonet 0/2/0/2
RP/0/RP0/CPU0:router(config-sonet)# path
RP/0/RP0/CPU0:router(config-sonet-path)# uneq-shut