Wednesday, January 2, 2019

ASR920 help - Metro Ethernet and EVC

So I'm hoping someone on here can potentially help me with configuring an ASR920. The ASR920 does not have sub-interfaces. All dot1Q trunk features are implemented with service instances and BDIs.

Scenario:

I've got multiple links at an NNI coming in on a single port (different VLANS) and I'd like to route the traffic to either the next-hop/VRF/another port.

Right now, I can see the tagged packets show up at the port but nothing is being seen by the service instance / at the BDI.

Can't ping the BDI but get replies from a loopback.

Outputs

# sh run int eth0/0 interface Ethernet0/0 no ip address no keepalive service instance 10 ethernet encapsulation dot1q 10 bridge-domain 10 ! end # sh run int bdi10 interface BDI10 ip address 10.0.0.1 255.255.255.0 end # sh ethernet service instance id 10 interface eth0/0 Identifier Type Interface State CE-Vlans 10 Static Ethernet0/0 Up # sh ip int br | in up Interface IP-Address OK? Method Status Protocol Ethernet0/0 unassigned YES unset up up BDI10 10.0.0.1 YES manual up up Loopback0 10.255.0.1 YES manual up up # ping 10.0.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds: .. Success rate is 0 percent (0/2) # ping 10.0.0.1 source bdi 10 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.0.0.1, timeout is 2 seconds: Packet sent with a source address of 10.0.0.1 ... Success rate is 0 percent (0/3) # ping 10.255.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.255.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/5 ms 

Let me know if you have any ideas or if there is any more info I can provide to make this easier. I can also get eve-ng lab exports mocking this up if you want to test any scenarios.



No comments:

Post a Comment