Operate and maintain
Documents under this category provide background concepts and procedures for configuring, operating, and maintaining SR Linux software.
- ACL and Traffic Steering Guide
  This document describes ACL and policy-based routing configuration for the Nokia Service Router Linux (SR Linux).
- Advanced Configuration Guide
  This document describes how to configure advanced solutions for the Nokia Service Router Linux (SR Linux). Advanced solutions are defined as more complex network-level configurations where additional guidance and more detailed procedures may be required.
- CLI Plug-in Guide
  This document describes how to create custom CLI plug-ins, and defines the classes and utility functions used to create them. It also defines how to install, modify, and remove a CLI plug-in.
- Configuration Basics Guide
  This document describes basic configuration for the Nokia Service Router Linux (SR Linux). Examples of commonly used commands are provided.
- gRIBI Guide
  This guide describes configuration details for the gRPC Routing Information Base Interface (gRIBI) feature set used with the Nokia Service Router Linux (SR Linux).
- Interfaces Guide
  This document describes interface configuration for the Nokia Service Router Linux (SR Linux), including subinterfaces, IRB interfaces, LAGs, DHCP relay, and IPv6 router advertisements.
- MPLS Guide
  This guide describes the services and provides configuration examples for the Multiprotocol Label Switching (MPLS) protocol used with the Nokia Service Router Linux (SR Linux).
- Multicast Guide
  This guide provides an overview of multicast routing concepts and provides configuration examples for Internet Group Management Protocol (IGMP), Multicast Listener Discovery (MLD), and Protocol Independent Multicast (PIM).
- Network Synchronization Guide
  This guide describes the network synchronization features for the Nokia Service Router Linux (SR Linux).
- P4Runtime Guide
  This document describes SR Linux support for P4Runtime and includes procedures for configuring SR Linux to operate with P4Runtime clients.
- Quality of Service Guide for 7220 IXR and 7250 IXR
  This document describes configuration details for the Quality of Service (QoS) feature set used with the Nokia Service Router Linux (SR Linux) on IXR-series platforms.
- Quality of Service Guide for 7730 SXR
  This document describes configuration details for the Quality of Service (QoS) feature set used with the Nokia Service Router Linux (SR Linux) on SXR-series platforms.
- Routing Protocols Guide
  This document describes routing protocol configuration for the Nokia Service Router Linux (SR Linux), including OSPF, IS-IS, and BGP.
- Security Best Practices and Hardening Guide
- Segment Routing Guide
  This document describes configuration details for the Segment Routing feature set used with the Nokia Service Router Linux (SR Linux).
- System Management Guide
  This document describes the interfaces used with the Nokia Service Router Linux (SR Linux).
- VPN Services Guide
  This document describes basic configuration for Layer 2 and Layer 3 Virtual Private Network service functionality on the Nokia Service Router Linux (SR Linux). It presents examples to configure and implement various protocols and services.

Ingress leaf in Anycast MH mode

The ingress leaf node (such as Leaf3 in EVPN Anycast MH) function is mainly a control-plane function and is supported on all platforms, without requiring any datapath extensions.

For creating the Ethernet Segment (ES) destination, the following four operation modes are supported.

Non-Anycast mode

The ingress leaf operates in this mode when the ESI is identified as a non-Anycast MH ES. A non-Anycast MH ES is an ES where all AD per ES routes are received with A=0.

Anycast mode with multiple AD per-ES routes

In this mode, the ingress leaf receives multiple AD per-ES routes for the same ESI, all with the 'A' flag set to 1 and a consistent Anycast VTEP.

The ES destination is created using the Anycast VTEP learned from these routes and the VNI from the first received MAC/IP Advertisement or IP Prefix route.

Anycast mode with a single AD per-ES route

This mode applies when only a single AD per-ES route is received for the ES, or when all but one of the AD per-ES routes have been withdrawn.

The ES destination is created using the next-hop from the AD per-ES route and the VNI from the first received MAC/IP Advertisement or IP Prefix route.

Mismatch mode

This mode occurs when multiple AD per-ES routes are received for the same ESI, but the 'A' flag or Anycast VTEP information is inconsistent. A single route with A=1 is enough for the ingress leaf to be in "anycast mode".

If the ingress leaf receives AD per ES routes with an inconsistent "A" flag or Anycast VTEP information, the ES destination is created using the VTEPs of the AD per-ES routes NLRI next hops (allows load balancing) and the VNI from the first received MAC/IP Advertisement or IP Prefix route.

Only resolved AD per-ES routes (those with a reachable next hop and Anycast VTEP) are considered.

If a route cannot be resolved, BGP applies treat-as-withdraw behavior.

July 16, 2026