Interoperability is the facet of an implementation where multiple vendor products come in contact with each other. Fibre Channel standards have been put in place to guide vendors toward common external Fibre Channel interfaces. If all vendors followed the standards in the same manner, then interconnecting different products would become a trivial exercise; however, the Fibre Channel standards are open to interpretation and contain many optional areas.
NX-OS Interop Modes
Cisco NX-OS software supports the following interop modes:
Mode 1 — Standards-based interop mode that requires all other vendors in the fabric to be in interop mode. t interoperates with Brocade and McData switches that have been configured for their own interoperability modes. Brocade and McData switches must be running in interop mode to work with this VSAN mode.
Mode 2 — Brocade native mode (Core PID 0). Integration with specific Brocade switches running in their own native mode of operation. Brocade switches must be configured with "core pid = 0" to work with this mode.
Mode 3 — Brocade native mode (Core PID 1). With this VSAN-based interop mode, Brocade switches will not have to be altered from their native mode (core pid = 1) and can be seamlessly added to a new or existing VSAN. This mode is also known as legacy switch interop mode 3.
Mode 4 — McData native mode. This mode, also known as legacy switch interop mode 4, provides seamless integration between VSANs and McData switches running in McData Fabric 1.0 interop mode.
Default or Native Mode — This is the default mode or behavior for a VSAN that is communicating between a SAN composed entirely of MDS 9000 switches.
A VM host is trying to connect to datastores. The connectivity works fine when using only the Nexus switches. Connectivity also works fine when using the HP Fabric switches. However when configuring ISL between Nexus and HP fabric switch the connectivity breaks.
interface mgmt0 vrf member management ip address 172.16.1.10/24 line console line vty
zone default-zone permit vsan 10 zoneset distribute full vsan 10
fcalias name SAN vsan 10 member pwwn SAN zone name ESXI vsan 10 member pwwn ESXI member pwwn SAN zone name WINDOWS vsan 10 member pwwn Win2k8 member fcid Win2k8 member fcid SAN member pwwn SAN zoneset name FABRIC-A vsan 10 member ESXI member WINDOWS zoneset activate name FABRIC-A vsan 10
The command “sh interface brief” shows the status of fabric channel ports.
You need to configure Nexus switch for correct interoperability mode. By default Nexus is in intro mode 1. Also for this particular interoperability to work with other vendor the FCDomain ID in the entire fabric needs to be between 97 and 127 as stated in the Cisco website.
The first link says 9200s support PVLANs, the second link doesn't list a maximum. Does the 9200 series support PVLANs and does it match the 16/20 (primary/secondary) that a 9300 supports? Does the 9200 support PVLAN over VXLAN?https://www.cisco....
Hello.I never run Nexus Swithes...So, I have a few questions. In an environment configured with a VPC Can the traffic of the Orphan port connected to the bottom be forwarded through the peer link??? (I wonder if it works like Catalyst's Inter-link.) ...
hello, i tried to find a document describing it but was not successful. i understood that on an ACI witch a BD and one EPG is always consuming an internal VLAN. maximum numbr of vlans is 3964 (or similar). therfore you can approx copnfigure 1980 EPGs...