
CISCO Refurbished
- Manufacturer
- CISCO
- Condition
- Refurbished
- Availability
- Not In Stock
Description
The ONS-QSFP-40G-SR4 is a networking product manufactured by Cisco. It is a high-speed optical transceiver designed for use in data centers and other networking environments. It is capable of transmitting and receiving data at speeds up to 40 gigabits per second.The device is compact and efficient, making it ideal for use in high-density network environments. It features four independent channels, each capable of transmitting data up to 10 gigabits per second. This allows for greater flexibility in network design and reduces the need for multiple transceivers.The ONS-QSFP-40G-SR4 is a multimode optical transceiver, meaning it uses multiple fibers to transmit and receive data. It uses a standard MPO connector, which makes it easy to incorporate into existing network infrastructure.Overall, the ONS-QSFP-40G-SR4 is a reliable and high-performance networking solution that is well-suited for data centers and other high-bandwidth environments. Its small size, high speed, and compatibility with existing infrastructure make it an attractive option for network administrators looking to upgrade or expand their networks.- Part Code
- ONS-QSFP-40G-SR4
- Description
- 40GBASE-SR4 QSFP Transceiver Module with MPO Connector
- Manufacturer
- CISCO
RMON Counters Supported by Ethernet Interfaces
Expand
RMON Counters Supported by Ethernet Interfaces
Counter
rxTotalPkts
Good frames that are successfully received from the client line interface by the device
etherStatsPkts
Total number of frames received on an interface (The received is referred to a probe on the interface so count both Rx and Tx directions.)
etherStatsOctets
The total number of octets of data, including those in good and bad frames, received from the client line side by the device (This count excludes Preamble byte(s) SFD and Extension byte(s) but includes the Destination and Source addresses, Length/Type field, Q-tag prefix, MAC client data/pad and FCS.)
etherStatsOversizePkts
Good jumbo-frames that are successfully received from the client line interface by the device (Jumbo frames are frames of length 1519 to the configured Max frame size.)
dot3StatsFCSErrors
Receive frames that are an integral number of octets in length and do not pass the FCS check
dot3StatsAlignmentErrors
Receive frames that are not an integral number of octets in length and do not pass the FCS check
dot3StatsSymbolErrors
Received frames that have an associated RX_ER assertion during a data reception error event (MII) or data reception error event or carrier extension error (GMII) from the PCS
dot3StatsFramesTooLong
Receive frames that exceed the maximum permitted frame size, as programmed, and had no other errors
etherStatsJabbers
Receive frames that exceed the maximum permitted frame size, as programmed, and had a bad Frame Check Sequence (FCS)
etherStatsUndersizePkts
Receive frames containing less than the minimum permitted frame size, as programmed, and had no other errors
etherStatsFragments
Receive frames containing less than the minimum permitted frame size, as programmed, and had a bad Frame Check Sequence (FCS)
etherStatsPkts64Octets
Good and bad frames received that were 64 octets in length (excluding framing bits but including FCS)
etherStatsPkts65to127Octets
Good and bad frames received that were between 65 and 127 octets in length (excluding framing bits but including FCS)
etherStatsPkts128to255Octets
Good and bad frames received that were between 128 and 255 octets in length (excluding framing bits but including FCS)
etherStatsPkts256to511Octets
Good and bad frames received that were between 256 and 511 octets in length (excluding framing bits but including FCS)
etherStatsPkts512to1023Octets
Good and bad frames received that were between 512 and 1023 octets in length (excluding framing bits but including FCS)
etherStatsPkts1024to1518Octets
Good and bad frames received that were between 1024 and 1518 octets in length (excluding framing bits but including FCS)
ifInUcastPkts
Good frames that are successfully received and are directed to a unicast group address
ifInMulticastPktss
Good frames that are successfully received and are directed to a multicast group address
etherStatsMulticastPkts
Good multicast frames successfully received or transmitted on an interface
ifInBroadcastPkts
Good frames that are successfully received and are directed to a broadcast group address
etherStatsBroadcastPkts
Good broadcast frames successfully received or transmitted on an interface.
ifInErrors
The sum for this interface of dot3StatsAlignmentErrors, dot3StatsFCSErrors, dot3StatsFrameTooLongs, dot3StatsInternalMacReceiveErrors and dot3StatsSymbolErrors.
IfOutUcastPkts
Good frames that were successfully transmitted to a unicast group destination address
IfOutMulticastPkts
Good frames that were successfully transmitted to a multicast group destination address
IfOutBroadcastPkts
Good frames that were successfully transmitted to a Broadcast group destination address
etherStatsPkts1519toMaxSizeOctets
Good and bad frames received that were between 1519 octets in length and the maximum frame size as programmed within the RMAC Max Frame Length Configuration Register (excluding framing bits but including FCS)
mediaIndStatsTXFramesBadCRC
Transmitted frames that are an integral number of octets in length and do not pass the FCS check
mediaIndStatsTXShortPkts
Transmitted frames containing less than the minimum permitted frame size as programmed with the transmit MAC Min Frame Length Configuration Register
dot3StatsLCVErrors/mediaIndStatsRxLcvErrors
Received line code violations at the PCS layer
dot3StatsLayer1Errors
Number of Layer 1 errors as defined within the following conditions:
During Packet Reception - Layer 1 errors are counted only one time per packet. The error is indicated as a direct result of a line side protocol violation in which RX_DV is asserted. This is an uncommon event that could the reason why a device loses synchronization.
During Interpacket Reception - The Layer 1 error is indicated as a direct result of a line side protocol violation in which RX_DV is deasserted. This is an uncommon event. The Layer 1 error is also asserted on detection of a False Carrier indication and an errored byte (interpacket) signal encoding. When the error is asserted during interpacket reception, it is statistically asserted only in the vector.
During Packet Reception - Layer 1 errors are counted only one time per packet. The error is indicated as a direct result of a line side protocol violation in which RX_DV is asserted. This is an uncommon event that could the reason why a device loses synchronization.
During Interpacket Reception - The Layer 1 error is indicated as a direct result of a line side protocol violation in which RX_DV is deasserted. This is an uncommon event. The Layer 1 error is also asserted on detection of a False Carrier indication and an errored byte (interpacket) signal encoding. When the error is asserted during interpacket reception, it is statistically asserted only in the vector.
ifOutOctets
The total number of octets transmitted out of the interface, including framing characters
txTotalPkts
Total packets good/bad that are egressing
RMON Counters Supported by 8- and 10-Gigabit Fibre Channel Interfaces
Expand
RMON Counters Supported by 8- and 10-Gigabit Fibre Channel Interfaces
rxTotalPkts
Receive frame counter: number of received packets
mediaIndStatsRxFramesTruncated
Receive undersize frame counter: number of received frames that are too small
mediaIndStatsRxFramesTooLong
Receive oversize frame counter: number of received FC packets with length > 2148 (2148 is the maximum length for standard FC packets.)
mediaIndStatsRxFrameBadCRC
Receive frame CRC error counter: received frame with bad CRC
ifInOctects
Receive (frame) octets counter: total number of octets received on the interface including framing octet
ifInErros
Receive total errored frame counter: Receive oversiCRC me + Receive Undersize Frame + Receive CRC Errored Frame
RMON Counters Supported by GFP Virtual Ports
Expand
RMON Counters Supported by GFP Virtual Ports
gfpStatsRxFrame
Number of received GFP frames
gfpStatsTxFrame
Number of transmitted GFP frames
gfpStatsRxCRCErrors
Number of packets received with a payload FCS error
gfpStatsRxOctets
Number of GFP bytes received
gfpStatsTxOctets
Number of GFP bytes transmitted
gfpStatsRxSBitErrors
Sum of all the single bit errors (In the GFP CORE HDR at the GFP-T receiver, these are correctable.)
gfpStatsRxMBitErrors
Sum of all the multiple bit errors (In the GFP CORE HDR at the GFP-T receiver, these are uncorrectable.)
gfpStatsRxTypeInvalid
Number of receive packets dropped due to Client Data Frame UPI errors
gfpStatsCFSRaised
Number of GFP client signal fail frames detected at the GFP-T receiver
gfpStatsLFDRaised
Count of core HEC CRC multiple bit errors
Note: This count is only of eHec multiple bit errors when in frame. This can be looked at as a count of when the state machine goes out of frame.
Note: This count is only of eHec multiple bit errors when in frame. This can be looked at as a count of when the state machine goes out of frame.
gfpRxCmfFrame
Number of received client management frames
Card Specifications
Expand
Card Specifications
Physical
Dimensions
Occupies 1 slot
Latency (End to End)
SFP+ or QSFP+ port
46 microseconds
Cisco CPAK client port
29 microseconds
Storage temperature
-40ºC to 70ºC (-40ºF to 158ºF)
Refurbished CISCO ONS-QSFP-40G-SR4 datasheet
Download PDF







