GV Convergent Training Manual v3.0
GV Convergent Training Manual v3.0
GV CONVERGENT
TM
TRAINING MANUAL
TRAINING MANUAL V3.0 (GVC VERSION 1.6)
SEP 2018
www.grassvalley.com
Table of Contents
IP Playout.............................................................................................................................................. 6
Getting started........................................................................................................................................ 10
User Management.............................................................................................................................. 56
Maintenance ....................................................................................................................................... 59
Assistance .......................................................................................................................................... 61
Channels/Sources.............................................................................................................................. 64
How to load the factory default database if the current database is corrupted .......................... 67
I uninstalled GVC client via Uninstall GV Convergent Client and installed right version, but I still
see previous version when I run GVC client. How can I fix this?.................................................... 68
Will the server be affected if you reverse the installation order, i.e. install SAAS before installing
the PAAS? ........................................................................................................................................... 69
When you create a CLUSTER, do you have to manually update the software of both System
Controllers? ........................................................................................................................................ 69
What happens with the Secondary GVC controller if I remove it from a 1+1 GVC cluster? ......... 69
When performing a backup, how long will the Panels go blank? ................................................... 69
GV CONVERGENT training sessions are custom designed to meet the specific tools and workflow
used at each customer’s facility. Classes are delivered by experienced Grass Valley training
professionals who use their years of broadcast experience to focus on the knowledge and skills GV
CONVERGENT engineers need.
Content is arranged into 9 sections, each covering the concepts and skills required to use a GV
CONVERGENT tool set. The Grass Valley CONVERGENT Trainer will reference the appropriate
Section content during the training.
Each Section can be accessed independently of the others, depending on the custom course outline
created by the Grass Valley GV CONVERGENT Trainer.
http://www.grassvalley.com/apps/doc_show?set=routers&c=^GV%20CONVERGENT$&super=broad
cast&skin=gvcmsnewpop&sort=rev#manuals
Opportunities to find more information in the Topic Library are referenced throughout this manual.
IP Production Studio
Third-party Control
Solid State Drives Dual hot swappable HDD INTEL DC 3500 150GB, SATA 6Gb/s 2.5"
1. If using a laptop, change the IP to the same range as the server’s Management IP address
(em1)
2. In a web browser, type the Management IP address of the GV Convergent server (default:
10.0.3.10).
3. Type the following login credentials, and then click Login
Username: admin
Password: admin
4. Once logged in, click Network Settings, and then change the Management IP, network mask,
and gateway address for em1. Click Apply when done.
5. Clicking Apply will restart the Linux service as well as the GVC service
6. Verify the network connectivity with the server issuing the Ping command
1. Login to the web server of GV CONVERGENT using the web login credentials
2. Click Software Update under the Maintenance Section
3. Update the PAAS file first and then update the SAAS. Click Browse… and then browse to the
location of the PAAS file, click Upgrade. Follow the same procedure to install the SAAS file.
PAAS contains the operating system specific modules and SAAS contains the GV CONVERGENT
software related modules.
3. Once the installer starts, a window appears, showing the download and installation progress
4. At the end of the installation, a shortcut should be added to your desktop to start the
application. Note that it is also added to the Start Menu, along with the Uninstall
5. You will be prompted to enter your username, password and management IP of the GV
CONVERGENT controller
6. Click Login using the same web credentials and the GV Convergent Client Stage appears
GV Convergent Client will be updated automatically the next time you open it after you upgrade
the software of the GV Convergent controller.
Stage View
The Stage View is also referred to as the Home View of the GV Convergent Client. To navigate to it,
click the icon on the bottom of the page.
Area Configurator
Opening Area Configurator
Renaming an area
1. Click the configured default area called Area (make sure that you are in Edit mode). Clicking
the Area bubble will open up the Properties in the Property Editor where you can rename it.
NOTE: The Reference IP in the System Controller Group Properties is used for fail-over
purposes. When connectivity is lost, a stand-by server will determine if it can become active
if it can ping this Reference IP. You can enter the IP address of any device that is always
running (ex. DNS server or client PC).
3. Specify a Virtual IP Address as well so that the Panels will also be active in case one of the
Controllers lost connectivity.
1. You can create multiple Areas using one System Controller. However, there will only be one
active Topology within an active Area. To add an Area, simply drag and drop an Area virtual
device to the workspace and name it accordingly.
Selecting an area
1. To select an Area, click the Area Configurator icon on the upper left corner of the screen,
select the Area, for example: Prod and click the Select Area icon.
AREA – represents a part of your facilities you wish to control. By default, GV Convergent is
configured with one generic area named Area.
3. Click Edit if you want to edit the label. Note that you cannot edit its compatibility or its
contents. You also cannot delete a system defined level.
Topology Configurator
1. Click the icon at the bottom left hand side of the screen to open up the Stage View
Adding a topology
1. Click the Topology icon on the upper top corner of the window and click
Renaming a topology
1. Click the Topology icon on the upper top corner of the window and select the topology
that you want to rename. Click Edit and enter the new name.
1. Click the Topology icon on the upper top corner of the window, select the topology to
activate and click Load
1. Click and drag a GV NODE device from the list of Virtual Devices to the Topology
Configurator workspace. Enter its properties, most importantly the Frame IP Address.
2. Click and drag a device such as a Camera that is physically connected to the GV Node. In
this example, we are adding 2 x SDI Cameras. Device Group Properties should be set as
follows:
Devices = 2
Input Connectors = 0
Output Connectors = 1
Gateway NP16 Connection State – in GV Node 1.3.1, a crosspoint change request is sent to the
CPU-ETH controller. However, with GV Node 2.x, the request is now sent using the NP0016
Protocol. This state will automatically be retrieved depending on the installed GV Node software.
1. To physically connect a device, you need to select the appropriate input or output port and
draw a line to the device it connects to. Sample below shows the output of the Camera
going into an XIO card installed on a GV Node frame.
2. Click on the line to open up the Builder section of the Physical Connections Table
3. Select the ports on the device and select the appropriate router ports where it connects to.
Hold the SHIFT key to select multiple selections. Hold the CTRL key on the destination side.
Click the Candidate button and verify if the connections are correct. Click Connect once
confirmed.
2 x SDI Cameras connected to ports 1 and 2 of the XIO board installed on Slot 1. Hence, it is
connected to SDI ports named RtrIn1 and RtrIn2. Refer to the IFM Enumeration Table.
The Advanced section of the Device Properties Menu will give you relevant statuses of the frame
such as Router (SDI) or Gateway (IP) Connection which will be very helpful in troubleshooting.
Statuses are automatically retrieved by the GV Convergent server from the physical device.
Device Group Properties allow you to set the Properties of the devices as a group while Device
Properties allow you to set the parameters of each individual device.
1. If you want to delete a connection, make sure that you are in Link mode. Draw a line over the
connection that you want to delete until you see a dotted line with a scissors icon.
2. To delete a device, click the Edit mode, click the device to delete and press DELETE on the
keyboard.
1. Make sure that MADI is enabled on the appropriate input of an XIO-4901 card. This is
configured in the GV Node Manager using iControl Navigator. Sample below shows that
MADI is to be enabled on input 9 of the XIO-4901 card installed on Slot 16 of a GV Node
Frame.
3. Since the ninth input of the XIO-4901 card in Slot 16 is determined as source 144. Refer to
the IFM Enumeration Table, select SDI input 144 and set MADI in Mods-In to IFM.
1. When adding a network switch to the topology, select a Network Switch device and give it an
appropriate name. Enter the number of physical ports (bi-directional for IP). Set the Control
Port by clicking Control Ports to Dummy Network Switch if you are not adding a Cisco
DCNM.
1. To add a Cisco DCNM, drag a Network Switch device to the topology and set the Control Port
as Cisco DCNM. Enter its IP address and its username/password. Once GVC has
established connections with the DCNM, it will retrieve both receive and transmit stream
policies as configured on the device that is connected to the switch, ex. GV Node.
An item will be highlighted ORANGE when a parameter is changed from its default value.
1. When adding an IP device such as an IPG-3901, you would need to select the IPG-
3901Virtual Device.
2. Click Device Properties and enter the Frame IP Address of the Densite Frame where the IPG-
3901 card is installed.
3. Enter the Slot Number (very important) where the IPG-3901 card is installed.
1. When adding an IP device such as an IP Camera, you can select a Virtual Device called IP
Device and name it accordingly.
To verify a valid connection with the IPG-3901, make sure that the Connection State is online.
Click on a line and click on the Physical Connections Table to check which ports
are currently connected.
An active topology is automatically locked once you log out of GV Convergent Client. You have to
unlock it before editing. Click the icon to unlock it.
3. Likewise, its head output will become router input source 28 and 29 to the GV Node frame.
Refer to the IFM Enumeration Table.
1. In order to add a physical monitoring device, add a Monitor Virtual Device to the topology.
6. Click on the selected protocol and enter the router’s physical IP Address. For proper
communication, make sure that the Connection State 1 is Online.
When a device, for example, GV Node frame is configured in redundancy mode, SMPTE 2022-7, you
have to consider the following IFM-2T port configuration as shown below to match your network
connections:
In the above sample, the GV Node frame is connected to the Blue Network on ports 1 and 2
and to the Red Network on ports 4 and 5.
Complete topology
After completing the topology with 2 GV Nodes connected to 2 networks, Blue and Red.
The following shows how a very basic 2 GV Node systems connected to a redundant COTS network
is represented in GV Convergent. It is important to understand that in GVC, physical connections
between devices (the lines on the pictures) have a direction. In this specific case, it means that:
GVC will automatically create Logical Sources for XIO1 and XIO2 and create Logical
destination for KMX4911.
If you want to make each GVN bi-directional (capable of sending and receiving signals), then you
would need to create the topology as follows:
It is worth understanding as well that each XIO can alternatively be represented as a bi-directional
device (ex. you don't need to have an XIO1 and an XIO2).
NOTE: To configure an SDI destination for vertically accurate switching on a GV Node, check
the IP Clean Switch option on the rightmost column.
1. Click in the Sources section of the Logical Device Table to add a new logical device
source.
2. Enter MyScr1 in the Base Name and click OK.
3. Click on the newly created MySrc1and drag CAM-1to MyScr1’s SDI column.
5. MyScr1 audio1 channel should now have audio3. The shuffle icon will also appear on the
top right corner of the newly created MyScr1.
Category Configurator
Once the topology has been built, you can create Categories that can be useful to group the different
types of sources according to their type or use.
1. Click the icon on the left bottom portion of the screen to open up the Stage View.
2. Click Category Configurator.
3. Click Add to create a new Category and give it a name. Click OK.
Panel Configurator
1. Click Panel Configurator in the Stage View.
5. To add a button such as Category, drag the button from the Tool Menu to your panel.
6. Click Categories from the Resources for Topology section and this will open up the
Categories that you have previously created. Select the Category that you want and drag it
to the button.
8. Click the newly added Panel and click on the Control Port. Select NV9XX Panel Control.
10. Click Panel Control Port and make sure to enter the PanelId. For proper communication with
the Panel, make sure that the Connection State 1 is Online.
11. If you are using a virtual Panel, you need to set the Controller IP to the IP of the GV
Convergent Server by right-clicking on the Panel and select Set Parameters….
13. If working correctly, the Panel should show proper colours as configured on the buttons.
24 character name sets are now available in GV Convergent. Do the following to enable this feature:
2. Click Colors and drag the color to the button that you want to change. For example change
the Blue Salvo button to Purple.
If you created multiple Panel configurations and you want to load it:
1. Click Manage
2. Select the name of the Panel configuration that you want to load and click Load.
1. Click the Quick Source icon in the Resources Menu to enable it.
2. Select the Source and drag it to the Panel.
LIST ITEM – List the items that are in a Category. You have to create a new page for these items.
KEYSTROKE – Numeric numbers that can be used only for Destinations. You would also need a
SELECT button on the same page for the TAKE button to be triggered.
DESTINATION ITEM – shows you the mapped Source and Destination on a single button.
INDEXED TAKE – allows TAKE on a DESTINATION ITEM button. Destination Index would refer to
the index of the Destination Item button.
SELECT PERSIST – a Mode that retains the last Source and Destination selections.
MULTI-SELECT – a Mode that allows you to select multiple Destinations with the same Source.
1. Design a Panel with levels where breakaway are to be achieved. For example:
2. On the Panel, select the DEST, LEVEL, SOURCE, press TAKE. In this sample, we routed Video
Level (V) of Svr-1 to Destination Mon12.
3. Routed Audio Level (A) which represents all 16 channels of Source Svr-2 to the same
Destination, Mon12.
Path Manager
You can use the Path Manager if you want to know information such as tie-line usage, what streams
are routed to specific destinations and status.
3. Streams view will show you the source stream name with its multicast address and port. It
will also show you where a source is routed to.
4. Click Destinations and select a destination name. In this sample, we wanted to know what
source is currently routed and the path it is taking to a destination called Dec1.
6. Status Menu will give you the switch and flow status of DCNM if applicable.
System Status
This menu allows you the check the health, CPU, memory and NIC status of the main and redundant
(if applicable) GVC Controllers. You can also FORCE ACTIVATE the redundant controller from this
menu, if needed.
It will also show the list of Panels that are connected and the status of router and switches.
2. Click the icon to add a new salvo. By default, it will create a generic Salvo 1, Salvo 2,
Salvo x.
5. Click Control, select the Salvos radio button. Select the salvo name that you want to run and
click TAKE.
Creating a user
3. Enter User ID and password. Note that the User ID is case sensitive.
4. Once the new user has been created, click the name of the new user and click the Area
where you want to grant the new user access. The roles should appear.
6. You can now login into the GV Convergent Admin and Client using the profile of the newly
created user.
Maintenance
Backup and Restore
1. To create a backup of the database, click the Backup and Restore icon. Click Backup to
create a backup database file. This file will initially be saved on the server.
2. Once the backup process is done, you can then click the Download button to save it locally.
The Backup process will momentarily stop the main service called Pegasus and disconnect all
active client connection; therefore, you will lose Panel control. It should reconnect once the
process is done. If there are multiple backup files, select the file that you want to download and
click Download.
If you have previously created a backup file and saved it remotely, you can upload it to the server by
clicking the Upload button and browse to the file when prompted.
To ensure that the server is properly rebooted or shutdown, use the Shutdown or Reboot function
from GV Convergent Admin.
Audit Logs
GVC’s logs can be obtained from the Audit Logs Menu. The current logs will be named audit.log and
the previous logs will be named audit.log.<date>.
Assistance
System Snapshot
Like other Grass Valley products, the GV Convergent server is also equipped with a utility that can
generate the logs and other pertinent information needed by Support to help the client in
troubleshooting issues.
Click the System Snapshot button to generate the logs. The output will be a .zip file.
1. Set the Protocol of the physical GV Node router to NVEP NV9000 Port Takes (NP0017),
connection type: TCP/IP.
2. Set the router host name/IP address to the IP address of GV Convergent. TCP/IP port would
be 9193 (default port of the NP0017 protocol) + External ID of the Area in GVC = 9194.
3. Logical router should be SAME size as the Physical router. Otherwise, it would not work.
Import the Source and Destination labels automatically using Auto Map.
2. Obtain the text label of either the destination or the source at destination, and assign it to
the KX local input.
DESTINATION
LABEL
SOURCE LABEL
How to load the factory default database if the current database is corrupted
1. SSH into the GVC server (see above)
2. Type ‘service pegasus stop’
3. Type ‘cd /usr/local/pegasus/ucs-embedded-launcher’
4. Type ‘rm –fr databases/’
5. Type ‘reboot’ (database folder will be recreated after the GVC server has rebooted)
If running, you should see a message as folllow: 'Checking of densite service: Service Densite
is running with PID 1517 since Thu Jan 19 02:45:49 2017'
Pegasus is the core GVC service running on the GVC CONTROLLER. If not running, panels, GVC
Client cannot communicate with the GVC controller.
Densite service is responsible for controlling IPG-3901 and IFM-2T version 1.3.1 (IP portion). IFT-
2T version 2.x uses NP0016.
I uninstalled GVC client via Uninstall GV Convergent Client and installed right
version, but I still see previous version when I run GVC client. How can I fix this?
Normal way of uninstalling GVC client is via link shown in below picture
Once that is done, you can install appropriate GVC Client from GVC Admin and launch it. If you
notice once you launched GVC Client that the version displayed (see example below) does not
match what is displayed on to GVC Admin, then you may need to manually delete GVC client from
your PC. This involves closing GVC Client, then deleting 'JWrapper-GVConvergentClient' folder. Go
back to GVC Admin and download Native Installer again.
Will the server be affected if you reverse the installation order, i.e. install SAAS
before installing the PAAS?
Not necessarily, but a SAAS may expect specific functions provided by PAAS to work correctly. This
means that if you upgrade SAAS before PAAS, Pegasus service which runs on GVC server may not
start correctly. It is a preferred approach to always upgrade PAAS before SAAS. Use the Rollback
function from GVC Admin if needed.
When you create a CLUSTER, do you have to manually update the software of both
System Controllers?
Yes, if the two GVC controllers are not running the same PAAS/SAAS version. This must be done
prior to creating the 1+1 cluster. GVC controllers that are part of a cluster should be running same
software version.
What happens with the Secondary GVC controller if I remove it from a 1+1 GVC
cluster?
Once the 1+1 GVC controller cluster is removed, you will be able to connect to Secondary controller
via either GVC Admin or the GVC Client. If you connect with GVC client, you will notice it contains the
same configuration as the Primary controller, but in the case of the Secondary controller (i.e. the one
removed from the cluster) all topologies are inactive. This means that there is no risk of having both
controllers controlling the same equipment.
configuration files
engineering logs
output of Linux commands
gvc.log – will give you pertinent information such as connection issue related to a problem with
the topology or incorrect logical level.