The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
First Published: April 21, 2014
This document is intended for Cisco StadiumVision Director administrators and describes how to configure the initial setup of the Cisco StadiumVision Director server.
Before you configure Cisco StadiumVision Director servers, be sure that the following requirements are met:
– IP address (IPv4 only) and network mask
Note The Cisco StadiumVision Director Remote server should be configured with a static IP address or a non-expiring DHCP lease. In addition, DHCP Server Option 43 should be set up to point to the primary server’s URL for auto-registration to work.
This section includes the following tasks:
When you install a full ISO on a Platform 3 server, you configure certain network settings in the Linux interface as part of the ISO installation such as the server IP address and DNS configuration.
As long as the network configuration is successfully completed as part of the installation, then the only remaining system configuration is to set the date and time options on the server and restart the Cisco StadiumVision Director software.
For detailed information about how to configure the date and time options, see the “Configuring NTP on Cisco StadiumVision Servers and DMPs” section.
Note If for some reason you were unable to complete the Linux network configuration as part of the ISO installation, then you need to complete all of the tasks in this module.
Note If for some reason you were unable to complete the Linux network configuration as part of the full ISO installation, then complete this task.
This task describes how to access the Linux menus from the TUI to configure the Cisco StadiumVision Director server network interface.
To configure the Cisco StadiumVision Director server network interface, complete the following steps:
Step 1 Log into the TUI as installer on the server using a directly-connected console or SSH client.
The TUI Main Menu is displayed.
Step 2 From the Main Menu, go to System Settings > Network Settings > Setup Network Information .
Tip To navigate through the TUI menus you must type the character that corresponds to the menu area where you want to go (a, b, c, and so on) and press Enter.
To return to other menus, you must back out of the hierarchy of menus using one of the indicated keys to return you to prior menus.
Step 3 At the Configure Network confirmation screen, press any key to continue to enter the Linux network configuration interface.
The Select Action Linux screen is displayed with the Edit Devices option selected.
Tip If you notice what appears to be stray characters in the Linux interface, verify that your SSH client is using the UTF-8 character set translation.
Step 4 In the Select Action screen, select Edit Devices and press Enter .
Step 5 In the Select a Device screen, select eth0 and press Enter .
Figure 2 Select a Device Screen
The Ethernet Configuration screen is displayed.
Note The Linux screen is mislabeled “Devernet Configuration.”
Step 6 In the Ethernet Configuration screen (Figure 3), do the following:
Figure 3 Devernet Configuration Screen
a. Press the Tab key until the cursor is positioned on the Static IP address line.
b. Press the backspace key to go to the beginning of the line and type in the IPv4 address of the Cisco StadiumVision Director Server.
Note This should be a different IP address than what you configured for the CIMC interface.
c. Press the tab key to go to the Netmask line. Type the network mask for the IPv4 address.
d. (Optional) In the Default gateway IP line, type the address of the default gateway of your network.
Step 7 When configuration of all options is complete, press the Tab key until the Ok button is selected and press Enter .
You return to the Select a Device screen.
Step 8 Press the Tab key until the Save button is highlighted and press Enter .
You return to the Select Action screen.
Step 9 Press the down arrow key to select the Edit DNS configuration option and press Enter .
The DNS configuration screen is displayed.
Step 10 In the DNS configuration screen (Figure 4), select and configure the Hostname and one or more DNS Server IP addresses.
Note Do not use hostnames that contain periods “.” within the name.
Figure 4 DNS Configuration Screen
Step 11 Press the Tab key until the Ok button is selected and press Enter .
You return to the Select Action screen.
Step 12 In the Select Action screen, press the Tab key until the Save&Quit button is selected and press Enter .
You return to the TUI Configure Network menu.
Note If for some reason you were unable to complete the Linux network configuration as part of the full ISO installation, then complete this task.
Before you begin, be sure that you know how to use the vi editor. For more information, see the Cisco StadiumVision Director Server Text Utility Interface.
To edit the hosts file, complete the following steps:
Step 1 From the TUI Network Settings menu, select the Edit hosts file option.
Step 2 At the confirmation prompt, press any key to open the /etc/hosts file for editing.
Step 3 Change the line with IP address “10.10.10.10” to a comment (insert a # character at the beginning of the line) as shown in the following example:
Step 4 Change the line for the IPv6 localhost entry “::1” to a comment as shown in the following example:
Step 5 Add a line for the server IP address and hostname as shown in the following example, where x.x.x.x is the IPv4 address of the Cisco StadiumVision Director server, and hostname is the name to identify the server:
Note Do not use hostnames that contain periods “.” within the name.
Step 6 Press Esc to enter vi command mode.
Step 7 Save the changes to the file by typing the following command:
Step 8 Press any key to return to the Network Settings menu.
Note If for some reason you were unable to complete the Linux network configuration as part of the full ISO installation, then complete this task.
After you complete the network configuration on the Cisco StadiumVision Director server, restart the network service to apply the network configuration.
Step 1 Log into the TUI as installer on the server using a directly-connected console or SSH client.
The TUI Main Menu is displayed.
Step 2 From the Main Menu, go to Services Control > Networking > Restart networking .
The network interface eth0 is restarted.
Step 3 Confirm that the command completed successfully.
Step 4 Press any key to return to the Networking menu.
Step 5 Return to the Main Menu.
Note If for some reason you were unable to complete the Linux network configuration as part of the full ISO installation, then complete this task.
To generate the SSL certificate, complete the following steps:
Step 1 From the Main Menu, go to System Settings > Network Settings .
Step 2 Select the Generate certificate file option.
Step 3 When the confirmation warning prompt appears, type Y to continue and generate a new SSL certificate.
To cancel without generating a new certificate, type N .
Step 4 Press any key to return to the Network Settings menu.
Network Time Protocol (NTP) service is required in Cisco StadiumVision Director on the following devices:
NTP provides the most reliable clocking for your Cisco StadiumVision network. NTP helps ensure synchronicity between redundant servers and the Cisco StadiumVision Director remote servers, and optimizes playlist synchronization on the DMPs.
You should verify the NTP configuration for your Cisco StadiumVision servers, since the default NTP source is a Red Hat Linux public pool and might not be the NTP server source that you want to use for your venue.
Configuration of the DMP NTP source is done within the Cisco StadiumVision Director Management Dashboard. As a best practice, the Cisco StadiumVision Director server is already set as the NTP host by default. This does not need to be changed unless the venue requires a different NTP source.
Before configuring NTP on Cisco StadiumVision Director Servers and DMPs, be sure that the following requirements are met:
– If you do not want to use the default public pool of NTP servers for the Cisco StadiumVision servers, you have the IP address or DNS name of the NTP host for your network.
– If you plan to use a public pool of NTP servers, be sure that the servers are reachable from the Cisco StadiumVision network. By default, the ntp.conf file on Cisco StadiumVision Director servers has configured the following Red Hat Linux public pool of servers:
server 0.rhel.pool.ntp.org
server 1.rhel.pool.ntp.org
server 2.rhel.pool.ntp.org
Tip For more information about using NTP pool servers see the Network Time Protocol website at:
http://support.ntp.org/bin/view/Servers/NTPPoolServers
– You have configured the NTP host for the Cisco StadiumVision Director server first.
– You have upgraded the DMP firmware to DMP-4310G Version 5.4.1(RB1) (Build 4544).
For more information about how to upgrade the DMP firmware, see the Cisco StadiumVision Director Software Installation and Upgrade Guide for your release.
– For optimal synchronization, use the same NTP server that is configured for the Cisco StadiumVision Director server. However, it is not required.
– The DMP must not reference an NTP server pool. If the Cisco StadiumVision Director server references an NTP server pool (the default), then select a specific server from that same pool as the NTP server for the DMPs.
– Only IPv4 is supported for the NTP server address on the DMPs.
– The NTP server for the DMPs must not be a load-balanced server.
UDP port 123 is used for communication between the Cisco StadiumVision servers and NTP hosts, and the DMPs and NTP host (by default, this is the Cisco StadiumVision Director server).
For a complete port reference for Cisco StadiumVision Director servers, see the “Port Reference” module of the Cisco StadiumVision Director Software Installation and Upgrade Guide for your release.
When you install or upgrade the Cisco StadiumVision Director or Cisco StadiumVision Director Remote servers, you need to configure the system date and time in the TUI. You also need to configure the time zone.
Note Although you can manually configure the system date and time on your servers when necessary, this should be avoided for your production network.
Note Complete this task only if you do not want to use the default public pool of servers.
Standard NTP server configuration uses the word “server” followed by the Domain Name System (DNS) name or IP address of an NTP server. By default, the ntp.conf file on Cisco StadiumVision Director servers has configured the following Red Hat Linux public pool of servers:
For these servers to be used as a reference clock, they must be reachable from the Cisco StadiumVision network.
If you want to use your own server, be sure to add it and comment out these default pool servers in the ntp.conf file. Otherwise, you do not need to do any further editing of the ntp.conf file in this task.
To set up the NTP host on Cisco StadiumVision servers, complete the following steps:
Step 1 From the TUI Main Menu, go to System Settings > Date and Time Settings > Setup NTP Source .
A confirmation screen to Configure NTP and edit the ntp.conf file is displayed.
Step 2 To open the ntp.conf file for edit, press any key.
The ntp.conf file opens in the vi editor and the cursor is positioned at the end of the last configured NTP server line. If this is not the case, navigate to the server configuration section.
Step 3 To enter INSERT line editing mode, type i .
The vi editor changes to INSERT mode.
Step 4 If you have a server that you want to use as the reference clock source at your site, do the following:
Step 5 To exit INSERT mode and return to vi command mode, press Esc .
Step 6 To save your changes, type :wq .
The configuration is saved and the ntpd service is restarted. Verify that you see the “OK” confirmation that the ntpd has started.
Step 7 To return to the Date and Time Settings menu, press any key.
Configuring the time zone is required for both the Cisco StadiumVision Director and Cisco StadiumVision Director Remote servers.
Note Although there is an option to set the time zone in the Venues interface of the Control Panel on the Cisco StadiumVision Director server, this option is informational only and is also used for proof-of-play reporting. The actual time zone for the venue is configured from the TUI on the remote server.
This section includes the following tasks:
Use this task if you need to find out the time zone code to configure the server’s time zone information.
Note This task provides information only and does not actually configure the time zone.
To find the time zone code for system configuration, complete the following steps:
Step 1 From the Date and Time Settings menu, do the following:
b. Type the number that corresponds to the applicable continent or ocean for the location of the remote server.
c. Type the number that corresponds to the country.
d. Type the number for the time zone (as applicable).
e. When the confirmation of the time zone information that you configured is displayed, type 1 ( for Yes) to accept your settings, or 2 (for No) to cancel (Figure 5).
Figure 5 Time Zone Confirmation Prompt
f. After confirming Yes at the prompt, note the time zone string that is provided.
Figure 6 shows a sample time zone code for America/Los_Angeles.
Figure 6 Sample Time Zone Code
Step 2 Press any key to return to the Date and Time Settings menu.
Step 3 Configure the system time zone using the appropriate code for the server location. See the “Configuring the System Time Zone” section.
Before you configure the system time zone, you should know the following information:
To configure the system time zone so that it persists after restart of the server, complete the following steps:
Step 1 From the TUI Main Menu on the server, go to System Settings > Date and Time Settings > Change System Timezone .
Step 2 At the prompt to edit the system clock file, press any key to continue.
The /etc/sysconfig/clock file is opened for editing.
Step 3 Use the vi editor to specify your time zone. Figure 7 shows an entry for the “America/Los_Angeles” time zone code.
Tip The quotation marks and underscore symbols are required.
Figure 7 Editing the Clock File
Step 4 To exit INSERT mode and return to vi command mode, press Esc .
Step 5 To save your changes, type :wq! .
Step 6 At the prompt, press any key to return to the Date and Time Settings menu.
Step 7 Restart the server to put the time zone changes into effect.
After you configure an NTP server and time zone in the TUI on the server, you must restart the software on the Cisco StadiumVision Director or Cisco StadiumVision Director Remote server.
To restart the Cisco StadiumVision software, complete the following steps:
Step 1 From the TUI Main Menu on the server, do one of the following according to the server that you need to restart:
Cisco StadiumVision Remote distribution is stopped and restarted.
Step 2 When the prompt appears, press any key to return to the Server Administration menu.
Step 3 Return to the Main Menu and exit the TUI.
Note This task is provided as a precaution if you should find it necessary to manually set the system date and time. Manual date and time configuration should be avoided on a production system and NTP service used instead.
To configure the date and time manually, complete the following steps:
Step 1 From the TUI Main Menu on the server, go to System Settings > Date and Time Settings > Change Date and Time .
Step 2 At the confirmation prompt, type Y to continue.
Step 3 Type the new date and time in the format: MMDDhhmm[[CC] YY] [.ss], where:
Step 4 Press any key to return to the Date and Time Settings menu.
Beginning in Release 3.2, you must configure NTP on the Cisco StadiumVision Director server and the DMPs. Granules are no longer used in Cisco StadiumVision Director for timing with the DMPs.
Through default MIB settings on the DMPs, the following values are preset and should not be modified:
Generally, the only values that you might consider changing are the NTP host and the sync interval. These values can be configured both globally and for selected DMPs.
The NTP service is automatically enabled for DMPs and uses the Cisco StadiumVision Director server as the host. If you do not plan to change the NTP host, then you can simply run the Global DMP Settings command to apply the standard configuration on all DMPs in the system.
To configure apply the standard NTP configuration on all DMPs, complete the following steps:
Step 1 Log into the Cisco StadiumVision Director server as an administrator.
Step 2 Go to the Management Dashboard .
Step 3 Go to DMP and TV Controls > Global Settings > Global DMP Settings .
Step 4 Select All Devices and click the Play ( > ) icon to run the command.
All global MIB settings, including the new NTP settings, are sent to all DMPs.
Table 1 provides information about all of the global DMP NTP properties that can be specified in the Management Dashboard to control NTP service on all DMPs.
To modify the standard NTP configuration globally on all DMPs, complete the following steps:
Step 1 Log into the Cisco StadiumVision Director server as an administrator.
Step 2 Go to the Management Dashboard .
Step 3 Click SV Director Configuration > System Configuration > Global DMP Settings > Common (Figure 8).
Figure 8 Common Global DMP Settings for NTP
Step 4 To change the NTP Host, type the IPv4 address of the NTP server that you want the DMPs to reference.
Step 5 (Optional) In the NTP status property, change the IP address and stratum number according to the new NTP host.
Note To skip this field when performing DMP compliance checking, use the $svd_ignore value.
Step 6 (Optional) Change other global NTP properties as required for your environment. Refer to Table 1 .
Step 7 Click the disk icon to Save changes (Figure 9).
Step 8 Go to DMP and TV Controls > Global Settings > Global DMP Settings .
Step 9 Select All Devices and click the Play ( > ) icon to run the command.
All global MIB settings, including the new NTP settings, are sent to all DMPs.
Table 2 describes all of the NTP MIBs and their default values.
Note Under normal operation, only the ntpc.hostname and ntpc.interval MIBs should be modified.
To modify the standard NTP configuration on selected DMPs, complete the following steps:
Step 1 Log into the Cisco StadiumVision Director server as an administrator.
Step 2 Go to the Management Dashboard .
Step 3 Click DMP and TV Controls > DMP Install > Setup NTP (Figure 10).
Figure 10 DMP and TV Controls Setup NTP MIBs
Step 4 From the Common tab in the Command:Setup NTP section, specify the values of the NTP MIB variables according to the recommended and required values in In the Select Devices panel, select the DMPs where you want to setup the NTP service.
Step 5 Click the Play button to set the MIB values on the selected devices.
You can find DMPs that are having problems synchronizing with the NTP server using the DMP compliance check in the Management Dashboard.
Before you can run a valid DMP compliance check for the DMP synchronization status, the “ Synchronized to server svd-ip at stratum n” value of the NTP status global DMP properties must reflect the IP address of your NTP host and its stratum level.
Note Outside of Cisco StadiumVision Director, if you know the DMP IP address, you can find a single DMP’s NTP status using a web browser and going to either of the following URLs:
http://dmpIpAddress
https://dmpIpAddress/get_param?p=*
Find “ntpc.status”. A sample line depicting unsuccessful time synchronization is:
ntpc.status T_STRING Not Synchronized
To verify DMP time synchronization, complete the following steps:
Step 1 Do one of the following to find and confirm the stratum level for the NTP host:
– Log into the TUI and go to Troubleshooting > NTP > Local clock state (Figure 11).
Figure 11 Stratum Field in Local Clock State TUI Output
Tip Alternatively, you can run a DMP Get Status command on one of the DMPs from the Management Dashboard and find the value reported in it ntpc.status MIB value.
– Log into the TUI and go to Troubleshooting > NTP > Show configured peers and clients . Find the configured NTP host in the “refid” field and its corresponding stratum level under the “st” column.
Figure 12 Stratum Field in Show Configured Peers and Clients Output
Step 2 Go to the Management Dashboard and do the following:
See the “Modifying the Standard NTP Configuration Globally on all DMPs” section for more information.
Step 3 Go to the Management Dashboard .
Step 4 Click DMP and TV Controls > Monitoring > Get Status .
Step 5 At the bottom of the screen, go to Status > Compliance .
Step 6 Find ntpc.status MIB and look for information about the synchronization status, such as “Not synchronized.”
If your DMPs are not synchronized, see the “What To Do Next” section.
If you find that DMPs are not synchronized:
For more information about other NTP troubleshooting on your network, refer to the following URL:
http://doc.ntp.org/3-5.93e/debug.html
Note After you verify DMP NTP synchronization, be sure to reset the NTP status field back to $svd_ignore because the stratum value can change.
In Cisco StadiumVision Director Release 3.2, the original Multicast Optimization introduced in Release 3.1 is replaced by Per-Script Multicast Optimization (for up to 20 different scripts) to reduce the number of multicast messages that each DMP must process.
Per-Script Multicast Optimization is designed to reduce the load on DMPs when the following conditions are present in Cisco StadiumVision Director:
The scripts can be running across multiple venues, scripts running in a single venue, or running in systems without Cisco StadiumVision Director Remote servers.
Table 3 provides a summary of the two different multicast optimization features supported in Cisco StadiumVision Director.
Multicast Optimization1 |
||||
Per Script |
1.For information about per-site multicast optimization in Cisco StadiumVision Director Release 3.1, see the “Multicast Optimization for Remote Venues” topic in the “Configuring Cisco StadiumVision Director for Multiple Venue Support” module of the Cisco StadiumVision Director Server Administration Guide, Release 3.1. 2.If you are running more than 20 scripts, then the first 20 scripts operate using per-script multicast channels, and the additional scripts are run over the global multicast host port. |
Benefits of Per-Script Multicast
In releases of Cisco StadiumVision Director 3.1 and earlier, the server uses a single multicast channel for all DMPs. In Release 3.2, you can configure multiple multicast channels, over which the server sends only the multicast messages needed for a particular event script for up to 20 scripts.
If you are running more than 20 scripts, then the first 20 scripts operate using per-script multicast channels, and the additional scripts are run over the global multicast host port.
Figure 13 shows this message separation. Each DMP goes from seeing four packets to seeing two. More importantly, each DMP now only has to process one XML payload, which is important when the XML payloads are sizeable.
Figure 13 Multicast Messaging With and Without Per-Script Multicast Optimization
All DMPs, including those associated with a Cisco StadiumVision Director Remote server, listen on these per-script multicast channels.
For messages that apply to multiple event scripts, the message is duplicated and sent to each multicast channel. Therefore, this feature can increase the load on Cisco StadiumVision Director and Cisco StadiumVision Director Remote servers (increasing the number of messages sent and copying of messages) as a tradeoff for reducing the number of messages seen and processed by DMPs. However, this load is expected to be negligible.
Cisco StadiumVision Director uses multicast messages for DMP control-plane operation. Cisco Connected Stadium network design assigns the following multicast group addresses for use by Cisco StadiumVision Director:
Multicast addressing is configured using registry keys from the Cisco StadiumVision Director Management Dashboard.
Table 4 describes the registry keys in Cisco StadiumVision Director that control the multicast configuration.
Before you configure multicast ports, be sure that the following requirements are met:
– For a summary of all of the input and output ports in use by Cisco StadiumVision Director and Cisco StadiumVision Director Remote, see the “Appendix B: Port Reference” module in the Cisco StadiumVision Director Software Installation and Upgrade Guide, Release 3.2 .
– For more information about the recommended multicast addressing for the Cisco Connected Stadium network, see the Cisco Connected Stadium Design Guide available from your Cisco Systems representative.
The global multicast host port is used by Cisco StadiumVision Director to send messages to DMPs when they are not part of a script, when per-script multicast is disabled, or when the number of scripts running exceeds to configured maximum of per-script multicast ports.
It is configured in the “MulticastHostPort” registry key in the Management Dashboard.
Note The default value currently uses the address 239.192.0.254:50001 and should be changed to a network address in the range 239.193.0.0/24.
To verify or configure the multicast addressing for Cisco StadiumVision Director, complete the following steps:
Step 1 From the Management Dashboard, select Tools > Advanced > Registry .
Step 2 Scroll to the “MulticastHostPort” registry key in the Parameters list and confirm the entry for the registry.
Step 3 Click on the value field and specify a multicast address in the range 239.193.0.0/24 and port number.
Note Be sure to use the value that is configured in your Cisco Connected Stadium network for Cisco StadiumVision Director control messages and include the :port. The recommended default is :50001.
By default, Per-Script Multicast Optimization is disabled and the Cisco StadiumVision Director server sends all communication over the MulticastHostPort address directly to all DMPs and Cisco StadiumVision Director Remote servers, including all remote DMPs.
To take advantage of per-script multicast optimization it must be enabled for systems being upgraded to Release 3.2.0-489. Otherwise, it is enabled by default for new installations.
To configure per-script multicast, complete the following steps:
Step 1 From the Management Dashboard, select Tools > Advanced > Registry .
Step 2 To enable per-script multicast, change the values of the following registry keys:
Note Be sure that these ports do not overlap with other multicast ports in use on your network.
Step 4 Reload the Flash template on all DMPs:
a. From the DMP and TV Controls dashboard drawer, navigate to and select the following command: DMP and TV Controls > DMP Install > Stage Template .
b. Select all of the DMP devices where the command should be applied.
c. Click the Play button to run the command on the selected devices.
Step 5 To verify the configuration:
a. Start and stop event scripts and change states.
b. Verify that the multicast port that the DMP is listening on is one of the per-script ports (50080-50099 by default), rather than the global multicast hostport (50001).
If the scripts do not sart and stop, see the “Troubleshooting Per-Script Multicast Configuration” section.
This section includes information about troubleshooting the following behaviors when per-script multicast optimization is enabled:
Scripts Unable to Start or Stop
Verify that the multicast packets are reaching the DMPs using any or all of the following methods:
Tip It is valuable to know the multicast group/port that a specific DMP should be listening on. This can be validated using the dmpconfig debug feature, by going to the URL:
http://svd-ip:8080/StadiumVision/dmpconfig/000000000000?ipaddr=x.x.x.x, where
x.x.x.x is the IP address of the DMP to be debugged.
In the XML output provided, you will see the multicast IP address and port in use.
DMPs rebooting or becoming unresponsive while per-script multicast is enabled is most likely due to some multicast video port overlap with the ports used for multicast control.
After you have configured the system settings for your Cisco StadiumVision Director servers, be sure to do the following:
The centralized Cisco StadiumVision Director server is configured by default to use a global account for communication with all Cisco StadiumVision Director Remote servers to support monitoring of venues from the Management Dashboard. Using the default configuration, you can specify a common password to be used by all Cisco StadiumVision Director Remote servers.
You can change the default configuration and specify a unique password for each remote server. To do this, you must modify the global credential on the Cisco StadiumVision Director server, and then configure a password in the Venues interface from the Control Panel on the Cisco StadiumVision Director server.
Whether you are using a common or unique password, the remote server must be configured to use the same password that is configured on the Cisco StadiumVision Director server for that venue.
For more information about configuring Cisco StadiumVision Director to support remote servers and multiple venue support, see the following modules:
– Configuring Cisco StadiumVision Director Remote Servers.
– Configuring Cisco StadiumVision Director for Multiple Venue Support.