![]() To contribute to this post you are welcomed to share troubleshooting methods or any issue you experienced and how you solved it. I hope to have explained L2 circuit in this short blog post. We should see the same show interfaces ge-0/0/0 | match HardwareĬurrent address: 00:0c:29:86:ba:4a, Hardware address: 00:0c:29:86:ba:4aĪs we again see, MAC is being learned with no issues. You can see that j40 learns the MAC address of j35 after an ARP request. Yes we can ping the IP address which is on the same ping 10.0.5.2 count 3Ħ4 bytes from 10.0.5.2: icmp_seq=0 ttl=64 time=39.416 msĦ4 bytes from 10.0.5.2: icmp_seq=1 ttl=64 time=35.215 msĦ4 bytes from 10.0.5.2: icmp_seq=2 ttl=64 time=35.254 msģ packets transmitted, 3 packets received, 0% packet loss ![]() Local interface: ge-0/0/2.800, Status: Up, Encapsulation: VLAN Remote PE: 10.1.1.6, Negotiated control-word: No Interface Type St Time last up # Up trans RD - remote site signaled down XX - unknown LD - local site signaled down RS - remote site standby NC - intf encaps not CCC/TCC TM - TDM misconfigurationīK - Backup Connection ST - Standby ConnectionĬB - rcvd cell-bundle size bad SP - Static Pseudowire OL - no outgoing label IB - TDM incompatible bitrate VM - vlan id mismatch CF - Call admission control failure To see if our setup is working we can ping j35 from j40 show l2circuit connectionsĮI - encapsulation invalid NP - interface h/w not presentĮM - encapsulation mismatch VC-Dn - Virtual circuit DownĬM - control-word mismatch Up - operational We can check the l2circuit status as below. You should also assign a circuit id which should be the same on both show protocols LDP should also be running on loopback show protocolsĪs you can see circuit neighbor address is the loopback of remote device and interface is the local CE facing interface. If OSPF isn’t running properly, don’t expect any L2 circuit. Things to remember are IGP i.e OSPF here is really important as LDP relies on this protocol. On this box as well, ge-0/0/2 is the CE facing interface and it has very similar config to j29. j40 device will think as if it is connected to a show interfaces As you can see we have no IP configuration here as we are connecting a L2 segment. It is a trunk interface and our vlan tag is 800. As you can see ge-0/0/2 is the CE facing interface i.e towards j40 device. Unnecessary interface config is removed from the output. Interface configuration is really important as a single mistake doesn’t bring the link show interfaces L2 circuit is established between j29 and j34. J40 and j35 have no special config, you can put PCs to test the connectivity as well.We don’t care what is on J30 as long as it provides MPLS connectivity, nothing special configured on that device.On this setup all these boxes are in packet mode.J29,j30 and j34 are forming an MPLS cloud.I know they are so far □ but we will set up the circuit and j40 will be able to ping 10.0.5.2 address of j35 from its address 10.0.5.1 which are in the same subnets.įirst of all my assumptions on this setup Look at the following sample topology and assume SRX j29 is in Ankara, which is my hometown □ and j34 (which is in Amsterdam where live currently). Simply, if you set up a Layer 2 circuit between two sites, you can connect the same subnet between two different geographic location over an MPLS cloud. I will briefly show how you can set up Layer 2 circuit between two packet-mode SRX boxes on 12.1X46-D10 release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |