cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2550
Views
4
Helpful
13
Replies

Getting error message when adding new camera in VSOM

Hi all,

 

Sorry,I am neophyte in Cisco CCTV systems.

 

I am getting an error message when adding or editing all existing cameras in VSOM. Please check it in attached. What might be the cause?

2 Accepted Solutions

Accepted Solutions

Have the additional virtual HDDs you've allocated to the media server been configured for use?  

i.e. - Have they been configured under the Media Server:

 

 

FYI - Although I can't find the document or resource right now, there is a Cisco doc that explains how to add these at the OS level, but I can't locate it at the moment.  It may be covered in one of the VSM 6.X documents, or perhaps Raghav would know where it is.

The short story is that the block device needs to have an XFS file system on it, and have a '/mediaX' mount point.

Best of luck!

 

 

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com

View solution in original post

I don't *think* you should have to restart the services, but I'm sure it wouldn't hurt.  It's probably best practice.  

... or I could be wrong and it's required. 

Chances are it will correct the issue and you should be able to start a new archive.  Have you done any basic math to project how much storage you are expecting to use for the archive you have in mind?

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com

View solution in original post

13 Replies 13

Raghav-Rao
Cisco Employee
Cisco Employee

when an camera is added via VSOM, depending on the template media server reserves the space on any one of the available media partitions and goes on with  keep adding cameras on to VSOM depending on the storage available with respect to design consideration. Error says, Server doesn't have enough space to accommodate camera.

Recommendation - size of the space has to be increased or work on other cameras to accommodate less storage on the existing partitions.

go to VSMC page --> Monitor --> Recordings --> estimate storage. this column give the approx. space reserved by media server for each camera.

Hope this helps you, let us know, if you have any further questions.

Thank you for the feedback, I have more questions:

- How can I increase the space? I have VSOM 7.5.0, running in a VM installed on a UCS C240 M3, with 10TB of hard disk space (find details in attached)

 

- How is the estimate storage calculated? Is it possible to get details on the calculation? Is it based on resolution, frame rate...? If so, how?

1. please find the deployment guide link below for your further reference.

http://www.cisco.com/c/en/us/td/docs/security/physical_security/video_surveillance/network/vsm/7_6/vm/deploy/vsm_7_ova/ova_deployment.html#pgfId-1055098

2. Yes, Camera bandwidth is depended on Resolution, Frame rate, Compression etc...

How to calculate the storage for a camera - Camera bit rate / 8 * 86400 * #days

above will give approx. calculations, though you could Google for calculator's for respective cameras.

 

Thank you very much. how shall the media server consider Virtual hard drive previously added to increase space? Because I already added 2 Virtual Hard drive of 2 TB, but the error message is still occurring.

VSM would get the space unless old archives are groomed. Once the groomer, grooms old recordings depending the no. of days retention space's are allocated to VSM accordingly.

Hope this answers your question.

As per Scott Olsen comments, don't I have to add space at OS level? (creating XFS partition)

Ok, I succeeded to add at OS level, and VSOM is now able to see additional partitions. I checked "recording", "clipping"... for all of them (see in attached), but I am still getting the same error message. Do I have to restart the server or the service?

I don't *think* you should have to restart the services, but I'm sure it wouldn't hurt.  It's probably best practice.  

... or I could be wrong and it's required. 

Chances are it will correct the issue and you should be able to start a new archive.  Have you done any basic math to project how much storage you are expecting to use for the archive you have in mind?

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com

Yes, I need at around 300 GB for IPC 3530 and 500 GB for IPC 6030. Total for all the cameras: 6.8 TB. But I am just trying to save settings for one IPC 6030 and it is refusing.

Have you since tried restarting the server after adding the new media repos to it's configurations?

What are the stream metrics you are trying to use with the 6030?  In your initial screenshot, it's estimating a single archive size of over 1 TB.

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com

Thank you very much guys, I did not restart, but it started now archiving footages!!!! I am very very happy!

 

I also reduced recording period from 14 days for continuous to 7 days.

Thank you for your support! Much appreciated!

From the snap i see, the media partitions are not configured for Recording and clipping. Partitions need to be checked and saved. by this media partitions are available for VSM server. Apply configuration on media server is essentials.

Reboot of server will sync up.

if server is in 7.5.0, upgrade to 7.5.1 or 7.6.

Have the additional virtual HDDs you've allocated to the media server been configured for use?  

i.e. - Have they been configured under the Media Server:

 

 

FYI - Although I can't find the document or resource right now, there is a Cisco doc that explains how to add these at the OS level, but I can't locate it at the moment.  It may be covered in one of the VSM 6.X documents, or perhaps Raghav would know where it is.

The short story is that the block device needs to have an XFS file system on it, and have a '/mediaX' mount point.

Best of luck!

 

 

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com