nqa entry qos ef type icmp-echo data-size 20000 destination ip 192.168.3.1 frequency 100 probe count 15 source ip 192.168.2.1 tos 184
nqa schedule qos ef start-time now lifetime forever
[P-AGG]dis acl all Advanced IPv4 ACL 3000, 1 rule, ACL's step is 5 rule 5 permit ip dscp ef counting (108977 times matched)
# traffic classifier voice operator or if-match acl 3000 # traffic behavior voice-out queue ef bandwidth 30000 cbs 750000 # qos policy pm-chd_AWS-PROD_out classifier voice behavior voice-out
ip route-static 192.168.3.0 24 192.168.0.1
interface GigabitEthernet0/0/10 port link-mode route combo enable copper ip address 192.168.0.2 255.255.255.0 qos apply policy pm-chd_AWS-PROD_out outbound [P-AGG]dis qos policy interface GigabitEthernet 0/0/10 Interface: GigabitEthernet0/0/10 Direction: Outbound Policy: pm-chd_AWS-PROD_out Classifier: default-class Matched : 0 (Packets) 0 (Bytes) 5-minute statistics: Forwarded: 0/0 (pps/bps) Dropped : 0/0 (pps/bps) Operator: AND Rule(s) : If-match any Behavior: be Default Queue: Flow based Weighted Fair Queue: Max number of hashed queues: 256 Matched : 0 (Packets) 0 (Bytes) Enqueued : 0 (Packets) 0 (Bytes) Discarded: 0 (Packets) 0 (Bytes) Discard Method: Tail drop Classifier: voice Matched : 107927 (Packets) 157911226 (Bytes) 5-minute statistics: Forwarded: 359/4209873 (pps/bps) Dropped : 0/0 (pps/bps) Operator: OR Rule(s) : If-match acl 3000 Behavior: voice-out Expedited Forwarding: Bandwidth 30000 (kbps) CBS 750000 (Bytes) Matched : 0 (Packets) 0 (Bytes) Enqueued : 0 (Packets) 0 (Bytes) Discarded: 0 (Packets) 0 (Bytes) Discard Method: Tail drop # qos policy pm-chd_AWS-PROD_out classifier voice behavior voice-out 只有qos流分类有计数,而流行为的 EF队列没有任何的计数
Behavior: voice-out Expedited Forwarding: Bandwidth 30000 (kbps) CBS 750000 (Bytes) Matched : 0 (Packets) 0 (Bytes) Enqueued : 0 (Packets) 0 (Bytes) Discarded: 0 (Packets) 0 (Bytes) Discard Method: Tail drop
NQA测试流量路径问题:
NQA源IP:192.168.2.1,目的IP:192.168.3.1
静态路由:192.168.3.0/24 → 192.168.0.1
接口地址:192.168.0.2/24
关键问题:NQA流量可能没有从GigabitEthernet0/0/10接口发出
流量路径验证:
display ip routing-table 192.168.3.1
tracert -a 192.168.2.1 192.168.3.1
解决方案
方案1:修正NQA配置匹配实际流量路径
# 修改NQA使用接口所在网段
nqa entry qos ef type icmp-echo
data-size 20000
destination ip 192.168.0.1 # 改为下一跳地址
frequency 100
probe count 15
source ip 192.168.0.2 # 改为接口地址
tos 184
方案2:添加回程路由确保双向流量
# 确保192.168.3.1到192.168.2.1的回报文也经过正确路径
ip route-static 192.168.2.0 24 192.168.0.1
方案3:使用更准确的测试方法
# 创建更精确的ACL匹配
acl advanced 3001
rule 5 permit ip source 192.168.2.1 0 destination 192.168.3.1 0 dscp ef
# 在接口入方向应用QoS进行测试
interface GigabitEthernet0/0/x
qos apply policy pm-chd_AWS-PROD_out inbound
诊断命令
# 检查实际流量路径
display ip routing-table 192.168.3.1
# 检查接口计数器的详细信息
display interface GigabitEthernet0/0/10
# 检查QoS策略详细统计
display qos policy interface GigabitEthernet0/0/10 verbose
# 实时监控NQA结果
display nqa result history
推荐配置调整
# 简化测试,直接使用接口地址
nqa entry qos ef type icmp-echo
data-size 1000
destination ip 192.168.0.1
frequency 10
probe count 5
source ip 192.168.0.2
tos 184
# 启动测试
nqa schedule qos ef start-time now lifetime forever
请先使用display ip routing-table命令确认192.168.3.1的路由确实指向GigabitEthernet0/0/10接口,这是问题的最可能原因。
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论