SDNO Controller Redundancy. Imagine communications Magellan SDNO Controller

Below you will find brief information for SDN Orchestrator Magellan SDNO Controller. This document will guide you through the installation, configuration, and operation of your SDN Orchestrator. It will cover topics such as setting up the SDNO Controller, creating routing systems, configuring switches, and integrating with third-party routers. You will also find information on managing the SDNO Controller, upgrading firmware, and troubleshooting.

PDF

Document

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Redundancy

SDNO Controller Redundancy

The SDNO Controller supports a redundant system in order to ensure system availability in the event of a failure.

The SDNO redundancy model is

Active

and

Standby

, even though the Controllers are referred to as

Primary

and

Secondary

. Only one Controller can be active at any given time.

Note: The UI refers to the Controllers as

Primary

and

Secondary

, but it's important to think of

Controllers using the

Active

and

Standby

notion, because those states define the Controller that is currently functioning and the one backing it up. The Active controller is not necessarily the Primary one; rather, it is the one (could be Primary or Secondary) that took over in the last failover situation (and there may be several such failover situations over a period of time).

This section provides information on configuration of Redundancy settings on the SDNO Controller, operational guidance on how to enable redundancy, how to detect a failover has occurred, and how to force failover from Primary to Secondary.This section also provides guidance on the sequence of events for upgrading the software on a redundant SDNO Controller system during operation.

Note:

All communication between the Primary and Secondary Controller is via ENET5 and ENET6 (if enabled), as these ports are used for

Internal

communication. All communication with

External

devices is via

ENET1-ENET4

Proprietary and Confidential.

Version 2.0 | Page 233

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

Platinum IP3 Frame 1

RC 1

ENET 1

RC 1

ENET 2

RC 2

ENET 1

RC 2

ENET 2

Subnet 6

Subnet 5

SDNO Controller Redundancy

Platinum IP3 Frame 2

RC 1

ENET 1

RC 1

ENET 2

RC 2

ENET 1

RC 2

ENET 2

Subnet 6

Subnet 5 Subnet 5

Subnet 5

Subnet 6

Internal Network Switch

Subnet 5

Subnet 6

Subnet 1

ENET 5 ENET 6

SDNO Controller

(Primary - Active)

ENET 1 ENET 2 ENET 3 ENET 4

Subnet 1 Subnet 3

Subnet 2 Subnet 4

ENET 5 ENET 6

SDNO Controller

(Secondary – Standby)

ENET 1 ENET 2 ENET 3 ENET 4

Subnet 1

Subnet 2

Subnet 3

Subnet 4

External Network Switch

Subnet 2 Subnet 3 Subnet 4 Subnet 1

Proprietary and Confidential.

Version 2.0 | Page 234

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Redundancy

Steps to define a Secondary SDNO Controller

Note:

Before adding a Secondary SDNO Controller, it is recommended you go to the Secondary SDNO

Controller locally, launch a web browser, and define the required Ethernet Interfaces (see Ethernet

Connections) as was done with the Primary SDNO Controller. Ethernet Interfaces can be set by going to

Configure System > Manage SDNO Controller Settings

Network & Redundancy

Network Settings.

In the Controller GUI, click the

Configure System

link in the toolbar at the top.

In the SDNO Routing System Configuration that is displayed, click the

Manage SDNO Controller

Settings

icon.

Click the

Network & Redundancy

button.

Click the

Add Redundant Controller

button.

Enter the

IP Address

of the Secondary SDNO Controller and click

Apply

Ensure you have the required Ethernet Interfaces defined on both Controllers (see Ethernet

Connections). This includes details on the Primary and Secondary IP, Subnet, Gateway for each ENET port.

Note: Once a Controller has been set as Secondary to a Primary Controller and redundancy enabled, the

Secondary (Redundant) Controller can still be accessed by remoting into it. You can also access logging diagnostics on the Secondary Controller via a web browser by going to http://<Secondary_IP>:8002/

Proprietary and Confidential.

Version 2.0 | Page 235

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

Enabling Redundancy

SDNO Controller Redundancy

Once your Secondary SDNO Controller has been set up, click the

Enable Redundancy

button to make redundancy active.

Disabling Redundancy

Once configured, Redundancy can be disabled by clicking the

Disable Redundancy

button.

Note: You may want to disable redundancy during an IP3 upgrade, initial setup, or when changing network settings. Note that when redundancy is disabled, failover doesn't work and data synchronization is turned off. Ensure that you're not in a disabled state except during maintenance or when making changes.

Redundancy Information

The current Redundancy setup can be viewed at any time by going to

System Configuration

Manage

SDNO Controller Settings

Network and Redundancy

Proprietary and Confidential.

Version 2.0 | Page 236

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Redundancy

The diagram displayed will show currently configured details of the Primary SDNO Controller and the

Secondary (if applicable).

Figure 63: Redundancy Setup

Data Sync Status

Data Sync status is displayed on the

System Configuration

Manage SDNO Controller Settings

Network and Redundancy

page as well as on the right side of the Controller homepage (main dashboard).

The

Sync Progress

and

Synchronized

LEDs indicate data synchronization status.

The

Sync Progress

LED is

gray

if:



There is no secondary SDNO Controller present



Redundancy is disabled



No Data Synchronization in progress

Proprietary and Confidential.

Version 2.0 | Page 237

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

The

Synchronized

LED is

green

if:



Data Synchronization is complete



Data Synchronization in progress

Heartbeat Status

SDNO Controller Redundancy

Heartbeat status is displayed on the

System Configuration

Manage SDNO Controller Settings

Network and Redundancy

page as well as on the right side of the Controller homepage.

The LED is

gray

if:



A secondary SDNO Controller has not been defined



Redundancy has not been enabled

The LED is

green

if:



Heartbeat between both Controllers is functioning normally

The LED is

red

if:



Heartbeat not functioning between both Controllers (likely due to networking issues or the

Secondary could be turned off).

Redundancy Status

Redundancy status is displayed on the

System Configuration

Manage SDNO Controller Settings

Network and Redundancy

page. It shows as either

Enabled

Disabled

Proprietary and Confidential.

Version 2.0 | Page 238

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

Redundancy in Depth

Data Synchronization



Synchronization is automatic and from Active to Standby Controller



Synchronization happens using

ENET 5

ENET 6



A status LED on the dashboard shows data synchronization status

SDNO Controller Redundancy

Redundancy based on Primary/Secondary Controller Power Status

The following table explains how failover works in different cases:

Primary

Unavailable

Secondary

Unavailable

Redundancy Behavior

If both Active and Standby Controllers become unavailable, the last known state is maintained.

Unavailable Running

If the Active Controller becomes unavailable, and a Standby is available and configured, the Active fails over to the Standby.

Running Unavailable

If the Primary is Active, and the Secondary becomes unavailable, the Primary continues to be the Active Controller.



If the Primary fails, if the Secondary is in Standby mode, it becomes active.



If the Secondary fails, and the Primary is in Standby mode, it becomes active.

Failover Scenarios

The following table explains different failover scenarios, what triggers them, and the action taken.

Primary

Active

Standby

Secondary

Standby

Active

Fault Scenario

Primary Controller:

All enabled external network cards (1,2,3,4) disconnected

Primary Controller:

All enabled internal network cards (5,6) disconnected

Primary Controller:

Power off or Power reset

Secondary Controller:

All enabled external network cards (1,2,3,4) disconnected

Secondary Controller:

All enabled internal network cards (5,6) disconnected

Secondary Controller:

Power off or Power reset

Failsafe Behavior

Secondary Controller takes over

Primary Controller takes over

Proprietary and Confidential.

Version 2.0 | Page 239

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

Primary Secondary Fault Scenario

Active Active Both Controllers Active

Standby Standby Both Controllers Standby

SDNO Controller Redundancy

Failsafe Behavior

Longest running

Controller takes over

Primary Controller takes over

Failover

From SDNO Controller version 1.3 onwards, failover functions both ways: Primary to Secondary and

Secondary back to Primary. In other words, in a redundant setup (

Active

and

Standby

controller), the

Active Controller is backed up by the Standby Controller. If the Active Controller fails, the Standby takes over. When the (previously) active Controller becomes available again, arbitration logic changes its mode to Standby and it continues to back up the currently active controller

Failover, however, is non-reverting - if control is passed to the Secondary SDNO Controller as the result of a natural failover, and if for some reason you want to restore control back to the original Controller once it becomes available, this needs to be done manually.

You can force failover at any time by going to

Configure System > Manage SDNO Controller Settings >

Network and Redundancy

and clicking the

Failover

button in the Primary Controller section.

Note: For the following settings:

SDNO Controller X/Y ID

Administrator ID

Operator ID

X/Y Server

If a SDNO Controller failover is initiated too soon after a change to these settings, the data synchronization mechanism may not have enough time to sync these changes over to the other SDNO

Proprietary and Confidential.

Version 2.0 | Page 240

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Redundancy

Controller, but regardless, the

Data Sync Status

LEDs may indicate that the SDNO Controllers are

Synchronized.

Failover Trigger Conditions

Failover presumes a redundant set up with Active and Standby Controllers.



Active SDNO Controller powered off



ALL of the "enabled" ENETS on the External network (ENETs 1, 2, 3, and 4) OR Internal network

(ENETs 5 and 6) - connection lost

Proprietary and Confidential.

Version 2.0 | Page 241

Key features

SDN-based routing and control
Simplified network management
Enhanced reliability and scalability
Seamless integration with third-party devices
Advanced monitoring and troubleshooting tools

Frequently asked questions

The SDNO Controller setup process involves connecting the controller to your network, logging in to the web interface, and configuring the Ethernet settings. You can find detailed instructions in the manual

The SDNO Controller requires a specific operating system and network configuration to function properly. The manual outlines the detailed system and network requirements

Creating a routing system involves defining levels, device types, and sources/destinations in the SDNO Database Editor. The manual provides step-by-step instructions on creating a routing system.

User questions

Robert E.

What is the power consumption of the Magellan Server III?

The power consumption information for the Magellan Server III is unavailable in the provided document.

Robert E.

What is the power consumption of the Magellan Server III?

The power consumption information for the Magellan Server III is unavailable in the viewed document. Therefore, a specific answer to this query cannot be provided from the document provided. Power consumption can vary based on configuration and usage.

Michael Q.

What is the device's power consumption?

I am unable to find the power consumption details for the device in the viewed document.

Patricia K.

Where can I find information about the power supply or power consumption of the device?

The manual provides information on power supply status indicators for the Magellan™ SDN Orchestrator, but it does not contain specific details regarding power supply specifications or power consumption.