Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
If you have a question or a use case, likely there are others who are experiencing or worked through the same thing. Don't hesitate to jump in and ask or share your knowledge! Post here or in the vMX community.
Need additional guidance? Check out these Juniper Resources.
Ask AI Documentation Technical Bulletins Knowledge Base Day One Books
According to that link the AS path you originally specified will match an AS path of exactly 1620: AS Path to Match Regular Expression Sample Matches AS path is 1234 1234 1234 which is functionally ...
found out that you need to use 'resolve' command for the multihop static route. ------------------------------ DANIEL NG ------------------------------
according to below URl, multihop BFD for static route is not supported on MX if there are more than one next hop. https://www.juniper.net/documentation/us/en/software/junos/static-routing/topics/topic-map/bfd-static-routes.html Juniper ...
at high level, ae as L2 Active Active ESI, with IRB virtual GW, with EVPN-MPLS between MX304 should work VGW and AA ESI will look as one device from SRX's view irb would be .1 as VGW address, .2 and .3 on each MX304 as unique address. but looks like ...
Interesting project, familiar remit (limited changes to surrounding devices). Maybe you should call my employer, Telent Network Services. An EVPN "collapsed core" can work just like the VC, doing both routing and switching, advantages being you now have ...
it works after changing to that regex. however, according to below URL, shouldn't ASN alone work too? https://www.juniper.net/documentation/us/en/software/junos/routing-policy/topics/concept/policy-configuring-as-path-regular-expressions-to-use-as-routing-policy-match-conditions.html ...
try updating your as-path ix to read ".* 1620 .*" <--be sure to include the quotes This will match any routes that have AS 1620 in the AS-Path. According to your policy, it will block them.
Juniper Networks is now part of HPE. Together, we’re building industry-leading, secure, AI-native networks – purpose-built with and for AI. As AI and networking converge, we’re driving a bold transformation across enterprises, service providers, and cloud operators.