Reading thru the Nexus 1000V deployment guide, the doc recommended to separate vlan for control/packet and management interfaces on VSM. Let's say I chose to use vlan 10 for control and packet interfaces and excuted the following CLI in the N1KV:
vlan 10
name N1K_Control/Packet
port-profile type vethernet N1K_Control/Packet
vmware port-group
switchport mode access
switchport access vlan 10
no shutdown
system vlan 10
state enabled
svs-domain
domain id 999
control vlan 10
packet vlan 10
svs mode L2
My question is:
Should VLAN 10 be created/defined in the upstream physical switch? OR when I exceute "vlan 10" CLI in N1KV, VLAN 10 would be created?
Thanks,
Ken
Thanks for the explanation Sachin.
Now, I have modified all the eth and veth port-profiles inside N1KV to use the VLANs that were created in the upstream switch.
From vCenter (Home -> Inventory -> Networking), select the N1KV vDS and click on the hosts tab, the state column showed "Out of sync" for all hosts assocated with the N1KV. Also, looking at the eth and veth port-profiles inside vCenter, they were still using the old vlan before the changes.
How can I sync the configuration so that they aren't out of sync anymore?
Thanks,
Ken
Here you go.
N1K-VSM_1# show svs connections
connection vcenter:
ip address: 172.19.246.183
remote port: 88
protocol: vmware-vim https
certificate: default
datacenter name: Core
admin:
max-ports: 8192
DVS uuid: 55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8
config status: Enabled
operational status: Connected
sync status: Complete
version: VMware vCenter Server 4.1.0 build-345043
No. vCenter showed the hosts are disconnected.
Also, the eth and veth port-profiles in vCenter showed that they are using the old vlan info.
Does it take long time to sync?
Hi Robert,
The VSM is Nexus 1000V. I remembered when I tried to change the VLAN and I need to do "no system vlan xx". The following question popup and I answered yes to proceed.
This will remove all system vlans from this port profile. Do you really want to proceed(yes/no)? [yes]
Could that cause the problem? If so, what is the correct to modify the system vlan?
Anyways, below is the running config of the N1KV:
Ken
_________________________
!Command: show running-config
!Time: Wed Aug 10 16:32:22 2011
version 4.2(1)SV1(4a)
no feature telnet
username admin password 5 $1$WJ5wg1U0$hjTXt7xIlxvS6iKVcsrAU. role network-admin
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip domain-lookup
hostname N1K-VSM_1
vem 3
host vmware id 414e3537-3241-3255-5839-333130323133
vem 4
host vmware id 414e3537-3241-3255-5839-333130323135
vem 5
host vmware id 33373531-3839-5553-4535-34364e363353
vem 6
host vmware id 33373531-3839-5553-4535-34364e363456
snmp-server user admin network-admin auth md5 0x124607b9071f117b518792eda385db59 priv 0x124607b9071f117b518792eda385db59 localizedkey
vrf context management
ip route 0.0.0.0/0 10.4.45.1
vlan 1
vlan 440
name N1K_Control/Packet
vlan 441
name Mgmt
vlan 445
name VM_Network_445
vlan 472
name VM_Network_472
vlan 474
name VM_Network_474
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile type ethernet Unused_Or_Quarantine_Uplink
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type ethernet ESX_Mgmt_Uplink
vmware port-group
switchport mode access
switchport access vlan 441
no shutdown
system vlan 441
state enabled
port-profile type ethernet VM_Uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 440,445,472,474
channel-group auto mode on mac-pinning
no shutdown
system vlan 440
state enabled
port-profile type vethernet Mgmt
vmware port-group
switchport mode access
switchport access vlan 441
no shutdown
system vlan 441
state enabled
port-profile type vethernet N1K_Control/Packet
vmware port-group
switchport mode access
switchport access vlan 440
no shutdown
system vlan 440
state enabled
port-profile type vethernet VM_Network_445
vmware port-group
switchport mode access
switchport access vlan 445
no shutdown
state enabled
port-profile type vethernet VM_Network_472
vmware port-group
switchport mode access
switchport access vlan 472
no shutdown
state enabled
port-profile type vethernet VM_Network_474
vmware port-group
switchport mode access
switchport access vlan 474
no shutdown
state enabled
vdc N1K-VSM_1 id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 32 maximum 32
limit-resource u6route-mem minimum 16 maximum 16
limit-resource m4route-mem minimum 58 maximum 58
limit-resource m6route-mem minimum 8 maximum 8
interface port-channel1
inherit port-profile VM_Uplink
vem 4
interface port-channel2
inherit port-profile VM_Uplink
vem 3
interface port-channel3
inherit port-profile VM_Uplink
vem 5
interface port-channel4
inherit port-profile VM_Uplink
vem 6
interface mgmt0
ip address 10.4.45.99/24
interface Vethernet1
inherit port-profile Mgmt
description VMware VMkernel, vmk0
vmware dvport 38 dvswitch uuid "55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8"
vmware vm mac 0023.7DE5.37F6
interface Vethernet2
inherit port-profile Mgmt
description VMware VMkernel, vmk0
vmware dvport 37 dvswitch uuid "55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8"
vmware vm mac 0023.7DE5.3802
interface Vethernet3
inherit port-profile Mgmt
description VMware VMkernel, vmk0
vmware dvport 36 dvswitch uuid "55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8"
vmware vm mac 0014.C2C0.4E43
interface Vethernet4
inherit port-profile Mgmt
description VMware VMkernel, vmk0
vmware dvport 39 dvswitch uuid "55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8"
vmware vm mac 0014.C2C1.0BAD
interface Vethernet5
inherit port-profile VM_Network_445
description Win2003, Network Adapter 1
vmware dvport 576 dvswitch uuid "55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8"
vmware vm mac 0050.56A7.0000
interface Ethernet3/1
inherit port-profile ESX_Mgmt_Uplink
interface Ethernet3/2
inherit port-profile VM_Uplink
interface Ethernet4/1
inherit port-profile ESX_Mgmt_Uplink
interface Ethernet4/2
inherit port-profile VM_Uplink
interface Ethernet5/1
inherit port-profile ESX_Mgmt_Uplink
interface Ethernet5/2
inherit port-profile VM_Uplink
interface Ethernet6/1
inherit port-profile ESX_Mgmt_Uplink
interface Ethernet6/2
inherit port-profile VM_Uplink
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-1
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-2
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-2
svs-domain
domain id 999
control vlan 440
packet vlan 440
svs mode L2
svs connection vcenter
protocol vmware-vim
remote ip address 172.19.246.183 port 88
vmware dvs uuid "55 73 27 50 ba ae 5b 51-17 03 79 2a b9 7e 5b b8" datacenter-name Core
max-ports 8192
connect
vsn type vsg global
tcp state-checks
vnm-policy-agent
registration-ip 0.0.0.0
shared-secret **********
log-level
