Discovery Linux Disks Probe Not Returning Any Information for CCISS-Presented Disk Devices
The Discovery Linux - Disks probe returns information for all IDE and SCSI based disk devices on the server being discovered. A customer reported that disks presented from HP Smart Array Controllers using the CCISS driver were not returning any information from the Discovery Linux - Disks probe.
Run the hd.sh Script on the Linux Host as the Discovery User
If no information is returned from the Linux - Disks probe, test the hd.sh shell script embedded in the probe. Run the script natively as the Discovery user on the Linux host where data was not retreived to verify it is working normally.
- On your ServiceNow instance, navigate to Discovery Definition -> Probes.
- Locate the Linux - Disks probe.
- Click Probe Parameters -> hd.sh to open the shell script embedded in the Value section of the form.
- Select all (<CTRL>A on Windows, or <CMD>A on a Mac) and copy the text (<CTRL>C on Windows, or <CMD>C on a Mac).
- Using a terminal emulator (such as PuTTY, or Terminal) login to the Linux host using the Discovery user account.
- From the account, open an editor session (such as vi/vim/emacs) and paste the contents (<CTRL>V on Windows, or <CMD>V on a Mac) into the file.
The file should now contain the contents of the hd.sh shell script.
- Save the file as hd.sh in the home directory of the Discovery user.
- Make the hd.sh shell script executable and then run the script:
$ chmod +x hd.sh
- Check for errors.
If no information is returned for the disks that are presented onto the system, try to run the script from the root account. If the results are the same from the root account, follow the next procedure, Determine How the Disk Devices are Presented to Linux.
Determine How the Disk Devices are Presented to Linux
If disks are not displayed using the script, the disks may be presented as non-IDE and non-SCSI disks. This can happen when the disks are using proprietary hardware or drivers.
- To determine if disks are using proprietary hardware or drivers, use the root account and type the following command:
# fdisk -l
- For the devices displayed, view the device column.
IDE drives are listed as /dev/hdxn (where x represents a letter such as a, b etc... and n represents a number).
SCSI drives are listed as /dev/sdxn (where x represents a letter such as a, b etc... and n represents a number).
If you see IDE or SCSI devices represented that are not displayed using the hd.sh script, please contact ServiceNow Customer Support for further assistance.
You may see disk devices represented that do not follow the above naming convention. This example shows disks presented from a Compaq/HP Smart Array Raid Controller, which uses the CCISS driver. Example device names:
The CCISS driver was deprecated in later versions of the Linux kernal and replaced with the HPSA driver. The HPSA driver shows disks presented from a Compaq/HP Smart Array Raid Controller using the standard SCSI naming convention. For information about transitioning to the HPSA driver, see the Hewlett Packard document 'hpsa' - A SCSI-based Linux device driver for HP Smart Array Controllers.
Solution and Workaround
The CCISS driver has been deprecated within the Linux kernel. ServiceNow will not build in the functionality to discover these devices using the base system hd.sh shell script.
Upgrade to a newer Linux kernel that supports the HPSA driver and transition your existing CCISS devices to HPSA standard SCSI presented devices. For information about transitioning to the HPSA driver, see the Hewlett Packard document 'hpsa' - A SCSI-based Linux device driver for HP Smart Array Controllers.
Build a custom probe and sensor pair to obtain the information.
Use the existing Linux - Disks probe and sensor pair to create a custom pair. Rename the existing pair, click on the record header, and select "Insert and Stay" to create new records. The hd.sh shell script contained in the probe parameters should be modified to detect CCISS presented disks.
|Note: Do not modify the base system Linux - Disks probe and sensor pair. Changing the existing pair could affect future upgrades of the probes.|