Cisco Cisco StadiumVision Mobile Streamer Manuel De Maintenance
© 2012 Cisco Systems, Inc. All rights reserved.
Page 90 of 103
Chapter 5 Troubleshooting
This chapter provides basic troubleshooting information for resolving problems you
may encounter with DMPs and the attached TVs.
may encounter with DMPs and the attached TVs.
Auto-Registration Issues
Follow these step by step directions to follow the auto-registration flow and look for
common problems. Several steps involve viewing the relevant log files. These log
files can be viewed from either TUI or from the unix shell. Viewing them from the
TIU can be challenging as the ability to filter on the fly is limited.
common problems. Several steps involve viewing the relevant log files. These log
files can be viewed from either TUI or from the unix shell. Viewing them from the
TIU can be challenging as the ability to filter on the fly is limited.
Step 1: Make sure the DMP is in its factory default state. This can be ensured by
depressing the reset button on the back of the DMP for at least 10 seconds, or until
the LED on the Ethernet port turns solid green.
depressing the reset button on the back of the DMP for at least 10 seconds, or until
the LED on the Ethernet port turns solid green.
Step 2: Confirm that the DMP receives an IP address via DHCP. When an IP
address is received the DMP turns off the red LED on the front and displays the IP
address on the monitor. Auto-registration does not work with static IP addressing.
address is received the DMP turns off the red LED on the front and displays the IP
address on the monitor. Auto-registration does not work with static IP addressing.
Step 3: Establish an ssh session to the DMP and run the udhcpc command. Verify
the option 43 URL received from the DHCP server. This URL appears on the last
line of the output. Verify that it contains the IP address of your Cisco StadiumVision
Director server, and that it is formatted as per the documentation:
the option 43 URL received from the DHCP server. This URL appears on the last
line of the output. Verify that it contains the IP address of your Cisco StadiumVision
Director server, and that it is formatted as per the documentation:
[guest@svd1 ~]$ ssh
root@10.10.99.20's password: <password can be found in SVD registry>
4310 10.10.99.20 # udhcpc
udhcpc (v1.15.2) started
/sbin/ifconfig eth0 0.0.0.0
Sending discover...
Sending select for 10.10.99.20...
Lease of 10.10.99.20 obtained, lease time 86400
/sbin/ifconfig eth0 10.10.99.20 netmask 255.255.255.0
/sbin/route del default gw 0.0.0.0 dev eth0
route: SIOCDELRT: No such process
/sbin/route add default gw 10.10.99.1 dev eth0
adding domain cisco.com
Calling vendor notification: http://10.194.172.82:8080/StadiumVision/dmp_reg
4310 10.10.99.20 # udhcpc
udhcpc (v1.15.2) started
/sbin/ifconfig eth0 0.0.0.0
Sending discover...
Sending select for 10.10.99.20...
Lease of 10.10.99.20 obtained, lease time 86400
/sbin/ifconfig eth0 10.10.99.20 netmask 255.255.255.0
/sbin/route del default gw 0.0.0.0 dev eth0
route: SIOCDELRT: No such process
/sbin/route add default gw 10.10.99.1 dev eth0
adding domain cisco.com
Calling vendor notification: http://10.194.172.82:8080/StadiumVision/dmp_reg
Step 4: Ping the DMP from Cisco StadiumVision Director to confirm that there is
two-way IP connectivity between them.
two-way IP connectivity between them.
Step 5: Check the Apache logs on Cisco StadiumVision Director to verify that the
auto-registration URL that the DMP received as a DHCP option actually reaches
Cisco StadiumVision Director. The following shows that URL
/StadiumVision/dmp_reg posted by 10.10.99.20 has been received.
auto-registration URL that the DMP received as a DHCP option actually reaches
Cisco StadiumVision Director. The following shows that URL
/StadiumVision/dmp_reg posted by 10.10.99.20 has been received.