::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
