Cisco Nexus 3000 Series NX-OS Release Notes, Release 6.0(2)U5(2)

Transcription

1 3000 Series N-OS Release Notes, Release 6.0(2U5(2 First Published: March 18, 2015 Last Updated: March 18, 2015 This document describes the features, bugs, and limitations for 3000 Series and 3100 Series taining Documentation and Submitting a Note: Release notes are sometimes updated with new information about restrictions and bugs. See the following website for the most recent version of the 3000 Series release notes: Table 1 shows the online change history for this document. Table 1. Online History Change Date Description March 18, 2015 May 12, 2015 November 2, 2015 January 7, 2016 Created N-OS Release 6.0(2U5(2 release notes Added Known Behaviors Added the following note: GLC-S-MMD is supported on all 3000 Series Switches except for the 3064-T. Please refer to the comparability matrix for all the supported platforms. Removed a bug Id (CSCuq92481 from Limitations. Systems, Inc. 1

2 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Contents Contents Introduction New and Changed Information Upgrade and Downgrade Guidelines Limitations Caveats MIB Support Related Documentation Documentation Feedback Obtaining Documentation and Submitting a Service Request Introduction Several new hardware and software features are introduced for the 3000 Series and 3100 Series devices to improve the performance, scalability, and management of the product line. N-OS Release 6.x also supports all hardware and software supported in N-OS Release 5.1 and N-OS Release 5.0. N-OS offers the following benefits: N-OS runs on all data center switch platforms: 7000, 5000, 4000, 3000, 2000, and 1000V Series switches. N-OS software interoperates with products that run any variant of IOS software and also with any networking operating system that conforms to common networking standards. N-OS modular processes are triggered on demand, each in a separate protected memory space. Processes are started and system resources are allocated only when a feature is enabled. The modular processes are governed by a real-time preemptive scheduler that helps ensure timely processing of critical functions. N-OS provides a programmatic ML interface that is based on the NETCONF industry standard. The N-OS ML interface provides a consistent API for devices. N-OS also provides support for Simple Network Management Protocol (SNMP Versions 1, 2, and 3 MIBs. N-OS enables administrators to limit access to switch operations by assigning roles to users. Administrators can customize access and restrict it to the users who require it. Also see these sections: 3000 Series Switches 3100 Series Switches 3000 Series Switches The 3000 Series switches are high-performance, high-density, ultra-low-latency Ethernet switches that provide line-rate Layer 2 and Layer 3 switching. The 3000 Series includes the following switches: 2

3 3000 Series N-OS Release Notes, Release 6.0(2U5(2 The 3064 switch is a 1 RU switch that supports or 10-Gigabit downlink ports, four Quad Small Form-Factor Pluggable (QSFP+ ports that can be used as a 40 Gigabit Ethernet port or 4 x10-gigabit Ethernet ports, one 10/100/1000 management port, and one console port. The 3048 switch is a 1 rack unit (RU switch that supports 48 10/100/1000 Ethernet server-facing (downlink ports, four 10-Gigabit network-facing (uplink ports, one 100/1000 management port, and one console port. The 3016 is a 1 RU, 16-port QSFP+ switch. Each QSFP+ port can be used as a 40-Gigabit Ethernet port or 4 x10-gigabit Ethernet ports. Each switch includes one or two power supply units and one fan tray module, and each switch can be ordered with either forward (port-side exhaust airflow or reverse (port-side intake airflow for cooling. All platforms support both AC and DC power supplies. All combinations of power (AC/DC and airflow (forward/reverse are available. The 3000 Series switches run the N-OS software. For information about the 3000 Series, see the 3000 Series Hardware Installation Guide Series Switches The 3100 Series switches are high-performance, high-density, ultra-low-latency Ethernet switches that provide line-rate Layer 2 and Layer 3 switching. In N-OS Release 6.0(2U2(2, the 3100 Series includes the 3132 and 3172 switches. The 3172PQ switch is a 10-Gbps Enhanced Small Form-Factor Pluggable (SFP+ based ToR switch with 48 SFP+ ports and 6 Enhanced Quad SFP+ (QSFP+ ports. The 3172TQ switch is a 10GBASE-T switch with 48 10GBASE-T ports and 6 Quad SFP+ (QSFP+ ports. Each SFP+ port can operate in 100-Mbps, 1-Gbps, or 10-Gbps mode, and each QSFP+ port can operate in native 40- Gbps or 4 x 10-Gbps mode. This switch is a true physical-layer-free (phy-less switch that is optimized for low latency and low power consumption. The 3132Q switch is a 1RU, 40-Gbps QSFP-based switch that supports 32 fixed 40-Gbps QSFP+ ports. It also has 4 SFP+ ports that can be internally multiplexed with the first QSFP port. Each QSFP+ port can operate in the default 40-Gbps mode or 4 x 10-Gbps mode, up to a maximum of Gbps ports. Each switch includes dual redundant power supply units, four redundant fans, one 10/100/1000 management port, and one console port. Each switch can be ordered with either forward (port-side exhaust airflow or reverse (port-side intake airflow for cooling. It supports both AC and DC power supplies. All combinations of power (AC/DC and airflow (forward/reverse are available. The 3100 Series switches run the N-OS software. For information about the 3100 Series, see the 3000 Series Hardware Installation Guide. This section includes the following topics: Memory Requirements Hardware Supported Twinax Cable Support on 3000 Switches QSFP 40-Gbps Bidirectional Short-Reach Transceiver 3

4 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Memory Requirements The N-OS Release 6.0(2U5(2 software requires 135 MB of flash memory. Hardware Supported N-OS Release 6.0(2U5(2 supports the 3000 Series switches. You can find detailed information about supported hardware in the 3000 Series Hardware Installation Guide. Table 2 shows the hardware supported by the N-OS Release 6.x software. Table 3 shows the hardware supported by the N-OS 5.x releases. Table 4 shows the transceivers supported by the N-OS Release 6.x software. Table 5. shows transceivers supported by the N-OS 5.x releases. Table 2. Hardware Supported by N-OS Related 6.x Software. Hardware Part Number Supported N-OS Release 3132Q- switch 3172TQ switch 3172PQ switch 3132Q switch 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 6.0(2U3(2 6.0(2U3(1 6.0(2U4(4 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 N3K-C3132Q-40G N3K-C3172TQ-10GT N3K-C3172PQ-10GE N3K-C3132Q-40GE 6.0(2U5(2 6.0(2U5( switch N3K-C3016Q-40GE 3048 switch N3K-C3048TP-1GE 3064-TQ switch switch 3064-E switch N3K-C3064TQ-10GT N3K-C3064PQ-10G N3K-C3064PQ-10GE 3064 switch N3K-C3064PQ 4

5 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 3048 fan module with forward airflow (port-side exhaust 3048 fan module with reverse airflow (port-side intake 3064-T 500W forward airflow (port-side exhaust AC power supply 3064-T 500W reverse airflow (port-side intake AC power supply 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 6.0(2U3(2 6.0(2U3(1 6.0(2U4(4 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 N3K-C3048-FAN N3K-C3048-FAN-B NA-PAC-500W NA-PAC-500W-B 6.0(2U5(2 6.0(2U5( forward airflow (port-side exhaust AC power supply N3K-C3064--FA- L reversed airflow (port-side intake AC power supply N3K-C3064--BA- L forward airflow (port-side exhaust DC power supply N3K-C3064--FD- L forward airflow (port-side intake DC power supply N3K-C3064--BD- L fan module with forward airflow (port-side exhaust; also used in the 3016 N3K-C3064-FAN 5

6 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 3064 fan module with reverse airflow (port-side intake; also used in the power supply with forward airflow (port-side exhaust 3000 power supply with reverse airflow (port-side intake 2000 power supply with forward airflow (port-side exhaust 2000 DC power supply with reverse airflow (port-side intake 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 6.0(2U3(2 6.0(2U3(1 6.0(2U4(4 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 N3K-C3064-FAN-B N2200-PAC-400W N2200-PAC-400W-B N2200-PDC-400W N3K-PDC-350W-B 6.0(2U5(2 6.0(2U5(1 Table 3. Hardware Supported by N-OS Release 5.x Software Hardware Part Number Supported N-OS Release 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d 6

7 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d 3016 switch N3K- C3016Q- 40GE 3048 switch N3K- C3048TP- 1GE 3064-TQ switch N3K- C3064TQ -10GT switch N3K- C3064P1 0G 3064-E switch N3K- C3064PQ -10GE 3064 switch N3K- C3064PQ 1 Recommended release for 3064-TQ switch is N-OS Release 5.0(3U5(1c or later releases. 7

8 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d 3048 fan module with forward airflow (port-side exhaust N3K- C3048- FAN 3048 fan module with reverse airflow (port-side intake N3K- C3048- FAN-B 3064-T 500W forward airflow (port side exhaust AC power supply NA- PAC- 500W 8

9 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d 3064-T 500 W reverse airflow (port side intake AC power supply NA- PAC- 500W-B forward airflow (port-side exhaust AC power supply N3K- C FA-L reversed airflow (port-side intake AC power supply N3K- C BA-L3 9

10 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d forward airflow (port-side exhaust DC power supply N3K- C FD-L forward airflow (port-side intake DC power supply N3K- C BD-L fan module with forward airflow (port-side exhaust; also used in the 3016 N3K- C3064- FAN 10

11 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 3064 fan module with reverse airflow (port-side intake; also used in the power supply with forward airflow (port-side exhaust N3K- C3064- FAN-B N2200- PAC- 400W 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d 11

12 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Hardware Part Number Supported N-OS Release 3000 power supply with reverse airflow (port-side intake 2000 power supply with forward airflow (port-side exhaust N2200- PAC- 400W-B N2200- PDC- 400W 5.0(3U5(1f 5.0(3U5(1 e 5.0(3U5(1 d 5.0(3U5(1c 5.0(3U5(1 b 5.0(3U5(1a 5.0(3U5(1 5.0(3U4(1 5.0(3U3(2 b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2 d 5.0(3U2(2c 5.0(3U2(2 b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2a 5.0(3U1(2 5.0(3U1(1 d 2000 DC power supply with reverse airflow (port-side intake N3K- PDC- 350W-B 12

13 3000 Series N-OS Release Notes, Release 6.0(2U5(2 13

14 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Table 4. Transceivers Supported by N-OS Release 6.x Software. Transceivers 2 Part Number Supported N-OS Release QSFP 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 40GBASE-LR4 QSFP40G transceiver module (SMF QSFP-40G-LR4 6.0(2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 40GBASE-CR4 QSFP+ direct-attach copper cable, 7 meters active 40GBASE-CR4 QSFP+ direct-attach copper cable, 8 meters active 40GBASE-CR4 QSFP+ direct-attach copper cable, 9 meters active 40GBASE-CR4 QSFP+ direct-attach copper cable, 10 m active QSFP-H40G-ACU7M QSFP-H40G-ACU8M QSFP-H40G-ACU9M QSFP-H40G-ACU10M 40G QSFP direct-attach active optical cable, 15 m QSFP-H40G-AOC15M QSFP to 4 x SFP 10Gbps active optical cable 15 m QSFP-410G-AOC15M QSFP 40G Bidirectional short-reach transceiver QSFP-40G-SR-BD QSFP 40G active optical cable 1 m QSFP-H40G-AOC1M QSFP 40G active optical cable 2 m QSFP-H40G-AOC2M QSFP 40G active optical cable 3 m QSFP-H40G-AOC3M QSFP 40G active optical cable 5 m QSFP-H40G-AOC5M QSFP 40G active optical cable 7 m QSFP-H40G-AOC7M QSFP 40G active optical cable 10 m QSFP-H40G-AOC10M QSFP to 4 x SFP 10Gbps active optical cable 1 m QSFP-410G-AOC1M 2 OIR is supported for all optical modules and transceivers in N-OS Release 6.02 and later releases. 14

15 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceivers 2 Part Number Supported N-OS Release 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 QSFP to 4 x SFP 10Gbps active optical cable 2 m QSFP-410G-AOC2M QSFP to 4 x SFP 10Gbps active optical cable 3 m QSFP-410G-AOC3M QSFP to 4 x SFP 10Gbps active optical cable 5 m QSFP-410G-AOC5M QSFP to 4 x SFP 10Gbps active optical cable 7 m QSFP-410G-AOC7M QSFP to 4 x SFP 10Gbps active optical cable 10 m QSFP-410G-AOC10M Active copper splitter cable 7 m QSFP-4x10G-AC7M 3 Active copper splitter cable 10 m QSFP-4x10G-AC10M 2 Active copper QSFP transceiver module 7 m QSFP-H40G-ACU7M 2 Active copper QSFP transceiver module 10 m QSFP-H40G-ACU10M 2 6.0(2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 40GBASE-CSR4 QSFP transceiver module with multifiber push-on (MPO connector 300 m 40GBASE-CSR4 QSFP transceiver module with MPO connector 300 m (using fiber splitter cables 40GBASE-SR4 QSFP transceiver module with MPO connector 100 m 40GBASE-SR4 QSFP transceiver module with MPO connector 100 m (using fiber splitter cables 40GBASE-LR4 QSFP transceiver module with LC connector 10 km (using single mode fiber QSFP-40G-CSR4 2 QSFP-40G-CSR4 2 QSFP-40G-SR4 2 QSFP-40G-SR4 2 QSFP-40GE-LR4 QSFP to SFP/SFP+ adapter CVR-QSFP-SFP10G 40GBASE-CR4 passive copper cable, 1 m QSFP-H40G-CU1M 3 Supported on the 3016, 3064-, 3064-TQ, 3064, 3064-E, and all 3100 Series switches. 15

16 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceivers 2 Part Number Supported N-OS Release 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 40GBASE-CR4 passive copper cable, 3 m QSFP-H40G-CU3M 40GBASE-CR4 passive copper cable, 5 m QSFP-H40G-CU5M 6.0(2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 QSFP to 4xSFP10G passive copper splitter cable, 1 m QSFP to 4xSFP10G passive copper splitter cable, 3 m QSFP to 4xSFP10G passive copper splitter cable, 5 m QSFP-4SFP10G-CU1M QSFP-4SFP10G-CU3M QSFP-4SFP10G-CU5M Revision 2 copper splitter cables 3 m Revision 2 copper splitter cables 5 m QSFP-4SFP10G-CU3 (Rev. 2 QSFP-4SFP10G-CU5 (Rev Gigabit 10 db attenuator FA GBASE-ZR SFP+ module (single-mode fiber [SMF] 4 SFP-10G-ZR 3 QSFP to SFP/SFP+ Adapter (QSA module CVR-QSFP-SFP10G QSFP to SFP/SFP+ Adapter (QSA module with 10GBASE-DWDM QSA w/ DWDM 10GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G Supported on the 3064-E and switches. 16

17 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceivers 2 Part Number Supported N-OS Release 10GBASE-DWDM nm SFP+ (100-GHz ITU grid 10GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G DWDM-SFP10G (2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 6.0(2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 10GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM nm SFP+ (100-GHz ITU grid DWDM-SFP10G GBASE-DWDM long-range transceiver module 80 km with single mode duplex fiber DWDM-SFP10G-C 10GBASE-DWDM long-range transceiver module 80 km with single mode duplex fiber DWDM-SFP10G 10GBASE-SR SFP+ module (multimode fiber [MMF] SFP-10G-SR 10GBASE-LR SFP+ module (single-mode fiber [SMF] 10GBASE-ER SFP+ module (single-mode fiber [SMF] SFP-10G-LR SFP-10G-ER 17

18 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceivers 2 Part Number Supported N-OS Release 10GBASE-ZR SFP+ module (single-mode fiber [SMF] 10GBASE-DWDM SFP+ module (single-mode fiber [SMF] 3 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 SFP-10G-ZR (2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 Active Twinax cable assembly, 7 m SFP-H10GB-ACU7M Active Twinax cable assembly, 10 m SFP-H10GB-ACU10M 10GBASE-CU SFP+ cable 1 m (Twinax cable SFP-H10GB-CU1M 10GBASE-CU SFP+ cable 1.5 m (Twinax cable SFP-H10GB-CU1-5M 10GBASE-CU SFP+ cable 2 m (Twinax cable 4 SFP-H10GB-CU2M 5 10GBASE-CU SFP+ cable 3 m (Twinax cable SFP-H10GB-CU3M 10GBASE-CU SFP+ cable 5 m (Twinax cable SFP-H10GB-CU5M 10GBASE-CU SFP+ cable 2.5 m (Twinax cable 4 SFP-H10GB-CU2-5M 4 Active optical cable 1 m SFP-10G-AOC1M 5 Active optical cable 2 m SFP-10G-AOC2M Active optical cable 3 m SFP-10G-AOC3M 5 Active optical cable 5 m SFP-10G-AOC5M 5 Active optical cable 7 m SFP-10G-AOC7M 5 Active optical cable 10 m SFP-10G-AOC10M 1-Gigabit Ethernet 5 Supported on the 3048, 3064-, 3064, and 3064-E switches. 18

19 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceivers 2 Part Number Supported N-OS Release Gigabit Ethernet SFP, LC connector S transceiver (MMF Gigabit Ethernet SFP, LC connector L/LH transceiver (SMF GLC-S-MMD Note: GLC-S-MMD is supported on all 3000 Series Switches except for the T. Please refer to the comparability matrix for all the supported platforms. GLC-LH-SMD 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 6.0(2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 QSFP to SFP/SFP+ Adapter (QSA module with GLC-T QSA w/ GLC-T 1000BASE-T SFP GLC-TE QSFP to SFP/SFP+ Adapter (QSA module with GLC-TE QSA w/ GLC-TE QSFP to SFP/SFP+ Adapter (QSA module with SFP-GE-T QSA w/sfp-ge-t 1000Base-B fiber transceiver GLC-B-D Base-B fiber transceiver GLC-B-U BASE-E fiber transceiver module, SMF GLC-E-SMD Gigabit Ethernet SFP, LC connector L/LH transceiver (SMF 1000BASE-L/LH SFP transceiver module for MMF and SMF Gigabit Ethernet SFP, LC connector S transceiver (MMF GLC-LH-SM 5 GLC-LH-SMD 5 GLC-S-MM 4 19

20 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceivers 2 Part Number Supported N-OS Release Gigabit Ethernet SFP, LC connector S transceiver (MMF GLC-S-MMD Note: GLC-S-MMD is supported on all 3000 Series Switches except for the T. Please refer to the comparability matrix for all the supported platforms. 6.0(2U1(3 6.0(2U1(2 6.0(2U1(1a 6.0(2U1(1 6.0(2U2(5 6.0(2U2(4 6.0(2U2(3 6.0(2U2(2 6.0(2U2(1 1000BASE-T SFP 6 GLC-T 5 6.0(2U5(2 6.0(2U5(1 6.0(2U4(3 6.0(2U4(2 6.0(2U4(1 6.0(2U3(2 6.0(2U3(1 1000BASE-Z fiber transceiver module, SMF, 1550 nm 1000BASE-T SFP transceiver module with extended operating temperature range GLC-Z-SMD SFP-GE-T Mbps Ethernet 100BASE-F SFP module for Gigabit Ethernet ports GLC-GE-100F BASE- F SFP module for Gigabit Ethernet ports GLC-GE- 100F 6 Supported on the 3064, 3064-E, and switches. For the GLC-GE-100F, only part number is supported. 7 Supported on the 3048, 3064-E, and switches. Not supported on 3132Q-. 20

21 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Note: The 3000 supports 1,000 and 10,000 speeds while using SFP+ with QSA [CVR-QSFP- SFP10G] (and a maximum of 6 QSAs. The 100 speed is not supported on the SFP+ along with QSA, but using any speed 100 is supported on the SFP+. Table 5. Transceivers Supported by N-OS Release 6.x Software. Transceiver s QSFP Part Number 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d Active copper splitter cable 7 m QSFP- 4x10G- AC7M 8 Active copper splitter cable 10 m Active copper QSFP transceiver module 7 m Active copper QSFP transceiver module 10 m QSFP- 4x10G- AC10M 8 QSFP- H40G- ACU7M 8 QSFP- H40G- ACU10M 8 8 Supported on the 3016, 3064-, 3064-TQ, 3064, and 3064-E switches. 21

22 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s Part Number 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 40GBASE- CSR4 QSFP transceiver module with MPO connector 300 m QSFP- 40G-CSR4 8 40GBASE- CSR4 QSFP transceiver module with MPO connector 300 m (using fiber splitter cables QSFP- 40G-CSR4 8 40GBASE- SR4 QSFP transceiver module with MPO connector 100 m QSFP- 40G-SR4 8 40GBASE- SR4 QSFP transceiver module with MPO connector 100 m (using fiber splitter cables QSFP- 40G-SR4 8 22

23 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s 40GBASE- CR4 passive copper cable, 1 m 40GBASE- CR4 passive copper cable, 3 m Part Number QSFP- H40G- CU1M QSFP- H40G- CU3M 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 40GBASE- CR4 passive copper cable, 3 m QSFP- H40G- CU3M 40GBASE- CR4 passive copper cable, 5 m QSFP- H40G- CU5M QSFP to 4xSFP10G passive copper splitter cable, 1 m CU5M CU1M QSFP to 4xSFP10G passive copper splitter cable, 3 m QSFP- 4SFP10G- CU3M 23

24 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s QSFP to 4xSFP10G passive copper splitter cable, 5 m Revision 2 copper splitter cables 3 m Revision 2 copper splitter cables 5 m Part Number QSFP- 4SFP10G- CU5M QSFP- 4SFP10G- CU3 (Rev. 2 QSFP- 4SFP10G- CU5 (Rev (3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 10-Gigabit 10GBASE- SR SFP+ module (multimode fiber [MMF] SFP-10G- SR 10GBASE- LR SFP+ module (singlemode fiber [SMF] SFP-10G- LR 24

25 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s 10GBASE- ER SFP+ module (singlemode fiber [SMF] 10GBASE- ZR SFP+ module (singlemode fiber [SMF] 9 Part Number SFP-10G- ER SFP-10G- ZR 9 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 10GBASE- DWDM SFP+ module (singlemode fiber [SMF] GBASE- CU SFP+ cable 1 m (Twinax cable SFP- H10GB- CU1M 10GBASE- CU SFP+ cable 3 m (Twinax cable SFP- H10GB- CU3M 9 Supported on the 3064-E and switches. 25

26 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s 10GBASE- CU SFP+ cable 5 m (Twinax cable Part Number SFP- H10GB- CU5M 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 10GBASE- CU SFP+ cable 2 m (Twinax cable3 10 SFP- H10GB- CU2M 10 10GBASE- CU SFP+ cable 2.5 m (Twinax cable 10 SFP- H10GB- CU2-5M3 10 Active optical cable 1 m SFP-10G- AOC1M 11 Active optical cable 3 m SFP-10G- AOC3M 11 Active optical cable 5 m SFP-10G- AOC5M 11 Active optical cable 7 m SFP-10G- AOC7M Supported on the 3048, 3064-, 3064, and 3064-E switches. 11 Supported on the 3048, 3064-E, and switches. 26

27 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s 1-Gigabit Ethernet Part Number 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 1000BASE- T SFP 11 GLC-T 11 Gigabit Ethernet SFP, LC connector S transceiver (MMF GLC-S- MM 10 Gigabit Ethernet SFP, LC connector S transceiver (MMF GLC-S- MMD Note: GLC- S-MMD is supported on all 3000 Series Switches except for the T. Please refer to the comparabili ty matrix for all the supported platforms. 27

28 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s Gigabit Ethernet SFP, LC connector L/LH transceiver (SMF 1000BASE- L/LH SFP transceiver module for MMF and SMF Part Number GLC-LH- SM 11 GLC-LH- SMD (3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d 1000Base- B fiber transceiver GLC-B- U Base- B fiber transceiver GLC-B- D BASE- T SFP transceiver module with extended operating temperature range SFP-GE- T Mbps Ethernet 28

29 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Transceiver s 100BASE- F SFP module for Gigabit Ethernet ports GLC- GE-100F 12 Part Number GLC-GE- 100F 5.0(3U5( 1f 5.0(3U5( 1e 5.0(3U5( 1d 5.0(3U5( 1c 5.0(3U5( 1b 5.0(3U5( 1a 5.0(3U5( 1 5.0(3U4(1 5.0(3U3(2b 5.0(3U3(2a 5.0(3U3(2 5.0(3U3(1 5.0(3U2(2c 5.0(3U2(2b 5.0(3U2(2a 5.0(3U2(2 5.0(3U2(1 5.0(3U1(2 5.0(3U1(2a 5.0(3U1(1a 5.0(3U1(1b 5.0(3U1(1d Twinax Cable Support on 3000 Switches Starting with Release N-OS 5.0(3U1(1, the following algorithm is used to detect copper SFP+ twinax, QSFP+ twinax, and QSFP+ splitter cables on 3000 Series switches. If the attached interconnect (transceiver is a copper SFP+ twinax or QSFP+ twinax cable: Verify the transceiver SPROM to match the magic code. If the check succeeds, bring up the interface. Otherwise, print the following warning message appears stating that a non- transceiver is attached and that you should try to bring up the port Oct 9 01:46:42 switch %ETHPORT-3-IF_NON-CISCO_TRANSCEIVER: Non- transceiver on interface Ethernet1/18 is detected. If the attached transceiver is a QSFP+ splitter cable, then no special check is performed. The N-OS software tries to bring up the port. The following disclaimer applies to non- manufactured and non- certified QSFP copper splitter cables: If a customer has a valid support contract for switches, TAC will support twinax cables that are a part of the compatibility matrix for the respective switches. However, if the twinax cables are not purchased through, a customer cannot return these cables through an RMA to for replacement. If a twinax cable that is not part of the compatibility matrix is connected into a system, TAC will still debug the problem, provided the customer has a valid support contract on the switches. However TAC may ask the 12 Supported on the 3064, 3064-E, and switches. For the GLC-GE-100F, only part number is supported. 29

30 3000 Series N-OS Release Notes, Release 6.0(2U5(2 New and Changed Information customer to replace the cables with qualified cables if there is a situation that points to the cables possibly being faulty or direct the customer to the cable provider for support. TAC cannot issue an RMA against uncertified cables for replacement. QSFP 40-Gbps Bidirectional Short-Reach Transceiver The QSFP 40-Gbps Bidirectional (BiDi transceiver is a short-reach pluggable optical transceiver with a duplex LC connector for 40-GbE short-reach data communications and interconnect applications by using multimode fiber (MMF. The QSFP 40-Gbps BiDi transceiver offers a solution that uses existing duplex MMF infrastructure for 40-GbE connectivity. With the QSFP 40-Gbps BiDi transceiver, customers can upgrade their network from 10-GbE to 40- GbE without incurring any fiber infrastructure upgrade cost. The QSFP 40-Gbps BiDi transceiver can enable 40- GbE connectivity in a range of up to 100 meters over OM3 fiber, which meets most data center reach requirements. It complies with the Multiple Source Agreement (MSA QSFP specification and enables customers to use it on all QSFP 40-Gbps platforms and achieve high density in a 40-GbE network. It can be used in data centers, highperformance computing (HPC networks, enterprise and distribution layers, and service provider transport applications. New and Changed Information This section lists the new and changed features in Release 6.0(2U5(2. New Supported Hardware New Software Features New Supported Hardware N-OS Release 6.0(2U5(2 does not include new hardware. New Software Features All 3000 Series switches are supported by N-OS Release 6.0(2U5(2. N-OS interoperates with any networking operating system, including IOS software, that conforms to the networking standards listed in the product data sheet. This release does not include any new software features. Upgrade and Downgrade Guidelines Ensure that you use the install all command to upgrade the switch software from one N-OS release to another Series switches that use software versions older than N-OS Release 5.0(3U5(1 need to be updated to N-OS Release 5.0(3U5(1 before they are upgraded to N-OS Release 6.0(2. N-OS Release 5.0(3U3(1 does not support a software upgrade from N-OS Release 5.0(3U2(2c. If you want to upgrade through this path, see CSCty75328 for details about how to work around this issue. Note: It is recommended that you upgrade to N-OS Release 6.0(2U5(2 by using N-OS install procedures. 30

31 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Limitations In N-OS Release 5.0(3U3(1, support for IPv6 has been added in Control Plane Policing (CoPP. To enable redirection of IPv6 control packets to the CPU, you must configure IPv6 CoPP on the system. Entering the write erase command on a device that runs Release 5.0(3U3(1 automatically applies CoPP on the device and ensures that all IPv4 and IPv6-related CoPP configuration is set up correctly. If you upgrade from a N-OS release that does not support the CoPP feature to a release that does support the CoPP feature, you must run the setup utility after the upgrade to enable CoPP on the device. If you upgrade from N-OS Release 5.0(3U2(2, which supports the CoPP feature, to N-OS Release 5.0(3U3(1, which adds CoPP classes for IPv6 support, you must run the setup script to enable the IPv6 CoPP feature on the device. In N-OS Release 6.0(2U2(2, the default interface name in LLDP MIB is in short form. To make it long form, you must set lldp portid-subtype to 1. In N-OS Release 6.0(2U2(3, this behavior was reversed. The default interface name in LLDP MIB is now in long form. To make it short form, you must set lldp portidsubtype to 0. If you have set lldp port-subtype to 1 and you are upgrading to N-OS Release 6.0(2U2(4, ensure that you set lldp port-subtype to 0. Limitations The following are the known limitations for N-OS Release 6.0(2U5(2: While installing the NAPI https certificate that is present in the device, the following error message can appear if the user does not have the permission to install this certificate (See CSCup72219: Certificate file read error.please re-check permissions. After configuring the NAPI feature, the default http port (port 80 is still in the listening state even after we run the no nxapi http command. This results in the sandbox becoming accessible. Although the sandbox becomes accessible, HTTP requests from the sandbox to the device do not go through. Thus, the functionality is not affected. (See CSCup Chunking is enabled while displaying ML output for any CLI, and html tags (& lt; and & gt; are displayed instead of < and > both on the sandbox and while running the Python script (See CSCup This is expected behavior. Each chunk should be in ML format for you to parse it and extract everything inside the <body> tag. This is done so that it can be later concatenated with similar output from all the chunks of the CLI ML output. After all the chunks are concatenated to get the complete ML output for the CLI, this complete ML output can be parsed for any parameter. The following workaround is recommended to address this issue: Concatenate the <body> outputs from each chunk Replace all the html tags (& lt; and & gt; with < and > Parse for any ML tag needed If you use the write erase command, you cannot view the output for the show startup feature command. To view the startup configuration, you must then use the show startup-config command. This limitation will remain until you run the copy running-config startup-config command. After that, the show startup-config feature command will display the feature-only configuration output as expected (See CSCuq

32 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Caveats A Python traceback is seen while running the show xml command by using the Python shell. The exception type is httplib.incompleteread. This happens when you use Python scripts to leverage the NAPI for retrieving switch data through ML or JSON. You should handle the exceptions in your Python scripts (See CSCuq While upgrading to a new release, when you create a checkpoint without running the setup script, the checkpoint file does not contain the copp-s-mpls class. After you run the write erase command and reload the switch, the copp-s-mpls class is created when the default configuration is applied. When a rollback is done to this checkpoint file, it detects a change in the CoPP policy and tries to delete all class-maps. Because you cannot delete static class-maps, this operation fails and, in turn, the rollback also fails. This can also happen if you create a checkpoint, then create a new user-defined class and insert the new class before any other existing class (See CSCup The following workarounds are recommended to address this issue: Run setup after upgrading to a new release. Always insert the new classes at the end before a rollback. After an interface is shut down and restarted, and after the device is reloaded, the following are observed (See CSCuh69660: Any trunk port in the VLAN is treated as an IGMP snooping Active Port. Access ports in the VLAN are not treated as IGMP snooping Active ports. The FWM multicast flood-list for VLAN contains all trunk ports and mrouter ports. The following workarounds are recommended to address this issue: Use the show ip igmp snooping vlan x command to see the Active Ports. Use the show platform fwm info vlan x command to see the flood-list. When both the ip icmp-errors source and ip source intf icmp error commands are configured, then the command that is configured last takes effect. Thereafter, if the last configured command is removed, the switch does not get configured with the command that was configured first. Users who upgrade to 6.0(2U5(2 need to run the set up script if they want to enable the MPLS static or the VRRpv3 feature. Link Level Flow Control (LLFC is not supported on 3000 series and 3100 series switches. Caveats The open and resolved bugs for this release are accessible through the Bug Search Tool. This web-based tool provides you with access to the bug tracking system, which maintains information about bugs and vulnerabilities in this product and other hardware and software products. Note: You must have a.com account to log in and access the Bug Search Tool. if you do not have one, you can register for an account. 32

33 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Caveats For more information about the Bug Search Tool, see the Bug Search Tool Help & FAQ. Resolved Bugs in this Release Open Bugs for this Release Known Behaviors for this Release Resolved Bugs in this Release Error! Reference source not found.table 6 lists descriptions of resolved bugs in N-OS Release 6.0(2U5(2. You can use the record ID to search Bug Search Tool for details about the bug. Table 6 N-OS Release 6.0(2U5(2 Resolved Bugs Record Number Resolved Bug Headline CSCur67361 CSCus93049 CSCut01928 CSCut13672 CSCut33289 When adding a particular MAC for an IPSG, an internal error is received, which causes the MAC addition to the database to fail. Deleting the MAC entry during an IPSG operation fails because the entry is not present in the FWM database. switchport block unicast and switchport block multicast CLIs are not effective when they are configured with multiple port-channels. 100M links connected to a 3172T flap continuously or stay down when connected to SuperMicro x9 server ports. Some control protocols like ARP and data traffic do not flow on some of the ports in the system. The switch reloads when attaching a port to a VLAN. Open Bugs for this Release Table 7 lists descriptions of open bugs in N-OS Release 6.0(2U5(2. You can use the record ID to search the Bug Search Tool for details about the bug. Table 7 N-OS Release 6.0(2U5(2 Open Bugs Record Number Open Bug Headline CSCuq01107 CSCuq89687 CSCur12654 CSCur14762 CSCur60142 CSCur76020 Traffic flooded when VPC Po is down with a static MAC entry configured for it. 40G Spirent test center connected port sometimes goes to linkflaperrdisabled. Removing feature mpls ldp also removes the label range config. Upon no shut of the vpc peer-link DC36-101, there is some packet duplication for all the sourced multicast groups. [no] shutdown is always displayed under show running interface. VRRPv3 tracking support to be added. 33

34 3000 Series N-OS Release Notes, Release 6.0(2U5(2 MIB Support Record Number Open Bug Headline CSCur96529 CSCur78515 CSCus31911 CSCus32402 Error message failed to allocate shared memory for per-protocol nexthop (nh type. Port channel members go down after downgrading. Entering the copy ABC running command when the switch has a default/l2 CoPP profile and a file ABC has an L3 CoPP profile config, the PPS credit limit exceeded error is thrown for the copp-s-routingproto1 class-map. Multihop Recursive routes may not be properly installed with MPLS static. Known Behaviors for this Release Large core files are split into 3 or more files. For example: _0x101_fwm_log.3679.tar.gzaa _0x101_fwm_log.3679.tar.gzab _0x101_fwm_log.3679.tar.gzac To decode the multiple core files, first club the files to a single file: $ cat _0x101_fwm_log.3679.tar.gz* > _0x101_fwm_log.3679.tar.gz MIB Support The Management Information Base (MIB list includes proprietary MIBs and many other Internet Engineering Task Force (IETF standard MIBs. These standard MIBs are defined in Requests for Comments (RFCs. To find specific MIB information, you must examine the proprietary MIB structure and related IETF-standard MIBs supported by the 3000 Series switch. The MIB Support List is available at the following FTP sites: ftp://ftp.cisco.com/pub/mibs/supportlists/nexus3000/3000mibsupportlist.html Related Documentation Documentation for the 3000 Series Switch is available at the following URL: The documentation set is divided into the following categories: Release Notes The release notes are available at the following URL: Installation and Upgrade Guides 34

35 3000 Series N-OS Release Notes, Release 6.0(2U5(2 Documentation Feedback The installation and upgrade guides are available at the following URL: Command References The command references are available at the following URL: Technical References The technical references are available at the following URL: Configuration Guides The configuration guides are available at the following URL: Error and System Messages The system message reference guide is available at the following URL: Documentation Feedback To provide technical feedback on this document, or to report an error or omission, please send your comments to We appreciate your feedback. Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the documentation, at: Subscribe to the as a Really Simple Syndication (RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and currently supports RSS version 2.0. and the logo are trademarks or registered trademarks of and/or its affiliates in the U.S. and other countries. To view a list of trademarks, go to this URL: Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between and any other company. (1110R 2015 Systems, Inc. All rights reserved. 35