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 address 10.0.0.1/24 set interfaces ethernet eth0 traffic policy in POLICY set traffic policy POLICY rule 1 action accept
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.0.0.2/24
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.698 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.698/0.698/0.698/0.000 ms
Step 4: Set the following configuration in DUT0
:
del traffic policy POLICY set traffic policy POLICY 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: Set the following configuration in DUT0
:
del traffic policy POLICY set traffic policy POLICY 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 5001Expect this output in
DUT1
:Connecting to host 10.0.0.1, port 5001 [ 5] local 10.0.0.2 port 55214 connected to 10.0.0.1 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 3.09 MBytes 25.9 Mbits/sec 302 15.6 KBytes [ 5] 1.00-2.00 sec 1.06 MBytes 8.86 Mbits/sec 140 17.0 KBytes [ 5] 2.00-3.00 sec 1.24 MBytes 10.4 Mbits/sec 153 17.0 KBytes [ 5] 3.00-4.00 sec 954 KBytes 7.82 Mbits/sec 137 18.4 KBytes [ 5] 4.00-5.00 sec 1.06 MBytes 8.86 Mbits/sec 132 14.1 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 7.37 MBytes 12.4 Mbits/sec 864 sender [ 5] 0.00-5.00 sec 6.82 MBytes 11.4 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 address 10.0.0.1/24 set interfaces ethernet eth0 traffic policy in POLICY set traffic policy POLICY rule 1 copy tos connmark
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.0.0.2/24
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.512 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=1.01 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.846 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.626 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.575 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 15ms rtt min/avg/max/mdev = 0.512/0.713/1.009/0.187 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=122 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=122 packets=5 bytes=420 mark=12 use=1 conntrack v1.4.5 (conntrack-tools): 1 flow entries have been shown.
Step 5: Set the following configuration in DUT0
:
del traffic policy POLICY set traffic policy POLICY 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.438 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.536 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.488 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.497 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.464 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 91ms rtt min/avg/max/mdev = 0.438/0.484/0.536/0.040 ms
Step 7: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
emark1=12Show output
icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=123 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=123 packets=5 bytes=420 mark=0 emark1=12 use=1 conntrack v1.4.5 (conntrack-tools): 1 flow entries have been shown.
Test Policy Set
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 address 10.0.0.1/24 set interfaces ethernet eth0 traffic policy in POLICY set traffic policy POLICY rule 1 set connmark 15
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.0.0.2/24
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.315 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.891 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.871 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.816 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.862 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 15ms rtt min/avg/max/mdev = 0.315/0.751/0.891/0.219 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=124 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=124 packets=5 bytes=420 mark=15 use=1 conntrack v1.4.5 (conntrack-tools): 1 flow entries have been shown.
Step 5: Set the following configuration in DUT0
:
del traffic policy POLICY set traffic policy POLICY 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.477 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.940 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.936 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.849 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.585 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 38ms rtt min/avg/max/mdev = 0.477/0.757/0.940/0.192 ms
Step 7: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
appdetect[U:80]Show output
icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=125 packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=125 packets=5 bytes=420 mark=0 use=1 appdetect[U:80] conntrack v1.4.5 (conntrack-tools): 1 flow entries have been shown.
Step 8: Set the following configuration in DUT0
:
del traffic policy POLICY set traffic policy POLICY rule 1 set vrf RED set system vrf RED set interfaces ethernet eth0 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.654 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.784 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=0.989 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=0.898 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=0.481 ms --- 10.0.0.1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 10ms rtt min/avg/max/mdev = 0.481/0.761/0.989/0.180 ms
Step 10: Run command system conntrack show
at DUT0
and check if output contains the following tokens:
vrf=REDShow output
icmp 1 29 src=10.0.0.2 dst=10.0.0.1 type=8 code=0 id=126 vrf=RED packets=5 bytes=420 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=126 vrf=RED packets=5 bytes=420 mark=0 use=1 conntrack v1.4.5 (conntrack-tools): 1 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 address 10.0.0.1/24 set interfaces ethernet eth0 traffic policy in POLICY set traffic policy POLICY rule 1 log prefix "DEBUG-" set traffic policy POLICY rule 1 log level err
Step 2: Set the following configuration in DUT1
:
set interfaces ethernet eth0 address 10.0.0.2/24
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.969 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.969/0.969/0.969/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
Oct 09 07:37:47.180784 osdx OSDxCLI[8590]: User 'admin' entered the configuration menu. Oct 09 07:37:47.243767 osdx OSDxCLI[8590]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.0.0.1/24'. Oct 09 07:37:47.332910 osdx OSDxCLI[8590]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 traffic policy in POLICY'. Oct 09 07:37:47.387465 osdx OSDxCLI[8590]: User 'admin' added a new cfg line: 'set traffic policy POLICY rule 1 log prefix "DEBUG-"'. Oct 09 07:37:47.485145 osdx OSDxCLI[8590]: User 'admin' added a new cfg line: 'set traffic policy POLICY rule 1 log level err'. Oct 09 07:37:47.574344 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Oct 09 07:37:47.703330 osdx cfgd[1327]: [8590]Completed change to active configuration Oct 09 07:37:47.706047 osdx OSDxCLI[8590]: User 'admin' committed the configuration. Oct 09 07:37:47.723971 osdx OSDxCLI[8590]: User 'admin' left the configuration menu. Oct 09 07:37:48.221541 osdx kernel: [DEBUG--1] ACCEPT IN=eth0 OUT= MAC=de:ad:be:ef:6c:10:de:ad:be:ef:6c:20:08:00 SRC=10.0.0.2 DST=10.0.0.1 LEN=84 TOS=0x00 PREC=0x00 TTL=64 ID=7763 DF PROTO=ICMP TYPE=8 CODE=0 ID=127 SEQ=1