The VC is UP/UP/UP on both sides, and the MTU does match (it doesn't
come up if they don't). The only odd thing that I see, is on the ASR920
the interworking type is "Ethernet" and on the ASR9K it's "none" (and it
doesn't support Ethernet). On the ASR920:
Local interface: Te0/0/25 up, line protocol up, Eth VLAN 95 up
Interworking type is Ethernet
Destination address: 10.100.25.11, VC ID: 95, VC status: up
MPLS VC labels: local 1631, remote 256476
Group ID: local 31, remote 67109312
MTU: local 9100, remote 9100
VPWS name: test1, State: UP
Te0/0/25 Te0/0/25:95(Eth VLAN) 0 UP UP
pw100038 10.100.25.11:95(MPLS) 0 UP UP
--
Jerry Bacon
Senior Network Engineer
StarTouch, Inc.
http://www.startouch.com
360-543-5679 ext. 111
Microwave - Fiber Optics - Internet Services
On 1/5/2021 11:03 AM, Emille Blanc wrote:
We have had problems with MPLS VC's on ASR's in the past, if the MTU on both
sides don't match.
Though the behavior is erratic - sometimes the VC comes up and won't pass
traffic, sometimes it doesn't come up at all.
We've also never tried an xconnect on an ASR physical interface. Though I don't
have any reason to suspect it wouldn't work, try an untagged service instance?
Do all three VC segments show up/up on the 920?
(sh xconnect int Ten0/0/25)
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
