locked
Dell MP alternative? RRS feed

  • Question

  • We are an "all Dell" shop.  But, cannot rely on the Dell Management Pack for alerts because of it's problem with discovering all servers.  I've tried all the fixes, it just doesn't get them all.

    Is there something out there that is comparable, even if it has to be purchased?

    Thursday, May 3, 2012 5:46 PM

Answers

  • v4.1 does still have issues.

    You have to constantly monitor the "Dell Unmanaged Servers Group"

    First, make sure you turn debug mode on (override the discovery to do this, instructions in the MP Guide), this will cause the discovery to create and write to a log file called "Discovery_DellServer.log" in the C:\Windows\Temp folder.  Using this log file you can usually figure out why it's "Unmanaged".

    On the majority of my servers, the issue is that the WMI Class doesn't exist.  The error in the log will be:

    "ERROR: UnManaged Server object created. Reason: Failure error while connecting to root-cimv2-Dell namespace." 

    The OMSA .mof file is not set to autorecover, so on the servers where I get the above error, I edit the "dccim32w2k3.mof" file (located here:  C:\Program Files (x86)\Dell\SysMgt\omsa\config) and add the following at the top of the file:

    #pragma autorecover

    Then save the file and import it using MOFCOMP dccim32w2k3.mof

    Then just restart the SCOM HealthService on the affected server and in a few minutes the server should be discovered.

    Now, I do still see these same servers in the Unmanaged group occasionally, usually with the following errors in the log file:

    ---- INFO: Dell_SoftwareFeature attributes retrieved successfully
    ---- ERROR: Unable to retrieve Dell_SoftwareFeature Err Number:-2147217357 Err Descr:
    ---- INFO: Dell_SoftwareFeature attributes retrieved successfully
    ----  ERROR: Object loop retrieval error. ErrNumber:-2147217357Description:
    ---- INFO: OMSA URL  :  OMSA Version  :

    a restart of the SCOM HealthService usually fixes this issue (or it will be successful next time the discovery runs on it's own).

    The servers where I see this happen the most are either SCCM/SMS Secondaries, or servers where the SCCM/SMS Client has to be repaired.

    • Edited by Richard Kinser Tuesday, May 8, 2012 7:08 PM
    • Proposed as answer by Blake Mengotto Wednesday, May 9, 2012 6:14 AM
    • Marked as answer by Yog Li Thursday, May 24, 2012 3:26 AM
    Tuesday, May 8, 2012 7:00 PM
  • Hi John,

    I work for Dell and this thread was brought to my attention, so I thought I would chime in.  I have a couple of suggestions:

    1. As an alternative to SCOM, you can manage Dell servers natively using a new, free Dell product called OpenManage Essentials (OME) which allows you to monitor and set up alerts for your servers.  More product information, demos, and a forum are available at DellTechCenter.com/OME.  Managing Dell servers with OME is preferable to the suggestion to use HP Insight Manager because Dell servers are supported natively by the Dell product, which should get you a much richer feature set.
    2. It seems that Ideally you want your MP to work correctly... have you opened a support case with Dell?  I asked someone from the team that works on the Dell Management Pack and he said he can better help troubleshoot if you are able to provide a trouble ticket number so we get a better idea of what your environment looks like.

    Hope that helps, feel free to get back in touch.

    • Marked as answer by Yog Li Thursday, May 24, 2012 3:26 AM
    Monday, May 14, 2012 10:35 PM

All replies

  • Hello John,

    I cannot find any MP can totally replace DELL MP.

    Thanks,


    Yog Li

    TechNet Community Support

    Tuesday, May 8, 2012 11:10 AM
  • Hi John,

    Here is an idea: use HP Systems Insight Manager (HP-SIM) to handle alerting on your Dell servers.

    Here is a Dell reference: http://www.dell.com/downloads/global/solutions/Integrating_PowerEdge_Servers_into_HPSIM50.pdf

    (and from HP): http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00709449/c00709449.pdf

    This is outside SCOM I know, however it's a reliable way to monitor Dell hardware at scale.

    I am aware of a history of Dell MPs having an issue with not discovering Dell servers reliably, however I heard that with the latest MP 4.1 this was improved. Are you sure you are using Dell server MP V 4.1? And have the Dell Server Administrator w/ SNMP installed on each computer? (just checking!)

    John Joyner
    MVP-SC-CDM


    John Joyner MVP-SC-CDM

    Tuesday, May 8, 2012 5:30 PM
  • v4.1 does still have issues.

    You have to constantly monitor the "Dell Unmanaged Servers Group"

    First, make sure you turn debug mode on (override the discovery to do this, instructions in the MP Guide), this will cause the discovery to create and write to a log file called "Discovery_DellServer.log" in the C:\Windows\Temp folder.  Using this log file you can usually figure out why it's "Unmanaged".

    On the majority of my servers, the issue is that the WMI Class doesn't exist.  The error in the log will be:

    "ERROR: UnManaged Server object created. Reason: Failure error while connecting to root-cimv2-Dell namespace." 

    The OMSA .mof file is not set to autorecover, so on the servers where I get the above error, I edit the "dccim32w2k3.mof" file (located here:  C:\Program Files (x86)\Dell\SysMgt\omsa\config) and add the following at the top of the file:

    #pragma autorecover

    Then save the file and import it using MOFCOMP dccim32w2k3.mof

    Then just restart the SCOM HealthService on the affected server and in a few minutes the server should be discovered.

    Now, I do still see these same servers in the Unmanaged group occasionally, usually with the following errors in the log file:

    ---- INFO: Dell_SoftwareFeature attributes retrieved successfully
    ---- ERROR: Unable to retrieve Dell_SoftwareFeature Err Number:-2147217357 Err Descr:
    ---- INFO: Dell_SoftwareFeature attributes retrieved successfully
    ----  ERROR: Object loop retrieval error. ErrNumber:-2147217357Description:
    ---- INFO: OMSA URL  :  OMSA Version  :

    a restart of the SCOM HealthService usually fixes this issue (or it will be successful next time the discovery runs on it's own).

    The servers where I see this happen the most are either SCCM/SMS Secondaries, or servers where the SCCM/SMS Client has to be repaired.

    • Edited by Richard Kinser Tuesday, May 8, 2012 7:08 PM
    • Proposed as answer by Blake Mengotto Wednesday, May 9, 2012 6:14 AM
    • Marked as answer by Yog Li Thursday, May 24, 2012 3:26 AM
    Tuesday, May 8, 2012 7:00 PM
  • Hi John,

    I work for Dell and this thread was brought to my attention, so I thought I would chime in.  I have a couple of suggestions:

    1. As an alternative to SCOM, you can manage Dell servers natively using a new, free Dell product called OpenManage Essentials (OME) which allows you to monitor and set up alerts for your servers.  More product information, demos, and a forum are available at DellTechCenter.com/OME.  Managing Dell servers with OME is preferable to the suggestion to use HP Insight Manager because Dell servers are supported natively by the Dell product, which should get you a much richer feature set.
    2. It seems that Ideally you want your MP to work correctly... have you opened a support case with Dell?  I asked someone from the team that works on the Dell Management Pack and he said he can better help troubleshoot if you are able to provide a trouble ticket number so we get a better idea of what your environment looks like.

    Hope that helps, feel free to get back in touch.

    • Marked as answer by Yog Li Thursday, May 24, 2012 3:26 AM
    Monday, May 14, 2012 10:35 PM
  • Hi John,

    I work for Dell.  What are the problems do you face when discovering Dell Servers?  What fixes have you tried?

    Tuesday, August 14, 2012 5:58 PM
  • I am having this same issue with the management pack version 4.1 getting the error number -2147023170. Sometimes it discovers, sometimes it does not and goes to Unmanaged. It seems to be hit or miss on some servers. I have been looking through the logs and it will sometimes discover, then the discovery re-runs and it undiscovers itself. Our number of Managed servers fluctuates hourly (I have the interval set to 1 hour, currently) We have been going through and upgrading OMSA to the latest version. It has helped on a few, but not all. I opened a case with Dell support, but so far no help. Did anybody make headway with this?
    Tuesday, November 20, 2012 9:39 PM