Elevate

Welcome to the Juniper Elevate Community

hero image


HPE Discover Barcelona 2025

Join us to discover what's next across networking, AI and hybrid cloud.

Learn More

Featured Post

Promoted

Promo tile background

Check out the new TechPost 

Bits and Bytes Articles on Automated WAN Solutions, from Network Engineers to Network Engineers.

Browse Posts

Latest Discussions

  • Posted in: Routing

    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 equivalent to ^1620$ , but your paths are not ...

  • Posted in: Routing

    found out that you need to use 'resolve' command for the multihop static route. ------------------------------ DANIEL NG ------------------------------

  • Posted in: Routing

    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 Bidirectional Forwarding ...

  • Posted in: Routing

    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 IP address is a concern, you may need at least ...

  • Posted in: Routing
  • Posted in: Routing

    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.

  • Posted in: Routing

    i am trying to block all routes from ASN 1620. but the routes are not learnt directly from that AS neighbor. the 'show route aspath-regex' command matches nothing, but both 'received protocol' and 'advertised protocol' commands returns routes from ASN 1620. import policy is applied to ibgp neighbor ...

Latest Articles

  • Posted to: TechPost Blogs

    Do you need secure, isolated multi-tenant connectivity across Kubernetes and cloud infrastructures. JCNR supports SRv6 L3VPN with micro-Segment Identifiers (uSIDs) in various SRv6 endpoint behaviors (End.DT4, End.DT6, End.DT46). Overview Juniper Cloud-Native Router (JCNR) is a containerized, cloud-native routing solution that brings enterprise-grade ...

  • Blog Entry
    Posted to: TechPost Blogs

    Let's use the Juniper filtering tools in a more comprehensive and realistic use case in which MX301 will serve as a filtering routing gateway to protect peering points, critical cloud platforms, or any network infrastructure that requires large-scale security. Introduction This is the second article on the MX301 platform's filtering topic. ...

  • Posted to: TechPost Blogs

    Explore how Juniper’s MX301 router, using Junos 24.4 and its Trio 6 ASIC’s specialized Fast Lookup Table (FLT), accelerates BGP FlowSpec rule processing so that even large and complex FlowSpec filters can be applied without degrading throughput by offloading 5-tuple matches to hardware. Introduction The Juniper Networks MX301 is the newest member ...

Top Contributors of the Week