22.05.2017 Views

nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

Nexus Switching 2nd Edition

Nexus Switching 2nd Edition

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

When configuring these VDC types, the following results will occur based on the<br />

following conditions. Conflicting modules are placed in a “suspended” state. With<br />

online insertion <strong>and</strong> removal (OIR), power is supplied, the module is in ok status but<br />

the interfaces are not available for configuration. Only VDC allocation is allowed for<br />

such interfaces, meaning, to move F1 interfaces from an M1-only VDC to an F1 or<br />

mixed-mode VDC.<br />

The introduction of NX-OS 5.2.1 for the Nexus 7000, enables the creation of an FCoE<br />

Storage VDC with F1series I/O modules. For FCoE support on F2 <strong>and</strong> F2-e, a Supervisor-2<br />

or Supervisor-2e must be deployed with NX-OS 6.1.1 <strong>and</strong> higher. The storage VDC enables<br />

traditional Fibre Channel SANs topologies: Fabric A <strong>and</strong> Fabric B separation. Today, there<br />

is support only for one Storage VDC; the default VDC cannot be the storage VDC. The<br />

storage VDC enables separation of job functions for LAN <strong>and</strong> SAN administrators to<br />

preserve current operational models. The storage VDC creates a “virtual” MDS within the<br />

Nexus 7000 with the following feature sets:<br />

• Participates as a full FCF in the network.<br />

• Zoning, FC alias, fcdomains, IVR, Fabric Binding, <strong>and</strong> so on.<br />

• FCoE target support.<br />

• FCoE ISLs to other switches: Nexus 7000, 5000, <strong>and</strong> MDS.<br />

• Only one storage VDC per chassis.<br />

• Does not require Advanced License (VDC).<br />

• Does count toward total VDC count; currently support for four per Nexus 7000 with<br />

Supervisor 1, 4+1 for Supervisor 2, <strong>and</strong> 8+1 for Supervisor 2e.<br />

• Shared interfaces, exception to the rule allowing an interface to exist in only one<br />

VDC. The shared interface concepts are for F1, F2, <strong>and</strong> F2e modules with a CNA<br />

installed in a server. The traffic is based on the L2 Ethertype; Ethernet VDC “owns”<br />

the interface, <strong>and</strong> the storage VDC sees the interface as well.<br />

The shared interface is the only exception to have an interface shared between two VDCs.<br />

The shared interface is supported when an F1 interface has a Converged Network Adapter<br />

(CNA) attached running FCoE. Depending on the Layer 2 Ethertype, the traffic is separated.<br />

There are two components to FCoE. The two Ethertypes are directed only to the storage<br />

VDC running FCoE; all other Ethertypes are directed to the Ethernet VDC (non-storage<br />

VDC):<br />

1. Control plane, FCoE Initialization Protocol (FIP) Ethertype 0x8914<br />

2. Data plane, FCoE 0x8906<br />

Figure 1-6 shows the shared interface concept with a CNA installed in a server connected to<br />

the Nexus 7000 F-Series modules.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!