Nexus 3548 and dot1q-tunnel

[mustapha.moussa1]

Hi,

I am new to this forum and I have a brief question, does the Nexus3548 support QinQ? 

Thank you

Mustapha

[Mark Malone]

Yes they do

http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3548-switch/data_sheet_c78-707001.html

Cisco Nexus Data Broker

●  Topology support for tap and SPAN aggregation ●  Support for QinQ to tag input source tap and SPAN ports ●  Traffic load balancing to multiple monitoring tools ●  Time stamping using PTP ●  Packet truncation ●  Traffic filtering based on Layer 1 through Layer 4 header information ●  Traffic replication and forwarding to multiple monitoring tools ●  Robust RBAC ●  Northbound Representational State Transfer (REST) API for all programmability support

[mustapha.moussa1]

That's great, would you know which license does it require to configure QinQ? I only have the basic license but if needed I can purchase an upgraded license.

Thank you

Mustapha

[avi]

Hi Mark,

I unable to see the Q in Q will support in your provided link, please cross verify,

http://www.cisco.com/c/en/us/products/collateral/switches/nexus-3548-switch/data_sheet_c78-707001.html

Cisco Nexus Data Broker

●  Topology support for tap and SPAN aggregation ●  Traffic load balancing to multiple monitoring tools ●  Time stamping using PTP ●  Packet truncation ●  Traffic filtering based on Layer 1 through Layer 4 header information ●  Traffic replication and forwarding to multiple monitoring tools ●  Robust RBAC ●  Northbound Representational State Transfer (REST) API for all programmability support

Hello Mustapha,

I am not seen this feature dot1q-tunnel will support on nexus 3548. Have checked on tool only N7K will support. you can see command in 3548 but you will not able to execute the command & if you try it will prompt you error.

[Mark Malone]

It was in that doc a year ago , its been removed , they get updated frequently features added /changed

Cisco Nexus Data Broker

●  Topology support for tap and SPAN aggregation ●  Traffic load balancing to multiple monitoring tools ●  Time stamping using PTP ●  Packet truncation ●  Traffic filtering based on Layer 1 through Layer 4 header information ●  Traffic replication and forwarding to multiple monitoring tools ●  Robust RBAC ●  Northbound Representational State Transfer (REST) API for all programmability support