cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
685
Views
0
Helpful
1
Replies

Issue with vlan tagging between Cisco router and Extreme switch

vonschabel
Level 1
Level 1

I have a Cisco C1111 router that is connected to an Extreme x670 switch and i can't seem to get any traffic through with my configuration.

 

Configuration Extreme:

"configure vman xx tag 143"
"configure vman xx add ports 1:30 tagged"

"configure vman yy tag 1902"
"configure vman yy add ports 1:30 tagged"

 

Configuration Cisco:

 

interface BDI143
vrf forwarding xxxx
ip address x.x.x.x x.x.x.x
no ip redirects
no ip unreachables
no ip proxy-arp
no cdp enable
no shutdown
!
interface BDI 1902
vrf forwarding yyyy
ip address y.y.y.y y.y.y.y
no shutdown

 

interface GigabitEthernet0/0/0
no shutdown
negotiation auto
no ip address
no cdp enable
service instance 143 ethernet
  encapsulation dot1q 143
  rewrite ingress tag pop 1 symmetric
  bridge-domain 143
service instance 1902 ethernet
  encapsulation dot1q 1902
  rewrite ingress tag pop 1 symmetric
  bridge-domain 1902
!

With this configuration I get no traffic flowing through. However, if I change one of the vmans on the extreme switch to untagged with command
"configure vman xx delete ports 1:30"
"configure vman xx add ports 1:30 untagged"

Then i can see my traffic going through and I can see incoming mac-address on the untagged vman with command:

"show xx fdb"
But still no traffic gets through on the tagged vman.

Does anyone know what can be the problem here? Has it something to do with "rewrite ingress tag" in Cisco configuration?

Thanks.

1 Reply 1

Hello,

 

Extreme by default tags all VLANs, so you have to make sure only the native VLAN is tagged. As an example, if you want Vlan 30 to be the native Vlan, the Extreme side would need:

 

--> config vlan 30 add port x untagged

 

and the Cisco side would be Vlan 30 with the 'untagged' keyword under the service instance.

 

 

Review Cisco Networking products for a $25 gift card