Change Summary
Table 1 summarizes the new and changed information in this document, and shows the releases in which each feature is supported. Your software release might not support all the features in this document. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release.
Feature Name |
Description |
Release |
Where Documented |
Port Beaconing |
This feature is supported on Cisco MDS switches that are operating in Cisco N-Port Virtualizer (Cisco NPV) mode. |
8.4(1) |
|
Port Beaconing |
This feature can be used to identify individual switch and directly attached peer ports in a data center environment. |
8.3(1) |
|
Buffer-to-Buffer Credit Recovery |
This feature is supported for F ports. |
8.2(1) |
|
Fibre Channel over Ethernet (FCoE) |
New FCoE commands were introduced and some FCoE commands were modified to align with the commands used in Fibre Channel. |
8.2(1) |
|
Port Monitor |
The link connecting a core switch to a Cisco NPV switch should be treated as an Inter-Switch Link (ISL) (core port) in the port monitor. Previously, core ports were included as access ports and were subject to any portguard actions configured. This allows portguard actions on true access (edge) ports, while ports connecting to Cisco NPV switches remain unaffected. |
8.1(1) |
|
Congestion Drop Timeout and No-Credit Frame Timeout Values for Fibre Channel |
The link connecting a core switch to a Cisco NPV switch should be treated as an ISL (core port) for the purposes of congestion-drop, no-credit-drop, and slowport-monitor thresholds for Fibre Channel. Previously, core ports were subject to any change in the congestion-drop or no-credit-drop mode F value. |
8.1(1) |
|
Slow Drain Detection and Congestion Isolation |
The new Congestion Isolation feature can detect a slow-drain device via port monitor or manual configuration and isolate it from other normally performing devices on an ISL. Once the traffic to the slow-drain device is isolated, the traffic to the rest of the normally behaving devices remain unaffected. Traffic isolation is accomplished via the following three features:
|
8.1(1) |