Discovery of server results in unwanted SAN disks that are not being used

book

Article ID: 36117

calendar_today

Updated On:

Products

EHEALTH CA eHealth

Issue/Introduction

Problem:

 

Each target server has up to 4,000 SAN disks that get discovered. Not all of the disks are in use, thus no statistics information is populated in the agent mib.

 

Reports on these elements show zeros for data

 

They appear in the agent mib under the Host-Resource mib's device table:

 

hrDeviceDescr -> hrDeviceEntry.3 (1.3.6.1.2.1.25.3.2.1.3)

 

SNMPv2-SMI::mib-2.25.3.2.1.3.20 = sd192,c2t20080020C211C827d43s0 SCSI Device
SNMPv2-SMI::mib-2.25.3.2.1.3.21 = sd193,c2t20080020C211C827d43s1 SCSI Device
SNMPv2-SMI::mib-2.25.3.2.1.3.22 = sd194,c2t20080020C211C827d43s2 SCSI Device
SNMPv2-SMI::mib-2.25.3.2.1.3.23 = sd195,c2t20080020C211C827d43s3 SCSI Device
<snipped>

 

In the discover results log, the elements will appear similar to this:

 

10.1.1.1  sysname-1691-SH-disk-sd192c2t20080020C211C827d43s0         Empire SH disk de 20 14     
10.1.1.1  sysname-1691-SH-disk-sd193c2t20080020C211C827d43s1         Empire SH disk de 21 17     
10.1.1.1  sysname-1691-SH-disk-sd194c2t20080020C211C827d43s2         Empire SH disk de 22 20     
10.1.1.1  sysname-1691-SH-disk-sd195c2t20080020C211C827d43s3         Empire SH disk de 23 21     
<snipped>      


We only want to monitor those disks that have data, and have the rest of them discarded / not generate elements.

Generating the elements that have no statistics data would cause the total supported element configuration to be exceeded very quickly if 200 of these servers were discovered in eHealth. For example: (200 servers x 4000 SAN disks)=800,000

Creating a DCI rule function to exclude these elements would only exclude all of the elements, because there isn't a unique identifier for the disks that do have data.

Environment:  

 

eHealth 6.2.2 D05 to 6.2.2 D17
Windows 2003, Redhat Linux, Solaris 10

 

eHealth 6.3.0 to 6.3.2.11 

Windows 2003, Redhat Linux, Solaris 10 

 

Resolution/Workaround:

 

Beginning in 6.3.2.13, code has been added to the discover engine that checks "hrDiskStorageCapacity" for values greater than zero, and based on the returned results, generates those elements and discards the rest.

 

Additional Information:

 

Additionally, as other disks in the hrDeviceTable come on line / go off-line, subsequent redscoveries would show "New elements" / "Missing elements" respectively.

The Missing elements can be retired or deleted depending on whether historical data is important to the user / customer.

 

 

Environment

Release: LHDEVC99000-6.3-eHealth-Live Health Upgrade Elements
Component: