路由器(1.1.1.1)---(ospf)---传输设备------(1.1.1.2)交换机
手动断掉nqa探测地址的接口,看track一直是Positive状态,同时也没有down掉 FortyGigE1/1/5 这个接口
interface Ten-GigabitEthernet1/0/1
port link-mode route
ip address x.x.1.1 255.255.255.252
ospf network-type p2p
ospfv3 300 area 0.0.0.0
ospfv3 network-type p2p
#
nqa entry admin NQA
type icmp-echo
destination ip x.x.1.2
frequency 1000
next-hop ip x.x.1.2
probe count 10
probe timeout 1000
reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only
source ip x.x.1.1
nqa schedule admin MHZWY start-time now lifetime forever
track 1 nqa entry admin NQA reaction 1
#
rtm cli-policy data-down
event track 1 state negative
action 0 cli system-view
action 1 cli interface FortyGigE1/1/5
action 2 cli shutdown
user-role network-admin
user-role network-operator
commit
#
rtm cli-policy data-up
event track 1 state positive
action 0 cli system-view
action 1 cli interface FortyGigE1/1/5
action 2 cli undo shutdown
user-role network-admin
user-role network-operator
commit
#
track的状态也是Positive,未改变
-----------display track all---------
Track ID: 1
State: Positive
Duration: 0 days 0 hours 7 minutes 24 seconds
Tracked object type: NQA
Notification delay: Positive 0, Negative 0 (in seconds)
Tracked object:
NQA entry: admin mhzwy
Reaction: 1
Remote IP/URL: x.x.1.2
Local IP: x.x.1.1
Interface: --
断掉交换机x.x.1.2所在接口时,发现路由器pingx.x.1.2还是能通
因为通过OSPF学到了此路由,但是下一跳地址改变了,所以nqa entry admin NQA就无法匹配了
Destination/Mask Proto Pre Cost NextHop Interface
x.x.1.2/30 O_INTRA 10 352 x.x.1.5 FGE5/2/1.100
在track没联动成功时查看NQA信息,发现一直有内部报错计数增加
[H3C]dis nqa statistics admin NQA
NQA entry (admin admin, tag naq) test statistics:
NO. : 1
Start time: 2023-10-24 17:18:23.1
Life time: 140 seconds
Send operation times: 860 Receive response times: 860
Min/Max/Average round trip time: 1/38/2
Square-Sum of round trip time: 10657
Extended results:
Packet loss ratio: 0%
Failures due to timeout: 0
Failures due to internal error: 540 ////因内部错误失败的次数
Failures due to other errors: 0
Reaction statistics:
Index Checked Element Threshold Type Checked Num Over-threshold Num
1 probe-fail consecutive 860 0
内部报错,不在Over-threshold Num值里体现,所以这里的探测失败次数显示为0。
将 next-hop ip ,改为out interface 配置探测报文出接口
且当因内部错误探测失败,无法联动track项切换
该案例暂时没有网友评论
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作