Conntrack

Test suite to validate conntrack-related operations

Test commit keep-contracks command

Description

Test to validate commit keep-conntracks command

Scenario

Step 1: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.0.0.2/24
set protocols static route 0.0.0.0/0 next-hop 10.0.0.1
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.0.0.1/24
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping the IP address 10.0.0.1 from DUT1:

admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1

Step 4: Initiate a tcp connection from DUT1 to DUT0 and exchange messages between both endpoints

admin@DUT0$ monitor test connection server 4321 tcp local-interface eth0
admin@DUT1$ monitor test connection client 10.0.0.1 4321 tcp local-interface eth0 source-port 54361

Step 5: Run the command configure on DUT0 and expect no output.

Step 6: Run the command set system alarm TEST on DUT0 and expect no output.

Step 7: Run the command commit keep-conntracks on DUT0 and expect no output.

Step 8: Run the command system conntrack show on DUT0 and check whether the output does not contain the following tokens:

0 flow entries have been shown