SDNO Controller Overview. Imagine communications Magellan SDNO Controller

PDF

Документ

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

SDNO Controller Overview

Imagine Communications' Software-Defined Networking (SDN) framework is a hybrid approach that facilitates the seamless integration of IP technology with SDI systems. It provides the necessary tools to gradually migrate current SDI-based infrastructures to IP-based technology in phases, while enabling you to maintain operational and workflow integrity in a hybrid environment.

Software Defined Networking separates the control of the traffic from the switching devices.

Commercial data center grade switches can be used, but application knowledge determines where signals go, rater than COTS switches. Imagine Communications' SDNO System currently supports the use of specific Arista, Brocade, and Cisco switches. Please contact Imagine Communications for specific models and details.

The central product in Imagine Communications' framework is the

Magellan™ SDN Orchestrator

, an overarching software control system for managing hybrid baseband and IP networks. The SDNO

Controller is the routing protocol engine of the SDNO System and provides a centralized point-of-control for the configuration and operation of the routing system. It uses routing control protocols and paradigms to integrate with other systems in the facility that utilize dynamic signal flow connections, while managing the underlying SDI routers, signal mappings, addressing, and translations between SDI and IP.

The SDNO Controller enables the integration of physical operator control panels and traditional routing control devices, including automation systems, multiviewers, master control panels, and other devices in the facility. It manages a variety of devices including Platinum™/Platinum™ IP3 routers, third party routers, Selenio™ MCP devices, EPIC MV™ IP Multiviewers, and commercial off-the-shelf (COTS)

Ethernet switches. It treats all devices in the system like routers, moving traffic from source to destination, controlled via routing protocols.This delivers complete visibility of the entire network, offering a management view for optimal operational monitoring.

With the SDNO Controller, you can set up customized network configuration, mapping both the hardware elements and software services into an SDN framework, providing an operationally transparent and carefully orchestrated migration of operations to an IP-enabled environment. You can also set up specific routes through the network to define how the bits will flow – based on ‘virtual tielines’ – effectively mapping the current operating model of a broadcast center into the next generation of all-IP and hybrid-IP networks.

The SDNO Controller provides a unified database and protocol engine for routing status and control clients, and provides protocol aggregation and support for configuration, status, and alarm management of the routing system. The SDNO Controller’s flexible routing system execution allows for connecting sources and destinations at runtime. The high level of flexibility allows the control system to be aware of different audio channel configurations on different devices, route the signals based on the actual channel alignments as defined in the database, and perform break-away takes based on automation and human control. The flexibility of the system puts the user in control of complex multichannel audio systems – allowing exact definition of relationships between video and audio, and assignment of attributes to organize the audio channels into sensible services.

Proprietary and Confidential.

Version 2.0 | Page 18

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

SDNO System

Routers

E1, E3

E2, E4

Platinum IP3

Platinum PT-RES

E1, E3

E2, E4

Platinum PX-RES

E1 E2 E3 E4 E5 E6

Magellan SDN Control Network Switch

Magellan SDN Managed Data Switch

SDNO Controller Overview

Clients

Magellan RCP

CCS Navigator PC

Client PC

Selenio MCP Frame

UCIP/J2K/ENC/DEC/MDX

Legend

SDNO CONTROL VLAN 2

SDNO CONTROL VLAN 3

SDNO EXTERNAL VLAN 4

SDI

Separate VLANs for each signal type (MPEG,

JPEG2000, UCIP, etc.)

This diagram depicts a typical connection scenario for the SDNO System.



The SDNO Controller plugs into a main switch and its communication with all other devices is via this switch



Routers (Platinum IP3, Platinum with a PT-RES, Platinum with a PX-RES, or third party routers) plug into the main switch



Managed Data Switches (Arista/Brocade/Cisco) plug into the main switch



Selenio MCP Controllers (Primary and Redundant) plug into the main switch



Selenio MCP Modules plug into the Arista/Brocade/Cisco switch, which in turn connect to the main switch



Routers communicate with Selenio MCP frames and modules via the switch



The PC running Magellan CCS Navigator, the Client PC, and any hardware control panels also connect into the main switch

Proprietary and Confidential.

Version 2.0 | Page 19

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Overview

SDNO Controller High Level Overview

The SDNO Controller is a powerful but easy to use web-based tool for configuration and operation of your SDNO System. Packaged in a commercial 1RU computing server, the SDNO Controller connects to

IP3 frames via Ethernet, and to Magellan control panels and other control sources via (separate)

Ethernet. A high-level view of a typical system is shown below.

CONTROL PANELS

Magellan RCP

Web UI

Magellan CCS

Navigator

Network Switch

Magellan SDNO Controller

Silverlight Web UI

Primary SDNO Controller

Network Switch

Third

Party

Router

Redundant SDNO Controller

IP3 Router 1

Figure 2: SDNO System High Level Overview

IP3 Router 2

For systems with is a mix of IP3 and other Imagine Communications routing or processing equipment, the SDNO Controller integrates tightly with the unified Command and Control System, Magellan CCS

Navigator™.

The SDNO Controller acts as an LRC protocol server, and as an XY-NET protocol server, processing routing requests from these protocols into routes across the IP3 routing frames and other routing frames, and generating appropriate control protocol commands to each of those frames. Status from the various frames is aggregated back into full-route status and returned into all of the original protocols to all of the connected clients. The SDNO Controller enables discover, control, and monitoring of IP3 frames which together form a complete non-blocking router. This is currently confined to two frames

using the System Expansion (on page 93) technique. If a specific configuration requires more than one

non-blocking router system (perhaps interconnected by tielines), then separate SDNO Controllers are required for each non-blocking routing complex within the system.

Proprietary and Confidential.

Version 2.0 | Page 20

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Overview

The SDNO Controller can be operated in a full 1:1 redundancy scenario for high availability applications.

See Controller Redundancy (see "SDNO Controller Redundancy" on page 233).

Software upgrades to IP3 frames and their modules are done directly by the SDNO Controller. See

Firmware Foundry (on page 108).

The user interface of the SDNO Controller is a browser-based application based on Microsoft Silverlight

5.0. It can run on any web browser which supports Microsoft Silverlight 5.0. See SDNO Controller Web

UI (on page 22)

The SDNO Controller is typically integrated within an overall command and control environment which undertakes higher-level functionality such as alarm logging and system-level aggregation of faults. To support this kind of integration, the SDNO Controller aggregates all of the controls and alarms from the frames underneath it, and presents them through unified northbound protocols to upper-layer management systems such as Magellan CCS Navigator and Magellan™ NMS Network Management

System.

Features

The SDNO Controller provides or intermediates the following major functions of the routing system:



Maintenance of the Routing Database (sources, destinations, tielines, etc.)



Logical Routing Protocol (LRC)



XY Stream Protocol (XY-Net)



Management, Configuration, and Status of the routing system



Event Logging



Firmware Version Management and Upgrade management



Web-Browser based Management of the routing system



Integration with Magellan CCS-Navigator



Alarm Generation and Management



Parametric Control of Processing functions in the routing system



Signal Route determination and execution across multiple physical IP3 frames



Tieline Management and Control, including tielines to/from 3rd-party routers



Web based utility for router control via any computer or mobile device with HTML5 support

Proprietary and Confidential.

Version 2.0 | Page 21

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual

System and Network Requirements

SDNO Controller Overview

The SDNO Controller is shipped on a commercial server-class computing platform provided by Imagine

Communications. The SDNO Controller services, and some related applications and libraries, come preinstalled on the unit and start at power-on automatically. It is expected that the installation will include network connections of at least 100-Base-T (preferably 1000-Base-T) Ethernet between the SDNO

Controllers and the IP3 Frames.

Generally, the SDNO Controller is accessed remotely using routing protocols and web service technologies; however, it is necessary during installation, diagnostic, and service operations to be able to access the console of the SDNO Controller, either through a KVM or through Remote Desktop techniques.

It is assumed you have the following:



A single (or 2) SDNO Controller intended for use either separately, or in a redundant configuration



One or more IP3 frames that the SDNO Controller(s) will communicate with



A separate client PC with Navigator (5.1 or higher) installed on it



An external network switch connecting the SDNO Controller with the client PC



An internal network switch connecting the SDNO Controller with the IP3 Frame



A keyboard, mouse, and monitor that can be used to directly connect to an SDNO Controller box.



Ensure that you plug in all 6 Ethernet cables before setting up IP addresses

SDNO Controller Web UI

Customer-furnished computers can be used to connect to the SDNO Controller. The SDNO Controller

Web UI is Silverlight based, so Browsers on those computers must meet the minimum requirements specified for support of Microsoft Silverlight 5.0 or higher.

Note:

Ensure the appropriate Silverlight version is used based on the Operating System running on the

PC, be it 32-bit (x86) or 64-bit (x64). The officially supported browser is Internet Explorer 10 or 11. Note that Google Chrome is no longer supported.

Default SDNO Controller PC Credentials (Username/Password)

The pre-installed

username

on the SDNO Controller machine is

harris

, and the pre-installed password for that username is

harrisadmin

. This login has full administrative rights on the local machine.

PCs running Magellan CCS Navigator™

Magellan CCS Navigator™ needs be installed on a separate PC running either Windows 7 Professional

(both 32-bit and 64-bit operating systems are supported), Windows XP (SP 3), Windows 2003 Server

(SP2).

Proprietary and Confidential.

Version 2.0 | Page 22

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Overview

SDNO Controller Protocols



The SDNO Controller acts as a CCS-P proxy between northbound CCS-P Controllers and the various controllable elements in the Router Frames below.



The Silverlight control clients communicate with the SDNO Controller using a combination of

Microsoft. NET WCF, SOAP over TCP, and CCS-P protocols.



The SDNO Controller acts as an LRC routing protocol server and translates LRC routing commands into lower-level routing commands across the various IP3 frames.



The SDNO Controller acts as an XY-Net routing protocol server and translates XY-Net routing commands into lower-level routing commands across the various IP3 frames.



Status of any routing operation is translated and returned back to all LRC and XY-Net clients.



The SDNO Controller acts as a CCS-P server, exposing its own configuration items and also acting as a proxy for the configuration and status items of the frames and modules of the SDNO System it is managing.

Network Traffic and Virtual Networks

The SDNO Controller has six dedicated LAN ports.

Ports 1-4 Control traffic generated via requests from devices such as Magellan CCS Navigator, Control panels, automation, etc.

Ports 5 and 6 Dedicated for communication with Resource Module (PX-RES) commands

Set up separate VLAN/IPVR Frames for different types of traffic.

For a simple SDNO Controller implementation, where there is a Primary and Secondary switch, it is best practice to configure each switch to have multiple VLANs. For example, configure VLAN 110 for

Uncompressed 1.5 Gbps traffic on the Primary Switch and VLAN 210 for Uncompressed 1.5 Gbps on the

Secondary Switch.

On each switch, set up another VLAN for JPEG2000 traffic; 120 and 220 on the Primary and Secondary switches, respectively. Follow the same pattern for MPEG Traffic on VLANs 130/230. It is very important to assign the correct ports that such that Selenio UCIPs are on VLAN 110/210, Selenio JPEG

2000 Encoders and Decoders are assigned to VLAN 120/220, and Selenio MPEG Encoders/Decoders are assigned to VLAN 130/230.

Proprietary and Confidential.

Version 2.0 | Page 23

Magellan™ SDN Orchestrator

Installation, Configuration, and Operation Manual SDNO Controller Overview

X/Y Pass-through Support - Telnetting into a SDNO Controller

You can telnet into a SDNO Controller by entering:

Telnet <IPAddress>



UserName:

leitch



Password:

leitchadmin

Once you telnet in (without specifying the port number), it connects directly to port

Note:

The SDNO Controller telnet only supports XY Pass-Through Protocol; XY Terminal Protocol is not supported.

You will see system heartbeats on connection (t*H,<ID>).

You can get X/Y status, query device status, crosspoint status, etc. For example:

@ I?T

Response from all the XY devices connected to the SDNO Controller

@ S?0

Requests the status of all destinations on Level 0

@ X?<Lvl><Dest>

Requests the crosspoint status of a specific destination on a specific level

@ F?0

Reports level 0 logical size and physical matrix size

Refer the

Serial Protocol Reference Manual

for more details and commands.

Port 23 is the router control terminal and is connected to by default.

PoE

The SDNO System control network is designed to be a closed system. No other IP devices should be placed on this network to avoid conflicts and excess traffic. Further, it has been found that PoE (power over Ethernet) generating devices must not be used as these devices can cause damage to the PX-RES module.