Table Of Contents
Troubleshooting Interfaces
Verifying and Troubleshooting Configured Interfaces
Verifying and Troubleshooting Pluggable Optical Interfaces
Troubleshooting Common Issues with Bundle Interfaces
Troubleshooting Interfaces
This chapter describes techniques that you can use to troubleshoot interfaces. It includes the following sections:
•
Verifying and Troubleshooting Configured Interfaces
•
Verifying and Troubleshooting Pluggable Optical Interfaces
•
Troubleshooting Common Issues with Bundle Interfaces
Verifying and Troubleshooting Configured Interfaces
To troubleshoot the configured interfaces on Cisco IOS XR software, perform the following procedure.
SUMMARY STEPS
1.
show interfaces type instance
2.
show controllers interface-type interface-instance stats
3.
show netio idb interface-type interface-instance
4.
show controllers plim asic statistics interface type instance
or
show hw-module subslot address counters mac index
or
show hw-module subslot counters framer
5.
Contact Cisco Technical Support if the problem is not resolved.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show interfaces type instance
Example:
RP/0/RP0/CPU0:router# show interfaces
gigabitEthernet 0/0/0/0
|
Displays statistics for all interfaces configured on the specified node. Check for interface errors.
|
Step 2
|
show controllers interface-type
interface-instance stats
Example:
RP/0/RP0/CPU0:router# show controllers
gigabitEthernet 0/0/0/0 stats
|
Displays interface controller status and configuration statistics for the specified node. Check for input drops.
If input drops are found, contact Cisco Technical Support. For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
|
Step 3
|
show netio idb interface-type
interface-instance
Example:
RP/0/RP0/CPU0:router# show netio idb
gigabitEthernet 0/0/0/0
|
Displays network input and output information for a specified node.
Check the software counters for the interface. Under Chains and Protocol chains in the output check if any drops occurred at a particular point in the Encap or Decap of the packet. The drops are displayed in the column on the right, showing drop packets and bytes for each step in the chain.
|
Step 4
|
show controllers plim asic statistics interface
type instance
or
show hw-module subslot address counters mac
index
or
show hw-module subslot counters framer
Example:
RP/0/RP0/CPU0:router# show controllers plim
asic statistics interface tenGigE 1/3/0/0
or
RP/0/RP0/CPU0:router# show hw-module subslot
0/0/0 counters mac 0
or
RP/0/RP0/CPU0:router# show hw-module subslot
counters framer
|
• Use the show controllers plim command for fixed PLIMs. Check for interface drops on fixed physical layer interface modules (PLIMs).
• Use the show hw-module subslot address counters mac command and show hw-module subslot counters framer command for shared port adapters (SPAs). Check for interface drops on SPAs.
Check the application-specific integrated circuit (ASIC) counters for drop counters or error counters incrementing for the interface.
|
Step 5
|
Contact Cisco Technical Support.
|
For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
|
The following example shows POS 0/0/1/0 with no input drop counters.
RP/0/RP0/CPU0:router# show interfaces pos 0/0/1/0
POS0/0/1/0 is up, line protocol is up
Hardware is Packet over SONET/SDH
Internet address is 172.18.140.1/24
MTU 4474 bytes, BW 155520 Kbit
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation HDLC, crc 32, controller loopback not set, keepalive set (10 sec)
Last clearing of "show interface" counters never
5 minute input rate 3000 bits/sec, 0 packets/sec
5 minute output rate 3000 bits/sec, 0 packets/sec
199794 packets input, 222359750 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
89911 packets output, 213413210 bytes, 0 total output drops
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
RP/0/RP0/CPU0:router# show controllers pos 0/0/1/0 framer statistics
POS Driver Internal Cooked Stats Values for port 0
===================================================
Rx Statistics Tx Statistics
------------- -------------
Total Bytes: 0 Total Bytes: 0
Good Bytes: 222379100 Good Bytes: 213436076
Good Packets: 199818 Good Packets: 89927
FCS Errors: 0 Min-len errors: 0
Runts: 0 Max-len errors: 0
FIFO Overflows: 0 FIFO Underruns: 0
RP/0/RP0/CPU0:router# show netio idb pos 0/0/1/0
POS0/0/1/0 (handle: 0x010800a0, nodeid:0x1) netio idb:
---------------------------------
interface handle: 0x010800a0
interface global index: 2
driver cookie: <0x4824cd68>
driver func: <0x4824cd54>
number of subinterfaces: 0
IN unknown proto bytes: 0
hdlc <14> <0xfd6a0a74, 0x00000000> < 0, 0>
<Protocol number> (name) Stats
Type Chain_node <caps num> <function, context> <drop pkts, drop bytes>
<9> (chdlc) Stats IN: 48466 pkts, 3559516 bytes; OUT: 41378 pkts, 910312 bytes
l2_adj_rewrite <86> <0xfceada88, 0x482c390c> < 0, 0>
queue_fifo <56> <0xfcedea68, 0x482ddc30> < 0, 0>
txm_nopull <60> <0xfce8fa5c, 0x482ddda4> < 0, 0>
queue_fifo <56> <0xfcedea4c, 0x482ddc30> < 0, 0>
chdlc <13> <0xfd6a252c, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfcead45c, 0x00000000> < 0, 0>
queue_fifo <56> <0xfcedea68, 0x482ddc30> < 0, 0>
txm_nopull <60> <0xfce8fa5c, 0x482ddda4> < 0, 0>
<10> (clns) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
clns <15> <0xfcfaa030, 0x00000000> < 0, 0>
hdlc <14> <0xfd6a0678, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfceada88, 0x48305a90> < 0, 0>
queue_fifo <56> <0xfcedea68, 0x482ddc30> < 0, 0>
txm_nopull <60> <0xfce8fa5c, 0x482ddda4> < 0, 0>
queue_fifo <56> <0xfcedea4c, 0x482ddc30> < 0, 0>
clns <15> <0xfcfa9508, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfcead45c, 0x00000000> < 0, 0>
queue_fifo <56> <0xfcedea68, 0x482ddc30> < 0, 0>
txm_nopull <60> <0xfce8fa5c, 0x482ddda4> < 0, 0>
<12> (ipv4) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
ipv4 <26> <0xfd0f341c, 0x482dd460> < 0, 0>
hdlc <14> <0xfd6a0678, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfceada88, 0x48349b54> < 0, 0>
queue_fifo <56> <0xfcedea68, 0x482ddc30> < 0, 0>
txm_nopull <60> <0xfce8fa5c, 0x482ddda4> < 0, 0>
queue_fifo <56> <0xfcedea4c, 0x482ddc30> < 0, 0>
ipv4 <26> <0xfd0f3474, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfcead45c, 0x00000000> < 0, 0>
queue_fifo <56> <0xfcedea68, 0x482ddc30> < 0, 0>
txm_nopull <60> <0xfce8fa5c, 0x482ddda4> < 0, 0>
Protocol SAFI Pkts In Bytes In Pkts Out Bytes Out
--------------- ---------- ---------- ---------- ---------- ----------
The following example shows counters implemented for Multiprotocol Label Switching (MPLS) packets. The following output under Protocol Chains in the show netio idb command shows the MPLS packets incrementing:
mpls <25> <0xfcc7b2b8, 0x00000000> < 152, 17328>
RP/0/RP0/CPU0:router# show netio idb gigabitEthernet 0/2/0/1
GigabitEthernet0/2/0/1 (handle: 0x01280040, nodeid:0x21) netio idb:
---------------------------------
name: GigabitEthernet0_2_0_1
interface handle: 0x01280040
interface global index: 3
driver cookie: <0x4829fc6c>
driver func: <0x4829f040>
number of subinterfaces: 4096
IN unknown proto bytes: 0
ether <30> <0xfd018cd8, 0x482c736c> < 0, 0>
<Protocol number> (name) Stats
Type Chain_node <caps num> <function, context> <drop pkts, drop bytes>
<7> (arp) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
l2_adj_rewrite <86> <0xfcaa997c, 0x4831a33c> < 0, 0>
pcn_output <54> <0xfd054bfc, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
pcn_input <55> <0xfd054bfc, 0x4830ba8c> < 0, 0>
q_fq_input <96> <0xfd05f330, 0x48312c7c> < 0, 0>
arp <24> <0xfcbfc2cc, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfcaa945c, 0x00000000> < 0, 0>
pcn_output <54> <0xfd054bfc, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
<10> (clns) Stats IN: 0 pkts, 0 bytes; OUT: 1861623 pkts, 2062483853 bytes
clns <15> <0xfcbe2c80, 0x00000000> < 0, 0>
ether <30> <0xfd0189b4, 0x482c736c> < 0, 0>
l2_adj_rewrite <86> <0xfcaa997c, 0x482d8660> < 0, 0>
pcn_output <54> <0xfd054bfc, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
pcn_input <55> <0xfd054bfc, 0x4830ba8c> < 0, 0>
q_fq_input <96> <0xfd05f330, 0x48312c7c> < 0, 0>
clns <15> <0xfcbe2444, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfcaa945c, 0x00000000> < 0, 0>
pcn_output <54> <0xfd054bfc, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
<12> (ipv4) Stats IN: 0 pkts, 0 bytes; OUT: 759095 pkts, 57691220 bytes
ipv4 <26> <0xfcc03dfc, 0x482e0414> < 0, 0>
ether <30> <0xfd0189b4, 0x482c736c> < 0, 0>
l2_adj_rewrite <86> <0xfcaa997c, 0x4831a294> < 0, 0>
pcn_output <54> <0xfd054c48, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
pcn_input <55> <0xfd054c48, 0x4830ba8c> < 0, 0>
q_fq_input <96> <0xfd05f330, 0x48312c7c> < 0, 0>
ipv4 <26> <0xfcc03e80, 0x00000000> < 0, 0>
l2_adj_rewrite <86> <0xfcaa945c, 0x00000000> < 0, 0>
pcn_output <54> <0xfd054c48, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
<13> (mpls) Stats IN: 204 pkts, 23256 bytes; OUT: 0 pkts, 0 bytes
mpls <25> <0xfcc7ddbc, 0x00000000> < 0, 0>
ether <30> <0xfd0189b4, 0x482c736c> < 0, 0>
l2_adj_rewrite <86> <0xfcaa997c, 0x4831a2e8> < 0, 0>
pcn_output <54> <0xfd0561f0, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
pcn_input <55> <0xfd0561f0, 0x4830ba8c> < 0, 0>
q_fq_input <96> <0xfd05f330, 0x48312c7c> < 0, 0>
mpls <25> <0xfcc7b2b8, 0x00000000> < 152, 17328>
l2_adj_rewrite <86> <0xfcaa945c, 0x00000000> < 0, 0>
pcn_output <54> <0xfd0561f0, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
<22> (ether_sock) Stats IN: 0 pkts, 0 bytes; OUT: 0 pkts, 0 bytes
ether_sock <98> <0xfd01a774, 0x482c736c> < 0, 0>
l2_adj_rewrite <86> <0xfcaa997c, 0x482d85f0> < 0, 0>
pcn_output <54> <0xfd054bfc, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
pcn_input <55> <0xfd054bfc, 0x4830ba8c> < 0, 0>
q_fq_input <96> <0xfd05f330, 0x48312c7c> < 0, 0>
ether_sock <98> <0xfd01a91c, 0x482c736c> < 0, 0>
l2_adj_rewrite <86> <0xfcaa945c, 0x00000000> < 0, 0>
pcn_output <54> <0xfd054bfc, 0x48319f04> < 0, 0>
q_fq <43> <0xfd05f4b8, 0x48320fec> < 0, 0>
txm_nopull <60> <0xfcadba38, 0x4824c0fc> < 0, 0>
Protocol SAFI Pkts In Bytes In Pkts Out Bytes Out
--------------- ---------- ---------- ---------- ---------- ----------
The following fixed physical layer interface module (PLIM) example shows the ASIC counters. The output displays any drop counters or error counters incrementing for the interface.
RP/0/RP0/CPU0:router# show controllers plim asic statistics interface tenGigE 1/3/0/0
-------------------------------------------------------------------------------
TenGigE1/3/0/0 Tx Statistics
-------------------------------------------------------------------------------
TotalOctets : 195723291 TotalPkts : 217711
Unicastpkts : 74830 MulticastPkts : 142879
BroadcastPkts : 2 <64Octets : 0
64Octets : 5337 65to127Octets : 73730
128to255Octets : 1813 256to511Octets : 2800
512to1023Octets : 2846 1024to1518Octets : 131185
1519to1548Octets : 0 1549to9216Octets : 0
>9216Octet : 0 BadCRCPkts : 0
802.1QPkts : 33396 Underrun : 0
PausePkts : 0 Jabbers : 0
DeferralAbort : 0 LateCollision : 0
CollisionAbort : 0 OneCollision : 0
MultiCollision : 0 TotalCollisions : 0
TotalDefer : 0 LateCollisionAbort: 0
LengthAbort : 0 TxBP count : 0
TenGigE1/3/0/0 Rx Statistics
-------------------------------------------------------------------------------
TotalPkts : 145028 UnicastPkts : 48672
MulticastPkts : 96354 BroadcastPkts : 2
64Octets : 27411 65to127Octets : 78648
128to255Octets : 15601 256to511Octets : 464
512to1023Octets : 533 1024to1518Octets : 22371
1519to1548Octets : 0 1549to9216Octets : 0
>9216Octets : 0 BadCRCPkts : 0
BadCodedPkts : 0 Runt : 0
ShortPkts : 0 802.1QPkts : 33392
ControlPkts : 0 Jabbers : 0
-------------------------------------------------------------------------------
RxFiFO Drop : 0 PAR Tail Drop : 0
PAR Err Drop : 0 MAC/VLAN Drop : 33392
RP/0/RP0/CPU0:router# show controllers plim asic statistics interface pos 0/5/0/0
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
TotalOctets : 85578609 TotalPkts : 265727
Unicastpkts : 265727 MulticastPkts : 0
BroadcastPkts : 0 <64Octets : 70059
64Octets : 0 65to127Octets : 145269
128to255Octets : 920 256to511Octets : 126
512to1023Octets : 659 1024to1518Octets : 48622
1519to1548Octets : 1 1549to9216Octets : 71
>9216Octet : 0 BadCRCPkts : 0
802.1QPkts : 0 Underrun : 0
PausePkts : 0 Jabbers : 0
DeferralAbort : 0 LateCollision : 0
CollisionAbort : 0 OneCollision : 0
MultiCollision : 0 TotalCollisions : 0
TotalDefer : 0 LateCollisionAbort: 0
LengthAbort : 0 TxBP count : 0
-------------------------------------------------------------------------------
TotalPkts : 159586 UnicastPkts : 159586
MulticastPkts : 0 BroadcastPkts : 0
64Octets : 0 65to127Octets : 51860
128to255Octets : 1534 256to511Octets : 555
512to1023Octets : 782 1024to1518Octets : 41278
1519to1548Octets : 0 1549to9216Octets : 63
>9216Octets : 0 BadCRCPkts : 0
BadCodedPkts : 0 Runt : 0
ShortPkts : 63514 802.1QPkts : 0
ControlPkts : 0 Jabbers : 0
-------------------------------------------------------------------------------
RxFiFO Drop : 1761 PAR Tail Drop : 0
The following 1 Gigabit Ethernet example shows the shared port adapter (SPA) counters. The output displays any drop counters or error counters incrementing for the interface.
RP/0/RP0/CPU0:router# show hw-module subslot 0/0/0 counters mac 0
SPA 0/0/0 device mac 0/0 info:
good_octets_received: 87538984
bad_octets_received: 41593
good_frames_received: 120401
broadcast_frames_received: 1
multicast_frames_received: 115293
good_octets_sent: 54953513
unrecog_mac_control_received: 0
The following Packet-over-SONET/SDH (POS) port example shows the SPA counters. The output displays any drop counters or error counters incrementing for the interface.
RP/0/RP0/CPU0:router# show hw-module subslot counters framer
SPA 0/0/1 device framer 0/0 info:
Pkts Bytes Underruns Aborts
port 0 90027 213674250 0 0
Pkts Bytes CRC errs Runts Giants Aborts
port 0 200042 222631936 0 0 0 0
SPA 0/0/5 device framer 0/0 info:
Port_1 (port 0) framer registers:
Rx Bytes (48-bit) (#0x60286078-0x883c): 3951749
Rx Good Bytes (48-bit) (#0x60286080-0x8840): 3112256
Rx Good Packets (48-bit) (#0x60286040-0x8820): 194516
Tx Byte Cnt Reg (48-bit) (#0x6028a070-0xa838): 3905343
Tx Good Bytes Cnt Reg (48-bit) (#0x6028a068-0xa834): 3112256
Tx Transmitted Packet Cnt Reg (48-bit) (#0x6028a040-0xa820): 194516
Verifying and Troubleshooting Pluggable Optical Interfaces
Troubleshooting the pluggable optical interfaces includes verifying that you have an optical card installed, enabled, and functioning properly. To troubleshoot the configured pluggable optical interfaces, perform the following procedure.
SUMMARY STEPS
1.
show hw-module subslot address brief pluggable-optics
2.
show hw-module subslot address status pluggable-optics
3.
show hw-module subslot address errors pluggable-optics
4.
show hw-module subslot address registers pluggable-optics
5.
Contact Cisco Technical Support if the problem is not resolved.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show hw-module subslot address brief
pluggable-optics
Example:
RP/0/RP0/CPU0:router# show hw-module subslot
0/6/4 brief pluggable-optics
|
Displays a brief summary of the pluggable optics status for all nodes, including optics type, vendor, and state. Check that the state is enabled for the node that you are troubleshooting.
|
Step 2
|
show hw-module subslot address status
pluggable-optics
Example:
RP/0/RP0/CPU0:router# show hw-module subslot
0/6/4 status pluggable-optics
|
Displays the status of the pluggable optics for the specified node, including faults and environmental data. Check that the state and the transceiver are enabled. Check for any warnings or alarms.
|
Step 3
|
show hw-module subslot address errors
pluggable-optics
Example:
RP/0/RP0/CPU0:router# show hw-module subslot
0/6/4 errors pluggable-optics
|
Displays any errors that are present on the node. Note if there are any errors.
Verify that Phased Initialization displays Phase Reached: 4. Verify that Socket Verification displays "passed" for both Compatibility and Security.
|
Step 5
|
Contact Cisco Technical Support.
|
For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
|
The following example shows typical outputs for these commands on systems.
RP/0/RP0/CPU0:router#show hw-module subslot 0/6/4 brief pluggable-optics
SPA 0/6/4 device pluggable-optics 0/0 info:
SPA 0/6/4 device pluggable-optics 1/0 info:
SPA 0/6/4 device pluggable-optics 2/0 info:
SPA 0/6/4 device pluggable-optics 3/0 info:
SPA 0/6/4 device pluggable-optics 4/0 info:
Xcvr Type: OC12 SR-1/STM4 MM (8)
Vendor part number: TRPD12MM2EAS-CS
SPA 0/6/4 device pluggable-optics 5/0 info:
Xcvr Type: OC12 SR-1/STM4 MM (8)
Vendor part number: TRPD12MM2EAS-CS
SPA 0/6/4 device pluggable-optics 6/0 info:
Xcvr Type: OC12 SR-1/STM4 MM (8)
Vendor part number: TRPD12MM2EAS-CS
SPA 0/6/4 device pluggable-optics 7/0 info:
RP/0/RP0/CPU0:router#show hw-module subslot 0/6/4 status pluggable-optics
SPA 0/6/4 device pluggable-optics 0/0 info:
SPA 0/6/4 device pluggable-optics 1/0 info:
SPA 0/6/4 device pluggable-optics 2/0 info:
SPA 0/6/4 device pluggable-optics 3/0 info:
SPA 0/6/4 device pluggable-optics 4/0 info:
Environmental Information - raw values
Supply voltage: 32669 in units of 100uVolt
Tx bias: 0 in units of 2uAmp
Tx power: -40 dBm (0 in units of 0.1 uW)
Rx power: -16 dBm (182 in units of 0.1 uW)
Version Identifier (VID): V01
Product Identifier (PID): SFP-OC12-MM
Part Number (PN): 10-2079-01
SPA 0/6/4 device pluggable-optics 5/0 info:
Environmental Information - raw values
Supply voltage: 32816 in units of 100uVolt
Tx bias: 0 in units of 2uAmp
Tx power: -40 dBm (0 in units of 0.1 uW)
Rx power: -16 dBm (194 in units of 0.1 uW)
Version Identifier (VID): V01
Product Identifier (PID): SFP-OC12-MM
Part Number (PN): 10-2079-01
SPA 0/6/4 device pluggable-optics 6/0 info:
Environmental Information - raw values
Supply voltage: 32816 in units of 100uVolt
Tx bias: 0 in units of 2uAmp
Tx power: -40 dBm (0 in units of 0.1 uW)
Rx power: -18 dBm (142 in units of 0.1 uW)
Version Identifier (VID): V01
Product Identifier (PID): SFP-OC12-MM
Part Number (PN): 10-2079-01
SPA 0/6/4 device pluggable-optics 7/0 info:
RP/0/RP0/CPU0:router#show hw-module subslot 0/6/4 errors pluggable-optics
SPA 0/6/4 device pluggable-optics 0/0 info:
SPA 0/6/4 device pluggable-optics 1/0 info:
SPA 0/6/4 device pluggable-optics 2/0 info:
SPA 0/6/4 device pluggable-optics 3/0 info:
SPA 0/6/4 device pluggable-optics 4/0 info:
Phase Exit Code: Success 0
Compatibility: Compatibility passed
Security: Security passed
SPA 0/6/4 device pluggable-optics 5/0 info:
Phase Exit Code: Success 0
Compatibility: Compatibility passed
Security: Security passed
SPA 0/6/4 device pluggable-optics 6/0 info:
Phase Exit Code: Success 0
Compatibility: Compatibility passed
Security: Security passed
SPA 0/6/4 device pluggable-optics 7/0 info:
RP/0/RP0/CPU0:router#show hw-module subslot 0/6/4 registers pluggable-optics
Tue Aug 17 05:29:36.306 DST
SPA 0/6/4 device pluggable-optics 0/0 info:
SPA 0/6/4 device pluggable-optics 1/0 info:
SPA 0/6/4 device pluggable-optics 2/0 info:
SPA 0/6/4 device pluggable-optics 3/0 info:
SPA 0/6/4 device pluggable-optics 4/0 info:
Xcvr Type: OC12 SR-1/STM4 MM (8)
50 micron-multimode fiber supported length: 500 m
62.5 micron-multimode fiber supported length: 500 m
Upper bit rate limit: not specified
Lower bit rate limit: not specified
Date code (yy/mm/dd): 05/06/17
Vendor Part Number (PN): TRPD12MM2EAS-CS
Vendor SN (SN): OCP09210623
Enhanced options implemented:
Diagnostic monitoring implemented:
Digital Diagnostic Monitoring
0x00: 03 04 07 00 00 10 00 00 00 00 00 05 06 00 00 00
0x10: 32 32 00 00 43 49 53 43 4F 2D 4F 43 50 20 20 20
0x20: 20 20 20 20 00 00 0A 1D 54 52 50 44 31 32 4D 4D
0x30: 32 45 41 53 2D 43 53 20 41 20 20 20 05 1E 00 FD
0x40: 00 12 00 00 4F 43 50 30 39 32 31 30 36 32 33 20
0x50: 20 20 20 20 30 35 30 36 31 37 20 20 68 80 01 87
0x60: 00 00 03 B5 E1 1E 6C A6 32 1B 46 E4 18 30 17 DE
0x70: 2A 95 A1 00 00 00 00 00 00 00 00 00 9C 5F 07 F7
0x80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Status/Control Register: 0000
high alarm high warning low warning low alarm
Temperature C +098.000 +095.000 -02.000 -03.000
Voltage V 003.5100 003.4950 003.1150 003.1000
Bias Current mA 000.0000 000.0000 000.0000 000.0000
Transmit power mW 000.0000 000.0000 000.0000 000.0000
Receive power mW 000.0631 000.0398 000.0008 000.0005
Diagnostics contents (hex):
0x00: 62 00 FD 00 5F 00 FE 00 89 1C 79 18 88 86 79 AE
0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x20: 02 77 00 05 01 8E 00 08 00 00 00 00 00 00 00 00
0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x40: 00 00 00 00 3F 80 00 00 00 00 00 00 01 00 00 00
0x50: 01 00 00 00 01 00 00 00 01 00 00 00 00 00 00 FF
0x60: 22 21 80 30 00 00 00 00 00 AB 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 49 50 55 49 41 47 39 52 41 41 31 30 2D 32 30 37
0x90: 39 2D 30 31 56 30 31 20 8A FB 55 00 00 00 00 6B
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 25 A8 00 00 00 00 00 CD 00 00 AA AA
0xC0: 53 46 50 2D 4F 43 31 32 2D 4D 4D 20 20 20 20 20
0xD0: 20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 F2
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 40 00 40 00 00 00 00
Troubleshooting Common Issues with Bundle Interfaces
Bundle interfaces utilize features and services provided by different components. To troubleshoot the common issues with bundle interface components on Cisco IOS XR software, perform the following procedure.
SUMMARY STEPS
1.
show tech-support bundles file filename
2.
show bundle bunde-name
3.
show iir interfaces name bundle-name
4.
show iir interfaces name bundle-name location location-id
5.
show pfi-ifh database bundle-name location location-id
6.
show cef adajacency bundle-name hardware egress detail location location-id
7.
show cef adajacency bundle-name hardware ingress remote detail location location-id
8.
Contact Cisco Technical Support if the problem is not resolved.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show tech-support bundles file filename
Example:
RP/0/RP0/CPU0:router# show tech-support bundles
file filename
|
Collects the output from bundle in both normal and admin modes and stores it in a file. It is important to do this as soon as possible after observing a problem because the traces with valuable information for debugging may wrap and be lost. It is strongly recommended that the command output be sent directly to file, rather than screen scraped, to avoid loss/corruption of part of the logs.
|
Step 2
|
show bundle bunde-name
Example:
RP/0/RP0/CPU0:router# sh bundle bundle-ether
202
|
Make sure that the member links are in Distributing (4) state.
|
Step 3
|
show iir interfaces name bundle-name
Example:
RP/0/RP0/CPU0:router# show iir interfaces name
bundle-ether 202
|
Ensure that the member links are in ACTIVE state.
|
Step 4
|
show iir interfaces name bundle-name location
location-id
Example:
RP/0/RP0/CPU0:router# show iir interfaces name
bundle-ether 202 location 0/RP0/CPU0
|
Make sure the IIR database of Bundle Interface Information is in sync.
|
Step 5
|
show pfi-ifh database bundle-name location
location-id
Example:
RP/0/RP0/CPU0:router# show pfi-ifh database
bundle-ether 205 location 0/1/CPU0
|
Make sure that the PFI-IFH database of bundle interface info is in sync.
|
Step 6
|
show cef adajacency bundle-name hardware egress
detail location location-id
Example:
RP/0/RP0/CPU0:router# show cef adjacency
bundle-name hardware egress detail location
0/RP0/CPU0
RP/0/RP0/CPU0:router# show cef adjacency
bundle-name hardware ingress remote detail
location 0/RP0/CPU0
|
Make sure that the TLU entries are allocated and bundle adjacency info is properly programmed
|
Step 7
|
Contact Cisco Technical Support.
|
For Cisco Technical Support contact information, see the "Obtaining Documentation and Submitting a Service Request" section in the Preface.
|