Verify PI Data Archive collective communication with piconfig

If you cannot use Collective Manager, you can manually verify that Data Archive collective members are properly communicating. Use piconfig to check the values of CommStatus, SyncStatus, LastSyncRecordID, LastCommTime, and LastSyncTime in the PISERVER table. When collective members are properly communicating, these values are the same for all servers.

1. Open a command prompt window.

2. Navigate to the ..\PI\adm directory.

3. Enter: piconfig < pisysdump.dif

   The display shows configuration output. For example, for a primary Data Archive server, output looks similar to:

   Collective Configuration
   Name, CollectiveID, Description
   -----------------------------------------------------------------
   uc-s1,08675309-0007-0007-0007-000000001001,UC 2006 Demo Collective
   
   Member Server Configuration
   Name, IsCurrentServer, ServerID, Collective, Description, FQDN, Role
   -----------------------------------------------------------------
   uc-s1,1,08675309-0007-0007-0007-000000001001,uc-s1,UC 2006 Demo Server 1,uc-s1.osisoft.int,1
   uc-s2,0,08675309-0007-0007-0007-000000001002,uc-s1,UC 2006 Demo Server 2,uc-s2.osisoft.int,2
   
   Collective Status
   Name, Status
   -----------------------------------------------------------------
   uc-s1,0
   
   Member Server Status
   Name,IsAvailable,CommStatus,SyncStatus,LastSyncRecordID,LastCommTime,LastSyncTime,SyncFailReason,UnavailableReason
   -----------------------------------------------------------------
   uc-s1,1,0,0,468,6-Nov-06 17:17:18,25-Oct-06 17:33:42,,
   uc-s2,1,0,0,468,6-Nov-06 17:17:14,6-Nov-06 17:17:04,,
   

4. Examine the values of CommStatus, SyncStatus, LastSyncRecordID, LastCommTime, and LastSyncTime under Member Server Status.

   If the collective is communicating properly, then:

   • CommStatus and SyncStatus will be 0.

   • The value of LastSyncRecordID will match for all servers.

   • LastCommTime (the last time the secondary server shared its status with the primary server) will contain a relatively recent time stam.p

   • LastSyncTime (the last time the server synchronized with the primary server) will contain similar time stamps at all secondary servers.