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.575 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.575/0.575/0.575/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 50732 connected to 10.0.0.1 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 2.99 MBytes 25.1 Mbits/sec 274 17.0 KBytes [ 5] 1.00-2.00 sec 891 KBytes 7.30 Mbits/sec 130 18.4 KBytes [ 5] 2.00-3.00 sec 1.30 MBytes 11.0 Mbits/sec 145 15.6 KBytes [ 5] 3.00-4.00 sec 1.12 MBytes 9.38 Mbits/sec 124 15.6 KBytes [ 5] 4.00-5.00 sec 1.30 MBytes 10.9 Mbits/sec 150 14.1 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 7.59 MBytes 12.7 Mbits/sec 823 sender [ 5] 0.00-5.00 sec 7.02 MBytes 11.8 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 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.533 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.533/0.533/0.533/0.000 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=136 packets=1 bytes=84 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=136 packets=1 bytes=84 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 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.405 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.405/0.405/0.405/0.000 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=137 packets=1 bytes=84 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=137 packets=1 bytes=84 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 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.513 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.513/0.513/0.513/0.000 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=138 packets=1 bytes=84 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=138 packets=1 bytes=84 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 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.369 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.369/0.369/0.369/0.000 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=139 packets=1 bytes=84 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=139 packets=1 bytes=84 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 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.310 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.310/0.310/0.310/0.000 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=50500 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=50500 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=140 vrf=RED packets=1 bytes=84 src=10.0.0.1 dst=10.0.0.2 type=0 code=0 id=140 vrf=RED packets=1 bytes=84 mark=0 use=1 udp 17 29 src=127.0.0.1 dst=127.0.0.1 sport=53895 dport=53 packets=1 bytes=62 [UNREPLIED] src=127.0.0.1 dst=127.0.0.1 sport=53 dport=53895 packets=0 bytes=0 mark=0 use=1 conntrack v1.4.5 (conntrack-tools): 3 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.332 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.332/0.332/0.332/0.000 ms
Step 4: Run command system journal show | tail
at DUT0
and check if output contains the following tokens:
[DEBUG--1]IN=eth0Show output
Apr 23 17:29:13.564231 osdx OSDxCLI[12455]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.0.0.1/24'. Apr 23 17:29:13.663781 osdx OSDxCLI[12455]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 traffic policy in POLICY'. Apr 23 17:29:13.716420 osdx OSDxCLI[12455]: User 'admin' added a new cfg line: 'set traffic policy POLICY rule 1 log prefix "DEBUG-"'. Apr 23 17:29:13.810955 osdx OSDxCLI[12455]: User 'admin' added a new cfg line: 'set traffic policy POLICY rule 1 log level err'. Apr 23 17:29:13.875018 osdx zebra[1124]: [RZ3YY-GPH41][EC 100663310] snmp[warning]: Warning: Failed to connect to the agentx master agent ([NIL]): Apr 23 17:29:13.898429 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Apr 23 17:29:13.947141 osdx cfgd[1182]: [12455]Completed change to active configuration Apr 23 17:29:13.952955 osdx OSDxCLI[12455]: User 'admin' committed the configuration. Apr 23 17:29:13.970112 osdx OSDxCLI[12455]: User 'admin' left the configuration menu. Apr 23 17:29:14.500069 osdx kernel: [DEBUG--1]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=10271 DF PROTO=ICMP TYPE=8 CODE=0 ID=141 SEQ=1