We are starting to work on migrating many layer2 LAN connections over to our MPLS environment. I did a lab on l2vpn and it worked fine - trying it now as a test on a production network and it's not working ;)
A pair of MX80's directly connected to one another - each MX80 has a trunked Ethernet port connected to a notebook computer for testing (each notebook supports dot1q VLAN and the proper VLAN is assigned). Trying to figure out why this won't work and pretty sure it's config related or my lack of understanding on something I thought I understood ;) Between the MX80's is iBGP and LSP's established (remote end example): xx.xx.100.72 11666 15798 15787 0 1 5d 0:11:59 Establ inet.0: 0/0/0/0 bgp.l3vpn.0: 0/0/0/0 bgp.l2vpn.0: 1/1/1/0 inet6.0: 0/0/0/0 bgp.l3vpn-inet6.0: 0/0/0/0 customer-1.l2vpn.0: 1/1/1/0 paul@dis1.millbrook1# run show route receive-protocol bgp xx.xx.100.72 inet.0: 381163 destinations, 511426 routes (381163 active, 0 holddown, 0 hidden) inet.3: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden) mpls.0: 44 destinations, 44 routes (44 active, 0 holddown, 0 hidden) inet6.0: 55308 destinations, 56716 routes (55308 active, 0 holddown, 0 hidden) bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path xx.xx.100.72:1:2:1/96 * xx.xx.100.72 0 I customer-1.l2vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden) Prefix Nexthop MED Lclpref AS path xx.xx.100.72:1:2:1/96 * xx.xx.100.72 0 I Router #1 is xx.xx.100.71 for loopback Router #2 is xx.xx.100.72 for loopback RSVP/LSP is fully established and appears operational. I keep getting "local site signaled down" status on the l2vpn: paul@dis1.millbrook1> show l2vpn connections Instance: customer-1 Local site: dis1.millbrook1 (1) connection-site Type St Time last up # Up trans 2 rmt LD Configuration on router #1 looks like this: interfaces { ge-1/3/5 { description TEST_l2vpn; vlan-tagging; unit 512 { vlan-id 512; } } } policy-options { community vpn-A members target:11666:9000; } routing-instances { customer-1 { instance-type l2vpn; interface ge-1/3/5.512; route-distinguisher xx.xx.100.71:1; vrf-target target:11666:9000; protocols { l2vpn { encapsulation-type ethernet-vlan; interface ge-1/3/5.512; site dis1.millbrook1 { site-identifier 1; interface ge-1/3/5.512; } } } } } Router #2 configuration looks like this: interfaces { ge-1/3/5 { description TEST_l2vpn; vlan-tagging; unit 512 { vlan-id 512; } } } policy-options { community vpn-A members target:11666:9000; } routing-instances { customer-1 { instance-type l2vpn; interface ge-1/3/5.512; route-distinguisher xx.xx.100.72:1; vrf-target target:11666:9000; protocols { l2vpn { encapsulation-type ethernet-vlan; interface ge-1/3/5.512; site dis2.millbrook1 { site-identifier 2; interface ge-1/3/5.512; } } } } } Thanks for any input, Paul _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp