Tc Snmp Monitor
These scenarios show how to configure a traffic control discipline in different interfaces to monitor its statistics using SNMP protocol.
Test Traffic Control OIDs On Ethernet Interface
Description
In this scenario, traffic control disciplines are attached to an Ethernet interface.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 192.168.100.1/24 set interfaces ethernet eth0 traffic control in NETEM set interfaces ethernet eth0 traffic control out WFQ set service snmp community COMMUNITY2TEST set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic control NETEM type network-emulator packet-loss 0.5 set traffic control WFQ type wfq bandwidth 100 set traffic control WFQ type wfq class 1 weight 10 set traffic control WFQ type wfq class 2 weight 10 set traffic control WFQ type wfq default-class 2 set traffic control WFQ type wfq match 1 class 1 set traffic control WFQ type wfq match 1 ip protocol tcp set traffic control WFQ type wfq match 1 ip source port 1234
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 192.168.100.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping the IP address 192.168.100.1 from DUT1:
admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.899 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.899/0.899/0.899/0.000 ms
Step 4: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 1234 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 47090 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 101 MBytes 845 Mbits/sec 374 29.7 KBytes [ 5] 1.00-2.00 sec 134 MBytes 1.12 Gbits/sec 513 36.8 KBytes [ 5] 2.00-3.00 sec 141 MBytes 1.18 Gbits/sec 487 18.4 KBytes [ 5] 3.00-4.00 sec 113 MBytes 951 Mbits/sec 420 48.1 KBytes [ 5] 4.00-5.00 sec 135 MBytes 1.13 Gbits/sec 474 25.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 624 MBytes 1.05 Gbits/sec 2268 sender [ 5] 0.00-5.00 sec 623 MBytes 1.05 Gbits/sec receiver iperf Done.
Step 5: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 4321 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 36314 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 158 MBytes 1.33 Gbits/sec 601 21.2 KBytes [ 5] 1.00-2.00 sec 123 MBytes 1.03 Gbits/sec 443 31.1 KBytes [ 5] 2.00-3.00 sec 116 MBytes 973 Mbits/sec 420 25.5 KBytes [ 5] 3.00-4.00 sec 102 MBytes 854 Mbits/sec 353 33.9 KBytes [ 5] 4.00-5.00 sec 97.7 MBytes 819 Mbits/sec 350 35.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 597 MBytes 1.00 Gbits/sec 2167 sender [ 5] 0.00-5.00 sec 595 MBytes 998 Mbits/sec receiver iperf Done.
Step 6: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 1234 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 47270 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.0 MBytes 118 Mbits/sec 154 116 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 98.0 Mbits/sec 103 70.7 KBytes [ 5] 2.00-3.00 sec 11.1 MBytes 93.3 Mbits/sec 67 79.2 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.0 Mbits/sec 70 69.3 KBytes [ 5] 4.00-5.00 sec 11.1 MBytes 93.3 Mbits/sec 71 77.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.7 MBytes 100 Mbits/sec 465 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 38132 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.7 MBytes 115 Mbits/sec 138 86.3 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 66 93.3 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 66 94.7 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 66 91.9 KBytes [ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec 58 83.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.3 MBytes 99.5 Mbits/sec 394 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0 OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassDrops\.[^=]+\.1 = INTEGER: \d+ OutClassDrops\.[^=]+\.2 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+ OutPps\.[^=]+ = INTEGER: [1-9]\d*Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPackets."eth0" = INTEGER: 203000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutPps."eth0" = INTEGER: 7914 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBytes."eth0" = INTEGER: 136284439 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutDrops."eth0" = INTEGER: 33 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutKind."eth0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutBps."eth0" = INTEGER: 9163602 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutOverlimits."eth0" = INTEGER: 7423 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutRate."eth0" = INTEGER: 100000000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassTag."eth0".1 = INTEGER: 1 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassTag."eth0".2 = INTEGER: 2 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".1 = INTEGER: 59747 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassPackets."eth0".2 = INTEGER: 143253 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".1 = INTEGER: 4031972 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassBytes."eth0".2 = INTEGER: 132252467 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassDrops."eth0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassDrops."eth0".2 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlOutClassOverlimits."eth0".2 = INTEGER: 3907 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPackets."eth0" = INTEGER: 890720 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInPps."eth0" = INTEGER: 15202 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBytes."eth0" = INTEGER: 1336674103 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInDrops."eth0" = INTEGER: 4462 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInKind."eth0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInBps."eth0" = INTEGER: 22224377 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInOverlimits."eth0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetTrafficControlInRate."eth0" = INTEGER: 0
Test Traffic Control OIDs On Ethernet VIF-S Interface
Description
In this scenario, traffic control disciplines are attached to a VLAN-aware Ethernet interface.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 vif 100 address 192.168.100.1/24 set interfaces ethernet eth0 vif 100 traffic control in NETEM set interfaces ethernet eth0 vif 100 traffic control out WFQ set service snmp community COMMUNITY2TEST set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic control NETEM type network-emulator packet-loss 0.5 set traffic control WFQ type wfq bandwidth 100 set traffic control WFQ type wfq class 1 weight 10 set traffic control WFQ type wfq class 2 weight 10 set traffic control WFQ type wfq default-class 2 set traffic control WFQ type wfq match 1 class 1 set traffic control WFQ type wfq match 1 ip protocol tcp set traffic control WFQ type wfq match 1 ip source port 1234
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 vif 100 address 192.168.100.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping the IP address 192.168.100.1 from DUT1:
admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.740 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.740/0.740/0.740/0.000 ms
Step 4: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 1234 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 36136 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 162 MBytes 1.36 Gbits/sec 627 28.3 KBytes [ 5] 1.00-2.00 sec 113 MBytes 944 Mbits/sec 413 35.4 KBytes [ 5] 2.00-3.00 sec 129 MBytes 1.08 Gbits/sec 481 45.2 KBytes [ 5] 3.00-4.00 sec 139 MBytes 1.16 Gbits/sec 519 36.8 KBytes [ 5] 4.00-5.00 sec 125 MBytes 1.05 Gbits/sec 441 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 667 MBytes 1.12 Gbits/sec 2481 sender [ 5] 0.00-5.00 sec 666 MBytes 1.12 Gbits/sec receiver iperf Done.
Step 5: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 4321 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 38682 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 126 MBytes 1.06 Gbits/sec 451 26.9 KBytes [ 5] 1.00-2.00 sec 95.8 MBytes 804 Mbits/sec 372 29.7 KBytes [ 5] 2.00-3.00 sec 140 MBytes 1.17 Gbits/sec 513 53.7 KBytes [ 5] 3.00-4.00 sec 142 MBytes 1.19 Gbits/sec 501 21.2 KBytes [ 5] 4.00-5.00 sec 146 MBytes 1.22 Gbits/sec 520 25.5 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 649 MBytes 1.09 Gbits/sec 2357 sender [ 5] 0.00-5.00 sec 649 MBytes 1.09 Gbits/sec receiver iperf Done.
Step 6: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 1234 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 42592 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.3 MBytes 120 Mbits/sec 176 90.5 KBytes [ 5] 1.00-2.00 sec 11.1 MBytes 92.8 Mbits/sec 70 90.5 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.5 Mbits/sec 66 94.7 KBytes [ 5] 3.00-4.00 sec 11.1 MBytes 93.3 Mbits/sec 58 97.6 KBytes [ 5] 4.00-5.00 sec 11.9 MBytes 99.6 Mbits/sec 93 69.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.9 MBytes 101 Mbits/sec 463 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 54490 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.4 MBytes 121 Mbits/sec 171 91.9 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.4 Mbits/sec 88 67.9 KBytes [ 5] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec 28 110 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 94.4 Mbits/sec 87 80.6 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 80 80.6 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.9 Mbits/sec 454 sender [ 5] 0.00-5.00 sec 58.5 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0 OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassDrops\.[^=]+\.1 = INTEGER: \d+ OutClassDrops\.[^=]+\.2 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+ OutPps\.[^=]+ = INTEGER: [1-9]\d*Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPackets."eth0"."100" = INTEGER: 209658 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutPps."eth0"."100" = INTEGER: 8127 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBytes."eth0"."100" = INTEGER: 136750089 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutDrops."eth0"."100" = INTEGER: 34 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutKind."eth0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutBps."eth0"."100" = INTEGER: 9237390 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutOverlimits."eth0"."100" = INTEGER: 7405 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutRate."eth0"."100" = INTEGER: 100000000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassTag."eth0"."100".1 = INTEGER: 1 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassTag."eth0"."100".2 = INTEGER: 2 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".1 = INTEGER: 64652 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassPackets."eth0"."100".2 = INTEGER: 145006 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".1 = INTEGER: 4365894 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassBytes."eth0"."100".2 = INTEGER: 132384195 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassDrops."eth0"."100".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassDrops."eth0"."100".2 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlOutClassOverlimits."eth0"."100".2 = INTEGER: 3902 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPackets."eth0"."100" = INTEGER: 960473 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInPps."eth0"."100" = INTEGER: 16933 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBytes."eth0"."100" = INTEGER: 1442170067 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInDrops."eth0"."100" = INTEGER: 4881 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInKind."eth0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInBps."eth0"."100" = INTEGER: 24830551 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInOverlimits."eth0"."100" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesEthernetVifTrafficControlInRate."eth0"."100" = INTEGER: 0
Test Traffic Control OIDs On Bridge Interface
Description
In this scenario, traffic control disciplines are attached to a Bridge interface.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces bridge br0 address 192.168.100.1/24 set interfaces bridge br0 traffic control in NETEM set interfaces bridge br0 traffic control out WFQ set interfaces ethernet eth0 bridge-group bridge br0 set service snmp community COMMUNITY2TEST set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic control NETEM type network-emulator packet-loss 0.5 set traffic control WFQ type wfq bandwidth 100 set traffic control WFQ type wfq class 1 weight 10 set traffic control WFQ type wfq class 2 weight 10 set traffic control WFQ type wfq default-class 2 set traffic control WFQ type wfq match 1 class 1 set traffic control WFQ type wfq match 1 ip protocol tcp set traffic control WFQ type wfq match 1 ip source port 1234
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 192.168.100.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping the IP address 192.168.100.1 from DUT1:
admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.475 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.475/0.475/0.475/0.000 ms
Step 4: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 1234 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 35908 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.01 sec 144 MBytes 1.20 Gbits/sec 512 35.4 KBytes [ 5] 1.01-2.00 sec 95.9 MBytes 812 Mbits/sec 347 18.4 KBytes [ 5] 2.00-3.00 sec 103 MBytes 867 Mbits/sec 372 41.0 KBytes [ 5] 3.00-4.00 sec 143 MBytes 1.20 Gbits/sec 505 67.9 KBytes [ 5] 4.00-5.00 sec 150 MBytes 1.26 Gbits/sec 515 58.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 636 MBytes 1.07 Gbits/sec 2251 sender [ 5] 0.00-5.00 sec 636 MBytes 1.07 Gbits/sec receiver iperf Done.
Step 5: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 4321 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 56194 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.01 sec 92.7 MBytes 773 Mbits/sec 338 35.4 KBytes [ 5] 1.01-2.00 sec 81.2 MBytes 685 Mbits/sec 317 25.5 KBytes [ 5] 2.00-3.00 sec 80.8 MBytes 679 Mbits/sec 289 24.0 KBytes [ 5] 3.00-4.00 sec 75.5 MBytes 633 Mbits/sec 305 17.0 KBytes [ 5] 4.00-5.00 sec 71.4 MBytes 600 Mbits/sec 277 11.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 402 MBytes 674 Mbits/sec 1526 sender [ 5] 0.00-5.00 sec 401 MBytes 673 Mbits/sec receiver iperf Done.
Step 6: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 1234 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 55070 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 156 73.5 KBytes [ 5] 1.00-2.00 sec 11.0 MBytes 92.3 Mbits/sec 68 83.4 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 73 82.0 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 72 82.0 KBytes [ 5] 4.00-5.00 sec 11.6 MBytes 97.0 Mbits/sec 60 69.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.7 MBytes 100 Mbits/sec 429 sender [ 5] 0.00-5.01 sec 58.4 MBytes 97.8 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 46130 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.3 MBytes 120 Mbits/sec 193 56.6 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 48 99.0 KBytes [ 5] 2.00-3.00 sec 11.2 MBytes 93.8 Mbits/sec 121 69.3 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.5 Mbits/sec 68 66.5 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 42 84.8 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 100 Mbits/sec 472 sender [ 5] 0.00-5.01 sec 58.5 MBytes 97.9 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0 OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassDrops\.[^=]+\.1 = INTEGER: \d+ OutClassDrops\.[^=]+\.2 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+ OutPps\.[^=]+ = INTEGER: [1-9]\d*Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPackets."br0" = INTEGER: 181274 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutPps."br0" = INTEGER: 7484 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBytes."br0" = INTEGER: 134845752 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutDrops."br0" = INTEGER: 34 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutKind."br0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutBps."br0" = INTEGER: 9163510 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutOverlimits."br0" = INTEGER: 7850 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutRate."br0" = INTEGER: 100000000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassTag."br0".1 = INTEGER: 1 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassTag."br0".2 = INTEGER: 2 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".1 = INTEGER: 62003 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassPackets."br0".2 = INTEGER: 119271 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".1 = INTEGER: 4178451 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassBytes."br0".2 = INTEGER: 130667301 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassDrops."br0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassDrops."br0".2 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlOutClassOverlimits."br0".2 = INTEGER: 4136 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPackets."br0" = INTEGER: 758854 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInPps."br0" = INTEGER: 12344 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBytes."br0" = INTEGER: 1137026119 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInDrops."br0" = INTEGER: 3820 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInKind."br0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInBps."br0" = INTEGER: 17895399 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInOverlimits."br0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeTrafficControlInRate."br0" = INTEGER: 0
Test Traffic Control OIDs On Bridge VIF-S Interface
Description
In this scenario, traffic control disciplines are attached to a VLAN-aware bridge interface.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces bridge br0 vif 100 address 192.168.100.1/24 set interfaces bridge br0 vif 100 traffic control in NETEM set interfaces bridge br0 vif 100 traffic control out WFQ set interfaces bridge br0 vlan 100 set interfaces ethernet eth0 bridge-group bridge br0 set interfaces ethernet eth0 bridge-group vlan 100 set service snmp community COMMUNITY2TEST set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic control NETEM type network-emulator packet-loss 0.5 set traffic control WFQ type wfq bandwidth 100 set traffic control WFQ type wfq class 1 weight 10 set traffic control WFQ type wfq class 2 weight 10 set traffic control WFQ type wfq default-class 2 set traffic control WFQ type wfq match 1 class 1 set traffic control WFQ type wfq match 1 ip protocol tcp set traffic control WFQ type wfq match 1 ip source port 1234
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 vif 100 address 192.168.100.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping the IP address 192.168.100.1 from DUT1:
admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.662 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.662/0.662/0.662/0.000 ms
Step 4: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 1234 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 44644 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 127 MBytes 1.06 Gbits/sec 456 35.4 KBytes [ 5] 1.00-2.00 sec 124 MBytes 1.04 Gbits/sec 461 18.4 KBytes [ 5] 2.00-3.00 sec 68.3 MBytes 573 Mbits/sec 246 19.8 KBytes [ 5] 3.00-4.00 sec 89.3 MBytes 749 Mbits/sec 337 22.6 KBytes [ 5] 4.00-5.00 sec 121 MBytes 1.02 Gbits/sec 482 24.0 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 529 MBytes 888 Mbits/sec 1982 sender [ 5] 0.00-5.00 sec 528 MBytes 886 Mbits/sec receiver iperf Done.
Step 5: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 4321 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 40884 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 147 MBytes 1.23 Gbits/sec 514 15.6 KBytes [ 5] 1.00-2.00 sec 129 MBytes 1.08 Gbits/sec 484 22.6 KBytes [ 5] 2.00-3.00 sec 124 MBytes 1.04 Gbits/sec 461 22.6 KBytes [ 5] 3.00-4.00 sec 97.3 MBytes 816 Mbits/sec 352 18.4 KBytes [ 5] 4.00-5.00 sec 89.2 MBytes 748 Mbits/sec 313 35.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 586 MBytes 983 Mbits/sec 2124 sender [ 5] 0.00-5.01 sec 585 MBytes 979 Mbits/sec receiver iperf Done.
Step 6: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 1234 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 43378 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 162 84.8 KBytes [ 5] 1.00-2.00 sec 11.0 MBytes 92.3 Mbits/sec 63 90.5 KBytes [ 5] 2.00-3.00 sec 11.5 MBytes 96.4 Mbits/sec 71 93.3 KBytes [ 5] 3.00-4.00 sec 11.4 MBytes 95.9 Mbits/sec 68 79.2 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.9 Mbits/sec 59 76.4 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.9 Mbits/sec 423 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 33200 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.2 MBytes 119 Mbits/sec 203 50.9 KBytes [ 5] 1.00-2.00 sec 11.2 MBytes 93.8 Mbits/sec 34 93.3 KBytes [ 5] 2.00-3.00 sec 11.7 MBytes 98.5 Mbits/sec 88 69.3 KBytes [ 5] 3.00-4.00 sec 11.2 MBytes 93.8 Mbits/sec 50 94.7 KBytes [ 5] 4.00-5.00 sec 11.2 MBytes 93.8 Mbits/sec 74 103 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.5 MBytes 99.9 Mbits/sec 449 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0 OutClassPackets\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassPackets\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.1 = INTEGER: [1-9]\d* OutClassBytes\.[^=]+\.2 = INTEGER: [1-9]\d* OutClassDrops\.[^=]+\.1 = INTEGER: \d+ OutClassDrops\.[^=]+\.2 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.1 = INTEGER: \d+ OutClassOverlimits\.[^=]+\.2 = INTEGER: \d+ OutPps\.[^=]+ = INTEGER: [1-9]\d*Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPackets."br0"."100" = INTEGER: 183879 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutPps."br0"."100" = INTEGER: 7608 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBytes."br0"."100" = INTEGER: 135039842 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutDrops."br0"."100" = INTEGER: 33 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutKind."br0"."100" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutBps."br0"."100" = INTEGER: 9117882 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutOverlimits."br0"."100" = INTEGER: 7703 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutRate."br0"."100" = INTEGER: 100000000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassTag."br0"."100".1 = INTEGER: 1 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassTag."br0"."100".2 = INTEGER: 2 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".1 = INTEGER: 47082 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassPackets."br0"."100".2 = INTEGER: 136797 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".1 = INTEGER: 3187082 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassBytes."br0"."100".2 = INTEGER: 131852760 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassDrops."br0"."100".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassDrops."br0"."100".2 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlOutClassOverlimits."br0"."100".2 = INTEGER: 4058 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPackets."br0"."100" = INTEGER: 814093 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInPps."br0"."100" = INTEGER: 14169 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBytes."br0"."100" = INTEGER: 1220826632 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInDrops."br0"."100" = INTEGER: 4150 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInKind."br0"."100" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInBps."br0"."100" = INTEGER: 20663828 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInOverlimits."br0"."100" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBridgeVifTrafficControlInRate."br0"."100" = INTEGER: 0
Test Traffic Control OIDs On Bonding Interface
Description
In this scenario, traffic control disciplines are attached to a Bonding interface.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces bonding bond0 address 192.168.100.1/24 set interfaces bonding bond0 miimon 1 set interfaces bonding bond0 traffic control in NETEM set interfaces bonding bond0 traffic control out WFQ set interfaces ethernet eth0 bond-group bond0 set interfaces ethernet eth1 bond-group bond0 set service snmp community COMMUNITY2TEST set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic control NETEM type network-emulator packet-loss 0.5 set traffic control WFQ type wfq bandwidth 100 set traffic control WFQ type wfq class 1 weight 10 set traffic control WFQ type wfq class 2 weight 10 set traffic control WFQ type wfq default-class 2 set traffic control WFQ type wfq match 1 class 1 set traffic control WFQ type wfq match 1 ip protocol tcp set traffic control WFQ type wfq match 1 ip source port 1234
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 192.168.100.2/24 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'
Step 3: Ping the IP address 192.168.100.1 from DUT1:
admin@DUT1$ ping 192.168.100.1 count 1 size 56 timeout 1Show output
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.939 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.939/0.939/0.939/0.000 ms
Step 4: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 1234 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 1234 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 1234 [ 5] local 192.168.100.2 port 55376 connected to 192.168.100.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 77.0 MBytes 645 Mbits/sec 306 49.5 KBytes [ 5] 1.00-2.00 sec 111 MBytes 932 Mbits/sec 382 28.3 KBytes [ 5] 2.00-3.00 sec 89.7 MBytes 752 Mbits/sec 306 22.6 KBytes [ 5] 3.00-4.00 sec 152 MBytes 1.28 Gbits/sec 552 42.4 KBytes [ 5] 4.00-5.00 sec 157 MBytes 1.32 Gbits/sec 570 28.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 587 MBytes 984 Mbits/sec 2116 sender [ 5] 0.00-5.00 sec 586 MBytes 983 Mbits/sec receiver iperf Done.
Step 5: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 4321 admin@DUT1$ monitor test performance client 192.168.100.1 duration 5 port 4321 parallel 1Expect the following output on
DUT1:Connecting to host 192.168.100.1, port 4321 [ 5] local 192.168.100.2 port 57234 connected to 192.168.100.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 88.5 MBytes 743 Mbits/sec 308 35.4 KBytes [ 5] 1.00-2.00 sec 108 MBytes 908 Mbits/sec 429 15.6 KBytes [ 5] 2.00-3.00 sec 85.4 MBytes 716 Mbits/sec 316 25.5 KBytes [ 5] 3.00-4.00 sec 64.8 MBytes 543 Mbits/sec 194 31.1 KBytes [ 5] 4.00-5.00 sec 62.4 MBytes 523 Mbits/sec 249 31.1 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 409 MBytes 687 Mbits/sec 1496 sender [ 5] 0.00-5.00 sec 409 MBytes 685 Mbits/sec receiver iperf Done.
Step 6: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 1234 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 1234 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 1234 [ 5] local 192.168.100.1 port 56168 connected to 192.168.100.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 15.1 MBytes 126 Mbits/sec 212 79.2 KBytes [ 5] 1.00-2.00 sec 11.4 MBytes 95.9 Mbits/sec 71 65.0 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 55 79.2 KBytes [ 5] 3.00-4.00 sec 11.3 MBytes 94.9 Mbits/sec 49 110 KBytes [ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec 91 70.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.5 MBytes 102 Mbits/sec 478 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 192.168.100.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 192.168.100.2, port 4321 [ 5] local 192.168.100.1 port 45108 connected to 192.168.100.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.0 MBytes 117 Mbits/sec 171 90.5 KBytes [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec 93 76.4 KBytes [ 5] 2.00-3.00 sec 11.4 MBytes 95.9 Mbits/sec 68 70.7 KBytes [ 5] 3.00-4.00 sec 11.5 MBytes 96.4 Mbits/sec 50 89.1 KBytes [ 5] 4.00-5.00 sec 11.4 MBytes 95.4 Mbits/sec 52 87.7 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 59.6 MBytes 99.9 Mbits/sec 434 sender [ 5] 0.00-5.00 sec 58.4 MBytes 98.0 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPackets."bond0" = INTEGER: 191559 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutPps."bond0" = INTEGER: 7718 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBytes."bond0" = INTEGER: 135502443 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutDrops."bond0" = INTEGER: 33 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutKind."bond0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutBps."bond0" = INTEGER: 9256041 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutOverlimits."bond0" = INTEGER: 7110 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutRate."bond0" = INTEGER: 100000000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassTag."bond0".1 = INTEGER: 1 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassTag."bond0".2 = INTEGER: 2 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".1 = INTEGER: 66723 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassPackets."bond0".2 = INTEGER: 124836 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".1 = INTEGER: 4485690 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassBytes."bond0".2 = INTEGER: 131016753 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassDrops."bond0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassDrops."bond0".2 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlOutClassOverlimits."bond0".2 = INTEGER: 3735 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPackets."bond0" = INTEGER: 728221 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInPps."bond0" = INTEGER: 12190 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBytes."bond0" = INTEGER: 1091099817 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInDrops."bond0" = INTEGER: 3653 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInKind."bond0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInBps."bond0" = INTEGER: 17677251 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInOverlimits."bond0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesBondingTrafficControlInRate."bond0" = INTEGER: 0
Test Traffic Control OIDs On Tunnel Interface
Description
In this scenario, traffic control disciplines are attached to a Tunnel interface.
Scenario
Step 1: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 192.168.100.1/24 set interfaces tunnel tun0 address 10.0.0.1/24 set interfaces tunnel tun0 encapsulation gre set interfaces tunnel tun0 local-address 192.168.100.1 set interfaces tunnel tun0 remote-address 192.168.100.2 set interfaces tunnel tun0 traffic control in NETEM set interfaces tunnel tun0 traffic control out WFQ set service snmp community COMMUNITY2TEST set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic control NETEM type network-emulator packet-loss 0.5 set traffic control WFQ type wfq bandwidth 100 set traffic control WFQ type wfq class 1 weight 10 set traffic control WFQ type wfq class 2 weight 10 set traffic control WFQ type wfq default-class 2 set traffic control WFQ type wfq match 1 class 1 set traffic control WFQ type wfq match 1 ip protocol tcp set traffic control WFQ type wfq match 1 ip source port 1234
Step 2: Set the following configuration in DUT1 :
set interfaces ethernet eth0 address 192.168.100.2/24 set interfaces tunnel tun0 address 10.0.0.2/24 set interfaces tunnel tun0 encapsulation gre set interfaces tunnel tun0 local-address 192.168.100.2 set interfaces tunnel tun0 remote-address 192.168.100.1 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 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.944 ms --- 10.0.0.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.944/0.944/0.944/0.000 ms
Step 4: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 1234 admin@DUT1$ monitor test performance client 10.0.0.1 duration 5 port 1234 parallel 1Expect the following output on
DUT1:Connecting to host 10.0.0.1, port 1234 [ 5] local 10.0.0.2 port 35336 connected to 10.0.0.1 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 203 MBytes 1.70 Gbits/sec 836 439 KBytes [ 5] 1.00-2.00 sec 205 MBytes 1.72 Gbits/sec 894 143 KBytes [ 5] 2.00-3.00 sec 170 MBytes 1.43 Gbits/sec 637 106 KBytes [ 5] 3.00-4.00 sec 180 MBytes 1.51 Gbits/sec 686 833 KBytes [ 5] 4.00-5.00 sec 262 MBytes 2.20 Gbits/sec 868 68.1 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1021 MBytes 1.71 Gbits/sec 3921 sender [ 5] 0.00-5.00 sec 1017 MBytes 1.71 Gbits/sec receiver iperf Done.
Step 5: Initiate a bandwidth test from DUT1 to DUT0
admin@DUT0$ monitor test performance server port 4321 admin@DUT1$ monitor test performance client 10.0.0.1 duration 5 port 4321 parallel 1Expect the following output on
DUT1:Connecting to host 10.0.0.1, port 4321 [ 5] local 10.0.0.2 port 52404 connected to 10.0.0.1 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 281 MBytes 2.36 Gbits/sec 1019 132 KBytes [ 5] 1.00-2.00 sec 281 MBytes 2.36 Gbits/sec 674 131 KBytes [ 5] 2.00-3.00 sec 226 MBytes 1.90 Gbits/sec 850 91.8 KBytes [ 5] 3.00-4.00 sec 239 MBytes 2.00 Gbits/sec 753 147 KBytes [ 5] 4.00-5.00 sec 265 MBytes 2.22 Gbits/sec 899 22.2 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 1.26 GBytes 2.17 Gbits/sec 4195 sender [ 5] 0.00-5.00 sec 1.26 GBytes 2.16 Gbits/sec receiver iperf Done.
Step 6: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 1234 admin@DUT0$ monitor test performance client 10.0.0.2 duration 5 port 1234 parallel 1Expect the following output on
DUT0:Connecting to host 10.0.0.2, port 1234 [ 5] local 10.0.0.1 port 43666 connected to 10.0.0.2 port 1234 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 14.9 MBytes 125 Mbits/sec 237 77.9 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 97.9 Mbits/sec 73 68.1 KBytes [ 5] 2.00-3.00 sec 11.6 MBytes 97.4 Mbits/sec 58 84.8 KBytes [ 5] 3.00-4.00 sec 11.6 MBytes 97.4 Mbits/sec 75 72.3 KBytes [ 5] 4.00-5.00 sec 10.9 MBytes 91.2 Mbits/sec 68 68.1 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.7 MBytes 102 Mbits/sec 511 sender [ 5] 0.00-5.00 sec 59.0 MBytes 98.9 Mbits/sec receiver iperf Done.
Step 7: Initiate a bandwidth test from DUT0 to DUT1
admin@DUT1$ monitor test performance server port 4321 admin@DUT0$ monitor test performance client 10.0.0.2 duration 5 port 4321 parallel 1Expect the following output on
DUT0:Connecting to host 10.0.0.2, port 4321 [ 5] local 10.0.0.1 port 57840 connected to 10.0.0.2 port 4321 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 13.9 MBytes 117 Mbits/sec 163 68.1 KBytes [ 5] 1.00-2.00 sec 11.7 MBytes 97.9 Mbits/sec 66 87.6 KBytes [ 5] 2.00-3.00 sec 11.3 MBytes 94.8 Mbits/sec 68 75.1 KBytes [ 5] 3.00-4.00 sec 11.7 MBytes 98.4 Mbits/sec 76 65.4 KBytes [ 5] 4.00-5.00 sec 11.5 MBytes 96.4 Mbits/sec 62 72.3 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-5.00 sec 60.1 MBytes 101 Mbits/sec 435 sender [ 5] 0.00-5.00 sec 59.0 MBytes 98.9 Mbits/sec receiver iperf Done.
Step 8: Run the command service snmp walk local-agent v1 COMMUNITY2TEST oid "1.3.6.1.4.1.2007.6.3.1" | grep TrafficControl on DUT0 and check whether the output matches the following regular expressions:
OutKind\.[^=]+ = STRING: (htb|ceetm) OutPackets\.[^=]+ = INTEGER: [1-9]\d* OutBytes\.[^=]+ = INTEGER: [1-9]\d* InKind\.[^=]+ = STRING: netem InPackets\.[^=]+ = INTEGER: [1-9]\d* InBytes\.[^=]+ = INTEGER: [1-9]\d* OutDrops\.[^=]+ = INTEGER: \d+ OutOverlimits\.[^=]+ = INTEGER: \d+ OutRate\.[^=]+ = INTEGER: 100000000 InPps\.[^=]+ = INTEGER: [1-9]\d* InDrops\.[^=]+ = INTEGER: [1-9]\d* InOverlimits\.[^=]+ = INTEGER: \d+ InRate\.[^=]+ = INTEGER: 0Show output
TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPackets."tun0" = INTEGER: 139878 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutPps."tun0" = INTEGER: 7131 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBytes."tun0" = INTEGER: 131097781 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutDrops."tun0" = INTEGER: 33 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutKind."tun0" = STRING: htb TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutBps."tun0" = INTEGER: 9007806 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutOverlimits."tun0" = INTEGER: 7187 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutRate."tun0" = INTEGER: 100000000 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassTag."tun0".1 = INTEGER: 1 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassTag."tun0".2 = INTEGER: 2 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".1 = INTEGER: 22785 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassPackets."tun0".2 = INTEGER: 117093 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".1 = INTEGER: 1198771 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassBytes."tun0".2 = INTEGER: 129899010 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassDrops."tun0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassDrops."tun0".2 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".1 = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlOutClassOverlimits."tun0".2 = INTEGER: 3786 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPackets."tun0" = INTEGER: 1702042 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInPps."tun0" = INTEGER: 33841 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBytes."tun0" = INTEGER: 2506112631 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInDrops."tun0" = INTEGER: 687 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInKind."tun0" = STRING: netem TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInBps."tun0" = INTEGER: 49527806 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInOverlimits."tun0" = INTEGER: 0 TELDAT-OSDX-MONDB-INTERFACES-MIB::telOSDxMonDBInterfacesTunnelTrafficControlInRate."tun0" = INTEGER: 0