cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
180560
Views
0
Helpful
1
Replies

Nexus1000v SVS mode l3 and ERSPAN

fly
Explorer
Explorer

I config N1kV in svs mode l3 using interface control0 and run in vlan 1, and application data vlan in vlan 11, when i config ERSPAN , source on VETH7 and destination is 192.168.1.1.12 , i create port-profile ERSPAN, and two vmkernel port on two ESXi.

but when i type commant:

port-profile ERSPAN

system vlan 11

two VEM left VSM, but same config in SVS mode l2 is ok,

what's problem, I think VLAN 11 is a application/data vlan ,not affect VSM and VEM communication.

Thank you!

Tom

port-channel   port-profile
Nexus1000V(config)# port-profile ERSPAN
Nexus1000V(config-port-prof)# system vlan 11
Nexus1000V(config-port-prof)# 2014 Oct  7 09:35:18 Nexus1000V %PLATFORM-2-PFM_VEM_REMOVE_NO_HB: Removing VEM 3 (heartbeats lost)
2014 Oct  7 09:35:18 Nexus1000V %PLATFORM-2-PFM_VEM_REMOVE_NO_HB: Removing VEM 4 (heartbeats lost)
2014 Oct  7 09:35:18 Nexus1000V %PLATFORM-2-MOD_REMOVE: Module 3 removed (Serial number )
2014 Oct  7 09:35:18 Nexus1000V %PLATFORM-2-MOD_REMOVE: Module 4 removed (Serial number )


Nexus1000V# show running-config
version 4.0(4)SV1(3a)
username admin password 5 $1$.aGFgZtH$qSe2G0lAB7JGmKzfLDwL50  role network-admin
no password strength-check
ip domain-lookup
ip host Nexus1000V 10.2.11.5
kernel core target 0.0.0.0
kernel core limit 1
system default switchport
vem 3
  host vmware id 420b5865-b9db-e6dc-0f02-99b3642c5d35
vem 4
  host vmware id 420bbf4d-7a3b-e73e-125a-72a503d2d022
snmp-server user admin network-admin auth md5 0xe90e1fbf4aa6dd0ccde9bb8f2db21c3f
priv 0xe90e1fbf4aa6dd0ccde9bb8f2db21c3f localizedkey
snmp-server enable traps license
vrf context management
  ip domain-name vpod.local
  ip name-server 10.2.11.1
  ip route 0.0.0.0/0 10.2.11.1
hostname Nexus1000V
vlan 1,10-12,111
vdc Nexus1000V id 1
  limit-resource vlan minimum 16 maximum 513
  limit-resource monitor-session minimum 0 maximum 64
  limit-resource vrf minimum 16 maximum 8192
  limit-resource port-channel minimum 0 maximum 256
  limit-resource u4route-mem minimum 32 maximum 80
  limit-resource u6route-mem minimum 16 maximum 48
port-profile type vethernet ERSPAN
  capability l3control
  vmware port-group
  switchport mode access
  switchport access vlan 11
  no shutdown
  state enabled
port-profile type vethernet L3-control
  capability l3control
  vmware port-group
  switchport mode access
  switchport access vlan 1
  no shutdown
  system vlan 1
  state enabled
port-profile type ethernet Unused_Or_Quarantine_Uplink
  description Port-group created for Nexus1000V internal usage. Do not use.
  vmware port-group
  shutdown
  state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
  description Port-group created for Nexus1000V internal usage. Do not use.
  vmware port-group
  shutdown
  state enabled
port-profile type vethernet VM-client
  vmware port-group
  switchport mode access
  switchport access vlan 11
  no shutdown
  state enabled
port-profile type vethernet Vmotion
  vmware port-group
  switchport mode access
  switchport access vlan 12
  no shutdown
  system vlan 12
  state enabled
port-profile type vethernet control-packet
  vmware port-group
  switchport mode access
  switchport access vlan 1
  no shutdown
  system vlan 1
  state enabled
port-profile type ethernet uplink
  vmware port-group
  switchport mode trunk
  switchport trunk allowed vlan 1,10-12,111
  no shutdown
  system vlan 1,10-12
  state enabled

interface Ethernet3/4
  inherit port-profile uplink

interface Ethernet4/4
  inherit port-profile uplink

interface mgmt0
  ip address 10.2.11.5/24

interface Vethernet1
  inherit port-profile L3-control
  description VMware VMkernel, vmk2
  vmware dvport 32

interface Vethernet2
  inherit port-profile control-packet
  description Nexus 1000V - VSM, Network Adapter 1
  vmware dvport 128

interface Vethernet3
  inherit port-profile control-packet
  description Nexus 1000V - VSM, Network Adapter 3
  vmware dvport 129

interface Vethernet4
  inherit port-profile L3-control
  description VMware VMkernel, vmk2
  vmware dvport 33

interface Vethernet5
  inherit port-profile Vmotion
  description VMware VMkernel, vmk3
  vmware dvport 160

interface Vethernet6
  inherit port-profile Vmotion
  description VMware VMkernel, vmk3
  vmware dvport 161

interface Vethernet7
  inherit port-profile VM-client
  description Windows 7 - A, Network Adapter 1
  vmware dvport 192

interface Vethernet8
  inherit port-profile VM-client
  description Windows 7 - B, Network Adapter 1
  vmware dvport 193

interface Vethernet9
  inherit port-profile ERSPAN
  description VMware VMkernel, vmk4
  vmware dvport 224

interface Vethernet10
  inherit port-profile ERSPAN
  description VMware VMkernel, vmk4
  vmware dvport 225

interface control0
  ip address 192.168.1.5/24
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.3a.bin sup-1
boot system bootflash:/nexus-1000v-mz.4.0.4.SV1.3a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.3a.bin sup-2
boot system bootflash:/nexus-1000v-mz.4.0.4.SV1.3a.bin sup-2
monitor session 1 type erspan-source
  source interface Vethernet7 both
  destination ip 192.168.1.12
  erspan-id 999
  ip ttl 64
  ip prec 0
  ip dscp 0
  mtu 128
  header-type 2
  no shut
svs-domain
  domain id 1
  control vlan 1
  packet vlan 1
  svs mode L3 interface control0
svs connection VC
  protocol vmware-vim
  remote hostname vcenter.vpod.local port 80
  vmware dvs uuid "f7 9e 09 50 bc c8 fc 05-82 39 46 ea 19 50 34 3a" datacenter-n
ame vPod
  connect

Nexus1000V#

1 Accepted Solution

Accepted Solutions

YanL
Beginner
Beginner

 

FYI:

 

Note: We only support a single VMK interface per host to be assigned to the L3capability port-profile.

From:

https://communities.cisco.com/docs/DOC-28631

 

  The configuration that you suggested to us has 2 Vmkernels assign to 2 different L3 port profiles. Seams not supported.

View solution in original post

1 Reply 1

YanL
Beginner
Beginner

 

FYI:

 

Note: We only support a single VMK interface per host to be assigned to the L3capability port-profile.

From:

https://communities.cisco.com/docs/DOC-28631

 

  The configuration that you suggested to us has 2 Vmkernels assign to 2 different L3 port profiles. Seams not supported.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers