To follow up on yesterday’s fix for a problem importing the Red Hat Linux Management Pack on System Center Operations Manager 2007, here’s another tip for an issue you may run into where the Discovery Wizard fails when attempting to discover UNIX/Linux servers:
While attempting to perform a UNIX/Linux server discovery within System Center Operations Manager 2007 R2, the Discovery Wizard ultimately fails with the following error:
"The Discovery Wizard was unable to locate any Unix/Linux support information. Two possible scenarios can cause this.
-Unix/Linix Operating System Management Packs are not imported
-Unix/Linux support information has not been fully discovered.
Please import the Operating System Management Packs for the Unix/Linux platforms or if the Management Packs are already imported, please run the Discovery Wizard again in a few minutes."
The only option available after this point is to click the OK dialog box and navigate back to the Operations Console.
This issue is usually caused by the fact that the Unix Supported Agents information has not been discovered accordingly. Without the Unix Supported Agents information populated within the Discovered Inventory, the Discovery Wizard cannot successfully discover a Unix/Linux agent. This information can be found at the following location:
From the System Center Operations Manager 2007 R2 console, Monitoring pane, click Discovered Inventory. Change the Target Type to "Unix Supported Agents" and click OK.
If nothing is returned then the system is not aware of the classes that are required for the UNIX/Linux agents. When properly discovered, the Unix Supported Agents should contain information within the Discovered Inventory such as the following:
State \ Name (UNIX\Linux Version) \ Agent Version \ Agent Build \ Supported OS \ Supported Architecture \ Package Extension
In addition, you may also see the following Event ID 3333 on the Root Management Server.
Event ID 3333
Data Access Layer rejected retry on SqlError:
Request: p_ManagedEntityInsert — (BaseManagedEntityId=a24b2df4-ff24-0f6e-a7cc-16079f98f4f5), (TypedManagedEntityId=a24b2df4-ff24-0f6e-a7cc-16079f98f4f5), (ManagedTypeId=ea99500d-8d52-fc52-b5a5-10dcd1e9d2bd), (FullName=Microsoft.Windows.Computer:host.contoso.com), (Path=), (Name=host.contoso.com), (TopLevelHostEntityId=a24b2df4-ff24-0f6e-a7cc-16079f98f4f5), (DiscoverySourceId=5ed2da35-708d-cab8-db04-68c527291888), (HealthServiceEntityId=0810a730-6dd1-540a-436e-bdde822e02b5), (PerformHealthServiceCheck=True), (TimeGenerated=11/3/2010 6:48:19 PM), (RETURN_VALUE=1)
Message: Health service ( RMS.contoso.com) should not generate data about this managed type ( Microsoft.Windows.Computer ) object Id ( A24B2DF4-FF24-0F6E-A7CC-16079F98F4F5 ).
This particular Event ID 3333 indicated that the RMS could not generate data about another managed type, or that Server Proxying was not enabled on the Root Management Server.
This issue is typically resolved by simply enabling Server Proxy for the Root Management Server in the environment. The exact steps as follows from the System Center Operations Manager 2007 R2 console are as follows:
Administration pane \ Management Servers \ Root Management Server \ Right-Click and select Properties \ Security Tab
From the Server Proxy section simply check the box to "Allow this server to act as a proxy server and discover managed objects on other computers."
Hope this helps,
Nicholas Dodge | System Center Senior Support Escalation Engineer
The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis