Topic
  • 13 replies
  • Latest Post - ‏2013-10-13T02:17:26Z by leone145
SystemAdmin
SystemAdmin
13279 Posts

Pinned topic No Access to AIX Common agent system

‏2008-12-15T03:05:16Z |
I am trying to manage two AIX machines that are running the common agent.

root@AIX_I:/opt/ibm/director/agent/bin#ksh lwistatus.sh
which: 0652-141 There is no lwistatus.sh in /usr/bin /etc /usr/sbin /usr/ucb /usr/bin/X11 /sbin /usr/java14/jre/bin /usr/java14/bin.
which: 0652-141 There is no lwistatus.sh in /usr/bin /etc /usr/sbin /usr/ucb /usr/bin/X11 /sbin /usr/java14/jre/bin /usr/java14/bin.
ACTIVE
root@AIX_I:/opt/ibm/director/agent/bin#

&

root@AIX_I:/opt/ibm/director/agent/runtime/agent/bin#ksh endpoint.sh start
The LWI Nonstop Profile is already running.
root@AIX_I:/opt/ibm/director/agent/runtime/agent/bin#

also

root@AIX_I:/opt/ibm/director/agent/runtime/agent/bin#lssrc -s platform_agent
Subsystem Group PID Status
platform_agent 18422 active
root@AIX_I:/opt/ibm/director/agent/runtime/agent/bin#

The above configuration / status is on both systems.

From IBM Director I can discover both but one gives me no access or access "fail"

and the other gives me access but shows as no agent system.

One system has the following:
Protocols: CAS, SNMP, SSH
And the other has the following:
Protocols: SNMP, SSH

Any help would be great thanks,

William
Updated on 2009-12-03T14:12:44Z at 2009-12-03T14:12:44Z by christian_bay
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-15T07:45:17Z  
    Hi William,

    that is just the same behaviour I can see on my systems. Some systems went on "Failed" or even "Unknown" on the Access-Row. Verifying the connection brings no success, so I do not know what to do here.

    Other thing is, that a system with common agent shows up as a platform agent with "No Access".

    Is there s script or something on the client reestablishing the Access ??

    Alf
  • gcorneau
    gcorneau
    234 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-15T14:09:58Z  
    Hi William,

    that is just the same behaviour I can see on my systems. Some systems went on "Failed" or even "Unknown" on the Access-Row. Verifying the connection brings no success, so I do not know what to do here.

    Other thing is, that a system with common agent shows up as a platform agent with "No Access".

    Is there s script or something on the client reestablishing the Access ??

    Alf
    Try running the following command to link the Common Agent to the Management Server:

    /opt/ibm/director/agent/runtime/agent/toolkit/bin/configure.sh -amhost <hostname> -passwd <password>

    Where the amhost is the Agent Manager host (typically the Director Server) and the password is (not necessarily) the Server password but the Agent Manager registration password that was configured as part of the Server setup (at least, for AIX this is the case).

    Glen Corneau
    IBM Power Systems Advanced Technical Support
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T06:11:37Z  
    • gcorneau
    • ‏2008-12-15T14:09:58Z
    Try running the following command to link the Common Agent to the Management Server:

    /opt/ibm/director/agent/runtime/agent/toolkit/bin/configure.sh -amhost <hostname> -passwd <password>

    Where the amhost is the Agent Manager host (typically the Director Server) and the password is (not necessarily) the Server password but the Agent Manager registration password that was configured as part of the Server setup (at least, for AIX this is the case).

    Glen Corneau
    IBM Power Systems Advanced Technical Support
    Hi Glen,

    I tried this several times,with different results. Sometimes the access is working and the "light" goes on green. Sometimes no effect and the "light" stays in Unknown. Ever if I run a discover from the commandline of the server, nothing changes. Then I tried to delete the client and rediscover, no success.

    Where is the log I can look into and see, what is happening and going wrong on my client?

    regards

    Alf
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T11:58:57Z  
    Hi Glen,

    I tried this several times,with different results. Sometimes the access is working and the "light" goes on green. Sometimes no effect and the "light" stays in Unknown. Ever if I run a discover from the commandline of the server, nothing changes. Then I tried to delete the client and rediscover, no success.

    Where is the log I can look into and see, what is happening and going wrong on my client?

    regards

    Alf
    I get the following (where IBM Director indicated no access but with common agent):
    ###########################################################################
    root@AIX_I:/#bin/configure.sh -amhost 192.168.168.11 -passwd ibm4ibm <

    BTC7861I Checking if the common agent is already registered...done

    BTC7872I Checking the common agent state...the common agent is running
    BTC7875I Stopping the common agent...done

    Resolved configuration:
    The common agent connection information:
    name = localhost
    port = 9510
    jport = 9514
    nport = 9515
    wport = disabled
    wsport = disabled
    The agent manager information:
    Common agent managed by the agent manager
    amhost = 192.168.168.11
    amport = 9513
    ctxroot = /AgentMgr
    The common agent service information:
    noinstall = false
    nostart = false

    BTC7878I Validating the resolved configuration of the common agent...done
    BTC8623I Validating the connection to the agent manager...done
    BTC8616W The connection to the agent manager has been established successfully, but the trust certificate downloaded from the certificate authority is not yet valid.
    BTC8624I Validating the registration password...failed
    BTC8618E The password is not valid. The common agent cannot register.
    root@AIX_I:/#
    ###########################################################################

    and on the other one I get (where IBM Director indicated access but as agent less):

    root@AIX_II:/#/bin/configure.sh -amhost 192.168.168.11 -passwd ibm4ibm <

    BTC7861I Checking if the common agent is already registered...done

    BTC7872I Checking the common agent state...the common agent is running
    BTC7875I Stopping the common agent...done

    Resolved configuration:
    The common agent connection information:
    name = localhost
    port = 9510
    jport = 9514
    nport = 9515
    wport = disabled
    wsport = disabled
    The agent manager information:
    Common agent managed by the agent manager
    amhost = 192.168.168.11
    amport = 9513
    ctxroot = /AgentMgr
    The common agent service information:
    noinstall = false
    nostart = false

    BTC7878I Validating the resolved configuration of the common agent...done
    BTC8623I Validating the connection to the agent manager...done
    BTC8624I Validating the registration password...done

    BTC7880I Configuring the common agent...done
    BTC7881I Installing the common agent service...done
    BTC7882I Starting the common agent...done
    root@AIX_II:/#
    ###########################################################################

    Very strange,

    William
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T12:14:28Z  
    I get the following (where IBM Director indicated no access but with common agent):
    ###########################################################################
    root@AIX_I:/#bin/configure.sh -amhost 192.168.168.11 -passwd ibm4ibm <

    BTC7861I Checking if the common agent is already registered...done

    BTC7872I Checking the common agent state...the common agent is running
    BTC7875I Stopping the common agent...done

    Resolved configuration:
    The common agent connection information:
    name = localhost
    port = 9510
    jport = 9514
    nport = 9515
    wport = disabled
    wsport = disabled
    The agent manager information:
    Common agent managed by the agent manager
    amhost = 192.168.168.11
    amport = 9513
    ctxroot = /AgentMgr
    The common agent service information:
    noinstall = false
    nostart = false

    BTC7878I Validating the resolved configuration of the common agent...done
    BTC8623I Validating the connection to the agent manager...done
    BTC8616W The connection to the agent manager has been established successfully, but the trust certificate downloaded from the certificate authority is not yet valid.
    BTC8624I Validating the registration password...failed
    BTC8618E The password is not valid. The common agent cannot register.
    root@AIX_I:/#
    ###########################################################################

    and on the other one I get (where IBM Director indicated access but as agent less):

    root@AIX_II:/#/bin/configure.sh -amhost 192.168.168.11 -passwd ibm4ibm <

    BTC7861I Checking if the common agent is already registered...done

    BTC7872I Checking the common agent state...the common agent is running
    BTC7875I Stopping the common agent...done

    Resolved configuration:
    The common agent connection information:
    name = localhost
    port = 9510
    jport = 9514
    nport = 9515
    wport = disabled
    wsport = disabled
    The agent manager information:
    Common agent managed by the agent manager
    amhost = 192.168.168.11
    amport = 9513
    ctxroot = /AgentMgr
    The common agent service information:
    noinstall = false
    nostart = false

    BTC7878I Validating the resolved configuration of the common agent...done
    BTC8623I Validating the connection to the agent manager...done
    BTC8624I Validating the registration password...done

    BTC7880I Configuring the common agent...done
    BTC7881I Installing the common agent service...done
    BTC7882I Starting the common agent...done
    root@AIX_II:/#
    ###########################################################################

    Very strange,

    William
    I removed both from IBM Director and re-discovered, now they have switched.

    192.168.168.13 access is OK
    192.168.168.17 access is fail

    Both system appear as: No Agent

    William
  • gcorneau
    gcorneau
    234 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T17:31:19Z  
    I removed both from IBM Director and re-discovered, now they have switched.

    192.168.168.13 access is OK
    192.168.168.17 access is fail

    Both system appear as: No Agent

    William
    You may be experiencing the same strangeness I saw during some of my testing.

    Try removing the two systems again from the server, then check both
    1. smcli lssys
    2. smcli lsmeps

    If you have an entry in the "lsmeps" output but not in the "lssys" output, then I suggest stopping and restarting the Server and see if this clears up the bogus "meps" entry. Its the only way I could figure out to do it and it cleared up the inability to securely and consistent authenticate with one of my AIX Agents.

    Otherwise, you might need to open a support ticket (if you have a support contract). Not sure exactly which log would be most helpful.


    Glen Corneau
    IBM Power Systems Advanced Technical Support
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T18:42:29Z  
    • gcorneau
    • ‏2008-12-16T17:31:19Z
    You may be experiencing the same strangeness I saw during some of my testing.

    Try removing the two systems again from the server, then check both
    1. smcli lssys
    2. smcli lsmeps

    If you have an entry in the "lsmeps" output but not in the "lssys" output, then I suggest stopping and restarting the Server and see if this clears up the bogus "meps" entry. Its the only way I could figure out to do it and it cleared up the inability to securely and consistent authenticate with one of my AIX Agents.

    Otherwise, you might need to open a support ticket (if you have a support contract). Not sure exactly which log would be most helpful.


    Glen Corneau
    IBM Power Systems Advanced Technical Support
    OK using this document:

    https://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/director_6.1/fqm0_c_elearning_managing_system_access_and_security.html

    to clean up and

    uninstalling IBM Director using this script:

    /opt/ibm/director/bin/diruninstall

    and then reinstalling the agents.

    Results:

    On one system I got it as Common Agent but with no access
    The other system it detected it as Platform Agent with access

    Very strange and this is just a LAB environment. Imagine when I try this as pre-sales for a customer.

    root@AIX_II:/#smcli lssys
    ksh: smcli: not found.
    root@AIX_II:/#smcli lsmeps
    ksh: smcli: not found.
    root@AIX_II:/#

    Thanks Glen, any help would be great.

    William
  • gcorneau
    gcorneau
    234 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T19:09:33Z  
    OK using this document:

    https://publib.boulder.ibm.com/infocenter/systems/index.jsp?topic=/director_6.1/fqm0_c_elearning_managing_system_access_and_security.html

    to clean up and

    uninstalling IBM Director using this script:

    /opt/ibm/director/bin/diruninstall

    and then reinstalling the agents.

    Results:

    On one system I got it as Common Agent but with no access
    The other system it detected it as Platform Agent with access

    Very strange and this is just a LAB environment. Imagine when I try this as pre-sales for a customer.

    root@AIX_II:/#smcli lssys
    ksh: smcli: not found.
    root@AIX_II:/#smcli lsmeps
    ksh: smcli: not found.
    root@AIX_II:/#

    Thanks Glen, any help would be great.

    William
    Sorry, I've got the PATH variable set to include /opt/ibm/director/bin (where smcli lives).

    When I had the problem I described, no amount of fiddling on the agent system cleared it up, I had to bounce the Director server via smstop/smstart (again, in the /opt/ibm/director/bin directory). This cleared up the bogus MEP and things worked like a charm after that.

    At least with a support contract a paying customer can send in some grablogs/service information to be analyzed. But I completely understand.

    Glen Corneau
    IBM Power Systems Advanced Technical Support
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T20:01:33Z  
    • gcorneau
    • ‏2008-12-16T19:09:33Z
    Sorry, I've got the PATH variable set to include /opt/ibm/director/bin (where smcli lives).

    When I had the problem I described, no amount of fiddling on the agent system cleared it up, I had to bounce the Director server via smstop/smstart (again, in the /opt/ibm/director/bin directory). This cleared up the bogus MEP and things worked like a charm after that.

    At least with a support contract a paying customer can send in some grablogs/service information to be analyzed. But I completely understand.

    Glen Corneau
    IBM Power Systems Advanced Technical Support
    Glen,

    I believe this would work on an AIX system of IBM Director, but I have Windows 2003 as IBM Director and the agents are AIX 5.3

    oslevel -s
    5300-06-09-0844
    Cheers,

    William
  • gcorneau
    gcorneau
    234 Posts

    Re: No Access to AIX Common agent system

    ‏2008-12-16T21:23:24Z  
    Glen,

    I believe this would work on an AIX system of IBM Director, but I have Windows 2003 as IBM Director and the agents are AIX 5.3

    oslevel -s
    5300-06-09-0844
    Cheers,

    William
    Not sure of the PATH then, but the smcli command is there on the Windows Systems Director Server as well.

    There is this caveat in the smcli man page for Windows SD Servers:

    Prerequisite: Management servers running Windows® XP, Windows 2000, or Windows 2003 require msvcr80.dll to run smcli. You can obtain the dynamic link library (DLL) by installing vcredist_x86.exe. For information about downloading and installing this file, see https://www.microsoft.com/downloads.

    Hopefully someone more Windows SD Server-saavy will chime in...


    Glen Corneau
    IBM Power Systems Advanced Technical Support
  • SystemAdmin
    SystemAdmin
    13279 Posts

    Re: No Access to AIX Common agent system

    ‏2009-06-23T10:59:55Z  
    Im having simmilar problems with my lab-environment...

    I can request acces to my windows and linux servers, and it is all fine and all. But as soon as I install the common agent on the servers, access turns to "no access" and requesting it again returns a big fat "failed" :/
  • christian_bay
    christian_bay
    3 Posts

    Re: No Access to AIX Common agent system

    ‏2009-12-03T14:12:44Z  
    Im having simmilar problems with my lab-environment...

    I can request acces to my windows and linux servers, and it is all fine and all. But as soon as I install the common agent on the servers, access turns to "no access" and requesting it again returns a big fat "failed" :/
    I just had the same problems but I resolved it. I unlocked every system successfully until I installed the Common Agent. The Platform Agent still worked, but every machine with the freshly installed Common Agent instantly lost access after rediscovery. On my Management Server I had the The RedHat default firewall running which was a little bit too restrictive... Open every port from the manual and it will work.
  • leone145
    leone145
    1 Post

    Re: No Access to AIX Common agent system

    ‏2013-10-13T02:17:26Z  
    I just had the same problems but I resolved it. I unlocked every system successfully until I installed the Common Agent. The Platform Agent still worked, but every machine with the freshly installed Common Agent instantly lost access after rediscovery. On my Management Server I had the The RedHat default firewall running which was a little bit too restrictive... Open every port from the manual and it will work.

    Hate to dig up an old post, but I am seeing the common agent issue as well. Fresh install pushed from Director Server to AIX host running 6.1, turn access to locked. I've tried everything, removing and wiping the directories, re-setting the agent manager password on the manager, ensuring all firewalls are disabled. Has anyone found a viable solution to this issue? My Director Server is running 6.3.3.