Topic
  • 6 replies
  • Latest Post - ‏2013-01-11T10:12:54Z by MaksKowalik
SystemAdmin
SystemAdmin
340 Posts

Pinned topic New ILMT installation, agent on VM is not registering

‏2013-01-04T10:45:31Z |
Hi, I wonder if anyone can help, I've installed ILMT on a windows server and patched to Fix Pack 1 as per the 7.5.0 installation guide. This seems to be working, i've downloaded and installed the latest software catalogue etc successfully.

I have now installed an agent on a RHEL6 linux VM. The agent installation was successful and I have confirmed that I can reach the ILMT server from the machine the agent is running.

If I run a ./tlmagent -cmds I can see the following:

/tlmagent -cmds
CODAG010I The command has been successfully executed.

Check Connection Status
Next execution time 04/01/13, 10:44:08
Last successful execution 04/01/13, 10:38:08
Last failed execution -
Period (seconds) 360

Plug In
Next execution time 04/01/13, 10:39:13
Last successful execution -
Last failed execution 04/01/13, 10:36:13
Period (seconds) 180

Upload Data
Next execution time 04/01/13, 11:31:39
Last successful execution -
Last failed execution 04/01/13, 08:21:09
Period (seconds) 11430

CODAG010I The command has been successfully executed.

As can be seen the connection check is successful, but the plugin/uploads are not.

A tcpdump of the data (I'm running both server and agent at level0) for a connection shows:

POST /msghandler/service HTTP/1.0
Host: x.x.x.x:9988
User-Agent: TLM Agent http/lib1.0
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Accept-Charset: UTF-8
Content-Type: text/plain
SubjectType: SLMAgent
SCPVersion: 7.5
Service: 2
SubjectID: <ilmt hostname>
Content-Length: 305

timestamp=1357229247000
customer=DEFAULT
agentId=8926414572033937580
serverGUID=
agentStatus=0
agentVersion=7.5.0.0
osName=Linux_x86
securityLevel=0
scanGroupName=DEFAULT
catalogMajorVersion=0
catalogMinorVersion=0
catalogHash=0
forceDeniedPlugin=false
hostname=<ilmt hostname>
<request:ok>
HTTP/1.0 200 OK
SubjectID: <agent hostname>
SCPVersion: 7.5
Content-Type: text/plain
Service: 2
Content-Language: en-GB
Date: Thu, 03 Jan 2013 16:07:26 GMT
Server: WebSphere Application Server/7.0

<response:0,-503,1357229246603:OK. Service successfull>
This appears to show a successful connection.

A tcpdump of the upload attempt shows:

POST /msghandler/service HTTP/1.0
Host: x.x.x.x:9988
User-Agent: TLM Agent http/lib1.0
Connection: close
Pragma: no-cache
Cache-Control: no-cache
Accept-Charset: UTF-8
Content-Type: multipart/mixed; boundary=---------------------------7d732c1530bd4
SubjectType: SLMAgent
SCPVersion: 7.5
Service: 25
SubjectID: <agent hostname>
Content-Length: 2529

---------------------------7d732c1530bd4
Content-Type: text/plain

timestamp=1357230519000
customer=DEFAULT
agentId=8926414572033937580
serverGUID=
agentStatus=0
<request:ok>

---------------------------7d732c1530bd4
Content-Disposition: form-data; name="HW Scan"; filename="tlm_hw_1357140530-1357140530.gz"
Content-Type: application/octet-stream

<snip>

---------------------------7d732c1530bd4--
HTTP/1.0 200 OK
SubjectID: <ilmt hostname>
SCPVersion: 7.5
Content-Type: multipart/mixed; boundary=---------------------------7d732c1530bd4
Service: 25
Content-Language: en-GB
Date: Thu, 03 Jan 2013 16:28:38 GMT
Server: WebSphere Application Server/7.0

<response:0,-1,1357230518161:Error in verifying the agent id>
Can anyone assist in debugging this issue? I can't understand why the agent is not registering.

If any more information/logs are required please let me know and i'll provide them.
Updated on 2013-01-11T10:12:54Z at 2013-01-11T10:12:54Z by MaksKowalik
  • SystemAdmin
    SystemAdmin
    340 Posts

    Re: New ILMT installation, agent on VM is not registering

    ‏2013-01-09T13:58:16Z  
    Hi,

    Your case requires a sort of debugging therefore I suggest to open PMR.

    There is a chain of actions that need to be done to localize the issue, including:
    checking firewall settings
    checking tlmagent.ini configuration file
    checking TCP/IP communication server-agent
    running tlmagent -p
    analyzing logs from agent
    analyzing logs from server
    changing the logs level maybe
    and even analyzing database content

    Regards,
    Michał Klak
    ILMT Central Team


    The postings on this site are my own and do not necessarily represent IBM's positions, strategies or opinions.
    Please contact product support if you need IBM's official advice.

    If you want to extend your knowledge of ILMT, you may check this site:
    https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/IBM+License+Metric+Tool
  • MaksKowalik
    MaksKowalik
    78 Posts

    Re: New ILMT installation, agent on VM is not registering

    ‏2013-01-09T14:37:44Z  
    Hi,

    please try tlmagent -p
    and then, on the server machine pack the C:\Program Files\IBM\tivoli\common\COD\logs directory and post it here. Maybe the server logs say something...

    Best regards,
    Maks Kowalik

    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
  • SystemAdmin
    SystemAdmin
    340 Posts

    Re: New ILMT installation, agent on VM is not registering

    ‏2013-01-09T18:12:41Z  
    Hi,

    please try tlmagent -p
    and then, on the server machine pack the C:\Program Files\IBM\tivoli\common\COD\logs directory and post it here. Maybe the server logs say something...

    Best regards,
    Maks Kowalik

    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    Hi, thanks for the responses.

    I attempted a tlmagent -p on the client but got the following error:

    ./tlmagent -p
    CODAG011E - The command cannot be executed.

    if I run a tlmagent -cmds I can see the plugin is being attempted and failing:

    /tlmagent -cmds
    CODAG010I The command has been successfully executed.

    Check Connection Status
    Next execution time 09/01/13, 18:11:00
    Last successful execution 09/01/13, 18:05:00
    Last failed execution -
    Period (seconds) 360

    Plug In
    Next execution time 09/01/13, 18:09:14
    Last successful execution -
    Last failed execution 09/01/13, 18:06:14
    Period (seconds) 180

    Upload Data
    Next execution time 09/01/13, 18:31:40
    Last successful execution -
    Last failed execution 09/01/13, 15:21:10
    Period (seconds) 11430

    CODAG010I The command has been successfully executed.

    I will try and get a capture of what happens when I run a tlmagent -p and what happens when the scheduled execution occurs.

    As mentioned in my first post there is agent to server communication, as shown by the payloads I've extracted from the tcpdump packet capture of the check connection status and upload data interactions. But if there is anything specific you'd like me to check please let me know.

    I've attached the logs requested.

    Thanks,
    Jag

    Attachments

  • MaksKowalik
    MaksKowalik
    78 Posts

    Re: New ILMT installation, agent on VM is not registering

    ‏2013-01-10T09:43:22Z  
    Hi, thanks for the responses.

    I attempted a tlmagent -p on the client but got the following error:

    ./tlmagent -p
    CODAG011E - The command cannot be executed.

    if I run a tlmagent -cmds I can see the plugin is being attempted and failing:

    /tlmagent -cmds
    CODAG010I The command has been successfully executed.

    Check Connection Status
    Next execution time 09/01/13, 18:11:00
    Last successful execution 09/01/13, 18:05:00
    Last failed execution -
    Period (seconds) 360

    Plug In
    Next execution time 09/01/13, 18:09:14
    Last successful execution -
    Last failed execution 09/01/13, 18:06:14
    Period (seconds) 180

    Upload Data
    Next execution time 09/01/13, 18:31:40
    Last successful execution -
    Last failed execution 09/01/13, 15:21:10
    Period (seconds) 11430

    CODAG010I The command has been successfully executed.

    I will try and get a capture of what happens when I run a tlmagent -p and what happens when the scheduled execution occurs.

    As mentioned in my first post there is agent to server communication, as shown by the payloads I've extracted from the tcpdump packet capture of the check connection status and upload data interactions. But if there is anything specific you'd like me to check please let me know.

    I've attached the logs requested.

    Thanks,
    Jag
    Hi,

    do you have
    
    organization = DEFAULT
    

    in the /etc/tlmagent.ini ?
    If so, please revert it to
    
    organization = DEFAULT_CUSTOMER
    

    retry agent plugin and tell us what's the result.

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
  • SystemAdmin
    SystemAdmin
    340 Posts

    Re: New ILMT installation, agent on VM is not registering

    ‏2013-01-10T15:44:45Z  
    Hi,

    do you have
    <pre class="jive-pre"> organization = DEFAULT </pre>
    in the /etc/tlmagent.ini ?
    If so, please revert it to
    <pre class="jive-pre"> organization = DEFAULT_CUSTOMER </pre>
    retry agent plugin and tell us what's the result.

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
    Thanks, this allowed the tlmagent -p to complete successfully.

    I now have the following in a tlmagent -cmds:

    ./tlmagent -cmds
    CODAG010I The command has been successfully executed.

    Check Connection Status
    Next execution time 10/01/13, 14:29:00
    Last successful execution 10/01/13, 14:23:00
    Last failed execution -
    Period (seconds) 360

    Download Parameters
    Next execution time 10/01/13, 14:27:24
    Last successful execution -
    Last failed execution -
    Period (seconds) 600

    Hardware Scan
    Next execution time 10/01/13, 14:56:24
    Last successful execution -
    Last failed execution -
    Period (seconds) 1800

    Upload Data
    Next execution time 11/01/13, 04:26:34
    Last successful execution -
    Last failed execution 10/01/13, 13:34:40
    Period (seconds) 50400

    CODAG010I The command has been successfully executed.

    Looking at the LMT console I can now see the agent has registered. The status of the agent is incomplete, which looking at the agent is due to the LMT not having received a software scan yet. Next scan is due tomorrow so I will see what the status is tomorrow afternoon.

    Many thanks for the help in getting the agent registered.
  • MaksKowalik
    MaksKowalik
    78 Posts

    Re: New ILMT installation, agent on VM is not registering

    ‏2013-01-11T10:12:54Z  
    Thanks, this allowed the tlmagent -p to complete successfully.

    I now have the following in a tlmagent -cmds:

    ./tlmagent -cmds
    CODAG010I The command has been successfully executed.

    Check Connection Status
    Next execution time 10/01/13, 14:29:00
    Last successful execution 10/01/13, 14:23:00
    Last failed execution -
    Period (seconds) 360

    Download Parameters
    Next execution time 10/01/13, 14:27:24
    Last successful execution -
    Last failed execution -
    Period (seconds) 600

    Hardware Scan
    Next execution time 10/01/13, 14:56:24
    Last successful execution -
    Last failed execution -
    Period (seconds) 1800

    Upload Data
    Next execution time 11/01/13, 04:26:34
    Last successful execution -
    Last failed execution 10/01/13, 13:34:40
    Period (seconds) 50400

    CODAG010I The command has been successfully executed.

    Looking at the LMT console I can now see the agent has registered. The status of the agent is incomplete, which looking at the agent is due to the LMT not having received a software scan yet. Next scan is due tomorrow so I will see what the status is tomorrow afternoon.

    Many thanks for the help in getting the agent registered.
    Hi,

    the "Incomplete" status has nothing to do with software scan. It's because your agent runs on virtualized system and the normal hardware (capacity) scan does not provide enough data to do correct PVU calculations. You have to configure connection between your ILMT server and VM Manager (vCenter, ESX, RHEV-M or Hyper-V host - depending on what manages your virtual machine).

    Best regards,
    Maks Kowalik


    The postings on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.