H3C的静态路由、Track与NQA联动配置举例

合集下载

H3C交换机配置静态路由的方法

H3C交换机配置静态路由的方法

H3C交换机配置静态路由的方法H3C交换机配置静态路由的方法其实关于配置静态路由的方法有很多,下面YJBYS店铺为大家整理了关于H3C交换机配置静态路由的方法,希望对你有所帮助。

一、组网需求:如下图所示,在三台Switch上通过配置静态路由,使得三台在不同网段的`PC之间可以相互通迅。

二、组网图:配置静态路由典型应用组网图三、配置步骤:软件版本:S9500交换机全系列软件版本硬件版本:S9500交换机全系列硬件版本如上图所示,三、配置步骤:软件版本:S9500交换机全系列软件版本;硬件版本:S9500交换机全系列硬件版本;如上图所示,所有IP地址的掩码均为255.255.255.0。

1)配置交换机SwitchA的配置静态路由[SwitchA]iproute-static1.1.3.0255.255.255.01.1.2.2[SwitchA]iproute-static1.1.4.0255.255.255.01.1.2.2[SwitchA]iproute-static1.1.5.0255.255.255.01.1.2.22)设置交换机SwitchB的配置静态路由。

[SwitchB]iproute-static1.1.2.0255.255.255.01.1.3.1[SwitchB]iproute-static1.1.5.0255.255.255.01.1.3.1[SwitchB]iproute-static1.1.1.0255.255.255.01.1.3.13)设置交换机SwitchC的配置静态路由。

[SwitchC]iproute-static1.1.1.0255.255.255.01.1.2.1[SwitchC]iproute-static1.1.4.0255.255.255.01.1.3.24)在主机A上配缺省网关为1.1.5.2,主机B上配缺省网关为1.1.4.1,主机C上配缺省网关为1.1.1.2。

H3C HA 高可用性 线路监控 track配置手册

H3C HA 高可用性 线路监控 track配置手册
目录
1 Track配置 ·········································································································································· 1-1 1.1 Track简介 ··········································································································································1-1 1.1.1 Track产生背景 ························································································································1-1 1.1.2 Track项简介····························································································································1-1 1.1.3 联动功能工作原理···················································································································1-1 1.1.4 联动功能应用举例···················································································································1-2 1.2 Track配置任务简介····························································································································1-3 1.3 配置Track与监测模块联动·················································································································1-3 1.3.1 配置Track与NQA联动·············································································································1-3 1.3.2 配置Track与BFD联动 ·············································································································1-4 1.3.3 配置Track与接口管理联动 ······································································································1-4 1.4 配置Track与应用模块联动·················································································································1-5 1.4.1 配置Track与VRRP联动 ··········································································································1-5 1.4.2 配置Track与静态路由联动 ······································································································1-6 1.4.3 配置Track与策略路由联动 ······································································································1-7 1.4.4 配置Track与流量重定向联动 ··································································································1-8 1.5 Track显示和维护 ·······························································································································1-9 1.6 Track典型配置举例··························································································································1-10 1.6.1 VRRP、Track与NQA联动配置举例(Master监视上行链路)··············································1-10 1.6.2 VRRP、Track与BFD联动配置举例(Backup监视Master)·················································1-13 1.6.3 VRRP、Track与BFD联动配置举例(Master监视上行链路) ··············································1-15 1.6.4 静态路由、Track与NQA联动配置举例 ·················································································1-19 1.6.5 静态路由、Track与BFD联动配置举例 ··················································································1-23 1.6.6 VRRP、Track与接口管理联动配置举例(Master监视上行接口) ·······································1-26

H3C路由器静态路由配置综合实例

H3C路由器静态路由配置综合实例

静态路由配‎置案例。

路由器A配‎置:[route‎A]inter‎f ace e0[route‎A-e0]ip addre‎s s 192.168.0.1 255.255.255.0[route‎A]inter‎f ace s0[route‎A-s0]ip addre‎s s 192.168.1.1 255.255.255.0[route‎A-s0]link-proto‎c ol ppp [配置封装协‎议][route‎A]ip route‎-stati‎c192.168.3.0 255.255.255.0 192.168.1.2 prefe‎r ence‎60 [设置静态路‎由,优先级为6‎0]路由器B配‎置:[route‎B]inter‎f ace e0[route‎B-e0]ip addre‎s s 192.168.3.1 255.255.255.0[route‎B]inter‎f ace s0[route‎B-s0]ip addre‎s s 192.168.2.1 255.255.255.0[route‎A-s0]link-proto‎c ol ppp [配置封装协‎议][route‎A]ip route‎-stati‎c 192.168.0.0 255.255.255.0 192.168.1.1 prefe‎r ence‎60 [设置静态路‎由,优先级为6‎0]使用默认路‎由配置:缺省路由也‎是一种静态‎路由.简单地说,缺省路由就‎是在没有找‎到任保匹配‎置的路由项‎情况下,才使用的路‎由.即只有当无‎任何合适的‎路由时,缺省路由才‎被使用.[rotue‎A]ip route‎-statc‎i 0.0.0.0 0.0.0.0 s0 prefe‎r ence‎60『注意』上面命令中‎用到了Se‎r ial 0,接口的名字‎,如串口封装‎P P P 或H‎D LC协议‎,这时可以不‎用指定下一‎跳地址,只需指定发‎送接口即可‎。

NQA配置指导(华为、H3C)

NQA配置指导(华为、H3C)

NQA配置指导(华为、H3C)1、H3C NQA、静态路由联动# 创建管理员名为admin、操作标签为test的NQA测试组[SwitchA] nqa entry admin test# 配置测试类型为ICMP-echo[SwitchA-nqa-admin-test] type icmp-echo# 配置测试的⽬的地址为10.2.1.4,下⼀跳地址为10.1.1.2[SwitchA-nqa-admin-test-icmp-echo] destination ip 10.2.1.4[SwitchA-nqa-admin-test-icmp-echo] next-hop 10.1.1.2# 配置测试频率为100ms[SwitchA-nqa-admin-test-icmp-echo] frequency 100# 配置可选参数:⼀次NQA测试中探测的次数为10,探测的超时时间为500毫秒,测试组连续两次测试开始时间的时间间隔为5000毫秒。

[SwitchA-nqa-admin-test-icmp-echo] probe count 10[SwitchA-nqa-admin-test-icmp-echo] probe timeout 500[SwitchA-nqa-admin-test-icmp-echo] frequency 5000# 开启NQA历史记录保存功能,并配置⼀个测试组中能够保存的最⼤历史记录个数为10[SwitchA-nqa-admin-test-icmp-echo] history-record enable[SwitchA-nqa-admin-test-icmp-echo] history-record number 10# 配置联动项1(连续失败5次触发联动)[SwitchA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only# 启动探测[SwitchA] nqa schedule admin test start-time now lifetime forever# 配置Track项1,关联NQA测试组(管理员为admin,操作标签为test)的联动项1[SwitchA] track 1 nqa entry admin test reaction 1# 显⽰ICMP-echo测试中最后⼀次测试的结果[SwitchA] display nqa result admin test# 显⽰ICMP-echo测试的统计结果[SwitchA] display nqa statistics admin test# 显⽰ICMP-echo测试的历史记录[SwitchA] display nqa history admin test# 显⽰Switch A上Track项的信息[SwitchA] display track all# 配置静态路由关联track 1[SwitchA] ip route-static 30.1.1.0 24 10.1.1.2 track 12、H3C NQA、VRRP联动# 在VLAN接⼝1下配置VRRP[SwitchA] interface vlan-interface 1# 创建备份组1,并配置备份组1的虚拟IP地址为10.1.1.10[SwitchA-Vlan-interface2] vrrp vrid 1 virtual-ip 10.1.1.10# 设置Switch A在备份组1中的优先级为110。

H3C交换机配置静态路由的具体方法和细则

H3C交换机配置静态路由的具体方法和细则

H3C交换机配置静态路由的具体方法和细则其实关于配置静态路由的方法我们也讲了很多,这里我们主要针对三台Switch,分析一下H3C交换机配置静态路由的具体方法,希望您看完本文后会有不少收获,也希望本文能教会你更多东西。

一、组网需求:如下图所示,在三台Switch上通过配置静态路由,使得三台在不同网段的PC之间可以相互通迅。

二、组网图:配置静态路由典型应用组网图三、配置步骤:软件版本:S9500交换机全系列软件版本硬件版本:S9500交换机全系列硬件版本如上图所示,三、配置步骤:软件版本:S9500交换机全系列软件版本;硬件版本:S9500交换机全系列硬件版本;如上图所示,所有IP地址的掩码均为255.255.255.0。

1)配置交换机SwitchA的配置静态路由[SwitchA]ip route-static 1.1.3.0 255.255.255.0 1.1.2.2[SwitchA]ip route-static 1.1.4.0 255.255.255.0 1.1.2.2[SwitchA]ip route-static 1.1.5.0 255.255.255.0 1.1.2.22)设置交换机SwitchB的配置静态路由。

[SwitchB]ip route-static 1.1.2.0 255.255.255.0 1.1.3.1[SwitchB]ip route-static 1.1.5.0 255.255.255.0 1.1.3.1[SwitchB]ip route-static 1.1.1.0 255.255.255.0 1.1.3.13)设置交换机SwitchC的配置静态路由。

[SwitchC]ip route-static 1.1.1.0 255.255.255.0 1.1.2.1[SwitchC]ip route-static 1.1.4.0 255.255.255.0 1.1.3.24)在主机A上配缺省网关为1.1.5.2,主机B上配缺省网关为1.1.4.1,主机C 上配缺省网关为1.1.1.2。

H3C路由器静态路由配置综合实例

H3C路由器静态路由配置综合实例

静态路由配置案例。

路由器A配置:[routeA]interface e0[routeA-e0]ip address 192.168.0.1 255.255.255.0[routeA]interface s0[routeA-s0]ip address 192.168.1.1 255.255.255.0[routeA-s0]link-protocol ppp [配置封装协议][routeA]ip route-static 192.168.3.0 255.255.255.0 192.168.1.2 preference 60 [设置静态路由,优先级为60]路由器B配置:[routeB]interface e0[routeB-e0]ip address 192.168.3.1 255.255.255.0[routeB]interface s0[routeB-s0]ip address 192.168.2.1 255.255.255.0[routeA-s0]link-protocol ppp [配置封装协议][routeA]ip route-static 192.168.0.0 255.255.255.0 192.168.1.1 preference 60 [设置静态路由,优先级为60]使用默认路由配置:缺省路由也是一种静态路由.简单地说,缺省路由就是在没有找到任保匹配置的路由项情况下,才使用的路由.即只有当无任何合适的路由时,缺省路由才被使用.[rotueA]ip route-statci 0.0.0.0 0.0.0.0 s0 preference 60『注意』上面命令中用到了Serial 0,接口的名字,如串口封装PPP 或HDLC协议,这时可以不用指定下一跳地址,只需指定发送接口即可。

对于以太口,Serial口封装了非点到点协议比如fr、x25等,必须配置下一跳的ip地址。

H3C HA 高可用性 线路监控 track配置手册

H3C HA 高可用性 线路监控 track配置手册
目录
1 Track配置 ·········································································································································· 1-1 1.1 Track简介 ··········································································································································1-1 1.1.1 Track产生背景 ························································································································1-1 1.1.2 Track项简介····························································································································1-1 1.1.3 联动功能工作原理···················································································································1-1 1.1.4 联动功能应用举例···················································································································1-2 1.2 Track配置任务简介····························································································································1-3 1.3 配置Track与监测模块联动·················································································································1-3 1.3.1 配置Track与NQA联动·············································································································1-3 1.3.2 配置Track与BFD联动 ·············································································································1-4 1.3.3 配置Track与接口管理联动 ······································································································1-4 1.4 配置Track与应用模块联动·················································································································1-5 1.4.1 配置Track与VRRP联动 ··········································································································1-5 1.4.2 配置Track与静态路由联动 ······································································································1-6 1.4.3 配置Track与策略路由联动 ······································································································1-7 1.4.4 配置Track与流量重定向联动 ··································································································1-8 1.5 Track显示和维护 ·······························································································································1-9 1.6 Track典型配置举例··························································································································1-10 1.6.1 VRRP、Track与NQA联动配置举例(Master监视上行链路)··············································1-10 1.6.2 VRRP、Track与BFD联动配置举例(Backup监视Master)·················································1-13 1.6.3 VRRP、Track与BFD联动配置举例(Master监视上行链路) ··············································1-15 1.6.4 静态路由、Track与NQA联动配置举例 ·················································································1-19 1.6.5 静态路由、Track与BFD联动配置举例 ··················································································1-23 1.6.6 VRRP、Track与接口管理联动配置举例(Master监视上行接口) ·······································1-26

H3C track配置手册

H3C track配置手册
i
1 Track配置
1.1 Track简介
1.1.1 Track产生背景
为了避免报文转发失败,提高通信的可靠性,一些模块需要及时感知接口的状态、链路的状态、网 络的可达性或网络的性能。例如,静态路由需要及时感知路由下一跳是否可达。当下一跳不可达时, 报文无法通过该静态路由到达目的网络。此时,应该将静态路由置为无效,确保报文不再通过该静 态路由转发。这些需要感知接口状态、网络可达性等的模块,称为应用模块。 设备可以通过多种方式监测接口状态、链路状态、网络可达性和网络性能,如 NQA(Network Quality Analyzer,网络质量分析)和 BFD(Bidirectional Forwarding Detection,双向转发检测)等。这些 负责监测接口状态、网络可达性等的模块,称为监测模块。 应用模块可以直接与监测模块关联。监测模块负责监测接口状态、链路状态、网络可达性或网络性 能,并将监测结果通知给应用模块;应用模块根据监测结果,进行相应的处理,例如,将静态路由 置为无效。如果应用模块支持与多种监测模块关联,则由于不同监测模块通知给应用模块的监测结 果形式各不相同,应用模块需要分别处理不同形式的监测结果。 在应用模块和监测模块之间增加 Track 模块,可以屏蔽不同监测模块的差异,简化应用模块的处理。
1.1.4 Байду номын сангаас动功能应用举例
下面以 NQA、Track 和静态路由联动为例,说明联动功能的工作原理。 用户在设备上配置了一条静态路由,下一跳地址为 192.168.0.88。如果 192.168.0.88 可达,则报文 可以通过该静态路由转发,该静态路由有效;如果 192.168.0.88 不可达,则通过该静态路由转发报 文会导致报文转发失败,此时,需要将该静态路由置为无效。通过在 NQA、Track 模块和静态路由 之间建立联动,可以实现实时监测下一跳的可达性,以便及时判断静态路由是否有效。 在此例中联动功能的配置方法及其工作原理为: (1) 创建 NQA 测试组,通过 NQA 测试组监测目的地址 192.168.0.88 是否可达。 (2) 创建和 NQA 测试组关联的 Track 项。192.168.0.88 可达时,NQA 会将监测结果通知给 Track

H3C NQA

H3C NQA

MSR系列路由器静态路由绑定探测组功能的配置关键字:MSR; Track; Auto-detect; 静态路由; NQA一、组网需求:原来v3平台Auto-detect功能在v5上被NQA(网络质量分析)和Track替代,v5上已经没有Auto-detect相关命令。

本实验需要实现RouterA上配置一条静态路由,下一跳是RouterB,RouterA和RouterB通过2层交换机相连,RouterA 上配置Track组探测RouterB的地址是否可达,如果探测失败,将RouterA上的静态路由失效。

设备清单:MSR系列路由器2台二、组网图:三、配置步骤:适用设备和版本:MSR系列、Version 5.20, Beta 1506后所有版本。

四、配置关键点:1) 配置NQA探测组,其中关键配置是Reaction的配置;2) 配置Track跟踪组,并和Reaction绑定;3) 将静态路由和Track组绑定;4) 使能nqa agent和nqa调度。

AR系列路由器Atuo-detect功能在静态路由应用中的典型配置【组网需求】在RouterA和RouterC之间创建静态路由;在RouterA上创建侦测组,当侦测组可达时使静态路由生效。

【组网图】【配置脚本】【验证】当RouterA和RouterC之间可达时,RouterA上的路由表和侦测组的情况为:[RouterA]dis ip rout Routing Table: public net Destination/Mask Protocol Pre Cost NexthopInterface10.1.1.0/24 STATIC 60 0 192.168.1.2Serial1/1127.0.0.0/8 DIRECT 0 0 127.0.0.1InLoopBack0127.0.0.1/32 DIRECT 0 0 127.0.0.1InLoopBack0192.168.1.0/24 DIRECT 0 0 192.168.1.1Serial1/1192.168.1.1/32 DIRECT 0 0 127.0.0.1InLoopBack0192.168.1.2/32 DIRECT 0 0 192.168.1.2Serial1/1[RouterA]dis detect-group detect-group 1 : detect loop time(s) : 15 ping wait time(s) : 2 detect retry times : 2detect ip option : and group state : reachable register module num : 1 detect ip count : 1 detect-list ip address next hop 1 10.1.1.1 192.168.1.2现人为断开RouterB和RouterC之间的链路,然后再次显示RouterA上的路由表及侦测组的情况:[RouterA]dis ip rout Routing Table: public net Destination/Mask Protocol Pre Cost NexthopInterface127.0.0.0/8 DIRECT 0 0 127.0.0.1InLoopBack0127.0.0.1/32 DIRECT 0 0 127.0.0.1InLoopBack0192.168.1.0/24 DIRECT 0 0 192.168.1.1Serial1/1192.168.1.1/32 DIRECT 0 0 127.0.0.1InLoopBack0192.168.1.2/32 DIRECT 0 0 192.168.1.2Serial1/1[RouterA]dis detect-group detect-group 1 : detect loop time(s) : 15 ping wait time(s) : 2 detect retry times : 2 detect ip option : and group state : unreachable register module num : 1 detect ip count : 1 detect-list ip address next hop 1 10.1.1.1 192.168.1.2可以看到,当侦测组不可达时,RouterA上到RouterC的静态路由已经消失。

h3c -静态路由命令 源于官网

h3c -静态路由命令 源于官网

02-静态路由命令目录1 静态路由配置命令 (2)1.1 静态路由配置命令 (2)1.1.1 delete static-routes all (2)1.1.2 ip route-static (2)1.1.3 ip route-static default-preference (5)1 静态路由配置命令在以下路由协议的介绍中所指的路由器及路由器图标,代表了一般意义下的路由设备,为提高可读性,在手册的描述中将不另行说明。

1.1 静态路由配置命令1.1.1 delete static-routes all【命令】delete [ vpn-instance vpn-instance-name ] static-routes all【视图】系统视图【缺省级别】2:系统级【参数】vpn-instance-name:指定VPN实例的名称,为1~31个字符的字符串,区分大小写。

【描述】delete static-routes all命令用来删除所有静态路由。

使用本命令删除静态路由时,系统会提示确认,确认后才会删除所配置的所有静态路由。

相关配置可参考命令ip route-static,“IP路由分册/IP路由基础命令”中的display ip routing-table。

【举例】# 删除所有静态路由。

<Sysname> system-view[Sysname] delete static-routes allThis will erase all ipv4 static routes and their configurations, you must reconf igure all static routesAre you sure?[Y/N]:Y1.1.2 ip route-static【命令】ip route-static dest-address{ mask| mask-length} { next-hop-address[ track track-entry-number ] | interface-typeinterface-number [ next-hop-address ][ bfd {control-packet | echo-packet } ] | vpn-instance d-vpn-instance-namenext-hop-address [ track track-entry-number ] } [ preference preference-value ] [ tag tag-value ] [ description description-text ]undo ip route-static dest-address{ mask| mask-length} [ next-hop-address| interface-type interface-number [next-hop-address] | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference-value ]ip route-static vpn-instance s-vpn-instance-name&<1-6> dest-address { mask | mask-length} { next-hop-address [track track-entry-number ] [ public] | interface-type interface-number [ next-hop-address] [ bfd{control-packet | echo-packet } ] | vpn-instance d-vpn-instance-name next-hop-address[ track track-entry-number ] } [ preference preference-value] [ tag tag-value] [ description description-text ]undo ip route-static vpn-instance s-vpn-instance-name&<1-6> dest-address { mask| mask-length} [ next-hop-address[ public] | interface-type interface-number [next-hop-address] | vpn-instance d-vpn-instance-name next-hop-address ] [ preference preference-value ]【视图】系统视图【缺省级别】2:系统级【参数】vpn-instance s-vpn-instance-name&<1-6>:指定源VPN实例的名称,取值范围为1~31个字符,区分大小写。

H3C NQA配置

H3C NQA配置

本文中标有“请以实际情况为准”的特性描述,表示各型号对于此特性的支持情况 可能不同,本节将对此进行说明。
说明:
z H3C MSR 系列路由器对相关命令参数支持情况、缺省值及取值范围的差异内容 请参见本模块的命令手册。
z H3C MSR 系列各型号路由器均为集中式设备。
第1章 NQA 配置
1.1 NQA 简介
1.1.2 NQA 的特点
1. 支持多种测试类型 以往的 Ping 功能是使用 ICMP(Internet Control Message Protocol,互联网控制报 文协议)测试数据包在本端和指定目的端之间的往返时间。NQA 是对 Ping 功能的 扩展和增强,它增加了多种测试类型,提供了更多的功能。 目前 NQA 支持九种测试类型:ICMP-echo、DHCP、FTP、HTTP、UDP-jitter、SNMP、 TCP、UDP-echo 和 DLSw 测试。客户端向对端发送不同类型的测试报文,统计对 端是否回应报文以及报文的往返时间等参数,以便用户根据统计结果判断协议的可 用性和网络的性能。
h3c nqa配置 s6nqau <s6 nqa server enable nqau<g!5b, nqaserver ip-addressport-number g!5b,xip s6nqa v0s6 s6 s6nqa v0s6 e924?system-view s6nqav0s6 nqa agent enable nqav0s6b(1.5 e924?system-view nqa#a4je nqa#a4?nqa entry admin-name operation-tag nqaentry 1.6g!5b nqa#a4 1.6 cmp-echo bh1(y[cyc?,,x,xe'icmp-echo uwpw operation interface interface-type interface-number nqajvn"dhcp-r nqav0n,xftp ,h,xg!5bftp g!5bftp 1-7g!5b ftp p@0ro@><wp%*u`kp0f0h?ppif'0f0n"0#<c system-view nqa#a4?nqa entry admin-name operation-tag g!5b#a2o_http je9 #a2o typehttp destinationip ip-address sourceip ip-address g!5b02o_operation g!5bhttp ,x5%url url http-versionv1.0 typesnmp destinationip ip-address [,x$d0source port port-number sourceip ip-address data-sizesize 00+8v +0data-fill string y[,x$d0source port port-number sourceip ip-address e924?system-view nqa#a4?nqa entry admin-name operation-tag g!5b#a2o_dl sw je 9#a2o_? type dlsw destinationip ip-address nqasystem-view nqa#a4?nqa entry admin-name operation-tag reactiontrap probe-failurecons

NQA与策略路由及静态路由联动配置-

NQA与策略路由及静态路由联动配置-
华为 3Com 机密 未经许可不得扩散
第2页 共6页
interface Vlan-interface20 ip address 192.168.2.1 255.255.255.0 # interface Vlan-interface30 ip address 192.168.3.1 255.255.255.0 # interface Vlan-interface40 ip address 10.1.1.1 255.255.255.252 # interface GigabitEthernet1/0/1 port access vlan 40 # interface GigabitEthernet1/0/2 port access vlan 10 # interface GigabitEthernet1/0/3 port access vlan 20 # interface GigabitEthernet1/0/4 port access vlan 30 # ip route-static 0.0.0.0 0.0.0.0 10.1.1.2 2. RT1 主要配置: sysname RT1 # acl number 2000 rule 0 permit source 192.168.1.0 0.0.0.255 acl number 2001 rule 0 permit source 192.168.2.0 0.0.0.255
华为 3Com 机密 未经许可不得扩散
第4页 共6页
history-records 10 probe count 10 probe timeout 500 reaction 2 checked-element probe-fail threshold-type consecutive 1 action-type trigger-only # policy-based-route aaa permit node 1 if-match acl 2000 apply ip-address default next-hop 100.1.1.2 track 1 policy-based-route aaa permit node 2 if-match acl 2001 apply ip-address default next-hop 200.1.1.2 track 2 policy-based-route aaa permit node 3 # ip route-static fast-reroute route-policy 1 # ip route-static 0.0.0.0 0.0.0.0 100.1.1.2 track 1(电信) ip route-static 0.0.0.0 0.0.0.0 200.1.1.2 track 2 preference 80(移动) ip route-static 192.168.1.0 255.255.255.0 10.1.1.1 ip route-static 192.168.2.0 255.255.255.0 10.1.1.1 # track 1 nqa entry dianxin test reaction 1 track 2 nqa entry yidong test reaction 2 # nqa schedule dianxin test start-time now lifetime forever nqa schedule yidong test start-time now lifetime forever

H3C 静态路由配置

H3C 静态路由配置

操作手册 IP路由分册静态路由目录目录第1章静态路由配置..............................................................................................................1-11.1 简介....................................................................................................................................1-11.1.1 静态路由..................................................................................................................1-11.1.2 缺省路由..................................................................................................................1-21.1.3 静态路由应用...........................................................................................................1-21.2 配置静态路由.....................................................................................................................1-31.2.1 配置准备..................................................................................................................1-31.2.2 配置静态路由...........................................................................................................1-41.3 检测静态路由下一跳是否可达............................................................................................1-41.3.1 配置BFD检测静态路由下一跳是否可达...................................................................1-51.3.2 配置静态路由与Track联动检测下一跳是否可达......................................................1-61.4 静态路由显示和维护..........................................................................................................1-71.5 静态路由典型配置举例(路由应用).................................................................................1-81.6 静态路由典型配置举例(交换应用)...............................................................................1-10本文中标有“请以实际情况为准”的描述,表示各型号对于此特性的支持情况可能不同,本节将对此进行说明。

H3C的静态路由Track与NQA联动配置举例

H3C的静态路由Track与NQA联动配置举例

H3C的静态路由、Track与NQA联动配置举例标签:1. 组网需求Device A、Device B、Device C和Device D连接了和两个网段,在设备上配置静态路由以实现两个网段的互通,并配置路由备份以提高网络的靠得住性。

Device A作为网段内主机的缺省网关,在Device A上存在两条抵达网段的静态路由,下一跳别离为Device B和Device C。

这两条静态路由形成备份,其中:下一跳为Device B的静态路由优先级高,作为主路由。

该路由可达时,Device A通过Device B将报文转发到网段。

下一跳为Device C的静态路作为备份路由。

在Device A上通过静态路由、Track与NQA联动,实时判定主路由是不是可达。

当主路由不可达时,备份路由生效,Device A通过Device C将报文转发到网段。

一样地,Device D作为网段内主机的缺省网关,在Device D上存在两条抵达网段的静态路由,下一跳别离为Device B和Device C。

这两条静态路由形成备份,其中:下一跳为Device B的静态路由优先级高,作为主路由。

该路由可达时,Device D通过Device B将报文转发到网段。

下一跳为Device C的静态路作为备份路由。

在Device D上通过静态路由、Track与NQA联动,实时判定主路由是不是可达。

当主路由不可达时,备份路由生效,Device D通过Device C将报文转发到网段。

2. 组网图图1-2 静态路由、Track与NQA联动配置组网图3. 配置步骤(1)依照创建VLAN,在VLAN中加入对应的端口,并配置各VLAN接口的IP地址,具体配置进程略。

(2)配置Device A# 配置抵达网段的静态路由:下一跳地址为,优先级为缺省值60,该路由与Track项1关联。

<DeviceA> system-view[DeviceA] ip route-static 24 track 1# 配置抵达网段的静态路由:下一跳地址为,优先级为80。

H3C静态路由配置实验

H3C静态路由配置实验

H3C静态路由配置实验一、实验目的1.了解静态路由的实验原理2.掌握静态路由的配置二、实验原理静态路由定义要想实现全网通信,也就是网络中的任意两个节点都能通信,这就要求每个路由器的路由表中必须有到所有网段的路由。

对于路由器来说,它只知道自己直连的网段,对于没有直连的网段,需要管理员人工添加到这些网段的路由。

管理员人工添加到某个网段如何转发,就是静态路由。

静态路由配置要想实现全网络通信,必须添加路由条目。

AR1路由器直连A、B两个网段,C、D网段没有直连,则需要添加到C、D网段的路由。

ip route-static 到达的目标网络号子网掩码下一跳的路由器接口地址ip route-static 172.16.1.0 24 172.16.0.2三、实验拓扑图RTA路由器配置[H3C]int g0/0[H3C-GigabitEthernet0/0]ip address 192.168.1.1 24[H3C-GigabitEthernet0/0]int g0/1[H3C-GigabitEthernet0/1]ip address 192.168.2.1 24[H3C-GigabitEthernet0/1]quit[H3C]ip route-static 192.168.3.0 24 192.168.2.2[H3C]ip route-static 192.168.4.0 24 192.168.2.2[H3C]ip route-static 192.168.5.0 24 192.168.2.2[H3C]display ip routing-tableDestinations : 19 Routes : 19Destination/Mask Proto Pre Cost NextHop Interface ……192.168.1.0/24 Direct 0 0 192.168.1.1 GE0/0 192.168.1.0/32 Direct 0 0 192.168.1.1 GE0/0 192.168.1.1/32 Direct 0 0 127.0.0.1 InLoop0 192.168.1.255/32 Direct 0 0 192.168.1.1 GE0/0 192.168.2.0/24 Direct 0 0 192.168.2.1 GE0/1 192.168.2.0/32 Direct 0 0 192.168.2.1 GE0/1 192.168.2.1/32 Direct 0 0 127.0.0.1 InLoop0 192.168.2.255/32 Direct 0 0 192.168.2.1 GE0/1 192.168.3.0/24 Static 60 0 192.168.2.2 GE0/1 192.168.4.0/24 Static 60 0 192.168.2.2 GE0/1 192.168.5.0/24 Static 60 0 192.168.2.2 GE0/1……RTB路由器配置[H3C]int g0/0[H3C-GigabitEthernet0/0]ip address 192.168.2.2 24[H3C-GigabitEthernet0/0]int g0/1[H3C-GigabitEthernet0/1]ip address 192.168.3.1 24[H3C-GigabitEthernet0/1]quit[H3C]ip route-static 192.168.4.0 24 192.168.3.2[H3C]ip route-static 192.168.5.0 24 192.168.3.2[H3C]ip route-static 192.168.1.0 24 192.168.2.1[H3C]display ip routing-tableDestinations : 19 Routes : 19Destination/Mask Proto Pre Cost NextHop Interface ……192.168.1.0/24 Static 60 0 192.168.2.1 GE0/0 192.168.2.0/24 Direct 0 0 192.168.2.2 GE0/0 192.168.2.0/32 Direct 0 0 192.168.2.2 GE0/0 192.168.2.2/32 Direct 0 0 127.0.0.1 InLoop0 192.168.2.255/32 Direct 0 0 192.168.2.2 GE0/0 192.168.3.0/24 Direct 0 0 192.168.3.1 GE0/1192.168.3.0/32 Direct 0 0 192.168.3.1 GE0/1 192.168.3.1/32 Direct 0 0 127.0.0.1 InLoop0 192.168.3.255/32 Direct 0 0 192.168.3.1 GE0/1 192.168.4.0/24 Static 60 0 192.168.3.2 GE0/1 192.168.5.0/24 Static 60 0 192.168.3.2 GE0/1 ……RTC路由器配置[H3C]int g0/0[H3C-GigabitEthernet0/0]ip address 192.168.3.2 24[H3C-GigabitEthernet0/0]int g0/1[H3C-GigabitEthernet0/1]ip address 192.168.4.1 24[H3C-GigabitEthernet0/1]quit[H3C]ip route-static 192.168.1.0 24 192.168.3.1[H3C]ip route-static 192.168.2.0 24 192.168.3.1[H3C]ip route-static 192.168.5.0 24 192.168.4.2[H3C]display ip routing-tableDestinations : 19 Routes : 20Destination/Mask Proto Pre Cost NextHop Interface……192.168.1.0/24 Static 60 0 192.168.3.1 GE0/0 192.168.2.0/24 Static 60 0 192.168.3.1 GE0/0 192.168.3.0/24 Direct 0 0 192.168.3.2 GE0/0 192.168.3.0/32 Direct 0 0 192.168.3.2 GE0/0 192.168.3.2/32 Direct 0 0 127.0.0.1 InLoop0 192.168.3.255/32 Direct 0 0 192.168.3.2 GE0/0 192.168.4.0/24 Direct 0 0 192.168.4.1 GE0/1 192.168.4.0/32 Direct 0 0 192.168.4.1 GE0/1 192.168.4.1/32 Direct 0 0 127.0.0.1 InLoop0 192.168.4.255/32 Direct 0 0 192.168.4.1 GE0/1 192.168.5.0/24 Static 60 0 192.168.4.2 GE0/1 ……SWA路由器配置[H3C]vlan 10[H3C-vlan10]port g1/0/1[H3C-vlan10]int vlan 10[H3C-Vlan-interface10]ip address 192.168.4.2 24[H3C-Vlan-interface10]vlan 20[H3C-vlan20]port g1/0/2[H3C-Vlan-interface20]ip address 192.168.5.1 24[H3C-Vlan-interface20]quit[H3C]ip route-static 192.168.1.0 24 192.168.4.1 [H3C]ip route-static 192.168.2.0 24 192.168.4.1 [H3C]ip route-static 192.168.3.0 24 192.168.4.1 [H3C]int g1/0/1[H3C-GigabitEthernet1/0/1]port link-type access [H3C-GigabitEthernet1/0/1]port access vlan 10 [H3C-GigabitEthernet1/0/1]int g1/0/2[H3C-GigabitEthernet1/0/2]port link-type access [H3C-GigabitEthernet1/0/2]port access vlan 20[H3C-GigabitEthernet1/0/2]dis cu int g1/0/1#interface GigabitEthernet1/0/1port link-mode bridgeport access vlan 10combo enable fiber#return[H3C-GigabitEthernet1/0/2]dis cu int g1/0/2#interface GigabitEthernet1/0/2port link-mode bridgeport access vlan 20combo enable fiber#Return<H3C>ping 192.168.5.88Ping 192.168.5.88 (192.168.5.88): 56 data bytes, press CTRL_C to break 56 bytes from 192.168.5.88: icmp_seq=0 ttl=251 time=12.000 ms56 bytes from 192.168.5.88: icmp_seq=1 ttl=251 time=8.000 ms56 bytes from 192.168.5.88: icmp_seq=2 ttl=251 time=7.000 ms56 bytes from 192.168.5.88: icmp_seq=3 ttl=251 time=6.000 ms56 bytes from 192.168.5.88: icmp_seq=4 ttl=251 time=7.000 ms<H3C>ping 192.168.1.88Ping 192.168.1.88 (192.168.1.88): 56 data bytes, press CTRL_C to break56 bytes from 192.168.1.88: icmp_seq=0 ttl=251 time=8.000 ms56 bytes from 192.168.1.88: icmp_seq=1 ttl=251 time=5.000 ms56 bytes from 192.168.1.88: icmp_seq=2 ttl=251 time=8.000 ms56 bytes from 192.168.1.88: icmp_seq=3 ttl=251 time=8.000 ms56 bytes from 192.168.1.88: icmp_seq=4 ttl=251 time=8.000 ms1.路由器只关心到某个网段如何转发数据包,因此在路由器上添加路由,必须是到某个网段(子网)的路由,不能添加到某个特定地址的路由。

H3C Track命令

H3C Track命令
<Sysname> system-view [Sysname] track 1 bfd echo interface ethernet 1/0 remote ip 192.168.40.1 local ip 192.168.40.2
z 交换应用 # 创建与 BFD 会话关联的 Track 项 1。BFD 会话使用 Echo 报文进行探测,出接口 为 VLAN 接口 2,远端 IP 地址为 192.168.40.1,本地 IP 地址为 192.168.40.2。
【举例】 # 创建与 NQA 测试组(admin–test)中联动项 3 关联的 Track 项 1。
<Sysname> system-view [Sysname] track 1 nqa entry admin test reaction 3
1-5
1.1.2 track bfd echo
【命令】 track track-entry-number bfd echo interface interface-type interface-number remote ip remote-ip local ip local-ip undo track track-entry-number
【描述】 track 命令用来创建与 NQA 测试组中指定联动项关联的 Track 项。undo track 命令 用来删除已创建的 Track 项。
1-4
命令手册 系统分册 Track
第 1 章 Track 配置命令
缺省情况下,没有创建 Track 项。 需要注意的是,Track 项创建后,不能再通过 track 命令修改其内容。 相关配置可参考“系统分册/NQA 命令”中的命令 nqa 和 reaction。

H3C 静态路由配置

H3C 静态路由配置

操作手册 IP路由分册静态路由目录目录第1章静态路由配置..............................................................................................................1-11.1 简介....................................................................................................................................1-11.1.1 静态路由..................................................................................................................1-11.1.2 缺省路由..................................................................................................................1-21.1.3 静态路由应用...........................................................................................................1-21.2 配置静态路由.....................................................................................................................1-31.2.1 配置准备..................................................................................................................1-31.2.2 配置静态路由...........................................................................................................1-41.3 检测静态路由下一跳是否可达............................................................................................1-41.3.1 配置BFD检测静态路由下一跳是否可达...................................................................1-51.3.2 配置静态路由与Track联动检测下一跳是否可达......................................................1-61.4 静态路由显示和维护..........................................................................................................1-71.5 静态路由典型配置举例(路由应用).................................................................................1-81.6 静态路由典型配置举例(交换应用)...............................................................................1-10本文中标有“请以实际情况为准”的描述,表示各型号对于此特性的支持情况可能不同,本节将对此进行说明。

H3C Track配置(S5500)

H3C Track配置(S5500)

目录1 Track配置 ............................................................................................................................................ 1-11.1 Track简介 ......................................................................................................................................... 1-11.1.1 Track模块与监测模块联动 ..................................................................................................... 1-11.1.2 Track模块与应用模块联动 ..................................................................................................... 1-11.2 Track配置任务简介........................................................................................................................... 1-11.3 配置Track与监测模块联动.............................................................................................................. 1-21.3.1 配置Track与NQA联动 ........................................................................................................ 1-21.3.2 配置Track与BFD联动......................................................................................................... 1-21.4 配置Track与应用模块联动.............................................................................................................. 1-21.4.1 配置Track与VRRP联动...................................................................................................... 1-21.4.2 配置Track与静态路由联动 ................................................................................................... 1-31.5 Track显示和维护 .............................................................................................................................. 1-41.6 Track典型配置举例........................................................................................................................... 1-41.6.1 VRRP、Track与NQA联动配置举例..................................................................................... 1-41.6.2 静态路由、Track与NQA联动配置举例................................................................................ 1-81 Track配置1.1 Track简介图1-1联动功能实现示意图Track的用途是实现联动功能。

  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

H3C的静态路由、Track与NQA联动配置举例标签:nqa静态路由track1. 组网需求Device A、Device B、Device C和Device D连接了20.1.1.0/24和30.1.1.0/24两个网段,在设备上配置静态路由以实现两个网段的互通,并配置路由备份以提高网络的可靠性。

Device A作为20.1.1.0/24网段内主机的缺省网关,在Device A上存在两条到达30.1.1.0/24网段的静态路由,下一跳分别为Device B和Device C。

这两条静态路由形成备份,其中:●下一跳为Device B的静态路由优先级高,作为主路由。

该路由可达时,Device A通过Device B将报文转发到30.1.1.0/24网段。

●下一跳为Device C的静态路作为备份路由。

●在Device A上通过静态路由、Track与NQA联动,实时判断主路由是否可达。

当主路由不可达时,备份路由生效,Device A通过Device C将报文转发到30.1.1.0/24网段。

同样地,Device D作为30.1.1.0/24网段内主机的缺省网关,在Device D上存在两条到达20.1.1.0/24网段的静态路由,下一跳分别为Device B和Device C。

这两条静态路由形成备份,其中:●下一跳为Device B的静态路由优先级高,作为主路由。

该路由可达时,Device D通过Device B将报文转发到20.1.1.0/24网段。

●下一跳为Device C的静态路作为备份路由。

●在Device D上通过静态路由、Track与NQA联动,实时判断主路由是否可达。

当主路由不可达时,备份路由生效,Device D通过Device C将报文转发到20.1.1.0/24网段。

2. 组网图图1-2 静态路由、Track与NQA联动配置组网图3. 配置步骤(1)按照图1-2创建VLAN,在VLAN中加入对应的端口,并配置各VLAN接口的IP地址,具体配置过程略。

(2)配置Device A# 配置到达30.1.1.0/24网段的静态路由:下一跳地址为10.1.1.2,优先级为缺省值60,该路由与Track项1关联。

<DeviceA> system-view[DeviceA] ip route-static 30.1.1.0 24 10.1.1.2 track 1# 配置到达30.1.1.0/24网段的静态路由:下一跳地址为10.3.1.3,优先级为80。

[DeviceA] ip route-static 30.1.1.0 24 10.3.1.3 preference 80# 配置到达10.2.1.4的静态路由:下一跳地址为10.1.1.2。

[DeviceA] ip route-static 10.2.1.4 24 10.1.1.2# 创建管理员名为admin、操作标签为test的NQA测试组。

[DeviceA] nqa entry admin test# 配置测试类型为ICMP-echo。

[DeviceA-nqa-admin-test] type icmp-echo# 配置测试的目的地址为10.2.1.4,下一跳地址为10.1.1.2,以便通过NQA检测Device A-Device B-Device D这条路径的连通性。

[DeviceA-nqa-admin-test-icmp-echo] destination ip 10.2.1.4[DeviceA-nqa-admin-test-icmp-echo] next-hop 10.1.1.2# 配置测试频率为100ms。

[DeviceA-nqa-admin-test-icmp-echo] frequency 100# 配置联动项1(连续失败5次触发联动)。

[DeviceA-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only[DeviceA-nqa-admin-test-icmp-echo] quit# 启动探测。

[DeviceA] nqa schedule admin test start-time now lifetime forever# 配置Track项1,关联NQA测试组(管理员为admin,操作标签为test)的联动项1。

[DeviceA] track 1 nqa entry admin test reaction 1(3)配置Device B# 配置到达30.1.1.0/24网段的静态路由:下一跳地址为10.2.1.4。

<DeviceB> system-view[DeviceB] ip route-static 30.1.1.0 24 10.2.1.4# 配置到达20.1.1.0/24网段的静态路由:下一跳地址为10.1.1.1。

[DeviceB] ip route-static 20.1.1.0 24 10.1.1.1(4)配置Device C# 配置到达30.1.1.0/24网段的静态路由:下一跳地址为10.4.1.4。

<DeviceC> system-view[DeviceC] ip route-static 30.1.1.0 24 10.4.1.4# 配置到达20.1.1.0/24网段的静态路由:下一跳地址为10.3.1.1。

[DeviceC] ip route-static 20.1.1.0 24 10.3.1.1(5)配置Device D# 配置到达20.1.1.0/24网段的静态路由:下一跳地址为10.2.1.2,优先级为缺省值60,该路由与Track项1关联。

<DeviceD> system-view[DeviceD] ip route-static 20.1.1.0 24 10.2.1.2 track 1# 配置到达20.1.1.0/24网段的静态路由:下一跳地址为10.4.1.3,优先级为80。

[DeviceD] ip route-static 20.1.1.0 24 10.4.1.3 preference 80# 配置到达10.1.1.1的静态路由:下一跳地址为10.2.1.2。

[DeviceD] ip route-static 10.1.1.1 24 10.2.1.2# 创建管理员名为admin、操作标签为test的NQA测试组。

[DeviceD] nqa entry admin test# 配置测试类型为ICMP-echo。

[DeviceD-nqa-admin-test] type icmp-echo# 配置测试的目的地址为10.1.1.1,下一跳地址为10.2.1.2,以便通过NQA检测Device D-Device B-Device A这条路径的连通性。

[DeviceD-nqa-admin-test-icmp-echo] destination ip 10.1.1.1[DeviceD-nqa-admin-test-icmp-echo] next-hop 10.2.1.2# 配置测试频率为100ms。

[DeviceD-nqa-admin-test-icmp-echo] frequency 100# 配置联动项1(连续失败5次触发联动)。

[DeviceD-nqa-admin-test-icmp-echo] reaction 1 checked-element probe-fail threshold-type consecutive 5 action-type trigger-only[DeviceD-nqa-admin-test-icmp-echo] quit# 启动探测。

[DeviceD] nqa schedule admin test start-time now lifetime forever# 配置Track项1,关联NQA测试组(管理员为admin,操作标签为test)的联动项1。

[DeviceD] track 1 nqa entry admin test reaction 1(6)验证配置结果# 显示Device A上Track项的信息。

[DeviceA] display track allTrack ID: 1Status: PositiveDuration: 0 days 0 hours 2 minutes 14 secondsNotification delay: Positive 0, Negative 0 (in seconds)Reference object:NQA entry: admin testReaction: 1# 显示Device A的路由表。

[DeviceA] display ip routing-tableRouting Tables: PublicDestinations : 10 Routes : 10Destination/Mask Proto Pre Cost NextHop Interface10.1.1.0/24 Direct 0 0 10.1.1.1 Vlan210.1.1.1/32 Direct 0 0 127.0.0.1 InLoop010.2.1.0/24 Static 60 0 10.1.1.2 Vlan210.3.1.0/24 Direct 0 0 10.3.1.1 Vlan310.3.1.1/32 Direct 0 0 127.0.0.1 InLoop020.1.1.0/24 Direct 0 0 20.1.1.1 Vlan620.1.1.1/32 Direct 0 0 127.0.0.1 InLoop030.1.1.0/24 Static 60 0 10.1.1.2 Vlan2127.0.0.0/8 Direct 0 0 127.0.0.1 InLoop0127.0.0.1/32 Direct 0 0 127.0.0.1 InLoop0以上显示信息表示,NQA测试的结果为主路由可达(Track项状态为Positive),Device A通过Device B将报文转发到30.1.1.0/24网段。

# 在Device B上删除VLAN接口2的IP地址。

<DeviceB> system-view[DeviceB] interface vlan-interface 2[DeviceB-Vlan-interface2] undo ip address# 显示Device A上Track项的信息。

相关文档
最新文档