How to re-initialize discovery of disks for existing cdm deployments

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)

Issue/Introduction

You can set up your .cfg to automatically detect new filesystems. If you wish to do this before following this procedure, follow the instructions in How to enable cdm to automatically monitor new disks

Then in order to make sure that you have discovered all existing filesystems, you may need to re-initialize discovery of existing filesystems. This procedure describes how to do so.

The approach/process outlined here does not involve MCS.

Environment

UIM 8.x or higher
Component: UIMCDM

Cause

- configuration requirements/filesystem discovery

Resolution

1.Modify the custom .cfx file within a configuration package using the following sample as a reference:

 

Note: Make sure to use the clear tag within the <fixed> section. This will remove existing disks, and force a rediscovery after the next restart of the cdm probe.

Here is a sample of this type of .cfx file for reference.

<disk> overwrite

interval = 15 min
samples = 4

<alarm> overwrite

active = yes

<connections> clear
</connections>

<fixed> clear
</fixed>

</alarm>
<fixed_default> overwrite

active = yes
qos_disk_usage = yes

qos_disk_usage_perc = yes
percent = yes

<error> overwrite

active = yes

threshold = 10
message = DiskError

</error>
<warning> overwrite

active = yes
threshold = 15

message = DiskWarning

</warning>

</fixed_default>

</disk>

2. Restart the cdm probe.
3. Drag and drop the probe onto the archive. When prompted, choose Configuration Only. 

You can then deploy this configuration to target servers either as a standalone configuration or as part of a super-package.

Additional Information

Simplified version using the clear tag for the fixed section - use the clear tag within the <fixed> section. This will remove existing disks, and force a rediscovery after the next restart of the cdm probe.

   <disk> overwrite
   <alarm>
   <fixed> clear
   </fixed>
   </alarm>
   </disk>

 

If you want to set a static threshold for a specific filesystem while resetting the rest to defaults, you can do so by including the filesystem threshold details.  This must be placed after the <fixed> clear  directive, and before <fixed_default>, as in the following example setting static alarm thresholds for a filesystem called "/data":

 

<disk> overwrite
<fixed> clear
</fixed>
    <alarm> overwrite
      active = yes
   <fixed> overwrite
            <#data> overwrite
            active = yes
            <error> overwrite
               active = yes
               message = DiskError
               threshold = 20
            </error>
            <warning> overwrite
               active = yes
               message = DiskWarning
               threshold = 10
            </warning>
           </#data>
    </fixed>
</alarm>
   <fixed_default> overwrite
       Monitor_Newly_Discovered_Disk_OnTheFly = yes
      (other defaults here)
   </fixed_default>
</disk>