14
Solution
To resolve the issue:
1. Identify the characteristics of the packets that are not forwarded correctly.
Use a packet capture tool to identify the characteristics of the traffic, such as the IP address,
MAC address, or VLAN. Make sure the characteristics are unique among traffic to be
forwarded.
2. Configure a QoS policy and apply it to interfaces:
Figure 8 Traffic path
a. Configure a QoS policy according to the traffic characteristics. This example uses
destination IP address 2.2.2.2.
<Sysname> system-view
System View: return to User View with Ctrl+Z.
[Sysname] time-range t1 from 12:00 11/11/2013 to 12:01 11/11/2013
[Sysname] acl number 3000 name geliACL
[Sysname-acl-adv-3000-geliACL] rule 0 permit ip destination 2.2.2.2 0 time-range
t1
[Sysname-acl-adv-3000-geliACL] quit
[Sysname] traffic classifier count
[Sysname-classifier-count] if-match acl 3000
[Sysname-classifier-count] quit
[Sysname] traffic behavior count
[Sysname-behavior-count] accounting packet
[Sysname-behavior-count] quit
[Sysname] qos policy count
[Sysname-qospolicy-count] classifier count behavior count
b. Apply the QoS policy to interfaces on devices along the forwarding path. In this example,
apply the QoS policy to the incoming traffic on Ten-GigabitEthernet 1/0/1 on Device B and
Ten-GigabitEthernet 2/0/1 on Device C.
The following shows the application on Device B:
[Sysname-qospolicy-count] quit
[Sysname] interface ten-gigabitethernet 1/0/1
[Sysname-Ten-GigabitEthernet1/0/1] qos apply policy count inbound
3. After the time range, execute the display qos policy interface command to display
traffic statistics on the interfaces:
{ On Ten-GigabitEthernet 1/0/1 of Device B:
<Sysname> display qos policy interface ten-gigabitethernet 1/0/1
Interface:ten-gigabitethernet1/0/1
Direction: Inbound
Policy: count
Classifier: count
Operator: AND
Rule(s) : If-match ACL 3000
Behavior: count
To Next Page
Loading...
Need help?
General