Hi folks, I have an odd issue here that perhaps you might have ran into. So we just upgraded from VSM 7.0 to 7.2.1 and I thought it would be a good time to start firmware upgrades to cameras to the latest version (2.5.2-2) to prepare for 7.5. I decided to start with the 2500's and go up in model number. I uploaded the current firmware release to the server and then sorted by version. For a test, I just chose one camera on the list. Selected it, and proceeded to upgrade. Once done, I directly logged into the camera to check its FM version, it still said it was on the older version. (2.5.1-1) I went back to the server and checked the job logs and it had upgraded a totally different camera then the one I had selected. As I started digging deeper I noticed that the VSM server is not reflecting the FM version that is actually on the camera, such as 2.5.2 is on the camera but VSM is saying it has 2.5.0-9 and such.
Have any of you seen this? is there a way to do a firmware version refresh on the server to get current versions synced? Why would I choose a camera to upgrade but it did a completely different camera?
It also has a similar workaround as you found on your own.
Workaround: Do not click the column headers to sort the list of cameras in the Bulk Action tool. Instead use the filters on the left side of the screen to get a smaller list of cameras and then select the cameras to update without sorting the columns. For example, filter the cameras by Media Server, Camera Model, Location or Camera template.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
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...