Operate and maintain
Documents under this category provide functional descriptions and procedures for configuring, operating, and maintaining 7705 SAR software.
- Basic System Configuration Guide
  This guide provides an overview of the CLI and describes 7705 SAR boot options file (BOF) configuration, file system management, and basic system management such as node timing and synchronization.
- Interface Configuration Guide
  This guide describes the functionality of the 7705 SAR cards, modules, and ports and how to configure these components.
- MPLS Guide
  This guide describes how to configure MPLS, RSVP-TE, PCEP, and LDP protocols on the 7705 SAR.
- Quality of Service Guide
  This guide describes the Quality of Service (QoS) functionality provided by the 7705 SAR and how to configure and implement QoS on the router.
- Router Configuration Guide
  This guide describes how to configure logical IP routing interfaces, VRRP filtering, routing policies, and the cflowd tool on the 7705 SAR.
- Routing Protocols Guide
  This guide describes how to configure unicast routing protocols (OSFP, IS-IS, BGP, RIP) and multicast routing protocols (IGMP, MLD, PIM, MSDP) supported on the 7705 SAR.
- Services Guide
  This guide describes how to configure service parameters such as service access points (SAPs) and service destination points (SDPs), Layer 2 and Layer 3 services, security functions (IPSec), and encryption functions (NGE) on the 7705 SAR.
- System Management Guide
  This guide describes how to configure system security and access features, SNMP functionality, and event and accounting logs on the 7705 SAR.

Security termination policy

The security termination policy, as with tunnel encryption, contains the tunnel protocol information and IGP instance. It also includes the local IP address, which identifies the system IP address or loopback address used to identify the local tunnel. This local IP address must match the BGP source IP address or TLDP source IP address; it is the IP address that identifies the SR tunnel terminating on the router for the service using that security termination policy. Multiple EGs can have the same security termination policy.

The security termination policy is a peer and transport tunnel concept. A peer can contain multiple services, some encrypted and others clear text. When a service is encrypted, it accepts only encrypted traffic; any clear text traffic is dropped. In scenarios where the node is connected to PEs that have a mix of ANYsec tunnel encryption, service encryption, and clear text traffic, the rx-must-be-encrypted command must be disabled in order to attach the security termination policy to a service EG and tunnel EG.

October 28, 2026