Note: See the chapter Asymmetric Routing in the Operational Related Issues section for the full explanation of the asymmetric routing feature.
The file asymrouting_table contains the current status of the asymmetric routing table:
Figure 6.81. Contents of the file "asymrouting_table"
10.20.53.121 10.21.1.201 SYN-rexmit 0 1344925735 1344925735 10.20.53.121 10.21.1.220 SYN-rexmit 4 1344925739 1344925739 10.8.6.20 10.8.32.54 bad-RST 54125 1344893467 1344900082 10.8.6.20 10.4.89.95 bad-RST 82927 1344922268 1344922277 10.8.6.20 10.12.64.20 bad-RST 54124 1344893466 1344922283 10.4.199.87 10.20.53.121 invalid-SYNACK 86170 1344925510 1344925510 10.20.53.121 10.21.1.212 SYN-rexmit 2 1344925737 1344925737 10.8.6.20 10.8.44.104 bad-RST 54124 1344893467 1344900082 10.20.53.121 10.21.1.200 SYN-rexmit 0 1344925735 1344925735
The format of the fields is:
IP address client
IP address server
Asymmetric routing reason
Timeout in seconds
Date and time created, seconds since 1 January 1970
Date and time last used, seconds since 1 January 1970
So for the line
10.8.6.20 10.4.89.95 bad-RST 82927 1344922268 1344922277
,
the timeout was most likely 86400 seconds (one day), the time it
was created was on 14 August 2012 at 05:31:08 and the last time a
new TCP session got passed-through was nine seconds later on 05:31:17.