The issue seems pretty clear. The error message about encapsulation failed is usually an indication that you are trying to send data and do not have the layer 2 address for the destination. This explanation is confirmed by the debug arp output. You can see lots of requests being sent for 192.168.206.7 but no responses. So that is your problem - you are attempting to communicate with 192.168.206.17 and it is not responding to your arp request.
There's no special reason to using bridging. It's that I'm using it as part of a validated CPE configuration template. It worked in the past. However, this time, the link between the CPE and the PE seems up but ping fails.
The issue appears on our 2911 router. I tried with a 1921 test router. I noticed that the same config (with bridging) does work. However I can not keep this router because it belongs to the provider.
I do have the L2 address of the 192.168.206.17 host, obtained from another site's ARP table. But I could not add a static ARP entry with the following command:
TNRTAGCS01057(config)#arp 192.168.106.17 001b.0de6.f040 arpa bvi2 Bad ARP command - Interface may only be specified when bridging IP TNRTAGCS01057(config)#
Have you specifically used the bridge spanning-disabled command on the subinterface? For some reason, I seem to have had problems with the topology if the STP was not enabled on the interfaces. In other words, have you replicated my configuration exactly down to the letter?
If this does not help then would you perhaps mind posting a debug of debug atm packet command when you try pinging the remote device?
Is there a specific reason why you want to use a Bridged Virtual Interface to configure an IP connection? Are you planning to do some kind of bridging between a local interface and the PVC circuit? This is not a typical configuration you are attempting to use.
In any case, for bridging, you will need to use a different style of configuration. This is an example, I will explain right away:
no ip address
interface ATM0/1/0.1 point-to-point
bridge-group 2 spanning-disabled
protocol bridge broadcast
ip address 192.168.206.18 255.255.255.0
bridge 2 route ip
bridge 2 protocol ieee
First of all, you have to define the bridging specifically for a subinterface, not for all possible PVCs on the physical ATM interface - you are going to use only PVC 0/35, anyway.
You have to enable to use the PVC for a specific purpose, in this case, bridging. That is the reason for the protocol bridge broadcast, also allowing broadcast frames to be bridged across.
The encapsulation you will need to use is AAL5SNAP. This has to be matched by the DSLAM as well but I suppose that it is already set at this value.
Once again - are you sure you want to run bridging in this setup? Why?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...