User Manual

TRex 43 / 113
Problem definition:
Scenario: TRex with two ports and an SFR traffic profile.
Without VLAN/sub interfaces, all client emulated traffic is sent on port 0, and all server emulated traffic (example: HTTP
response) on port 1.
TRex port 0 ( client) <-> [ DUT ] <-> TRex port 1 ( server)
Without VLAN support, the traffic is asymmetric. 10% of the traffic is sent from port 0 (client side), 90% from port 1 (server).
Port 1 is the bottlneck (10Gb/s limit).
With VLAN/sub interfaces
TRex port 0 ( client VLAN0) <-> | DUT | <-> TRex port 1 ( server-VLAN0)
TRex port 0 ( server VLAN1) <-> | DUT | <-> TRex port 1 ( client-VLAN1)
In this case, traffic on vlan0 is sent as before, while for traffic on vlan1, the order is reversed (client traffic sent on port1 and
server traffic on port0). TRex divides the flows evenly between the vlans. This results in an equal amount of traffic on each port.
Router configuation:
!
interface TenGigabitEthernet1/0/0
v
1
mac-address 0000.0001.0000
mtu 4000
no ip address
load-interval 30
!
i
interface TenGigabitEthernet1/0/0.100
encapsulation dot1Q 100
v
2
ip address 11.77.11.1 255.255.255.0
ip nbar protocol-discovery
ip policy route-map vlan_100_p1_to_p2
v
3
!
interface TenGigabitEthernet1/0/0.200
encapsulation dot1Q 200
v
4
ip address 11.88.11.1 255.255.255.0
ip nbar protocol-discovery
ip policy route-map vlan_200_p1_to_p2
v
5
!
interface TenGigabitEthernet1/1/0
mac-address 0000.0001.0000
mtu 4000
no ip address
load-interval 30
!
interface TenGigabitEthernet1/1/0.100
encapsulation dot1Q 100
ip address 22.77.11.1 255.255.255.0
ip nbar protocol-discovery
ip policy route-map vlan_100_p2_to_p1
!
interface TenGigabitEthernet1/1/0.200
encapsulation dot1Q 200
ip address 22.88.11.1 255.255.255.0
ip nbar protocol-discovery
ip policy route-map vlan_200_p2_to_p1
!