The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure the Cisco Nexus 1000V domain, including creating the domain and assigning VLANs.
This chapter includes the following topics:
•Creating the Control VLAN for the Domain
•Creating the Packet VLAN for the Domain
You must create a domain name for Cisco Nexus 1000V and then add control and packet VLANs for communication and management. This process is part of the initial setup of the a Cisco Nexus 1000V when installing the software. If you need to create a domain later, you can do so using the setup command or the procedures described in this chapter.
Use this procedure to create a domain name for the Cisco Nexus 1000V that identifies the VSM and VEMs; and then add control and packet VLANs for communication and management. This process is part of the initial setup of the Cisco Nexus 1000V when installing the software. If you need to create a domain after initial setup, you can do so using this procedure.
Before beginning this procedure, you must know or do the following:
•If two or more VSMs share the same control and/or packet VLAN, the domain helps identify the VEMs managed by each VSM.
•You are logged in to the CLI in EXEC mode.
•You must have a unique domain ID for this Cisco Nexus 1000V instance.
•You must identify the VLANs to be used for control and packet traffic.
•Cisco recommends using distinct vlans for control and packet traffic.
•Cisco recommends using distinct vlans for different instances of Nexus 1000V (different domains)
•The svs mode command in the SVS Domain Configuration mode is not used and has no effect on a configuration.
•For information about changing a domain ID after adding a second VSM see the Cisco Nexus 1000V High Availability and Redundancy Reference, Release 4.0(4)SV1(1).
1. config t
2. svs-domain
3. domain id domain-id
4. control vlan vlan-id
5. packet vlan vlan-id
6. exit
7. show svs-domain
8. copy running-config startup-config
Example:
n1000v# config t
n1000v(config)# svs-domain
n1000v(config-svs-domain)# domain id 100
n1000v(config-svs-domain)# control vlan 190
n1000v(config-svs-domain)# packet vlan 191
n1000v(config-vlan)# exit
n1000v (config)# show svs domain
SVS domain config:
Domain id: 100
Control vlan: 190
Packet vlan: 191
L2/L3 Aipc mode: L2
L2/L3 Aipc interface: mgmt0
Status: Config push to VC successful.
n1000v(config)#
n1000v(config)# copy run start
[########################################] 100%
n1000v(config)#
Use this procedure to add a control VLAN to the domain.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You have already configured and enabled the required switched virtual interface (SVI) using the document, Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(1). The SVI is also called the VLAN interface and provides communication between VLANs.
•You are familiar with how VLANs are numbered. For more information, see the document,
Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(1).
•Newly-created VLANs remain unused until Layer 2 ports are assigned to them.
1. config t
2. vlan vlan-id
3. name vlan-name
4. state vlan-state
5. exit
6. show vlan id vlan-id
7. copy running-config startup-config
Example:
n1000v# config t
n1000v(config)# vlan 30
n1000v(config-vlan)# name cp_control
n1000v(config-vlan)# state active
n1000v(config-vlan)# exit
n1000v(config)# show vlan id 30
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
30 cp_control active
VLAN Type MTU
---- -----
5 enet 1500
Remote SPAN VLAN
----------------
Disabled
Primary Secondary Type Ports
------- --------- --------------- -------------------------------------------
n1000v(config)# copy run start
[########################################] 100%
n1000v(config)#
Use this procedure to add the packet VLAN to the domain.
Before beginning this procedure, you must know or do the following:
•You are logged in to the CLI in EXEC mode.
•You have already configured and enabled the required switched virtual interface (SVI) using the document, Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(1). The SVI is also called the VLAN interface and provides communication between VLANs.
•You are familiar with how VLANs are numbered. For more information, see the document,
Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(1).
•Newly-created VLANs remain unused until Layer 2 ports are assigned to them.
1. config t
2. vlan vlan-id
3. name vlan-name
4. state vlan-state
5. exit
6. show vlan id vlan-id
7. copy running-config startup-config
Example:
n1000v# config t
n1000v(config)# vlan 31
n1000v(config-vlan)# name cp_packet
n1000v(config-vlan)# state active
n1000v(config-vlan)# exit
n1000v(config)# show vlan id 31
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
31 cp_packet active
VLAN Type MTU
---- -----
5 enet 1500
Remote SPAN VLAN
----------------
Disabled
Primary Secondary Type Ports
------- --------- --------------- -------------------------------------------
n1000v(config)# copy run start
[########################################] 100%
n1000v(config)#
This section provides the domain feature release history.
|
|
|
---|---|---|
Domains |
4.0(4)SV1(1) |
This feature was introduced. |