Monitoring Interfaces
To display statistics for channelized SONET and SDH interfaces, use the show controllers sonet command. The following section describes some of the options for the command and shows some sample displays.
From User Exec mode, use the following show commands to monitor and display the T3, T1/E1, and HDLC serial data channel information:
host1#show controllers sonet 2/0 e1Display T3 statistics. host1#show controllers sonet 2/1 ds3Display statistics for the section, line, path, and tributary layers. host1#show controllers sonet 2/1 sectionDisplay the configuration for channelized SONET and SDH interfaces. host1#show controllers sonet 2/0 configurationDisplay statistics for serial interfaces. host1#show interfaces serial 2/0:1/1/1/1/1Setting a Baseline
You can set statistics baselines for serial interfaces, subinterfaces, and circuits using the baseline interface serial command. You can also set statistics baselines for the section, line, and path layers using the baseline interface sonet command. Use the delta options with the show commands to display statistics with the baseline subtracted.
Output Filtering
You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. See JUNOSe System Basics Configuration Guide, Chapter 2, Command-Line Interface, for details.
baseline interface serial
- Use to set a statistics baseline for serial interfaces.
- The router implements the baseline by reading and storing the statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the delta keyword with the show interfaces serial command to view the baseline statistics.
- Example
host1#baseline interface serial 2/0:1/1There is no no version. baseline line interface sonet
- Use to set a statistics baseline for the SONET/SDH line layer.
- The router implements the baseline by reading and storing the MIB statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the total [ delta ] keywords with the show controllers sonet line command to view the baseline statistics.
- Example
host1#baseline line interface sonet 2/0There is no no version. baseline path interface sonet
- Use to set a statistics baseline for the SONET/SDH path layer.
- The router implements the baseline by reading and storing the MIB statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the total [ delta ] keywords with the show controllers sonet path command to view the baseline statistics.
- Example
host1#baseline path interface sonet 2/0:1There is no no version. baseline section interface sonet
- Use to set a statistics baseline for the SONET/SDH section layer.
- The router implements the baseline by reading and storing the MIB statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved.
- Use the total [ delta ] keywords with the show controllers sonet section command to view the baseline statistics.
- Example
host1#baseline section interface sonet 2/0There is no no version. show controllers sonet configuration
- Use to display the configuration for channelized SONET and SDH interfaces.
- Specify an interface in slot/port format.
- To view information for a controller and all layers above that controller, specify a controller. For example, to view all controllers on interface 3/0, use show controllers sonet 3/0 configuration. To view information for path 1 only, use show controllers sonet 3/0:1 configuration.
- Field descriptions
- Interface specifier in slot/port format
- channelizedNumber of channels and speed for the interface
- ifAdminStatusConfigured status of the interface: up or down
- descriptionConfigured description of the controller
- snmp trap link-statusState of SNMP link status processing for the section and line layers of the interface: enabled or disabled
- alarms used for operational status calculationTypes of defects that the router uses to determine the operational status of the interface at the section and line layers
- defect trigger soaking delayTime that the router waits to set an alarm when the router records a defect at the section or line layer
- Operational StatusPhysical state of the interface:
- upInterface is operational
- down, failure alarmInterface is not operational; type of defect that caused failure is specified
- time since last status changeTime since the line module was rebooted
- Loopback StateType of loopback configured at this layer in the interface, or none
- Last Remote Loopback Request Sent
- BERT testNumber of current test and total number of tests
- Test intervalLength of the BERT test
- statusSync (controller is synchronized with remote device) or NoSync (controller is not synchronized with remote device
- Sync countNumber of times the pattern detector synchronized with the incoming data pattern
- Received bit countNumber of bits received
- Error bit countNumber of bits with errors
- internal moduleInternal clock is from the line module itself
- chassisInternal clock is from the configured router clock
- Current section alarmsNumber of suspect bit patterns found in several consecutive frames in section layer, or none
- Current line alarmsNumber of suspect bit patterns found in several consecutive frames in line layer
- Channel configurationParameters for specific controllers; the actual parameters depend on the controller.
- ifAdminStatusState of the controller in the software configuration: up or down
- ifOperStatusPhysical state of the controller: up or down
- Time since last status changeTime the controller has been up or down
- AlarmsNumber of suspect bit patterns found in several consecutive frames
- snmp trap link-statusState of SNMP link status processing for the controller: enabled or disabled
- alarms used for operational status calculationTypes of defects that the router uses to determine the operational status of the interface at the path layer
- defect trigger soaking delayTime that the router waits to set an alarm when the router records a defect at the path layer
- c2 byteSetting of path signal byte: set by upper interface type (automatic setting) or configured value
- Operational StatusPhysical state of this layer: up, down, or lowerLayerDown
- c-bit parity framing (for T3 interfaces)
- M23 multiplexer framing (for T3 interfaces)
- crc4Cyclic redundancy check (for E1 interfaces)
- no-crc4No cyclic redundancy check (for E1 interfaces)
- esfExtended superframe (for T1 interfaces)
- sfSuperframe (for T1 interfaces)
- Line CodeType of line coding the router assigned to the controller: B8ZS or AMI
- Clock sourceType of clock source configured for the channel:
- moduleInternal clock is from the line module itself
- chassisInternal clock is from the configured router clock
- J1 transmit trace messageTrace message sent to the remote device
- J1 expected trace messageTrace message expected from the remote device
- J1 received trace messageTrace message received from the remote device
host1#show controllers sonet 3/0 configurationoc12 3/0non channelizedifAdminStatus: updescription: link1snmp trap link-status: enabledalarms used for operational status calculation: LOS LOF AIS RDIdefect trigger soaking delay: 2500 millisecondsOperational Status: uptime since last status change: 00:03:30Loopback State: noneMode: sonetTiming source: internal moduleReceive FIFO Overruns: 0, Reconfigurations: 0Current section defects: noneCurrent line defects: noneChannel configuration:channel = 0, path = oc12, hierarchy = 1/1/0/0, current path defects: noneifAdminStatus: upsnmp trap link-status: disabledalarms used for operational status calculation: LOP AISdefect trigger soaking delay: 2500 millisecondsc2 byte override 20Operational Status: uptime since last status change: 00:03:30J1 transmit trace message: sonet3/0J1 expected trace message: sonet4/0J1 received trace message: sonet4/0Example 2If you do not specify the layer in the interface, the router shows the configuration for all layers, whether or not you specify the keyword configuration. host1#show controllers sonet 2/1oc3 2/1channelized (3 channels, oc1 minimum speed)ifAdminStatus: updescription: link1snmp trap link-status: enabledalarms used for operational status calculation: LOS LOF AIS RDIdefect trigger soaking delay: 2500 millisecondsOperational Status: uptime since last status change: 00:03:30Operational Status: uptime since last status change: 00:06:49Loopback State: noneMode: sonetTiming source: internal moduleCurrent section alarms: noneCurrent line alarms : noneChannel configuration:channel = 1, path = oc1, hierarchy = 1/1/1/1, current path alarms: noneifAdminStatus: upsnmp trap link-status: disabledalarms used for operational status calculation: LOP AISdefect trigger soaking delay: 2500 millisecondsc2 byte override 20Operational Status: uptime since last status change: 00:06:49Ds3 1, unchannelizedifOperStatus = ifOperUpsnmp trap link-status = disabledFraming is C-BIT, Line Code is B3ZS, Clock Source is Internal - ModuleExample 3This example displays the configuration for T3 1/1 on slot 2, port 1. host1#show controllers sonet 2/1:1/1oc3 2/1channelized (3 channels, oc1 minimum speed)ifAdminStatus: updescription: link1snmp trap link-status: enabledalarms used for operational status calculation: LOS LOF AIS RDIdefect trigger soaking delay: 2500 millisecondsOperational Status: uptime since last status change: 00:03:30Loopback State: noneMode: sonetTiming source: internal moduleCurrent section alarms: noneCurrent line alarms : noneChannel configuration:channel = 1, path = oc1, hierarchy = 1/1/1/1, current path alarms: noneifAdminStatus: upsnmp trap link-status: disabledalarms used for operational status calculation: LOP AISdefect trigger soaking delay: 2500 millisecondsc2 byte override 20Operational Status: uptime since last status change: 00:05:37Ds3 1, unchannelizedifOperStatus = ifOperUpsnmp trap link-status = disabledFraming is C-BIT, Line Code is B3ZS, Clock Source is Internal - Moduleshow controllers sonet ds1|e1
- Use to display E1 or T1 (DS1) statistics for the different layers in channelized SONET and SDH interfaces. Figure 8 shows the layers in the interface.
- For definitions of the MIB statistics, see RFC 2495Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types (January 1999).
- Specify an interface in slot/port format.
- To view information for a specific controller in a layer, enter the specifier for the controller and the type for the controller. For example, to view the E1 controller 1/1/1 on path 1 on the interface 4/0, enter show controllers sonet 4/0:1/1/1/1 e1.
- To view information for all controllers above a particular layer, enter the specifier for the layer and the type for the controller. For example, to view all E1 controllers on the interface 4/0 path 1, enter show controllers sonet 4/0:1 e1.
- To view E1 or T1 statistics for a layer, specify the controller type, e1 or ds1.
- To view the configuration for a controller or all controllers in a layer, omit the controller type.
- Field descriptions
- DescriptionText description or alias if configured for the interface
- BERT testNumber of current test and total number of tests
- Test intervalLength of the BERT test
- statusSync (controller is synchronized with remote device) or NoSync (controller is not synchronized with remote device
- Sync countNumber of times the pattern detector synchronized with the incoming data pattern
- Received bit countNumber of bits received
- Error bit countNumber of bits with errors
- Number of valid intervalsNumber of 15-minute intervals since the line module was last powered on or reset
- Time elapsed in current intervalReported in 15-minute intervals
- Errored secondsNumber of errored seconds encountered by a T1 or an E1 in the current interval
- Severely errored secondsNumber of severely errored seconds encountered by a T1 or an E1 in the current interval
- Severely errored frame secondsNumber of severely errored framing seconds encountered by a T1 or an E1 in the current interval
- Unavailable secondsNumber of unavailable seconds encountered by a T1 or an E1 in the current interval
- Clock slip secondsNumber of clock slips encountered by a T1 or an E1 in the current interval
- Path code violationsNumber of coding violations encountered by a T1 or an E1 in the current interval
- Line errored secondsNumber of line errored seconds encountered by a T1 or an E1 in the current interval
- Bursty errored secondsNumber of bursty errored seconds encountered by a T1 or an E1 in the current interval
- Degraded minutesNumber of minutes that a T1 or an E1 line is degraded
- Line code violationsNumber of line code violations encountered by a T1 or an E1 in the current interval
host1#show controllers sonet 2/0 e1E1 1/1/1Description: boston111 e1BERT test - 2 in 11Test Interval 1 minute(s), Running - Status is Sync0 minute(s), 33 second(s) left in test intervalSync count = 1Received bit count = 41472000Error bit count = 0Number of valid interval - 0Time elapse in current interval - 0Current Interval CountersErrored seconds = 0Severely errored second = 0Severely errored frame seconds = 0Unavailable seconds = 0Clock slip seconds = 0Path code violations = 0Line errored seconds = 0Bursty errored seconds = 0Degraded minutes = 0Line code violations = 024 Hour Total CountersErrored seconds = 0Severely errored second = 0Severely errored frame seconds = 0Unavailable seconds = 0Clock slip seconds = 0Path code violations = 0Line errored seconds = 0Bursty errored seconds = 0Degraded minutes = 0Line code violations = 0show controllers sonet ds3
- Use to display T3 statistics for the different layers in channelized SONET and SDH interfaces. Figure 8 shows the layers in the interface.
- For definitions of the MIB statistics, see RFC 2496Definitions of Managed Objects for the DS3/E3 Interface Types (January 1999).
- Specify an interface in slot/port format.
- To view information for a specific controller in a layer, enter the specifier for the controller and the type for the controller. For example, to view T3 controller 1 on path 1 on the interface 4/0, enter show controllers sonet 4/0:1/1 ds3.
- To view information for all controllers above a particular layer, enter the specifier for the layer and the type for the controller. For example, to view all DS3 controllers on the interface 4/0, enter show controllers sonet 4/0 ds3.
- To view T3 statistics for a layer, specify the controller type, ds3.
- To view the configuration for a controller or all controllers in a layer, omit the controller type.
- Field descriptions
- DescriptionText description or alias if configured for the interface
- BERT testNumber of current test and total number of tests
- Test intervalLength of the BERT test
- statusSync (controller is synchronized with remote device) or NoSync (controller is not synchronized with remote device
- Sync countNumber of times the pattern detector synchronized with the incoming data pattern
- Received bit countNumber of bits received
- Error bit countNumber of bits with errors
- Number of valid intervalsNumber of 15-minute intervals since the line module was last powered on or reset
- Time elapse in current intervalTime (seconds) passed in current interval
- Current Interval CountersStatistics for the current 15-minute interval
- P-bit errored secondsNumber of errored seconds encountered by a T3
- P-bit severely errored secondsNumber of severely errored seconds encountered by a T3
- Severely errored frame secondsNumber of severely errored framing seconds encountered by a T3
- Unavailable secondsNumber of unavailable seconds encountered by a T3
- Line code violationsNumber of line code violations encountered by a T3
- P-bit coding violationsNumber of coding violations encountered by a T3
- Line errored secondsNumber of line errored seconds encountered by a T3
- C-bit coding violationsNumber of C-bit coding violations encountered by a T3
- C-bit errored secondsNumber of C-bit errored seconds encountered by a T3
- C-bit severely errored secondsNumber of C-bit severely errored seconds encountered by a T3
- 24 Hour Total countersStatistics for last 24 hours
host1#show controllers sonet 2/1 ds3Ds3 1Description: ottawa211 ds3Number of valid interval - 0Time elapse in current interval - 696Current Interval CountersP-bit errored seconds = 0P-bit severely errored seconds = 0Severely errored frame seconds = 0Unavailable seconds = 541Line code violations = 0P-bit coding violations = 0Line errored seconds = 0C-bit coding violations = 0C-bit errored seconds = 0C-bit severely errored seconds = 024 Hour Total CountersP-bit errored seconds = 0P-bit severely errored seconds = 0Severely errored frame seconds = 0Unavailable seconds = 0Line code violations = 0P-bit coding violations = 0Line errored seconds = 0C-bit coding violations = 0C-bit errored seconds = 0C-bit severely errored seconds = 0Example 2This example shows statistics for the T3 controller 1/1 on interface 2/0. host1#show controllers sonet 2/0:1/1 ds3Ds3 1Description: ottawa2011 ds3Number of valid interval - 0Time elapse in current interval - 534Current Interval CountersP-bit errored seconds = 0P-bit severely errored seconds = 0Severely errored frame seconds = 0Unavailable seconds = 117Line code violations = 0P-bit coding violations = 0Line errored seconds = 0C-bit coding violations = 0C-bit errored seconds = 0C-bit severely errored seconds = 024 Hour Total CountersP-bit errored seconds = 0P-bit severely errored seconds = 0Severely errored frame seconds = 0Unavailable seconds = 0Line code violations = 0P-bit coding violations = 0Line errored seconds = 0C-bit coding violations = 0C-bit errored seconds = 0C-bit severely errored seconds = 0show controllers sonet line | path | section | tributary
- Use to display statistics for the different layers in channelized SONET and SDH interfaces. Figure 8 shows the layers in the interface.
- For definitions of the MIB statistics, see RFC 2558Definitions of Managed Objects for the SONET/SDH Interface Type (March 1999).
- Specify an interface in slot/port format.
- To view information for a specific controller in a layer, enter the specifier for the controller and the type for the controller. For example, to view tributary 1/1/1 on path 1 of interface 4/0, enter show controllers sonet 4/0:1/1/1/1 tributary.
- To view information for all controllers above a particular layer, enter the specifier for the layer and the type for the controller. For example, to view all tributaries on path 1 of interface 4/0, enter show controllers sonet 4/0:1 tributary.
- To view statistics for a layer, specify the type of layer.
- To view the configuration for a controller or all controllers in a layer, omit the controller type.
- To view all statistics for all sessions, specify the total keyword.
- To view baselined statistics for all intervals, specify the delta total keywords.
- Field descriptions
- Errored secondsNumber of errored seconds encountered by a T1 or an E1 in an interval
- Severly errored secondsNumber of severely errored seconds encountered in an interval
- Severly errored framing secondsNumber of severely errored framing seconds encountered in an interval
- Coding violationsNumber of coding violations encountered in an interval
- Unavailable secondsNumber of unavailable seconds encountered in an interval
- Last Interval CountersStatistics for the previous 15-minute interval
- Current Far End Interval CountersStatistics for the remote connection associated with the SONET/SDH path in the current 15-minute interval
- Last Far End Interval CountersStatistics for the remote connection associated with the SONET/SDH path in the previous 15-minute interval
- Total interval countersShows the statistics for all intervals or baselined statistics
host1#show controllers sonet 2/1 sectionCurrent Section Interval CountersCurrent status = No DefectErrored seconds = 0Severly errored seconds = 0Severely errored framing seconds = 0Coding violations = 0Last Section Interval CountersErrored seconds = 0Severly errored seconds = 0Severely errored framing seconds = 0Coding violations = 0Example 2This example illustrates the behavior of the baseline section interface sonet command. The examples show the MIB statistics of the section layer before and after the command is issued. host1#show controllers sonet 2/0 section totalNumber of valid intervals - 0Time elapsed in current interval - 192Current Section Interval CountersCurrent status = No DefectErrored seconds = 68Severly errored seconds = 68Severely errored framing seconds = 2Coding violations = 4018Total Section CountersErrored seconds = 68Severly errored seconds = 68Severely errored framing seconds = 2Coding violations = 4018host1#baseline section interface sonet 2/0host1#show controllers sonet 2/0 section total deltaNumber of valid intervals - 0Time elapsed in current interval - 209Current Section Interval CountersCurrent status = No DefectErrored seconds = 68Severly errored seconds = 68Severely errored framing seconds = 2Coding violations = 4018Total Section CountersErrored seconds = 0Severly errored seconds = 0Severely errored framing seconds = 0Coding violations = 0Example 3This example shows the MIB statistics for the line layer on interface 2/1. host1#show controllers sonet 2/1 lineCurrent Line Interval CountersCurrent status = No DefectErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 190Last Line Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 900Current Far End Line Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Far End Last Line Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Example 4This example shows the MIB statistics for the path layer on interface 2/1. host1#show controllers sonet 2/1 pathChannel number 1Current Path Interval CountersCurrent status = No DefectErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 248Last Path Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Current Far End Path Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 248Far End Last Path Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Example 5This example displays the tributary statistics for all tributaries on interface 4/0, path 1. host1#show controllers sonet 4/0:1 tributaryTributary 1/1/1Current Tributary Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Last Tributary Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Current Far End Path Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Far End Last Tributary Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Example 6This example displays the tributary statistics for the tributary 1/1/1 on path 1 on slot 4, port 0. host1#show controllers sonet 4/0:1/1/1/1 tributaryTributary 1/1/1Current Tributary Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Last Tributary Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Current Far End Path Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0Far End Last Tributary Interval CountersErrored seconds = 0Severly errored seconds = 0Coding violations = 0Unavailable seconds = 0show controllers sonet remote
- Use to display MIB statistics for the remote end of a channelized T3 interface configured for MDL or for the remote end of a T1 channel configured for FDL.
- Specify the all option to display detailed information for all 15-minute intervals.
- For definitions of the MIB statistics for a T3 connections, see RFC 2496Definitions of Managed Objects for the DS3/E3 Interface Types (January 1999).
- For definitions of the MIB statistics for a T1 connections, see RFC 2495Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types (January 1999).
- Field descriptions for a T3 interface
- Far End Equipment Identification Codeeic string sent by remote device for MDL
- Far End Line Identification Codelic string sent by remote device for MDL
- Far End Frame Identification Codefic string sent by remote device for MDL
- Far End Unit Identification Codeunit string sent by remote device for MDL
- Far End Facility Identification Codepfi string sent by remote device for MDL
- Far End Generator Numbergenerator string sent by remote device for MDL
- Far End Port Numberport string sent by remote device for MDL
- Number of valid intervalsNumber of 15-minute intervals since the line module was last powered on or reset
- Time elapse in current intervalNumber of seconds that have passed in the 15-minute (900-second) interval
- C-bit errored secondsNumber of C-bit errored seconds encountered by a T3 in the current interval
- C-bit severely errored secondsNumber of C-bit severely errored seconds encountered by a T3 in the current interval
- C-bit coding violationsNumber of C-bit coding violations encountered by a T3 in the current interval
- Unavailable secondsNumber of unavailable seconds encountered by a T3 in the current interval
- Invalid secondsNumber of seconds when statistics were not collected
- DS1Identifier of T1 channel
- Number of valid intervalsNumber of 15-minute intervals since the line module was last powered on or reset
- Time elapse in current intervalNumber of seconds that have passed in the 15-minute (900-second) interval
- Far End FDL Carrier bitStatus of FDL configuration on remote device connected to T1 channel
- Far End Equipment Identification Codeeic string sent by remote device for FDL
- Far End Line Identification Codelic string sent by remote device for FDL
- Far End Frame Identification Codefic string sent by remote device for FDL
- Far End Unit Identification Codeunit string sent by remote device for FDL
- Far End Facility Identification Codepfi string sent by remote device for FDL
- Far End Generator Numbergenerator string sent by remote device for FDL
- Far End Port Numberport string sent by remote device for FDL
- Errored secondsNumber of errored seconds encountered by a T1 in the current interval
- Severely errored secondsNumber of severely errored seconds encountered by a T1 in the current interval
- Severely errored frame secondsNumber of severely errored framing seconds encountered by a T1 in the current interval
- Unavailable secondsNumber of unavailable seconds encountered by a T1 in the current interval
- Clock slip secondsNumber of clock slips encountered by a T1 in the current interval
- Path code violationsNumber of coding violations encountered by a T1 in the current interval
- number of coding violations encountered by a T1 in the current interval
- Line errored secondsNumber of line errored seconds encountered by a T1 in the current interval
- Bursty errored secondsNumber of bursty errored seconds encountered by a T1 in the current interval
- Degraded minutesNumber of minutes that a T1 line is degraded
host1#show controllers sonet 5/0:1/1 remoteFar End MDL Carrier bit is not setFar End Equipment Identification Code is the null stringFar End Line Identification Code is the null stringFar End Frame Identification Code is the null stringFar End Unit Identification Code is the null stringFar End Facility Identification Code is the null stringFar End Generator Number is the null stringFar End Port Number is the null stringNumber of valid interval - 3Time elapse in current interval - 756Ds3 Current Interval CountersC-bit errored seconds = 0C-bit severely errored seconds = 0C-bit coding violations = 0Unavailable seconds = 0Invalid seconds = 0Ds3 Last Interval CountersC-bit errored seconds = 0C-bit severely errored seconds = 0C-bit coding violations = 0Unavailable seconds = 0Invalid seconds = 0Ds3 24 Hour Total CountersC-bit errored seconds = 1C-bit severely errored seconds = 1C-bit coding violations = 330Unavailable seconds = 0Invalid seconds = 0Example 2In this example, a T1 channel on a T3 over channelized SONET interface is specified. host1#show controllers sonet 5/0:1/1/1 remoteDS1 10/1:1Number of valid interval - 0Time elapse in current interval - 0Far End FDL Carrier bit is not setFar End Equipment Identification Code is the null stringFar End Line Identification Code is the null stringFar End Frame Identification Code is the null stringFar End Unit Identification Code is the null stringFar End Facility Identification Code is the null stringFar End Port Number is the null stringFar End Generator Number is the null stringDS1 Current Interval CountersErrored seconds = 0Severely errored second = 0Severely errored frame seconds = 0Unavailable seconds = 0Clock slip seconds = 0Path code violations = 0Line errored seconds = 0Bursty errored seconds = 0Degraded minutes = 0DS1 24 Hour Total CountersErrored seconds = 0Severely errored second = 0Severely errored frame seconds = 0Unavailable seconds = 0Clock slip seconds = 0Path code violations = 0Line errored seconds = 0Bursty errored seconds = 0Degraded minutes = 0Example 3In this example, a T1 over channelized SONET interface is specified. host1#show controllers sonet 5/0:1/1/1/2/2 remoteDS1 10/1:1Number of valid interval - 0Time elapse in current interval - 0Far End FDL Carrier bit is not setFar End Equipment Identification Code is the null stringFar End Line Identification Code is the null stringFar End Frame Identification Code is the null stringFar End Unit Identification Code is the null stringFar End Facility Identification Code is the null stringFar End Port Number is the null stringFar End Generator Number is the null stringDS1 Current Interval CountersErrored seconds = 0Severely errored second = 0Severely errored frame seconds = 0Unavailable seconds = 0Clock slip seconds = 0Path code violations = 0Line errored seconds = 0Bursty errored seconds = 0Degraded minutes = 0DS1 24 Hour Total CountersErrored seconds = 0Severely errored second = 0Severely errored frame seconds = 0Unavailable seconds = 0Clock slip seconds = 0Path code violations = 0Line errored seconds = 0Bursty errored seconds = 0Degraded minutes = 0show interfaces serial
- Serial InterfaceLocation of the interface
- DescriptionText description or alias if configured for the interface
- ifOperStatusPhysical state of the interface
- ifOperDownInterface is not functioning
- ifOperLowerLayerDownLower layer in the interface stack is not functioning
- ifOperNotPresentModule has been removed from the chassis
- ifOperTestingInterface is being tested
- ifOperUpInterface is functioning
- snmp trap link-statusEnabled or disabled
- EncapsulationLayer 2 encapsulation display; options: ppp, frame-relay ietf, mlppp, mlframe-relay ietf, hdlc
- Crc type checkingSize of the CRC
- Hdlc mruCurrent size of the MRU
- Hdlc mtuCurrent size of the MTU
- Hdlc interface speedCurrent line speed of the interface
- Hdlc idle-characterCurrent idle character
- Invert data disabledStatus of the data inversion feature
- Ds0 modeNx56 or Nx64
- 5 minute input rateData rates based on the traffic received in the last five minutes
- 5 minute output rateData rates based on the traffic sent in the last five minutes
- Interface Statistics
- Packets receivedNumber of packets received on the interface
- Bytes receivedNumber of bytes received on the interface
- Errored packets receivedNumber of packets with errors received on the interface
- Packets sentNumber of packets sent on the interface
- Bytes sentNumber of bytes sent on the interface
- Errored packets sentNumber of packets with errors sent from the interface
host1#show interfaces serial 2/0:1/1/1/1/1Serial Interface at 2/0:1/1/1/1/1Description: toronto20 hdlc channelifOperStatus = ifOperUpsnmp trap link-status = disabledEncapsulation hdlcCrc type checking - CRC16Hdlc mru = 1600Hdlc mtu = 1600Hdlc interface speed = 1536000Hdlc idle-character marksInvert data disabled, Ds0 time slot map = 0xffffffDs0 mode = Nx645 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/secInterface statisticsPackets received 100Bytes received 1300Errored packets received 1Packets sent 100Bytes send 1436Errored packets sent 0Monitoring APS/MSP
For information about monitoring APS/MSP, see Monitoring APS/MSP in Chapter 3, Configuring Unchannelized OCx/STMx Interfaces.