Description of problem:
Using different identifiers, namely peerinfo->identifier and conn->id for 'clients' when logging the connection accept event and disconnect event respectively, makes it nearly impossible to find the correspondence between the identifiers and the actual machine.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Create volume of any type.
2. Start the volume and mount it.
3. Kill the mount process or bring the interface down in the client machine
(Assuming client and (at least one) brick reside on different machines).
4. Observe the log messages involving "accept" and "disconnect".

In the steps described above, there is atmost one client and the correspondence between the different identifiers and the actual machine involved is obvious. When there are more than one client (mount process) involved, it becomes difficult.
  
Actual results:


Expected results:


Additional info: