Generating a Patch Report for a Specific Server

This procedure generates a report that displays the cached patch state data for a given server.

As with other PAIR reporting features, executing the commands in this procedure does not connect with the target servers and retrieve patch information. The report output is cached patch state data and is only as current as the last refresh. The last refresh date can be determined by noting the UTC time stamp reflected in the field labeled Data retrieved on:. To retrieve the latest patch information from a given server, or all servers, see Refresh Patch Information.

Multiple patches may be reflected in the output. Valid patch states include ACCEPTED, REJECTED, or PENDING.

Under certain conditions, patch state data my be unavailable for a given server. When this happens, specific messages display in the appropriate field detailing the reason. These include:

• Server does not support patch reporting (TPD<7.3.0)
• Server has never been refreshed
• Last server refresh was not successful

1. PAIR Server: Login using admusr credentials.
   SSH into the PAIR server and authenticate using admusr credentials.

   login as: admusr [Enter]
   admusr@10.75.152.79's password: <admusr_password> [Enter]
   Last login: Mon Jun  6 10:35:36 2016 from 10.75.7.157
   [admusr@myPairServer ~]$

2. PAIR Server: Display cached patch information.
   Execute the following command to display the latest cached patching information for a given server:

   Note:

   The output is for example only.

   [admusr@myPairServer ~]$ pair getStatus --address <target_address> [Enter]
   Report:  PAIR Server Patch Status
   
   Generated at: <UTC timestamp>
   Generated on: myPairServer
   Generated as: admusr
   --------------------------------------------
   
   Hostname: pmac-lab1
   Address: 10.240.72.40
   Product: TPD
   Version: 7.2.0.0.0_88.21.0
   Data retrieved on: 07/28/2016 17:09:39 UTC
   Warning: Last refresh attempt failed
   
   Patches:
   
       Name: somePatch
       Description: description of somePatch from its metadata
       Last patching activity: 06/23/2016 19:09:39 UTC
       RPMs: somePatch-0.0.1-0.noarch.rpm
       State: REJECTED
       
       Name: aPatch
       Description: description of aPatch from its metadata
       Last patching activity: 07/25/2016 14:47:48 UTC
       RPMs: aPatch-0.0.1-0.noarch.rpm
       State: REJECTED
   
       Name: myPatch
       Description: description of myPatch from its metadata
       Last patching activity: 07/25/2016 15:13:16 UTC
       RPMs: myPatch-0.0.1-0.noarch.rpm
       State: PENDING
   
   --------------------------------------------
   Report complete.
   
   [admusr@myPairServer ~]$

   Check the output of this command for any notes, warnings, or errors. A successful query displays the message Report complete.