AnsweredAssumed Answered

Cluster / cdm: Unable to register section

Question asked by OscarGarza on Mar 14, 2017
Latest reply on Mar 26, 2018 by Issac08

Like • Show 0 Likes0
Comment • 10

I'm trying to configure cluster monitoring on a Windows 2008 R2 Cluster, but each time that I try to create the profile on the cluster probe and select the cdm probe I got a communication error... Reviewing the log on the cdm I found the following message.... The same type of message is recorded for all the drives which are part of the cluster,

cdm: Unable to register section /cluster/Cluster Group/disk for group Cluster Group with cluster probe (error)

Have you deal with a similar issue on yoru environments?

CDM probe version 5.80

Cluster version 3.42

OS Windows 2008 R2

Note: I can configure ntservices profiles in the cluste probe without issue...

No one else has this question

Outcomes

casph02

Apr 7, 2017 1:22 PM

Hi Oscar, were you able to resolve this? Do you have the 'fixed_default' key set to active in the probe configuration? In a cluster setup, this should not be active because it can cause some issues.

Actions

masru01

Jun 5, 2017 10:59 AM

Hi Philip,

I have the same issue with my customer don't matter if this Fixed_default key is NO or YES has the same results.

Any other advice?

Thank you

Rubens.

Actions

Britta_Hoffner

Aug 24, 2017 1:29 PM

Hello Oscar, is this still an open question ?

Kind regards,

Britta Hoffner

CA Support

Actions

imrankhcl

@ Britta_Hoffner on Nov 20, 2017 12:43 PM

I have the same question.

Actions

Issac08

@ imrankhcl on Nov 20, 2017 3:33 PM

Fixed default of disk active should be no ..Can you share the exact error

Actions

Manish_Sharma Mar 26, 2018 9:28 AM

we are also facing same issue although fixed_default value if no in CDM probe configuration.

Actions

Issac08

@ Manish_Sharma on Mar 26, 2018 1:50 PM

Can u pls make a entry robotip = <node ip> in robot .cfg -> restart nimbus service and try once ,some times u may get conflict with cluster private ip.

Actions

Manish_Sharma @ Issac08 on Mar 26, 2018 1:56 PM

Hi Isaac,

Thanks a lot for your response, however we found some other workaround solution (mentioned below) for this issue.

1. Deleted CDM probe

2. Stop service from Nimsoft service controller

3. Deleted CDM folder from probes

4 Started agent service

5. Deployed CDM probe

After deploying CDM probe from scratch we were able to discover cluster drives in cluster probe.

Regards,

Manish Sharma

Actions

Issac08

@ Manish_Sharma on Mar 26, 2018 1:59 PM

Good manish . I hope before deploying cdm probe you have already deployed cluster probe or it is present before.

Actions

Manish_Sharma @ Issac08 on Mar 26, 2018 2:06 PM

Cluster probes was already deployed, after deploying cluster probe we identified this issue and we did not make any changes in the Cluster probe to fix the issue.

Therefor our first troubleshooting step was with CDM probe and fortunately it fixed on first step itself.

Although in cluster probe version 3.43 release notes this is mentioned that this communication issue is fixed in 3.43 version, however I am afraid its not fixed with new version.

Actions

10 Replies

casph02 Apr 7, 2017 1:22 PM
Mark Correct
Correct Answer
Hi Oscar, were you able to resolve this? Do you have the 'fixed_default' key set to active in the probe configuration? In a cluster setup, this should not be active because it can cause some issues.
Like • Show 0 Likes0
Actions
masru01 Jun 5, 2017 10:59 AM
Mark Correct
Correct Answer
Hi Philip,

I have the same issue with my customer don't matter if this Fixed_default key is NO or YES has the same results.

Any other advice?

Thank you

Rubens.
Like • Show 0 Likes0
Actions
Britta_Hoffner Aug 24, 2017 1:29 PM
Mark Correct
Correct Answer
Hello Oscar, is this still an open question ?

Kind regards,
Britta Hoffner
CA Support
Like • Show 0 Likes0
Actions
- imrankhcl @ Britta_Hoffner on Nov 20, 2017 12:43 PM
  Mark Correct
  Correct Answer
  I have the same question.
  Like • Show 0 Likes0
  Actions
  - Issac08 @ imrankhcl on Nov 20, 2017 3:33 PM
    Mark Correct
    Correct Answer
    Fixed default of disk active should be no ..Can you share the exact error
    Like • Show 0 Likes0
    Actions
Manish_Sharma Mar 26, 2018 9:28 AM
Mark Correct
Correct Answer
we are also facing same issue although fixed_default value if no in CDM probe configuration.
Like • Show 0 Likes0
Actions
- Issac08 @ Manish_Sharma on Mar 26, 2018 1:50 PM
  Mark Correct
  Correct Answer
  Can u pls make a entry robotip = <node ip> in robot .cfg -> restart nimbus service and try once ,some times u may get conflict with cluster private ip.
  Like • Show 0 Likes0
  Actions
  - Manish_Sharma @ Issac08 on Mar 26, 2018 1:56 PM
    Mark Correct
    Correct Answer
    Hi Isaac,
    
    Thanks a lot for your response, however we found some other workaround solution (mentioned below) for this issue.
    
    1. Deleted CDM probe
    2. Stop service from Nimsoft service controller
    3. Deleted CDM folder from probes
    4 Started agent service
    5. Deployed CDM probe
    
    After deploying CDM probe from scratch we were able to discover cluster drives in cluster probe.
    
    Regards,
    Manish Sharma
    Like • Show 0 Likes0
    Actions
    - Issac08 @ Manish_Sharma on Mar 26, 2018 1:59 PM
      Mark Correct
      Correct Answer
      Good manish . I hope before deploying cdm probe you have already deployed cluster probe or it is present before.
      Like • Show 0 Likes0
      Actions
      - Manish_Sharma @ Issac08 on Mar 26, 2018 2:06 PM
        Mark Correct
        Correct Answer
        Cluster probes was already deployed, after deploying cluster probe we identified this issue and we did not make any changes in the Cluster probe to fix the issue.
        Therefor our first troubleshooting step was with CDM probe and fortunately it fixed on first step itself.
        Although in cluster probe version 3.43 release notes this is mentioned that this communication issue is fixed in 3.43 version, however I am afraid its not fixed with new version.
        Like • Show 0 Likes0
        Actions

Cluster / cdm: Unable to register section

Outcomes

Related Content

Recommended Content