Configuring Promiscuous mode Nexus 1000V VLAN 4095

[ajcolas1978]

Dear all,

This is the first time I ask in the Cisco Support Forum. First of all thanks to everybody for making this happen.

We need to install AppResponse Expert from Riverbed for application performance monitoring & troubleshooting purposes.

This tool (is a virtual machine) needs promiscuous mode enabled in order to monitor all ports on the virtual switch and the VM needs to be connected to VLAN 4095 (VMware's all trunked VLANs).

All our production traffic goes through Nexus 1000V and my question is:

Which is the right way of configuring promiscuous mode in a new port-profile of a Nexus 1000V and assign it the VLAN 4095?

I have found on Internet that promiscuous mode can be only configured with PVLANs.

1. config t

2. port-profile [type {ethernet | vethernet}] name

3. switchport mode private-vlan {host | promiscuous | trunk promiscuous}

Any help will be welcome

Alfonso

[ajcolas1978]

Dear all,

We finally got what we wanted configuring SPAN in the Nexus 1000V.

Using promiscuous mode in PVLANs sounds confusing and was not what we wanted.

Thanks anyway

Alfonso

[andy.liubo]

Hi Alfons,

I meet the same problem as yours. I have vshark from Riverbed deployed in ESXi, and need monitor all ports on Nexus 1000v. But I'm not sure how to configure the SPAN.

Could you please share your knowledge about SPAN configuration in the Nexus 1000V?

Thanks a lot!

Regards,

Andy Liu

[ajcolas1978]

Hi Andy,

Our Nexus 1000V is as follows:

monitor session 1

  description Riverbed AppResponse POC

  source vlan 1510,1600-1620 rx

  destination interface Vethernet367

  no shut

EMEA-DC1-VSM01# show monitor session 1

   session 1

---------------

description       : Riverbed AppResponse POC

type              : local

state             : up

source intf       :

    rx            :

    tx            :

    both          :

source VLANs      :

    rx            : 1510,1600-1620

    tx            :

    both          :

source port-profile :

    rx            :

    tx            :

    both          :

filter VLANs      : filter not specified

destination ports : Veth367

destination port-profile :

Hope it helps,

Best regards,

Alfonso

[andy.liubo]

Hi Alfons,

Thanks for your reply.

I still have questions. Should the destination interface Vethernet367 in promiscuous mode, and assigned in VLAN 4095?

Regards,

Andy Liu

[ajcolas1978]

Hi Andy,

Finally we didn't need to assign any port to VLAN 4095.

We got what we needed just by configuring SPAN (monitor session 1) in our Nexus 1000V (see config in previous answer)

Vethernet367 corresponds to the VM we wanted to send all the traffic to. In your case it will be a different interface.

Hope this helps,

Alfonso

[andy.liubo]

Hi Alfons,

I have vlan 102 and vlan 103, and the monitor session includes traffic from VMs in both vlan 102 and vlan 103. But the destination interface Vethernet139 can only receive traffic from vlan 102. Also, please note that the Vethernet 139 is in vlan 102.

I think maybe I need add another monitor interface, and assign it to vlan 103, so that it can receive traffic from vlan 103.

Regards,

Andy Liu

[ajcolas1978]

Hi again,

Our config is as follows:

monitor session 1

  description Riverbed AppResponse POC

  source vlan 1510,1600-1620 rx

  destination interface Vethernet367

  no shut

and we receive traffic from all VLANs

I don't think you need to create another monitor interface, maybe there is some error in the configuration.

Best regards,

Alfonso

[andy.liubo]

Thanks a lot!

I'll double check the configuration.