Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
4738
Views
1
Helpful
9
Replies

nexus 1000v Installtion problem: Can't see the data port group in the vCenter

wagde
Level 1
Level 1

‎04-29-2010 04:36 AM

Hi

I'm trying to install and configure the Nexus1000v.4.0.4.SV1.2 according to the Getting Started guide n1000v_gsg.pdf.

I finished the installation and configuration "almost" successfully. Every thing worked fine, until I wanted to connect a VM vNic to the data20 port group. I noticed that the port group (data20) is not shown in the list of the port groups when I try to connect "Network Adapter 1" to it.

If I switch to the Network view. I see that my nexus configured and have a "data20" network. but It have 0 ports.

Can you please help?

Thanx

Wagde

Labels:
0 Helpful
9 Replies 9

abbharga
Level 4
Level 4

‎04-29-2010 05:53 AM

Hi Wagde,

Can you post / attach your configuration from the VSM for us to take a look at?

Abhinav

0 Helpful

wagde
Level 1
Level 1
In response to abbharga

‎04-29-2010 05:57 AM

Hi Abhinav

Can you please tell me what commands should I run in the VSM to get the configuration?

I'm new to cisco nexus 1000v and I'm not familiar with the commands.

Thanx

Wagde

0 Helpful

abbharga
Level 4
Level 4
In response to wagde

‎04-29-2010 05:59 AM

Output of the 'show run' command from the VSM will be fine..

0 Helpful

wagde
Level 1
Level 1
In response to abbharga

‎04-29-2010 06:02 AM

Here you go:

n2# show run

version 4.0(4)SV1(2)

username admin password 5 $1$qHZap8N4$lF/1bHAcf37gElFTvv4Vu1  role network-admin

telnet server enable

ip domain-lookup

ip host n2 172.23.5.124

kernel core target 0.0.0.0

kernel core limit 1

system default switchport

vem 3

  host vmware id a2b92215-0d76-33a4-9df9-a81c8ebe0bdb

snmp-server user admin network-admin auth md5 0xe60b8856f288d60787ef398b8ea5ba28 priv 0xe60b8856f288d60787ef398b8ea5ba28 localizedke

y

snmp-server enable traps license

vrf context management

  ip route 0.0.0.0/0 172.23.5.4

switchname n2

vlan 1,20,260

vdc n2 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 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 ethernet data20

  description "Data"

  vmware port-group

  switchport mode access

  switchport access vlan 20

  no shutdown

  state enabled

port-profile type ethernet system-uplink

  description "System"

  vmware port-group

  switchport mode trunk

  switchport trunk allowed vlan 260

  no shutdown

  system vlan 260

  state enabled

port-profile type ethernet vm-uplink

  description "VM"

  vmware port-group

  switchport mode access

  switchport access vlan 260

  no shutdown

  state enabled

interface Ethernet3/3

  inherit port-profile system-uplink

interface mgmt0

  ip address 172.23.5.124/24

interface control0

boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.2.bin sup-1

boot system bootflash:/nexus-1000v-mz.4.0.4.SV1.2.bin sup-1

boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.2.bin sup-2

boot system bootflash:/nexus-1000v-mz.4.0.4.SV1.2.bin sup-2

svs-domain

  domain id 153

  control vlan 260

  packet vlan 260

  svs mode L2 

svs connection VC

  protocol vmware-vim

  remote ip address 194.29.47.70 port 80

  vmware dvs uuid "3e 30 00 50 9f d0 ff 32-d0 83 e2 e8 2f 06 a4 86" datacenter-name Wagde

  connect

Thanx

Wagde

0 Helpful

abbharga
Level 4
Level 4
In response to wagde

‎04-29-2010 06:12 AM

Wagde,

Here is issue:

You have defined the 'data20' port-profile as an ethernet type profile, which will allow it be be used only for the uplink interface i.e to be applied on the physical ethernet interfaces. For a profile to be used for the VM interfaces it has to be of the type 'vethernet'.

Here is what you can do:

1) On the VSM issue the following command to delete the current data20 port-profile: 'no port-profile data20'

2) Define the port-profile again as: 'port-profile type vethernet data20' and then specify the rest of the configuration.

In the show run it would look something like this:

port-profile type vethernet data20

description "Data"

  vmware port-group

  switchport mode access

  switchport access vlan 20

  no shutdown

  state enabled

Hope this helps!!!

./Abhinav

wagde
Level 1
Level 1
In response to abbharga

‎04-29-2010 06:43 AM

Great thanx

In the getting started guide it's ethernet and not vethernet :-)

I guss it should be fixed.

It's working fine now

Thanx

Wagde

0 Helpful

Vinutha Rao
Cisco Employee
Cisco Employee
In response to wagde

‎05-14-2010 12:34 AM

Hi Wagde,

   Can you please specify which installation guide you are referring to and the section/chapter which has this ambiguity? We will get it corrected.

Thanks,

Vinutha

0 Helpful

wagde
Level 1
Level 1
In response to Vinutha Rao

‎05-15-2010 11:06 PM

Hi

I'm referring to the n1000v_gsg.pdf document

Chapter 4

Page 19

In step 2: The data20 port profile type should be vethernet.

Thanx

Wagde

0 Helpful

Vinutha Rao
Cisco Employee
Cisco Employee
In response to wagde

‎05-17-2010 10:53 PM

Thanks Wagde. The feedback has been submitted to the documentation team.

Thanks,

Vinutha

0 Helpful
Customers Also Viewed These Support Documents

Review Cisco Networking for a $25 gift card