• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 漏洞说明
  • 全部
  • 全部
  • 大数据引擎
  • 知了引擎
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
搜索引擎
匹配模式
高级搜索

msr-3600s做双网热备,但是不能自动切换。

1天前提问
  • 0关注
  • 0收藏,42浏览
粉丝:0人 关注:0人

问题描述:

 

msr-3600s做双网热备,但是不能自动切换。

https://github.com/CWVAFM

https://github.com/CWVAFM/sfdwe

https://github.com/CWVAFM/wre1987

https://github.com/CWVAFM/ewewoo

https://github.com/CWVAFM/baidu121

https://github.com/CWVAFM/windowsess

https://github.com/CWVAFM/ewewoo/issues

https://github.com/CWVAFM/sfdwe/issues

https://github.com/CWVAFM/wre1987/issues

https://github.com/CWVAFM/ewewoo/issues

https://github.com/CWVAFM/baidu121/issues

https://github.com/CWVAFM/windowsess/issues

https://github.com/3w5yflm01

https://github.com/3w5yflm01/fe

https://github.com/3w5yflm01/00

https://github.com/3w5yflm01/110

https://github.com/3w5yflm01/x1

https://github.com/3w5yflm01/v49

https://github.com/3w5yflm01/520

https://github.com/3w5yflm01/fe/issues

https://github.com/3w5yflm01/00/issues

https://github.com/3w5yflm01/110/issues

https://github.com/3w5yflm01/x1/issues

https://github.com/3w5yflm01/v49/issues

https://github.com/3w5yflm01/520/issues

https://github.com/TheodoreRitaify

https://github.com/TheodoreRitaify/Irvingsuxiliu

https://github.com/TheodoreRitaify/baidu

https://github.com/TheodoreRitaify/sddeef

https://github.com/TheodoreRitaify/suhou

https://github.com/TheodoreRitaify/feiji

https://github.com/TheodoreRitaify/Irvingsuxiliu/issues

https://github.com/TheodoreRitaify/baidu/issues

https://github.com/TheodoreRitaify/sddeef/issues

https://github.com/TheodoreRitaify/suhou/issues

https://github.com/TheodoreRitaify/feiji/issues

https://github.com/TheodoreRitaify/vs9/issues

https://github.com/BridgesSetlladvz

https://github.com/BridgesSetlladvz/Gibbonyuezhaixu/issues

https://github.com/BridgesSetlladvz/s90/issues

https://github.com/TheodoreRitaify/a29/issues/580

https://github.com/TheodoreRitaify/a29/issues/581

https://github.com/TheodoreRitaify/a29/issues/582

https://github.com/TheodoreRitaify/a29/issues/583

https://github.com/TheodoreRitaify/a29/issues/584

https://github.com/TheodoreRitaify/a29/issues/585

https://github.com/TheodoreRitaify/a29/issues/586

https://github.com/TheodoreRitaify/a29/issues/587

https://github.com/TheodoreRitaify/a29/issues/588

https://github.com/TheodoreRitaify/a29/issues/589

https://github.com/TheodoreRitaify/a29/issues/590

https://github.com/TheodoreRitaify/a29/issues/591

https://github.com/TheodoreRitaify/a29/issues/592

https://github.com/TheodoreRitaify/a29/issues/593

https://github.com/TheodoreRitaify/a29/issues/594

https://github.com/TheodoreRitaify/a29/issues/595

https://github.com/TheodoreRitaify/a29/issues/596

https://github.com/TheodoreRitaify/a29/issues/597

https://github.com/TheodoreRitaify/a29/issues/598

https://github.com/TheodoreRitaify/a29/issues/599

https://github.com/TheodoreRitaify/a29/issues/600

https://github.com/TheodoreRitaify/a29/issues/601

https://github.com/TheodoreRitaify/a29/issues/602

https://github.com/TheodoreRitaify/a29/issues/603

https://github.com/TheodoreRitaify/a29/issues/604

https://github.com/TheodoreRitaify/a29/issues/605

https://github.com/TheodoreRitaify/a29/issues/606

https://github.com/TheodoreRitaify/a29/issues/607

https://github.com/TheodoreRitaify/a29/issues/608

https://github.com/TheodoreRitaify/a29/issues/609

https://github.com/TheodoreRitaify/a29/issues/610

https://github.com/TheodoreRitaify/a29/issues/611

https://github.com/TheodoreRitaify/a29/issues/612

https://github.com/TheodoreRitaify/a29/issues/613

https://github.com/TheodoreRitaify/a29/issues/614

https://github.com/TheodoreRitaify/a29/issues/615

https://github.com/TheodoreRitaify/a29/issues/616

https://github.com/TheodoreRitaify/a29/issues/617

https://github.com/TheodoreRitaify/a29/issues/618

https://github.com/TheodoreRitaify/a29/issues/619

https://github.com/TheodoreRitaify/a29/issues/620

https://github.com/TheodoreRitaify/a29/issues/621

https://github.com/TheodoreRitaify/a29/issues/622

https://github.com/TheodoreRitaify/a29/issues/623

https://github.com/TheodoreRitaify/a29/issues/624

https://github.com/TheodoreRitaify/a29/issues/625

https://github.com/TheodoreRitaify/a29/issues/626

https://github.com/TheodoreRitaify/a29/issues/627

https://github.com/TheodoreRitaify/a29/issues/628

https://github.com/TheodoreRitaify/a29/issues/629

https://github.com/TheodoreRitaify/a29/issues/630

https://github.com/TheodoreRitaify/a29/issues/631

https://github.com/TheodoreRitaify/a29/issues/632

https://github.com/TheodoreRitaify/a29/issues/633

https://github.com/TheodoreRitaify/a29/issues/634

https://github.com/TheodoreRitaify/a29/issues/635

https://github.com/TheodoreRitaify/a29/issues/636

https://github.com/TheodoreRitaify/a29/issues/637

https://github.com/TheodoreRitaify/a29/issues/638

https://github.com/TheodoreRitaify/a29/issues/639

https://github.com/TheodoreRitaify/a29/issues/640

https://github.com/TheodoreRitaify/a29/issues/641

https://github.com/TheodoreRitaify/a29/issues/642

https://github.com/TheodoreRitaify/a29/issues/643

https://github.com/TheodoreRitaify/a29/issues/644

https://github.com/TheodoreRitaify/a29/issues/645

https://github.com/TheodoreRitaify/a29/issues/646

https://github.com/TheodoreRitaify/a29/issues/647

https://github.com/TheodoreRitaify/a29/issues/648

https://github.com/TheodoreRitaify/a29/issues/649

https://github.com/TheodoreRitaify/a29/issues/650

https://github.com/TheodoreRitaify/a29/issues/651

https://github.com/TheodoreRitaify/a29/issues/652

https://github.com/TheodoreRitaify/a29/issues/653

https://github.com/TheodoreRitaify/a29/issues/654

https://github.com/TheodoreRitaify/a29/issues/655

https://github.com/TheodoreRitaify/a29/issues/656

https://github.com/TheodoreRitaify/a29/issues/657

https://github.com/TheodoreRitaify/a29/issues/658

https://github.com/TheodoreRitaify/a29/issues/659

https://github.com/TheodoreRitaify/a29/issues/660

https://github.com/TheodoreRitaify/a29/issues/661

https://github.com/TheodoreRitaify/a29/issues/662

https://github.com/TheodoreRitaify/a29/issues/663

https://github.com/TheodoreRitaify/a29/issues/664

https://github.com/TheodoreRitaify/a29/issues/665

https://github.com/TheodoreRitaify/a29/issues/666

https://github.com/TheodoreRitaify/a29/issues/667

https://github.com/TheodoreRitaify/a29/issues/668

https://github.com/TheodoreRitaify/a29/issues/669

https://github.com/TheodoreRitaify/a29/issues/670

https://github.com/TheodoreRitaify/a29/issues/671

https://github.com/TheodoreRitaify/a29/issues/672

https://github.com/TheodoreRitaify/a29/issues/673

https://github.com/TheodoreRitaify/a29/issues/674

https://github.com/TheodoreRitaify/a29/issues/675

https://github.com/TheodoreRitaify/a29/issues/676

https://github.com/TheodoreRitaify/a29/issues/677

https://github.com/TheodoreRitaify/a29/issues/678

https://github.com/TheodoreRitaify/a29/issues/679

https://github.com/TheodoreRitaify/a29/issues/680

https://github.com/TheodoreRitaify/a29/issues/681

https://github.com/TheodoreRitaify/a29/issues/682

https://github.com/TheodoreRitaify/a29/issues/683

https://github.com/TheodoreRitaify/a29/issues/684

https://github.com/TheodoreRitaify/a29/issues/685

https://github.com/TheodoreRitaify/a29/issues/686

https://github.com/TheodoreRitaify/a29/issues/687

https://github.com/TheodoreRitaify/a29/issues/688

https://github.com/TheodoreRitaify/a29/issues/689

https://github.com/TheodoreRitaify/a29/issues/690

https://github.com/TheodoreRitaify/a29/issues/691

https://github.com/TheodoreRitaify/a29/issues/692

https://github.com/TheodoreRitaify/a29/issues/693

https://github.com/TheodoreRitaify/a29/issues/694

https://github.com/TheodoreRitaify/a29/issues/695

https://github.com/TheodoreRitaify/a29/issues/696

https://github.com/TheodoreRitaify/a29/issues/697

https://github.com/TheodoreRitaify/a29/issues/698

https://github.com/TheodoreRitaify/a29/issues/699

https://github.com/TheodoreRitaify/a29/issues/700

https://github.com/TheodoreRitaify/a29/issues/701

https://github.com/TheodoreRitaify/a29/issues/702

https://github.com/TheodoreRitaify/a29/issues/703

https://github.com/TheodoreRitaify/a29/issues/704

https://github.com/TheodoreRitaify/a29/issues/705

https://github.com/TheodoreRitaify/a29/issues/706

https://github.com/TheodoreRitaify/a29/issues/707

https://github.com/TheodoreRitaify/a29/issues/708

https://github.com/TheodoreRitaify/a29/issues/709

https://github.com/TheodoreRitaify/a29/issues/710

https://github.com/TheodoreRitaify/a29/issues/711

https://github.com/TheodoreRitaify/a29/issues/712

https://github.com/TheodoreRitaify/a29/issues/713

https://github.com/TheodoreRitaify/a29/issues/714

https://github.com/TheodoreRitaify/a29/issues/715

https://github.com/TheodoreRitaify/a29/issues/716

https://github.com/TheodoreRitaify/a29/issues/717

https://github.com/TheodoreRitaify/a29/issues/718

https://github.com/TheodoreRitaify/a29/issues/719

https://github.com/TheodoreRitaify/a29/issues/720

https://github.com/TheodoreRitaify/a29/issues/721

https://github.com/TheodoreRitaify/a29/issues/722

https://github.com/TheodoreRitaify/a29/issues/723

https://github.com/TheodoreRitaify/a29/issues/724

https://github.com/TheodoreRitaify/a29/issues/725

https://github.com/TheodoreRitaify/a29/issues/726

https://github.com/TheodoreRitaify/a29/issues/727

https://github.com/TheodoreRitaify/a29/issues/728

https://github.com/TheodoreRitaify/a29/issues/729

https://github.com/TheodoreRitaify/a29/issues/730

https://github.com/TheodoreRitaify/a29/issues/731

https://github.com/TheodoreRitaify/a29/issues/732

https://github.com/TheodoreRitaify/a29/issues/733

https://github.com/TheodoreRitaify/a29/issues/734

https://github.com/TheodoreRitaify/a29/issues/735

https://github.com/TheodoreRitaify/a29/issues/736

https://github.com/TheodoreRitaify/a29/issues/737

https://github.com/TheodoreRitaify/a29/issues/738

https://github.com/TheodoreRitaify/a29/issues/739

https://github.com/TheodoreRitaify/a29/issues/740

https://github.com/TheodoreRitaify/a29/issues/741

https://github.com/TheodoreRitaify/a29/issues/742

3 个回答
粉丝:8人 关注:0人

MSR3600系列路由器做双网热备无法自动切换,最常见的原因是:虽然配置了两条默认路由,但没有配置链路检测机制(如NQA联动Track),或者配置了但Track检测状态没有正确联动路由。

一、问题原因分析

你的描述很关键:“联通出问题了,没有外网,然后所有网没有自动切换”。根据H3C设备的运行机制,出现这种情况通常有以下几种可能:

可能原因说明排查方法
链路检测机制缺失只配置了两条静态路由,但未配置NQA/BFD检测,设备认为物理接口UP就是正常,不会自动切换检查是否配置了track和nqa
Track联动未生效配置了NQA但Track状态变化没有触发路由切换display track 查看状态
路由优先级配置问题两条路由优先级相同,形成了负载分担而不是主备display ip routing-table 查看
接口物理状态问题联通线路接口没有down,但运营商侧已经断网display interface 查看
RBM热备配置问题如果是两台设备做热备,可能主备设备配置未同步display remote-backup-group status


二、快速排查命令

登录到MSR3600路由器,执行以下命令检查当前状态:

# 1. 查看当前路由表,确认默认路由情况
display ip routing-table | include 0.0.0.0 
 # 2. 查看Track项状态(如果配置了NQA联动) 
display track all 
 # 3. 查看接口状态 
display interface brief | include up 
 # 4. 查看NQA探测结果 
display nqa result
三、解决方案(两种方式)

方案一:NQA联动Track + 主备静态路由(推荐)

这是最常用、最稳定的双出口主备切换方案。核心思路:通过NQA持续检测主链路(联通)的连通性,一旦检测失败,自动撤销主路由,让备用路由(电信)生效。

完整配置步骤

# 1. 进入系统视图
system-view 
 # 2. 配置接口IP和NAT(假设已配置好,省略) 
 # 3. 创建NQA测试组,检测联通线路网关连通性 
nqa entry admin liantong type icmp-echo 
# 配置检测目标(联通线路的网关地址,假设为100.0.0.1) 
destination ip 100.0.0.1 
# 检测频率:3秒一次 
frequency 3000 
# 配置联动条件:连续3次失败触发 
reaction 1 checked-element probe-fail threshold-type consecutive 3 action-type trigger-only 
quit 
 # 4. 启动NQA测试 
nqa schedule admin liantong start-time now lifetime forever 
 # 5. 创建Track项关联NQA 
track 1 nqa entry admin liantong reaction 1 
 # 6. 配置主路由(联通),优先级60,联动Track 1 
ip route-static 0.0.0.0 0.0.0.0 100.0.0.1 track 1 
 # 7. 配置备用路由(电信),优先级80(数值越大优先级越低) 
ip route-static 0.0.0.0 0.0.0.0 200.0.0.1 preference 80 
 # 8. 保存配置 
save force
验证方法
# 正常情况下,Track 1状态应为Positive
display track 1 
 # 路由表只有主路由生效 
display ip routing-table | include 0.0.0.0 
 # 拔掉联通线路或断开网关后,Track 1状态变为Negative 
# 路由表切换为备用路由(preference 80) 
关键点:NQA检测的目标建议配置为运营商网关地址公网DNS地址(如114.114.114.114),而不是对端设备的接口IP。这样可以检测到运营商层面的网络故障


方案二:RBM热备(两台MSR做设备级热备)

如果你有两台MSR3600做热备(一台主用一台备用),需要使用RBM(Remote Backup Management)功能。

但需要注意:根据H3C官方资料,MSR3600系列不是所有型号都支持RBM热备

型号RBM支持情况
MSR3600-28, MSR3600-51 不支持
MSR3600-28-SI, MSR3600-51-SI 不支持
MSR3600-28-X1, MSR3600-51-X1 不支持
MSR3600-28-G-DP, MSR3600-51-G-DP 不支持
MSR3610, MSR3620, MSR3640, MSR3660 支持

如果你的设备支持RBM,可以参考以下配置要点:

# 创建RBM组
remote-backup group # 配置双活模式(两台同时处理业务)或主备模式 backup-mode dual-active # 启用配置自动同步 configuration auto-sync enable # 配置主设备IP和备用设备IP peer ip 10.0.0.1 peer ip 10.0.0.2如果RBM配置后无法切换,需要检查:
  1. 配置是否自动同步成功:display remote-backup-group sync-check

  2. 主备状态是否正确:display remote-backup-group status

  3. 是否配置了路由开销调整:adjust-cost ospf enable absolute 60000



四、你的情况适用哪种方案?

根据你描述的“一条联通、一条电信”的场景:

  • 如果你只有一台MSR3600 → 使用方案一(NQA联动Track)

  • 如果你有两台MSR3600做热备 → 先确认设备型号是否支持RBM,如果支持则用方案二


暂无评论

粉丝:3人 关注:14人

具体网络架构是什么?怎么配置的?

暂无评论

粉丝:2人 关注:9人

双网热备不能自动切换,通常涉及备份组状态、接口跟踪或路由问题。请按以下步骤排查:

1. 检查备份组状态
display vrrp brief
确认主备设备的VRRP组状态是否正确(Master/Backup),虚拟IP地址是否一致。

2. 检查接口跟踪
display vrrp
查看`Track`信息。如果配置了接口跟踪,确认被跟踪的上行接口(如拨号接口)物理及协议状态是否为`UP`。如果被跟踪接口`DOWN`但备份组未切换,检查跟踪配置:
interface Vlan-interface X
vrrp vrid X track interface Dialer X reduced Y

3. 检查上行接口
对于PPPoE拨号,检查Dialer接口状态:
display interface Dialer X
确认获得IP地址且链路协议为`UP`。检查物理接口(如G0/0)状态。

4. 检查路由
在主设备上,确认存在指向上行接口的默认路由(如`ip route-static 0.0.0.0 Dialer X`)。如果使用动态路由,检查路由表是否正常。

需要您补充的信息:
- 当前VRRP和接口跟踪的具体配置。
- `display vrrp`和`display interface Dialer X`的输出结果。
- 网络拓扑,特别是上行链路连接方式。

暂无评论

编辑答案

你正在编辑答案

如果你要对问题或其他回答进行点评或询问,请使用评论功能。

分享扩散:

提出建议

    +

亲~登录后才可以操作哦!

确定

亲~检测到您登陆的账号未在http://hclhub.h3c.com进行注册

注册后可访问此模块

跳转hclhub

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作

举报

×

侵犯我的权益 >
对根叔社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 pub.zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到pub.zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明