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.