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.

Prerequisites

Following are the prerequisites for egress leaf nodes (such as Leaf1 and Leaf2 in EVPN Anycast MH) to operate in Anycast Multi-Homing (MH) mode:

Each egress leaf node must be configured with the same loopback IP address (ethernet-segment.anycast-multi-homing.ip-address <ip-address>). This IP address is referred to as the Anycast VTEP. This Anycast VTEP must be advertised in the underlay routing protocol (IS-IS, OSPF, or BGP) to ensure reachability from ingress leaf and spine routers.

Note: The Anycast VTEP's loopback state is independent of the Ethernet Segment (ES) state. If the loopback goes down, the A-D per ES route is still advertised.
All egress leaf routers attached to the same ES in Anycast MH mode must use the same Anycast VTEP address.
Note: If the user wants to bring down the loopback interface when an ES goes down, Event Handling System (EHS) can be used.
All egress leaf routers connected to the same ES in Anycast MH mode must use the same ingress VNI for each MAC-VRF.
Note: Asymmetric VNIs are not supported for egress leaf nodes in Anycast MH mode.
The Anycast VTEP feature requires VXLAN termination on at least two distinct IP addresses: the system IP and a non-system IPv4 address. Egress leaf nodes must support VXLAN termination across multiple loopback interfaces.

July 16, 2026