vsm 7.5 camera problems

[amurgescu]

Hi,

We are trying to install a VSM 7.5 with 4 attached cameras (2 x 6000P & 2x4500E).

I have installed all servers into the same virtual machine, and this virtual machine is located alone on a physical server (C220 M3) (Media Server & Management Console & Operations Manager)

the 2 x 6000P cameras are working fine, but we cannot setup the 2 x 4500E Cameras.

They both have an error: config_mismatch_status 

Device : CV3

Server : VsomServer

Description : Stream configuration in VSOM is not the same as in media server VsomServer

 

Please help

[Sergey Muravjev]

Hi,

Try to read log tail -f /media1/BWhttpd/logs/ims.log while adding cameras. Usually there are written all the problems when installing a new camera. 

Maybe this is codec/resolution/framerate mismatch

[amurgescu]

Hi,

There is not such path in my server.(BWhttpd/logs/ims.log)

, but we can see the logs into Operations Manager. I deleted the camera, and then added again (same error):

[Sergey Muravjev]

In ims.log more raw data. Log in VSMS/VSOM not so informative...

Try to find file in bash:

find / -name ims.log

[amurgescu]

ok, found it.

indeed, there is a lot of raw data. Please see the attached file.

[Sergey Muravjev]

2014-09-23 16:56:37.292 [ umsdevice(7205).50a76719-b190-447b-9f85-ae6ea03acf80 DEVICE=1 <Device.cxx:5294> ] Medianet config failed [Unable to update server entries on camera (failed to parse DiscoverySetting with Auto Discovery.). Please verify camera firmware version  supports medianet feature.]

Maybe unsupported firmware version on camera? Can you update firmware version om these cameras?

Are you tried add camera manually, not with medianet?

[amurgescu]

The camera is supporting medianet:

General Information

ID: 1 Name: CIVS-IPC-4500E-CV1 Current Time: 09/23/2014 17:30:19

Serial Number: FYO.............. Firmware: 3.1.2-18 (08/08/2012) Codec: 7.7 (06/01/2012) Part Number: 74-................. Top Assembly Revision: A0

most of time I tried to add cameras manually.

The log is from a manual add.

I can access these cameras through web browser. I can see image from them this way, and I can change settings. 

[Scott Olsen]

You still need to upgrade your 4500Es. 

According to the release notes for 7.5 (and I'm assuming onward), the required firmware version for these endpoints is at least:

3.2.3-218

According to the data you provided, They are at 3.1.2-18.  Update the firmware and you should be good to go.

Cheers,

Scott.

[Bogdan Voiculescu]

Hi Scott,

We upgraded the firmware to 3.2.4-223 and the problem still persist. We tried againg manual adding/removing the cameras but still no luck.

Thanks.

[Scott Olsen]

I'm assuming you've tried running a Configuration Repair, or a Configuration Replace on the affected endpoints?

Is there anything else throwing an error in your setup?  Anything indicating a problem with the VSMS instance?

Scott.

[Bogdan Voiculescu]

Hi all,

Thanks for the support. We managed to reinstall the cameras. After several attempts repair/replace etc. the cameras are working.

We didn't changed anything so it is very strange.

Thanks.

[Raghav-Rao]

what type of templates is been used?

what type of drivers is been used?

can you go to system setting --> camera --> select the camera --> general (take snap shot)

can you go to system setting --> camera --> select the camera --> Status --> Device status (take snap shot)

can you go to system setting --> camera --> select the camera --> Status --> status history (take snap shot)

[Raghav-Rao]

what type of templates is been used?

what type of drivers is been used?

can you go to system setting --> camera --> select the camera --> general (take snap shot)

can you go to system setting --> camera --> select the camera --> Status --> Device status (take snap shot)

can you go to system setting --> camera --> select the camera --> Status --> status history (take snap shot)

what is the status of the Server? Go to System Settings --> Server --> select the Server --> Status --> Status History (take snap shot).

[Bogdan Voiculescu]

Update from log:

5:37:38.183 [ umsdevice(30706).b3f49cf4-5535-4dfb-aed2-39332d2f086b BE_PROXY=1 <Proxy.cxx:144> ] Unable to configure or handshake with the device
2014-09-30 15:37:38.183 [ umsdevice(30706).b3f49cf4-5535-4dfb-aed2-39332d2f086b BE_PROXY=1 <Proxy.cxx:1018> ] Proxy sending config ack (fail).
2014-09-30 15:37:38.183 [ umsdevice(30706).b3f49cf4-5535-4dfb-aed2-39332d2f086b BE_PROXY=1 <Proxy.cxx:1046> ] Reverting to old configuration.
2014-09-30 15:37:38.183 [ umsdevice(30706).b3f49cf4-5535-4dfb-aed2-39332d2f086b BE_PROXY=1 <Proxy.cxx:1051> ] No old config to revert to, exiting.

[Nadeem Ahmed]

Hello,

Just do the replace configuration from the affected cameras it will push updated config from VSOM to VMSM--Camera and fix the issue.

generally these error found when we see mismatch configuration between VSOM and media server or Cameras. as master data being maintain at VSOM SQL DB which find if there is mismatch config in his data for that particular camera or DB synchronization issue.

Br,

Nadeem Ahmed