Guest

Preview Tool

Cisco Bug: CSCut07779 - umsdevice running high cpu usage in case of hwid mismatch

Last Modified

Jan 04, 2017

Products (1)

  • Cisco Video Surveillance Manager

Known Affected Releases

7.6(0.75)

Description (partial)

Symptom:
Camera status is critical and Camera status Configuration details shows Camera admin state Configured value as enabled and in Primary MS value as disabled. Camera Status history show the following alert -

Camera Hardware Id in Media Server does not match with the camera

In this case camera's identity has been changed since camera is added to VSM. This could happen due to camera IP address changed due to DHCP or somebody have physically replaced the existing camera with newer one. CPU usage of the umsdevice process associated with the camera is greater than 90%.

Conditions:
Camera's identity has been changed since the camera is added to VSM. This could happen due to camera IP address changed due to DHCP or somebody have physically replaced the existing camera with newer one.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.