[ITM] IP.SPIPE vs IP.PIPE / ITCAM Pain!
Martin Butler <[email protected]>
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <OFE383F65A.DE96839B-ON85257B83.0071FA8D-85257B83.0076274F__41775.3219874159$1370640686$gmane$org@ca.ibm.com> |
We are fighting against [64 bit] ITCAM 6.3 agents (SQL and Active
Directory) that will not connect using ip.spipe.
Ordinarily we use IP.SPIPE (Primary Protocol) and IP.PIPE (Secondary
Protocol) with a primary and secondary RTEMS.
Our desired state is to use IP.SPIPE only for a particular client.
In the above configuration, the 64 bit ITCAM agent will always use PIPE, to
our increasing frustration!
(51B23113.0000-654:kde11sa.c,94,"KDE1_StringToAddress") Status
1DE00010=KDE1_STC_INVALIDFAMILY
(51B23113.0001-654:kdck1fn.c,76,"socket__from_name") status=1002000a,
"address family invalid", ncs/KDC1_STC_FAMILY_NOT_VALID
(51B23113.0002-654:kraarreg.cpp,2425,"PrimaryTEMSperiodicLookupThread")
Unable to create lookup socket to host IP.SPIPE:#172.17.151.10, status =
1002000a!
In the case of SQL - we found a PMR that advised to update the PATH
variable to add {HOME}\GSK7_KIT and update {HOME}\TMAITM6 to
{HOME}\TMAITM6_X64, and copy kdebe.dll into {HOME}\GSK7_X64\lib64
This DID fix the SQL agent issue. Is this the panacea for ALL 64 bit
agents ????
Sample Problem
Operating system = W2K8 R2 (64 bit)
Monitoring Agent for Active Directory WIX64 Version: 06.30.00.00 Build:
22911
We cannot get this agent to connect via SPIPE, despite the NT agent
connecting via SPIPE.
Any advice would be greatly appreciated.
Martin
Martin 410 Albert Street (Embedded
(M.A.) image moved to
Butler file:
pic09387.gif)
Senior IT Waterloo, Ontario
Services N2L 3V3
Professional
- Tivoli on
Demand
Services
T7Z Canada
DM
Phone: +1-519-880-2920
e-mail: [email protected]
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]
pic09387.gif
(image/gif, 360 B) - not displayed