- Introduction
- Key Features in Junos OS Release 22.3
- play_arrow Junos OS Release Notes for ACX Series
- play_arrow Junos OS Release Notes for cRPD
- play_arrow Junos OS Release Notes for cSRX
- play_arrow Junos OS Release Notes for EX Series
- play_arrow Junos OS Release Notes for MX Series
- play_arrow What's New
- play_arrow What's New in 22.3R1-S1
- play_arrow What's New in 22.3R1
- Class of Service
- Chassis
- EVPN
- Hardware
- Interfaces
- Junos Telemetry Interface
- J-Web
- Licensing
- MACsec
- MPLS
- Network Address Translation (NAT)
- Network Management and Monitoring
- OpenConfig
- Precision Time Protocol (PTP)
- Routing Policy and Firewall Filters
- Routing Protocols
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Services Applications
- Software Defined Networking (SDN)
- Source Packet Routing in Networking (SPRING) or Segment Routing
- Subscriber Management and Services
- Additional Features
- What’s Changed
- Known Limitations
- Open Issues
- Resolved Issues
- Migration, Upgrade, and Downgrade Instructions
- play_arrow Junos OS Release Notes for NFX Series
- play_arrow Junos OS Release Notes for PTX Series
- play_arrow Junos OS Release Notes for QFX Series
- play_arrow Junos OS Release Notes for SRX Series
- play_arrow Junos OS Release Notes for vMX
- play_arrow Junos OS Release Notes for vRR
- play_arrow Junos OS Release Notes for vSRX
- Licensing
- Finding More Information
- Requesting Technical Support
- Revision History
Routing Protocols
Strip and replace BGP private-AS path (ACX710, JRR200, MX480, PTX10001, QFX5220, and QFX10003)—In Junos OS Release 22.3R1, we have introduced the
strip-as-path
policy option that removes the incoming autonomous system (AS) path as part of the import policy for a BGP session and replaces the received autonomous system (AS) path with the receiving router's local AS number for the receiving session. Note that the local AS number may be different from the number configured underautonomous system
in the[edit routing-options]
hierarchy.If you need to normalize externally injected routes, you can use this policy option for the incoming autonomous system (AS) path so that it may be used similarly to routes that originate solely within the fabric. The new
strip-as-path
policy option has no impact on the BGP export policy.You can configure the
strip-as-path
option underpolicy-options
then
clause:set policy-options policy-statement do-strip term a then strip-as-path