Cisco NX-OS and VDCs
The next-generation data center-class operating system has been built by cisco. The data center-class is designed for maximum scalability and application availability. The NX-OS data center-class operating system was built with modularity, resiliency, and serviceability at its foundation. NX-OS is based on the industry-proven Cisco Storage Area Network Operating System (SAN-OS) Software and helps ensure continuous availability to set the standard for mission-critical data center environments. The self-healing and highly modular design of Cisco NX-OS enables for operational excellence increasing the service levels and enabling exceptional operational flexibility. Several advantages of Cisco NX-OS include the following:
Unified data center operating system
Robust and rich feature set with a variety of Cisco innovations
Flexibility and scalability
IPv4 and IPv6 IP routing and multicast features
Comprehensive security, availability, serviceability, and management features
One key benefit of NX-OS is the use of VDCs. Cisco Nexus 7000 Series switches can be segmented into virtual devices based on customer requirements. VDCs offer several benefits such as fault isolation, administration plane, separation of data traffic, and enhanced security. This logical separation provides the following benefits:
Administrative and management separation
Change and failure domain isolation from other VDCs
Address, VLAN, VRF, and vPC isolation
Each VDC appears as a unique device and allows for separate Roles-Based Access Control Management (RBAC) per VDC. This enables VDCs to be administered by different administrators while still maintaining a rich, granular RBAC capability. With this functionality, each administrator can define virtual routing and forwarding instance (VRF) names and VLAN IDs independent of those used in other VDCs safely with the knowledge that VDCs maintain their own unique software processes, configuration, and data-plane forwarding tables.
Each VDC also maintains an individual high-availability (HA) policy that defines the action that the system will take when a failure occurs within a VDC. Depending on the hardware configuration of the system, there are various actions that can be performed. In a single supervisor system, the VDC can be shut down, restarted, or the supervisor can be reloaded. In a redundant supervisor configuration, the VDC can be shut down, restarted, or a supervisor switchover can be initiated.
There are components that are shared between VDC(s), which include the following:
A single instance of the kernel which supports all of the processes and VDCs
System fan trays
Hardware SPAN resources
This figure shows the logical segmentation with VDCs on the Nexus 7000. A common use case is horizontal consolidation to reduce the quantity of physical switches at the data center aggregation layer. In this figure, there are two physical Nexus 7000 chassis; the logical VDC layout is also shown.
VDC Configuration Examples
This section shows the required steps to creating a VDC; once the VDC is created, you will assign resources to the VDC. VDC(s) are always created from the default admin VDC context, VDC context 1.
Note: The maximum number of VDCs that can be configured per Nexus 7000 chassis is four; the default VDC (VDC 1) and three additional VDC(s).
--By Certkey Sales Team