simple bridging of 2 ethernet ports on ASR1001-X

[mpauls]

Hello,

I recently got a new ASR1001-X running Cisco IOS XE Software, Version 16.04.01.
After trying now 4 days without success creating a simple bridge between 2 ethernet interfaces I decided asking here.

All documentation that I found stated something like this:

interface GigabitEthernet0/0/1
no ip address
negotiation auto
service instance 999 ethernet
encapsulation untagged
bridge-domain 10
!
interface GigabitEthernet0/0/2
no ip address
negotiation auto
service instance 999 ethernet
encapsulation untagged
bridge-domain 10
!
interface BDI10
ip address 192.168.55.1 255.255.255.0

I also tried it with

!
bridge-domain 10
 member GigabitEthernet0/0/1 service-instance 999
 member GigabitEthernet0/0/2 service-instance 999

....

what seems to be the new method doing it.

I connect my computer to GigabitEthernet0/0/1 or GigabitEthernet0/0/2 and can't reach 192.168.55.1 (of course I'm in the same network).
Before someone will ask: yes, the BDI if is not shutdown. ;)

Any ideas for this simple task?

Best regards,

Marc.

[Georg Pauwen]

Hello Marc,

I checked the feature navigator, BDI is supported in 16.03, 16.04 is not listed. I don't know if this means that 16.04 doesn't support BDI, but can you downgrade to 16.03 and check if that makes a difference ?

[mpauls]

I also thought about something like this but as it is a real production system with many clients connected to it this test I'm not willing to do just so ;) because I think it is very very impersistent that suddenly they stopped supporting such an important and trivial feature.

[Georg Pauwen]

I agree, it wouldn't make sense to drop that feature.

I'll check further if I can find something...

[Georg Pauwen]

I wonder if this bug might apply. Can you try to ping anything from the ASR1001 with the BDI as the source:

ASR1001#ping x.x.x.x source BDI IP Address

Ingress Unicast traffic not received on the BDI.
CSCvb36753
Description
Symptom:
** On ASR1001-X running on code 16.3.1, unicast traffic is not been received on the BDI.

** Only ingress traffic is affected. Traffic going out from the BDI works fine

** Issue is not seen for multicast / broadcast traffic.

Conditions:
None

Workaround:
None

Further Problem Description:
Issue seen on or after 3.13.6, 3.16.3 and 3.17.2 releases.

[mpauls]

I tried ping anything with the BDI interface as source. It works. But the packet counters in the BDI interface as well as the "Last input never" doesn't change.

Concerning this bug it really might be this. Great that you found it.

But here:

https://supportforums.cisco.com/discussion/12441656/bridge-domain-issue 

2 years ago someone had the same problem. Mhh... so bug or not?!

Marc.

[Georg Pauwen]

Hello,

it might or might not be a bug. Two years ago, they must have been running something around the 3.x release, so it could be related.

Either way, try to add the below line to your config. I still have a feeling that the problem is with the VLAN tagging:

interface GigabitEthernet0/0/1
no ip address
negotiation auto
cdp enable
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 10
!
interface GigabitEthernet0/0/2
no ip address
negotiation auto
cdp enable
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 10
!
interface BDI10
ip address 192.168.55.1 255.255.255.0

[mpauls]

I already tried defining a separate VRF and assigning it - but no change...

[paul driver]

Hello
I have not implemented bridging on asrs and tbh at ths time not check the cco documentation either but to allow connectivity  between a routiing and bridging environment on ios you can use IRB

bridge irb
bridge 100 protocol ieee
bridge 100 route ip

int bvi 100
ip adress x.x.x. y.y.y.

int x/x
no ip address
bridge-group 100

res
Paul

[mpauls]

Hello,

thanks for your reply. Those bridge-group statements in the int x/x sections in IOS-XE 16 don't exist anymore. Also something like "bridge xxx protocol ieee" seems to be old. I already tried everything according to many manuals... :(

Regards,

Marc.

[esehabdbel]

Hello Marc,

I am facing the same problem did you finally resolve the issue ?

Thank you for your feedback.

Regards,

Abdenour