Table of Contents
Advertisement
Solution
To resolve the problem:
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 all traffic to be forwarded.
2.
Configure a QoS policy and apply it to an interface:
Figure 17 Traffic path
a.
Configure a QoS policy according to the traffic characteristics. In this example, use a
destination IP address 2.2.2.2.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] time-range t1 from 12:00 11/11/2013 to 12:01 11/11/2013
[H3C] acl number 3000 name geliACL
[H3C-acl-adv-3000-geliACL] rule 0 permit ip destination 2.2.2.2 0 time-range t1
[H3C-acl-adv-3000-geliACL] quit
[H3C] traffic classifier count
[H3C-classifier-count] if-match acl 3000
[H3C-classifier-count] quit
[H3C] traffic behavior count
[H3C-behavior-count] accounting
[H3C-behavior-count] quit
[H3C] qos policy count
[H3C-qospolicy-count] classifier count behavior count
b.
Apply the QoS policy to interfaces on different devices on the forwarding path. In this example,
apply the QoS policy to GigabitEthernet 1/0/1 on Device B and GigabitEthernet 2/0/1 on
Device C.
The following shows the application on Device B:
[H3C-qospolicy-count] quit
[H3C] interface gigabitethernet 1/0/1
[H3C-GigabitEthernet1/0/1] qos apply policy count inbound
3.
Execute the display qos policy interface command to display traffic statistics on the interfaces:
On GigabitEthernet 1/0/1 on Device B:
[H3C-GigabitEthernet1/0/1] display qos policy interface gigabitethernet 1/0/1
Interface: GigabitEthernet1/0/1
Direction: Inbound
Direction: Inbound
Policy: count
Classifier: count
43
Advertisement
Table of Contents
Troubleshooting
