Table Of Contents
Video SLA Assessment Agent 3.1
Installation Guide
Overview of VSA Agent
System and USB Drive Requirements
Port Requirements
Installing VSA Agent on the USB Drive
Creating a Bootable USB Flash Drive for VSA Agent
Booting from the USB Drive
Configuring the VSA Agent System IP Address
Troubleshooting the VSA Agent Installation
Appendix: Tested Systems and USB Drives
Tested Systems
Tested USB Drives
Related Documentation
Video SLA Assessment Agent 3.1
Installation Guide
This guide is for Cisco Prime Collaboration 9.0 users.
Overview of VSA Agent
Prime Collaboration uses VSA Agent to assess a network's readiness to deploy or upgrade Cisco TelePresence systems. VSA Agent provides network path characteristics, such as latency, jitter, and packet loss measurements, prior to deployment. By automating the assessment process, VSA Agent accelerates and simplifies deployment. We recommend that you review "Diagnostics for Video Endpoints" in the Cisco Prime Collaboration 9.0 Network Monitoring, Reporting, and Diagnostics Guide.
VSA Agent tests are run between two systems: source and destination. These systems must reside on the same topology as the source and destination video feeds (the Cisco TelePresence System). VSA Agent must be deployed at both the source and destination systems (see Figure 1 for the deployment topology).
Figure 1 VSA Agent Deployment Topology
System and USB Drive Requirements
You can install VSA Agent 3.1 on the USB drive only. Table 1 lists system and USB drive requirements for running the VSA Agent software.
Table 1 System and USB Drive Requirements
Parameter
|
Requirement
|
Processor
|
Intel Pentium 4 or higher
|
CPU speed
|
2 GHz or higher
|
RAM size
|
2 GB minimum
|
Ethernet
|
1 Gig
|
Swap size
|
Not required.
|
Disk space
|
Not required; VSA Agent runs from the USB drive.
|
USB flash drive
|
16 GB to 32 GB
Note  Do not use a USB drive with more than 32 GB of memory.
|
USB version
|
2.0
|
USB port on the system
|
2.0
|
Recommended USB manufactures
|
•Kingston
•Patriot
Note Do not use partitioned USB drives, such as SanDisk USB drives, for VSA agent installation.
|
Note The display driver, USB driver, and Intel Chipset Device Software on the system must support the Fedora Linux operating system. See Appendix: Tested Systems and USB Drives for all tested systems and USB drives.
Port Requirements
Table 2 lists the ports that VSA Agent uses. These ports must be open in both directions on the source and destination systems on which VSA Agent is installed.
Table 2 Port Requirements
Port Number
|
Protocol
|
22
|
TCP
|
80
|
TCP
|
123
|
UDP
|
5060
|
TCP
|
8080
|
TCP
|
8081
|
TCP
|
8090
|
TCP
|
16384-16788
|
UDP
|
Make sure that the ICMP ping and traceroute commands are enabled between:
•VSA Agent systems
•VSA Agent systems and the Prime Collaboration Assurance server
Installing VSA Agent on the USB Drive
VSA Agent installation consists of two steps:
1. Creating a Bootable USB Flash Drive for VSA Agent
2. Booting from the USB Drive
We recommend that you install and test VSA Agent in a lab environment before you test it in a production environment.
If you are installing VSA Agent 3.1 software on multiple USB drives, make sure that the same VSA Agent version is installed on all systems.
Before You Begin:
1. Verify the following:
•A minimum 16 GB USB drive is available for the installation.
Caution Do
not use a USB flash drive with more than 32 GB of memory.
•USB 2.0 port is available for the installation.You cannot install VSA agent on a USB 3.0 port.
•Administrator privilege is available on the system on which you plan to use the USB drive.
2. From the Cisco Prime Collaboration software download site, download the following images to the Windows system on which you plan to install VSA Agent:
•pc90-vsaa-creator-3.1.0.0-FC14.zip
•pc90-Fedora-14-i686-Live-Desktop.iso
Note You must have a valid Cisco.com user account to download the files.
Creating a Bootable USB Flash Drive for VSA Agent
To create a bootable USB flash drive:
Step 1 As administrator, log into the system on which you have downloaded the zip files from the software download site.
Step 2 Unzip the pc90-vsaa-creator-3.1.0.0-FC14.zip file.
Step 3 Insert the USB drive.
Step 4 Navigate to the directory where you have extracted the pc90-vsaa-creator-3.1.0.0-FC14.zip file.
If you are using Windows 7 operating system, you must run the file as an administrator (right-click the file and select the Run as administrator option).
Step 5 Open a command prompt and enter buildkey to format the USB drive.
Step 6 In the Buildkey window, select the USB device and click Browse for Fedora 14.
Step 7 Navigate to the directory where you have downloaded the pc90-Fedora-14-i686-Live-Desktop.iso file.
Step 8 Choose the pc90-Fedora-14-i686-Live-Desktop.iso file and click Accept.
Step 9 Click Install VSAA.
Step 10 Enter y to start the installation.
Step 11 Press any key to continue after the installation is complete.
Booting from the USB Drive
After you install VSA Agent on the USB drive, you must then boot the system from the USB drive. The system must have wired network connection. The wireless connection should be turned off.
To boot the system from the USB drive:
Step 1 Reboot the system and press the F12 key while rebooting.
Step 2 From the list of devices that allow you to boot, choose the USB drive.
You are logged in automatically.
Step 3 At the command prompt, switch user to root using the following command:
su -
Step 4 Enter the password tpc1sc0.
Step 5 Click the terminal icon and verify the VSA Agent installation using the following command:
The following is sample output of the command:
root 6996 1 0 May22 pts/3 00:00:00 /usr/local/mtaa/bin/vsaaTrouteSvc
root 9276 1 0 May23 pts/3 00:00:05 bin/mtaaSoapServer
root 9281 1 0 May23 pts/3 00:00:00 bin/mtaaHttpServer
root 9286 1 0 May23 pts/3 00:16:59 bin/mtaaSipServer
root 9291 1 0 May23 pts/3 00:22:47 bin/mtaaActiveqos
root 9295 1 0 May23 pts/3 01:42:03 bin/mtaaPassiveqos
root 14004 13987 0 11:50 pts/1 00:00:00 grep --color=auto mtaa
You can also verify the status of VSA Agent processes by entering the IP address of the VSA Agent system in a web browser:
http://localhost
or
http://Agent_IP_Address
See Troubleshooting the VSA Agent Installation if the processes are not running.
Step 6 Configure the VSA Agent IP address (see Configuring the VSA Agent System IP Address).
Caution The USB drive contains the live file system. To avoid data corruption, be sure to shut down the VSA Agent system in the proper manner.
Configuring the VSA Agent System IP Address
You can configure the VSA Agent system IP address in either of two ways:
•DHCP IP Address—The VSA agent system IP address is obtained automatically. Use the command ifconfig to find the IP address of the VSA Agent system. You can log into the VSA Agent system using SSH with the username root and the password tpc1sc0.
•Static IP Address—The VSA Agent system IP address must be configured manually.
To configure the static IP address on the VSA Agent system:
Step 1 Boot the VSA agent system using the USB drive. See Booting from the USB Drive.
Step 2 Choose System > Preferences > Network Connections.
Step 3 In the Query dialog box, enter the root password tpc1sc0, and click OK.
Step 4 In the Network Configuration properties window, double-click a device name.
Step 5 In the Ethernet Device properties window, change the interface from DHCP to STATIC and enter the required data.
If you change settings remotely, be sure to enter the values very carefully. You must have physical access to the VSA Agent system if you enter incorrect values.
Step 6 After the configuration, reboot the system and verify the IP address configuration using the command ifconfig.
Also, you must verify whether you can reach the default gateway from the VSA agent system.
You are now ready to run the network readiness assessment using Prime Collaboration. See "Diagnostics for Video Endpoints" in Cisco Prime Collaboration 9.0 Network Monitoring, Reporting, and Diagnostics Guide for the procedure.
Troubleshooting the VSA Agent Installation
Table 3 Troubleshooting VSA Agent Installation
Issue
|
Description/Workaround
|
VSA agent processes are not running
|
1. Use SSH to log into the VSA Agent system as root with the password tpc1sc0.
2. Restart VSA Agent using the following command:
/usr/local/mtaa/bin/restart --ip localhost --force
To restart another VSA Agent system, use the following command:
/usr/local/mtaa/bin/restart --ip Agent_IP_Adress --force
|
USB creation fails
|
The following message appears while installing VSA Agent on the USB drive:
Fedora-14-i686-Live.iso selected
Verifying SHA1 of LiveCD image...
Extracting live image to USB device...
There was a problem executing the following command: `tools\7z.exe x
""C:/installs/VSAA/liveusb-creator-2.7.15/liveusb-creator-2.7.15/Fedora-9-i686-Live
.iso"" -x![BOOT] -y -oE:`
A more detailed error log has been written to 'liveusb-creator.log'
LiveUSB creation failed!"
Make sure that you have administrator privilege on the system on which you plan to install VSA Agent on the USB drive.
|
Appendix: Tested Systems and USB Drives
Tested Systems
Table 4 list the systems that are compatible with Fedora Linux 14 and tested for VSA Agent 3.1.
Table 4 Recommended System Models for VSA Agent 3.1
Manufacturer
|
Recommended System Models
|
Not Recommended System Models
|
ASUS
|
—
|
ASUS K50IJ-BNC5
|
Dell
|
•Inspiron 1000, 1100, 1420, 1501, 1520, 1525, 1526, 4150, 5100, 510M, 150, 5160, 6000, 600M, 630M, 6400, 640M, 700M, 8100, 8200, 8500, 8600, 9100, 9200, 9300, 9400, B130
•Precision M60, M65, M6300, M6400
•Latitude C610, C800, C840, CSx
•Latitude D400, D420, D505, D510, D600, D610, D620, D800, D810, D820, D830
•Latitude X1, X300
•Vostro 1310
•XPS gen 2, M1210, M1330, M1530
|
•Studio Laptop S15Z-2249CPN
•Studio Laptop S1558-5691MSL
•Inspiron Laptop IM501R-1212PBL
|
Gateway
|
—
|
•Gateway ID49C07u
•Gateway NV53A24u
|
HP Compaq
|
•Compaq R3240US
•Compaq Presario X1400, X1010AL
•Compaq Presario V2000, V2617LA, v2335us, V3018cl
•HP Compaq 6510b
•HP Compaq 8510w
•HP Compaq nc4200, nc6000, nc6120, nc6120, nc8230, NC8000
•HP G62-225DX
•HP L2000
•HP Compaq nw8000, nw8440
•HP Compaq nx6110, nx7300, nx9030
•HP nx6110, nx6125, nx7010, nx7400, nx9010
•HP DV1000, dv1170ca, dv1227us, dv2000, DV2118la, dv2125, DV8000, dv8491ea, DV9000t, dv9013z, HDX X18-1180US, dv9500t
•HP Pavilion dv1000, dv6000z, dv6636nr, dv6650ee, dv8040, dv9010us, DV9225US, dv9310us, DV9375eu
•HP Pavilion tx1000z
•HP Pavilion ZE1230, ZE2315us, ZE4430US, ZE4805us, zx5030EA, zv5340us, ZV6015us, zd8000
|
•HP Pavilion Laptop (SKU: 9999133100050009 and 9983204)
•Compaq Presario Laptop CQ62-215DX
•HP Pavilion Laptop dv4-2145dx
|
IBM and Lenova
|
•Thinkpad R30, R31, R40, R50, R52
•Thinkpad X20, X21, X24, X30, X31, X40, X61
•Thinkpad Z60
•Thinkpad T23, T30, T40, T40P, T41, T41P, T42, T42P, T43, T60, T60P, T61P
|
—
|
Sony
|
•Vaio VGN-FS790B
•Sony Vaio PCG-FJ-170,PCG-FVR28, PCG-FX310, PCG-FX702, PCG-GRT896HP,
•PCG-GRX520, PCG-GRX616MP, PCG-K315S, PCG-N505VE, PCG-TR2A, PCG-TR3A, PCG-TR5F, PCG-V505ECP, PCG-VGN-A170P, PCG-VGN-B1XP, PCG-VGN-C140G, PCG-VGN-CR11z7R, PCG-VGN-fe11s, PCG-VGN-FE21S, PCG-VGN-FE31Z, PCG-VGN-FS315H, PCG-VGN-FS315H, PCG-VGN-FS640/W, PCG-VGN-FW11ZRU, PCG-VGN-S3HP, PCG-VGN-S3XP, PCG-VGN S580, PCG-Z505C/BP, PCG-Z600NEK
|
•VAIO Laptop VPCS111FM/S
•VAIO Laptop VPCEB23FM/BI
|
Toshiba
|
Toshiba Satellite C655-S5049 (Fast boot loader F-12)
|
•Toshiba Satellite U505-S2008
•Toshiba Satellite L645D-S4030
|
Tested USB Drives
Table 5 list the USB drives that are tested for VSA Agent 3.1.
Table 5 Recommended USB Drives for VSA Agent 3.1
Recommended Manufactures
|
Not Recommended Manufacturer
|
•Kingston
•Patriot
|
SanDisk
|
Related Documentation
See Cisco Prime Collaboration 9.0 Documentation Overview for a list of Prime Collaboration guides.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2012 Cisco Systems, Inc. All rights reserved
Feedback
