As root, you can try these: /opt/MegaRAID/MegaCli/MegaCli -pdrbld -progdsply -physdrv\[E:S\] -aAll or /opt/MegaRAID/MegaCli/MegaCli -pdrbld -showprog -physdrv\[E:S\] -aAll In above commands replace "E" and "S" by the Enclosure Device ID and Slot Number of the physical drive. You can get this information for each drive via following command: /opt/MegaRAID/MegaCli/MegaCli -pdlist -aall ... View more

Hi Matvey, Ask your Cisco account team to fill in the Custom camera driver request form located at this (Cisco internal) URL: http://wwwin.cisco.com/etg/physec/selling_resources/driver.shtml Sincerely, Dirk Christeaens ... View more

I have verified this again, but for an encoder this time and it works the same way as for an IP camera. This is what gets inserted in the VSOM MySQL database upon creating a new preset (test1). This can be seen by setting the operations manager log level to 'Debug' from within VSMC and then tailing vsom.log:      2012-07-26 09:54:36 10.55.228.86 [debug] INSERT INTO bas_camera_presets (label, position, camera_id) VALUES ('test1', 1, 13) To see preset communication between VSOM and VSMS/Endpoint you can f.e. tail mediaout_access.log on the VSMS server: Setting preset label 1 to 'test1':      10.55.228.86    [26/Jul/12 00:54:20 -0700] "GET /camera.bwt?command=S1,test1&model=pelco_d&comport=COM1&number=0&source=1@10.48.63.187&srctype=cisco_smsg&priority=100&protocol=D HTTP/1.0" PROXIED command=S1 means 'set/store preset 1' Testing preset label 1:      10.55.228.86    [26/Jul/12 00:54:27 -0700] "GET /camera.bwt?model=pelco_d&comport=COM1&srctype=cisco_smsg&source=1@10.48.63.187&number=0&speed=50&protocol=D&priority=100&command=G1 HTTP/1.0" PROXIED command=G1 means 'go to preset 1' So, VSOM does not hold any information about the actual shot itself. VSOM is merely acting as a remote control here to select/set the desired preset, while the programming of the actual shot and associated preset happens in the endpoint only. ... View more

Do you remember the exact model of encoder? Indeed perhaps there are differences in how some endpoints handle this. ... View more

It is strange that it didn't work for your client. I have just reinstalled VSOM (6.3.2-MR2), wiped the database with a blank, new database and then restored a previous backup and all presets for my Cisco 2900 camera are back and working. VSOM merely stores the label you give to the preset and to which camera and preset thereon it maps to, but the coordinates of the actual shot and which preset it belongs to (on the camera) are normally stored inside the camera only. Below are my presets in the VSOM MySQL database. As you can see the information that VSOM stores is very minimal. It's the camera that knows which actual shot belongs to which preset. mysql> select * from pub_camera_presets_view; +-----------+------------+----------+-------+ | camera_id | name       | position | label | +-----------+------------+----------+-------+ |         8 | lab-2900-1 |        1 | left  | |         8 | lab-2900-1 |        2 | right | |         8 | lab-2900-1 |        3 | front | |         8 | lab-2900-1 |        4 | down  | |         8 | lab-2900-1 |        5 | up    | |         8 | lab-2900-1 |        6 | test  | +-----------+------------+----------+-------+ 6 rows in set (0.00 sec) mysql> select * from bas_camera_presets; +----+-----------+----------+-------+ | id | camera_id | position | label | +----+-----------+----------+-------+ |  1 |         8 |        1 | left  | |  2 |         8 |        2 | right | |  3 |         8 |        3 | front | |  4 |         8 |        4 | down  | |  5 |         8 |        5 | up    | |  6 |         8 |        6 | test  | +----+-----------+----------+-------+ 6 rows in set (0.00 sec) ... View more

Maybe try restarting them individually: # /usr/BWhttpd/root/hydra/bin/hydra restart # /usr/BWhttpd/bin/init_mrtg restart ... View more

PTZ presets are stored in the MySQL database in the VSOM server (and in the camera itself of course). So, when you have a backup of your VSOM server, the presets should be there as the backup contains a dump of VSOM's MySQL database. ... View more

Does this only happen when streaming to VSOM? What happens when you watch the video when directly browsing to the camera? Also, you can try to stream to VLC to see if that works well. Also, have you tried different resolutions and bit rates? ... View more

The 2500 camera only supports MJPEG and MPEG-4 as media types. MJPEG is just a sequence of individual JPEG images. You can get those with the HTTP URL you're showing, but for streaming MPEG-4 you'll have to use RTSP. You can find all supported RTSP URLs on page 4-6 of the user guide: http://www.cisco.com/en/US/docs/security/physical_security/video_surveillance/ip_camera/2500/english/user_guide/ipug.pdf ... View more

This should work f.e. for streaming to VLC using RTSP: rtsp:// : @ /img/media.sav ... View more

Which GRUB error number did you get (see here)? ... View more