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: August 12, 2014
The StadiumVision Mobile Streamer Text Utility Interface (TUI) provides a console-based text interface for use by system installers and on-site troubleshooting personnel. The TUI can be used to perform routine system tasks such as modifying system configurations, changing passwords, and checking system logs. Remote TAC access and troubleshooting can both be facilitated from the TUI in the event of a Cisco StadiumVision Mobile Streamer outage or failure.
This module contains information that system administrators will use to configure and maintain the StadiumVision Mobile Reporter, and contains the following sections:
To access the TUI, you need either physical console access or an SSH client such as PUTTY. Log in from the console or over SSH with the following credentials:
username = installer
password = cisco!123
You will be prompted to change the password on your first successful login. You also have the option of changing the password via the TUI.
Several of the TUI options open server system files for you to modify using the Unix system vi editor. The following configuration files are editable from the TUI:
Before modifying configuration files, you should be familiar with the simple editing techniques used within the vi editor. Table 1 describes some of the more common vi Editor commands.
|
|
---|---|
Figure 1 shows an overall view of the StadiumVision Mobile Streamer TUI. The following sections provide a brief description of each TUI menu item.
Figure 1 Cisco StadiumVision Mobile Streamer TUI Hierarchy
Figure 2 Cisco StadiumVision Mobile Streamer TUI Hierarchy (continued)
Allows for configuration of network devices and the DNS server
Manually edit network config file
The system date, timezone, and NTP server address should be set during the installation process. If these items were not configured during installation, it is critical to configure these items to avoid time drift and to ensure accurate reporting.
Allows for setting the timezone. Choose a number next to the correct timezone.
Allows for setting the Network Time Protocol (NTP). Enter an IP address for a valid NTP server.
Displays network information for eth0 and eth1 ports, hosts file, DNS information, and NTP server information.
Enables a Cisco TAC representative to remotely troubleshoot the StadiumVision Mobile Streamer. This will allow for remote shell access which will be used for remote troubleshooting purposes. Always disable this access once you complete troubleshooting the system.
Changes the Java Management Extensions password, which may be used to allow JMX clients to monitor and troubleshoot the Streamer.
Displays the installed software version.
Provides a way to upgrade the StadiumVision Mobile Streamer software by choosing an ISO image from a list. See the “Upgrading StadiumVision Mobile Streamer Using the Web Browser User Interface” section in the Cisco StadiumVision Mobile Reporter and Cisco StadiumVision Mobile Streamer Installation and Upgrade Guide .
On a nightly basis, backups are done of the Streamer configuration files. The file archives are automatically removed from the StadiumVision Mobile Streamer after 20 days. See the “StadiumVision Mobile Streamer Log” section for more information about backup and restore procedures.
Allows for connectivity testing by pinging an IP address.
Log files are written as events transpire. The log files are available to be downloaded via HTTP. The log files are intended for a Cisco TAC representative to aid in troubleshooting. The log files are rotated out of the system, typically after 20 days.
– System console messages (/var/log/messages)
– Authentication/Authorization logs (/var/log/secure)
– Authentication/Authorization logs