I have several cameras that show a configuration mismatch. The process to repair/replace the configuration is simple enough. However, when I attempt to update the configuration, I get error messages. The firmware version is correct. I can ping the cameras and VSOM shows they are reachable. What is causing these errors and keeping the configuration update from completing?
The text of the errors is as follows:
1) Operation failed: Media server reported the error Motion configuration for device [cc3f3216-fd9e-4147-b519-b4159caBed8a] failed. Error message:[ACK:Time out]
2) Operation failed: Invalid authentication
Has anyone else encountered these errors?? What did you do to resolve them??
I have a 3rd error to add to this list that occurs when I attempt to configure a camera with a configuration mismatch. To restate conditions: firmware version is correct, able to ping camera, shows reachable via VSOM.
3) Operation failed: Media server reported the error Failed to update device (get TimeSetting failed).
Has anyone else encounted these errors? What did you do to resolve them?
Scott, The firmware version is specific to each camera model, but for each model (we have 4 different camera models in use throughout our system), in each case, the firmware is what it should be for our version of VSM. We are running VSM 7.0.
Scott, Sure. No Problem. The cameras having the configuration problems are 2500s, 2530s and 2600s. The 25xx model are running firmware version 2.5.0-9 and the 2600s are running firmware version 4.4.1-1. We also have HD cameras installed here, but at the moment, I'm not having any configuration difficulties with any of those.
Ahh... we run those as well. You may want to move to the most recent firmware:
There aren't any caveats that cover what you've described, but it wouldn't hurt to upgrade them.
This is across your entire install base? Multiple cameras, and not just one or more problem units? Is it possible you're experiencing any packet loss or performance issues (contention) at the VSMS instance?
An ACK timeout and a failure to poll a setting sounds suspiciously like lost packets to me. Is it /consistently/ repeatable? Exact same errors on same cameras, etc... or does it occassionally function?
Bulletproof Solutions Inc.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...