cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
14106
Views
16
Helpful
32
Replies

Installing and configuring 1000v

vaishali_palkar
Level 1
Level 1

Hi ,

I have downloaded Nexus1000v.4.0.4.SV1.3 and trying to install it.

Installation works fine till I reach the step to register 1000v plug-in on vcenter server.

"new plugin" is always disabled.

I tried command : show vmware vc extension-key on switch console.

It show extension-id :Cisco_Nexsus_1000v_1203930214

What may be the reason , I am not able to register the plugin ?

I cannot proceed futher.

I hope somebody will help me solving this issue.

Thanks

Vaishali

32 Replies 32

Please let me know whether this port profile will work or not

1. 3 pnics on host
   1 nic - eth3/1 - ip addrees 10.192.10.175
   It is used for management port.
   It is on 1 gb switch.
   I do not want to configure port channel on this switch.


   2 nics - eth3/2 - These 2 are portchannel using LACP.
            eth3/3

   These 2 are on n5k switch.
   The corrosponding ports on n5k switch are port channeled using LACP.


So , is this port-channel information ok:

1. port-profile ethernet uplinkprof
2. capability uplink
3. vmware port-group
4. switch mode port trunk
5. switchport trunk allowed vlan 5 , 10
6. channel-group auto mode active subgroup cdp
7. no shutdown
8. system vlan 1
9. state enabled

int ethernet 3/2
inherit port-profileuplinkProf

int ethernet 3/3
inherit port-profileuplinkProf
 

So , for pnic eth3/1 , I am not using port profile because I do not want it to be part of uplink but I need that interface for management purpose.

Is this the correct configutaion or i have to do something else?

Can you please help to figure out the best configutaion for ports I mentioned earlier ?

Thanks

Vaishali,

Couple of comments:

In your sample config, you define "system vlan 1" however you're  not allowing this over the trunk.  Any systems VLANs defined still need  to be allowed over the trunk interfaces.

1. port-profile ethernet uplinkprof
2. capability uplink
3. vmware  port-group
4. switch mode port trunk
5. switchport trunk allowed  vlan 5 , 10
6. channel-group auto mode active subgroup cdp
7. no  shutdown
8. system vlan 1
9. state enabled

If you are separating your Management and  VM uplink traffic you need a separate Uplink Port Profile for each.  LACP will not bring up a Port Channel with a single interface.  Since you want your VM uplink using 2 x 10G nics channeled with LACP and your single 1G Management NIC alone, you would need two ethernet profiles like:

port-profile type ethernet Management-Uplink
capability uplink
vmware  port-group
switchport mode access
switchport access vlan <Mgmt VLAN>

no  shutdown

system vlan <Mgmt VLAN>
state enabled


port-profile type ethernet VM-Uplink
capability uplink
vmware  port-group
switchport mode trunk
switchport trunk allowed vlan x,y,z     <===[EXCLUDING YOUR MGMT VLAN!!]

no  shutdown

system vlan <Control, Packet, IP Storage VLANs>
state enabled

You would then assign your single GB nic to the first Uplink Port Profile in vCenter, and your 2 x 10G nics to the second.

Regards,

Robert