L2SWITCH-72 & L2SWITCH-73 deals with resolution of host expiry features and make sure that hosts are seen again if the there is any new traffic generated among hosts.

We need tests in csit/integration which validates the host_expiry feature implementation.

Possible configuration values that may be handy while writing test cases:-

<timestamp-update-interval> at l2switch / addresstracker/config/src/main/resources/initial/56-addresstracker.xml

<is-proactive-flood-mode> at l2switch / arphandler/config/src/main/resources/initial/54-arphandler.xml

<host-purge-interval> & <host-purge-age> at l2switch / hosttracker/config/src/main/resources/initial/57-hosttracker.xml

<reactive-flow-idle-timeout> & <reactive-flow-hard-timeout> at l2switch/l2switch-main/config/src/main/resources/initial/58-l2switchmain.xml

sample values are as follows:-
<timestamp-update-interval> - 600000 (in miiliseconds corresponds to 600 seconds)
<is-proactive-flood-mode> - true or false (should work in both modes)
<host-purge-interval> - 60 (time interval at which hosts are checked for expiry)
<host-purge-age> - 600 (hosts will expire after 600 seconds)
<reactive-flow-idle-timeout> - 600
<reactive-flow-hard-timeout> - 600 (the flows pushed should expire so that arp is sent to controller so as to make expired hosts come back)