10-28-2014 03:18 PM
I am getting a couple of different errors when trying to add or change cameras that are associated to one of my media servers.
I have added screenshots of the errors that I have found.
Any help would be appreciated.....
Steve
10-30-2014 09:38 AM
Hi Steve,
The initial error message looks like VSOM is attempting to provision 65GB of estimated storage prior to starting a new archive, and that there isn't a VSMS instance with sufficient storage for the request. Is there?
The camera change screenshot I'm not 100% on, but my gut tells me the camera you are trying to swap in may not be at an appropriate firmware level for VSM 7.5.1. Check the release notes for VSM 7.5.1 and ensure the camera you are adding is at the minimum FW required.
The server health / NIC usage message is the most unexpected one in my opinion. Is this VSMS instance physical or virtual? What speed is the NIC negotiated at? If its negotiated at 1000MBps as it's supposed to be, it would imply that you're ingress traffic is near 930 MBps? That is monsterously excessive if that's the case.
Can you provide any additional detail?
Cheers!
10-30-2014 10:09 AM
I found the space issue and have it resolved. But the nic issue has persisted. It is a physical server. It was connected to 100/1000 standard port. Configured Full Duplex/1000Mb. I moved the link to an sfp port with a GLC-T and configured the same. This has seemed to mitigate the nic error for now.
10-30-2014 10:43 AM
Do you have an idea of what your ingress throughput into the chassis should be? Unless I'm mistaken, I think the general limit is still 200 Mbps.
I can't find any bugs related to nic_usage, and although I can't recall the specifics, I believe you can check aggregate throughput somewhere on the VSMS page.
Cheers,
Scott.
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