Policy
The following scenarios show how to configure different
traffic policies
. Policies can be used to manage and
classify network packets. traffic selectors
can be
configured to filter packets based on certain fields.
Test Policy Actions
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). Different traffic actions are
configured to accept, drop or limit incoming traffic.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 action accept set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.258 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms
Step 4: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 action accept set traffic policy POLICY_IN rule 1 action drop
Step 5: Expect a failure in the following command:
Initiate a udp connection from DUT1
to DUT0
and try to send some messages between both endpoints
admin@DUT0$ monitor test connection server 8080 udp admin@DUT1$ monitor test connection client 10.0.0.1 8080 udp
Step 6: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 action drop set traffic policy POLICY_IN rule 1 action rate-limit 10
Step 7: Initiate a bandwidth test from DUT1
to DUT0
admin@DUT0$ monitor test performance server port 5001 admin@DUT1$ monitor test performance client 10.0.0.1 duration 5 port 5001 parallel 1Expect this output in
DUT1
:Connecting to host 10.0.0.1, port 5001 [ 5] local 10.0.0.2 port 34762 connected to 10.0.0.1 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 5.50 MBytes 46.1 Mbits/sec 634 5.66 KBytes [ 5] 1.00-2.00 sec 1.25 MBytes 10.5 Mbits/sec 99 1.41 KBytes [ 5] 2.00-3.00 sec 1.25 MBytes 10.5 Mbits/sec 128 8.48 KBytes [ 5] 3.00-4.00 sec 1.25 MBytes 10.5 Mbits/sec 134 33.9 KBytes [ 5] 4.00-5.00 sec 1.25 MBytes 10.5 Mbits/sec 115 5.66 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 10.5 MBytes 17.6 Mbits/sec 1110 sender [ 5] 0.00-5.00 sec 6.90 MBytes 11.6 Mbits/sec receiver iperf Done.
Note
Previous test should show a very low bandwidth rate.
Test Policy Copy
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). Different copy
actions are
configured to store the ToS value in the conntrack mark
and extra conntrack mark
fields.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 copy tos connmark set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 tos 12 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.233 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.229 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.306 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.246 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.255 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4094ms rtt min/avg/max/mdev = 0.229/0.253/0.306/0.027 ms
Step 4: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
mark=12Show output
icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=403 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=403 packets=5 bytes=420 mark=12 use=1 conntrack v1.4.7 (conntrack-tools): 1 flow entries have been shown.
Step 5: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 copy tos connmark set traffic policy POLICY_IN rule 1 copy tos extra-connmark 1
Step 6: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 tos 12 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.212 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.256 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.238 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.237 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.230 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4087ms rtt min/avg/max/mdev = 0.212/0.234/0.256/0.014 ms
Step 7: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
emark1=12Show output
udp 17 26 src=127.0.0.1 dst=127.0.0.1 sport=48994 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=48994 packets=0 bytes=0 mark=0 use=1 udp 17 29 src=127.0.0.1 dst=127.0.0.1 sport=57961 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=57961 packets=0 bytes=0 mark=0 use=1 udp 17 26 src=127.0.0.1 dst=127.0.0.1 sport=49468 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=49468 packets=0 bytes=0 mark=0 use=1 udp 17 29 src=127.0.0.1 dst=127.0.0.1 sport=37559 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=37559 packets=0 bytes=0 mark=0 use=1 udp 17 28 src=127.0.0.1 dst=127.0.0.1 sport=52988 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=52988 packets=0 bytes=0 mark=0 use=1 udp 17 28 src=127.0.0.1 dst=127.0.0.1 sport=48071 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=48071 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=404 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=404 packets=5 bytes=420 mark=0 emark1=12 use=1 conntrack v1.4.7 (conntrack-tools): 7 flow entries have been shown.
Test Policy Set
Description
In this scenario, an egress traffic policy
is configured
in DUT0 (‘eth0’ interface) to mark outgoing packets
using ToS and CoS fields.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN set traffic policy POLICY_OUT rule 1 set tos 12
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Run command traffic dump monitor detail interface eth0 filter "host 10.0.0.2"
at DUT1
.
Step 4: Ping IP address 10.0.0.2
from DUT0
:
admin@DUT0$ ping 10.0.0.2 count 1 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.280 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.280/0.280/0.280/0.000 ms
Step 5: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_OUT rule 1 set tos set traffic policy POLICY_OUT rule 1 set cos 5
Step 6: Run command traffic dump monitor detail interface eth0 filter "host 10.0.0.2"
at DUT1
.
Step 7: Ping IP address 10.0.0.2
from DUT0
:
admin@DUT0$ ping 10.0.0.2 count 1 size 56 timeout 1Show output
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=0.246 ms --- 10.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.246/0.246/0.246/0.000 ms
Test Policy Set Conntrack Values
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). Different set
actions are
configured to change the conntrack mark, the app-id and the
VRF.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 set connmark 15 set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.331 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.464 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.210 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.249 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.477 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4048ms rtt min/avg/max/mdev = 0.210/0.346/0.477/0.108 ms
Step 4: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
mark=15Show output
icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=405 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=405 packets=5 bytes=420 mark=15 use=1 conntrack v1.4.7 (conntrack-tools): 1 flow entries have been shown.
Step 5: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 set connmark set traffic policy POLICY_IN rule 1 set app-id custom 80
Step 6: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.239 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.228 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.249 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.236 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.231 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4090ms rtt min/avg/max/mdev = 0.228/0.236/0.249/0.007 ms
Step 7: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
appdetect[U:80]Show output
udp 17 28 src=127.0.0.1 dst=127.0.0.1 sport=50546 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=50546 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=406 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=406 packets=5 bytes=420 mark=0 use=1 appdetect[U:80] udp 17 28 src=127.0.0.1 dst=127.0.0.1 sport=53330 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=53330 packets=0 bytes=0 mark=0 use=1 conntrack v1.4.7 (conntrack-tools): 3 flow entries have been shown.
Step 8: Modify the following configuration lines in DUT0
:
delete traffic policy POLICY_IN rule 1 set app-id set interfaces ethernet eth0 vif 100 vrf RED set system vrf RED set traffic policy POLICY_IN rule 1 set vrf RED
Step 9: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 5 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.305 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.247 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.229 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.223 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.221 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4080ms rtt min/avg/max/mdev = 0.221/0.245/0.305/0.031 ms
Step 10: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
vrf=REDShow output
udp 17 29 src=127.0.0.1 dst=127.0.0.1 sport=58328 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=58328 packets=0 bytes=0 mark=0 use=1 udp 17 25 src=127.0.0.1 dst=127.0.0.1 sport=36634 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=36634 packets=0 bytes=0 mark=0 use=1 udp 17 26 src=127.0.0.1 dst=127.0.0.1 sport=52566 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=52566 packets=0 bytes=0 mark=0 use=1 udp 17 25 src=127.0.0.1 dst=127.0.0.1 sport=50605 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=50605 packets=0 bytes=0 mark=0 use=1 udp 17 29 src=127.0.0.1 dst=127.0.0.1 sport=58787 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=58787 packets=0 bytes=0 mark=0 use=1 udp 17 26 src=127.0.0.1 dst=127.0.0.1 sport=47015 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=47015 packets=0 bytes=0 mark=0 use=1 icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=407 vrf=RED packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=407 vrf=RED packets=5 bytes=420 mark=0 use=1 conntrack v1.4.7 (conntrack-tools): 7 flow entries have been shown.
Test Policy Log
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). The log
option is configured to
show system messages that help debug and analyze the
network status.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 log level err set traffic policy POLICY_IN rule 1 log prefix DEBUG- set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.317 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.317/0.317/0.317/0.000 ms
Step 4: Run command system journal show | tail
at DUT0
and check if output contains the following tokens:
[DEBUG--1] ACCEPT IN=eth0Show output
Dec 03 16:30:32.482533 osdx OSDxCLI[367824]: User 'admin' added a new cfg line: 'set traffic policy POLICY_OUT'. Dec 03 16:30:32.581687 osdx OSDxCLI[367824]: User 'admin' added a new cfg line: 'set traffic policy POLICY_IN rule 1 log prefix DEBUG-'. Dec 03 16:30:32.635233 osdx OSDxCLI[367824]: User 'admin' added a new cfg line: 'set traffic policy POLICY_IN rule 1 log level err'. Dec 03 16:30:32.761863 osdx OSDxCLI[367824]: User 'admin' added a new cfg line: 'show working'. Dec 03 16:30:32.883925 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Dec 03 16:30:32.908768 osdx (udev-worker)[464515]: Network interface NamePolicy= disabled on kernel command line. Dec 03 16:30:33.130645 osdx cfgd[1634]: [367824]Completed change to active configuration Dec 03 16:30:33.166191 osdx OSDxCLI[367824]: User 'admin' committed the configuration. Dec 03 16:30:33.182435 osdx OSDxCLI[367824]: User 'admin' left the configuration menu. Dec 03 16:30:33.875925 osdx kernel: [DEBUG--1] ACCEPT IN=eth0.100 OUT= MAC=de:ad:be:ef:6c:00:de:ad:be:ef:6c:10:08:00:45:00:00:54 SRC=10.0.0.2 DST=10.0.0.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=48008 DF PROTO=ICMP TYPE=8 CODE=0 ID=408 SEQ=1
Test Policy Advisor
Description
In this scenario, an ingress traffic policy
is configured
in DUT0 (‘eth0’ interface). The advisor
option is
configured to enable/disable the rule depending on
the advisor status. If the rule is enabled, incoming traffic
will be dropped.
Scenario
Step 1: Set the following configuration in DUT0
:
set interfaces ethernet eth0 vif 100 address 10.0.0.1/24 set interfaces ethernet eth0 vif 100 traffic policy in POLICY_IN set interfaces ethernet eth0 vif 100 traffic policy out POLICY_OUT set system advisor ADV test false set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy POLICY_IN rule 1 action drop set traffic policy POLICY_IN rule 1 advisor ADV set traffic policy POLICY_OUT
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 vif 100 address 10.0.0.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.355 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.355/0.355/0.355/0.000 ms
Step 4: Modify the following configuration lines in DUT0
:
set system advisor ADV test true
Step 5: Expect a failure in the following command:
Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. --- 10.0.0.1 ping statistics --- 1 packets transmitted, 0 received, 100% packet loss, time 0ms
Step 6: Modify the following configuration lines in DUT0
:
set system advisor ADV test false
Step 7: Ping IP address 10.0.0.1
from DUT1
:
admin@DUT1$ ping 10.0.0.1 count 1 size 56 timeout 1Show output
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.220 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.220/0.220/0.220/0.000 ms