cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2198
Views
4
Helpful
2
Replies
Highlighted
Beginner

Nexus 1000v VSM can't comunicate with the VEM

This is the configuration I have on my vsm

!Command: show running-config

!Time: Thu Dec 20 02:15:30 2012

version 4.2(1)SV2(1.1)

svs switch edition essential

no feature telnet

banner motd #Nexus 1000v Switch#

ssh key rsa 2048

ip domain-lookup

ip host Nexus-1000v 172.16.0.69

hostname Nexus-1000v

errdisable recovery cause failed-port-state

vem 3

  host vmware id 78201fe5-cc43-e211-0000-00000000000c

vem 4

  host vmware id e51f2078-43cc-11e2-0000-000000000009

priv 0xa2cb98ffa3f2bc53380d54d63b6752db localizedkey

vrf context management

  ip route 0.0.0.0/0 172.16.0.1

vlan 1-2

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 vmware-uplinks

  vmware port-group

  switchport mode trunk

  switchport trunk allowed vlan 1-3967,4048-4093

  channel-group auto mode on

  no shutdown

  system vlan 2

  state enabled

port-profile type vethernet Management

  vmware port-group

  switchport mode access

  switchport access vlan 2

  no shutdown

  state enabled

port-profile type vethernet vMotion

  vmware port-group

  switchport mode access

  switchport access vlan 2

  no shutdown

  state enabled

port-profile type vethernet ServidoresGestion

  vmware port-group

  switchport mode access

  switchport access vlan 2

  no shutdown

  state enabled

port-profile type vethernet L3-VSM

  capability l3control

  vmware port-group

  switchport mode access

  switchport access vlan 2

  no shutdown

  system vlan 2

  state enabled

port-profile type vethernet VSG-Data

  vmware port-group

  switchport mode access

  switchport access vlan 2

  no shutdown

  state enabled

port-profile type vethernet VSG-HA

  vmware port-group

  switchport mode access

  switchport access vlan 2

  no shutdown

  state enabled

vdc Nexus-1000v 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 1 maximum 1

  limit-resource u6route-mem minimum 1 maximum 1

interface mgmt0

  ip address 172.16.0.69/25

interface control0

line console

boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1.bin sup-1

boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1.bin sup-1

boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1.bin sup-2

boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1.bin sup-2

svs-domain

  domain id 1

  control vlan 1

  packet vlan 1

  svs mode L3 interface mgmt0

svs connection vcenter

  protocol vmware-vim

  remote ip address 172.16.0.66 port 80

  vmware dvs uuid "ae 31 14 50 cf b2 e7 3a-5c 48 65 0f 01 9b b5 b1" datacenter-n

ame DTIC Datacenter

  admin user n1kUser

  max-ports 8192

  connect

vservice global type vsg

  tcp state-checks invalid-ack

  tcp state-checks seq-past-window

  no tcp state-checks window-variation

  no bypass asa-traffic

vnm-policy-agent

  registration-ip 172.16.0.70

  shared-secret **********

  policy-agent-image bootflash:/vnmc-vsmpa.2.0.0.38.bin

  log-level

for some reason my vsm can't the the vem. I could before, but then my server crashed without doing a copy run start and when it booted up all my config but the uplinks was lost.

When I tried to configure the connection again it wasn't working.

I'm also attaching a screen capture of the vds
and a capture of the regular switch.

I will appreciate very much any help you could give me and will provide any configuration details that you might need.

Thank you so much.

2 REPLIES 2
Highlighted
Cisco Employee

Hello Carlos,

Are you able to ping ESXi vmkernel IP address from VSM ?

Padma

Highlighted
Cisco Employee

Carlos,

   Looking at vds.jpg, you do not have any VEM vmkernel interface attached to port-profile L3-VSM. So fix VSM-VEM communication problem, you either migrate your VEM management vmkernel interface to L3-VSM port-profile of the vds, or create new VMkernel port on your VEM/host and attach it to L3-VSM port-profile.