Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
Design Guide
© 2010 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 3 of 15
Introduction
This chapter is part of a larger document that provides guidelines for designing and deploying access and
aggregation layers in the data center using Cisco Nexus and Catalyst products.
aggregation layers in the data center using Cisco Nexus and Catalyst products.
This document covers the main additions and differences in Cisco
®
NX-OS Software compared with Cisco Catalyst
®
IOS
®
Software. Use this document as a quick reference to the main commands for building and designing a data
center Layer 2 and Layer 3 infrastructure with Cisco Nexus
®
products. This document is not intended as a
replacement for the configuration guides available from the Cisco public website.
In addition, because features like virtual domain contexts, role-based access, checkpoint and rollback, fabric
extenders, or port profiles are Cisco NX-OS Software-specific, they are explained here so that you can become
familiar with the configuration-specific aspects.
extenders, or port profiles are Cisco NX-OS Software-specific, they are explained here so that you can become
familiar with the configuration-specific aspects.
For additional command-line interface (CLI) configuration information, visit these sites:
●
For information on Cisco Nexus 7000 Series Switches:
●
For information on Cisco Nexus 5000 Series Switches:
●
For information on Cisco Nexus 2000 Series Fabric Extenders:
●
For information on Nexus 1000V Series Switches:
Summary of Cisco NX-OS CLI Commands Used in Data Center Design
Most data center deployments use both Cisco NX-OS and Cisco Catalyst IOS Software. Although the underlying
operating system characteristics differ, from a configuration point of view, the two operating systems are very similar.
This section highlights how some key portions of the data center configuration can be performed with either operating
system.
operating system characteristics differ, from a configuration point of view, the two operating systems are very similar.
This section highlights how some key portions of the data center configuration can be performed with either operating
system.
For more information about the two operating systems, visit:
Virtual Domain Context Concept
Cisco Nexus 7000 Series Switches running Cisco NX-OS Software have introduced the capability to divide a single
physical switch into as many as four virtual switches, referred to as virtual device contexts (VDCs). Each VDC
operates similarly to a standalone switch with a distinct configuration file, complement of physical ports, and separate
instances of necessary control plane protocols such as routing protocols and spanning tree. This means that when
you are operating a Cisco Nexus 7000 Series Switch, it is relevant to know which VDC you are operating.
physical switch into as many as four virtual switches, referred to as virtual device contexts (VDCs). Each VDC
operates similarly to a standalone switch with a distinct configuration file, complement of physical ports, and separate
instances of necessary control plane protocols such as routing protocols and spanning tree. This means that when
you are operating a Cisco Nexus 7000 Series Switch, it is relevant to know which VDC you are operating.
There are four VDCs as of this writing, of which only one, VDC 1 (also called the default) has higher privileges than
the others. VCD 1 can do the following:
the others. VCD 1 can do the following:
●
Create and destroy other VDCs.
●
Allocate resources to VDCs (the main resources that you will allocate are physical interfaces).
●
Set the dual-supervisor redundancy policy.
●
Maintain software.
●
Reboot the system.