HP Cisco Nexus 5000 Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1 - Page 6

Changes to the FCoE Model and Related Configuration Send documentation comments to [email protected] Fibre Channel Port Shutdown The following table describes the changes to the interface shutdown command syntax. 4.0(0)-based releases 4.0(1a)N1(1) Upgrade Downgrade The system default switchport shutdown command causes all Fibre Channel ports, virtual or physical, to default to shutdown. The system default switchport shutdown command now configures the administrative state for all Ethernet ports as down. To configure the Fibre Channel ports to shutdown state, use the system default switchport shutdown san command. Ethernet ports will default to shutdown instead of Fibre Channel ports. This capability needs to be reconfigured after the downgrade. Otherwise, the switch will flag the system default switchport shutdown san command as invalid. Switched Port Analyzer (SPAN) The following table describes the changes to SPAN sessions. 4.0(0)-based releases 4.0(1a)N1(1) The default is to keep session in an open state. To shut a session, use the following command: switch(config)# monitor session session-number suspend The default is to keep session state shut. To open a session, use the following command: switch(config)# no monitor session session-number shut Upgrade Downgrade Note The syntax of the command has also changed. The suspend keyword has been changed to shut. SPAN session will be in shut state after the upgrade. If you do not execute a specific shut or no-shut command on the SPAN session, the SPAN session will be in a no suspend state after the downgrade. Changes to the FCoE Model and Related Configuration In the previous Cisco NX-OS 4.0(0)-based releases, the FCoE model allowed Ethernet and FCoE to co-exist on the interface. The virtual interfaces, virtual Ethernet and virtual Fibre Channel (VFC), did not affect each other. For example, if the virtual Ethernet interface was errdisabled, the VFC interface could still be up. With Cisco NX-OS Release 4.0(1a)N1(1), the CLI implementation was changed to provide forward compatibility with the forthcoming T11 FCoE Initialization Protocol (FIP). In this new FCoE model the following is changed: • FCoE traffic is passed over Ethernet; the Ethernet STP controls port status. • FCoE traffic for a VSAN is transported over a single dedicated FCoE-enabled VLAN. Although the CLI implementation requires a VLAN-to-VSAN mapping, the FCoE frames are expected to be untagged or priority-tagged. The FCoE VLAN is not expected to be carried in the FCoE frames. This will change in a future release once FIP-based FCoE is supported. Cisco Nexus 5000 Series Release Notes, Release 4.0(1a)N1(1) 6 OL-16601-01