02-23-2011 07:54 AM
I 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 no the fix for it.
Thanks
Problem Resolved.
Solved! Go to Solution.
02-24-2011 01:53 PM
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 VSMS
server 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.)
I hope that helps,
Jim
02-24-2011 11:33 AM
I have seen this problem similar to the configuration you described. I have VSOM 6.3.1 running on a 1RU and VSM running on twelve 4RU servers and the alarms particularly end point errors doesn't show up either. Oddly enough I have a remote site with a 4RU running VSOM and VSM and the alarms show up in this configuration.
02-24-2011 02:46 PM
Jim,
Thank you very much for the very detailed response. I understood most of what you outlined but I got lost with the commands where you manually enter the hostname for the VSOM server into /etc/host on the media server. I am new to linux so I am mostly working mostly through YaST. As per your instructions I SSH into each media server and tried to ping the hostname of the VSOM and received no responses. I am going to give your recommendation a try so if possible can you please outline how to do it through the YaST GUI? I believe I am in the right spot when I checked in YaST (Network Services>Hostnames) but I am not sure.
02-25-2011 08:23 AM
Ainsley, yes you are in the right spot.
Yast menu---- then in the Hostnames. Click add--- enter name of server then ip address then the alias name ie.... vsms1 10.1.2.3 vsms1
Click save or add i cant remember for sure and dont have one in front of me righ this second.
Try that and let me know
02-25-2011 02:19 PM
Greg,
Thank you for following up. I was added the VSOM information (IP/Hostname) to the VSMS and I was able to ping the VSOM from the media server however the endpoint errors from known offline cameras did not show up in VSOM. I also added the hostname of the VSMS to VSOM and still nothing. Any ideas what I am missing? I also looked for the snmpd.conf file and did not find it in the conf folder. I noticed that there is a SNMP trap configuration screen in the camera (CIVS-IPC-2531) menu, does this have to be configured first in order for it to work?
Thanks.
02-25-2011 02:32 PM
Ainsley,
Try this
02-25-2011 02:38 PM
You are the man Greg. It worked!
Thank you so much!
02-25-2011 02:45 PM
No im not "the man" Jim is the man it took a TAC case with him yesterday for it to work for me. I guess he posted to this after our TAC case.
Maybe this will help others out there. so they can get it quickly resolved also like yourself
Thanks
02-24-2011 01:53 PM
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 VSMS
server 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.)
I hope that helps,
Jim
02-24-2011 03:33 PM
Yes Jim was "the man" that gave me the fix for this.
Also i think the snmp stop restart also.
Thanks
02-25-2011 03:12 PM
Thanks for the vote of confidence, Greg. You are correct, I saw this thread shortly after assisting in your TAC case. The purpose of the Cisco Support Community is to help foster community support to help spread knowledge and solutions to common issues. Your reply in this thread is demonstration that this support community is working.
Thank you Sir!
Jim
02-25-2011 03:16 PM
And a very special thanks to you Jim for the top notch explanation and resolution.
08-08-2013 12:07 PM
Do you guys know if this issue was fixed in VSM6.3.2 or 6.3.3? Going throught the release notes now.
Thx
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide