|
Interface
|
Identifies
the WAN physical interface, in the format
rack/slot/module/port.
-
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. Shared port adapters (SPAs) are referenced by their subslot
number.
-
port: Physical port number of the interface.
|
|
Configuration Mode
|
Current
configuration mode running on this controller. Can be WAN mode or LAN mode.
|
|
SECTION
|
Displays
the following section alarms:
- LOF—Number of Loss of
Framing (LOF) errors on this connection section. LOF alarms are critical
because they indicate that the link associated with this section is down.
- LOS—Number of loss of
signal (LOS) errors on this connection section. LOS alarms are critical because
they indicate that the link associated with this section is down.
- BIP(B1)—Number of bit
interleaved parity (BIP) B1 errors on this section that exceeded the specified
threshold.
|
|
LINE
|
Displays
the following line alarms:
- AIS—Number of AIS errors on
this line. AIS alarms are critical because they indicate that the line is down.
- RDI—Remote defect
indication.
-
Line remote defect indication is reported by the downstream LTE
when it detects LOF4, LOS5, or AIS6.
-
Path remote defect indication is reported by the downstream PTE
when it detects a defect on the incoming signal.
- FEBE—Number of far-end
block errors (FEBE) on this line. Line FEBE errors are accumulated from the M0
or M1 byte, and are reported when the downstream LTE detects BIP7 (B2) errors.
- BIP(B2)—Number of bit
interleaved parity (BIP) B2 errors on this line that exceeded the specified
threshold.
|
|
PATH
|
Displays
the following path alarms:
- AIS—Number of AIS errors on
this path. AIS alarms are critical because they indicate that the line
associated with this path is down.
- RDI—Number of RDI errors on this path. Path RDI is a legacy alarm and is not supported.
- FEBE—Number of FEBE errors
on this path. Path FEBEs are accumulated from the G1 byte, and are reported
when the downstream PTE detects BIP (B3) errors.
- BIP(B2)—Number of bit
interleaved parity (BIP) errors on this path that exceeded the specified
threshold.
- LOP—Number of loss of
pointer (LOP) errors on this path. Path LOPs are reported as a result of an
invalid pointer (H1, H2) or an excess number of new data flag enabled
indications.
- NEWPTR—Inexact count of the
number of times the SONET framer has validated a new SONET pointer value (H1,
H2).
- PSE—Inexact count of the
number of times the SONET framer has detected a positive stuff event (PSE) in
the received pointer (H1, H2).
- NSE—Inexact count of the
number of times the SONET framer has detected a negative stuff event in the
received pointer (H1, H2).
|
Note
|
For
Cisco IOS XR software release 3.5.0, the following fields display no
errors:RDIFEBEBIP(B2)NEWPTRPSENSE
|
|
|
WIS ALARMS
|
Displays
the following WAN Interconnect Sublayer (WIS) layer alarms:
- SER—Number of Severely
Errored Frames (SER) errors
- FELCDP—Number of Far End -
Loss of Code-group Delineation - Path (FELCDP) errors
- FEAISP—Number of Far End -
AIS - Path (FEAISP) errors
- WLOS—Number of WIS LOS
(WLOS) errors.
- PLCD—Number of Path Loss of
Code-group Delineation (PLCD) errors
- LFEBIP—Number of Line - Far
End - BIP (LFEBI) errors
- PBEC—Number of Path - Block
Error Counter (PBEC) errors
|
Note
|
Alarms
are applicable only when the controller is configured in WAN-PHY mode.
|
|
|
Active
Alarms[All defects]
|
Total
number of currently active alarms on this interface.
|
Note
|
Alarms
are applicable only when the controller is configured in WAN-PHY mode.
|
|
|
Active
Alarms[Highest Alarms]
|
Total
number of the most significant active alarms on this interface. These alarms
are likely causing all other alarms on the interface.
|
Note
|
Alarms
are applicable only when the controller is configured in WAN-PHY mode.
|
|
|
Rx(K1/K2)
|
Total
number of errored K1/K2 bytes from the Line OverHead (LOH) of the SONET frame
that were received by this interface.
|
|
Tx(K1/K2)
|
Total
number of errored K1/K2 bytes from the Line OverHead (LOH) of the SONET frame
that were transmitted by this interface.
|
|
S1S0
|
Number of
errored payload pointer bytes on this interface.
|
|
C2
|
Number of
errored STS identifier (C1) bytes on this interface.
|
|
PATH TRACE
BUFFER
|
Rx J1
trace buffer received from the far end. If the received data is valid it will
be shown below the PATH TRACE BUFFER field.
|
|
Remote IP
addr
|
Byte
string containing the IP address of the remote end of this connection. If the
received data is invalid, this field displays no IP address.
|
|
BER
thresholds
|
BER
threshold values of the specified alarms for a the 10-Gigabit Ethernet
controller.
|
|
TCA
thresholds
|
TCA
threshold values of the specified alarms for a the 10-Gigabit Ethernet
controller.
|
|
REGISTERS
|
Displays
output from the following registers in hexadecimal format:
- P_FEBE—Total number of Far
End Block Errors (FEBEs) that occurred on the path that is associated with this
interface.
- L_FE_BIP—Total number of
far end BIP errors that occurred on this interface.
- L_BIP—Total number of local
BIP errors that occurred on this interface.
- P_BEC—Total BIP error count
(BEC) that occurred on the path that is associated with this interface.
- S_BIP—Total number of far
end BIP errors that occurred on the current section.
- J1-Rx0—Characters from far
end IPV4 address string.
- J1-Rx1—Characters from far
end IPV4 address string.
- J1-Rx2—Characters from far
end IPV4 address string.
- J1-Rx3—Characters from far
end IPV4 address string.
- J1-Rx4—Characters from far
end IPV4 address string.
- J1-Rx5—Characters from far
end IPV4 address string.
- J1-Rx6—Characters from far
end IPV4 address string.
- J1-Rx7—Characters from far
end IPV4 address string.
|
Note
|
The
following Serdes-WIS HW registers are used to debug counters and can be cleared
only by power cycling the hardware:P_FEBEL_FE_BIPL_BIPP_BECS_BIPThe J1-Rx
registers (J1-Rx0 through J1-Rx7) comprise the raw 16 bytes of data received
from the Rx J1 Path Trace Buffer, and are used to debug IPV4 address sent from
far end.
|
|
|
Internal
Information
|
Displays
the following internal information for the interface:
- Operational Mode—Current
operation mode for this controller. Can be WAN mode or LAN mode.
- Current Alarms—Bit map of
all currently active alarms on this controller. Use this information for
debugging purposes.
|
Note
|
Alarms
are applicable only when the controller is configured in WAN-PHY mode.
|
|
Feedback