As a result of some experiements I have done to try and get my iphone or android to work with our VSM server in the lab here, I wrote some php to offer RTSP links out in an easy to find location.
I offer it here to others if they are trying to do something similar.
To use this, copy the file into the /usr/BWhttpd/root/htdocs directory and use the command chmod +x mobile.php to make it executable.
you can then go to the url http://<server address>/mobile.php and you will be presented with a list of available RTSP links.
Scenario 2:
Problem:
User have a new installation of Cisco VSM and VSOM 6.3.1 VSOM and VSM running on 1 server and a second server running just VSM. The health monitor doesnt show any alarms even when i know i have some cameras and streams down. Anyone else seen this and know the fix for it.
Solution:
I think I know what's going on with your Health Monitoring Dashboard issue. Let me start by providing some background on how this
system works. The Health Monitoring Dashboard is a GUI representation of SNMP traps
received by the VSOM server. As such, it only changes device states if it receives a SNMP trap for a degraded, failed or offline
condition. VSOM does not poll the devices, it only listens. The end devices (cameras) do not send these SNMP traps, instead
relying on the VSM Sserver to communicate a change in status of the proxy for a camera.It is likely the VSMS server could not
resolve the hostname of the VSOM server, so the VSOM server and Health Monitoring Dashboard did not receive the trap. The receipt
of SNMP traps is further complicated by the fact that registration of VSOM to the media servers is not by IP address, rather
hostname, and if the media server cannot resolve the host name, traps are not received by the VSOM console. This has the potential to leave us in a position where the end user may not be aware of offline devices as the default state is UP rather than UNKNOWN. There is a defect written to address this scenario through a redesign such that VSMS can use the IP address rather than hostname to send SNMP traps ( CSCtj68042). From each media server, ensure that the VSOM hostname is resolvable to an IP address.
This can be done by updating the DNS server (if your network is using one) or by editing the "/etc/hosts" file on each of the media servers to including a hostname to IP address mapping for the VSOM server.
Alternatively, the media server's
/usr/BWhttpd/conf/snmpd.conf
can be manually updated to replace the VSOM hostname with the IP address.
Here is an example of the hosts file on the media server:
ese-mediasvr-cc1:/usr/BWhttpd/etc # cat /etc/hosts
#
[snip]
#
172.26.157.7 ese-mediasvr-cc1.cisco.com
192.0.2.137 ese-mediasvr-cc1.cisco.com ese-mediasvr-cc1
Using Yast, manually enter the host for the VSOM server into /etc/hosts on the media server
ese-mediasvr-cc1:/usr/BWhttpd/etc # cat /etc/hosts | grep 192.0.2.138
192.0.2.138 ese-vsom-vm-cc1.cisco.com
After adding the entry into /etc/hosts and restarting the server through the management console, the alarms should once again be
received by VSOM and Health Monitor should report cameras which are offline. So in summary, verify by pinging the hostname of the
VSOM server from each VSMS server in the network. For any which are unresolved by hostname, either change DNS entry to map
hostname to IP, or using Yast or vi, edit /etc/hosts to map IP to hostname for VSOM on each media server, (or the media server's
/usr/BWhttpd/conf/snmpd.conf can be manually updated to replace the VSOM hostname with the IP address.)
