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

H3C V7防火墙在目标IP地址不可达的情况下实现流量切换

2017-08-31 发表
  • 0关注
  • 0收藏 2680浏览
粉丝:24人 关注:0人

 

H3C V7防火墙部署在出口,连接移动和联通的路由器,H3C V7防火墙和运营商路由器之间部署二层交换机,当移动路由器出现故障接口DOWNH3C V7防火墙无法感知接口仍然UP,无法实现切换。本案例讲述track结合nqa探测实现切换:

1)当FW1的接口G1/0/21.0.0.2)和目标IP地址1.0.0.1不可达的情况下,流量发生切换,走FW2

2)当故障消除,FW1的接口G1/0/21.0.0.2)和目标IP地址1.0.0.1可达的情况下,流量回切,走FW1


接口配置、安全域、域间策略等基础配置不再累述,关键配置如下:

#创建ICMP-echo类型的NQA测试组(管理员为yhy,操作标签为123),并配置探测报文的目的地址为1.0.0.1,建立联动项。

<H3C>system-view

[H3C]nqa entry yhy 123

[H3C-nqa-yhy-123] type icmp-echo

[H3C-nqa-yhy-123-icmp-echo]destination ip 1.0.0.1

[H3C-nqa-yhy-123-icmp-echo]frequency 1000

[H3C-nqa-yhy-123-icmp-echo]next-hop ip 1.0.0.1

[H3C-nqa-yhy-123-icmp-echo]reaction 1 checked-element probe-fail threshold-type consecutive 1 action-type trigger-only

[H3C-nqa-yhy-123-icmp-echo]quit

# 启动ICMP-echo测试操作,并一直进行测试。

[H3C]nqa schedule yhy 123 start-time now lifetime forever

 

#配置Track,监测上、下行接口的状态,track2关联nqa探测项

[H3C]track 1 interface GigabitEthernet1/0/1 physical

[H3C]track 2 nqa entry yhy 123 reaction 1

[H3C]track 3 interface GigabitEthernet2/0/1 physical

[H3C]track 4 interface GigabitEthernet2/0/2 physical

 

#配置冗余组

[H3C]redundancy group aaa

#创建Node 1Node 1FW1绑定,为主节点,成员接口为GE1/0/1GE1/0/2。关联的Track项为12

[H3C-redundancy-group-aaa]node 1

[H3C-redundancy-group-aaa-node-1]bind slot 1

[H3C-redundancy-group-aaa-node-1]priority 100

[H3C-redundancy-group-aaa-node-1]track 1 interface GigabitEthernet1/0/1

[H3C-redundancy-group-aaa-node-1]track 2 interface GigabitEthernet1/0/2

[H3C-redundancy-group-aaa-node-1]node-member interface GigabitEthernet1/0/1

[H3C-redundancy-group-aaa-node-1]node-member interface GigabitEthernet1/0/2

[H3C-redundancy-group-aaa-node-1]quit

#创建Node 2Node 2FW2绑定,为主节点,成员接口为GE2/0/1GE2/0/2。关联的Track项为34

[H3C-redundancy-group-aaa]node 2

[H3C-redundancy-group-aaa-node-2]bind slot 2

[H3C-redundancy-group-aaa-node-2]priority 50

[H3C-redundancy-group-aaa-node-2]track 3 interface GigabitEthernet2/0/1

[H3C-redundancy-group-aaa-node-2]track 4 interface GigabitEthernet2/0/2

[H3C-redundancy-group-aaa-node-2]node-member interface GigabitEthernet2/0/1

[H3C-redundancy-group-aaa-node-2]node-member interface GigabitEthernet2/0/2

[H3C-redundancy-group-aaa-node-2]quit

 

测试步骤:

1)和目标IP 1.0.0.1 可达

<H3C>ping 1.0.0.1  //和目标IP 1.0.0.1 可达

Ping 1.0.0.1 (1.0.0.1): 56 data bytes, press CTRL_C to break

56 bytes from 1.0.0.1: icmp_seq=0 ttl=255 time=1.109 ms

56 bytes from 1.0.0.1: icmp_seq=1 ttl=255 time=0.979 ms

56 bytes from 1.0.0.1: icmp_seq=2 ttl=255 time=0.975 ms

56 bytes from 1.0.0.1: icmp_seq=3 ttl=255 time=0.767 ms

56 bytes from 1.0.0.1: icmp_seq=4 ttl=255 time=0.997 ms

--- Ping statistics for 1.0.0.1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.767/0.965/1.109/0.111 ms

 

<H3C>dis track all 

Track ID: 1

  State: Positive

  Duration: 0 days 0 hours 0 minutes 18 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet1/0/1

    Protocol: None

Track ID: 2

  State: Positive   // track2Positive

  Duration: 0 days 0 hours 0 minutes 21 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    NQA entry: yhy 123

    Reaction: 1

    Remote IP/URL: 1.0.0.1                                                     

    Local IP: --                                                         

    Interface: --

Track ID: 3

  State: Positive

  Duration: 0 days 1 hours 18 minutes 14 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet2/0/1

    Protocol: None

Track ID: 4

  State: Positive

  Duration: 0 days 1 hours 7 minutes 45 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet2/0/2

Protocol: None

 

<H3C>display redundancy group

Redundancy group aaa (ID 1):

  Node ID      Slot          Priority   Status        Track weight

  1            Slot1         100        Primary       255 

  2            Slot2         50         Secondary     255

 

Preempt delay time remained     : 0    min

Preempt delay timer setting     : 1    min

Remaining hold-down time        : 0    sec

Hold-down timer setting         : 1    sec

Manual switchover request       : No

 

Member interfaces:

 

Node 1:

  Node member     Physical status

    GE1/0/1       UP

    GE1/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    1        Positive     255                GE1/0/1

    2        Positive     255                GE1/0/2

Node 2:

  Node member     Physical status

    GE2/0/1       UP

    GE2/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    3        Positive     255                GE2/0/1

    4        Positive     255                GE2/0/2

 

2)和目标IP 1.0.0.1 不可达,流量切换

<H3C>ping 1.0.0.1    //和目标IP 1.0.0.1 不可达

Ping 1.0.0.1 (1.0.0.1): 56 data bytes, press CTRL_C to break

Request time out

Request time out

Request time out

--- Ping statistics for 1.0.0.1 ---

4 packet(s) transmitted, 0 packet(s) received, 100.0% packet loss

 

*Aug 23 21:38:21:859 2017 H3C NQA/7/Event: -COntext=1; NQA entry (yhy-123): Probe timed out.

*Aug 23 21:38:21:860 2017 H3C NQA/7/Reaction: -COntext=1; NQA entry (yhy-123) reaction (1): Status changed from below-threshold to over-threshold.

*Aug 23 21:38:21:860 2017 H3C NQA/7/Reaction: -COntext=1; NQA entry (yhy-123) reaction (1): Trigger notified.

%Aug 23 21:38:21:864 2017 H3C RDDC/5/RDDC_ACTIVENODE_CHANGE: -COntext=1; Redundancy group aaa active node changed to node 2 (slot 2), because of node&#39;s weight changed.  //冗余组切换到node2

%Aug 23 21:38:21:908 2017 H3C IFNET/3/PHY_UPDOWN: -COntext=1; Physical state on the interface GigabitEthernet1/0/1 changed to down.  //联动下行口DOWN

%Aug 23 21:38:21:908 2017 H3C IFNET/5/LINK_UPDOWN: -COntext=1; Line protocol state on the interface GigabitEthernet1/0/1 changed to down.

 

 

<H3C>dis track all

Track ID: 1

  State: Negative

  Duration: 0 days 0 hours 0 minutes 43 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet1/0/1

    Protocol: None

Track ID: 2

  State: Negative   // track2Negative

  Duration: 0 days 0 hours 0 minutes 43 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    NQA entry: yhy 123

    Reaction: 1

    Remote IP/URL: 1.0.0.1                                                    

    Local IP: --                                                         

    Interface: --

Track ID: 3

  State: Positive

  Duration: 0 days 1 hours 16 minutes 41 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet2/0/1

    Protocol: None

Track ID: 4

  State: Positive

  Duration: 0 days 1 hours 6 minutes 12 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet2/0/2

    Protocol: None

 

<H3C>

*Aug 23 21:38:25:859 2017 H3C NQA/7/Event: -COntext=1; NQA entry (yhy-123): Probe timed out.

*Aug 23 21:38:29:859 2017 H3C NQA/7/Event: -COntext=1; NQA entry (yhy-123): Probe timed out.

*Aug 23 21:38:33:859 2017 H3C NQA/7/Event: -COntext=1; NQA entry (yhy-123): Probe timed out.

<H3C>display redundancy group

Redundancy group aaa (ID 1):

  Node ID      Slot          Priority   Status        Track weight

  1            Slot1         100        Secondary    -255 //权值改变,状态切换成功

  2            Slot2         50         Primary      255

 

Preempt delay time remained     : 0    min

Preempt delay timer setting     : 1    min

Remaining hold-down time        : 0    sec

Hold-down timer setting         : 1    sec

Manual switchover request       : No

 

Member interfaces:

 

Node 1:

  Node member     Physical status

    GE1/0/1       DOWN(redundancy down)  //联动下行口DOWN

    GE1/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    1        Negative     255                GE1/0/1

    2        Negative     255                GE1/0/2(Fault)  //故障口

Node 2:

  Node member     Physical status

    GE2/0/1       UP

    GE2/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    3        Positive     255                GE2/0/1

    4        Positive     255                GE2/0/2

 

<H3C>debug ip icmp

This command is CPU intensive and might affect ongoing services. Are you sure you want to continue? [Y/N]:Y

<H3C>

*Aug 23 21:39:42:852 2017 H3C SOCKET/7/ICMP: -COntext=1;  

ICMP Output:   //发出请求,但是未回应

 ICMP Packet: src = 1.0.0.2, dst = 1.0.0.1

              type = 8, code = 0 (echo)

*Aug 23 21:39:46:852 2017 H3C SOCKET/7/ICMP: -COntext=1;

ICMP Output:

 ICMP Packet: src = 1.0.0.2, dst = 1.0.0.1

              type = 8, code = 0 (echo)

 

3)和目标IP 1.0.0.1 恢复成可达状态,流量回切

<H3C>ping 1.0.0.1  //IP 1.0.0.1 恢复可达

Ping 1.0.0.1 (1.0.0.1): 56 data bytes, press CTRL_C to break

56 bytes from 1.0.0.1: icmp_seq=0 ttl=255 time=1.109 ms

56 bytes from 1.0.0.1: icmp_seq=1 ttl=255 time=0.979 ms

56 bytes from 1.0.0.1: icmp_seq=2 ttl=255 time=0.975 ms

56 bytes from 1.0.0.1: icmp_seq=3 ttl=255 time=0.767 ms

56 bytes from 1.0.0.1: icmp_seq=4 ttl=255 time=0.997 ms

 

--- Ping statistics for 1.0.0.1 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 0.767/0.965/1.109/0.111 ms

 

*Aug 23 21:40:15:869 2017 H3C NQA/7/Event: -COntext=1; NQA entry (yhy-123): Probe timed out.

*Aug 23 21:40:16:866 2017 H3C NQA/7/Reaction: -COntext=1; NQA entry (yhy-123) reaction (1): Status changed from over-threshold to below-threshold.

*Aug 23 21:40:16:866 2017 H3C NQA/7/Reaction: -COntext=1; NQA entry (yhy-123) reaction (1): Trigger notified.

%Aug 23 21:40:20:017 2017 H3C IFNET/3/PHY_UPDOWN: -COntext=1; Physical state on the interface GigabitEthernet1/0/1 changed to up. //联动下行口UP

%Aug 23 21:40:20:017 2017 H3C IFNET/5/LINK_UPDOWN: -COntext=1; Line protocol state on the interface GigabitEthernet1/0/1 changed to up.

 

<H3C>display track all 

Track ID: 1

  State: Positive

  Duration: 0 days 0 hours 0 minutes 18 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet1/0/1

    Protocol: None

Track ID: 2

  State: Positive  //track2状态变为Positive

  Duration: 0 days 0 hours 0 minutes 21 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    NQA entry: yhy 123

    Reaction: 1

    Remote IP/URL: 1.0.0.1                                                     

    Local IP: --                                                         

    Interface: --

Track ID: 3

  State: Positive

  Duration: 0 days 1 hours 18 minutes 14 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet2/0/1

    Protocol: None

Track ID: 4

  State: Positive

  Duration: 0 days 1 hours 7 minutes 45 seconds

  Notification delay: Positive 0, Negative 0 (in seconds)

  Tracked object:

    Interface: GigabitEthernet2/0/2

    Protocol: None

 

<H3C>display redundancy group

Redundancy group aaa (ID 1):

  Node ID      Slot          Priority   Status        Track weight

  1            Slot1         100        Secondary   255  //权值正常,状态暂未切换

  2            Slot2         50         Primary     255

 

Preempt delay time remained     : 1    min

Preempt delay timer setting     : 1    min

Remaining hold-down time        : 0    sec

Hold-down timer setting         : 1    sec

Manual switchover request       : No

 

Member interfaces:

 

Node 1:

  Node member     Physical status

    GE1/0/1       UP

    GE1/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    1        Positive     255                GE1/0/1

    2        Positive     255                GE1/0/2

Node 2:

  Node member     Physical status

    GE2/0/1       UP

    GE2/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    3        Positive     255                GE2/0/1

    4        Positive     255                GE2/0/2

 

<H3C>

%Aug 23 21:41:17:671 2017 H3C RDDC/5/RDDC_ACTIVENODE_CHANGE: -COntext=1; Redundancy group aaa active node changed to node 1 (slot 1), because of node&#39;s weight changed.  //冗余组回切成功

<H3C>display redundancy group

Redundancy group aaa (ID 1):

  Node ID      Slot          Priority   Status        Track weight

  1            Slot1         100        Primary       255   //状态切换成功

  2            Slot2         50         Secondary     255

 

Preempt delay time remained     : 0    min

Preempt delay timer setting     : 1    min

Remaining hold-down time        : 0    sec

Hold-down timer setting         : 1    sec

Manual switchover request       : No

 

Member interfaces:

 

Node 1:

  Node member     Physical status

    GE1/0/1       UP

    GE1/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    1        Positive     255                GE1/0/1

    2        Positive     255                GE1/0/2

Node 2:

  Node member     Physical status

    GE2/0/1       UP

    GE2/0/2       UP

  Track info:

    Track    Status       Reduced weight     Interface

    3        Positive     255                GE2/0/1

4        Positive     255                GE2/0/2

 


1NQA一定要配置正确,要记得启动ICMP-echo测试操作;

2track项要调用nqa探测项,而track 1 interface GigabitEthernet1/0/1 protocol ipv4监控的是本设备接口状态,无法监控对端设备的接口状态。


该案例对您是否有帮助:

您的评价:1

若您有关于案例的建议,请反馈:

作者在2019-06-12对此案例进行了修订
0 个评论

该案例暂时没有网友评论

编辑评论

举报

×

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

侵犯我的权益

×

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

泄露了我的隐私

×

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

侵犯了我企业的权益

×

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

抄袭了我的内容

×

原文链接或出处

诽谤我

×

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

对根叔知了社区有害的内容

×

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

不规范转载

×

举报说明

提出建议

    +

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

确定

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

注册后可访问此模块

跳转hclhub

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