locked
ERROR with SCOM and TEC (Tivoli Console) Provider RRS feed

  • Question

  • Hi,

    I am having problem configuring the Interop Connector between my SCOM server (WIN2003) and my TEC Server (AIX 5.3)

    I have enabled TRACE and below is what I am observing (among many other erros):

    ----------------
    2011-09-28 14:28:06.968 [Microsoft.SystemCenter.Interop.Framework.Modules.WSManModule] ERROR Could not deliver some events.  No providers were available.  Could not forward any provider
    ---------

    I have the feeling that the TEC side (AIX) is not listening for incoming request of SCOM.

     

    The following command (run on SCOM server side) returns no error what makes me think that communication and authentication is well configured. (it though returns many config information)

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/sc
    x -username:root -password:MyPass -r:https://bms150:1270/wsman -auth:basic -skipCACheck -encoding:UTF-8

    Could someone please guide me on finding the cause of this interop conection problem? I don't want to paste here all TRACE, logs and printscreen but I, of course, will give the information as needed.

    Thank you very much!


    -- leoh
    Wednesday, September 28, 2011 5:47 PM

All replies

  • did you install both provider packages(scx+scxinterop)? Configured provider? Configured Connector?


    follow this thread http://social.technet.microsoft.com/Forums/en-US/interopgeneral/thread/fb00bd1b-11ab-4263-9676-f26abe6aa8cd/

    to troubleshoot "Could not forward any provider"

    Thursday, September 29, 2011 10:27 AM
  • ::I have installed in the AIX5.3  (TEC Server)

    scinterop-6.1.7000-58.aix.5.3.ppc-tec.lpp.gz
    scx-1.0.4-248.aix.5.ppc.lpp.gz

    http://screencast.com/t/X6vDrBjZt
    http://screencast.com/t/GKd6uPZRb0

    ::In the SCOM server I have installed:

    SciConnectorSetup_x64.msi
    OpsMgr Connector for IBM Tivoli Enterprise Console service up and running

    :: I have configured the Connector
    http://screencast.com/t/sg6bNYTQ

    :: I am not sure if the provider is correctly configured.

    The log says that there is no provider running. What would indicate me that it is running or not on AIX TEC Server? Another process? Another TCP port? A specific log file during start up? Is there any specific command to startup the provider or it starts automaticaly together with scx core agent?


    -- leoh
    Thursday, September 29, 2011 11:54 AM
  • provider should also be configured, follow deployment guide.

    to check if provider is running try

     

    /opt/microsoft/scx/bin/tools/scxadmin -status all 
    

    or simple

     

    ps -ef | grep scx 
    

     

    (not sure if this syntax is correct for AIX)

    take into account that providers do not run continuously and started/stopped by scx manager on demand.

    i.e. if no one utilizes provider then scx manager unloads it.  


    Thursday, September 29, 2011 1:23 PM
  • # scxadmin -status all
    scxcimserver: is running
    scxcimprovagt: 1 instance running

    # ps -elf|grep scx

    2:40 [scxcimse]
    0:45 /opt/microsoft/scx/bin/scxcimprovagt 0 12 16 root SCXCoreProviderModule

     

    Everything seems to be running. That why I cannot understand why it says no provider found...

    The SCX core agent is ok. I have being monitoring this server for a while.

    I found this command on another thread (run on SCOM Server):

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_OperatingSystem?__cimnamespace=root/scx -username:root -password:nsasDev1 -r:https://bms150:1270/wsman -auth:basic encoding:UTF-8

    which gives me the following result:

    http://screencast.com/t/gbQMmIbxmr

    So, SOAP is fine, Port 1270 up, but still no provider found?


    -- leoh
    Thursday, September 29, 2011 1:54 PM
  • # scxadmin -status all
    scxcimserver: is running                   <----- scx manager
    scxcimprovagt: 1 instance running <----- core provider

    TEC provider will be named like SCXInteropProviderTecAdapter

    check folder /opt/microsoft/scx/lib/providers to be sure you installed binaries.

     

    and then try to call TEC provider 

    winrm enumerate http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Connector?__cimnamespace=root/scx -username:root -password:nsasDev1 -r:https://bms150:1270/wsman -auth:basic -encoding:utf-8

    have you followed troubleshooting guide posted above?

     

    Thursday, September 29, 2011 4:27 PM
  • ::Binaries seem to installed

    http://screencast.com/t/pSHbwBFBaS74

    ::The winrm command returned

     

    Fault
        Code
            Value = SOAP-ENV:Sender
            Subcode
                Value = wsa:DestinationUnreachable
        Reason
            Text = CIM_ERR_NOT_FOUND: SCX_Connector
    
    Error number:  -2144108526 0x80338012
    The client cannot connect to the destination specified in the request. Verify that the service on th
    e destination is running and is accepting requests. Consult the logs and documentation for the WS-Ma
    nagement service running on the destination, most commonly IIS or WinRM. If the destination is the W
    inRM service, run the following command on the destination to analyze and configure the WinRM servic
    e: "winrm quickconfig".

     

    What seeems to prove that provider is not running.

    The debug steps (from that other thread), has another winrm command that returns pretty much the same error (http://technet.microsoft.com/en-us/library/ee809025.aspx):

    winrm e http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Connector?__cimnamespace=root/scx -r:https://bms150:1270 -u:root -p:nsasDev1 -auth:basic -encoding:utf-8 -skipCAcheck -skipCNcheck -filter:"select * from SCX_Connector where ManagementGroupName = "MyRMSGroup"

    Fault
        Code
            Value = SOAP-ENV:Sender
            Subcode
                Value = wsa:DestinationUnreachable
        Reason
            Text = CIM_ERR_NOT_FOUND: SCX_Connector
    
    Error number:  -2144108526 0x80338012
    The client cannot connect to the destination specified in the request. Verify that the service on th
    e destination is running and is accepting requests. Consult the logs and documentation for the WS-Ma
    nagement service running on the destination, most commonly IIS or WinRM. If the destination is the W
    inRM service, run the following command on the destination to analyze and configure the WinRM servic
    e: "winrm quickconfig".


    During the installation of the provider (AIX TEC Side) I did:

    #gzip -d scinterop-6.1.7000-58.aix.5.3.ppc-tec.lpp.gz
    # installp -X -d scinterop-6.1.7000-58.aix.5.3.ppc-tec.lpp MSFTscinteropTec.rte

    http://screencast.com/t/cgfnbwx08v

    There are some other steps related to TEC configuration. The scinterop comes with a bunch of scripts to automate these configurations and some of them won't work without some customization. But before getting worried about proper event mapping (TEC classess) I think I should be able to see something getting to Tec Port (5529) or, at least, stop getting those "no provider found" alarms from SCOM Server.

    Anyway, it seems to me that this TEC provider specific process (SCXInteropProviderTecAdapter) may not be running because of some missing configuration. If so, it should be able to tell me: "Hey, I am giving up my startup because tec-foo.cfg is missing".

    The /var/opt/microsoft/scx/log directory has no clue about it. I tried to enable tracing for scx agent using the following command, which returned a weird output which deservers a thread alone for it self :) :

    /opt/microsoft/scx/bin/tools/scxadmin -log-set all verbose

    exec(): 0509-036 Cannot load program /opt/microsoft/scx/bin/tools/scxcimconfig because of the following errors:
    rtld: 0712-001 Symbol findBaseName__Q2_7Pegasus6SystemFPCc was referenced
          from module scxcimconfig(), but a runtime definition
          of the symbol was not found.
    rtld: 0712-001 Symbol __ct__Q2_7Pegasus17ConfigFileHandlerFRCQ2_7Pegasus6StringRCQ2_7Pegasus6Stringb was referenced
          from module scxcimconfig(), but a runtime definition
          of the symbol was not found.
    

     

    Summing up:
    Now I know that there is a TEC Provider Process that should be running. The winrm command proved that no SCX_Connector is registred. What did I do that was not right?


    -- leoh
    Thursday, September 29, 2011 5:12 PM