Please Refer to the post:
Page 15 from the above Doc
- Setup arsystem.response.hostip=true in Mid-Tier config.properties and restart Mid-Tier. This setting prints the Mid-Tier Host IP Address as the ARRESPONSEHOSTIP header in the HTTP Servlet Response. This can be used along with Fiddler for examining the HTTP Response Headers and for making sure that all Requests for a User Session are directed to the same Host IP Address. If all Requests for a User Session are not directed to the same Host IP Address, there can be a problem with Load Balancer settings."
tTis will help from the client machine/browser using fiddler logs- a given request is redirected to which Mid-tier.
Alternatively the logging can also be enabled at the Load Balancer level to know where the requests are getting re-directed too. ( The networking team that setup Load Balancer should help out with the LB logs)
For knowing the which midtier the user is connected to, we slightly modified the midtier login html page to add a hardcoded server name in it. The only down side with this is anytime you redploy midtier you need to redo these changes. And to to know the which arserver the midtier connected to, usually before 7.6.04 once the midtier connected to a arserver it will always connected to the same arserver untill the midtier or arserver is restarted.
So we usually check the user logs in each arserver to verify which midtier is connected to which arserver.
But with 7.6.04 it would be tricky becasue there is no need to maintain a session affinity between midtier and arserver. So these connections can be different from user to user.