Requirements for the dual-homing deployment

This HA deployment model requires following conditions:

• Both Cisco Optical Site Manager redundancy and management interfaces must be configured as Loopback interfaces.

• The IP addresses assigned to the MgmtEth interfaces of the devices are typically part of a private subnet, isolated under the Top-of-Rack (ToR) switches.

• Loopback IP addresses are distributed within the Data Communication Network (DCN) and must be reachable from Cisco Optical Network Controller.

• Loopback 0 interfaces are designated as Cisco Optical Site Manager management interfaces.

• Loopback 1 interfaces serve as Cisco Optical Site Manager redundancy interfaces, also providing direct access to the devices.

Implementing this deployment model requires specific network configurations and routing considerations:

• ToR switches must advertise the default route to downstream devices. This can be achieved by configuring a static route on the devices or by using `default-information originate` with OSPF on the switches.

• The two devices hosting Cisco Optical Site Manager in high availability must have a static route or routing protocol configuration to reach the peer's Cisco Optical Site Manager redundancy interface (for example, Loopback 1 interface) using the VRRP IP as the next hop.

• ToR switches should implement VRRP and channel aggregation on multiple ports towards the peer switch for enhanced redundancy.

This figure explains the connections diagram of two-degrees node deployment model with devices connected to DCN in dual-homing.

IP addressing schema for devices connected to DCN in dual-homing

This table details the IP addressing for the devices connected to DCN in dual-homing deployment model, with MgmtEth interfaces of the devices using the 192.168.1.0/24 subnet and loopback interfaces distributed within the DCN as part of the 10.1.1.0/27 subnet.

Requirements for the single-homing deployment

This HA deployment model requires following conditions:

• Devices connect to the network over a single MgmtEth interface with a single cable to a single ToR switch.

• The Cisco Optical Site Manager redundancy interface can match the cabled interface (MgmtEth 0).

• The Cisco Optical Site Manager management interface must be configured as a Loopback interface (Loopback 0).

• IP addresses assigned to the MgmtEth interfaces can be part of a private subnet isolated under the ToR switches.

• The Loopback IP address should be distributed within the Data Communication Network (DCN) and be reachable from CONC.

• Direct access to the devices is always possible through the MgmtEth 0 IP addresses.

This deployment model offers specific operational characteristics and configuration guidelines:

• While a single failure can impact the reachability of a device, Cisco Optical Site Manager configured in high availability remains continuously reachable.

• The address plan and configurations described are specifically focused on the deployment of transponder platforms (e.g., NCS1014) to highlight differences from other deployment models.

• For optical line system platforms (e.g., NCS1010) in a mesh network, where an alternative path to reach the Cisco Optical Site Manager peer device exists via OSC, the address plan and configurations are consistent with models using Loopback interfaces for both Cisco Optical Site Manager redundancy and management interfaces (excluding MgmtEth0/RP0/CPU0/1 configuration if not cabled).

This figure explains the connections diagram of three Cisco Optical Site Manager instances configured in high availability mode on NCS 1000 device with devices connected to DCN in single-homing.

IP addressing schema for devices connected to DCN in single-homing

This table details the IP addressing for the devices connected to DCN in single-homing deployment model, with the MgmtEth interface of the devices in subnet 192.168.1.0/24 and the Loopback interface distributed in the DCN as part of the subnet 10.1.1.0/27.

Requirements for devices interconnected and managed remotely via OSC

This HA deployment model requires these conditions:

• Cisco Optical Site Manager is configured in high availability mode on the remote node.

• The remote node is reachable over the Optical Service Channel (OSC) from other nodes connected to the customer's DCN.

• Devices within the remote node (e.g., Location 2) achieve DCN reachability through multiple paths over the OSC of different degrees.

• The two devices hosting Cisco Optical Site Manager in high availability are directly interconnected through an Ethernet cable connected to their MgmtEth interfaces.

Implementing this deployment model requires specific interface configurations and routing to ensure high availability and remote manageability, independent of failures.

• Both Cisco Optical Site Manager redundancy and management interfaces must be configured as Loopback interfaces to ensure reachability independent of potential failures.

• IP addresses assigned to the MgmtEth interfaces (used for device interconnection) and GigabitEthernet interfaces must be strategically distributed within the network to support interconnection failures.

• Loopback IP addresses must be distributed within the DCN and be reachable from the Centralized Operations and Network Control (CONC) system.

• The two devices hosting Cisco Optical Site Manager in high availability in the remote location, which are directly interconnected via an Ethernet cable on their MgmtEth interfaces, require a static route or routing protocol configuration.

• This routing configuration must define how to reach the peer's Cisco Optical Site Manager redundancy interface (e.g., Loopback 1 interface) using the peer's MgmtEth interface as the next hop.

This figure shows a network diagram with three Cisco Optical Site Manager instances in three different locations, configured in HA mode on NCS 1000 family devices. The Cisco Optical Site Manager-2 device in the middle is managed as a remote device.

IP addressing schema for devices interconnected and managed remotely via OSC

This table details the IP addressing for devices in the managed remotely via OSC deployment model. The MgmtEth interfaces are in subnet 192.168.1.12/31, and the Loopback interfaces are distributed in the DCN as part of subnet 10.1.1.0/27.

Requirements for devices interconnected with redundancy and managed remotely via OSC

This HA deployment model requires these conditions:

• Devices in the remote node are interconnected with physical redundancy and lack direct DCN connectivity.

• Cisco Optical Site Manager instances are configured in high availability, accessible via OSC from other nodes connected to the customer's DCN.

• Devices within the remote node (Location 2) achieve DCN reachability through multiple paths over the OSC with varying degrees.

• Two devices hosting Cisco Optical Site Manager in high availability are directly interconnected through both an Ethernet cable plugged into MgmtEth interfaces and an external switch.

Implementing this deployment model requires specific interface configurations and routing to ensure high availability and remote manageability, even with physical redundancy.

• Both Cisco Optical Site Manager redundancy and management interfaces must be configured as Loopback interfaces to ensure reachability independent of potential failures.

• IP addresses assigned to the MgmtEth interfaces (used for device interconnection) and GigabitEthernet interfaces must be strategically distributed within the network to support interconnection failures.

• Loopback IP addresses must be distributed within the DCN and be reachable from the Centralized Operations and Network Control (CONC) system.

• The two devices hosting Cisco Optical Site Manager in high availability in the remote location require a static route or routing protocol configuration.

• This routing configuration must define how to reach the redundancy interface for Cisco Optical Site Manager on the peer device (e.g., Loopback 1 interface) using the peer's MgmtEth interface as the next hop.

This figure illustrates the connection diagram of three Cisco Optical Site Manager instances in three different locations, configured in HA mode on NCS 1000 family devices. The device in the middle, Cisco Optical Site Manager-2, is managed as a remote device.

IP addressing schema for devices interconnected with redundancy and managed remotely via OSC deployment

This table details the IP addressing for the devices interconnected with redundancy and managed remotely via OSC deployment model, with the MgmtEth interfaces of the devices in subnets 192.168.1.0/24 and 192.168.2.12/31 and the Loopback interfaces distributed in the DCN as part of the subnet 10.1.1.0/27.