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.

Point-to-multipoint (switch-to-switch) topology

In a multipoint topology with N nodes, each node needs a single Tx-SC and N Rx-SCs, one for each of the peers. For example, 64 Rx-SAs per security zone translates to 32 Rx-SCs, which breaks down to only 32 peers (only 33 nodes in the multipoint topology per security zone, where each node has one Tx-SC and 32 Rx-SCs).

Figure 1. Switch multipoint-to-switch multipoint topology

In the preceding figure, when the 34th node joins the multipoint topology, the other 33 nodes that are already part of this domain do not have SAs to create an Rx-SC for this 34th node. However, the 34th node has a Tx-SC and accepts 32 peers. The 34th node starts to transmit and encrypt the PDUs based on its Tx-SC but, because the other nodes do not have an SC for this SAI, they drop all Rx PDUs.

To ensure that a multicast domain for a single security zone does not exceed 32 peers or the total of all the nodes in a security zone CA domain, Nokia recommends not exceeding 33 nodes. This is the same as if a security zone has four CAs; the total of all nodes in the four CAs must be 33 or less.

October 30, 2024