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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Figure 1-5. Logical Segmentation with VDCs on the Nexus 7000<br />

The default VDC is a fully functional VDC with all capabilities. The default VDC has<br />

special tasks that are unique to the default VDC. Tasks unique to the default VDC are<br />

• VDC creation/deletion/suspend<br />

• Resource allocation: interfaces <strong>and</strong> memory<br />

• NX-OS Upgrade acr<strong>os</strong>s all VDCs<br />

• EPLD Upgrade (for new hardware features)<br />

• Ethanalyzer captures: control plane/data plane (with ACL) traffic<br />

• Feature-set installation for Nexus 2000, FabricPath <strong>and</strong> FCoE<br />

• CoPP<br />

• Port Channel load balancing<br />

• Hardware IDS checks control<br />

If the operational <strong>and</strong> administrative requirements or tasks are met, the default VDC can be<br />

used for production traffic with no issues; some customers may cho<strong>os</strong>e to reserve it for<br />

administrative functions.<br />

The non-default VDC is also a fully functional VDC with all capabilities <strong>and</strong> scale. The<br />

VDC feature offers a superset of functionality; the following features are a subset of VDC<br />

functionality:<br />

• Changes in nondefault VDC affect only that particular VDC.

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

Saved successfully!

Ooh no, something went wrong!