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.
Imagine Communications Magellan SDNO Controller SDN Orchestrator Installation, Configuration, and Operation Manual
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
Advertisement
Advertisement
Installation, Configuration, and
Operation Manual
Magellan™ SDN Orchestrator
SDNO Controller
Version 2.0
September 2016
Magellan™ SDN Orchestrator SDNO Controller Installation, Configuration, and Operation Manual
Publication Information
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Imagine Communications considers this document and its contents to be proprietary and confidential.
Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal.
This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product.
Trademarks
Magellan™ SDN Orchestrator, Platinum™ IP3, Platinum™ VX, Magellan CCS Navigator™ are trademarks or trade names of Imagine Communications or its subsidiaries.
Microsoft® and Windows® are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies.
Contact Information
Imagine Communications has office locations around the world. For domestic and international location and contact information, visit our Contact page (http://www.imaginecommunications.com/howbuy/contact-us).
Support Contact Information
For domestic and international support contact information see:
Support Contacts (http://www.imaginecommunications.com/how-buy/contact-us)
Worldwide Support e-mail (mailto: [email protected])
Customer Community Portal (http://app.imaginecommunications.com/customercommunity)
Warranty & Contract Information (http://www.imaginecommunications.com/services/customercare)
MyImagine Academy Training (http://www.imaginecommunications-academy.com)
Product Manuals (http://www.imaginecommunications.com/services/product-manuals)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 2
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
Contents
SDNO Controller - Logging in and Ethernet Settings............................................. 26
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 3
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
Invalid Characters in Source, Destination, Alias, Long Name, Description, Level, and Frame Names
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 4
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
Selenio MCP™ Devices in your SDNO System ....................................................... 65
PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System ............. 67
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 5
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 6
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 7
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 8
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 9
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Contents
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 10
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Preface
Preface
Manual Information
Purpose
This manual details the features, installation, operation, maintenance, and specifications for the SDNO
Controller.
Audience
This manual is written for engineers, technicians, and operators responsible for installation, setup, maintenance, and/or operation of the SDNO Controller.
Revision History
Edition Date
A
B
C
December
2012
January
2013
Comments
Preliminary Version
First Release
April 2013 Second Release corresponding to version 1.1 of the Controller firmware.
D January
2014
Third Release corresponding to version 1.2 of the Controller firmware. The following are new features in this release:
Support for adding up to 6 frames to be controlled from a single Controller
Input Matrix Expansion. (See Matrix Expansion (on page 92))
Support for 4K Video (See 4K Support (on page 157))
Information on interfacing with a Legacy router (See Interfacing with a Legacy Router
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 11
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Edition Date Comments
1.3.1 September
2014
1.3.3 February
2015
Preface
Release corresponding to version 1.3.1 of the Controller firmware. The following is new in this release:
Support for Third Party Routers. See Interfacing with a Third Party Router (on page 211 )
Edits to Interfacing with a Legacy Router (on page 215 )
New Soft Panel application. See Soft Panel Application (see "Router Soft Panel" on page 273).
Safe Power Off functionality for SDNO Controllers. See Maintenance (on page 106)
SNMP support. See SNMP Overview (see "SNMP" on page 251)
Database Import/Export functionality in the IP3 Database Editor. See Database Import
New interface and options when adding devices. See Adding a Device (on page 76)
Changes to Add/Insert dialog for sources/destinations in the IP3 Database Editor. See
Support for Platinum Multiviewers. See Platinum SX Pro and Platinum SX Hybrid
PX-RES Redundancy using ENET6. See PX-RES Redundancy (on page 134)
Changes to Redundancy. See SDNO Controller Redundancy (on page 233)
Additions to valid characters in source/destination/level/frame names. See Valid
Characters in Source, Destination, Level, and Frame Names (on page 42)
Tielines and Reserved Tielines. See Tielines (on page 41).
Firmware restrictions on Crosspoint Module upgrades. See Crosspoint (XPT) Modules
Version number changes. No other edits.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 12
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Edition Date
1.5 December
2015
Preface
Comments
Support for Platinum VX
routers in system Mode. See Adding a Platinum VX Router (on
Support for SDNO Controller 15 RU
routers. See Adding a Platinum Router (on page 77)
Adding Devices via X/Y
. See Adding an X/Y Device (on page 81)
Adding Offline Frames
. See Adding Incorrect/Offline Frames (on page 90)
Edits to Router Soft Panel functionality
Operators with read only access. See Operation Modes (on page 274 )
Changes to the Dashboard. See Dashboard (on page 273)
Source/Destination Reports. See Report (on page 290)
SNMP MIB Generator Utility
. See MIB Generator Utility (on page 248 )
New Restrict Editor
for restricted routing of selected logical sources to logical
destinations. See Restrict Editor (on page 155)
Support for 64 Levels. See 64 Levels Support (on page 160)
Updates to Redundancy/Failover
behavior. See SDNO Controller Redundancy (on page
Updated list of IP3 Services
. See SDNO Controller Services (on page 242)
Dahsboard UI updates
, and how different frames are displayed in the dashboard. See
IP3 System List View (see "System List View" on page 45) and Right Pane Displays (on
New Power Supply Status Indicators
on the Dashboard. See Power Supply Status
Single/Dual PX-RES Activation
. See Resource Modules (on page 114)
Updated Frame Faults
(Platinum IP3 and Platinum frames). See Frame Faults - IP3 Frame
(on page 132) and Frame Faults - Platinum Frame with PX-RES (on page 133)
Example use case to
connect two independent systems with tielines
. See Connecting 2
Independent IP3 Systems with Tielines (on page 222).
Example use case to
add a second IP3 Routing System to an existing Routing System
See Adding a Second IP3 Routing System to an existing Routing System (on page 228)
.
Backup and Restore Tool
. See Backup and Restore Tool (on page 245)
Changing Frame IP Addresses
. See Changing Frame IP Addresses (on page 91)
Breakaway of Mono
audio sources. Support for Breakaway of Mono Audio Sources (on
Minor edits to the Logging Server content and UI. See Logging Server (on page 292).
Additions to Database/UI Validation. See Validate (on page 142)
Updates to the
Output Standard
(previously, Sync Reference). See Sync (on page 126)
Reserved Tielines for Snapshots. See Snapshot Scheduler (on page 285)
Automatic increments in numbering by appending a space and a number when
adding/inserting/updating multiple sources/destinations. See Add (on page 138), Insert
(on page 141), Update (on page 142).
Warning about PoE devices. See PoE (on page 24)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 13
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Preface
Edition Date Comments
1.5.1 March 2016
Note about Maximum number of frames. See Adding a Device (on page 76 )
X/Y Passthrough Support. See X/Y Passthrough Support - Telnetting into a SDNO
Controller (see "X/Y Pass-through Support - Telnetting into a SDNO Controller" on page
Support for Platinum SX Hybrid Multiviewers. See Platinum SX Hybrid Modules in the
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 14
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Edition Date
2.0 September
2016
Preface
Comments
Rebranded from IP3 to SDNO
Support for
Sony's IP Live System Manager
. See:
Adding a Sony IP Live Manager device (on page 80 )
Sony's IP Live System Manager (on page 201)
Audio Expansion
support. See Expansion Setup (on page 91 ).
Selenio MCP Devices
in the SDNO System. See:
Selenio MCP™ Devices in your SDNO System (on page 65 )
Sources/Destinations from IPVR Devices (on page 144)
EPIC MV Multiviewers
in the SDNO system. See:
EPIC™ MV Devices in your SDNO System (on page 66 )
Adding an EPIC™ MV IP Multiviewer (on page 88)
Sources/Destinations from IPVR Devices (on page 144)
PX-UCIP Modules
in the SDNO system. See:
PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System (on page 67 )
PX-UCIP Modes and Database Setup (on page 67)
PX-UCIP and Tielines (on page 69)
Module Configuration: PX-UCIP Configuration (on page 180)
Setting up your SDNO Controller
Router Access Control and Database Filtering for third party and client devices.
See Client Device (Access Control) (see "Client Device Router Database Access
Control" on page 98 ) section in the Hardware Foundry
Ability to open Router Ports (on page 105) (in the Manage Controller Settings tab)
UI changes to the SDNO Database Editor
), Update (on page 142 ) in the Database
Editor section
Minor edits to the fields and settings in Sources and Destinations from Selenio MCP
Devices as a result of UI changes to the Database Editor.
Changes to the Routing System Name pre and post SDNO Controller 2.0. See note in
STEP 5 - Define Sources/Destinations (SDNO Database Editor) (see "STEP 4 - Define
Sources/Destinations (SDNO Database Editor)" on page 38)
Support for
CISCO Switches
. See Cisco Setup (on page 62 )
IGMP/IGMP-Plus Switches (see "IGMP/IGMP-Plus Data Switches" on page 152)
Managed/Unmanaged Sources and Destinations (on page 153)
Support for the
LAWO V__link 4 Video-Over-IP Stage Box.
See LAWO V__link 4 - Video-
Over-IP Stage Box (on page 210)
Network Teaming
to allow for grouping of multiple Ethernet adapters to provide load balancing and redundancy, and support failover scenarios. See Network Teaming (on
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 15
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Obtaining Documents
Preface
Product support documents can be viewed or downloaded from our website. Alternatively, contact your
Customer Service representative to request a document.
Unpacking/Shipping Information
Unpacking a Product
This product was carefully inspected, tested, and calibrated before shipment to ensure years of stable and trouble-free service.
1.
Check equipment for any visible damage that may have occurred during transit.
2.
Confirm that you have received all items listed on the packing list.
3.
Contact your dealer if any item on the packing list is missing.
4.
Contact the carrier if any item is damaged.
5.
Remove all packaging material from the product and its associated components before you install the unit.
Keep at least one set of original packaging, in the event that you need to return a product for servicing.
Returning a Product
In the unlikely event that your product fails to operate properly, please contact Customer Service to obtain a Return Authorization (RA) number, and then send the unit back for servicing.
Keep at least one set of original packaging in the event that a product needs to be returned for service.
If the original package is not available, you can supply your own packaging as long as it meets the following criteria:
The packaging must be able to withstand the product’s weight.
The product must be held rigid within the packaging.
There must be at least 2 in. (5 cm) of space between the product and the container.
The corners of the product must be protected.
Ship products back to us for servicing prepaid and, if possible, in the original packaging material. If the product is still within the warranty period, we will return the product prepaid after servicing.
Standards
Refer to the
IP3 Safety and Standards Manual
for details.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 16
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Waste from Electrical and Electronic
Equipment (WEEE) Compliance
Preface
The European Union (EU) Directive 2002/96/EC on Waste from Electrical and Electronic Equipment
(WEEE) deals with the collection, treatment, recovery, and recycling of electrical and electronic waste products. The objective of the WEEE Directive is to assign the responsibility for the disposal of associated hazardous waste to either the producers or users of these products. As of August 13, 2005, the producers or users of these products were required to recycle electrical and electronic equipment at end of its useful life, and may not dispose of the equipment in landfills or by using other unapproved methods. (Some EU member states may have different deadlines.)
In accordance with this EU Directive, companies selling electric or electronic devices in the EU will affix labels indicating that such products must be properly recycled. (See our website for more information.)
Contact your local sales representative for information on returning these products for recycling.
Equipment that complies with the EU directive will be marked with a WEEE-compliant emblem.
Figure 1: WEEE Compliance Emblem
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 17
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Controller Overview
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.
© 2016 Imagine Communications Corp.
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
E1
E2
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
© 2016 Imagine Communications Corp.
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
non-blocking router system (perhaps interconnected by tielines), then separate SDNO Controllers are required for each non-blocking routing complex within the system.
© 2016 Imagine Communications Corp.
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
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
© 2016 Imagine Communications Corp.
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).
© 2016 Imagine Communications Corp.
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.
© 2016 Imagine Communications Corp.
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
23
.
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.
Upgrade Instructions
See standalone document on upgrade instructions. Contact your Customer Support representative for more details.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 24
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Setting up your SDNO Controller
Your SDNO Controller setup involves the following steps:
SDNO Controller Overview
SETUP
Create a Routing System
Set up your Switches
Add Routers to your SDNO Controller via the Web UI
Configure any Selenio MCP Modules you have
Note: Selenio MCP Module settings specific to the SDNO
Controller have been detailed here for your convenience.
Note that these steps are done in the Selenio MCP Web UI; for more details, refer to the documentation that comes with them.
Add any Selenio MCP Modules you have as Devices
See STEP 1 - Create a Routing System (on page 32)
See Setting up and Configuring Switches (on page 57)
Adding a Platinum Router (on page 77 )
Adding a Platinum VX Router (on page 78)
Adding a Third Party Router (on page 79)
Setting up the Selenio Uncompressed
Video‐Over‐IP (UCIP) Module (on page 184 )
Setting up the Selenio JPEG 2000 (J2K) Module (on
Setting up the Selenio MDX Module (on page 191)
Setting up the Selenio Encoder/Decoder Module
Adding Selenio (JPEG 2000/UCIP/ENC/DEC/MDX)
MCP Modules as Devices (on page 86)
Configure any EPIC MV IP Multiviewers
Add any EPIC MV IP Multiviewers you have as Devices
View your Dashboard and System Information
Parametric Device Control for Modules
Frame Specific Parameters
System Configuration and Monitoring
See the EPIC MV documentation.
See Adding an EPIC™ MV IP Multiviewer (on page 88)
See SDNO Controller Navigation
See Parametric Control
See Frame Parameters (on page 122)
See Configuring the System (see "System
MAINTENANCE
Upgrades for Frames, Resource Cards, Modules
Upgrades for SDNO Controllers
Redundancy Support
Access Rights
Logging
See Firmware Foundry (on page 108)
See Upgrading Controller Firmware
See Controller Redundancy (see "SDNO Controller
See User Foundry (on page 106)
See Logging Server (on page 292)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 25
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Controller - Logging in and Ethernet Settings
SDNO Controller - Logging in and
Ethernet Settings
Launching the SDNO Controller Interface
Note:
Connect a keyboard and monitor (console) to the SDNO Controller before performing the operations below.
When starting out-of-the-box, connect directly to the SDNO Controller console. By default, there is no password for both
Administrator
and
Operator.
To log in as Operator, enter
Operator
as Username.
1.
From the console of the SDNO Controller, launch a Web Browser and connect to the SDNO
Controller at
127.0.0.1
2.
The first time you connect to the SDNO Controller, you will be prompted to
add Frames
. Click
No
for now.
3.
Click the
Configure System
Link in the toolbar at the top.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 26
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Controller - Logging in and Ethernet Settings
4.
Go to
Manage SDNO Controller Settings
, click
Network & Redundancy
, then click
Network Settings
.
This dialog specifies the addresses and network parameters for each of the Ethernet ports. To edit, click on a port on the left and make edits in the section on the right. Click
Set
to confirm changes.
Click
Close
when finished.
5.
Click
System Configuration
in the toolbar at the top again to go back to the System Configuration root.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 27
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Controller Ethernet Settings
SDNO Controller - Logging in and Ethernet Settings
Each SDNO Controller has
six (6) Ethernet interfaces
, and requires use of at least two of them to perform correctly.
Figure 3: Ethernet Ports 1-6 on the SDNO Controller
Note: ENETs 1-4 are for routing system client devices, like the Navigator PC, Magellan RCP.
ENETs 5 and 6 are used to connect to IP3 frames.
ENET
ENET1
ENET2
ENET3
ENET4
ENET5
ENET6
The 6 Ethernet interfaces on the SDNO Controller that can be defined by going to
Configure System > Manage SDNO Controller Settings > Network & Redundancy > Network Settings
You can select the Ethernet connection ports that are used and only configure those
The SDNO Controller only accepts connections on enabled Ethernet ports
Disabled ports will not be used even when fully configured and wired
By default,
ENET 5
(internal) and
ENET 1
(external) are enabled
ENET5
and
ENET1
connections (required for the system to be fully functional) are enabled by default and cannot be disabled from the UI
ENET6
(internal) and
ENETs 2/3/4
(external) are disabled by default can be enabled/disabled from the UI
Type
External
External
External
External
Internal
Internal
Connection Status
Enabled. Cannot be disabled.
Can be enabled/disabled.
Can be enabled/disabled
Can be enabled/disabled.
Enabled. Cannot be disabled.
Can be enabled/disabled.
Each of the configurable ENETs (2/3/4/6) can be activated/deactivated by doing the following:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 28
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Controller - Logging in and Ethernet Settings
1.
Select the relevant ENET in the Network Settings dialog by clicking it
2.
Use the Enable/Disable toggle option. Once an ENET has been enabled, you need to set the IP
Address info.
SDNO Controller Factory Default ENET IPs
ENETs
ENET1
ENET5
Factory Default Hardware IPs
192.168.100.247
192.168.100.249
External IPs
Not set
Not applicable
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 29
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
ETH Notes
SDNO Controller - Logging in and Ethernet Settings
ENETs 1-4 are for routing system client devices such as the Navigator PC and Magellan RCP.
ENETs 5-6 are used to connect to IP3 frames.
ENETs 1-4 - External and Hardware IPs (External Network)
The Hardware IP is the IP Address of the Controller box and it stays with the SDNO Controller
The External IP is the IP Address that clients connect to, and is seamlessly transferred over to the Secondary SDNO Controller in case of failover
Clients connecting to the IP3 System should always use the External IP address.
For each ENET, the Hardware IP and External IP should have the same Network ID.
ENETs 5-6 - Hardware IPs (Internal Network)
Internal network. Used for communication between the SDNO Controller(s) and Frame(s)
Subnets
It is required you configure each of the ENETs (1-6) on different subnets
IP Addresses
For the Primary SDNO Controller, ensure that you set the
Hardware IP
address before the
External IP
Address. You cannot choose to provide only an
External IP
address without providing a
Hardware IP
address.
Clients connecting to the SDNO System should use the
External IP
address. Even though the Hardware IP address will work, it is best practice to use External IPs, because in case of failover, external IP addresses are seamlessly transferred over to the SDNO Controller that takes over. Whereas, if Hardware IPs are used, in case of failover, clients will still be attempting to connect to the unavailable IP.
Go to
Configure System > Manage SDNO Controller Settings > Network & Redundancy > Network
Settings
to configure IP addresses.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 30
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Creating a Routing System
Creating a Routing System
Your entire SDNO System is tied together via a Routing System that you need to create in Magellan CCS
Navigator™.
To support compatibility and inter-operation with legacy routers, tielines, and control panels, the SDNO
System routing database engine is designed to tightly coordinate with the Magellan CCS Navigator™ database which supports all of these legacy system elements. For this reason, it is required to install
Magellan CCS Navigator™ , and to associate the SDNO routing system with it.
Routing in the SDNO System is not restricted to Levels and Partitions as with typical industry routers of the past. There is flexibility to route across levels; components within a source and destination are described by their physical location properties, and matched up based on signal attributes that flow from the device type definitions.
Identify a computer which will be used for the routing system database work. It is possible to move this to a different computer in the future; however Magellan CCS Navigator™ Server typically runs on a single computer and keeps a master copy of the database on that computer. This computer must meet the minimum standards documented in the
Magellan CCS Navigator™
User Manual.
Magellan CCS Navigator™ 5.5 or later is required for the SDNO System 2.0
Refer to the Magellan CCS Navigator™ User Manual for details.
Also see the standalone SDNO Controller 2.0 Upgrade Instructions.
The following operations should be done on the PC provisioned as the Navigator Server.
STEP 1 - Create a Routing System (on page 32 )
STEP 2 - Delete the Default Sources and Destinations in DBEditor
STEP 3 - Define Levels in DBEditor (see "STEP 2 - Define Levels in DBEditor" on page 33)
STEP 4 - Define Device Types in DBEditor (see "STEP 3 - Define Device Types in DBEditor" on page 34)
STEP 5 - Define Sources/Destinations (SDNO Database Editor) (see "STEP 4 - Define
Sources/Destinations (SDNO Database Editor)" on page 38)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 31
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
STEP 1 - Create a Routing System
Creating a Routing System
Start
Navigator
. Ensure you are in
Build
Mode.
1.
Create a new routing system by right clicking the
Routers
folder in the left pane, and then selecting
Create > Routing System
2.
Provide a
Name
for the routing system, select the
Perform System Poll
check box, and enter the
IP
Address
of the SDNO Controller
Note: Ensure that you provide the External IP of the SDNO Controller and not the Hardware IP.
3.
Click
OK
to start Polling. You will get a message confirming that a routing configuration operation is in progress. Wait for it to complete.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 32
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
4.
Once complete, you will see the new routing system (with the name you provided) created, and the routers added to that Controller will be displayed under the
Routers
sub folder.
Next, create the Routing System Database.
STEP 2 - Define Levels in DBEditor
1.
Click the
Levels
Tab.
2.
Enter a proper
Name
and
Description
. For example,
WBV
,
Wideband Video
.
Note:
Ensure that video is always on level 0.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 33
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
3.
Define as levels all of the signal types that you plan to switch separately and/or name in device type configurations that follow.
STEP 3 - Define Device Types in DBEditor
Note:
Device types are an extremely important part of the signal definition used in the SDNO routing engine. Take time to consider and plan these device types as part of the system design. See Why Device
Types are Important (on page 37)
1.
Click the
Wizard
button and set up the required device type(s) based on your modules.
2.
Select
Create a New Custom Device Type
, provide a relevant name, for example
IP3 WBV
, and click
Next
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 34
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
3.
In the
Connection Types
dialog, select your connection type, for example
HD Video
, and click
Next
4.
In the
Level Selection
dialog, ensure the starting level matches what you expect, and click
Next
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 35
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
5.
Click
Next
on the
Configure Connection Types
dialog after double-checking the mapping of the components to the levels.
6.
Click
Finish
on the last dialog.
7.
Save
and
Publish
. Close DBEditor.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 36
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
Tip:
The Publish function facilitates easy distribution of logical information, and allows distribution of salvos and other database information in the names.txt file to all of the devices in the routing system. All existing device list components are preselected; however, you can uncheck any selection that you do not want to publish to.
Clicking the Start Transfer button at the bottom left corner of the dialog box starts the file transfer process, during which, information messages are displayed in the Overall Status text box. After each device has the names.txt transferred to it, Navigator's Database Editor sends an X-Y command to the system to let the devices know to refresh their names.txt files. If some devices fail to transfer or the command fails to send, the Retry button is displayed. Clicking the Retry button enables Database Editor to repeat the process for the failed devices.
Why Device Types are Important
Device Types are used in routing systems to identify and organize all of the separately routable parts of a signal. For example, a VTR feed with SDI and two separate AES audio signals. Or an SDI with an embedded 5.1 mix arriving through an FSDX Input Module.
In past routers, it was required to make the distinction between the physical arrival pattern of these signal package -- embedded -vs- AES -- in defining the device types. In the IP3 with Full Physical
Flexibility (FPF) technology, the Device Type serves mainly to identify the subcomponents that route together (regardless of how they physically appear in the router). Even in a router which routes only wideband video, it is required to define a device type for wideband video (as shown below). Even though device types are required in SDNO, no device types are created by default.
Tip:
Device Type definitions should correspond to the standard kinds of feeds (fed from devices) in your plant. Physical associations and how they map to specific physical inputs and outputs will be specified later to match the actual wiring. The wizard contains several templates. With SDNO, because the actual physical associations of video/audio channels are very flexible, the template could say HD Embedded while the audio channels could be physically separate, or come from MADI, or even embedded on other video signals.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 37
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
STEP 4 - Define Sources/Destinations (SDNO
Database Editor)
1.
Launch the
SDNO Database Editor
interface
(
within Navigator) by double clicking
SDNO Routing
System
under your routing system in the
Routers
folder.
Note: If you're creating a brand new routing system in SDNO Controller 2.0, it will show as
SDNO
Routing System
(in the Navigation pane in Navigator). If you have an existing system or if you re-poll an existing routing system created in a version of SDNO Controller prior to 2.0, it will show as
IP3
Routing System
.
2.
The
SDNO Database Editor
screen will be displayed.
See Valid Characters in Source, Destination, Level, and Frame Names (on page 42 ).
3.
In this example, we have
9 Input Modules
installed in the first
56
input slots, and want to create a simple "wiring checkout" database.
Click the
Add
button in the
Sources
tab to start adding your sources.
Add
504
Sources (56 slots, 9 per slot) prefixed by INX, starting at Slot 1, with
Device Type
as
WBV
(previously defined in Navigator).
Click
Add Rows
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 38
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
4.
Click to add Inputs corresponding to other Input Modules you may have in your system.
In this example, we add 8
Input Frame Sync Input Modules
in slots
57-64
.
5.
Next, go to the
Destinations
tab and click
Add
to start adding your Outputs (Destinations).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 39
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
In this example, we have
31 System Expansion Output Modules
with 8 outputs per slot, so we add
248
outputs.
6.
Add any other Output types that you require. For example, Fiber Outputs.
In this example, we add
40 Outputs
starting at slot
31
, to correspond to 5 Fiber Output Modules with 8 outputs each.
7.
If you have a Multiviewer in the system, define the
Multiviewer Outputs
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 40
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
In this example, we have
SX PRO multiviewers
in slots
37
through
64
,
16
outputs per slot, so a total of
448
Destinations.
8.
This completes adding of
Sources
and
Destinations
. It is vital to click
Save
in order to commit these changes into the database.
9.
Close the Navigator sub-window that the Database Editor is running in by clicking the
X
in the corner to close the sub-window.
Note:
Do not click the
Close
button within the Navigator window; ensure you click the X in the corner.
10.
Re-Open
Navigator DBEditor
to
synchronize
and check that the synchronization has been successful.
11.
Click
Publish
in the
DBEditor
window. This will create the files required by any legacy elements
(including the Magellan control panels) and transfer those files out to those devices.
Other Routing System Considerations
Tielines
Tielines allow sources/destinations from one frame (the upstream connection) to be available to another frame or frames. Tielines help you expand the size of your system, make resources available to several users at the same time, or restrict remote user access to available sources.
See the
Magellan CCS Navigator™
user manual for information on using tielines and tieline monitoring.
In the
Tieline Monitoring
application (external to but installed with Magellan CCS Navigator), a new column
Reserved Destination
indicates the destination that the tieline is reserved for. You may edit this column by choosing the destination to be reserved. When an upstream source is requested by the reserved destination, it will always use this tieline and no other destinations will utilize this tieline. It will remain clear until required.
Note: the Reserved Tieline feature is only supported by SDNO Controller version 1.3 or higher.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 41
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
In the Magellan CCS Navigator™ user manual, follow the steps outlined for adding tielines to a routing system (See Managing Enhanced Tielines section). When creating a routing system and its corresponding logical database, keep in mind that the tieline routing system must contain at least one
SDNO Controller to serve as the tieline controller.
Note: In a system configured with tielines, the SDNO Controller scans any connections that utilize tielines and reports the ultimate source for a destination. In a multiframe configuration, a source may be
selected that is a tieline from a further upstream frame. The source displayed will be the source of the upstream tieline. Normally, tieline sources should not be made available to the configured control panels for routing, and this situation would not occur. However, since some panels can be configured with all sources and destinations for troubleshooting or other purposes it is worth noting this behavior.
Also see Connecting 2 Independent IP3 Systems with Tielines (on page 222)
Valid Characters in Source, Destination, Level, and Frame
Names
The following characters are allowed in source, destination, and frame names.
Table 1: Valid Characters in Source/Destination/Level/Frame Names
Character Description
A-Z Uppercase Alphabetic a-z
0-9
@ * - # ^ %
/
Lowercase Alphabetic
Numeric
A few specific punctuation marks
Forward slash (but NOT "\" backslash)
( )
" "
Regular parenthesis (but NOT {}, [], or <>)
Blank Spaces ARE allowed in source and destination names, including leading and trailing blank spaces.
[
#
,,
=
Invalid Characters in Source, Destination, Alias, Long Name,
Description, Level, and Frame Names
]
$,
;
+
\\
,
:
~
{
|
&
}
?
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 42
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Creating a Routing System
Other Restrictions
The
Frame Name
(Hardware Foundry) can be a maximum of 50 characters
The
Alias
(SDNO Database Editor) can be can be a maximum of 30 characters
The
Description
(SDNO Database Editor) can be can be a maximum of 90 characters
The
Long Name
(SDNO Database Editor) can be a maximum of 30 characters
The
Name Prefix
(SDNO Database Editor) can be a maximum of 8 or 16 characters
The length of the Name Prefix is 8 characters but can be increased to 16 if you go Options in
Navigator DBEditor and enable 16 character names.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 43
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Navigation
Navigation
SDNO Controller System Interface
Once you log into the SDNO Controller system (by opening a web browser and entering the (external) IP
Address of the SDNO Controller), the home page displays a dashboard from where you can configure, view, and monitor different elements of your system.
Key Label
1 System List View (on page
2 System Faults View (on page
3 Controller in the System (on
4 Frames in the System (on
5 Go to Frame links
6 Power Supply Status section
See Power Supply Status
7 Fan Status section
See Right Pane Displays (on
Description
Physical view of the overall system (Default view)
An overview of components/modules with faults and links to open, disable, or acknowledge faults
The configured Controller with snapshot information
A list of configured Frames in the system along with IP addresses, firmware versions, resource card information, and fault information.
Buttons that link to devices. Available for each added Frame.
Visible on clicking a frame.
For 28 RU: Power Supply Status by Zones 1-4 for top, bottom, and external (redundant) power supplies.
For 15 RU: Power Supply Status by Zones 1-2 for top/bottom and external (redundant) power supplies.
For 28 RU: Fan supply status categorized by location (front top, front bottom, rear).
For 15 RU: Fan supply status categorized by location (front, back).
Overview information listing total number of major/minor system faults.
8 System Faults.
See System Faults View (on
9 Configure System
See Configuration
Dashboard
10 Fault Log
See Logging Server (on page
11 Help
Links to configure the system and perform functions related to
Hardware and Firmware Management, Controller Settings, and User
Accounts.
Link to the Fault Log that opens in a new window.
Link to the User Manual
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 44
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
System List View
Navigation
The List view is the default view of the system. A snapshot of all configured frames and the SDNO
Controller is displayed.
Figure 4: SDNO System Dashboard (with a 28 RU Frame selected)
Figure 5: SDNO System Dashboard (with a 15 RU Frame selected)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 45
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Right Pane Displays
Navigation
On selecting a Frame, the right pane in the List View differs depending on whether you have a SDNO
Controller 28 RU frame, SDNO Controller 15 RU, Platinum VX frame, legacy router frame, or third party frame selected.
Platinum VX frames
15/28 RU SDNO Controller frames
The right pane displays IP Addresses, Power Supply Status, and Chassis fan status.
The right pane displays IP Addresses, Power Supply Status (4 zones for 28 RU, 2 zones for 15 RU), and Chassis fan status (Front Top, Front Bottom, Back for 28 RU and Front, Back for 15 RU). In addition, for detailed fan status reported, see
Front Fans Status in the Web UI (on page 48) and Rear Fans Status in the Web UI
The right pane displays only the IP Addresses.
Third Party/Legacy router frames
Figure 6: Platinum VX 8 RU frame
Figure 7: Platinum IP3 28
RU frame
Figure 8: Platinum IP3 15
RU Frame
Figure 9: Third party frame
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 46
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Power Supply Status Indicators
Navigation
Power Status Indicators for Platinum IP3 15RU/28RU Frames
When you select a frame in the main SDNO Controller Dashboard, Frame Power Supply status is displayed on the right. Status is displayed for each individual power supply in the frame as well as by power zone. There are 2 power zones for a 15 RU frame, and each can contain up to 4 power supplies (2 internal, 2 external). There are 4 power zones for a 28 RU frame, each with up to 4 power supplies (2 internal, 2 external).
Figure 10: Power Supply Status for a 28 RU frame Figure 11: Power Supply status for a 15 RU frame
Individual power supplies show as either green (healthy), red (alarmed), or gray
(not present).
POWER ZONE HEADERS
Power Zones headers display a color as well, indicating the overall power status of a frame:
If the
Zone
header is
green
, this indicates that at least 2 healthy power supplies are available, one of which is redundant and can take over if the other fails
If the
Zone
header is
amber
, this indicates that:
Only one power supply is present in the zone, there is no redundant supply to take over if the main one fails
Two (green/healthy) power supplies are present in the zone but they are still not enough to supply the power needs of the entire frame
(depending on how loaded the frame is) if one of the power supplies fails. If you see both power supplies in a zone showing as green, but the zone header showing amber, you should review the overall power situation and add another power supply to support the frame load
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 47
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Navigation
Platinum VX frames
Platinum VX frames just display status for individual power supplies - left and right for 4/8 RU frames and PS1 and PS1 for 1/2 RU frames.
Front Fans Status in the Web UI
The Controller Web UI reports
Front Fans
status in the
PX-FRONT-FAN
module, accessible by going to the List of Modules > Control Cards and clicking
Open Module
against
PX-FRONT-FAN
.
Figure 12: Front Fan Status for a 15 RU Frame
Status is displayed for all 6 front fans; you can view Fan Speed and Fan Failure status.
Rear Fans Status in the Web UI
The Controller Web UI reports
Rear Fans
status in the
PX-ALARM-DATA
module, accessible by going to the List of Modules > Control Cards and clicking
Open Module
against
PX-ALARM-DATA
.
A 28 RU frame displays status for 7 of its rear fans. A 15 RU frame displays status for its 4 rear fans, and
Fans 5/6/7 will show as N/A. You can see individual fan speed, as well as whether any of the fans have failed.
Figure 13: Rear Fan Status for a 15 RU Frame
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 48
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Frames in the System
Navigation
Frames/Modules
In the snapshot of Controllers/Frames displayed on the main navigation page, frame component status is indicated by the button color:
Table 2: Frames in the SDNO Controller System
Button Color Description
Primary/Secondary Green indicates active; Gray indicates inactive; Red indicates Alarmed
Power Supply Green indicates active; Gray indicates inactive; Red indicates Alarmed
Fan Status Green indicates active; Gray indicates inactive; Red indicates Alarmed
Select a Frame in the
Frame
section by clicking it; then click
Go to Frame
to have its details and
components displayed. See Frame and Module Parameters (on page 118).
Frame Parameters
See Frame Parameters (on page 122)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 49
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Modules in a Frame
Modules are displayed grouped by Category -
Input
,
Output
,
Crosspoint
, or
Control
Navigation
Figure 14: Modules Categories (collapsed) in the SDNO Controller Frame View
Note:
Only modules that are physically present and responsive in the system are displayed; modules that become unavailable are automatically filtered out of the list. Modules that have been configured in the past but are not present or not currently responsive are also not displayed.
Figure 15: Expanded View of Modules
The following details are displayed per component:
Name
: The name of the card. For example, PX-HSR9C-IBG
Slot
: The slot the card resides in
Category
: The type of card - Input, Output, Crosspoint, Control
Version
: The firmware version running on the card
Product ID
: The ID for the module
Alarm Status
: Red (major), Yellow (minor), Blank (healthy)
Open Module
: Click to go to a specific card/module and view details.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 50
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Module Details
Navigation
When you click the
Open Module
button against a module in the Frame View, Module details are displayed in a window superimposed over the previous frame window. The Module window displays ALL of the modules of the same type as the one that you selected. The following details are displayed:
Figure 16: Module Details
1 Modules List The first column displays the name of the selected module
(and the slot it is in), and lists other modules of the same type in the frame, if present. You can access details of other similar modules by clicking on them in the list. When you select a module in this list, information on the frame it belongs to, the slot, version, and serial number is dynamically updated in the header at the top, and parameters are displayed on the right.
2 Module
Parameters
Displays parameter categories/menus and individual parameters for the selected module. Parameter options can be changed using the GUI.
See Parametric Control.
3 Module Faults Displays any existing faults (and related details) for the
selected module. See Module Faults (on page 52)
4 Faults Overview The number of major and minor faults for the module are displayed at the top.
5 Close Button You can close the Module window at any time by clicking the
Close
button at the top right hand corner of the screen.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 51
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Module Faults
Module faults can be viewed by doing the following:
1.
Go to a frame by clicking the
Go to Frame
button on the main navigation page
2.
Click the
Open Module
button against a Module
3.
Click the
Faults
button to open the module specific Faults tab
Module faults are displayed with the following details:
Navigation
Figure 17: Module Faults
ID
: The Fault ID
Fault Name:
The Fault Name, for example,
Output Signal Presence
Error Level:
Major or Minor
Enable/Disable
: Whether the fault is active or not
Priority
: The priority level of the fault (1-10)
Ack
: Whether the fault has been acknowledged
Active
: Whether the fault is active
Note:
Changes to Alarm Acknowledgments are not saved if the Resource Module is rebooted. For example, if you go to the faults for a specific Module (by clicking the Open Module button against a
Module in the list of Modules, and then going the Faults tab for that module) change a setting, and select Acknowledge, if the Resource Card (PX-RES) is rebooted, the Alarm Acknowledgment state is not saved.
Filtering Module Faults
Use the
Sort All by Active
or
Show All
options to filter the fault display.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 52
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Editing Module Fault Properties
Click on any of the faults to have editable details displayed to the right. You can choose to enable/disable the fault, change priority, trigger value, clear value, and acknowledge.
Navigation
Figure 18: Fault Properties
Module Fault Descriptions
The following table lists possible module faults and descriptions:
Table 3: Module Faults
Data
Signal Presence
Lock Detect
Description
Loss of Signal in an Input Module
Loss of Signal in an Output Module
Failsafe Mode
Power Failure
Module is in Failsafe Mode
Module does not have proper power supply
Firmware Upgrade Required Module firmware upgrade required
Back Module Missing Cannot detect the back module
Incorrect Back Module Mismatch with detected back module
Over Temperature Threshold Module has a reached a critical temperature threshold
Unsupported Module Module not supported with the current Resource
Module (PX-RES) firmware. Perform Module upgrade.
Module Parameters
Refer to the
IP3 Frame and Modules Installation and Operation Manual
for individual modules supported in an IP3 Frame along with parameter details.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 53
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Controller in the System
Navigation
If you click on a
Controller
in the main dashboard, the right pane displays
ENET Status
(status for each of
The following details are displayed for a Controller in the system:
Figure 19: SDNO Controller in the System
Name
: The Controller Name, which shows as
SDNO Controller
ID
: The Controller ID
IP Address
: The Controller IP Address
Status
: The status of the Controller
Faults
: The number of Major/Minor faults
Primary/Secondary
: A highlight around the Primary/Secondary buttons indicates the currently active Controller
Redundancy Status
: Indicates if Redundancy has been enabled
Data Synced Status
: Indicates data is synchronized
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 54
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Navigation
Clicking the
Open Controller
link against a Controller in the system takes you to the SDNO Controller
Settings page (
Configure System > Manage SDNO Controller Settings
), where you can define the
Controller XY ID, the Server IP and Network and Redundancy Settings. See Manage SDNO Controller
System Faults View
Faults View is a filtered view of only those modules in the system that currently have faults.
This is a high level view of all modules in the Frame that currently have faults, as opposed to the Module specific fault view that is displayed when you choose to see faults for a specific module (Module Faults
You can opt to view alarms in the following ways:
No Grouping
: A flat list of all active alarms
(Major, minor, informational)
Group by Device
: List of active alarms grouped by device
(Module)
Grouping by
Device
creates groups per module listing all faults for that module. The header of the group indicates the module name, slot number, and the total number of major/minor faults for that module.
Figure 20: Faults Grouped by Device
Individual items are listed with details on:
Parent
- The Frame (name) that the Module is in
Device
- The name of the Module, for example, PX-HSR8C2D-OBG
Fault Name
- The type of Fault, for example, Input Signal Presence
Acknowledgment
- Whether the Fault has been acknowledged
Time Issued
- The Time the Fault occurred. See Fault Time (on page 56).
Data
- Information on the fault, for example, Lock Detect
Error Level
- Whether major, minor, etc.
Count
- The Fault count
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 55
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
There are also links to:
Disable the Fault
Acknowledge the Fault
Open the Module
Navigation
Faults can be selected by clicking on them individually, or clicking the
Select All
button at the top to select all faults.
You can group Disable/Acknowledge Faults by either selecting all, or multiple selecting using the CRTL or
SHIFT key and then clicking
Disable Faults
or
Acknowledge Faults
beside
Multi-Row Edit
at the top.
Note: Once you disable a fault, to re-enable it, you will need to go to that Module’s Faults view and enable the fault from there.
Fault Time
The time at which a fault occurred is not displayed in the Faults View but is available in the Fault Log of
the Logging Server (on page 292). Use the link to the
Fault Log
in the toolbar at the top to go directly to it.
Note:
The Fault time is shown for faults triggered when the UI is open.
To correlate a specific fault from the Faults View with the Logging Server:
1.
First, look at the details of the specific Fault in the Faults View and note the slot number and IP address of the frame that contains the module with the fault.
2.
Go to the Logging component -
http://<Controller IP>:8002
3.
Expand IP3 Controller, select
Fault Log
, and click the
History
button.
4.
Click the
Examine Logs
button in the Examiner that is displayed.
5.
In the list that is displayed, look for the Fault message.
To help co-relate with the specific fault you’re looking for, look at the following details in the Message section of the Fault:
Parent<IP>
- The IP of the Frame that contains the module
Location
- The slot your module is in
Fault Name
- The fault name that was displayed
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 56
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Setting up and Configuring Switches
Setting up and Configuring Switches
This section applies if you have switches in your SDNO System or if you're using the SDNO Controller to manage your switches and through them, other equipment downstream.
Imagine Communications' SDNO System currently supports the use of specific Arista, Brocade, and Cisco switches. Please contact Imagine Communications for specific models and details.
Arista Setup
Configure a Management IP Address
1.
Connect one end of a serial port cable to the serial port on the switch and the other end to an RS-
232 serial port on a workstation. Use the following settings:
9600 baud
8 data bits
no parity bits
1 stop bit
no flow control
2.
The default username is "admin" and the default password is "password". To set or change the password for a user, enter the following commands:
enable
configure
username <user name> secret <password>
For example: username admin secret password
3.
Enter the following commands to set the management IP:
enable
configure
interface Management 1
ip address <ip address>/<mask>
For example: ip address 172.10.95.99/16
4.
If necessary, configure a route to the default gateway. From the top-level (use "exit" to move up a level if necessary), enter the following commands:
enable
configure
ip route 0.0.0.0/0 <default gateway)
For example: ip route 0.0.0.0/0 172.10.10.1
5.
Enable Telnet:
enable
configure
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 57
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
management telnet
no shutdown
Setting up and Configuring Switches
6.
Save the running configuration to the startup configuration. From the top-level, enter the following command:
copy running-config startup-config
7.
It should now be possible to telnet into the switch on port 23 using the management IP configured above.
Enable the eAPI over HTTP
1.
From the top level, enter the following commands:
enable
configure
management api http-commands
no protocol https
protocol http
no shutdown
2.
Test that eAPI over HTTP is enabled by using a web browser and entering > in the address bar. The username and password will be the same as that used to log in through telnet.
For example: http://172.10.95.99/
Enable IP Routing
1.
From the top level, enter the following commands:
enable
configure
ip routing
Enable Multicast Routing
1.
From the top level, enter the following commands:
enable
configure
ip multicast-routing
Enable IGMP Snooping
1.
From the top level, enter the following commands:
enable
configure
ip igmp snooping
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 58
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Setting up and Configuring Switches
Configure Ports
1.
From the top level, enter the following commands to configure the ports:
enable
configure
interface <port id>
For example: interface Ethernet1
Note: The <port id> is what should be entered in Flat Matrix under either "Port" if this is the primary path or "Port (2nd)" if this is the secondary path for managed sources/destinations.
switchport
switchport mode access
switchport access vlan <vlan id>
For example: switchport access vlan 200
2.
Repeat for all ports. To configure a range of ports at the same time, use interface Ethernet<startId>-
<endId>.
For example, to configure ports 1 through 20, use interface Ethernet1-20
.
3.
Save the running configuration to the startup configuration. From the top-level, enter the following command:
copy running-config startup-config
Configure VLANs
1.
From the top level, enter the following commands to create SVI interfaces for the VLAN:
enable
configure
interface Vlan <Vlan Identifier>
The Vlan identifier should match the Vlan identifier specified earlier. For example: interface
Vlan200
ip address <ip address>/<mask>
For example: ip address 192.168.95.1/24
This value should match the "Primary Gateway" (under IP WAN -> General) on the UCIP if this is the primary VLAN or the "Secondary Gateway" on the Selenio UCIP Module if this is the secondary VLAN.
no shutdown
2.
Enable IGMP snooping querier on the VLAN. This is necessary as without a querier, the Arista switch will flood multicast traffic to the VLAN. From the top-level, enter the following commands:
enable
configure
ip igmp snooping vlan <Vlan Identifier> querier
For example: ip igmp snooping vlan 200 querier
ip igmp snooping vlan <Vlan Identifier> querier <IP Address>
The IP Address should match the IP Address configured on the SVI in Step 1 of the VLAN configuration.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 59
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Setting up and Configuring Switches
For example: ip igmp snooping vlan 200 querier 192.168.95.1
3.
To confirm that traffic is not being flooded to the VLAN, use the following command:
show ip igmp snooping vlan <Vlan Identifer>
For example: show ip igmp snooping vlan 200
4.
Repeat these steps for all the VLANs.
5.
Save the running configuration to the startup configuration. From the top-level, enter the following command:
copy running-config startup-config
Brocade Setup
Configure a Management IP Address
1.
Connect a serial port cable to the serial port on the switch and to an RS-232 serial port on a workstation. Use the following settings:
9600 bits per second
8 data bits
no parity
1 stop bit
no flow control
2.
The default username is “admin” and the default password is “password”.
3.
Enter the following commands to set the management IP:
configure
interface Management 1/0
ip address <ip address>/<mask>
For example: ip address 172.10.95.99/16
4.
If necessary, configure a route to the default gateway. From the top-level (use “exit” to move up a level if necessary), enter the following commands:
configure
rbridge-id 1
ip route 0.0.0.0/0 <default gateway)
For example: ip route 0.0.0.0/0 172.10.10.1
5.
Save the running configuration to the startup configuration. From the top-level, enter the following command:
copy running-config startup-config
6.
It should now be possible to telnet into the switch on port 23 using the management IP configured above.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 60
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Enable IGMP Snooping
1.
From the top level, enter the following commands:
configure
ip igmp snooping
Setting up and Configuring Switches
Configure VLANs
1.
From the top level, enter the following commands to create a VLAN:
configure
interface Vlan <Vlan identifier>
• For example: interface Vlan 200
2.
From the top level, enter the following commands to crate Ve interfaces for the VLAN:
configure
rbridge-id 1
interface Ve <Vlan Identifier>
The Vlan identifier should match the Vlan identifier specified in Step 1 above. For example: interface Ve 200
ip address <ip address>/<mask>
For example:
ip address 192.168.95.1/24
This value should match the “Primary Gateway” (under IP WAN -> General) on the UCIP if this is the primary VLAN or the “Secondary Gateway” on the UCIP if this is the secondary VLAN.
no shutdown
3.
Repeat steps 1 and 2 above for all VLANs.
4.
Save the running configuration to the startup configuration. From the top-level, enter the following command: copy running-config startup-config
Configure Ports
1.
From the top level, enter the following commands to configure the ports:
configure
interface TenGigabitEthernet <port id>
For example: interface TenGigabitEthernet 1/0/1
Note: The <port id> is what should be entered in Flat Matrix under either “Port” if this is the primary path or “Port (2nd)” if this is the secondary path for managed sources/destinations.
switchport
switchport mode access
switchport access vlan <vlan id>
For example: switchport access vlan 200
2.
Repeat Step 1 for all ports.
3.
Save the running configuration to the startup configuration. From the top-level, enter the following command:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 61
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual copy running-config startup-config
Setting up and Configuring Switches
Cisco Setup
Configure a Management IP Address (Cisco)
1.
Connect a serial port cable to the serial port on the switch and to an RS-232 serial port on a workstation. Use the following settings:
9600 baud
8 data bits
no parity bits
1 stop bit
no flow control
2.
Enter the following commands to set the management IP:
enable
configure
interface mgmt0
ip address <ip address>/<mask>
For example: ip address 172.10.95.99/16
vrf member management
Enable VRF Context Management
1.
If necessary, configure a route to the default gateway. From the top-level (use "exit" to move up a level if necessary), enter the following commands:
enable
configure
vrf context management
ip route 0.0.0.0/0 <default gateway)
For example: ip route 0.0.0.0/0 172.10.10.1
Enable Telnet
1.
From the top level, enter the following commands:
enable
configure
feature telnet
2.
It should now be possible to telnet into the switch on port 23 using the management IP configured
3.
Save the running configuration to the startup configuration.
4.
From the top-level, enter the following command: copy running-config startup-config
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 62
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Enable interface-vlan
1.
From the top level, enter the following commands:
enable
configure
feature interface-vlan
Setting up and Configuring Switches
Enable IGMP Snooping (Cisco)
1.
From the top level, enter the following commands:
enable
configure
ip igmp snooping
Configure Ports (Cisco)
1.
From the top level, enter the following commands to configure the ports:
enable
configure
interface <port id>
For example:
interface Ethernet1/1
Note: The <port id> should be entered in the SDNO Database Editor under either "Port" (if this is the primary path) or "Port (2nd)" if this is the secondary path for managed sources/destinations.
switchport
switchport mode access
switchport access vlan <vlan id>
For example: switchport access vlan 200
2.
Repeat Step 1 for all ports.
To configure a range of ports at the same time: use interface Ethernet<startId>-<endId>
For example, to configure ports 1 through 20, use
interface Ethernet1-20
3.
Save the running configuration to the startup configuration. From the top-level, enter the following command: copy running-config startup-config
Configure VLANs (Cisco)
1.
From the top level, enter the following commands to create SVI interfaces for the VLAN:
enable
configure
interface Vlan<Vlan Identifier>
The Vlan identifier should match the Vlan identifier specified in Step 1 above. For example: interface Vlan200
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 63
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
ip address <ip address>/<mask>
For example: ip address 192.168.95.1/24
Setting up and Configuring Switches
This value should match the
Primary Gateway
(under IP WAN -> General) on the UCIP if this is the primary VLAN or the
Secondary Gateway
on the UCIP if this is the secondary VLAN.
no shutdown
2.
Enable IGMP snooping querier on the VLAN. This is necessary as without a querier, the Cisco switch will flood multicast traffic to the VLAN. From the top-level, enter the following commands:
enable
configure
vlan configuration <Vlan Identifier>
ip igmp snooping
ip igmp snooping querier <IP Address>
The IP Address should match the IP Address configured on the SVI in Step 1 of the VLAN configuration.
For example: ip igmp snooping querier 192.168.95.1
3.
Repeat steps 1, 2 and 3 above for all VLANs.
4.
Save the running configuration to the startup configuration.
5.
From the top-level, enter the following command: copy running-config startup-config
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 64
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Selenio MCP™ Devices in your SDNO System
Selenio MCP™ Devices in your SDNO
System
If you have Selenio MCP™ Devices in your SDNO System:
1.
Configure the Selenio MCP modules independently via the Selenio Controller UI. Specific Selenio
MCP Module settings that the SDNO Controller requires are covered here Selenio MCP Module
Note: SDNO only supports
multicast
routing.
2.
Add the Selenio MCP™ Modules to your SDNO System. See Adding Selenio (JPEG
2000/UCIP/ENC/DEC/MDX) MCP Modules as Devices (on page 86)
3.
Set up your Sources and Destinations. See Sources/Destinations from IPVR Devices (on page 144)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 65
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual EPIC™ MV Devices in your SDNO System
EPIC™ MV Devices in your SDNO
System
If you have EPIC™ MV IP Multiviewer Devices in your SDNO System:
Ensure you configure the EPIC™ MV device independently, following the instructions in the EPIC MV documentation
Add the EPIC™ MV to your SDNO System. See Adding an EPIC™ MV IP Multiviewer (on page 88)
Set up your Destinations. See Sources/Destinations from IPVR Devices (on page 144)
Note: Only Destinations are supported for the EPIC MV in SDNO.
The EPIC™ MV multiviewer supports up to 4 PCIE UCIP cards in physical slots 1, 2, 3, and 6. SDNO references these slightly differently:
2
3
Slots in EPIC MV
1
6
Mapping of Slots in SDNO
1
2
3
4
Each EPIC-MV-UCIP card supports six channels of 3G (using dual SFPs) or twelve channels of 1.5 Gb/s over IP. When completely filled, the maximum capacity in a single EPIC™ MV is either twenty-four (24)
3G or forty-eight (48) 1.5G signals.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 66
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
PX-UCIP (Uncompressed Video-Over-
IP) Modules in your SDNO System
The Platinum™ IP3 PX-UCIP (Uncompressed Video-Over-IP) module serves as a Media Gateway between the IP3 router and IP networks, enabling a hybrid infrastructure. The PX-UCIP module is a multichannel
SDI-to-IP encapsulator and IP-to-SDI de-encapsulator supporting real-time transport of multiple
3G\HD\SD-SDI uncompressed video channels over an IP network.
If you have PX-UCIP modules in your SDNO System:
1.
Ensure the IP3 frame that contains your PX-UCIP Module is added to your SDNO System. See Adding
a Platinum Router (on page 77)
2.
Configure the PX-UCIP module independently by accessing it via the SDNO Controller UI and then
launching the PX-UCIP specific UI. See PX-UCIP Configuration (on page 180).
3.
Set up your Sources and Destinations in the SDNO Database Editor. See PX-UCIP Modes and
PX-UCIP Modes and Database Setup
Your PX-UCIP Module resides in an IP3 Frame in your SDNO System and this module can function in 2 ways simultaneously:
As an SDI to IP Encapsulator
In this case, your PX-UCIP input module and an SDI feeder module (PX-HSR1D2D-OBG) reside in the same frame. The Feeder Module's Densishield OUT 1 Port needs to be physically connected to the
PX-UCIP's DensiShield IN port. The feeder module transmits SDI signals to the PX-UCIP Module via the DensiShield cable. The PX-UCIP encapsulates the SDI signals from the DensiShield input into
SMPTE-2022-6 packets.
As an IP to SDI De-encapsulator
In this case, the PX-UCIP receives SMPTE-2022-6 packets directly from an
IPVR
device or data switch in the SDNO System. The PX-UCIP module has two Links, Link A and Link B on the module (referred to as Port 1 and Port 2 on the SDNO Controller; see figures below). Each Link consists of a Primary and Secondary 10 Gbps Ethernet interface, via which, it can receive SMPTE-2022-6 packets. A bidirectional connection exists between the data switch and the Ethernet ports on the PX-UCIP module. These SMPTE-2022-6 packets are then de-encapsulated to re-generate the SDI signals and made available to the Platinum IP3 Video Crosspoint and DensiShield Output port.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 67
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
Figure 21: Mapping of "A" menus in the PX-UCIP UI to Port 1 in the SDNO Controller Database Editor
Figure 22: Mapping of "B" menus in the PX-UCIP UI to Port 2 in the SDNO Controller Database Editor
You can use your PX-UCIP module as:
An IP to SDI converter
An SDI to IP converter
Both, at the same time (which would utilize 8 sources and 8 destinations).
Once you have your PX-UCIP module physically setup in the IP3 frame, you need to configure sources
(see "SDI to IP" on page 70) sections illustrate sample setup in the SDNO Database Editor.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 68
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
PX-UCIP and Tielines
In order or route the sources and destinations from IPVR to SDI and vice versa
in a single step route
, you need to define Tielines in the SDNO System. Tieline definition is done via Magellan CCS Navigator, in the
DB Editor.
Launch
Navigator
, and then launch the
DB Editor
. Go to the
Sources
tab. If you do not see the
Tielines
column, click the
Show Tielines
Button. Select a Source and then select the Destination in the Tielines
drop down (see the reference tables in PX-UCIP Modes and Database Setup (on page 67)).
Note: Use Tielines cautiously. When using tielines, SDI to Tx is mapped by the Tieline Controller. Without tielines, you can freely map based on your route.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 69
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
SDI to IP
This table illustrates a sample setup when your PX-UCIP module is being used in SDI to IP mode. The PX-
UCIP can encapsulate 4 SDI per Link:
FROM
SDI 1-4
SDI 5-8
TO
LINK A TX 1-4
LINK B TX 1-4
SDI DESTINATIONS IN THE DATABASE IP SOURCES (TX) IN THE DATABASE
SDI
Output
SDI
SDI
SDI
SDI
SDI
SDI
SDI
SDI
Frame Location
Type
Slot Port Channel
IP3
IP3
OUT
OUT
Slot 1 Port 1 Video 1
Slot 1 Port 2 Video 1
IP3
IP3
IP3
OUT
OUT
OUT
Slot 1 Port 3 Video 1
Slot 1 Port 4 Video 1
Slot 1 Port 5 Video 1
IP3
IP3
IP3
OUT
OUT
OUT
Slot 1 Port 6 Video 1
Slot 1 Port 7 Video 1
Slot 1 Port 8 Video 1
IP
Receiver
Frame Location
Type
Slot Port Channel
Tx 1A
Tx 2A
Tx 3A
Tx 4A
Tx 1B
Tx 2B
Tx 3B
Tx 4B
IPVR
IPVR
IPVR
IPVR
IPVR
IPVR
IN
IN
IN
IN
IN
IPVR IN
IPVR IN
IN
Slot 1 Port 1 Video 1
Slot 1 Port 1 Video 2
Slot 1 Port 1 Video 3
Slot 1 Port 1 Video 4
Slot 1 Port 2 Video 1
Slot 1 Port 2 Video 2
Slot 1 Port 2 Video 3
Slot 1 Port 2 Video 4
Link A
Link B
Note: These SDIs are received via a DensiShield cable, that is fed from the feeder module DensiShield output, therefore, they are located in "Destinations". These SDIs are
hardwired
to PX-UCIP
LINK A TX 1-4
and
LINK B TX1-4
input for SDI to IP encapsulation.
Note: Tielines can optionally be built between the Feeder and the the IPVR Tx.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 70
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
1.
In the
SDNO Database Editor
,
Sources
tab, create 8 sources for your IP (IPVR) input.
2.
Go to the
Destinations
tab and create 8 destinations for your SDI Output (since these SDIs are actually fed from the DensiShield feeder module output via a DensiShield cable).
Also see Sources/Destinations from IPVR Devices (on page 144).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 71
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
IP to SDI
This table illustrates a sample setup when your PX-UCIP module is being used in IP to SDI mode. The PX-
UCIP can de-encapsulate IP to re-generate SDI signals:
FROM
LINK A Rx 1-4
LINK B Rx 1-4
TO
SDI 1-4
SDI 5-8
IP DESTINATIONS (RX) IN THE DATABASE
IP
Receiver
Frame Location
Type
Slot Port Channel
Link A
Rx 1A
Rx 2A
Rx 3A
Rx 4A
Link B
Rx 1B
IPVR
IPVR
IPVR
IPVR
IPVR
IN
IN
IN
IN
IN
Slot 1 Port 1 Video 1
Slot 1 Port 1 Video 2
Slot 1 Port 1 Video 3
Slot 1 Port 1 Video 4
Slot 1 Port 2 Video 1
Rx 2B
Rx 3B
Rx 4B
IPVR IN
IPVR IN
IPVR IN
Slot 1 Port 2 Video 2
Slot 1 Port 2 Video 3
Slot 1 Port 2 Video 4
SDI SOURCES IN THE DATABASE
SDI Input Frame Location
Type
Slot Port Channel
SDI Input 1 IP3
SDI Input 2 IP3
SDI Input 3 IP3
SDI Input 4 IP3
SDI Input 5 IP3
IN
IN
IN
IN
IN
Slot 1 Port 1 Video 1
Slot 1 Port 2 Video 1
Slot 1 Port 3 Video 1
Slot 1 Port 4 Video 1
Slot 1 Port 5 Video 1
SDI Input 6 IP3
SDI Input 7 IP3
SDI Input 8 IP3
IN
IN
IN
Slot 1 Port 6 Video 1
Slot 1 Port 7 Video 1
Slot 1 Port 8 Video 1
Note:
8 SDI sources (from the IP3 wideband video crosspoint perspective) are
hardwired
from the PX-
UCIP
LINK A RX 1-4
and
LINK B Rx 1-4
to
SDI 1-8
.
1.
In the
SDNO Database Editor
,
Sources
tab, set up 8 Sources for your SDI Inputs
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 72
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual PX-UCIP (Uncompressed Video-Over-IP) Modules in your SDNO System
2.
Go to the
Destinations
tab and set up 8 (IPVR) Destinations for your IPVR Output
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 73
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
System Configuration
Click the
Configure System
link in the toolbar at the top to start configuring your SDNO Controller system.
Figure 23: SDNO Controller Toolbar
You can do the following via the System Configuration Dashboard:
Manage SDNO Controller Settings (on
Firmware Foundry (on page 108)
Add, Remove, or Modify Frames and Devices
Manage SDNO Controller Settings
Apply Firmware Upgrades to Devices and/or Manage
Firmware Repository
Manager User Accounts and Passwords
Figure 24: System Configuration Dashboard
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 74
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Hardware Foundry
System Configuration
Click the
Hardware Foundry
icon to define or modify your system hardware configuration.
You will see two links:
Routing Device (See Routing Device (on page 75 ))
Client Device (See Client Device (see "Client Device Router Database Access Control" on page 98))
Routing Device
The Routing Devices section lets you add/modify/delete routing devices in your system. It lists existing
Router devices and panels with information on
Vendor
, Frame
Name
, Frame
Type
, and
IP Address(es).
Routing Devices are grouped by Vendor (Imagine Communications or Grass Valley) and then by Frame.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 75
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
See:
System Configuration
Modifying a Device (on page 91)
Removing a Device (on page 91)
To return to the main System Configuration menu, click the System Configuration link or the back arrow icon next to it in the toolbar at the top.
Adding a Device
Click the
Add Devices
button to add a new frame to the system.
Note that you can currently add a maximum of 20 devices to the system. This includes frames, switches, third party devices, etc.
You can add:
Imagine Communications routers (default):
Platinum IP3 (15/28 RU)
Platinum with PX-RES
Platinum VX (1/2/4/8 RU)
Legacy routers (via X/Y)
Third party routers - currently, Grass Valley is supported.
Sony IP Live
Selenio MCP Devices (via a switch, using IPVR)
EPIC MV Multiviewer Devices (via a switch, using IPVR)
Important
: Every time you add or remove a device, you need to publish (via Navigator) for the changes to take effect in the routing system.
If a frame used in the database is removed and re-added using a different family, a message will be displayed indicating that. And the SDNO Database Editor will be in read-only mode (delete only) until the problem is resolved.
Figure 25: Database Editor - Frame/Family mismatch
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 76
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Adding a Platinum Router
System Configuration
Use this option to add Platinum IP3 15 RU and 28 RU frames, as well as Platinum frames that have a PX-
RES Resource module.
1.
Provide a
Name
for your device
Note:
The Name that you choose in this step will become part of the routing system database, and part of the physical location properties of every signal that terminates at this routing frame.
Carefully choose a name that is meaningful in your facility, which differentiates the frames within a multi-frame router in a way that will be unambiguous to the maintenance and operations staff. It is also visually helpful in the tools if the name is relatively short.
2.
Ensure
Platinum
is selected in the Family
drop down
list
3.
The
Protocol
by default is
IP3 PRC
4.
Enter the
IP Address
of the router device (IP Address 1) and secondary IP address (IP Address 2) if available
Note: Also see Changing Frame IP Addresses (on page 91 ).
5.
Click
Add
Note: If a Platinum PX-RES Resource Module is installed in a Platinum frame, it becomes part of the
SDNO Controller Control system, and the web based SDNO Controller UI is used for configuration, control, and monitoring of the entire system. To support this, the SDNO Controller version must be 1.3.3 or higher and the PX-RES version must be 1.5 or higher.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 77
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Once complete, you will see your frame and other details on the main page.
System Configuration
It can take up to 90 seconds for the SDNO Controller to pull in all of the details of the frame and display them for the first time.
Select the row containing the frame - if the power supply and fan indicators appear on the right in color, then you have successfully added the frame.
Click
Go to Frame
to check that all of the modules appear as expected within the frame
Adding a Platinum VX Router
Note: Platinum VX Routers can be controlled by the SDNO Controller if they are set to
System
mode (set this via
Manage Controller Settings
in the Platinum VX's
System Configuration
dashboard). When a
Platinum VX is in
Standalone
mode, you can only access it via its own web interface.
In
System
mode, your Platinum VX can be controlled by an SDNO Controller that's also controlling other devices such as Platinum IP3 15/28 RU, third party routers, and legacy routers. Once a Platinum VX system is in
System
mode, it cannot be accessed via the Platinum VX web interface. It will only be accessible if you switch to
Standalone
mode, but then the frame will not be controllable by the SDNO
Controller.
1.
Provide a
Name
for your device
2.
Ensure
Platinum VX
is selected in the Family
drop down
list.
3.
The
Protocol
by default is
PVX PRC
4.
Enter the
IP Address
of the router device (IP Address 1) and secondary IP address (IP Address 2) if available
Note: Also see Changing Frame IP Addresses (on page 91 ).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 78
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
5.
Click
Add
System Configuration
Adding a Third Party Router
1.
Provide a unique
Name
for the device
2.
Select
Grass Valley
in the
Vendor
drop down
3.
The
Protocol
by default is
SMS 7000
4.
Enter the
Port
number or leave the default
12345
5.
Enter the main
IP Address
of the router device in
IP Address 1
6.
Enter a secondary
IP Address,
if available, in
IP Address 2
7.
Click
Add
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 79
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Adding a Sony IP Live Manager device
System Configuration
1.
Click the
Add Devices
button to add a new frame to the system.
2.
Provide a unique
Name
for your IP Live System Manager device
3.
Select
Sony
in the
Vendor
drop down. The Protocol by default is External Router Gateway.
4.
Enter the
Port
number.
Ensure that this number matches what you provided when adding the SDNO Controller to the IP Live
System Manager
5.
Enter the main
IP Address
of the IP Live System Manager in
IP Address 1
6.
If you have a redundant IP Live System Manager, enter the secondary IP Address in
IP Address 2
7.
Click
Add
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 80
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Adding an X/Y Device
System Configuration
Use this option to add a legacy router (for example, Panacea, Edge, Integrator, etc.) that supports Telnet
X/Y.
Note: Devices added via X/Y will be available for control only and not configuration.
Adding X/Y Devices is a 2 step process:
1.
Add your router device
(for example, a Platinum router) as an X/Y Passthrough device
See Adding an X/Y device in the Hardware Foundry (on page 81)
2.
Import the Router's database separately into the Database Editor
See Importing the Database of a Device added via X/Y Passthrough (on page 83)
Adding an X/Y device in the Hardware Foundry
1.
From within
SDNO Routing System Configuration
>
Hardware Foundry > Routing Device
, click
Add
Devices
2.
Provide a
Name
for your device
3.
Ensure
Vendor
selection is set to Imagine Communications
4.
Select
XY Pass Through
from the Family selection
drop down
list (the
Protocol
by default is
X/Y)
5.
Enter the
IP Address
of the device
6.
Enter the
Telnet
username and password to access the device (default: leitch/leitchadmin)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 81
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
7.
Click
Add
at the bottom of the window
System Configuration
Once added, the
XY
device will show up on the dashboard, under
Pass-through and Third-Party Frames
and the IP Address will be displayed on the right.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 82
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Importing the Database of a Device added via X/Y Passthrough
System Configuration
Follow these steps to import the database of the router added as an X/Y Device:
Note: Before proceeding, ensure the added X/Y Device is online and Active.
1.
Create a Routing system in Navigator. Or, if one already exists, proceed to step 2.
2.
Poll using the IP Address of the SDNO Controller
3.
Once completed, you will see the "Imagine Communications X/Y" Device under the SDNO Routing
System
4.
Double-click the
SDNO Routing System
node under Routers folder to go to the SDNO Database
Editor
5.
In the "Selected View" drop down, select the X/Y Device (this will show using the frame Name provided when adding the router via X/Y Pass Through in the Hardware Foundry)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 83
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
6.
Click
Import > Import from Device
(or File) to import the router's database as part of the overall IP3 router database.
7.
Accept the Level Mappings or make changes and click OK
8.
This imports the sources and destinations from the Platinum Router's database. Click Save.
9.
Close the SDNO Database Editor Window and open the Routing System DB Editor (under the Control
Views folder). This is needed to merge and synchronize the SDNO routing database with the rest of the Routing System's database. Save and Publish.
Note: X/Y Pass Through added devices are intended for CONTROL purposes only from SDNO. You cannot make changes to Source/Destination Names, Indexes, etc., only editing of Long Names and Alias
Names are permitted. If database changes or updates of the X/Y Pass Through device are required, you must navigate to that device's database configuration and make the changes there. Once those changes are published/downloaded to the device, repeat steps 4-9 above to re-import the updated device's database into the overall SDNO router database again.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 84
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Adding a Switch (Arista/Brocade/Cisco) as a Device
System Configuration
External switches (such as Brocade, Arista, or Cisco) need to be added as
IPVR
Devices. IP Virtual Router
(IPVR) Devices added to the system are for all purposes just like any other IP3 frame device. To add a switch, follow these steps:
1.
Click
Add Devices
in the
Hardware Foundry
2.
Enter a unique
Name
for the IPVR device
3.
Select
Vendor
as
Imagine Communications
4.
Select
IPVR
from the
Family
drop down
5.
Under
Management
, select
IGMP-Plus
Note: Arista, Brocade, and Cisco are managed switches; all other switches are currently unmanaged.
Also see Managed/Unmanaged Sources and Destinations (on page 153 ).
6.
Select the appropriate
Protocol
based on the switch being used.
Select
NETCONF-Brocade
for a
Brocade
switch
Select
NETCONF-Cisco
for a
Cisco
switch
Select
JSON RPC-Arista
for an
Arista
switch
7.
In the
Primary IP
and
Secondary IP
fields, enter the management IP addresses of your
Brocade/Arista/Cisco switch.
Note: If you have only one switch, enter the SAME IP Address in both fields.
8.
Under
Data VLAN
, In the
Primary
and
Secondary Switch
fields, enter the VLAN IDs created during switch configuration
9.
Enter the
Username
and
Password
details to log into the switch via the management port (
admin
as username and
password
as password is the default if it has not been changed)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 85
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
10.
Click
Add
. This will create a new device in the system.
System Configuration
Note that an IPVR device will not show as active with a Go to Frame link in the main dashboard as an IP3 frame will.
Adding Selenio (JPEG 2000/UCIP/ENC/DEC/MDX) MCP Modules as Devices
Selenio MCP Modules - such as JPEG 2000/UCIP/ENC/DEC/MDX – are not directly added into Hardware foundry; the switch or switches that these modules connect to are added as IPVR devices. See
instructions for .Adding an Arista/Brocade/Cisco switch as as Device (see "Adding a Switch
(Arista/Brocade/Cisco) as a Device" on page 85)
Note: Create an
IPVR
device for each signal/video type. As an example, presume you have three Selenio
MCP Modules - Selenio JPEG2000, Selenio UCIP, and Selenio MDX , all on separate VLANs, but connected to the same switch. To separate out the traffic, create 3 IPVR devices - one for the Selenio JPEG2000, a second for the Selenio UCIP, and a third for the Selenio MDX - and use the same (primary and secondary) IP Address for all three (the address of the switch), but different primary/secondary VLAN
IDs for each one.
When creating the IPVR device:
Name
: Provide a unique
Name
for the device in the Name field
Vendor
: Set Vendor to Imagine Communications
Family
: Select IPVR from the drop-down
Management
: Select IGMP-Plus
Protocol:
Select from
JSON RPC-Arista, NETCONF-Brocade, NETCONF-Cisco
depending on your switch type
Management IP Address
: The primary and secondary IP address(es) that correspond to the
Management IP address of the switch
that the Selenio module is connected to.
Note that when creating an IPVR device for a Selenio MCP module, you do not enter the IP
Addresses of the Selenio MCP frame(s) or modules.
Data VLAN Primary/Secondary Switch
: It is recommended that you segregate the traffic from different Selenio MCP modules types, effectively different signals, onto separate VLANs to avoid any issues with handling or routing of signals. Once you do that, enter the relevant Primary and
Secondary VLAN IDs into the VLAN fields in the Frame Details dialog when creating the IPVR device for that traffic/signal type.
Authentication
: Enter the Username and Password for the system. Use a name that makes the IPVR device easy to identify, such as
IPVR_Arista_EPIC
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 86
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Switch Configuration: Enter the following here:
Set the
Architecture
of your switch, whether
Modular
or
Fixed
.
If
Modular
, enter the
Start Port
,
Start Slot
,
End Port
, and the
number of ports per slot
.
If Fixed, enter the
Start
and
End Port
.
Note that switch configuration settings here affects sources and destinations added via this switch. For example, if you define a switch with a specific port range, when adding sources/destinations the entered Port should be within that range. Of if you define a fixed Port, when adding sources/destinations, you need to add the Port number in the Switch section, but if you define a Modular Port, you have to enter the Port and Slot # in the Switch section. See
Add (on page 138) for details.
Here is an example of your SDNO Controller dashboard with 3 IPVR devices added for Selenio Modules.
Sources and Destinations from Selenio MCP Devices
Once your Selenio MCP modules have been independently configured and set up as IPVR devices, source/destination definition from the modules is done via the Database Foundry. The Database
Foundry is not directly accessible (or visible) from the SDNO Controller Web UI. You need to create a routing system in Magellan CCS Navigator, poll using the SDNO Controller IP Address, and then click IP3
Routing System under the Routers folder. This launches the SDNO Controller Web UI within Navigator
(on the right) and displays the Database Foundry.
Note: You need one or more device type definitions before using the Database Foundry to add sources/destinations.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 87
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
See Sources/Destinations from IPVR Devices (on page 144).
System Configuration
Adding an EPIC™ MV IP Multiviewer
EPIC™ MV multiviewer devices are not directly added into the Hardware Foundry; the switch or switches that these devices connect to are added as
IPVR
devices. See instructions for Adding a
Brocade/Arista switch as as Device (see "Adding a Switch (Arista/Brocade/Cisco) as a Device" on page
Create an IPVR device for your EPIC MV
OR
Use an existing IPVR Device (created for the same signal type, UCIP, in this case. So if you already have an IPVR device created for an existing Selenio UCIP module, you can use that one).
If creating a new IPVR device:
Name
: As with all IPVR devices, ensure you provide a unique
Name
for the device in the Name field
Vendor
: Set Vendor to Imagine Communications
Family
: Select IPVR from the drop-down
Management
: Select IGMP-Plus
Protocol:
Select from
JSON RPC-Arista, NETCONF-Brocade, NETCONF-Cisco
depending on your switch type
Management IP Address
: The primary and secondary IP address(es) that correspond to the
Management IP address of the switch
that the EPIC MV device is connected to.
Note that when creating an IPVR device for an EPIC MV, you do not enter the IP Address of the EPIC
MV itself, but that of the switch it is connected to.
Data VLAN Primary/Secondary Switch
: It is recommended that you segregate the traffic from different modules types, effectively different signals, onto separate VLANs to avoid any issues with handling or routing of signals. Once you do that, enter the relevant Primary and Secondary VLAN IDs into the VLAN fields in the Frame Details dialog when creating the IPVR device for that traffic/signal type.
Authentication
: Enter the Username and Password for the system. Use a name that makes the IPVR device easy to identify, such as
IPVR_Arista_EPIC
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 88
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Switch Configuration:
System Configuration
Sources and Destinations from EPIC MV Devices
Once your EPIC MV devices have been independently configured and set up as IPVR devices, source/destination definition from the modules is done via the Database Foundry. The Database
Foundry is not directly accessible (or visible) from the SDNO Controller Web UI. You need to create a routing system in Magellan CCS Navigator, poll using the SDNO Controller IP Address, and then click IP3
Routing System under the Routers folder. This launches the SDNO Controller Web UI within Navigator
(on the right) and displays the Database Foundry.
Note: You need one or more device type definitions before using the Database Foundry to add sources/destinations.
See Sources/Destinations from IPVR Devices (on page 144).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 89
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Adding Incorrect/Offline Frames
System Configuration
Adding Offline Frames
If you add a frame that is offline, it cannot be validated right away and will be validated when the frame becomes available. Unavailable/unvalidated frames that have been added will show frame type as "IP3
Frame", details will be grayed out, and you will see a warning message in the right pane.
Once the device becomes available, its details will be updated in the main dashboard, and you should be able to click the Go to Frame button, as well as see Power Supply, Fan, and IP address information in the right hand pane.
Adding Frames with Frame/Family Mismatch
When you add a frame, you also need to select the frame family - for example,
Platinum
(for Platinum or Platinum IP3 frames),
Platinum VX
(for Platinum VX frames), or
XY Pass Through
(for X/Y frames). If you add a frame using the incorrect product family, for instance, a
Platinum VX
frame using the
Platinum
family (instead of the Platinum VX family), if the device is offline, will not be validated right away. If it is online, or once it becomes available, you will see an error message stating that there is a mismatch between the frame type and the family selected. To fix this, remove the frame and re-add it again using the correct family.
Figure 26: SDNO Controller Dashboard - Frame/Family mismatch
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 90
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Modifying a Device
System Configuration
Once a router device has been added to the system, you can edit details in
Configure System >
Hardware Foundry > Routing Device.
Click the
Edit
link against a Frame.
Note: Also see Changing Frame IP Addresses (on page 91).
Removing a Device
To remove a device that has been added to the system, select a frame or panel in the list and click the
Remove Device
button to delete that component.
Important
: When you remove a frame, you need to publish (via Navigator) for the changes to take effect in the routing system.
Changing Frame IP Addresses
If you need to change the Primary or Secondary IP address of a frame that has been added to your SDNO
Controller, the following is recommended:
1.
First change the IP Address on the device
2.
In the SDNO Controller UI, remove the frame (with the old IP Address) from the hardware foundry.
3.
Add the frame again, using the IP Address of the primary Ethernet adapter on the frame
4.
Publish from Navigator so the changes take effect in the Routing System
Note:
It is important that you use the same label (Name) when re-adding the frame, so you don't lose any routing control.
Expansion Setup
To set up expansion, click the
Expansion Setup
button in the
Hardware Foundry
.
The following types of expansion are supported:
Matrix expansion
System expansion (Video)
Audio expansion
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 91
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Matrix Expansion
Matrix Expansion Input Modules help distribute input signals across 2 or more frames, connected via
DensiShield cables. By routing the inputs of one frame to another, you double the original number of outputs; if you route to 2 frames, you triple the number of outputs.
Note: Matrix expansion does not require the use of the Expansion Setup UI.
Matrix expansion is configured in the
SDNO Database Editor
at the
Source
level, using a
Device Type
with
2 Video Channels
. The Device Type itself should be defined though the
DB Editor
in
Navigator
.
Follow the wizard to create a
Video
Device Type
(for example, HD video), and then add another
Video
based
Connection Type
to it (for example, HD Video again).
Figure 27: Example of Device Type with 2 Video channels
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 92
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Map the input on the first frame to one video channel, and the map corresponding expanded input on the second frame to the second video channel.
For example, consider the case of two IP3 Frames,
F1
and
F2
. Both have cards in
Slot 1,
and the inputs of the card in
F1, Slot 1
can be expanded to
F2, Slot 1
(via DensiShield cable connecting the two).
System Expansion
System Expansion allows for multiple frames in your system to be ganged together to form a larger routing system. To do this:
1.
Click the
System Expansion
button to get to the Expansion dialog.
2.
Select the first frame from the
Frame
drop-down list
3.
Select the frame to connect it to from the second
Frame
drop-down list
4.
Click the
Add Connection
button
Figure 28: System Configuration - System Expansion
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 93
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Once created, connections will be displayed in the
Defined Expansion Connections
section.
Audio Expansion
Audio Expansion functions like System Expansion, but at the Audio level, allowing for Audio to be available to other frames.
To set up audio expansion:
1.
Click the
Expansion Setup
button in the Hardware Foundry.
2.
Select
Audio Expansion
from the Type drop-down
3.
Select the first frame from the
Frame
drop-down list
4.
Select the frame to connect it to from the second
Frame
drop-down list
5.
Click the
Add Connection
button
Figure 29: System Configuration - Audio Expansion
Once created, audio expansion connections will be displayed in the
Defined Expansion Connections
section.
Note: A single frame can be used in a maximum of one audio expansion and one system expansion connection.
In addition to the Audio expansion definition in the UI, ensure you make the required physical
connections - see Hardware Connections for Audio Expansion (on page 94).
Hardware Connections for Audio Expansion
To physically enable audio expansion, connect densishield cables across the PX-ATDM64-X28 modules in both frames, setting up a bi-directional connection between the TDM modules, so audio can be routed from one frame to another.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 94
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
For example, to route audio across 2 frames (presuming an active and redundant TDM Crosspoint module in each):
1.
Frame 1, TDM XPT OUT1 > Frame 2, TDM XPT IN1
Connect a Densishield cable from the OUT1 of the top PX-ATDM64-X28 module in Frame 1 to the
IN1 of the top PX-ATDM64-X28 module in Frame 2
2.
Frame 2, TDM XPT OUT1 > Frame 1, TDM XPT IN1
Connect a Densishield cable from the OUT1 of the top PX-ATDM64-X28 module in Frame 2 to the
IN1 of the top PX-ATDM64-X28 module in Frame 1
3.
Frame 1, TDM XPT OUT2 > Frame 2, TDM XPT IN2
Connect a Densishield cable from the OUT2 of the bottom PX-ATDM64-X28 module in Frame 1 to the IN2 of the bottom PX-ATDM64-X28 module in Frame 2
4.
Frame 2, TDM XPT OUT2 > Frame 1, TDM XPT IN2
Connect a Densishield cable from the OUT2 of the bottom PX-ATDM64-X28 module in Frame 2 to the IN2 of the bottom PX-ATDM64-X28 module in Frame 1
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 95
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
FRAME 1 FRAME 2
System Configuration
PX-ALARM-ATDM Module
v u x w
PX-ALARM-ATDM Module
u v w x
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 96
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
A bank of LEDs on the top of the PX-ATDM64-X28 module serve as a physical indicator of connection status. LEDs
D9
,
D6
,
D7
indicate the presence, Frame Lock and Phase lock of incoming ATDM signals. If both frames are properly locked to the same Sync and DARS signals and if the DensiShield cable is properly connected, all three LEDs will be on.
The web interface also indicates the connection status. See Audio Expansion Connection Status in the
Audio Expansion Connection Status in the Web UI
Open the
PX-ATDM64-X28
Audio TDM Crosspoint Module from the list of modules by clicking the
Open
Module
button against it.
In the parameters displayed, the Frame Expansion section displays a parameter
Expansion Link Status
.
This shows as "Link Present" if the connections have been properly made.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 97
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Client Device Router Database Access Control
System Configuration
The SDNO Controller enables you to set up access control for the router database. You can define portions of the router database that will be accessible to third party/client devices connecting to it.
Router control panels such as Magellan RCP, legacy router frames such as Edge, automation systems
(both Imagine Communications and third party), etc. are considering Client Devices. Setting up access control at the router database level helps reduce routing communication traffic to the client device, thus improving system performance.
Access Control can be set up in two ways:
Based on the
Client Device
IP address
Based on the
Router Port
on the SDNO Controller
The first way is more specific, and requires you to individually create entries specifying IP Addresses for all the client devices you have. The second way is more generic and doesn't rely on individual client IPs; rather, you apply the access control at the SDNO Controller port level and everything that communicates with the SDNO Controller via that port is subject to those restrictions.
After creating a client device or router port (access control) definition, you need to
create a filter
and apply it to the client definition, specifying the sources and destinations that should be accessible. Filters are created on the SDNO Controller, and have to be set up via Navigator (Filter Editor). By defining a subset of your database and creating a filter, you can establish access control, and only the defined set of database information (sources and destinations) will be accessible to specified clients.
As an example, if you have a third party router in your system, do the following:
1.
In the SDNO Controller Web UI:
Define the third party router as a
Client Device
in the SDNO Controller UI.
See STEP 1 (Option 1) - Define a Client Device for Access Control (on page 99)
OR
Define a
Router Port
that the router will communicate through.
See STEP 1 (Option 2) - Define a Router Port for Access Control (on page 100)
2.
Launch the SDNO Controller UI in Navigator, go to the
Filter Editor
(sub component of the
Database
Foundry
) and define the sources/destinations to make accessible from there. See STEP 2 - Define a
Filter for the Client Device/Router Port (on page 101)
Note: Apart from access control, filters can also be used to control network traffic, since client devices (when part of your routing system) are capable of generating a lot of traffic depending on information that flows between the SDNO Controller and them, including queries and other communication.
3.
After the Router Database is published to a client device, that client device can only access the sources and destinations defined in the filter
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 98
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
STEP 1 (Option 1) - Define a Client Device for Access Control
1.
Go to
Configure System
>
Hardware Foundry
>
Client Device
2.
Click
Add Device
to define a new Client Device
System Configuration
3.
Enter a
Name
for the Device, provide its
IP Address
, the
Type
is Routerclient by default
4.
Click
Add
This client will now be listed in the list of Existing Client devices. This Client device will now will be subject to the restrictions of the filter associated with it. See STEP 2 - Define a Filter for the Client
Device/Router Port (on page 101)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 99
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
STEP 1 (Option 2) - Define a Router Port for Access Control
1.
Go to
Configure System
>
Manage SDNO Controller Settings
>
Router Ports
System Configuration
2.
Click
Add Port
3.
Enter the
Port
Number, keep in mind the available ranges listed.
Note: The Port number you enter here is the one via which third party devices will communicate with the SDNO Controller (you need to configure this on third party devices).
4.
Select the
Protocol
; most equipment communicates with the SDNO Controller via LRC
5.
Enter a
Name
for the Port definition and click
Add
Once defined, any third party equipment communicating with the SDNO Controller via the specified port, will be subject to the restrictions of the filter associated with this port. See Define a Filter for the
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 100
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
STEP 2 - Define a Filter for the Client Device/Router Port
System Configuration
Note: Ensure you have defined a client device or a Router Port before defining a filter.
1.
Launch the SDNO Controller UI via Magellan CCS Navigator
2.
Go to
Database Foundry
>
Filter Editor
3.
Click
New Filter
4.
You will see the available
Sources
and
Destinations
in tabs
5.
Choose a subset that you want to make accessible and click the
Add
button to move them to the
Selected
column. This is what will go into the filter.
6.
Do the same with the
Destinations
7.
Give the filter a
Name
and click
OK
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 101
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
8.
Once you save the filter, select it in the
Filters
column in the
Filter Editor
9.
Click the
Assign Resources
button on top
System Configuration
10.
Create an association with a previously defined
Client Device
or
Router Port
by selecting it in the list and then clicking
Add
Define a Client Device/Router Port from Navigator itself
Since you have to set up your Filter in Navigator, if you prefer, you can do the entire process in
Navigator itself.
Note: You can launch the SDNO Controller UI in Navigator and replicate all the same steps as when you do it via the Silverlight web UI, or you can follow the steps below, first defining a filter and then using some shortcuts provided in the Filter Editor to define client devices/server ports.
1.
Launch the
SDNO Controller UI
via
Magellan CCS Navigator
2.
Go to
Database Foundry
>
Filter Editor
3.
Click
New Filter
4.
You will see the available Sources and Destinations in each of those tabs
5.
Choose a subset that you want to make accessible and click the
Add
button to move them to the
Selected
column. This is what will go into the filter.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 102
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
6.
Do the same with the Destinations
7.
Give the filter a
Name
and click
OK
.
8.
Once you save the filter, select it in the
Filters
column in the Filter Editor
9.
Click the
Assign Resources
button on top
10.
Click
Add Client Devices
to associate the filter with a client device
System Configuration
11.
Click
Add Router Ports
to associate the filter with a port
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 103
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Manage SDNO Controller Settings
System Configuration
Click the
Manage SDNO Controller Settings
icon to define or modify your system hardware configuration
Four tabs are displayed:
Router Settings (on page 104 )
Network and Redundancy (on page 106)
Router Settings
Set the XY ID for the SDNO Controller here. In the XY control protocol, every device including the router itself has a unique ID. In systems with only one router, it is common (but not required) that the router have ID 0, and this is the default on the SDNO Controller.
In systems with more than one router (for example, tieline systems with Platinum Routers), it may be desirable to set the XY ID to something other than zero.
In the XY control protocol, there is a tree structure of connections between devices such that XY messages get distributed from device to device. In many configurations, the SDNO Controller is the
ROOT of that tree, and the other XY devices will point to the SDNO Controller as their server. In this case, setting this Server IP field to 0.0.0.0 indicates that the SDNO Controller should not connect to any higher server.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 104
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
In some system configurations, it may be desirable to have the SDNO Controller make a client connection to another XY server; if that is the case, fill in the IP address of that remote server here. Be very careful to avoid creating loops of connectivity in the XY distribution - if you do this, messages can cycle endlessly and make the routing system unusable.
In the
Server
field, in case of Hybrid systems, enter the IP Address of the other Router, for example,
Platinum. When you create a routing system in Navigator by
polling
the Controller IP, the device (for which you provided an IP here) will be included in your routing system.
Checking
Operator Read only Access
under
Soft Panel Options
ensures that users that login to the Soft
Panel application as operators are provided with read-only access.
Router Ports
The SDNO Controller enables you to set up access control for third party/client devices connecting to it.
Access Control can be set up based on the Client Device IP address or based on the Server Port on the
SDNO Controller.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 105
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Network and Redundancy
See Controller Redundancy (see "SDNO Controller Redundancy" on page 233).
System Configuration
Maintenance
The Maintenance tab provides an option to safely Power Off your Primary and Secondary SDNO
Controllers.
User Foundry
Click the
User Foundry
icon to manage user accounts and passwords.
User Accounts
The SDNO Controller application ships with two access accounts:
Administrator Account
This account has full access rights. Some of the key Administrator privileges include:
System Setup (Configuring Controller ID, IP, IP3 frames)
Router Database Configuration
Routing System Control and Monitoring
Managing Operator and Administrator Passwords
Software Upgrades
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 106
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Operator Account
This account has the following privileges:
Routing System Control and Monitoring
Software Upgrades
System Configuration
Changing a Password
To change the existing password for either an
Administrator
or
Operator
:
1.
Click the
User Foundry
link on the
SDNO Routing System Configuration
dashboard.
2.
Then click
Change Password
against the
Administrator
or
Operator
.
Figure 30: Change Password Selection Dialog
1.
Enter the new password, then re-enter to confirm and click
Save
.
Figure 31: Password Change Dialog
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 107
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Firmware Foundry
System Configuration
The
Firmware Foundry
enables you to manage and upgrade firmware on frame modules.
Note:
The Firmware Foundry allows you to manage/upgrade firmware on frame modules only. You cannot upgrade SDNO Controller firmware from here. SDNO Controller firmware is upgraded via a
Windows desktop procedure.
Click the
Firmware Foundry
link on the
IP3 Routing System Configuration
dashboard to apply a
firmware upgrade on a module in a frame or manage the Firmware Repository (on page 108).
The Firmware Foundry allows batch upgrading of similar modules within a zone of the IP3 frame -- downloading the new firmware to like modules in parallel. In addition, firmware upgrade requests are queued by the Firmware Foundry and then sequenced to the hardware.
Multiple versions of firmware for the same module and for different modules can be stored. Firmware to be upgraded on a module must first be transferred to the firmware repository, since modules can only be upgraded with firmware that is available in the repository.
This section is divided into several areas:
Firmware Repository (on page 108 )
Resource Modules (on page 114)
Firmware Repository
The
Firmware Repository
tab is active by default. It lists all previous firmware versions for various modules. The following details are displayed per package:
Type
Version
Filename
Description
Build Date
Size
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 108
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
The
Add Package
and
Remove Package
buttons at the top allow for adding new firmware packages or selecting and deleting existing ones. You can also choose to group the listed firmware versions in the repository by
Type
(which lists by module type) or
None
, (a flat list will be displayed).
Figure 32: Firmware Repository
IO Modules
The
IO Modules
tab displays a list of individual Input, Output, and Crosspoint modules in the system.
The following information is displayed per module:
Name
Slot
Firmware
Repository Firmware
Category
Frame
Bookmark
Progress
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 109
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Figure 33: Firmware Foundry - IO Modules
The list of Modules can be grouped as follows:
Default -
Modules grouped alphabetically based on category (such as Control, Input, etc.).
Type -
Modules grouped based on type (for example, Alarm modules).
None -
Modules displayed in a flat list
Apart from the above groupings, if you want to group certain modules together for display, you can do so by selecting the
Bookmark
checkbox against modules. When you click the
Bookmark
column to sort, all modules that have been bookmarked will be displayed together at the top of the list (when grouped by None) or the top of the category (when grouped by Default).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 110
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Note: Bookmarking modules serves as a way to sort them, and the modules are not bookmarked for upgrades.
To upgrade the firmware on a module, select the module, then click the
Select Firmware
button, and then click
Upgrade
. Upgrade progress will be displayed in the Progress column and in the Active
Upgrade (on page 111) section.
Active Upgrade
The
Active Upgrade
section is displayed to the right of the screen. It provides details on in progress upgrades including the
Name
of the upgrade, the
Slot
the module being upgraded is in, and the
Progress
.
While upgrading module firmware, the ability to do parametric control of module parameters is impaired for modules in the same
zone
of the router where the upgrade is going on. It is advisable to pick a time of limited router usage in order to do module upgrades.
WARNING
Be aware of how long an upgrade may take before starting, in order to plan an adequate maintenance interval with the operations staff. Simple Input and Output modules upgrade in a few minutes per zone.
Upgrades to the Input Frame Sync module may take more than an hour.
While firmware upgrades of modules are being applied, parameter controls of modules in the same zone as the current upgrade will be impaired. Routing requests will still take effect and status will be returned as normal, but adjustments of the parametric controls of modules in the affected zone of the router will be impaired during firmware upgrade.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 111
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Configuration
Clicking the Upgrade Service Log
link takes you Magellan Diagnostic Logging.
Figure 34: Active Upgrades
Crosspoint (XPT) Modules
Crosspoint Modules are displayed in the
Firmware Foundry
in the
IO Modules
tab under
Category:
Crosspoint Cards
.
When upgrading Crosspoint Modules, there are certain restrictions with regard to compatibility between firmware versions. You cannot upgrade crosspoint modules running firmware versions 3.x to
4.x and vice versa. The following table displays information on firmware version compatibility.
Table 4: 3G XPT Modules
3G XPT Module
Name
Type
PM-40x32-3G5 A
A
PM-72x64-3G5
PM-64x64-3G9
B
B
B
A
B
B
B
A
B
B
A
A
B
Product ID
086
086
086
086
085
085
085
085
086
084
084
084
084
084
085
Versions
3.0
3.1
4.0
4.1
3.1
4.0
4.1
4.2
4.2
3.0
3.1
4.0
4.1
4.2
3.0
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Filename
PM-40x32-3g5_3_0.zip
PM-40x32-3g5_3_1.zip
PM-40x32-3g5_4_0.zip
PM-40x32-3g5_4_1.zip
PM-40x32-3g5_4_2.zip
PM-72x64-3g5_3_0.zip
PM-72x64-3g5_3_1.zip
PM-72x64-3g5_4_0.zip
PM-72x64-3g5_4_1.zip
PM-72x64-3g5_4_2.zip
PM-64x64-3g9_3_0.zip
PM-64x64-3g9_3_1.zip
PM-64x64-3g9_4_0.zip
PM-64x64-3g9_4_1.zip
PM-64x64-3g9_4_2.zip
Version 2.0 | Page 112
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
PM-128x128-3G9 A
A
B
087
087
087
PT-128x256-3G15
B
B
A
087
087
088
A
A
B
088
088
088
PT-128x256-3G28
A
A
B
B
B
B
A
B
B
B
088
088
088
089
089
089
089
089
089
089
3.0
3.1
2.3
4.0
4.1
4.2
2.0
3.0
3.1
4.0
4.1
4.2
2.0
3.0
3.1
2.3
4.0
4.1
4.2
System Configuration
PM-128x128-3g9_3_0.zip
PM-128x128-3g9_3_1.zip
PM-128x128-3g9_4_0.zip
PM-128x128-3g9_4_1.zip
PM-128x128-3g9_4_2.zip
PT-128x256-3g15_2_0.zip
PT-128x256-3g15_3_0.zip
PT-128x256-3g15_3_1.zip
PT-128x256-3g15_2_3.zip
PT-128x256-3g15_4_0.zip
PT-128x256-3g15_4_1.zip
PT-128x256-3g15_4_2.zip
PT-128x256-3g28_2_0.zip
PT-128x256-3g28_3_0.zip
PT-128x256-3g28_3_1.zip
PT-128x256-3g28_2_3.zip
PT-128x256-3g28_4_0.zip
PT-128x256-3g28_4_1.zip
PT-128x256-3g28_4_2.zip
Table 5: 1.5G XPT Modules
1.5G XPT Module Name Type Product ID Versions Filename
PM-64x64-X9
A
A
A
A
032
032
032
032
2.0
3.0
3.1
3.2
PM-64x64-X9_2_0.zip
PM-64x64-X9_3_0.zip
PM-64x64-X9_3_1.zip
PM-64x64-X9_3_2.zip
PM-128x128-X9
PT-128x256-X15
A
A
A
A
A
A
A
033
033
033
033
021
021
021
2.0
3.0
3.1
3.2
2.0
3.0
3.1
PM-128x128-X9_2_0.zip
PM-128x128-X9_3_0.zip
PM-128x128-X9_3_1.zip
PM-128x128-X9_3_2.zip
PT-128x256-X15_2_0.zip
PT-128x256-X15_3_0.zip
PT-128x256-X15_3_1.zip
PT-XP
A
A
A
012
012
012
2.0
3.0
3.1
PT-XP_2_0.zip
PT-XP_3_0.zip
PT-XP_3_1.zip1
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 113
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Resource Modules
The
Resource Modules
tab displays a list of Resource Modules (PX-RES) for upgrade.
System Configuration
Figure 35: Firmware Upgrade on the RES Card
Resource Module upgrades are a two part process:
1.
Transferring the firmware package from the IP3 Controller to the Resource Module
2.
Activation of the new firmware on the Resource Module
Note:
Upgrades to Resource modules occur in the background and are non-invasive to system operations. Firmware activation can take up to 15 minutes, and all of the services of the router will be interrupted during the Activation of new firmware on the Resource Module(s).
Primary and Secondary Resource Modules are always upgraded synchronously. The Secondary Resource
Module cannot be upgraded explicitly.
You can store up to 2 firmware versions on Resource Module(s) - one active and one alternate. The alternate firmware is always upgraded onto the alternate partition. You have to switch to the alternate partition to Activate the alternate firmware.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 114
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Upgrading Firmware on a Module
System Configuration
To upgrade the firmware on a module:
1.
Select the module, then click the
Select Firmware
button
2.
Click
Upgrade
. Upgrade progress will be displayed in the
Progress
column and in the Active Upgrade
Figure 36: Information on Active Upgrades
3.
Click
Activate
to make active once complete.
PX-RES Firmware Activation - Single PX-RES
Table 6: Single PX-RES Activation
Primary PX-RES
(PX-RES 1)
Active
Secondary PX-RES
(PX-RES 2)
Not Present
Active Upgrade States Dashboard Status
Activating
Activating Primary
Completed
Blank
Active > Inactive
Inactive > Activating
Activating > Inactive
Inactive > Active
Approximate Time to
Upgrade
5 minutes
When you choose to activate a firmware version on a Resource Module, activation States are displayed in the
Progress
column.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 115
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
The
Active Upgrade
section on the right shows you activation details.
System Configuration
And the main dashboard displays the Activation
Status
as well.
PX-RES Firmware Activation - Dual PX-RES
Table 7: Dual PX-RES
Active Upgrade States Primary PX-RES
Status
(PX-RES 1)
Activating Secondary
(PX-RES 2)
Active
Secondary PX-RES
Status
(PX-RES 2)
Standby
Not Present
Initializing
Configuring
Synchronizing
Active
Dashboard Status Approximate Time
N/A 15 mins
Activating Primary
(PX-RES 1)
Not Present
Configuring
Initializing
Synchronizing
Standby
N/A 15 mins
In case of dual PX-RES modules, the dashboard does not indicate activation status.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 116
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Upgrade Service Log
System Configuration
The
Upgrade Service Log
can be accessed in the Active Upgrade area to the right of the screen. Clicking the
Upgrade Service Log
link opens a new browser window that connects to
Magellan Diagnostic
Logging
(which runs on
http://<Controller IP Address>:8002
), and provides information on past upgrades.
Select
UpgradeService
under
IP3_Controller
and then click the
History
button
Figure 37: UpgradeService Log option
Then click the
Examine Logs
button.
Details on upgrade messages are then displayed. For example, messages indicating that firmware was updated for a specific module (along with the time). Or that new firmware for a specific module type was added to the firmware repository.
Figure 38: Upgrade information in the Examiner tab
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 117
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Frame and Module Parameters
Frame and Module Parameters
Through the web based UI, once you've set up your frames and modules, you can configure and control parameters for those modules.
For a complete list of modules and parameters, refer to the
IP3 Frame and Modules User Manual
.
Frames and Modules in the Web Interface
After a frame has been added to your system, you can see status and set editable parameters for both the frame and the modules in the frame. Click the
Go to Frame
button against the Frame for details (See
Frame Components (on page 122)).
A list of available modules and parameters are displayed, categorized by type.
Click the
Open Module
button to the right to see details of a module.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 118
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Frame and Module Parameters
The module is then displayed along with all of its parameters. Some of the parameters are status only
(read-only) and some are editable.
Note:
The window that is displayed (superimposed) contains details for the module clicked on - however, if there are more than one of that type of module in the frame, all modules of that type will be displayed in the column on the left.
Parameter/Status Menu Groups
For each Input/Output module, parameters/statuses are organized into three groups:
Module
Parameters that affect the module as a whole (such as Sync Select), or status that reflects the module as a whole (such as Software Version), are usually organized under this category.
Inputs/Outputs
Parameters and status that are indexed for each Input/Output on the module are organized under
Inputs
(for Input modules) or
Outputs
for Output modules (See Table Parameters (on page 121)).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 119
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Parameter Types
Frame and Module Parameters
Read-Only (Status) Parameters
Read-only or status parameters feed back the current state of a specific parameter.
Figure 39: Example of a Read-Only parameter
String Parameters
String parameters are items that can be renamed using text characters. String parameter changes do not take effect until the entire string has been modified. Use a keyboard, or copy and paste, to enter a value.
List Parameters
List parameters contain a series of possible values for a specific parameter. Enumeration and string-list parameter changes are always delayed. List parameters are identifiable by the arrow in the right corner of the button. When you roll the mouse over a list parameter, the button highlights, and when you click the arrow, available options are displayed. Select an item in the list to set the value for this parameter.
Figure 40: Example of a List Parameter
Range Parameters
A range parameter uses an incremented slider to choose a value from all available values. Numeric parameter values are represented by a sliding bar on the display screen. A progress bar indicates where the current value is within the entire range the parameter presents. The current value is shown at the right of the progress bar.
Figure 41: Example of a Range Parameter
You can control the editable parameters by entering values, selecting options from drop down lists, or in some cases by dragging a slider to the appropriate value.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 120
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Table Parameters
Frame and Module Parameters
Table parameters provide an interface to view a large number of settings in a single screen, linking multiple instances of the same parameter or series of parameters (for example, parameters that apply to multiple channels) OR simply grouping similar parameters together.
This screenshot shows parameters for the PT-FSDX8C1D-IBG Input Module, which has some General Info parameters
grouped
under a table. Click
Show Table
to view/expand options.
This screenshot displays how parameters that apply to multiple channels are combined and displayed.
The screen is divided into three panes - with the module on the left, instances in the middle, and the parameter fields to the right. You can drag the divider between these panes to expand and contract the view. You will see multiple rows corresponding to multiple channels.
Menu options can be accessed from menu links on the left and menu options in the drop down list in the top right hand corner.
To change a table parameter:
1.
Select a row (input) from the middle section (in this case, a channel). The Parameter pane updates to display the options and current settings for that row. By default, the parameter pane displays parameters for the first row in the table. The top right corner of the screen updates to indicate the row the parameters are for.
2.
Select the parameter you want to change.
The individual parameter control types are the same as for regular parameters.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 121
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Frame Components
Frame and Module Parameters
When you click the
Go to Frame
option for a specific frame on the main navigation page, it displays a complete snapshot of that frame including:
Modules in a Frame (on page 50 )
Frame Parameters (on page 122)
Power Supply and Chassis Fan Status
Frame Parameters
Frame specific components and their parameters can be viewed by clicking the
Open Frame
link.
Figure 42: Open Frame option to access Frame parameters
The following parameters provide a control interface to the IP3 frame. These parameters are divided into different menu groups, all listed below the main Frame:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 122
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Frame and Module Parameters
Frame Parameters (on page 122 )
Video Crosspoint (on page 125)
Frame
The
Frame
section provides the following parameters:
Table 8: Frame parameters
Parameter
Frame Type
Frame ID
Ambient Temperature
Type Description/Options
RO
RO
RO
IP3 28 RU
IP3 15 RU
A unique 6-byte frame identifier
The Frame temperature in degrees celsius
Figure 43: Frame Parameters
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 123
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
PX-RES
The
PX-RES
section provides the following parameters:
Frame and Module Parameters
Table 9: PX-RES parameters
Parameter
PX-RES 1 Serial #
PX-RES 2 Serial #
PX-RES 1
PX-RES 2
Select Active PX-RES
PX-RES Firmware Version
Type Description/Options
RO
RO
RO
RO
RW
<String>
Not Present
<String>
Not Present
Active
Standby
Not Present
Initializing
Configuring
Failsafe
Active
Standby
Not Present
Initializing
Configuring
Failsafe
PX-RES1
PX-RES2
RO A string showing the current firmware version of the active
PX-RES
PX-RES Alternate Version RO A string showing the firmware version on the alternate bank of the active PX-RES
Figure 44: PX-RES Parameters
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 124
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Video Crosspoint
The
Video Crosspoint
section provides the following parameters:
Table 10: Video Crosspoint parameters
Parameter
Video Crosspoint 1
Video Crosspoint 2
Select Active Video Crosspoint
Type Description/Options
RO
RO
RW
Active
Standby
Not Present
Failed
Active
Standby
Not Present
Failed
Module1
Module2
Frame and Module Parameters
Figure 45: Video Crosspoint Parameters
TDM Crosspoint
The
TDM Crosspoint
section provides the following parameters:
Table 11: TDM Crosspoint parameters
Parameter
TDM Crosspoint 1
Type Description/Options
RO
Active
Standby
Not Present
Failed
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 125
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Parameter
TDM Crosspoint 2
Select Active TDM Crosspoint
Type Description/Options
RO
RW
Active
Standby
Not Present
Failed
Module1
Module2
Frame and Module Parameters
Figure 46: TDM Crosspoint Parameters
Sync
The
Sync
section provides the following parameters:
Table 12: Sync Parameters
Parameter
Sync Mode
(Table Parameter)
Type Description/Options
RW Auto, Standard, Advanced
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 126
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Parameter
Output Standard
(RW only when Sync Mode (Table
Parameter) is set to Standard)
(Table Parameter)
Sync Pulse Delay
(available only when Sync Mode
(Table Parameter) is set to
Advanced)
(Table Parameter)
Type Description/Options
RW
None
525/60
525/59.94
625/50
1920x1080/60I
1920x1080/59.94I
1920x1080/50I
1920x1080/30P
1920x1080/29.97P
1920x1080/25P
1920x1080/24P
1920x1080/24PsF
1920x1080/23.97P
1920x1080/23.97PsF
1280x720/60P
1280x720/59.94P
1280x720/50P
1920x1080/60P
1920x1080/59.94P
1920x1080/50P
RW 0 to 65535
RO
Frame and Module Parameters
Displays the current detected reference standard. Detected Sync
(Table Parameter)
Sync Module 1
Sync Module 2
Select Active Sync Module
Sync 3 - Source Select
Sync 4 - Source Select
RO
RO
RW
RW
RW
Active, Standby, Not Present
Active, Standby, Not Present
Module1
Module2
Sync 1
Sync 2
Sync 3
Sync 1
Sync 2
Sync 4
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 127
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Frame and Module Parameters
Figure 47: Sync Parameters
Sync Notes
The
Sync Mode
parameter (set to
Auto
by default) allows for configuration of switching point settings. In
Auto
mode, the output switches relative to the detected sync reference assigned to the module.
If
Sync Mode
is set to
Standard
, the
Output Standard
parameter can be used to specify the video standard to use as the switching point timing reference relative to the sync reference signal detected on the selected Sync input (Sync 1 - 4)
If
Sync Mode
is set to
Advanced
, the
Sync Pulse Delay
parameter can be used to specify where the output switching point is relative to the reference signal. The delay is in units of microseconds.
Power Supplies
The
Power Supplies
section provides the following parameters:
Table 13: Power Supplies parameters
Parameter
Top Shelf 5V Power
(28 RU only)
5V Power
(15 RU only)
Bottom Shelf 5V Power
(28 RU only)
Zone 1 24V Power
Zone 2 24V Power
Type Description/Options
RO
RO
RO
RO
RO
Present
Failed
Present
Failed
Present
Failed
Present
Failed
Present
Failed
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 128
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Parameter
Zone 3 24V Power
(28 RU only)
Zone 4 24V Power
(28 RU only)
Type Description/Options
RO
Present
Failed
RO
Present
Failed
Frame and Module Parameters
Figure 48: Power Supplies Parameters for a 28 RU Frame
Ethernet Ports
The
Ethernet Ports
section provides the following parameters:
Table 14: Ethernet Ports Parameters
Parameter
MAC Address 1
Type Description/Options
RO MAC Address of the 1st Ethernet Port on the active PX-RES
Port 1 if PX-RES on the top slot is active
Port 3 if PX-RES on the bottom slot is active
IP Address 1
IP Mask 1
Gateway Address 1
Save Ethernet 1
RW
RW
RW
RW
IP address string for the back panel Ethernet connectors 1 and 3
IP mask string for the back panel Ethernet connectors 1 and 3
Gateway Address string
No
Yes
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 129
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Parameter
MAC Address 2
Frame and Module Parameters
Type Description/Options
RO MAC Address of the 2nd Ethernet Port on the active PX-
RES
Port 2 if PX-RES on the top slot is active
Port 4 if PX-RES on the bottom slot is active
IP Address 2 RW
IP Mask 2
Gateway Address 2
Save Ethernet 2
RW
RW
RW
IP address string for the back panel Ethernet connectors 2 and 4
IP mask string for the back panel Ethernet connectors 2 and 4
Gateway Address string
No
Yes
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 130
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Serial Ports
The
Serial Ports
section provides the following parameters:
Table 15: Serial Ports parameters
Parameter
Port (1-2) Mode
Port (1-2) Baud Rate
Port (1-2) Stop Bit
Port (1-2) Parity
Save Serial (1-2)
Type Description/Options
RW
RW
RW
RW
RW
RS 232
RS 422
300
600
1200
2400
4800
9600
14400
19200
38400
57600
115200
1
2
None
Odd
Even
No
Yes
Frame and Module Parameters
Frame Faults
To see Frame specific faults:
1.
On the main navigation page, click the
Go to Frame
button against a Platinum IP3 or Platinum frame
2.
Click the
Open Frame
button under Frame Configuration on the right
3.
In the Frame view that is displayed, click the
Faults
button
For information on the cause of the fault, look at the
Fault Name
column.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 131
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Frame Faults - IP3 Frame
Frame and Module Parameters
The following table lists possible Frame faults and descriptions for an IP3 Frame.
Table 16: Frame Faults
Fault Name
Power Supply Failure
Description
One of the Power Supplies has failed
Video Crosspoint 1 Cooling Failure Video Crosspoint 1 has reached a critical temperature threshold
Video Crosspoint 2 Cooling Failure Video Crosspoint 2 has reached a critical temperature threshold
Front Fan 1 Failure
Front Fan 2 Failure
At least one of the Fans in Fan Module 1 has failed
At least one of the Fans in Fan Module 2 has failed
Rear Fan Failure
Power Supply Fan Failure
Failsafe Mode
At least one of the Rear Fans has failed
At least one of the Power Supply Fans has failed
The Resource Module (PX-RES) is in failsafe mode
(this is a warning, not an alarm)
Image Activation Failure
Synchronization Failure
The active image has rebooted more than 5 times (this occurs if the software crashes)
Synchronization between the Active and Standby Resource
Module (PX-RES) has failed.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 132
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Frame Faults - Platinum Frame with PX-RES
Frame and Module Parameters
The following table lists possible Frame faults and descriptions for a Platinum Frame with PX-RES.
Table 17: Frame Faults
Fault Name
Power Supply Failure
Power Supply Fan Failure
Failsafe Mode
Image Activation Failure
Synchronization Failure
Upper Fan Failure
Control Section Fan Failure
Lower Fan Failure
Module Alarm
Description
One of the Power Supplies has failed
At least one of the Power Supply Fans has failed
PX-RES is in failsafe mode
(this is a warning, not an alarm)
The active image has rebooted more than 5 times (this occurs if the software crashes)
Synchronization between the Active and Standby Resource
Module (PX-RES) has failed.
At least on of the fans in the IO Module section has failed
At least one of two fans in the Resource Module section has failed
At least one of the fans in the lower section of the frame has failed (only applies to a 28 RU Platinum frame)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 133
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Resource Module (PX-RES)
Resource Module (PX-RES)
PX-RES Overview
The
PX-RES
Resource card serves as the central control point for the Platinum IP3 frame and all modules that reside in the frame. The PX-RES is a control module with software and hardware components that control communications between the different processing modules (input, output, crosspoint) in an
Platinum IP3 Controller frame. It also enables communication with external devices (configuration, control, monitoring, and routing).
The PX-RES module also provides the sync processing necessary to determine the switch timing for the frame. The control system reports the presence and type of sync signal detected on each of the four inputs. The PX-RES module distributes the synchronization signals to all the crosspoint, streaming, and output monitoring modules in the frame. It also automatically generates and distributes an internal synchronization signal when no external sync input is present.
PX-RES Parameters and Upgrades
The PX-RES provides access to frame and module parameters via the CCS protocol, and routes video and audio signals within a deterministic time frame.
It also provides a consistent mechanism to upgrade module firmware. See Upgrade information for
Resource Modules (on page 114).
PX-RES Redundancy
The PX-RES Resource module and optional redundant resource module are located in the middle of the frame and are visible when the front panel door is opened.
Each Platinum IP3 frame can have up to two PX-RES modules operating redundantly. If one module detects failure of the other, it switches over control and continues router operation.
ENET5
is the primary PX-RES Ethernet port. SDNO Controller version 1.3 onwards uses the redundant PX-RES
Ethernet port (ENET6) to connect to IP3 Frames. The redundant ENET6 port will be used if the connection to the primary port ENET5 fails.
Both IP addresses of a frame are required in the hardware configuration to allow the SDNO Controller to connect to a frame using either
ENET5
or
ENET6
. When
ENET 6
is enabled, the addition of one or more frames to the SDNO Controller system enables the additional IP. Both IPs (if available) will be displayed in the Hardware Foundry UI.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 134
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Resource Module (PX-RES)
The SDNO System dashboard displays the frame IP being used by the SDNO Controller to connect to the
IP3 frame. When the frame is selected in the dashboard, both IPs are displayed in the property pane on the right side of the dashboard. The IP being used by the SDNO Controller to connect to the frame is highlighted.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 135
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Resource Card Synchronization
Resource Module (PX-RES)
In normal operating mode, all parameter and route changes are synchronized from the active/master
PX-RES to the standby PX-RES.
When upgrading PX-RES firmware, images are also synchronized. If the alternate firmware image is activated on the active PX-RES, the alternate image on the standby PX-RES also becomes active.
Active and Standby Determination
Active and Standby states are non-volatile.
An active PX-RES remains active after a power cycle.
The standby PX-RES only becomes active if the active PX-RES is removed or in case of manual failover.
If two PX-RES modules are inserted into a frame and powered up at the same time, the PX-RES in the top slot will have higher priority.
Alarms
All alarms are off by default, except for critical temperature alarms. Individual alarms can be turned on or off. The following error conditions can trigger an alarm:
Loss of input or output signal
Power supply failure
Fan failure or missing front fan modules
Video crosspoint reaching critical temperature
PX-RES synchronization failure
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 136
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Database Editor
SDNO Database Editor
The
SDNO Database Editor
is a Database Matrix Definition System for
SDNO Controller only
or
SDNO
Controller hybrid
systems. A hybrid system is a routing system composed of IP3 and other routers.
Unlike traditional routing systems that may have different audio/video components on different levels corresponding to physical matrices, with the SDNO Database Editor, restrictions caused by physical level and physical matrix definitions are removed, and every part of every signal is accessible by name and easily routable.
Device Type definitions are used to group the parts (or components) of a signal together into a Source or
Destination that can be routed as a whole. These device types are created in the DB Editor in Magellan
CCS Navigator and exported into the SDNO Database Editor.
Note: Ensure you have a device type definition (done via the DB Editor in Navigator) before you attempt to add sources/destinations in the SDNO Database Editor. See STEP 4 - Define Device Types in DBEditor
(see "STEP 3 - Define Device Types in DBEditor" on page 34)
The SDNO Database Editor launches on the following conditions:
The Navigator user must be an
Administrator
.
Navigator must be running in
Build
Mode. The
SDNO Database Editor
is disabled/hidden in
Control
mode.
The Controller node must be under the
Routers
folder in Navigator, not under
Discovery
or
Network
.
Navigator’s
DBEditor
cannot be open/running. This is to prevent simultaneous configuration changes that may result in unsynchronized data between Navigator and SDNO Controller.
To launch the SDNO Database Editor:
1.
Start Navigator Server.
2.
Double click
SDNO Routing System
under the
Routers
folder to launch the SDNO Controller interface.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 137
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
3.
The Database Editor screen will be displayed.
SDNO Database Editor
Sources/Destinations in the SDNO Database
Editor
Click on the
Sources
or
Destinations
tab to define your sources/destinations. You can switch between these tabs at any time. The following functions can be performed here:
Add
Click the
Add
button to add a new source or destination. Provide the following details for your source/destination:
Number
: The
number
of Sources or Destinations to create. By default, a single Source/Destination will be created. If a greater number is entered here, for example 10, 10 sequential sources or destinations will be created, incrementally named (based on the Name Prefix) and with the same details.
Field Names Section
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 138
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
Name Prefix
: Enter a name for the Source or Destination. By default,
Sr
or
Ds
. Limited to 16 characters.
Use Name Index
: Select this option to use Name Indices. Unchecking this grays out the
Name Index
field.
Name Index
: Index of the Source/Destination.
Alias
: Alias for the Source/Destination.
Long Name
: Long Name for the Source/Destination. Opt to provide a longer more descriptive name than the character limited
Name
.
Description
: Description of the Source/Destination.
Note: If you append a space and a number after the
Alias
,
Long Name
, or
Description
fields, the number is automatically incremented for the number of sources or destinations you create. For example, if you choose to Add 5 Sources and enter
MySource 1
in the
Long Name
, the other 4 sources created will have Long Name
MySource 2
,
MySource 3
,
MySource 4
, and
MySource 5
.
Physical Location Configuration Section
Device Type
: Select the appropriate Device Type from the drop-down list. All created device types are listed here.
Link
: When you select a Device Type, its connection types are displayed in a list below it. So if for example you have an HD Embedded Device Type with HD Video, Analog Audio, and MADI connections, you will see all of those as checkboxes listed below the main device type. You can select two or more like connections within a device type and link them by clicking the Link button below. By doing this you can make changes to the source/destination details on the right applicable to specific connections.
Frame
: Select the Frame or Device that contains the source/destination. You will see a combination of routers and IPVR devices.
Management Type
(
Only displayed for IPVR devices
): You can define where this will be Managed or
Unmanaged Source
Device
: Either select from the drop-down list of IP3 frames, or enter the IP Address of the device.
For example if you're adding destinations from an EPIC MV device, enter its IP Address here. Or if
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 139
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor you're adding sources/destinations from a Selenio MCP Module, enter the Selenio MCP Controller IP
Address here.
Location Type
: (
Only displayed for Imagine Communications router frames
) Select if IN, OUT, or EXT
Slot
: Select the Slot in the frame that the module resides in
Port
: Select the applicable Port
Channel
: Select the Channel
# of Ports/Slot
: Enter the number of ports per slot for the module
# of Channels/Slot
: Enter the number of channels per slot for the module
Primary/Secondary Switch Configuration
(
Only displayed for IPVR switches
): Select the appropriate
Interface Type for your switch from the drop-down (for example. 10GbE). The other options you see here are based on
Switch Configuration
settings made in the
Hardware Foundry
when creating the switch. For example, if you define a switch with a specific port range, the Port entered here has to be within that range. If you define a fixed switch, you will only see the Port option.
Breakaway Configuration
This section is only displayed if you're using a Device Type that has an Audio connection. Select this check box to create a breakaway source or destination - the defined source/destination will be available on all levels, with the ability to route across levels.
Preview Channels
Two icons are displayed to the right enabling you to configure the location of the preview for your channels, either below or to the right, depending on your space availability and personal preferences.
Add Rows
: Click to Add rows or effectively, sources or destinations with the defined settings.
Cancel
: Click Cancel to exit without making or saving any changes.
Note:
When you "Add" a Source/Destination, it gets positioned at the bottom of the list, after any existing sources/destinations. Use the "Insert" option to insert into a specific spot, rather than at the end.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 140
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Undo
Click to
Undo
the last action.
Redo
Click to
Redo
the last action.
Insert
SDNO Database Editor
The
Insert
option is identical to
Add
- the only difference is with
Insert
, you can choose
where
to add sources/destinations.
For example, if you previously defined SR1-SR5, and you want to add a new source right after SR1
(rather than after SR5), use the Insert option to do so. If you use Add in this case, SR6 will be placed after
SR5.
Note: If you append a space and a number after the
Alias
,
Long Name
, or
Description
fields, the number is automatically incremented for the number of sources or destinations you insert. For example, if you choose to insert 5 Sources and enter
InsertedSource 1
in the
Long Name
, the other 4 sources created will have Long Name
InsertedSource 2
,
InsertedSource 3
,
InsertedSource 4
, and
InsertedSource 5
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 141
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Update
SDNO Database Editor
Use the
Update
option to modify details for a previously created Source or Destination. Select the appropriate checkbox to modify that section.
Note: If you append a space and a number after the
Alias
,
Long Name
, or
Description
fields, the number is automatically incremented for the number of sources or destinations updated. For example, if you choose to update 5 Sources and enter
UpdatedSource 1
in the
Long Name
, the other 4 sources updated will have Long Name
UpdatedSource 2
,
UpdatedSource 3
,
UpdatedSource 4
, and
UpdatedSource 5
.
Remove
Select one or more Sources/Destinations and click
Remove
to delete them.
Save
Click to
Save
changes.
Validate
Click to
Validate
sources/destinations added. If any of the sources/destinations do not validate properly, you will see an icon beside them that you can click on to see the validation details.
Note: When you click the Validate button, validations are performed on the SDNO Controller. By default, some validation is done at the UI level (as you add things in).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 142
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
Validation for duplicate names, duplicate physical locations are some examples of validations performed at the UI level. You will typically see duplicate names only when you import in a database, since you cannot add a duplicate name. Physical locations are validated on a per channel basis and reported even if they are on different levels. For IPVR sources and destinations, duplicate locations are reported if the
Multicast IP and Channel are duplicated. The switch IP address and Port are not required to match for a duplicate physical location validation error to show.
Refer to the Navigator help for additional steps in configuring your routing system such as:
Integrating IP3 and non-IP3 sources and destinations into the Navigator DBEditor
Adding Magellan remote control panels
Configuring tielines between IP3 frames and other routers
Disconnect and Park
The SDNO Controller supports
Disconnect
and
Park
functions (to free tielines), but changes need to be made in Magellan CCS Navigator, and not through the SDNO Database Editor.
Use the
Park
function to free a tieline used by a destination without disconnecting it; if you are unsure of a good local source available for switching, switch the destination to Park, which will route the designated park source to the output.
Use the
Disconnect
function to disconnect the destination using the tieline, with the result that the tieline is freed and the output is disconnected.
Resync
The Resync Sources menu provides the following options:
Resync Source Numbers
resyncs source numbers only
Resync Source XY Indices
resyncs XY only
The Resync Destinations menu provides the following options:
Resync Destination Numbers
resyncs destination numbers only
Resync Destination XY Indices
resyncs XY only
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 143
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
Sources/Destinations from IPVR Devices
This section covers setting up sources and destinations from IPVR devices such as Selenio MCP Modules,
EPIC MV Multiviewers, or PX-UCIP modules functioning as IP to SDI converters.
Note that in case of EPIC MV, you can only add destinations.
To add a
Source/Destination
from an IPVR device:
Go to the
Sources
or
Destinations
tab in the
SDNO Database Editor
Click the
Add
button
Enter
number
of
Sources/Destinations to create
Enter a
Name
,
Alias
,
Long
Name
,
Description
, and select whether to
Use Name
Index
.
Select the appropriate
Device Type
In the
Frame
drop-down, select the Frame that contains the
Source/Destination. This
Frame is the Switch previously configured for the IPVR Device in question.
Set
Management Type
to
Managed
(See
Managed/Unmanaged
Sources and Destinations
In the
Device
field, type in the IP
Address of the
Selenio MCP
Controller
device or your EPIC
MV device.
In case of a PX-UCIP module, select the IP3 frame that contains the module.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 144
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
In the
Slot
field:
For a Selenio MCP device, enter the physical slot # that the module resides in, in the
Selenio MCP frame.
For an EPIC MV device, enter the physical slot that the EPIC output module resides in.
For a PX-UCIP module, enter the slot the module resides in, in the IP3 frame.
Enter the
Port
. For example, in case of the EPIC MV, this is the quad 1 GBE port.
Enter # Ports/Slot. For example in case of the EPIC MV, it is 2 ports per slot.
In case of the PX-UCIP, the module has two Links, Link A and Link B that correspond to
Port 1 and Port 2 in the SDNO
Controller Database Editor. See mapping example figures in PX-
UCIP Modes and Database
SDNO Database Editor
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 145
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
In the
Channel
field, enter the
Module Channel #.
Note: If you add multiple sources/destinations in one go, the channel number may not increment accordingly, You may need to open each source or destination and manually increment the channel number.
Note
: In case of Selenio MCP, what you enter here differs depending on the
Selenio Module. For example:
In case of J2K, this is the Encoder/Decoder # which is 1-4 (depending on licensing)
In case of the Encoder/Decoder, it’s always 1.
In case of UCIP, it depends on:
The
Module I/O Configuration
(for example, 6 SDI In, 2 SDI Out)
And the resultant
IP Receiver
or
IP Transmitter #
Enter the
# of Channels/Port.
For example, the EPIC MV supports 6 3GB or 12 1.5 GB channels.
The PX-UCIP supports 8 channels.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 146
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
In the
Primary/Secondary
Switch Configuration sections,
enter the data ports for
Arista/Brocade/Cisco switch that the module (Selenio or EPIC
MV) plugs into.
Click Add Rows. You will see the sources or destinations added.
SDNO Database Editor
Note: When adding sources/destinations in bulk (for example 48 in one go), the port number is incremented automatically (for example, the first 6 destinations will be Slot 1/Port 1, the next 6 will be
Slot 1/Port 2, etc.). If you're setting it up non-sequentially, you have to reconfigure manually. For non sequential Ethernet ports, configure them in smaller groups rather than in bulk.
Link Function when Adding/Inserting
Sources/Destinations
When adding sources/destinations in the Database Foundry, a new
Link
button allows you to group together different portions of a device type comprising different connection types.
When to use Link
Use Link when adding/inserting sources or destinations that need a
fill pattern applied to a common starting location
.
Example
:
Consider a use case for 4K Video routing with
consecutive ports across Slots
. You use a device type consisting of 4 HD Video connections. When these connections are linked:
Connection 1:
Its Frame/Slot/Port/Channel gets treated as the starting location
Connections 2, 3, 4:
Channel values populate incrementally based on the
'# of Channels/Port' and '# of Ports/Slot' entered values.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
HD Video Connection 1:
Frame 1, Slot 1, Port 1,
Channel 1
HD Video Connection #2:
Frame 1, Slot 1, Port 1,
Channel 2
HD Video Connection #3:
Frame 1, Slot 1, Port 1,
Channel 3
HD Video Connection #4:
Frame 1, Slot 1, Port 1,
Channel 4
Version 2.0 | Page 147
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
So for example, if you want to add 6 logical sources:
SDNO Database Editor
1.
You have a
4K video device type
already defined, comprised of
4 HD Video connections
, each on a
separate level
(levels 0,1,2,3).
2.
You click the
Add
button in
Database Editor
, enter "
6
" as the number of Sources to create, assign a name and prefix (for example, IN 1)
3.
You move on to
Physical Location Configuration
section and select the 4K video device type
(which will list 4 HD Video connections)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 148
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
Assign a check mark beside each
Video Connection
and click the "
Link
" button
SDNO Database Editor
5.
Next, select the
Frame
,
Slot
,
Port
, and
Channel
(for example: Frame 1, Slot 1, Port 1, Video 1 and "# of Ports/Slot" = 8, "# of Channels/Port" = 1).
6.
Click
Add Rows
IN 1 will cover:
Slot 1: Ports 1-4
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 149
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
IN 2 will cover:
Slot 1: Ports 5-8
SDNO Database Editor
IN 3 will cover:
Slot 2: Ports 1-4
...
When not to use Link
Do
not
use link if a
fill pattern needs to be applied to 2 or more different starting locations
.
For example: consider a matrix expansion scenario. Let's say you have a device type with:
2 HD Video connections
Video Connection 1 mapped to a starting location of
Frame 1
, Slot 1, Input 1
Video Connection 1 mapped to a starting location of
Frame 2
, Slot 1, Input 1
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 150
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
Another example is in case of 4K Video routing, using each port of a quad-link on different slots. Let's say you have a device type with:
4 HD Video connections
Each mapped to the first port of each slot
Connection 1
Connection 2
Connection 3
Connection 4
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 151
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
IGMP/IGMP-Plus Data Switches
SDNO Database Editor
Data Switches
that you configure in the SDNO System are either
IGMP
or
IGMP-Plus
.
IGMP Plus Switches
are controlled by the SDNO Controller
; these are currently Arista, Brocade, and
Cisco. Any other Switches are considered
IGMP
whose performance will solely rely on the IGMP capabilities of the Switch. The IGMP/IGMP-Plus definition is done when adding a switch as an IVPR
frame (see Adding an Arista/Brocade/Cisco switch as as Device (see "Adding a Switch
(Arista/Brocade/Cisco) as a Device" on page 85)) in the Hardware Foundry, via a Management drop
down list.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 152
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Managed/Unmanaged Sources and
Destinations
SDNO Database Editor
Sources/Destinations
in the SDNO System can be either
Managed
or
Unmanaged
.
Managed Sources/Destinations are those generated from
devices controlled by the SDNO Controller
.
Sources/Destinations from devices not controlled by the SDNO Controller are considered "ummanaged", and also referred to as Blind sources/destinations. The managed/unmanaged selection is done when adding sources/destinations in the Database Foundry, via the Management Type drop down list.
You could have an IGMP-Plus Switch that uses unmanaged sources/destinations, or an IGMP switch using managed sources/destinations.
Note: When you add sources/destinations (SDNO Database Editor) from an IPVR device, there is no validation done.
Unmanaged Sources/Destinations in the Database Foundry and Database Editor
When adding blind sources/destinations in the Database Foundry, the following additional information needs to be defined:
Multicast IP stream and a secondary IP stream if available
Multicast port
Physical port which the blind source connected to the switch
After adding unmanaged sources/destinations, switch to the Database Editor. Any unmanaged sources/destinations will show up in a darker shade of green, as compared to the lighter green for managed sources/destinations.
Save and publish the database.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 153
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Database Import and Export
SDNO Database Editor
An SDNO Controller logical database can be exported to/imported from a text file, allowing for the database to be reused on a different SDNO Controller.
The Database Foundry provides an option to import an SDNO Controller database from file or export the current Database to a text file.
The import/export mechanism uses a txt file format similar to Magellan CCS Navigator's Names.txt file.
This file can be imported into the SDNO Database Editor, but not into Navigator.
Import/Export Information
Import/Export information includes:
Source and Destination data
Device Type definitions
Frame name definitions
Additional information required to restore the database to the exact same state
Import Validation
When importing a database (text file) into the Database Editor, device types contained in the exported database are validated against the ones in the current SDNO Database Editor.
If there is a conflict in device type
Name
(even though the definition may be different in terms of channels, channel names, levels, etc.) in the existing database and the imported one, a message will be displayed to indicate the conflict. Import will not proceed until the conflicting names have been changed or removed.
If there are no device type name conflicts, the database will be imported.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 154
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Restrict Editor
SDNO Database Editor
Click the
Restrict Editor
button in the
Database Foundry
view to access the Restrict Editor.
The Restrict Editor enables you to restrict routing of selected logical sources to logical destinations.
These restrictions are used to enforce business policy and reduce operator errors. Source Restrict definitions are in sets; you can define one or more source restrict sets, and each set consists of a list of one or more logical sources restricted from being routed to a list of one or more logical destinations.
You can define as many source restrict sets as required.
The database must be defined before any source restrict definitions, because Source Restricts apply to the existing logical database.
The editor displays existing source restrict sets on the left, and the content of the currently selected restrict set on the right. You can remove or edit an existing restrict set, or create a new one.
Rules when creating Restrict Sets
The following rules apply when creating a new restrict set:
The relation between destinations and sources defined in a restrict set is "
Any of
".
For example,
any of
the sources included into the restrict set cannot be routed to
any of
the destinations included in that restrict set.
Restrict sets can be defined in any of the following formats:
One source to many destinations
Many sources to one destination
Many sources to many destinations
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 155
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
The same source/destination can be used in multiple restriction sets.
SDNO Database Editor
Creating a new Restrict Set
1.
Click the
New Restrict
button. The
New Restrict Set
dialog is displayed.
2.
In the
Destinations
tab, define the list of logical destinations that the restrict set applies to by selecting from the available logical destinations (in the database) and clicking
Add
.
3.
In the
Sources
tab, define the list of logical sources that you want to restrict from being routed to each destination defined in the previous step by selecting from the available logical sources (in the database) and clicking
Add
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 156
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
Optionally, name the restrict set (at the bottom of the screen) and click
OK
.
Once the dialog closes the new restrict set will appear in the list of restrict sets.
SDNO Database Editor
5.
Click the
Save
button to save changes, and then click
Publish
.
4K Support
SDNO Controller 1.2 supports 4K which can be configured via the
SDNO Database Editor
. The first thing to do is have a clear idea of where your sources are for the 4K signals.
For example, you may have 4 separate cards that will contribute to the 4 components of the 4k signal, as follows:
Module 1, Slot 1, Port 1 > 4K1
Module 2, Slot 2, Port 1 > 4K2
Module 3, Slot 3, Port 1 > 4K3
Module 4, Slot 4, Port 1 > 4K4
Or you may have a single module, 4 different ports that will comprise the signal, as follows:
Module 1, Slot 1, Port 1 > 4K1
Module 1, Slot 1, Port 2 > 4K2
Module 1, Slot 1, Port 3 > 4K3
Module 1, Slot 1, Port 4 > 4K4
Make a note of the relevant slot numbers and port numbers.
Device Type for 4K
Ensure you have or create a
Device Type
with 4 Video channels. Follow these steps:
1.
In
Navigator
, run the
DB Editor
.
2.
Use the Wizard to create an
HD Video
device type, and give it a name to distinguish it, like
4KVideo.
Click
Next.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 157
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
3.
In the
Select Connection Types
dialog, click
Add Connection from Template
, and add 4
HD Video
connections
4.
In the
Level Selection Dialog
, select the starting level and click
Next
5.
In the
Configure Connection Types
dialog, select the appropriate levels for the video channels.
Normally, 4K video will be configured all on the same level as breakaways would not be needed.
However, if breakaways are required, then select different levels for each HD Video component.
Click
Next
.
6.
Click
Finish
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 158
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Sources for 4K
SDNO Database Editor
1.
In
Navigator
, close the
DB Editor
2.
Run the
SDNO Database Editor
3.
Click the
Add
button to add a source
4.
Ensure you use the correct
Device Type
with the 4 video channel definition. Select the correct
Slot
and
Port
and click
Add Rows
.
5.
Click the newly created source, you will see the 4 channels in the lower pane.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 159
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
6.
Double click an entry to change the
Slot
and
Port
, as required
SDNO Database Editor
Ensure the final definition physically matches the slots and ports for your 4K channel sources.
Destinations for 4K
Configure destinations the same way as the sources. See Sources for 4K (on page 159).
64 Levels Support
SDNO Controller 2.0 onwards supports up to 64 levels. The following are examples on how you can set this up and use it.
Note: This will only work with clients in LRC Mode. Clients in X/Y mode switch only the first 16 levels, not the rest.
Example 1 - Creating a 64 Level HD Embedded Device Type
1.
In
Navigator
, run the
DB Editor
. Use the
Wizard
to create a device type.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 160
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
2.
In the
Select Device Type
dialog, select
Create New Device Type From A Template
and select
HD
Embedded
. Click
Next
.
3.
In the
Select Connection Types
dialog, check the
Enable additional levels
checkbox. Click
Next
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 161
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
In the
Level Selection
dialog, you will see 64 levels available. Click
Next
.
SDNO Database Editor
5.
In the
Configure Connection Types
dialog, select levels for video and audio channels. Click
Next
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 162
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
6.
In the
Device Type Details
dialog, make any required changes, and click
Finish
.
SDNO Database Editor
Example 2 - Creating a 64 Level Custom Device Type
1.
In Navigator, run the
DB Editor
. Use the
Wizard
to create a device type.
2.
In the
Select Device Type
dialog, select
Create New Custom Device Type
, enter a
Name
, and click
Next
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 163
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
3.
In the
Select Connection Types
dialog, add
1 HD Video
connection type. And then add
63 Multiplex
Mono Audio
connection types.
4.
Click
Next
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 164
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
5.
In the
Level Selection
dialog, make any required changes and click
Next
.
SDNO Database Editor
6.
In the
Configure Connection Types
dialog, select levels for video and audio channels. Click
Next
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 165
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
7.
In the
Device Type Details
dialog, make any required changes, and click
Finish
.
SDNO Database Editor
Using the 64 levels Device Type
When you add a Source/Destination using a 64 level device type in the SDNO Database Editor, you will see the available levels.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 166
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual SDNO Database Editor
Support for Breakaway of Mono Audio
Sources
The SDNO database supports the ability to "fan out" Mono audio (or Stereo audio on the same level) to the extent of the number of levels defined in the routing system.
There is no longer a requirement to create a device type with multiple connections. In the SDNO
Database Editor, add Sources using a single level audio device type and click the breakaway flag. A duplicate copy of the physical location is created across all of the (defined) levels in the database, making that source accessible to any audio destination.
The following figures show sources added in the SDNO Database Editor (with and without the breakaway flag checked), and viewed from the DBEditor to see the fanning out across levels.
Figure 49: Sources added with a single connection defined on Level 1 with 'Breakaway' flag unchecked
Figure 50: Sources added with a single connection defined on Level 1 with 'Breakaway' flag checked
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 167
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Module Specific Configuration
IP3 Module Configurations
PX-HSRAEC-OM Output Monitoring Module Configuration
The
PX-HSRAEC-OM
is configured via the
SDNO Database Editor
in the
Magellan CCS Navigator
UI.
The following is an example that describes how to:
1.
Configure Output Monitoring Destinations
See Add PX-HSRAEC-OM Destinations (on page 169)
2.
Add Output Monitoring External Sources/Inputs
See Add PX-HSRAEC-OM External Sources/Inputs (on page 170)
3.
Add Router Destinations for monitoring
See Add Monitoring Router Destinations (on page 171)
The following steps walk you through the configuration and definition of output ports from both of these output modules for monitoring.
Launch the SDNO Database Editor
1.
Open
Magellan CCS Navigator
2.
Go to your routing system and open the
SDNO Database Editor
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 168
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Add PX-HSRAEC-OM Destinations
1.
Go to the
Destinations
tab, click the
Add
button
Module Specific Configuration
Enter
4
as number of
Destinations
to create
(Recommended)
Change the name in the
Name Prefix
field to visually distinguish this from other (non-monitoring) destinations. For example, include
MON OUT
in the name prefix.
Select a Video Device Type and select the appropriate Frame
Select
Slot
as
Slot 6,
Port as
Port 1
Note: This is to map the OUT 1 port
Set
Location Type
to
MON (Settings for Slot, Port, Channel, Max No of Ports per module, and
Max No of Channels per port fields will be set accordingly by default)
Click
Add Rows
You will see 4 monitoring destinations added at Slot 6 and 7 (ports 1 and 2).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 169
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Add PX-HSRAEC-OM External Sources/Inputs
Go to the
Sources
tab. Click
Add
to add the External Output Monitoring Sources/Inputs.
1.
Add
4
sources in total,
2
at Slot 6, and
2
at Slot 7.
Add
4
as the
Number of Sources
to create
Change the name in the
Name Prefix
field to distinguish as a monitoring output; for example, include
MON IN
Select a Video Device Type and select the appropriate Frame
Set
Location Type
to
EXT (Settings for Slot, Port, Channel, Max No of Ports per module, and
Max No of Channels per port fields will be set accordingly by default)
Click
Add Rows
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 170
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Add Monitoring Router Destinations
In the
Sources
tab, click the
Add
button
Module Specific Configuration
Enter
16
as number of
Sources
to create
(Recommended) Change the name in the
Name Prefix
field to visually distinguish this from other sources. For example, include
OM
in the name prefix.
Select a Video Device Type and select the appropriate Frame
Set
Location Type
to
OUT
Select
Slot
as
Slot 1
,
Port
as
Port 1
Note: This is to map the Slot 1 (OUT 1-8 ports) and Slot 2 (OUT 1-8 ports).
Click
Add Rows
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 171
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
You will see 8 destinations for monitoring added at slot 1 and slot 2 (ports 1-8) respectively.
Save and Validate Database Matrix
1.
Click
Save
to save the database matrix.
2.
Click
Validate
to validate it; there should be no errors.
3.
Click the
X
at the top to close.
4.
Open the
DBEditor
window under
Control Views
5.
Click
Publish
to send the Database configuration to the IP3 Controller. Click
Start Transfer.
Route Outputs
1.
Launch and log in to the
Router Soft Panel
by going to
http://<IPAddress>/panel
2.
To monitor a router
Destination
:
Route any of the
Destinations
(created in Add Monitoring Router Destinations (on page 171 ))
from the source list to one of the monitoring outputs (created in Add PX-HSRAEC-OM
You can monitor Router
Sources/Inputs
in the same way.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 172
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
3.
To view any of the external PX-HSRAEC-OM inputs:
Module Specific Configuration
Route the
MON Input
created in Add PX-HSRAEC-OM External Sources/Inputs (on page 170 ) to
the corresponding monitoring Output created in Add PX-HSRAEC-OM Destinations (on page
NOTE:
You can only monitor 1 channel from any given Output module. If you choose to monitor another channel from a given Output module, it will only be allowed if that channel is routed to monitoring port
OUT 1. And in doing so, you will disconnect any routes from another channel on that given Output card/slot/module to the other monitoring ports OUT 2 - OUT 4.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 173
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
PX-HSRMX-OBG Platinum Frame Synchronizer and Mux
Module Configuration
Follow these steps to configure your
PX-HSRMX-OBG
Output Frame Sync card.
1.
Launch
Navigator
. Discover your IP3 device and create a Routing System.
2.
Run the
DB Editor.
3.
Create 2 Device Types:
HD Embedded
and
HD Video
4.
Follow the Wizard to create the
HD Embedded
Device type
When creating the
HD Embedded
Device type, in the
Level Selection
dialog box, set the Number of embedded audio channels to 16 (default is 10).
Follow the Wizard to create the
HD Video
device type.
5.
Open the
SDNO Database Editor
from Navigator. Go to the
Destinations
tab.
6.
Click the
Add
button to add the 8 processed outputs
Use the
HD Embedded
device type add logical destinations for the 8 processed outputs
Enter
8
for the number of
Destinations to create
Ensure the
Slot number
corresponds to the Slot that contains your HSR module
Change the
Name prefix
to clearly identify these as Processed outputs, for example,
ProcX
Ensure the
Index
is set to
1
This adds 8 Outputs (Ports 1-8) with 1 video (Video 1) and 16 Audio (Audio 1-15) channels. Check that the entries have been correctly created in the upper and lower panes.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 174
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
7.
Click the
Add
button again to add the 8 unprocessed outputs.
Module Specific Configuration
Note: Unprocessed outputs are available on the same 8 physical ports as the processed ones, but the actual video channel is Video 2. After inserting unprocessed destinations, the location for each video channel on them needs to be manually changed to use Video 2 channel instead of Video 1. So create just 1 destination defined as Video 2, and then add the remaining 7, which inherit the Video 2 definition.
Use the
HD Video
device type to add a logical destination
Enter
1
for the
number of Destinations to create
Ensure the
Slot number
corresponds to the Slot that contains your HSR module
Change the
Name prefix
to clearly identify these as Unprocessed outputs, for example,
UnprocX
Select
Port 1
in the Port drop down
Ensure the
Index
is set to
1
8.
Once created, double click the entry in the lower pane and change from
Video 1
to
Video 2
9.
Click the
Add
button again to add
7
more sources; ensure you start at
Port 2.
10.
This completes the definition for the 8 processed and 8 unprocessed outputs.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 175
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
11.
Check that the unprocessed output entries have been properly created
Module Specific Configuration
12.
Validate
and
Save
.
13.
Open the
DB Editor
and
Publish
.
Platinum SX Pro and Platinum SX Hybrid Multiviewers
Platinum SX Pro and Platinum SX Hybrid are multiviewer modules in a Platinum IP3 router frame.
Platinum SX Pro modules occupy from one to four slots, and Platinum SX Hybrid modules occupy four slots.
Platinum Multiviewers Upgrade Procedure
Follow this procedure to upgrade firmware on Platinum SX Pro or Platinum SX Hybrid modules that are installed in your IP3 frame:
1.
Download the appropriate PIPE file and save it to the PC that you are accessing the IP3 system from
PIPE file for Platinum SX Pro
PIPE file for Platinum SX Hybrid
2.
Connect to the IP3 system by typing the IP address of the SDNO Controller in the URL field of your browser
3.
Click
Configure System
and select
Firmware Foundry
4.
In the F
irmware Repository
tab, click
Add package
.
5.
Locate the saved PIPE zip package and click
Open
. (Repeat for all three PIPE zip packages)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 176
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
6.
Go to the
IO Modules
tab and then select an HView-SXPRO and/or PX-SXP module in the Output
Cards category
7.
Highlight the module and click the
Select Firmware
button
8.
Select the upgrade zip file
9.
Click the
Upgrade
button and follow the instructions that appear on the screen
Platinum SX Hybrid Modules in the Frame
See the
Platinum IP3 Frame and Modules User Manual
for details on installing Platinum SX Hybrid modules in your Platinum IP3 frame.
Platinum SX Hybrid multiviewer modules in the frame are displayed under the
Output Cards
category in the list of modules in the frame. Since a single Platinum SX Hybrid module takes up 4 slots, each module is displayed over four slots - one module is the master, and the other 3 are slaves. For example, in this screen shot, you see:
Module Name
PX-SXH-32x2-S
PX-SXH-32x2-S
PX-SXH-32x2-S
PX-SXH-32x2
Description
Slave Module
Slave Module
Slave Module
Master Module
Slot
Slot 24
Slot 25
Slot 26
Slot 27
Figure 51: Platinum SX Hybrid Modules in a Platinum IP3 Frame
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 177
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Configuring a Platinum SX Hybrid Module
Module Specific Configuration
1.
Create a Routing system in Magellan CCS Navigator and poll for the SDNO Controller OR
Go to your existing routing system in Navigator
2.
Launch the SDNO Controller Web UI from within Navigator by double clicking
SDNO Routing System
under the
Routers
folder. This launches the
Database Foundry
.
3.
In the
Database Foundry
, go to the
Destinations
tab
4.
Click the
Add
button and do the following: a.
Enter
Destinations
as
32
(4 modules times 8 channels per module) b.
Enter a relevant
Name
,
Alias
,
Description
, etc. c.
Select the appropriate
Device Type
, for example, HD Embedded if you're using discrete audio d.
Select the
Frame
that contains your multiviewer modules e.
Select the first Slot that the module is in. f.
Set the Maximum number of channels per port, based on the device type. g.
Click
Add Rows
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 178
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
5.
You will see 32 destinations created, spanning 4 slots.
Save
.
Module Specific Configuration
6.
Close the
SDNO Database Editor
and open the
DB Editor
. Publish to synchronize with the routing system.
Refer to the
Platinum SX Hybrid Installation and Operation Manual
, the
Platinum SX Hybrid Designer
User Manual
, and the
Platinum SX Hybrid Quick Start
for more details on configuring your SX Hybrid
Module.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 179
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
PX-UCIP Configuration
Follow these steps to configure your
PX-UCIP4E1D-IBG
uncompressed video over IP module. The following procedure sets the PX-UCIP to transmit SDI to IP and receive IP to SDI.
1.
In the SDNO Controller dashboard, click the
Go to Frame
button against the frame that contains your PX-UCIP module
2.
Find the PX-UCIP module in the list of modules (under
Input Cards
), and click the
Open Module
link against it
3.
In the parameters, go to the
Control Ethernet Primary
section, and set the
IP Address Config
and the
IP Net Mask Config
parameters (the
IP Address Current
and
IP Gateway Current
are read only parameters that display the status for what's currently set)
Figure 52: Control Ethernet Primary section in
PX-UCIP in the SDNO Controller UI
4.
Set
IP Config Enable
to
Yes
to save the IP Address
Note that while you can set the IP Address from the PX-UCIP module UI itself, the first time you do it, you need to do it from here. Wait about 20 seconds for changes to take effect after setting IP config Enable to Yes.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 180
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
5.
Go to the root level (click on
Slot <Number> PX-UCIP4E1D-IBG
) and click
Open/Download
under
Primary Web Link
. This launches the PX-UCIP module UI.
Figure 53: Link to the standalone
PX-UCIP
UI from the
SDNO Controller
UI
Note: The following steps are not sequential, you can do them in any order.
6.
Go to
IP WAN A
, click
Show Table
, set at least one of the interfaces; set the
IP Address
,
Subnet
Mask
, and
VLAN IDs
. If you're setting more than one interface, from subsequent interfaces, change the VLAN ID first and then set the IP address.
Figure 54: IP WAN Menu in the
PX-UCIP
UI
7.
Go to the IP
Transmitter A.
In the
Transmit Interface
, select
Primary Only
or
Primary + Secondary
depending on whether you're using Seamless Protection.
Figure 55: IP Transmitter Menu in the
PX-UCIP
UI
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 181
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
8.
Click
Show Table
, set the
Max Transmission Rate
for each interface.
Module Specific Configuration
Figure 56: Setting the Transmission Rate in the
PX-UCIP
UI
Note:
Since there are up to four SDI inputs per Link on the PX-UCIP module, it is possible for the video bandwidth to exceed the 10G Ethernet bandwidth if all four IP Transmitter channels are enabled and configured for 3G: 3.0 Gbps.
To prevent this from occurring, the Maximum Transmission Rate parameter makes it possible to set the maximum bandwidth allowed for each SDI input. The total SDI bandwidth for all four SDI inputs must not exceed 9 Gbits per second (Gb/s). If the transmission rate detected for an SDI input is greater than the selected Maximum Transmission Rate, this channel is automatically disabled to prevent corrupting the other IP Transmitter channels.
9.
Go to
IP WAN A,
click
Show Table
, set IP Addresses and VLAN IDs
Figure 57: Setting IP Addresses and VLAN IDs in the IP WAN Menu in the
PX-UCIP
UI
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 182
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
10.
Go to
IP Receiver A,
click
Show Table
, set the
Max Receive Rate
and
WAN Select.
See Note about
Max Receive Rate (on page 183).
Figure 58: Setting the Max Receive Rate and selecting the WAN in the IP Receiver Menu in the
PX-UCIP
UI
11.
If using, repeat the same steps for
IP WAN B
,
IP Receiver B
,
IP Transmitter B
.
Note about Max Receive Rate
The maximum bandwidth of a 10 GBPS Ethernet (SFP+) port is 10.3125 Gbps.
If:
The
Max Receive Rate
on the four IP Receiver A channels are configured as follows: 3G, 3G, 3G, SD
And the bandwidth for the fourth IP Receiver channel changes from
SD
to
HD
or
3G
, at the video source
This will cause the 10G Ethernet bandwidth to be exceeded and will cause Ethernet packets to be randomly dropped. When Ethernet packets are dropped, all four IP Receiver channels will be missing packets and this will cause the video output on the IP-to-SDI path to break-up, freeze or go to video black. It is your responsibility to ensure that the IP Receivers don’t ‘over subscribe’ the 10G Ethernet bandwidth.
Note that if oversubscribed, the
Channel Bandwidth Status
parameter shows as
Channel Disabled
, however data packets are still transmitted over the network.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 183
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Selenio MCP Module Configuration
Setting up the Selenio Uncompressed Video‐Over‐IP (UCIP)
Module
Access your Selenio UCIP Module via the Selenio Controller UI and do the following:
UCIP Module Configuration on the Transmit Side
1.
Go to the
Module
>
General
menu
2.
Set the
Module I/O Configuration
as required, for example, set it to
4 SDI In, 4 SDI Out
3.
Set the
CTR SDI Out Select
to
EXT SDI 1
to confirm signal presence on the Streaming tab
IP WAN Configuration
1.
In
IP WAN
>
General
, click
Show Table
under IP Wan
2.
Select
IP WAN 1
and enter the appropriate information
3.
Click
Confirm VLAN Values
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 184
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
4.
Go back to the
IP WAN
>
General
tab and verify that the Primary and Secondary packets are increasing
SDI to IP Configuration
Go to IP Transmitter, and set the Transmit Interface to
Primary
or
Primary + Secondary
.
The Transmit Interface refers to the one (or two) 10 Gbe SFPs on the Selenio UCIP module. The external data ports on the Selenio frame are not used for this module.
Primary + Secondary sends IP packets out both interfaces simultaneously, allowing seamless protection
(SMPTE 2022-7 to be enabled)
IP Transmitter Configuration
1.
In the
IP Transmitter
tab, click Show Table under IP Transmitter
2.
Ensure
IP Transmitter Enable
is
On
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 185
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
3.
Set
Max Transmission Rate
to HD 1.5 Gbps for HD or 270 Mbps for SD
Module Specific Configuration
4.
Select
IP Wan Primary
from the drop down menu on the right
5.
Enter the
Destination IP Address
(Multicast), and
Port
When entering a Destination IP, it is recommended you enter an address that resembles the IP WAN address. For example, 239.95.15.1 and 239.95.15.2. This make it easier to troubleshoot/verify the
UCIPs are actually switching correctly (where the stream is being sent from).
6.
Under
WAN Select
, select the appropriate WAN Interface (
WAN 1
).
7.
Ensure the
IP WAN Address
matches the value from WAN Configuration section.
8.
If required, follow the same steps for the
IP WAN Secondary
9.
Select
FEC
from the from the drop down menu on the right
10.
Set
FEC level
to the appropriate value.
Note that if the Transmit Interface is set to Primary + Secondary, FEC level defaults to None and cannot be adjusted. SMPTE 2022-7 and -5 are not active simultaneously.
UCIP Module Configuration on the Receive Side
1.
Go to the
Module
>
General
menu
2.
Set the
Module I/O Configuration
as required, for example, set it to
4 SDI In, 4 SDI Out
3.
Set the
CTR SDI Out Select
to
IP Receiver
to confirm signal presence on the Streaming tab
IP Wan Configuration (Receive)
1.
In
IP WAN
>
General
, click
Show Table
under IP Wan
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 186
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
2.
Select
IP WAN 1
and enter the appropriate information. Click
Confirm VLAN values
to save.
SDI to IP Configuration (Receive)
Go to
IP Receiver
, and make the necessary settings based on your network. Some things to consider:
Packet Delay Variation
: Measures difference in the one-way delay of selected packets. Maximum 50 msec variation.
Seamless Max Path Diff
: Measures difference in arrival time of duplicate packets through diverse network paths. Maximum 150 msec differential.
Minimum Required Playout Delay
: Calculated based on the above values to represent minimum playout delay needed to process incoming packets.
Playout Delay
: Value must be set to at least Minimum Required, otherwise a Playout Delay Too Low error is displayed on Dashboard.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 187
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Setting up the Selenio JPEG 2000 (J2K) Module
Access your Selenio JPEG2000 Module via the Selenio Controller UI and do the following:
Selenio JPEG Encoder Setup
IP LAN Configuration
1.
Go to
Module
>
IP LAN
>
LAN A
>
Primary Data Ethernet
2.
In the IP Address field, the IP Address entered should have a VLAN associated with it on the data switch. Set the
IP Gateway
to the IP address on the switch pertaining to this VLAN.
3.
Click
Apply
to make changes.
4.
Repeat for
Secondary Data Ethernet
(if applicable)
5.
Go to
Module
>
Encoder 1
>
IP Encapsulation
Under
Primary IP Address
, enter an appropriate multicast address; enter
Primary Port
.
Do the same for
Secondary IP Address
(if applicable)
Assign a
Primary LAN
(LAN A in this example), that matches the LAN ID used in the Configuration
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 188
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Note: SDNO Controller does not manipulate the Multicast IP addresses entered into the module.
They remain static on the module and the system routes addresses to appropriate destination.
Selenio JPEG Decoder Setup
The Selenio J2K Decoder module requires the following to be configured for use in SDNO Controller:
LAN Address
(SDNO Controller requires one; you can have up to four). Supports Primary and Backup
Primary Source
(for TS Input)
Primary LAN
(for Primary and Secondary IP TS Input)
IP Lan Configuration
1.
Go to
Module
>
IP LAN
>
LAN A
>
Primary Data Ethernet
2.
Enter the
IP Address.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 189
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
3.
The IP Address entered should have a VLAN associated with it on the data switch. Set the
IP
Gateway
to the IP address on the switch pertaining to this VLAN
4.
Click
Apply
to make changes.
5.
Repeat for
Secondary Data Ethernet
(if applicable)
6.
Go to
Module
>
TS Input
and set
Primary Source
to
EXT IP
.
Under
Primary IP
and
Secondary IP
(if redundancy is available), enter in an appropriate multicast address, as well as Port
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 190
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Assign a
Primary LAN
(LAN A in this example), that matches the LAN ID selected in the IP LAN configuration.
Note: The Selenio JPEG2000 Decoder's Primary (and Secondary) IP Group and Port are values that
SDNO Controller can change.
Repeat for
Secondary Data Ethernet
(if applicable) and Secondary IP Address.
Setting up the Selenio MDX Module
Access your Selenio UCIP Module via the Selenio Controller UI and do the following:
MDX Module Configuration on the Receive Side
Note: Input channels within each Multiplexer are controlled as destinations in SDNO Controller. The actual multiplexer itself and the output of the multiplexer module cannot be controlled by SDNO
Controller.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 191
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
1.
Go to
IP LANs
. Set up the Primary and Secondary IP Addresses
Module Specific Configuration
2.
Go to
Multiplexer Functions > Input Channels
. For each channel, set the
Source Type
to
EXT-IP-CBR
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 192
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
3.
Go to
IP Source
. On each source, if the data port on the Selenio MCP is connected to an access port, set the
Primary/Secondary VLAN ID
to
0.
If connected to a trunk port, set to the appropriate VLAN
ID.
Note: The channel ID used in the SDNO Controller SDNO Database Editor needs to match the channel ID on the MDX Module.
Figure 59: Channel ID when defining destinations in the SDNO Database Editor
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 193
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Figure 60: Channel ID on the Mux Module
4.
Go to
Multiplexer Functions.
Set the
Output Rate
to the total rate of the input channels.
This multiplexer can now function as a SDNO Controller Destination.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 194
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
MDX Module Configuration on the Transmit Side
Note: The input of the Demultiplexer cannot be controlled by SDNO Controller.
1.
Go to
IP source
, set the
Primary/Secondary VLAN ID
and
Port
2.
Go to
Output Channels
, set up your channels
Note: The output channels are used by the SDNO Controller. The channel ID used in the SDNO
Controller Database Editor needs to match the channel ID on the MDX Module when defining sources.
Figure 61: Channel IDs when defining sources in the SDNO Database Editor
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 195
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
Figure 62: Channel ID on the Mux Module
3.
Go to
IP Destinations
, set up the Primary and Secondary IP Addresses.
This demultiplexer can now function as an SDNO Source.
Setting up the Selenio Encoder/Decoder Module
Access your Selenio Encoder/Decoder Modules via the Selenio Controller UI and do the following:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 196
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Selenio Encoder Setup
Module Specific Configuration
IP LAN Configuration
Note: the SDNO Controller does not change any values set in the Selenio Encoder module. It only routes the multicast group to the necessary destination.
1.
Go to
Module
>
IP LANs
>
Primary Data IP LAN
2.
In the
IP Address
field, the IP Address entered should have a VLAN associated with it on the data switch.
3.
Set the
IP Gateway
to the IP address on the switch pertaining to the VLAN the module is on.
4.
Set the
VLAN ID
5.
Click
Apply
to make changes
6.
Go to
Module
>
IP Encapsulation
>
Main Program IP
7.
Under
Primary IP Address
, enter an appropriate multicast address; enter
Primary Port
. Do the same for Secondary (if applicable).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 197
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Module Specific Configuration
8.
Under
Transmit Interface
, it is recommended you select
Both
, especially if a redundant network is being used (Primary and Secondary)
Note: The SDNO Controller does not monitor Selenio data connection status (that is, which data link is active, Primary or Secondary) so if Transmit Interface is not set to Both, the SDNO Controller cannot determine the switch to communicate with based on the data connection status.
Selenio Decoder Setup
IP LAN Configuration
1.
Go to
Module
>
TS Input
2.
Set
Primary Source
to
EXT IP
3.
Go to
Module
>
Control
>
IP Lan
>
Primary Data Ethernet
4.
Set
IP Address
and
Gateway
Set the IP Gateway to the IP address on the switch pertaining to the VLAN the module is on.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 198
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
5.
Set the
VLAN ID
6.
Click
Apply
Module Specific Configuration
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 199
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
System Integration
This section contains the following:
Sony's IP Live System Manager (on page 201 )
LAWO V__link 4 - Video-Over-IP Stage Box (on page 210)
Interfacing with a Third Party Router (on page 211)
Interfacing with a Legacy Router (on page 215)
Connecting 2 Independent IP3 Systems with Tielines (on page 222)
Adding a Second IP3 Routing System to an existing Routing System (on page 228)
System Integration
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 200
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Sony's IP Live System Manager
SDNO Controller now supports integration of Sony's IP Live System Manager into the SDNO Controller system. The IP Live System Manager is the control system for Sony's IP Live Production System.
The steps to integrate the two systems involve the following:
Note: Presuming a dual (primary and secondary/backup) Sony IP Live Manager system setup, it is recommended that you connect the Primary Live System Manager to SDNO Controller ENET 1, and the
Secondary Live System manager to SDNO Controller ENET2.
1.
Add the SDNO Controller to Sony's IP Live System Manager's
External Routing System List
2.
Add Sony's IP Live System Manager to the SDNO Controller
Hardware Foundry
3.
Establish connection between the two systems. Ensure you can ping the Sony Live Manager system from the SDNO Controller and vice versa.
4.
Create a Routing system in Magellan CCS Navigator by polling for the SDNO Controller which pulls
Sony's IP Live System Manager into the routing system
5.
Import sources/destinations from Sony's database into the Sony view of the SDNO Controller database in the routing system
6.
Optionally create tielines across the two systems
7.
Publish the routing system to control panels and devices
8.
Control the Sony System routing (sources and destinations) from hardware control panels such as
Magellan™ Router Control Panels
Adding the SDNO Controller to Sony's IP Live System Manager
1.
In the IP Live System Manager, go to
Settings > External Routing System
. Click the
Create
button.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 201
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
2.
Enter the
IP Address
and
Port
of your SDNO Controller, provide a
Name
and Description. Click the
Save
button.
3.
Once you Save, the option to import the router settings file will be enabled. Click the
Import
button and input this file.
4.
You will see a message confirming successful creation of the new external routing system.
5.
The dashboard will reflect the newly added system but the status will be inactive. The IP Live System
Manager now needs to be added into the SDNO Controller system in order for the connection to be established.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 202
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
6.
Once you add the IP Live System Manager to the SDNO Controller system (see Adding Sony's IP Live
System Manager to the SDNO Controller (on page 203)), refresh the IP Live System Manager
dashboard and the SDNO Controller status should show as green and active.
Adding Sony's IP Live System Manager to the SDNO Controller
Go to the SDNO Controller Web UI and do the following:
1.
Click
Configure System
on the toolbar at the top
2.
Click the
Hardware Foundry
icon to define or modify your system hardware configuration.
3.
Click the
Add Devices
button to add a new frame to the system.
4.
Provide a unique
Name
for your IP Live System Manager device
5.
Select
Sony
in the
Vendor
drop down. The Protocol by default is
IP Live
.
6.
The
Port
number is pre-populated with 11700. Leave this as is for the first Sony device you add. If you need to add another one, change the port number accordingly, for example, 11701.
Ensure that this number matches what you provided while adding the SDNO Controller to the IP Live
System Manager
7.
Enter the main
IP Address
of the IP Live System Manager in
LSM IP Address 1
8.
If you have a redundant IP Live System Manager, enter the secondary IP Address in
LSM IP Address
2
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 203
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
9.
Click
Add
System Integration
IP Live System Manager in the SDNO Controller Dashboard
Once you add the IP Live System Manager via the Hardware Foundry, go back to the main SDNO
Controller dashboard and you should see it listed under the
Pass-through and Third-Party Frames
section.
The
LSM IP Address 1/2
that you configured in the Hardware Foundry will be displayed as part of the frame details. If you provided only IP Address 1,
LSM IP 2
will show as 0.0.0.0. LEDs are displayed against the IP addresses to indicate status:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 204
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Indicates that IP address 1/2 is active
Indicates that IP address 1/2 is inactive
Indicates that IP address 1/2 has not been defined
System Integration
Note that if you provide both
LSM IP Address 1
and
LSM IP Address 2
when adding the Sony device to the Hardware Foundry, both of these connect to the SDNO Controller in parallel and maintain that connection.
If you click the
Go to Frame
button against Sony's IP Live System Manager, you will see its details displayed. There are 3 read only parameters -
Name
,
Type
, and
Version
.
SDNO Database and Routing
The next step is to look at your IP Live System Manager (Sony) database in the Database Foundry.
Creating a Routing System in Navigator
1.
Poll for the SDNO Controller by right clicking the
Routers
folder and selecting
Create > Routing
System
2.
Provide a
Name
for the Routing System, select the
Perform System Poll
checkbox, and enter the
IP
Address
of the SDNO Controller
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 205
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
3.
Once discovery is complete, you will see the IP3/SDNO Routing system with Sony IP Live as one of the components.
IP Live System Manager Database in the SDNO Database Editor
1.
Double click
SDNO Routing System
under
Routers
to launch the
Database Editor
. The
Selected View
drop down allows you to switch between IP3, Sony, and any other databases.
2.
Select
Sony
for a view of the Sony database.
3.
Click the
Query Database
button to pull in sources and destinations from the IP Live System
Manager
4.
If the
Level Mappings
dialog is displayed, the
Level
drop down list provides an option to re-map the
Sony Live System Manager matrix to the appropriate level in the IP3 Database. Click
OK
to confirm the level mapping setting.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 206
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
The
Level Mappings
dialog will only be displayed if there are new levels detected after the query. If no new levels are detected, the dialog will not be displayed, but the user can access it through the
Level Mapping button on the toolbar.
5.
The database is then populated with the sources and destinations.
Note:
IP Live System Manager devices in the SDNO Controller system are intended for CONTROL purposes only. You cannot add or edit any of the IP Live System Manager Sources and Destinations - you cannot make changes to Source/Destination Names, Indexes, etc., only editing of Long Names,
Alias Names, Description, and Levels are permitted. You can delete any of the sources/destinations by selecting and clicking the Remove button (see Step 6).
If database changes or updates to Sony's IP Live System Manager are required, go to Sony's IP Live
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 207
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
System Manager and make the changes there. Once those changes are published/downloaded to the device, repeat the steps above to re-import the updated device's database into the overall IP3 router database again.
6.
Optional
:
When you initially bring in your IP Live System Manager sources/destinations, you can optionally create a backup by clicking More > Export and saving to a zip file. In case you delete of of the sources/destinations and want to revert, you can simply re-import in the zip file (More > Import).
7.
Close the SDNO Database Editor.
IP Live System Manager in the DBEditor
1.
Launch the DBEditor view by double clicking the System Name under Control Views. The DBEditor shows you a consolidated view of all the elements in your database, whether IP3, or IP Live
Manager, or other third party ones.
2.
You will see the IP Live Manager sources/destinations displayed in a bright green, as compared to
IP3 and other sources/destinations which show in a lighter green. This distinction is because of the
Navigator fix you applied earlier (see Updating Navigator 5.4.1). Source/Destination Names and
Numbers are not editable.
3.
Click Publish to synchronize with the routing system.
Creating Tielines
You can also create tielines across sources/destinations in the IP Live Manager System and the IP3 one.
This is done via the DBEditor. To create tielines:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 208
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
1.
Open the
DBEditor
if not already open
System Integration
2.
In the toolbar at the top, click the
Show Tielines Column
icon
3.
You can than make tielines across systems, for example from source in the IP Live Manager System to a destination in the IP3 system.
4.
Once finished, go to the
Tielines
tab to see all defined tielines
5.
Save
and
Publish.
You can now use the Magellan™ Router Control Panel or the Router Soft Panel (see Router Soft Panel
(on page 273)) to route Sony sources and destinations.
Note: In an IP3/Sony blended system, so long as the IP3 control system is the exclusive user interface,
Lock and Protect functionality is supported via Magellan Router Control Panels and IP3 HTML Panels.
Note that Lock/Protect status is reset if the Controller is rebooted, restarted, or if it fails over.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 209
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
In the event that a Sony control interface is used, all locks and protects are bypassed and no longer provide the intended function.
LAWO V__link 4 - Video-Over-IP Stage Box
SDNO Controller now supports integrating with the LAWO V__link 4 Video-Over-IP Stage Box as a source or destination.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 210
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Interfacing with a Third Party Router
Your SDNO Controller is mainly intended for control of your IP3 router. Limited support for third party routers is also provided. SDNO Controller version 1.3 supports the addition of a Grass Valley router into your routing system. With some minimal GUI configuration, you can control sources and destinations across one or more Imagine Communications routers and others that support the Grass Valley SMS7000 protocol. Utilizing tie lines, sources and destinations can be shared across these routers.
Note: You can also include legacy Imagine Communications routers in your system for control (see
Interfacing with a Legacy Router (on page 215)).
Steps to Configuring a Third Party Router
1.
In the SDNO Controller UI, add the third party (Grass Valley) router as a routing device (in addition to your IP3 Router frame(s). See Adding a Third Party Router Device.
2.
In
Navigator
, if you do not have an existing configuration, discover the SDNO Controller that contains your IP3 routing devices and third party router
3.
In
Navigator,
run the
DBEditor
a.
If you do not see sources and destinations, import them from the SDNO Controller device by doing the following: i.
Click the
Import Database Names
icon (in the toolbar at the top) ii.
Then select the
Import from Device
option iii.
Provide the IP Address of the router to import from
Note: If you have an existing database, you may not need to import from device.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 211
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration b.
Sources and Destinations from the current router configuration will be displayed in the
Sources
and
Destinations
tab c.
Save
and
Close
4.
In
Navigator,
run the
SDNO Database Editor
a.
In the Database Editor displayed, select the name of of your third party router in the
Selected
View
drop down list at the top . b.
Click the
Query Database
button. This retrieves sources and destinations from the database c.
A Level Mappings dialog will be displayed. This dialog allows you to map the levels for your 3rd party router to work within your SDNO Controller system. It does not change the levels or
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 212
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration configuration of the native Grass Valley control system. Click in the Level column to assign the remapped levels as necessary.
Note: The SDNO router database handles Video at level 0 and Audio at levels 1and above.When configuring your third party router, it is essential to take note of this and configure levels accordingly. d.
Duplicate source/destination names (if any) will be highlighted. Click
OK
.
5.
Re-open
DBEditor
to synchronize
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 213
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Note the difference in the shade of green for GVG versus IP3 Sources. This allows you to differentiate the two types. Any duplicate Source/Destination names will be flagged in yellow in the
DBEditor
Note: Any changes to the Grass Valley Router Source/Destination names will have to be done on the
Grass Valley router. Then re-import sources/destinations into the DBEditor.
6.
Click
Publish
in the
DBEditor
window to transfer to the SDNO Controller and other devices
Handling Duplicate Source/Destination Names
Duplicates are allowed in the system. When you have a third party router and an IP3 router in your system, duplicates are resolved by using the local (to the router) reference. This is useful for tie-line configurations where a source may be present on both the local and other routers. It forces the local source to be used without utilizing a tie line resource.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 214
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Interfacing with a Legacy Router
This section covers the required configuration if you intend for your IP3 router to interface with a legacy router (for example, Platinum, Panacea, Integrator, etc).
From a configuration standpoint, there are different ways in which you can accomplish integration with a legacy router.
You can have sources/destinations from IP3 and non-IP3 be on separate levels
(Note that in this case, you cannot have tielines in the system).
You can have sources/destinations from IP3 and non-IP3 share the same levels and route together.
You can add the legacy router sources/destinations into an existing SDNO database.
You can use the Offset functionality in Navigator and offset the indices.
IP3 and non-IP3 on different levels
This example explains how we add in an additional Level for the Legacy Router matrix. So you have your
IP3 sources/destinations on a certain level or levels, and then create an additional level for the Legacy
Router. Note that this works for only one additional level, meaning only one legacy router can be configured to interface with the IP3 router at this time.
As an example, create an
HD Video
device type, and configure
HD Video
on
Level 0
. So in this case, Level
0 is for the IP3 and later we will create another level (say Level 1) for the Legacy router.
Note: Level 0 and Level 1 is just an example. You can choose any 2 levels, as appropriate to your routing system.
Presuming you have your IP3 matrix set up, follow these steps:
Create a Device Type
1.
Launch
Navigator
and open the
DBEditor
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 215
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
2.
Use the Wizard to create a device type, for example,
HD Video
.
System Integration
3.
Click Next in the
Connection Types
dialog.
4.
In the
Level Selection
dialog box, select
Level 0
as the starting level and Click
Next.
5.
In the
Configure Connection Types
dialog, click Next.
6.
In the
Device Type Details
dialog, click
Finish
.
7.
Save the
DBEditor
database and close it.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 216
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Add Sources/Destinations in SDNO Database Editor
1.
Open the
SDNO Database Editor
2.
Click the
Add
button to add your
Sources
.
Select the device type (
HD Video
) as created earlier.
Ensure the
Slot
corresponds to the Slot that contains your card.
System Integration
Once complete, you will see a video and an audio matrix in the selected Slot.
3.
Repeat these steps to add your
Destinations
.
4.
Save
the database.
Publish to DBEditor
1.
Open
DB Editor
in
Navigator.
Go to the Physical View
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 217
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
2.
You should see something similar to the following with your IP3 sources under level 0
3.
Now add in another level for your legacy router, by going into the Levels tab in DBEditor and selecting Add Level.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 218
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
Go back to the Sources tab and you will see the new level that you added
System Integration
5.
Configure your legacy router, define your matrix and then assign indices in Level 1
See the Magellan CCS Navigator documentation for details on defining the matrix for your legacy router.
6.
Save
and
Publish
the DBEditor database to the router/control panels.
IP3 and non-IP3 on the same level
1.
Create at least one device type in the
DB Editor
.
2.
Add in your IP3 sources and destinations via the
SDNO Database Editor
.
3.
Go back to the
DB Editor
. Switch to the Physical View
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 219
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
Physically delete the Platinum specific sources (highlighted in yellow)
System Integration
5.
At the bottom, you will see the sources that have both IP3 and non-IP3.
6.
Switch to the Destinations tab and repeat.
7.
Save.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 220
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Using Offsets
System Integration
You can also use the
Offset
functionality in Navigator, and offset your IP3 router. Note that the offset needs to be higher than the maximum index in your Legacy database. For example, if the sources go to
1095, go to 1096 so there is no overlap.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 221
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Connecting 2 Independent IP3 Systems with
Tielines
This example explains how you can maintain two completely independent IP3 systems, but still make some sources/destinations available across both, by creating tielines across systems.
This example describes a use case where:
System 1
has its own Controller, a couple of IP3 Frames, a third party Router, (and optionally, some
SDN devices)
System 2
also has its own Controller, an IP3 Frame, and a third party router.
System 1
System 2
Tielines
IP3 Controller 1
IP3 Controller 2
PX-RES
PX-RES
PX-RES
Third
Party
Router
SDN
Devices
IP3 Frame C
IP3 Frame A
IP3 Frame B
Note: A tieline is a logical connection between one or more sources or destinations, allowing the sources/destinations from one frame to be available to another frame(s). Tielines help you expand the size of your system, make resources available to several users at the same time, or to restrict remote user access to available sources.
Setting up System 1
Note: A System in this context refers to an SDNO Controller and all the Imagine Communications and third party frames that have been added to its control system.
1.
Set up
SDNO Controller 1
via its web UI by adding in the IP3/other router/third party frames that will comprise the system (Hardware Foundry)
2.
Create a
Routing system
and poll using the
SDNO Controller 1
IP Address
3.
This Controller and the frames it controls (along with tielines across frames within the system) is an
"independent" system with connections within the system.
4.
Next, export the Database.
Note: If you intend to pull this system into a common routing system with other systems, you need to export the Database via the SDNO Database Editor.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 222
Third
Party
Router
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual a.
Go the the SDNO Database Editor. Click
More
>
Export
System Integration b.
Provide a name for the exported (zip) file.
Setting up System 2
Ensure you export the System 2 Database via the SDNO Database Editor, similar to System 1.
Pulling Both Systems into a Single Routing System
Now each of the Controllers and the frames they control are "independent" systems with connections within the system, but not across systems. The first step to creating connections
across
systems is to pull both
IP3 systems
into a
single Routing system
. This is done in Navigator.
Designate one of the SDNO Controllers as Server
Follow these steps to designate one of the SDNO Controllers as the
Server
(the other is automatically the
Client
)
1.
Launch the Web UI of the SDNO Controller that you want to designate as
Client
2.
Go to
Configure System
>
Manage SDNO Controller Settings
>
Router Settings
3.
Click the
Set
box against
Server
under
IP
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 223
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
4.
Set the IP Address of the other SDNO Controller (the one you want to designate as
Server
)
5.
Click
Apply
Create a New Routing System (System 3)
Launch Navigator and follow these steps:
1.
Create a new Routing system (recommended instead of trying to update or add to an existing routing system)
2.
Poll using the IP Address of the SDNO Controller designated as
Server
3.
Once complete, you should see both SDNO Controllers along with their frames in a single routing system
Note that each of these systems has their own database, which can be launched by double clicking
IP3
Routing System
, which then launches that system's Database Foundry within the IP3 Controller UI.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 224
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Import the Database from the Server SDNO Controller System
System Integration
1.
Go into the
SDNO Database Editor
of the SDNO Controller designated as
Server
.
2.
Double click the relevant
SDNO Controller
(based on the IP Address) under
SDNO Routing system.
This launches the SDNO Controller's web UI and takes you to the
Database Foundry
.
3.
Import in the previously exported database from this system.
Import the Database from the Client SDNO Controller System
1.
Go into the
SDNO Database Editor
of the SDNO Controller designated as
Client
.
2.
Double click the relevant
SDNO Controller
(based on the IP Address) under
SDNO Routing system.
This launches the SDNO Controller's web UI and takes you to the
Database Foundry
.
3.
Import in the previously exported database from this system.
Create Offsets in DBEditor
The next step is to create offsets in the DB Editor, to handle any overlapping Sources/Destinations.
1.
Launch
DB Editor
(under
Control Views
). You will see the "
Server
" sources/destinations at the top, and the "
Client
" sources/destinations below that (in a different shade of green).
2.
Click the
IP3 Matrix Settings
button and create the offsets on the "
Client
" in the
Source Offset
and
Destination Offset
fields.
The Offset you enter here should be calculated depending on the number of Sources/Destinations on the "Server", this is how much you need to offset by. You may want to include a buffer, additionally.
Create Tielines across both Systems or Frames in the System
In order to make tielines
across both systems
or
frames in the system
:
1.
Run the
DB Editor
which pulls sources and destinations from both systems into a single view.
2.
Define tielines as required across sources/destinations in devices in both systems.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 225
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Do this by first clicking the
Show Tielines Column
button to show the Tielines column in the
Sources/Destinations
tab, and then directly creating tielines for a given source/destination by selecting a source/destination in the Tielines column drop down list.
OR
By going to the
Tielines tab
and clicking the
Add Tielines
button
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 226
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
The Tielines Editor will reflect any defined tielines.
System Integration
3.
Once complete, publish the database and download the tielines to one of the SDNO Controllers - the one that will serve as your Tieline Controller.
4.
Delete any residual tieline configuration from the other IP3 Routing System NOT designated to serve as the Tieline Controller.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 227
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Adding a Second IP3 Routing System to an existing Routing System
This example describes a use case where you have an
existing IP3 Routing System
, and you want to add in a
second IP3 Routing System
to create a
larger overall Routing System
consisting of
2 separate IP3
Routing Systems
.
Existing IP3 Routing System (System 1)
It is presumed that System 1 is already set up - this is a routing system created in Navigator, that contains an IP3 Routing System, and potentially other elements.
New IP3 Routing System (System 2)
The new IP3 Routing System is a standalone system in its own right, comprised of a Primary and/or
Secondary SDNO Controller pair, one or more Platinum or Platinum IP3 frames, and any number of control panels.
Since we intend to merge it into the existing Routing System (System 1), we need to point this
NEW
IP3
Routing System to the
Existing
IP3 Routing System.
Point System 2 to System 1
1.
Launch the SDNO Controller Web UI for System 2
2.
Click
Configure System > Manage SDNO Controller Settings
3.
Under
IP > Server
, click the
Set
button
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 228
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
4.
In the
Set Server IP
dialog, enter the
External
IP Address
of the
Active SDNO Controller
in
System 1
.
Click
Apply
and then
Close
.
Poll System 1 to discover the newly added IP3 Routing System
1.
Right-click on the
Existing Routing System
node in Navigator and select
Poll
.
This process will pull in the
New IP3 Routing System
into the overall "
System 1
" Routing System since the IP Server connection joining the two has been established.
2.
Once complete, you will see 2
IP3 Routing Systems
under your Routing System. Note that it is still a single routing system.
And if each
IP3 Routing System
is expanded, you will see all discovered devices under each respective IP3 Routing System.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 229
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
NOTE: Any devices (frames/modules/panels) found to be OFFLINE during the Poll process will not be displayed.
Define Offsets
1.
Launch the routing system's
DB Editor
(by double clicking the element under
Control Views
)
2.
Click the
IP3 Matrix Settings
button
3.
Enter
Source Offsets
and
Destination Offsets
for
System 2 (IP3 Controller 2)
.
Rather than an exact offset, you may want to leave a buffer, depending on your requirements and future expansion plans for System 1.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 230
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual System Integration
Note: Offsets are defined since the newly added Sources/Destinations may overlap existing XY
Indexes.
Add Sources/Destinations for System 2
1.
From Navigator, in your Routing System, double click the newly discovered '
IP3 Routing System
' node to launch the
IP3 Database Editor
for
System 2
.
2.
Add
Sources
and
Destinations
.
Save
.
Handling Overlapping Sources/Destinations
1.
Once Offsets have been defined and Sources/Destinations added, review to check if there are still any overlapping Sources/Destinations.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 231
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
2.
Modify
Source Offsets
and
Destination Offsets
if required to adjust.
System Integration
Define Tielines
1.
Define Tielines as required.
2.
Once complete, publish the database and download the tielines to one of the SDNO Controllers - the one that will serve as your Tieline Controller.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 232
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
© 2016 Imagine Communications Corp.
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 6
Subnet 5
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 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
© 2016 Imagine Communications Corp.
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.
1.
In the Controller GUI, click the
Configure System
link in the toolbar at the top.
2.
In the SDNO Routing System Configuration that is displayed, click the
Manage SDNO Controller
Settings
icon.
3.
Click the
Network & Redundancy
button.
4.
Click the
Add Redundant Controller
button.
5.
Enter the
IP Address
of the Secondary SDNO Controller and click
Apply
.
6.
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/
© 2016 Imagine Communications Corp.
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
.
© 2016 Imagine Communications Corp.
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
© 2016 Imagine Communications Corp.
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
or
Disabled
.
© 2016 Imagine Communications Corp.
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
or
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
Active
Active
Standby
Standby
Standby
Secondary
Standby
Standby
Standby
Active
Active
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
Secondary Controller takes over
Secondary Controller takes over
Primary Controller takes over
Primary Controller takes over
Primary Controller takes over
© 2016 Imagine Communications Corp.
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
© 2016 Imagine Communications Corp.
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
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 241
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Tools and Utilities
SDNO Controller Services
Verify that the IP3 system services started up correctly.
There are NINE Services that run on the SDNO Controller machine:
IP3 CCSP (CCSP Proxy Services)
IP3 Controller Manager
IP3 IP Virtual Router
IP3 Panel Manager
IP3 Protocol Service
IP3 PTP V2 (see Time Synchronization (on page 243))
IP3 Router Control
IP3 System Manager
IP3 Web Server
Tools and Utilities
Figure 64: SDNO Controller Services via Windows Services
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 242
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
Figure 65: Controller Services via SDNO Status
Time Synchronization
Note:
There are two possible SDNO Controller configurations: Single SDNO Controller and a redundant configuration consisting of a Primary and Secondary SDNO Controller.
The PTP V2 Service performs time synchronization between the Primary SDNO Controller, the Secondary
SDNO Controller, and the PX-RES (IP3 Frame). This system level service automatically initiates on startup or restarting, and is deployed in the form of a Windows Service.
PTP V2
syncs time between the Primary and Secondary SDNO Controller as well as time between the
Primary SDNO Controller and the PX-RES (IP3 Frame). It is bound to ENET 5/6.
The Master clock (master time reference) is either the Primary or Secondary SDNO Controller, but never the PX-RES; the PX-RES is always a Slave. The Slave SDNO Controller (Primary or Secondary) that is not the Master syncs with the master every second or so. If at any time it finds there is no response from the
Master, that SDNO Controller then takes over as the Master. The Master Clock arbitrates through selfadministration and cannot be set/fixed manually.
Note:
The IP3 Time Sync Status (see "SDNO Time Sync Status" on page 245) shortcut provides time
synchronization status and Controller states (client, server, unknown).
The Grandmaster clock is elected through a Best Master Clock (BMC) algorithm that uses network latency and other measurement statistics to determine which clock is most suitable as a master. If either
Primary or Secondary controller is physically removed, or disconnected from the network, then the remaining one (that is still connected to the PX-RES) will automatically take over as a Master. If another controller is re-connected, then it may or may not be elected as Master through BMC arbitration.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 243
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Controller Scripts
When the SDNO Controller is installed, shortcuts to some utility scripts (located in
C:\IpxController\Scripts) are created directly on the Desktop.
Tools and Utilities
Stop SDNO
Stops the SDNO Services
Start SDNO
Starts the SDNO Services
SDNO Backup
Backs up SDNO Data
SDNO Status
Provides status on all SDNO services, the Logging Server, and FileZilla and indicates if they are running. Also lists the currently active SDNO Controller (whether Primary or Secondary) and what operating mode it is in (Active or Standby).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 244
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Time Sync Status
Tools and Utilities
SDNO Redundancy Management
Utility to handle redundancy
Backup and Restore Tool
The SDNO Backup and Restore tool enables you to backup or restore your SDNO Controller database.
Running the Backup Function
Backup can be performed by running the SDNO Backup (on page 244) script on your SDNO Controller
desktop. The backup procedure creates a zip file, with all the data on the SDNO Controller.
Note: For a full system backup, you need to back up both the SDNO Controller and Magellan CCS
Navigator. Use the Navigator
Backup and Restore Utility
to back up Navigator.
Run the backup utility (C:\IPXController\Backup\Backup.exe) with the following arguments:
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 245
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Backup [-h] source destination [-r]
Where:
Parameter
-h
Description
Help on the various options available
source
The SDNO Controller data directory
destination
The path of the output zip file
-r
Includes redundancy settings
Tools and Utilities
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 246
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Restoring a Backup
Tools and Utilities
You can restore a backup by going to the
Restore
folder in your SDNO Controller data directory, for example,
C:\IPXController\Restore
Run the Restore utility with the following arguments:
Restore [-h] backup-file [-r]
Where:
Parameter
-h backup-file
-r
Description
Help on the various options available
Location of the backup zip file
Restores the redundancy data
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 247
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
MIB Generator Utility
Tools and Utilities
The MIB Generator Utility runs on the SDNO Controller and enables you to generate MIBs off modules in your frame and off the Controller.
You can access the MIB Generator Utility by going to http://<SDNO Controller IP Address>/mib/
Once the utility launches, it queries all the frames currently added to the SDNO Controller.
A drop down list lets you select either the SDNO Controller itself, or one of the frames.
SDNO Controller MIBs
If you select the SDNO Controller from the drop down list, you see the associated MIBs:
SDNO Controller MIB
Router Control MIB
Infrastructure Network MIB
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 248
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Select one or click the Select All button and click
Generate
to generate the MIBs.
Tools and Utilities
Note that in case of the SDNO Controller, the MIBs are not actually generated at run time, they are part of the Controller so you're just downloading them.
You will see a dialog prompting to you to save the MIBs (in a zip) or open directly.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 249
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Controller Frame and Module MIBs
Tools and Utilities
If you select a SDNO Controller Frame from the drop down list, you see the associated frame and module MIBs. MIBs for a frame are classified by:
Frame Name
Input Modules
Output Modules
Crosspoint Module
Control Modules
Each listed module has information on the Module OID, the Version, the Product ID, and the Slots these modules are in
Select one or more modules under these categories and click
Generate
to generate the MIBs.
Note that the SDNO Controller Frame and Module MIBs are generated at run time.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 250
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
You will see a dialog prompting to you to save the MIBs (in a zip) or open directly.
Tools and Utilities
You can view the MIBs in a MIB Browser.
SNMP
The SDNO Controller supports SNMP via an SNMP agent that runs on the Controller and allows any
and receive traps (see Configure SNMP Traps (on page 255)). SNMP notifications are sent for alarms,
device state, and CCSP events.
A Protocol Service (that uses the Windows SNMP agent) translated SNMP requests to LRC routing and
CCSP control commands. The Protocol Service is an independent Windows service that communicates with the Router service using the LRC protocol and with the CCSP Service using the CCSP protocol.
Controlling your SDNO Controller using a MIB Browser
You can use any SNMP browser, for example, NuDesign Visual MIBrowser from NuDesign Technologies.
Note that Magellan CCS Navigator and the MIB browser cannot run on the PC at the same time to receive traps, since they use the same SNMP port.
In the MIB browser, you don't need to configure anything on the client side; config is done on the SDNO
Controller server side.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 251
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
SDNO Controller MIBs
Tools and Utilities
For SNMP support on the SDNO Controller , there are some generic MIBs that you must have, and some module specific MIBs.
The generic MIBs are:
InfrastructureNetwork29286.mib
SDNO_Controller.mib
Routing.mib
Download and load module specific MIBs depending on the modules you have in your frame.
For more details, see MIB Generator Utility (on page 248)
Set the SNMP ID
The SNMP ID is set from the SDNO Controller web UI configuration (
Configure System > Manage SDNO
Controller Settings > Router Settings
)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 252
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Enable SNMP
Tools and Utilities
Do the following on the primary SDNO Controller, either by remoting into it, or directly on the
SDNO Controller if a keyboard is connected to it. After completing the steps on the primary SDNO
Controller, repeat the steps on the secondary SDNO Controller, to ensure that this functionality works even in case of fallback to the Secondary.
1.
Open
Control Panel
>
Programs and Features
2.
Click
Turn Windows features on or off
3.
Select
Simple Network Management Protocol (SNMP)
The
WMI SNMP Provider
sub option is not required
4.
Click
OK
Configure SNMP
Follow these instructions to set up the SNMP service on the SDNO Controller.
1.
Open a command prompt
2.
Type
services.msc
to bring up the Computer Management Services window
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 253
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
3.
From the
Services
list, right-click
SNMP Service
and select
Properties
Tools and Utilities
4.
Select the
Security
tab
5.
Click the
Add
button and enter
Community Name
a.
Enter
public
for READ ONLY
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 254
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual b.
Enter
private
for READ WRITE
Tools and Utilities
6.
Click
Add
again and then
Apply
to save changes
Configure SNMP Traps
1.
In the SNMP Service Properties,
Traps
tab
2.
Type in the
Community Name
(for example,
public
) then click the
Add to list
button
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 255
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
3.
In the
Traps destination
section, click the
Add
button and enter the IP address(es) of the client(s) that you would like to configure to receive traps.
4.
Click
Apply
to save changes and then click
OK
to close the SNMP Service Properties dialog.
5.
In the Computer Management Services window, in the status, ensure the SNMP Service is started.
Parametric Control
All CCSP parameters are available for monitoring and control.
Read/Write parameters support SNMP
Read only parameters support SNMP
set set
and
get
Example
The following is an example on how to change a parameter value on your SDNO Controller via SNMP.
Note: Some of the screen shots in this example are specific to the NuDesign Visual MIBrowser. This is just representative; you can use any MIB browser.
1.
Open up the MIB Browser
2.
Load the three generic MIBs for the SDNO Controller - I
nfrastructureNetwork29286.mib
,
SDNO_Controller.mib
, and R
outing.mib
3.
Load your module specific MIBs
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 256
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
4.
Configure the SDNO Controller. The information you provide here should be similar to what you set on the Server side. For example, the Read Community and Write Community names must match.
5.
Configure the SNMP agent
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 257
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
6.
Now browse to the module you want to control
Tools and Utilities
7.
Go to the specific parameter and Set
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 258
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
8.
Select the Object index. Then set the Value
Tools and Utilities
9.
Execute.
The parameter change will then be made and visible in the SDNO Controller UI.
Switching
The following is supported/provided:
Support for global salvo execution
Table of all configured Sources in the database
Table of all configured Destinations in the database
Source/Destination tables provide SNMP link to CCSP device for parametric control
Destination control:
Take/Disconnect Crosspoints
Lock/Protect/Unlock Destinations
Crosspoint Status via SNMP notifications
Current lock/source status
RoutingSources Table
Column Header
INDEX routingSourceNameValue routingSourceIndexValue routingSourceCCSPOid
Description
SNMP instance (row) for Source
Source Name
Routing Index for the Destination
Provides the SNMP OID of the CCSP parametric control of
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 259
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Column Header Description
the input module routingSourceCCSPTableIndex Provides the SNMP Table Index for input parametric control
Tools and Utilities
RoutingDestination Table
Column Header
INDEX routingDestinationNameValue routingDestinationIndexValue routingDestinationSourceValue routingDestinationUserValue
Description
SNMP instance (row) for Destination
Destination Name
Routing index for the destination
Current source routed to the destination/field used to specify source for router take
Current user that has the destination locked/or protected
Field to set the lock/protect/unlock of a destination
Field to set take/disconnect of a destination routingDestinationLockValue routingDestinationTakeValue routingDestinationNotify
Field to enable/disable SNMP notifications for crosspoint status routingDestinationCCSPOid Provides the SNMP OID of the CCSP parametric control of the output module routingDestinationCCSPTableIndex Provides the SNMP Table Index for the parametric control of the output
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 260
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
Router Salvo Table
Column Header
INDEX routingSalvoNameValue routerSalvoIndexValue routingSalvoTakeValue
Description
SNMP instances for the salvo
Name of the salvo
Index of the salvo
Field to take/lock/protect/unlock salvo
Functions
Crosspoint TAKEs
Set the source name in the
routingDestinationSourceValue
for destination instance in the router destination table
Set Take value in the
routingDestinationTakeValue
for the same destination instance in the router destination table
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 261
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
Crosspoint Disconnect
Set Disconnect value in the
routingDestinationTakeValue
for destination instance in the router destination table
Destination Lock/Protect
Set Unlock/Lock/Protect/Unlock in the
routingDestinationLockValue
for destination instance in the router destination table
Salvo Execution
Set Take/Lock/Protect/Unlock value in the
routerSalvoTakeValue
for salvo instance in routing salvo table
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 262
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
Network Teaming
Network Teaming or NIC Teaming allows for multiple Ethernet adapters to be grouped together or placed in a team, to provide load balancing and redundancy, and support failover scenarios.
In case of the SDNO Controller, you can take two network cards and team them such that they work as a single network card for redundancy. From the system's standpoint, it looks like a single card, but one takes over if the other fails.
The SDNO Controller supports NIC Teaming via Intel® Advanced Network Services (Intel® ANS), which uses an intermediate driver to group multiple physical ports.
Note that you can currently only team ENETs 1 and 2. ENETS 3,4,5,6 are not currently supported.
Steps to Enable Network (NIC) Teaming
Follow these steps to set up NIC teaming:
Disable Redundancy
Note: If you have a redundant Controller, it is recommended that you perform all the same network teaming steps, and set it up in a similar fashion. In a redundant system, perform NIC teaming on the
Standby first, manually failover using the Redundancy Management tool, and then perform NIC teaming on the other Controller.
1.
Disable SDNO Controller redundancy by going to
Configure System > Manage SDNO Controller Settings > Network and Redundancy > Disable
Redundancy
2.
Remote into the SDNO Controller using any of the enabled ENET interfaces, preferably other than
ENET1 or ENET2.
3.
Stop the SDNO Controller by running the
Stop SDNO
script on the Desktop
4.
Run the
SDNO Status
script on the Desktop to verify that all services have stopped
Install Microsoft Powershell®
1.
Install Microsoft PowerShell 4.0 or higher (for Windows 7) from the Microsoft website.
Note that this will require a restart.
2.
Enable the Windows Update service
Note: If Powershell has already been installed, you can check the version by opening a Powershell console (click the Start menu and type Powershell) and entering the command
$PSVersionTable
. This displays the current version (
PSVersion
) which should be 4.0 or higher. If it is lower, you need to install a higher version.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 263
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Install Intel ANS (Advanced Network Service)
Tools and Utilities
1.
Install Intel ANS from the Intel website http://www.intel.com/support/network/sb/cs-009747.htm http://www.intel.com/support/network/sb/cs-009747.htm
2.
When installing, ensure you select the
Windows Powershell Module
option in the
Setup Options
dialog
3.
Turn off Windows Update service
Note: You can check if Intel ANS has already been installed by going to the
Control Panel > Programs and Features
and looking for
Intel Network Connections
.
Register NIC Team Monitoring
1.
Contact Customer Support to get the
RegisterNicTeamMonitor.ps1
file
2.
Select
RegisterNicTeamMonitor.ps1
, right-click Run with PowerShell
You can verify if this has been registered correctly by going to the
Task Scheduler
in Windows, and looking under
Task Scheduler Library > Platinum IP3.
You should see 3 tasks.
Team ENETs 1 and 2
1.
Open the
Control Panel
, go to
Network and Sharing Center
, and click
Change adapter settings
2.
In the list of ENETs, rename
ENET1
to
NIC1
and
ENET2
to
NIC2
(or any other distinguishing name)
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 264
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Note: This is done to free up the
ENET1
name for virtual teaming.
Tools and Utilities
Note: It is recommended you switch to Details View, which shows Ethernet Adapter names as well as Device names.
3.
Once renamed, right click
NIC1
and select
Properties
. Click the
Configure
button.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 265
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
Go to the
Teaming
tab and click the
New Team
button.
Tools and Utilities
5.
In the new team wizard, provide a team name for example
NIC1+NIC2.
6.
In the next screen, select the adapters to include in the team and click
Next.
7.
Select the appropriate team mode (for example,
IEEE 802.3ad
) and click
Finish
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 266
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
8.
Ensure that it is working properly by looking at the
Device Status
in the
General
tab
Tools and Utilities
9.
You should see the new team in the
Network Connections
. Now, rename this back to
ENET1
by right clicking and selecting
Properties.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 267
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
10.
To test this, disconnect
NIC1
and the Controller should still be accessible via
NIC 2
. Do the reverse as well.
You can also click the
Test Switch
button in the Team tab.
11.
Restart Services by running the
Start IP3
script on the desktop.
Start the SDNO Controller and Enable Redundancy
1.
Start the SDNO Controller by running the
Start SDNO
script on the Desktop
2.
Enable SDNO Controller redundancy by going to
Configure system > Manage SDNO Controller Settings > Network and Redundancy > Enable
Redundancy
Teamed ENETs in the WebUI
The SDNO Controller Web UI reflects the status and presence of teamed ENETs.
1.
Launch the SDNO Controller Web UI by entering the IP Address in a web browser
2.
Click
Configure System > Manage SDNO Controller Settings > Network and Redundancy
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 268
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
3.
Under the
ENET1
LED, you will see it is now split into
NIC1
and
NIC2.
When both LEDs show green, it indicates that both network cards are functioning.
4.
If one of the network cards becomes unavailable, you will see the LED show red.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 269
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
5.
ENET status (including teamed ENETs) is also indicated on the SDNO Controller's main dashboard, on the right hand side.
Steps to Remove Network Teaming
Once Network teaming has been set up, if you need to disable it, follow these steps:
1.
If you have a Redundant SDNO Controller and Redundancy has been set up, disable it by going to
Configure System > Manage SDNO Controller Settings > Network and Redundancy > Disable
Redundancy
2.
Stop the SDNO Controller (primary & secondary) by running the
Stop SDNO
script on the Desktop
3.
Remote into the SDNO Controller Controller using using any of the enabled ENET interfaces, preferably other than ENET1
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 270
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Tools and Utilities
4.
Remove Teaming from
ENET1
by selecting it, right clicking, and then clicking the
Remove Team
button in the
Properties
dialog
5.
Rename
NIC1
and
NIC2
to
ENET1
and
ENET2
6.
Restart Services by running the
Start SDNO
script on th Desktop
7.
Launch the Web UI, go to
Configure System
>
Manage SDNO Controller Settings > Network and
Redundancy
and you should see ENET1 no longer reflecting the TEAMed status
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 271
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
8.
Go the main SDNO Controller dashboard and review the ENET status there too.
Tools and Utilities
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 272
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
Router Soft Panel
The Router Soft Panel is a new web based utility for controlling SDNO Controller routers via any computer or mobile device with HTML5 support. The Router Soft Panel essentially runs on a SDNO
Controller, and is specific to routing control for that SDNO Controller.
Logging in
The Router Soft Panel interface can be accessed using
http://<SDNO ControllerIP Address>/panel/
Figure 66: Router Soft Panel Login Screen
Dashboard
Once you log in, a dashboard is displayed with the following:
Views
and
Function buttons
on the top
Sources
and
Destinations
on the left with the ability to filter Sources/Destinations (See Display Pane
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 273
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
A
Display pane
on the right that shows status of selected sources and destinations (See Display Pane
Figure 67: Router Soft Panel Dashboard View
Operation Modes
The users for the Router Soft Panel application correspond to the user accounts (Administrator and
Operator) on the SDNO Controller.
Users logged in as
Administrators
have full access to all Router Soft Panel functionality
Users logged in as
Operators
have limited views and functions available. They have access to the
Multibus view, Batch View, the Snapshot Repository, and Report views. They see some function buttons such as TAKE and Breakaway, and can perform those functions.
Users logged in as
Operators with read only access
see only the Multibus View, Snapshot
Repository, and Report views. They do not see any function buttons such as TAKE or Breakaway.
They can run Source/Destination reports in the Report view.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 274
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
Note: Read only access for Operators can be set on the SDNO Controller by going to
Configure System >
Manage SDNO Controller Settings
and checking the
Operator Read Only Access
checkbox under
Soft
Panel Options
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 275
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Sources and Destinations
Router Soft Panel
In the default
MultiBus View
,
Sources
and
Destinations
defined in the SDNO Controller are displayed on the left of the dashboard.
Figure 68: Sources and Destinations in MultiBus View
Display Pane - Details
Figure 69: Source/Destination Details
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 276
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
Click on a
Source
or
Destination
(in the left pane) to have its details displayed. When you select a
Destination, that Destination and the Source currently connected is displayed. If you select a Source (to switch to) it is displayed on the extreme right, highlighted in red. If there are multiple levels to that source, the levels are displayed as well.
Note:
To enable selection of multiple Destinations, turn on the Multi-select option at the bottom.
Display Pane - Filtering
Click the Filter icon to the right of
Destination
or
Source
(in the header) for a filtering interface.
Figure 70: Filter Icon
You can filter sources/destinations by
Category
,
Group
,
Status,
or
Custom
(filtering).
The
Category
option lets you filter by Category
The
Group
option lets you select a Group to filter on
The
Status
option lets you input a Destination Status Name to search on
The
Custom
option lets you select a one or more items to filter on
Figure 71: Filter Destination by Category
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 277
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Functions
Router Soft Panel
The top of the dashboard displays several buttons to perform functions on Sources and Destinations.
You can perform the following functions:
Takes
Undoing Takes
Adding to a Batch
Breakaways
Lock
Protect
Clear (Lock and Protect)
Note:
Turn on the Multi-select option at the bottom if you want to select multiple destinations.
Takes
You can do a
TAKE
by selecting a sources and destination(s).
Note:
The
TAKE
button at the top is enabled (Red) when you select at least one source and one or more destinations.
Figure 72: Performing a Take
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 278
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
Undoing a Take
Once a
TAKE
has been performed, the
Undo
button is enabled and you can choose to Undo the last
TAKE
.
Note that only the last
TAKE
can be undone, not any takes prior to that.
When you click
Undo
, a message will be displayed asking for confirmation of the requested
Undo
function for the last
TAKE
.
Figure 73: Undoing a Take
Add to Batch
You can select a
Source
and one or more
Destinations
and add it to a Batch.
Note:
The
Add to Batch
button at the top is enabled when you have at least one source and one destination selected.
Figure 74: Add to Batch
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 279
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
The Add to Batch button reflect the number of batches currently stored.
Switch to the Batch View (on page 283) to see the contents of batches.
Router Soft Panel
Breakaway
To perform a breakaway, select a Source and a Destination and click the Breakaway button at the top.
A confirmation dialog displays the following details:
Destination
Selected Destination(s) will be displayed. Select the Level.
Take
The
TAKE
button is then enabled and you can click TAKE to send the Breakaway command to the
Router.
Lock
The Lock function prevents all users from changing the destination.
You can lock one or more destinations by selecting (use multi-select to select multiple) the destinations , clicking the last function button at the top and clicking
Lock
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 280
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Locked Destinations will display a special icon to denote their locked status.
Router Soft Panel
The user that initiated the Lock can clear it using the
Clear Lock/Protect
function. See Clear
Protect
The Protect function prevents users (except the user who initiated the Protect) from changing the destination.
You can protect one or more destinations by selecting (use multi-select to select multiple) the destinations , clicking the last function button at the top and clicking
Protect
.
Protected Destinations will display a special icon to denote their protected status.
The user that initiated the Protect can clear protected Destinations using the
Clear Lock/Protect
function. See Clear (Lock/Protect) (on page 282).
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 281
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Clear (Lock/Protect)
Router Soft Panel
The
Clear
function can be used to clear locked or protected Destinations. Administrator users can override the locks set by other operators.
To clear locks or protects, select the locked/protected destinations and then select the
Clear
option from the last function button at the top.
Views
The Router Soft Panel interface is divided into several views.
MultiBus (default)
Batch
Salvo
Macro
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 282
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
MultiBus View
Router Soft Panel
MultiBus View is the default view for the dashboard. It displays all the Sources and Destinations and
various function buttons. See Sources and Destinations (on page 276).
Batch View
The Batch View is populated by the Add to Batch function. See Add to Batch (on page 279).
If you have added
Sources
and
Destinations
to a batch (from the default MultiBus View), they will be displayed here. Click the
TAKE
button to execute.
If nothing has been added to a batch, the View will be empty.
Salvo View
If you have any Salvos defined, they will be displayed here.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 283
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
If there are no Salvos, this view will be empty.
Macro View
In the Macro View, you can choose to perform:
A Diagonal Take
A Reverse Diagonal Take
A One To All Take
Router Soft Panel
For a
Diagonal
or
Reverse Diagonal
Take, click the
TAKE
button to execute.
For a
One to All Take:
1.
Click the
Select Source
button
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 284
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
2.
Select a Source from the list that is displayed or filter using criteria and click
OK
.
Router Soft Panel
3.
Click the TAKE button under
One To All
which will now be enabled Red.
Snapshot Scheduler
The Schedule View lists defined schedules, and provides an interface to create/edit/delete/execute schedules
Note: Before executing the snapshot, ensure that tielines are available or that you have sufficient tielines. If some of your tielines are in use, you may not be able to execute some of the crosspoints in the snapshot. One option is to use
reserved tielines
(See Tielines (on page 41)). Another option is to
disconnect all the tielines before executing the snapshot.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 285
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Creating a New Schedule Task
Router Soft Panel
Enter a
Name
and
Description
for the Task. Select the Enable checkbox to
Activate
the task.
Schedule Trigger
Enter the
Trigger
action for the created task.
Start Time
: Enter the start date and time for the task
End Time
: Enter the end date and time for the task
Frequency
: Can be defined in hours or days
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 286
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
Based on this criteria, the schedule will run during the window defined by the start and end date/time, at the defined frequencies.
Action
Define whether the task will run on ALL destination or selected ones.
For
ALL
destinations, leave the
All
checkbox selected
For
specific
destinations, clear the All checkbox and click the SELECT button. Filter to select the desired destinations or Ctrl+select multiple destinations.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 287
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Editing/Deleting Tasks
Once defined, tasks will be displayed in the Snapshot Scheduler view.
Router Soft Panel
To edit a task, select it in the Schedule View, and click
Edit
To delete a task, select it and click
Delete
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 288
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Snapshot Repository
Router Soft Panel
The Snapshot Repository contains snapshots of the system taken per the configurations in the Snapshot
Scheduler.
Snapshots are saved in .CSV format, and you can open it in an application like Microsoft Excel or even
Notepad.
You can select a snapshot and and click the
Show
button to view it, the
Delete
button to erase it, or the
Export
button to save it locally.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 289
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Report
Router Soft Panel
A Report can be generated for current crosspoint status, by
Destination
or
Source.
Select
Report
from the drop down menu to go Report mode, and then click the appropriate checkbox under
Report Mode
to select
Source
or
Destination
.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 290
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Router Soft Panel
Depending on your mode selection, a timestamped snapshot of crosspoints is displayed. Click the
Export
button to export to
.CSV
format .
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 291
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Logging Server
Logging Server
Overview
Magellan™ Diagnostic Logging provides logging information on SDNO Controller and Routing functions.
It is pre-installed on the SDNO Controller and can be accessed on port 8002 on the same IP address as the SDNO Controller .
To launch the Magellan Diagnostic Logging:
In the URL field of your browser, type
http://<Controller IP Address>:8002/
OR
Click the
Fault Log
link on the SDNO Controller dashboard.
The following is explained in this section:
Logging Server Interface (on page 294 )
Configuring the Logging Server (on page 298)
Browser Settings
If using Internet Explorer, turn off caching to prevent any issues with content being displayed in popup windows
1.
Go to Tools > Internet Options
2.
In the General tab, click the Settings button in the Browsing History section
3.
In the Temporary Internet Files and History Settings dialog, select Every time I visit the webpage under check for newer versions of stored pages.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 292
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
4.
Click OK.
Logging Server
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 293
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Logging Server Interface
Logging Server
Figure 75: Logging Server Home tab
1
2
Table 18: Logging Server Interface Options
Item Description
3
4
5
6
Home Tab The top level Home Tab.
Diagnostic Elements The available elements to view logs for. For example, Database Service, Debug Log, etc. Note that elements are displayed depending on whether they have any related logs. For example, if a firmware upgrade has never been performed on a
Controller, logs for that will not be displayed.
History
Examine Logs
Select an element and click the
History
button to view History for the selected element
Select an element and click the
Examine Logs
button to review logs for the selected element
View Live Logs Select an element and click the
View Live Logs
button to view real time logs for the selected element
Filters and Actions Click to filter display and content preferences for logs
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 294
7
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Item
Export
Description
Select an element and click the
Export
button to export log information. Logs can be exported by day, week, or all.
8 Summary
9 Find
Click the Summary icon to display a Summary toolbar at the top of the page that contains shortcut links to Exports, Imports, and Collections.
Searches for the entered text on the page
Logging Server
10
11
Settings Click to view/define System-wide settings, Log
Viewer Settings, and Logging Server Settings.
Import and View Log
Collections
Click to view/access
Log collections
that can then be
examined
or
exported
. You can also
import
logs.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 295
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Working with Logs
Logging Server
Examining Logs
On the
Home
tab, select devices (if no devices are selected, it’s the same as if all of them are) and click
Examine Logs
to view logs in detail.
Figure 76: Examiner Tab
6
7
2
3
1
4
Table 19: Examiner Tab
Item
5
8
Log Date
Log End Range
Description
Date to view logs from. Click the calendar icon and go to a date.
Log Start Range The Start Point of the Log Range. Click and drag to define.
The End Point of the Log Range
Date/Time Range Date and Time range for the selected log range
Next/Previous
Page
First/Last Page
Click to go to the next or previous page.
Click to go to the last or first page.
Options Click to view/define Log Options and to filter logs.
Log Range Options
Right click to view options for the selected log range. You can choose to refresh logs or export the selected range, or zoom into a selection
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 296
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Logging Server
The top portion of the
Examiner
tab shows a timeline. To View a specific time, click the timeline with the mouse. The log examiner updates to show logs surrounding that time.
Above the timeline, you can adjust the content that is displayed by changing the date and duration. To view a different part of the log, drag the sliders. Below the timeline, messages are displayed in a static format. You can sort the log entries by clicking on column headers.
Live Logs
To view a live (real time) log, place a check beside the device on the Home page, and then click
View
Live Logs
.
Figure 77: Live Logs
If no logs are selected or all logs are selected, click
View Live Logs
and the log that opens will contain entries for all connected devices.
If no device has activity when you select View Live Logs, the viewer tab is empty. The viewer updates dynamically as events occur.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 297
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Log History
Click the
History
button against a module to view Module Log History.
Logging Server
Figure 78: Logging Server History Tab
Clearing Logs
When you clear logs from the logging server, all devices are also removed. Be sure to save logs that you need prior to clearing.
1.
If the
Filters
palette is not open at the right side of the screen, click
Show Filters/Actions
.
Click
Clear All Logs
and then click
OK
. All logs and all information in the logs are removed.
When a device has activity, it will reappear on the
Home
page of the logging server.
Configuring the Logging Server
Click
Settings
in the top right corner of the screen to open the
Settings
pane.
Settings are divided into:
Network
,
Log Viewer
,
Logging Server,
and
System Wide
settings.
When you make any changes to the Logging Server’s settings, click
Save Settings
to commit changes.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 298
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Logging Server
For the most part, don’t change port numbers and other settings except on the advice of Customer
Service.
If your logging server is not receiving any messages, despite having devices configured, check the
Send
Messages over SysLog option under
Network Settings. If this item is not checked, no messages will be received.
Changing Columns That Appear in the Logging Server
1.
In the
Settings > Log
Viewer section, scroll down to
Column Preferences
.
Figure 79: Column References Selector in the Logging Server
The items in the
Available
list on the left are not currently used in the Log display. Items in the
Visible
list on the right are column headers in the Log display.
To move items from one column to the other, click on the item and hold the mouse down while dragging from one column to the other. When you see a shadow of the item in the column you’re dragging to, release the mouse button. The item appears at the point in the list where you dropped it.
You can change column order by dragging items within a column.
Note:
You can also drag column headers on the table interfaces themselves.
Click
Save Settings
to commit the changes.
Changes to columns are universal and apply to all examiner pages.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 299
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual Logging Server
Changing (Filtering) the Content Displayed in the Examiner
In addition to sorting a log file by the display columns, you can choose to view only certain types of logs.
Follow these steps:
1.
Click
Show Filters/Actions
.
The
Filters
palette appears at the right side of the screen.
2.
Place checks beside types of information you would like to see in the
Examiner
.
You can only filter out information.
3.
Click
Apply
. The table refreshes to display the selected information.
Interpreting Messages in the Logging Server
Information such as
Date
,
Time
,
Level
, etc., in the logging server is defined by the logging server itself; see the Logging Server’s documentation for more information on those items.
The
Application
field in the logging server tells you which component the message is from, for example,
Platinum IP3 Diagnostics
. The
Message
field is specific to the particular device. A single device action, such as a Take, can trigger numerous messages in the log, as the repercussions of that action are executed.
The message field of a typical log entry is separated by commas, and contains the following information:
The source of the change, for example: Operation, meaning an operator performed an action)
The device where the action took place, for example RCP: IP address, meaning a specific remote control panel triggered an action
The item that was triggered
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 300
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
The action that happened as a result of the triggered item
Logging Server
Message Types
Error:
This level is reserved for problems that directly affect output, such as loss of signal and loss of reference. High-priority CCSP alarms with a level of
Critical
generate this message when asserted.
Warning
: This level notifies about potential problems. Medium-priority CCSP alarms with a level of
Warning
generate this message when asserted.
Notice
: These messages apply to all alarm de-assertions and RCP connection messages.
Informational
: This level indicates routine device operation.
Debug
: This level is disabled by default and only intended for use in specific troubleshooting guided by tech support.
Informational messages will be generated for all operational changes from control sources enabled in the logging server setup. Control by RCP will list the IP of the device to identify which one performed the operation. Other sources have a sole source available - all Automation message are assumed to come from the same source, but EAS is considered another source. All messages control from the parametric system are identified as CCSP.
Import and Exporting Logs
Exporting Logs
When you export a log, it is saved as a zip file that contains an XML file. Do one of the following:
Logging Server Home Page
From the Logging Server’s
Home
page, do either of the following:
At the right end of the header line, click
Export
, enter Duration and Format, and then click
Export
again.
Place checks beside items in the Devices and Application Profiles list, and then click
Show
Filters/Actions
, and click
Export
under
Actions
. All selected logs (any log with a check beside it) are exported.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 301
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
Examiner Tab
From the Examiner, click
Show Options
, and then, under
Actions
, click
Export
.
Logging Server
History Tab
From the
History
tab, place a check beside the logs you want to export, and then click
Export
.
Importing Logs
The Logging Server can import logs that it or another Logging Server has saved. To import a log, follow these steps:
1.
Click
Import and View Log Collections
at the bottom of the
Home
page. This enables you to see past log collections or to import logs.
The lower section of the screen expands to display details.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 302
Magellan™ SDN Orchestrator
Installation, Configuration, and Operation Manual
2.
Click
Import Logs
and then browse to a .zip or .magellanlog file and click
Open
.
Logging Server
A progress bar appears, and when the import is finished, an
Import Complete
message appears in the top right corner of the screen.
3.
Click an item in the
Log Collections
column on the left.
The
Collection Devices
column updates to display all devices contained in that collection.
4.
Place a check beside each device log you would like to load in the Examiner, and then click
Examine
Logs
.
5.
The logs open in the
Examiner
.
Using Summaries
If you have recently imported or exported a log, the
Summary
bar appears below the button bar at the top of your Logging Server screen. If the Summary bar is not open, click
Summary
to open it. Click the X at the end of the toolbar to close it.
Figure 80: Summary Toolbar
The Summary bar has three options:
Exports
,
Imports
, and
Collections
.
Click one of these options to open the
Summary Details
dialog box.
The three options correspond to three tabs on the
Summary Details
dialog box.
Each tab details recent activity for that area of the interface.
© 2016 Imagine Communications Corp.
Proprietary and Confidential.
Version 2.0 | Page 303
/
Download
Just a friendly reminder. You can view the document right here. But most importantly, our AI has already read it. It can explain complex things in simple terms, answer your questions in any language, and help you quickly navigate even the longest or most compilcated documents.
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
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?
No votes
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?
No votes
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?
No votes
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.
Patricia K.
Where can information regarding the device's power supply and power consumption be found?
No votes
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.
