04-07-2013 12:49 AM
I have a HA Pair setup and everything works fine when both my primary and secondary VSMs are on the same host. However, when I migrate either of my VSMs to another host Communication is lost.
Both hosts are on the same subnet and is able to ping each other. Subnet is 10.20.0.0/16
Any help would be much appreciated..
I also receive this message on my primary VSM:
%VEM_MGR-SLOT5-1-VEM_SYSLOG_ALERT: sfswitchdata : L3 Control and System VLAN configurations not applied on vethernet port. VMware Port[83886108] DVPortGroup[dvportgroup-36347]. L3 Control can be applied only on VMKernel port.
Show module on my VSM produces this output:
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V active *
2 0 Virtual Supervisor Module powered-up
3 248 Virtual Ethernet Module NA ok
4 248 Virtual Ethernet Module NA ok
5 248 Virtual Ethernet Module NA ok
my uplink port profile:
port-profile system-uplinks
type: Ethernet
description: uplinks to management nics p1,2 (v0,1)
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
switchport mode trunk
switchport trunk allowed vlan 20
no shutdown
evaluated config attributes:
switchport mode trunk
switchport trunk allowed vlan 20
no shutdown
assigned interfaces:
Ethernet3/1
Ethernet3/2
Ethernet4/1
Ethernet4/2
Ethernet5/1
Ethernet5/2
port-group: system-uplinks
system vlans: 20
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vservice: no
port-profile role: none
port-binding: static
My vethernet profiles:
port-profile mgmt
type: Vethernet
description:
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
switchport mode access
switchport access vlan 20
no shutdown
evaluated config attributes:
switchport mode access
switchport access vlan 20
no shutdown
assigned interfaces:
Vethernet1
Vethernet3
Vethernet4
Vethernet6
Vethernet7
Vethernet13
Vethernet18
port-group: mgmt
system vlans: 20
capability l3control: yes
capability iscsi-multipath: no
capability vxlan: no
capability l3-vservice: no
port-profile role: none
port-binding: static
port-profile ctrl-pkt
type: Vethernet
description:
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
switchport mode access
switchport access vlan 20
no shutdown
evaluated config attributes:
switchport mode access
switchport access vlan 20
no shutdown
assigned interfaces:
port-group: ctrl-pkt
system vlans: 20
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vservice: no
port-profile role: none
port-binding: static
Solved! Go to Solution.
05-19-2013 04:04 PM
The capability L3 control setting is only for use on the port-profile that the VSM <--> VEM vmk.
You would need a second port-profile to put the VSMs on (all 3 interfaces on them can go in the same port-profile in L3 mode). Just be sure to set the vlan that it's set to as a system vlan.
05-08-2013 12:10 PM
Hi,
Is your vCenter server using port-profile mgmt as the Network? I'm assuming your vCenter is a virtual server as well?
05-19-2013 04:04 PM
The capability L3 control setting is only for use on the port-profile that the VSM <--> VEM vmk.
You would need a second port-profile to put the VSMs on (all 3 interfaces on them can go in the same port-profile in L3 mode). Just be sure to set the vlan that it's set to as a system vlan.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide