Guest

Preview Tool

Cisco Bug: CSCur72069 - Vault Drive Alarming does not work in Release 2.5.4_B28

Last Modified

Sep 16, 2015

Products (4)

  • Cisco Videoscape Distribution Suite for Television
  • Cisco TV Streamer Application
  • Cisco Visual Quality Experience (VQE) Channel Provisioning Tools
  • Cisco Visual Quality Experience Application

Known Affected Releases

2.5(4) 3.7(1)

Description (partial)

Symptom:
faulty drive in vault does not glow red led.

Conditions:
faulty drive in vault should glow red led.

Drives are not coming online after system startup.
The consistent blinking of the blue LED indicates the device is initializing/spinning-up.
(A sporadically blinking blue LED indicates activity.)
These devices are not yet online,and apparently not going to come online,
and thus are not reported in /proc/cds/cdd/disks. These devices are bad and need to be replaced.

Note:

1.My driver will illuminate the red LED of a failed device if, and only if,
the driver knows about the device. If the device has failed in such a way
that it is not reported to the driver during system initialization then the
driver cannot control the device in anyway.

2.The red LED is lit solidly for a failed drive. A logically removed drive is not a failed drive.
When a drive is logically removed, as you have done with csdX where x is disk numbers from 1 to 24,
the intent is for the red LED to be blinking to indicate which drive is logically removed and prepared
to be physically removed from the chassis. The blue LED should be off and the red LED should be blinking.

3.GUI point of view if disks are sick, abandoned,not present in /proc/cds/cdd/disks and failed of device.
Red colour shown disk status page in GUI.

4.If disk is sick,abandoned and reported sick, It illuminated solid blue led on disk and it shows red colour in a GUI page.

5.Know that when a SAS drive is idle it's blue LED will be on solid. An idle SATA drive's blue LED will be off.
When you logically removed csd1 the drive was spun down and thus the blue LED turned off and
the red LED should have been illuminated.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.