Check A2A Client Connection Status

The following table describes the different A2A Client connection status values and the condition under which the A2A Client has that status.
capam33
HID_A2AClientsPanel
You can verify the connection status of an A2A Client from the GUI and from the CLI. The A2A Client connection status is shown as
Online
,
Offline,
or
Unknown
on the Client List page.
The following table describes the different A2A Client connection status values and the condition under which the A2A Client has that status.
Icon
Status
Condition
Green Bubble
Online
The A2A Client has connected to the
Privileged Access Manager
appliance within the configured threshold.
Yellow Bubble
Unknown
The A2A Client has not connected to the 
Privileged Access Manager
appliance within the configured threshold.
Red Bubble
Offline
The A2A Client service
cspmclientd
is stopped.
Use the following procedure to verify the A2A Client connection status from the GUI.
Follow these steps:
  1. Select
    Credentials
    ,
    Manage A2A
    ,
    Clients
    . The Client List page appears.
  2. Select the server where the A2A client whose logs you want to view is installed and select
    VIEW
    . The Client Details page appears.
    The
    Connection Status
    field displays the previous connection status icon followed by the last status updated date and time.
  3. Select the
    Check Connection Status
    button. The updated A2A Client connection status is displayed in the Connection Status field with a connection status icon followed by the connection status updated date and time.
Use the following procedure to verify the A2A Client connection status from the CLI.
Follow these steps:
  1. Retrieve the request server ID by running the
    searchRequestServer
    CLI command.
  2. Use the resulting request server ID in the
    checkConnectionStatus
    CLI command. The following is an example:
    capam_command adminUserID=admin capam=mycompany.com cmdName=checkConnectionStatus RequestServer.ID=1001
  3. Enter your password at the prompt. Credential Manager returns the following XML command string:
    <CommandResult> <cr.itemNumber>0</cr.itemNumber> <cr.statusCode>400</cr.statusCode> <cr.statusDescription>Success.</cr.statusDescription> <cr.result> <RequestServer> <type>CLIENT</type> <port>28888</port> <osName>Windows 7</osName> <osVersion>7.0</osVersion> <active>true</active> <action></action> <osPlatform>win</osPlatform> <clientVersionNum>4.4.1</clientVersionNum> <currentFingerprint>aXrPcM52mlPUH+yqaDqjN6+wi+8=</currentFingerprint> <currentKey>{1}fec6fe90d3c5b63aaad9f1f0f084554a426a8909448c7e9239544e5f0de55217a4d9a3d6736317c2a413a3865e2725de0244323fcd02ce1aea0afd29396145f6</currentKey> <oldKey>{1}58005ca6fbf6101d7428cda4580ed8c5437fc5e1ab3e24d3c7c53dcffed3809311a18ff0ce7c7c5175a769b8f4e762f012b6783450f4b4b4d60e9131c32223a2</oldKey> <pendingAcknowledgement>false</pendingAcknowledgement> <osArchitecture>x86</osArchitecture> <patchStatus>Idle</patchStatus> <previousClientVersion></previousClientVersion> <pendingFingerprint></pendingFingerprint> <pendingFingerprintDate></pendingFingerprintDate> <actionRequired>false</actionRequired> <connectionStatus>1</connectionStatus> <preserveHostName>false</preserveHostName> <clientType>java</clientType> <siteID>1000</siteID> <connectionStatusUpdateDate>Thu May 05 11:39:43 UTC 2011</connectionStatusUpdateDate> <currentFingerprintDate>2011-05-05 10:00:42.477</currentFingerprintDate> <lastPatchStatusChangeDate></lastPatchStatusChangeDate> <hostName>xp-sushma.cpa.intra</hostName> <IPAddress>192.168.0.230</IPAddress> <ID>1001</ID> <Attribute.cspm_serverkeyid>1</Attribute.cspm_serverkeyid> <Attribute.descriptor1></Attribute.descriptor1> <Attribute.descriptor2></Attribute.descriptor2> <createDate>Thu May 05 10:00:42 UTC 2011</createDate> <updateDate>Thu May 05 10:59:00 UTC 2011</updateDate> <updateUser>CSPM_CLIENT</updateUser> <extensionType></extensionType> <createUser>CSPM_CLIENT</createUser> <hash>j3kMJ+3DBi/EQXSV76bdZ5Or15Q=</hash> </RequestServer> </cr.result> </CommandResult>