cdm.cfx leaves everything blank

[Keith Clay]

Here is the cdm.cfx I am using for linux robots.  When I deploy this probe to a robot, all the values are blank.  Am I missing something?

I had to change the name to cdm.txt since it won't let me upload cdm.cfx.

Attachment(s)

cdm.txt   34 KB 1 version

[Stephen Danseglio]

Hi Keith,

Here is what you normally need to do:

1. Drag and Drop the cdm probe from a source robot machine you want to edit some parameters for, to the local archive and rename it as desired, e.g., cdm_linux_master.
    Then click Ok.
2. Double-click to open the new configuration package
3. Rt-click the package and chose Save file as...and save the cdm.cfx to the filesystem, e.g., your Desktop.
4. Using Notepad, open the cdm.cfx and make your desired changes, e.g, overwrite one or more sections as desired.
5. Choose File->Save As and save the edited cdm.cfx to the desktop.
6. REMOVE the original cdm.cfx from the cdm probe configuration package.
7 Choose Add file and add your NEW cdm.cfx to the package. View the cdm.cfx file contents to make sure it looks as expected.
8. Deploy it to the target machine and check the configuration changes to confirm.

You may also find these KB articles helpful:

Editing probe packages (probe configuration files and templates, e.g., .cfx and .cfg, and tips on modification)
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=34027 

How to create a configuration-only package that adds a new profile to deployed probes without editing existing profiles
https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=34347

Best Regards,
Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------

[Keith Clay]

This is exactly what I did, adding overwrite directives to the disk, cpu and memory stanzas.  When I deploy to a robot that has no cdm probe, it still shows up blank.

[Stephen Danseglio]

Ah didn't realize you were deploying to a robot that did not have the cdm probe already in place. Make sure there is a cdm probe package in the local archive and review this set of slides on creating a Super package (which will come in handy when you need to create one), but for now just focus on cdm and in Step 2 you'll see what has to be done when the cdm probe is not already deployed on the target Robot. You have to create a Dependency...

------------------------------
Support Engineer
Broadcom
US
------------------------------

Attachment(s)

Creating_a_SuperPackage.pdf   1.02 MB 1 version

[Keith Clay]

I will be deploying to both robots that have a current probe and those that don't, but I copied the current linux cdm.cfx from our 8.3.1 installation to 9.0.2 since we need to migrate our packages to there. I just did a simply copy and I get blanks.  I deleted the cdm probe from the 9.0.2 robot and pushed my new cdm package from the archive and still nothing.  

Also, from the pdf, if you have overwrite at the disk stanza why would you need it anywhere else? I see it's at <disk> and every stanza below it.

[James Christensen]

The overwrite key word needs to be at every section label <> you include in the cfx file. That's just the way it works. If you don't wish to overwrite/change a particular section, then remove it from the cfx file.

 

James Christensen

Sr. Services Architect  |  Enterprise Studio

HCL Technologies Ltd.

Mobile: [phone]  |  eMail: [e-mail]

www.hcltech.com  | www.ca.com/services

 

 

Vacation Alert: Dec. 24 – Dec. 26

 

::DISCLAIMER::

---

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

---

[Garin Walsh]

Just to be careful with the interpretation of this reply, there are four directives: "nothing", overwrite, edit, and clear

"nothing" adds the section and keys in the section if they don't already exist.
overwrite adds the section and keys in the section if they don't already exist and changes the values of the ones that do exist.
edit changes the values of the keys that exist in the section.
clear removes all keys and sub section from the sections and replaces it with the contents of the <clear></clear> section.

overwrite is the one that you will use most often but the others have their place.

CDM has been talked about in this thread and so consider the issue if you have Windows servers with arbitrary drives C: - Z: that have been manually configured over the years and you want disable the Warning thresholds on all drives.

You could touch every system or you could have a cfx file that looks like (note the edit on the warning section):
# It's undocumented but you can comment cfx files with #. 
<disk> overwrite
   <alarm> overwrite
      <fixed> overwrite
         <C:\> overwrite
            <warning> edit
               active = no
            </warning>
         </C:\>
      </fixed>
   </alarm>
</disk>
<disk> overwrite
   <alarm> overwrite
      <fixed> overwrite
         <D:\> overwrite
            <warning> edit
               active = no
            </warning>
         </D:\>
      </fixed>
   </alarm>
</disk>

stanzas for E: - Y:

<disk> overwrite
   <alarm> overwrite
      <fixed> overwrite
         <Z:\> overwrite
            <warning> edit
               active = no
            </warning>
         </Z:\>
      </fixed>
   </alarm>
</disk>

Since the directive is edit, it will change it if it's there and do nothing if it's not. Now you have no need to know what's there in order to make this type of wholesale change.
   
-Garin​​

[Keith Clay]

Also, how would a superpackage help me with just one probe?

[Stephen Danseglio]

Ignore the other probes - just wanted you to be aware of the dependency option for the sake of cdm when its not already deployed.

------------------------------
Support Engineer
Broadcom
US
------------------------------

[Keith Clay]

What dependency option for new deploys? Also the first link doesn't load. I get a 404 error.

[Stephen Danseglio]

I got the same 404 error when I clicked on the link in the community post. I then googled the following string:

UIM Editing probe packages

and clicked on the url in the results and it worked.

Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------

[James Christensen]

A superpackage would not only deploy the desired configuration, but would also deploy the related probe if it was not already present on the server/robot.

 

James Christensen

Sr. Services Architect  |  Enterprise Studio

HCL Technologies Ltd.

Mobile: [phone]  |  eMail: [e-mail]

www.hcltech.com  | www.ca.com/services

 

 

Vacation Alert: Dec. 24 – Dec. 26

 

::DISCLAIMER::

---

The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.

---

[Garin Walsh]

When I create a package with the intent of deploying a cfx file, I add a tab left most in the list (that's the order they're processed) that includes the probe the cfx is dependent on:

When a package is deployed, the dependencies tab is processed before the files tab for the section. If the dependency isn't satisfied, the package installer deploys that package before continuing with the current package. It's recursive and has no apparent limit on the number of layers you can have.

So this particular package will ensure that the package named cdm is installed and at least version 6.30. If not it will deploy the latest (because the test is ge) cdm package. Then it will continue with the files tab of the "dep" section. Then move on to the "ALL" section:

which has my cfx file in it.

-Garin

[Olaf Pape]

Hi Keith,

your attached cdm.cfx file is probably a copy of a cdm.cfg file and does not contain any directives like 'overwrite', 'delete' or 'clear'.
Without this the cfx file will only be transfered in the cdm folder and copied to cdm.cfg.

If you are using IM than you can drag a cdm probe to the archive and you will get a new probe package (dont forget renaming) with an cdm.cfx file. All sections are marked as 'overwrite'. Than you can edit the cfx file to match your needs.

[James Christensen]

Hi Keith, 
I looked at the attached cdm.txt file and, as previously noted by Olaf, it does not contain any of the proper directives - primarily overwrite. Also, if it is uploaded to the archive package as cdm.txt, it will have no effect. the package will deploy a copy of it as cdm.txt, but the robot will not know what to do with it.It must be named cdm.cfx to and have the proper directives to work as you need it to. Please see Steve's comment for the proper method for creating this configuration package.

------------------------------
[Designation]
[City]
------------------------------

[Keith Clay]

This site will not allow me to upload a .cfx file so I had to change the extension.

[Keith Clay]

If you look you will see the overwrite directives for the appropriate stanzas

[Sam Green]

You can do it all from Infrastructure Manager Keith.

Drag the configured probe from a robot back into your archive, rename it.  Rt-click the package you saved in the Archive, click "Edit", when it loads, rt-click the .cfg, click "Edit File" (I think), then it opens in an editor, or notepad if the CFG is too big..

Edit away and click ok, then ok again.  Deploy by drag and drop, as long as the target already had the probe, your new template will overwrite.  As long as the "overwrite" directives are present of course, usually are unless adding something bespoke.

Hope that helps.

------------------------------
CA - UIM administrator
------------------------------

[Stephen Danseglio]

I will test your config file/deployment as soon as I get a chance.

Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------

[Garin Walsh]

Were this my cdm config, I'd make the <disk> section look like the following. In particular, put the "<fixed> clear" at the end after the rest of the settings. Also make sure that there's a space between the ">" and "clear" directive - you look to be missing that. The regex for the ignore_filesystem in your original file is also damaged - not sure if that's the forum or what you intended but make sure that it starts and ends with / and that any special characters are escaped correctly. Also that * is used correctly.

The "<fixed> clear" statement ( as it was explained to me) fires at the point that is encountered. So if you have no default in place, when this runs there's nothing to supply for the stanza. Also keep in mind that the cfx files are processed a line at a time so their order of contents is important - as opposed to almost all cfg files where order isn't generally relevant. 

<disk> overwrite
   interval = 5 min
   samples = 4
   use_systemspace = no
   ignore_filesystem = /\/run\/user\/.*|\/dev|\/(.*\/?snapshot\/.*)|\/\/.gvfs.*\/|\/opt\/vormetric\/DataSecurityExpert\/agent\/secfs\/.sec/
   ignore_device =
   filesystem_type_regex = /^(?!.*?(tmpfs|iso9660)).*/

   <alarm>  overwrite
      active = yes
      <connections>  overwrite
         active = yes
         level = minor
         message = Network connection not as expected
      </connections>
   </alarm>

   <fixed_default>  overwrite
      active = yes
      qos_disk_usage = yes
      qos_disk_usage_perc = yes
	  qos_disk_total_size = yes
      percent = yes
      qos_inode_usage = no
      qos_inode_usage_perc = no
      inode_percent = yes
	  delta_percent = no
	  qos_disk_delta = no
	  qos_disk_delta_perc = no

       <error>  overwrite
         active = yes
         threshold = 15
         message = DiskError
      </error>
      <warning>  overwrite
         active = yes
         threshold = 18
         message = DiskWarning
      </warning>
      <inode_error>  overwrite
         active = no
         threshold = 10
         message = InodeError
      </inode_error>
      <inode_warning>  overwrite
         active = no
         threshold = 20
         message = InodeWarning
      </inode_warning>
      <missing>  overwrite
         active = yes
         message = DiskMissing
      </missing>
      <delta_error>  overwrite
         active = no
         threshold = 200
         message = DeltaError
      </delta_error>
      <delta_warning>  overwrite
         active = no
         threshold = 8
         message = DeltaWarning
      </delta_warning>
   </fixed_default>

      <fixed> clear
      </fixed>

</disk>​

-Garin