Introduction to VDC Part 2

Interface Allocation to VDC

--> By default, all the physical interfaces belong to Default VDC.

--> When you create any new VDC in Nexus 7K we need to manually allocate physical interfaces to it.

--> When you move the interface from default VDC to New VDC, all the configuration under interface is erased.

--> If you are not able to assign any interface or interfaces are automatically assigned then it is due to port grouping.

--> Port group is primarily how many numbers of physical ports are present on same hardware ASIC of Nexus Switch.

--> Port group consists of 2 or 4 ports each.

--> if there are 2 ports on the same hardware ASIC of nexus switch then all these 2 Ports must be in same VDC as they are on the same hardware asic.

--> All the interfaces belong to the same port group automatically added to the VDC when you assign an interface.

--> A Physical interface can belong to only one VDC at a time.

VDC Administration

1) Network Admin

--> Admin is the first user created in Nexus 7K Switch.

--> Network Admin role is assigned to Admin user by default.

--> Network Admin is having full functionality of Nexus Switch and it is available only in default VDC.

--> By using Network Admin role, we can create/delete/update Non-Default VDC.

2) Network Operator

--> Network Operator is having read-only functionality in default VDC.

--> By default, no user is assigned to Network Operator role.

--> Network Operator can access all the Non-Default VDC by using switchto command.

3) VDC Admin

--> Admin is the first user created on the new VDC.

--> VDC Admin role is assigned to Admin user by default on Non-Default VDC.

--> VDC Admin is having full functionality of Non-default VDC.

--> VDC Admin user is not having access to other NON-Default VDC using switchto command.

4) VDC Operator

--> VDC Operator is having read-only functionality specific to Non-default VDC.

--> VDC Operator user is not having access to other NON-Default VDC using switchto command.


VDC Deployment Scenarios

1) Used in Migration Secnarios of Data Center

2) Used to create a redundant core and aggregation layer.

3) Used for creating separate environments for test,production and development.

4) Used for creation of different organizations on the same physical switch.

5) Used for Separate application environments.


VDC Fault Domains

--> Each VDC runs its own control plane, data plane, and management plane thus creating a separate fault domain.

--> When control plane fails in one VDC does not affect the control plane of other VDCs.

--> VLAN number and VRF names can be reused within different VDC.

--> By default, no internal communication between different VDC.

-->  A separate connection is required to forward the traffic from one VDC to another VDC.

Configuration:

1) Create a VDC from default or admin VDC:

N7K(config)# VDC Sales

2) Define which switching or I/O module type can be used within the VDC:

N7K(config)# VDC Sales

N7K(config-VDC)# limit-resource module-type m1 f2e

3) Allocate the physical Interfaces to VDC

N7K(config)# VDC Sales

N7K(config-VDC)# allocate-interface e2/1-48

4) Allocate physical resources to the VDC, such as the amount of memory( IPv4/IPV6 unicast routing table, IPV4/IPV6 multicast routing table, number of VLANs, VRF and port-channels etc) that can be assigned to the VDC.

N7K(config)# VDC Sales

N7K(config-VDC)# limit-resources u4route-mem minimum 64 maximum 64

N7K(config-VDC)# limit-resources u6route-mem minimum 64 maximum 64

N7K(config-VDC)# limit-resources vlan minimum 8 maximum 8

N7K(config-VDC)# limit-resources vrf minimum 8 maximum 8

5) Configure HA policy

N7K(config)# VDC Sales

N7K(config-VDC)# ha-policy dual-sup restart

Verification: 

# show VDC

# show VDC detail

# show VDC membership

# show VDC resource

Ref: Cisco.com

Md.Kareemoddin

CCIE # 54759