Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
Cisco UCS Monitoring - SCOM 2012

Answered Cisco UCS Monitoring - SCOM 2012

  • Wednesday, January 23, 2013 6:33 PM
     
     
    Sign In to Vote
    1

    Hi,

    We have SCOM 2012 Environment with 3 management servers. Among 3 three management servers, 2nd management server is dedicated to network monitoring and added to the new resource pool created and removed from AD Assignment and Notification resource pools.

    We have installed cisco ucs 2.5 MP on 2nd Management server and added Cisco UCS Instance successfully.

    Since we have installed the MP on 2nd Management server all the scripts related to Cisco UCS MP should run from 2nd Management server as per my understanding.

    Instead, we are seeing the event logs for cisco ucs mp on 3rd Management server as below that too warnings

    ==============================================================================

    The process will be dropped because the it has been waiting in the queue for more than 10 minutes.
     
    Command executed: "%windir%\system32\cscript.exe" /nologo "CISCO.UCS.R2.Fault.DataSource.vbs" "/exclude:" "/loging:0" "/moniker:sys/switch-B/slot-1/switch-ether/port-9" "/send:false" "/type:77fba2d966d2442e9b827db429ffd296" "/Url:https://xx.xx.xxx.x:443/nuova" "/user:abc"
    Working Directory: D:\Program Files\System Center 2012\Operations Manager\Server\Health Service State\Monitoring Host Temporary Files 906\34760\

    One or more workflows were affected by this. 

    Workflow name: CISCO.UCS.R2.77fba2d966d2442e9b827db429ffd296.Port.General.Rule
    Instance name: Port 9
    Instance ID: {4644834C-1E67-B1FE-EE43-30E1B5579552}
    Management group: SCOM_PROD

    ================================================================================

    Please let us know what is the cause of these warnings and why we are seeing the event logs on 3rd Management Server instead of 2nd Management Server.

    Any help in this regard will be very much appreciated.

    Thanks

    Kumaresan Lakshmanan

     

All Replies

  • Friday, January 25, 2013 8:45 AM
    Moderator
     
     Answered
    Sign In to Vote
    0


    Hi,

    Based on my understanding, I think this is an issue that the discovery or other workflows failed on server 3. If you don’t need the workflow work on this server, you can create an override for it.

    Please also check the following post about the configurations for the MP:

    Cisco UCS MP Download & Information Links
    http://thoughtsonopsmgr.blogspot.com/2012/11/cisco-ucs-mp-download-information-links.html

    As this is relate to the Cisco UCS MP, if you need further support about it, please also contact Cisco support.

    Thanks. 

    Nicholas Li
    TechNet Community Support

     
  • Sunday, January 27, 2013 3:27 PM
     
     Answered
    Sign In to Vote
    0

    Hi,

    Not sure whether it is possible to run the workflows and rules on particular management server through Overrides.

    But what I observed is that if we install the cisco ucs management pack on the management server which is already dedicated for network monitoring added into the specified resource pool, then the workflows never run from that server. Instead, it will run from other available servers.

    Also if we distribute the Run As Account created for cisco ucs connection to particular management server, then scom will not discover the cisco ucs systems. We should distribute the Run As Account to all of the management servers in a management group.

    So, the best way is to install the Cisco UCS Management Pack on the management server other than the one which is being used for network monitoring.

    This answer is based on my observation. It may also be in-correct.

    Thanks

    Kumaresan Lakshmanan