Table Of Contents
Verifying and Troubleshooting Interface Status
Verifying and Troubleshooting Gigabit Ethernet Interfaces
Verifying and Troubleshooting Pluggable Optical Line Card Interfaces
Verifying and Troubleshooting Interface Status
This chapter describes how to verify that interfaces are up (operational), and how to troubleshoot problems on interfaces. It includes the following sections:
•
Verifying and Troubleshooting Gigabit Ethernet Interfaces
•
Verifying and Troubleshooting Pluggable Optical Line Card Interfaces
Verifying and Troubleshooting Gigabit Ethernet Interfaces
To troubleshoot gigabit Ethernet interfaces, 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 hw-module subslot address counters
or
show hw-module subslot counters framer
5.
If your system has pluggable optical line cards, perform additional troubleshooting steps applicable to these cards.
6.
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/RSP0/CPU0:router# show interfaces
gigabitEthernet 0/0/0/0
|
Displays statistics for all interfaces configured on the specified node. Check for interface errors and conflicting configurations, such as IP addresses defined incorrectly on interfaces.
|
Step 2
|
show controllers interface-type
interface-instance stats
Example:
RP/0/RSP0/CPU0:router# show controllers
gigabitEthernet 0/1/0/23 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/RSP0/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 hw-module subslot address counters
or
show hw-module subslot counters framer
Example:
RP/0/RSP0/CPU0:router# show hw-module subslot
0/0/0 counters
or
RP/0/RSP0/CPU0:router# show hw-module subslot
counters framer
|
Use these commands to check for status and interface drops on shared port adapters (SPAs).
|
Step 5
|
If your system has pluggable optical line cards, perform the additional troubleshooting steps applicable to these cards. See "Verifying and Troubleshooting Pluggable Optical Line Card Interfaces" section.
|
Check for interface drops on the pluggable optical line cards.
|
Step 6
|
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/RSP0/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/RSP0/CPU0:router# show controllers gigabitEthernet 0/1/0/2 stats
Wed Nov 3 12:41:54.201 DST
Statistics for interface GigabitEthernet0/1/0/2 (cached values):
Input pkts 65-127 bytes = 0
Input pkts 128-255 bytes = 0
Input pkts 256-511 bytes = 0
Input pkts 512-1023 bytes = 0
Input pkts 1024-1518 bytes = 0
Input pkts 1519-Max bytes = 0
Input drop invalid VLAN = 0
Input drop invalid DMAC = 0
Input drop invalid encap = 0
Input error fragments = 0
Input error collisions = 0
Output pkts 65-127 bytes = 0
Output pkts 128-255 bytes = 0
Output pkts 256-511 bytes = 0
Output pkts 512-1023 bytes = 0
Output pkts 1024-1518 bytes = 0
Output pkts 1519-Max bytes = 0
Output multicast pkts = 0
Output broadcast pkts = 0
RP/0/RSP0/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/RSP0/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 example shows the SPA status.
RP/0/RSP0/CPU0:router# show hw-module subslot 0/4/1 counters
Wed Nov 3 09:00:34.258 EDT
Subslot 0/4/1 counts info:
SPA operational state: READY
SPA insertion time: Mon Nov 1 08:28:12 2010
SPA last time ready: Mon Nov 1 08:30:04 2010
SPA uptime [HH:MM:SS]: 48:30:30
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/RSP0/CPU0:router# show hw-module subslot counters framer
SPA 0/2/0 device framer 0/0 info:
ABC (port 0) framer registers:
Rx Bytes (48-bit) (#0x60e7d078-0x883c): 567674
Rx Good Bytes (48-bit) (#0x60e7d080-0x8840): 479474
Rx Good Packets (48-bit) (#0x60e7d040-0x8820): 21795
Tx Byte Cnt Reg (48-bit) (#0x60e81070-0xa838): 567709
Tx Good Bytes Cnt Reg (48-bit) (#0x60e81068-0xa834): 479496
Tx Transmitted Packet Cnt Reg (48-bit) (#0x60e81040-0xa820): 21796
SPA 0/2/0 device framer 1/0 info:
ABC (port 1) framer registers:
Rx Bytes (48-bit) (#0x60dfd078-0x883c): 567628
Rx Good Bytes (48-bit) (#0x60dfd080-0x8840): 479438
Rx Good Packets (48-bit) (#0x60dfd040-0x8820): 21793
Tx Byte Cnt Reg (48-bit) (#0x60e01070-0xa838): 567690
Tx Good Bytes Cnt Reg (48-bit) (#0x60e01068-0xa834): 479478
Tx Transmitted Packet Cnt Reg (48-bit) (#0x60e01040-0xa820): 21795
Verifying and Troubleshooting Pluggable Optical Line Card Interfaces
Troubleshooting the pluggable optical line card interfaces includes verifying that you have an optical card installed, enabled, and functioning properly. To troubleshoot the configured pluggable optical line card interfaces, perform the following procedure.
SUMMARY STEPS
1.
show controllers plim asic SPAQFPBridgeCtrl counters instance <0 - 3> all location node-id
2.
show hw-module subslot brief pluggable-optics
3.
show hw-module subslot address status pluggable-optics
4.
show hw-module subslot address errors pluggable-optics
5.
show hw-module subslot address registers pluggable-optics
6.
Contact Cisco Technical Support if the problem is not resolved.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show controllers plim asic SPAQFPBridgeCtrl
counters instance <0 - 3> all location node-id
Example:
RP/0/RSP0/CPU0:router# show controllers plim
asic SPAQFPBridgeCtrl counters instance 0 all
location 0/4/CPU0
|
Displays the drop counters and error counters incrementing on the interface.
|
Step 1
|
show hw-module subslot brief pluggable-optics
Example:
RP/0/RSP0/CPU0:router# show hw-module subslot
brief pluggable-optics
|
|
Step 2
|
show hw-module subslot address status
pluggable-optics
Example:
RP/0/RSP0/CPU0:router# show hw-module subslot
0/2/0 status pluggable-optics
|
|
Step 3
|
show hw-module subslot address errors
pluggable-optics
Example:
RP/0/RSP0/CPU0:router# show hw-module subslot
0/2/0 errors pluggable-optics
|
|
Step 4
|
show hw-module subslot address registers
pluggable-optics
Example:
RP/0/RSP0/CPU0:router# show hw-module subslot
0/2/0 registers pluggable-optics
|
Displays all available information on the optics including the IDPROM contents.
|
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.
|
Examples
The following example displays the drop counters and error countersincrementing on the SPA in the line card.
RP/0/RSP0/CPU0:router# show controllers plim asic SPAQFPBridgeCtrl counters instance 0 all
location 0/4/CPU0
Wed Nov 3 08:58:07.062 EDT
=======================================
------------ SPAQFPBridgeCtrl 0 SPA1 Counters --------
--------------- SPAQFPBridgeCtrl 0 HT Counters ----------
-------------- SPAQFPBridgeCtrl 0 NP Counters ---------
-------------- SPAQFPBridgeCtrl 0 Diag Counters ---------
RXNP Online Diag Bytes: 0
RXNP Online Diag Packets: 0
TXNP Online Diag Bytes: 0
TXNP Online Diag Packets: 0
-------------- SPAQFPBridgeCtrl 0 Error Counters ---------
ERP Read out of sync Error: 0
CPUIF ERP Parity Error: 0
CPUIF ERP Protocol Error: 0
RXRLDC Mem Low Byte ECC: 0
RXRLDC Mem High Byte ECC: 0
TXRLDC Mem Low Byte ECC: 0
TXRLDC Mem High Byte ECC: 0
-------------- SPAQFPBridgeCtrl 0 Drop Counters ---------
TXNP Errored Low Priority Packets: 0
TXNP Errored High Priority Packets: 0
TXNP Errored Loopback Packets: 0
TXNP Errored HT Packets: 0
TXNP Errored Low Priority Bytes: 0
TXNP Errored High Priority Bytes: 0
TXNP Errored Loopback Bytes: 0
--------- SPAQFPBridgeCtrl 0 RXDCM Drops --------
--------- SPAQFPBridgeCtrl 0 TXDCM Drops --------
The following example shows typical outputs for these commands.
RP/0/RSP0/CPU0:router# show hw-module subslot brief pluggable-optics
SPA 0/2/0 device pluggable-optics 0/0 info:
Xcvr Type: OC48 SR/STM16 I-16 (44)
Vendor name: CISCO-FINISAR
Vendor part number: FTRJ1321P1BTL-C4
SPA 0/2/0 device pluggable-optics 1/0 info:
Xcvr Type: OC48 SR/STM16 I-16 (44)
Vendor name: CISCO-FINISAR
Vendor part number: FTRJ1321P1BTL-C4
RP/0/RSP0/CPU0:router# show hw-module subslot 0/2/0 status pluggable-optics
SPA 0/2/0 device pluggable-optics 0/0 info:
Environmental Information - raw values
Supply voltage: 32970 in units of 100uVolt
Tx bias: 12678 in units of 2uAmp
Tx power: -4 dBm (2848 in units of 0.1 uW)
Rx power: -7 dBm (1554 in units of 0.1 uW)
Version Identifier (VID): V01
Product Identifier (PID): SFP-OC48-SR
Part Number (PN): 10-1961-01
SPA 0/2/0 device pluggable-optics 1/0 info:
Environmental Information - raw values
Supply voltage: 32914 in units of 100uVolt
Tx bias: 11166 in units of 2uAmp
Tx power: -5 dBm (2282 in units of 0.1 uW)
Rx power: -5 dBm (2411 in units of 0.1 uW)
Version Identifier (VID): V01
Product Identifier (PID): SFP-OC48-SR
Part Number (PN): 10-1961-01
RP/0/RSP0/CPU0:router# show hw-module subslot 0/2/0 errors pluggable-optics
SPA 0/2/0 device pluggable-optics 0/0 info:
Phase Exit Code: Success 0
Compatibility: Compatibility passed
Security: Security passed
SPA 0/2/0 device pluggable-optics 1/0 info:
Phase Exit Code: Success 0
Compatibility: Compatibility passed
Security: Security passed
RP/0/RSP0/CPU0:router# show hw-module subslot 0/2/0 registers pluggable-optics
SPA 0/2/0 device pluggable-optics 0/0 info:
Xcvr Type: OC48 SR/STM16 I-16 (44)
Single mode fiber supported length: 2 km
Single mode fiber supported length: 20 m
Upper bit rate limit: not specified
Lower bit rate limit: not specified
Date code (yy/mm/dd): 05/12/13
Vendor Part Number (PN): FTRJ1321P1BTL-C4
Vendor SN (SN): FNS0951J0VN
Enhanced options implemented:
Diagnostic monitoring implemented:
Digital Diagnostic Monitoring
0x00: 03 04 07 00 01 00 00 12 00 01 05 05 19 00 02 14
0x10: 00 00 00 00 43 49 53 43 4F 2D 46 49 4E 49 53 41
0x20: 52 20 20 20 00 00 90 65 46 54 52 4A 31 33 32 31
0x30: 50 31 42 54 4C 2D 43 34 42 20 20 20 05 1E 00 23
0x40: 00 1A 00 00 46 4E 53 30 39 35 31 4A 30 56 4E 20
0x50: 20 20 20 20 30 35 31 32 31 33 20 20 58 80 01 D3
0x60: 00 00 02 4C D2 86 D7 04 F8 8D 92 6D 3C 8B D2 2D
0x70: 60 F3 BD 00 00 00 00 00 00 00 00 00 62 56 5D CD
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: 10f8
high alarm high warning low warning low alarm
Temperature C +110.000 +093.000 -30.000 -40.000
Voltage V 003.9000 003.7000 002.9000 002.7000
Bias Current mA 080.0000 070.0000 004.0000 002.0000
Transmit power mW 002.7234 001.7251 000.1704 000.1143
Receive power mW 005.0328 003.3461 000.0373 000.0120
Diagnostics contents (hex):
0x00: 6E 00 D8 00 5D 00 E2 00 98 58 69 78 90 88 71 48
0x10: 9C 40 03 E8 88 B8 07 D0 6A 62 04 77 43 63 06 A8
0x20: C4 98 00 78 82 B5 01 75 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 3E 72 B9 A5 41 37 B7 FE 01 00 00 00
0x50: 00 77 FF AB 01 00 00 00 01 00 00 00 10 00 00 90
0x60: 21 EC 81 18 01 0E 00 BA 19 DA 00 00 00 00 10 F8
0x70: 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 01
0x80: 57 4D 31 54 32 54 54 41 41 41 31 30 2D 31 39 36
0x90: 31 2D 30 31 56 30 31 20 8A FB 55 00 00 00 00 64
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 AA AA
0xC0: 53 46 50 2D 4F 43 34 38 2D 53 52 20 20 20 20 20
0xD0: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 66
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
SPA 0/2/0 device pluggable-optics 1/0 info:
Xcvr Type: OC48 SR/STM16 I-16 (44)
Single mode fiber supported length: 2 km
Single mode fiber supported length: 20 m
Upper bit rate limit: not specified
Lower bit rate limit: not specified
Date code (yy/mm/dd): 06/04/25
Vendor Part Number (PN): FTRJ1321P1BTL-C4
Vendor SN (SN): FNS1017R0BV
Enhanced options implemented:
Diagnostic monitoring implemented:
Digital Diagnostic Monitoring
0x00: 03 04 07 00 01 00 00 12 00 01 05 05 19 00 02 14
0x10: 00 00 00 00 43 49 53 43 4F 2D 46 49 4E 49 53 41
0x20: 52 20 20 20 00 00 90 65 46 54 52 4A 31 33 32 31
0x30: 50 31 42 54 4C 2D 43 34 42 20 20 20 05 1E 00 23
0x40: 00 1A 00 00 46 4E 53 31 30 31 37 52 30 42 56 20
0x50: 20 20 20 20 30 36 30 34 32 35 20 20 58 80 01 CE
0x60: 00 00 02 91 44 1B BF 32 33 64 55 09 CB 9B FD A3
0x70: 39 11 A4 00 00 00 00 00 00 00 00 00 88 17 A0 7B
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: 10f8
high alarm high warning low warning low alarm
Temperature C +110.000 +093.000 -30.000 -40.000
Voltage V 003.9000 003.7000 002.9000 002.7000
Bias Current mA 080.0000 070.0000 004.0000 002.0000
Transmit power mW 003.5276 002.2272 000.2022 000.1291
Receive power mW 005.0147 003.3353 000.0407 000.0155
Diagnostics contents (hex):
0x00: 6E 00 D8 00 5D 00 E2 00 98 58 69 78 90 88 71 48
0x10: 9C 40 03 E8 88 B8 07 D0 89 CC 05 0B 57 00 07 E6
0x20: C3 E3 00 9B 82 49 01 97 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 3E 73 C5 30 40 46 23 7C 01 00 00 00
0x50: 00 5B FF F2 01 00 00 00 01 00 00 00 10 00 00 7C
0x60: 21 D8 80 B8 00 54 00 22 2A 02 00 00 00 00 10 F8
0x70: 00 00 00 80 00 00 00 00 00 00 00 00 00 00 00 01
0x80: 57 4D 31 54 32 54 54 41 41 41 31 30 2D 31 39 36
0x90: 31 2D 30 31 56 30 31 20 8A FB 55 00 00 00 00 64
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 AA AA
0xC0: 53 46 50 2D 4F 43 34 38 2D 53 52 20 20 20 20 20
0xD0: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 66
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