cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1085
Views
0
Helpful
3
Replies

1000v promiscuous veth port groups

JCcisco123
Level 1
Level 1

I have setup a promiscuous VETH port group on a 1000v. I have found it works, as in the veth port group can ping all VM's in the secondary community and isolated vLans.


My problem is that Cisco is saying this is NOT supported. They state that the only ports that can be configured as promiscuous are eth ports. This eliminates any possibilty of having VM's have promiscuous access to any PVLan zone.

Why then does the CLI allow for applying "switchport mode private-vlan promiscuous" to a vethernet interface?

port-profile type vethernet SamplePP

  vmware port-group

  switchport mode private-vlan promiscuous

  switchport private-vlan host-association 555 521

  switchport private-vlan mapping 555 520-530,532

  no shutdown

  state enabled

What function is served by applying a promiscuous PVLan to a eth interface?

3 Replies 3

Chad Peterson
Cisco Employee
Cisco Employee

Seems odd we'd say its not supported when the configuration guide shows an example of using promiscuous port on vEth ports:

http://www.cisco.com/en/US/products/ps9902/products_installation_and_configuration_guides_list.html

From config guide example:

switch(config-port-prof)# port-profile type vethernet pvprom

switch(config-port-prof)#   vmware port-group

switch(config-port-prof)#   switchport mode private-vlan promiscuous

switch(config-port-prof)#   switchport private-vlan mapping 153 154-155

switch(config-port-prof)#   no shutdown

switch(config-port-prof)#   state enabled

switch(config-port-prof)# show run port-profile pvprom

!Command: show running-config port-profile pvprom

!Time: Fri Jan  7 15:11:43 2011

version 4.2(1)SV1(4)

port-profile type vethernet pv153

  vmware port-group

  switchport mode private-vlan promiscuous

  switchport private-vlan mapping 153 154-155

  no shutdown

  max-ports 1024

  state enabled

Thank you for replying.

Regarding your comment, that's exactly what I told the TAC engineer. He responded "showing a uplink profile as a 'veth' is misleading and not technically correct...I will be filing a doc bug to have the reference changed."

freost
Level 1
Level 1

Veth promiscous mode is supported. Documentation is somewhat misleading regarding upstream connectivity when veth promiscuous is used but is being corrected.

Review Cisco Networking for a $25 gift card