System Integration. Imagine communications Magellan SDNO Controller
Pubblicità
Pubblicità
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
Scarica
Link pubblico aggiornato
Il link pubblico alla tua chat è stato aggiornato. Puoi visualizzare e gestire i tuoi link di chat dopo la registrazione qui.
Link pubblico del documento
Pubblicità
