 |
Note: If you are accessing the router from the console connection, make sure you set the CLI terminal type using the set cli terminal command. |
Purpose
By monitoring Channelized OC12 interfaces, you begin the process of isolating Channelized OC12 interface problems when they occur.
To monitor your Channelized OC12 interfaces, follow these steps:
To display the status of Channelized OC12 interfaces, use the following JUNOS command-line interface (CLI) operational mode command:
Sample Output 1
The following sample output is for a Channelized OC12 interface:
user@host> show interfaces terse t3-0/3/0:* Interface Admin Link Proto Local Remote t3-0/3/0:0 up up t3-0/3/0:1 up up t3-0/3/0:2 up up t3-0/3/0:3 up up t3-0/3/0:4 up up t3-0/3/0:5 up up t3-0/3/0:6 up up t3-0/3/0:7 up up t3-0/3/0:8 up up t3-0/3/0:9 up up t3-0/3/0:10 up up t3-0/3/0:11 up down
Meaning
The sample output shows the status of both the physical and logical interfaces. In this example, all of the Channelized OC12 interfaces are up except the channel interface t3-0/3/0:11.
When only one or some individual T3 channels are down, you must troubleshoot the T3 channel by checking the configuration, transmission network, and equipment. If all of the physical layers for the T3 channels are down, you must work with this as a T3 or OC12 SONET link, or a Physical Interface Card (PIC) problem. For more information on monitoring SONET interfaces, see Monitor Channelized OC12 Interfaces.
To display the status of specific Channelized OC12 interface, use the following JUNOS CLI operational mode command:
Sample Output
user@host> show interfaces terse t3-0/3/0:0
Interface Admin Link Proto Local Remote t3-0/3/0:0 up up user@host> show interfaces terse t3-0/3/0:11 Interface Admin Link Proto Local Remote t3-0/3/0:11 up down
Meaning
The first line of the output shows the status of the link. If this line shows that the physical link is up, the physical link is healthy and can pass packets. If this line shows that the physical link is down, the physical link is unhealthy and cannot pass packets.
When only one or some individual T3 channels are down, you must troubleshoot the T3 channel by checking the configuration, transmission network, and equipment. If all of the physical layers for the T3 channels are down, you must work with this as an OC12 SONET link or PIC problem. For more information on monitoring SONET interfaces, see Monitor Channelized OC12 Interfaces.
To display extensive status information for a Channelized OC12 interface, use the following JUNOS CLI operational mode command:
Sample Output
user@host> show interfaces t3-0/3/0:0
extensive Physical interface: t3-0/3/0:0, Enabled, Physical link is Up
Interface index: 193, SNMP ifIndex: 118, Generation: 122
Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: T3,
Loopback: Local, SONET Loopback: None, FCS: 16, Mode: C/Bit parity
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags : Keepalives
Hold-times : Up 0 ms, Down 0 ms
CoS queues : 4 supported
Last flapped : 2004-05-21 15:23:34 UTC (01:59:02 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Bucket drops: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0
DS3 alarms : None
SONET alarms : None
DS3 defects : None
SONET defects : None
DS3 media: Seconds Count State
AIS 0 0 OK
LOF 0 0 OK
LOS 0 0 OK
IDLE 0 0 OK
YELLOW 0 0 OK
BPV 0 0
EXZ 0 0
LCV 0 0
PCV 0 0
CCV 0 0
LES 0
PES 0
PSES 0
CES 0
CSES 0
SEFS 0
UAS 0
HDLC configuration:
Policing bucket: Disabled
Shaping bucket : Disabled
Giant threshold: 4484, Runt threshold: 3
Idle cycle flag: flags, Start end flag: shared
DSU configuration:
Compatibility mode: None, Scrambling: Disabled, Subrate: Disabled
FEAC loopback: Inactive, Response: Disabled, Count: 0
DS-3 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Algorithm: 2^3 - 1, Pseudorandom (1), Induced error rate: 10e-0
Interface transmit queues:
B/W WRR Packets Bytes
Queue0 0 0
Transmitted: 0 0
Drops: 0 0
Errors: 0
Queue1 0 0
Transmitted: 0 0
Drops: 0 0
Errors: 0
Queue2 0 0
Transmitted: 0 0
Drops: 0 0
Errors: 0
Queue3 0 0
Transmitted: 0 0
Drops: 0 0
Errors: 0
SONET PHY: Seconds Count State
PLL Lock 0 0 OK
PHY Light 0 0 OK
SONET section:
BIP-B1 1 22
SEF 0 0 OK
LOS 0 0 OK
LOF 0 0 OK
ES-S 1
SES-S 0
SEFS-S 0
SONET line:
BIP-B2 1 307
REI-L 0 0
RDI-L 3 1 OK
AIS-L 0 0 OK
BERR-SF 0 0 OK
BERR-SD 0 0 OK
ES-L 1
SES-L 0
UAS-L 0
ES-LFE 3
SES-LFE 3
UAS-LFE 0
SONET path:
BIP-B3 1 35
REI-P 1 7
LOP-P 0 0 OK
AIS-P 0 0 OK
RDI-P 0 0 OK
UNEQ-P 0 0 OK
PLM-P 1 1 OK
ES-P 1
SES-P 0
UAS-P 0
ES-PFE 1
SES-PFE 0
UAS-PFE 0
Received SONET overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x04, C2(cmp) : 0x04, F2 : 0x00
Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00
Transmitted SONET overhead:
F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x04, F2 : 0x00, Z3 : 0x00
Z4 : 0x00
Received path trace: t3-0/1/0:0
74 33 2d 30 2f 31 2f 30 3a 30 00 00 00 00 0d 0a t3-0/1/0:0......
Transmitted path trace: t3-0/3/0:0
74 33 2d 30 2f 33 2f 30 3a 30 00 00 00 00 00 00 t3-0/3/0:0......
Packet Forwarding Engine configuration:
Destination slot: 0, PLP byte: 1 (0x00)
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % bytes
0 best-effort 95 42499200 95 0 low none
3 network-control 5 2236800 5 0 low none
Meaning
The sample output shows where the errors might be occurring, either with the T3 media or the SONET layer. In this example, there are no SONET or DS3 alarms or defects. However, if errors occur, you must troubleshoot the T3 media or the SONET layer. For more information on diagnosing a T3 media problem, seeInvestigate T3 Interfaces. For more information about diagnosing a SONET layer problem, see .
To monitor statistics for a Channelized OC12 interface, use the following JUNOS CLI operational mode command:
Sample Output
user@host> monitor interfaces t3-0/3/0:11 host Seconds: 12 Time: 17:27:15
Delay: 32/0/32
Interface: t3-0/3/0:11, Enabled, Link is Down
Encapsulation: Cisco-HDLC, Keepalives, Speed: T3
Traffic statistics: Current delta
Input bytes: 109846 (176 bps) [44]
Output bytes: 110308 (176 bps) [44]
Input packets: 1687 (1 pps) [2]
Output packets: 1693 (1 pps) [2]
Encapsulation statistics:
Input keepalives: 8 [2]
Output keepalives: 7 [2]
Error statistics:
Input errors: 0 [0]
Input drops: 0 [0]
Input framing errors: 1066 [0]
Input runts: 0 [0]
Input giants: 0 [0]
Policed discards: 0 [0]
L3 incompletes: 0 [0]
L2 channel errors: 3 [0]
L2 mismatch timeouts: 0 [0]
Carrier transitions: 7 [0]
Output errors: 0 Output drops: [0]
Interface warnings:
o Loopback detected while not in test mode
Meaning
The sample output shows common interface failures, indicates whether loopback is detected, and shows increases in framing errors. Use information from this command to help narrow down possible causes of an interface problem.
|
Note: If you are accessing the router from the console connection, make sure you set the CLI terminal type using the set cli terminal command. |
 |
Caution: We recommend that you use this command only for diagnostic purposes. Do not leave it on during normal router operations because real-time monitoring of traffic consumes additional CPU and memory resources. |
