Blogs

Showing 1 - 5 of 16 results.
Items per Page 5
of 4

Forums

« Back to Microsoft Discussions

RE: UCS mgmt pack for SCOM 2012 not collecting data

Combination View Flat View Tree View
Threads [ Previous | Next ]
Hi Jed,
I can help you with the issue. 
Can you check the following to start with
(1) The Run-As-Account is configured as in the quick start guide. Are you using less-secure or more-secure. If you are using more-secure, have you distributed the accounts manually?
(2) Is the Run-As-Account associated to the MP profile.
 
You can directly write to me at vvb@cisco.com to speed up the resolution. I can also help you do a webex with the engineering team, If required.
 
Thanks,
Vijay Vikrant Balyan
 

I have a similar issue using the 2.5 version of the Cisco UCS management pack.  I have installed per the provided documentation and all was successful.  I’m using the current Cisco emulator to test the management pack with our DEV SCOM system.  The account used for the MP install is the config ID. 
Everything tests successfully and the emulator is discovered, but stays unmonitored.  I verified the discovery rules are enabled.
The Run-As-Account is configured using less-secure method and has been associated with the MP profile.
What do I need to do so that the UCS Instance changes from unmonitored to monitored in SCOM.
My DEV version of SCOM is 2012 released CU1, no SP1.
Thanks,
-Matt.
 

Matt Martin:
I have a similar issue using the 2.5 version of the Cisco UCS management pack.  I have installed per the provided documentation and all was successful.  I’m using the current Cisco emulator to test the management pack with our DEV SCOM system.  The account used for the MP install is the config ID. 
Everything tests successfully and the emulator is discovered, but stays unmonitored.  I verified the discovery rules are enabled.
The Run-As-Account is configured using less-secure method and has been associated with the MP profile.
What do I need to do so that the UCS Instance changes from unmonitored to monitored in SCOM.
My DEV version of SCOM is 2012 released CU1, no SP1.
Thanks,
-Matt.
 

I am having the exact same problem. All my credentials look correct, and when I test the connection during the setup, all is successful. Its been several hours and all the components still show as "unmonitored". Is there any way to force this to attempt to collect the data? I have tried reinstalling the management pack as well. 
 

Paarin Mehta:

Matt Martin:

I have a similar issue using the 2.5 version of the Cisco UCS management pack.  I have installed per the provided documentation and all was successful.  I’m using the current Cisco emulator to test the management pack with our DEV SCOM system.  The account used for the MP install is the config ID. 
Everything tests successfully and the emulator is discovered, but stays unmonitored.  I verified the discovery rules are enabled.
The Run-As-Account is configured using less-secure method and has been associated with the MP profile.
What do I need to do so that the UCS Instance changes from unmonitored to monitored in SCOM.
My DEV version of SCOM is 2012 released CU1, no SP1.
Thanks,
-Matt.
 


I am having the exact same problem. All my credentials look correct, and when I test the connection during the setup, all is successful. Its been several hours and all the components still show as "unmonitored". Is there any way to force this to attempt to collect the data? I have tried reinstalling the management pack as well. 
 

 
The 2.6 version of the MP is released on CDN. You should not notice this problem with that. v2.5 has an issue which shows up in some scenarios - specifically when you have a resource pool configuration on the Management servers. This problem would not show up if you have a single management server. There is a patch available for v2.5 to fix this; but I would suggest trying out v2.6.

Vijay, 
I upgraded to version 2.6 and am still seeing the issue. I am running dual management servers, which you alluded may be the root of my issue. Any other suggestions?

Paarin,
Then the problem very likely is your configuration. If you can verify ones that the configuration is as per the document. If you still see the issue, drop me an email at vvb@cisco.com and we will look at your setup and help you out.
Thanks,
Vikrant

Collateral


No files available