• 全部
  • 经验案例
  • 典型配置
  • 技术公告
  • FAQ
  • 全部
  • 全部
产品线
搜索
取消
案例类型
发布者
是否解决
是否官方
时间
高级搜索

Announcement on the loss of Leaf switch configuration caused by the disconnection between Spine and Leaf in the automation scenario of the ADCampus Phase III B02 solution

2020-06-16发表
  • 0关注
  • 0收藏,65浏览
孟普 五段
粉丝:0人 关注:0人

问题描述



Product model
H3C ADCampus solution


 


Related version


 


Any of the following switch versions or Director software version in the H3C ADCampus Phase III B02 solution automation scenario.


 


1) Version before R7585 (excluding R7585) of S12500S, S10500X, S10500, S7500X, S7500E, S7500E-XS, S7500E-X, S7600-X, S7600 series switches.


2) Version before R6308 (excluding R6308) of S5560X, S6520X-HI, S6520X-EI series switches.


3) Version before E0508P06 (excluding E0508P06) of Director 2000.


 


Problem Description


In the automation scenario of the ADCampus Phase III B02 solution, When Spine switch automation is running normally and Leaf automation is suspended, the following two situations occur during the normal operation of the switch automation of the entire network:


  1. Reboot the Spine switch

  2. Interconnect interface of Spine to Leaf being DOWN / UP.


 


For any of the above two situations, the Leaf device may lose the following configuration:


 


  1. Global interconnect VLAN configuration of Leaf;

  2. Related VLAN permission configuration of Leaf uplink;

  3. Interconnect VLAN-interface and its IP address configuration.



原因分析

Root Cause

The Leaf switch actively deletes the device configuration in response to the change of the status information of its interface, resulting in the loss of this Leaf configuration. Even if the Leaf switch suspends its own automation process, it will still trigger this configuration loss problem.

 


规避措施/解决方案

Avoidance measures

After such a fault occurs, it is recommended to immediately reboot the Leaf that cannot communicate normally to restore the configuration.

 

Solution

In the automation scenario of the ADCampus Phase III B02 solution, for the site where the software version of the field switch is in [Related Version], when upgrading any switch version, the following steps should be followed:

Step 1: Check the settings of the automatic template _white_list_check  on the Spine device.

  1. If it is True, you need to perform the following modification operations on Spine before performing the second and third steps.

  2. If it is False, you can proceed directly to the second and third steps.

 

Regarding the modification operations performed before Spine upgrade, when the automation template _white_list_check is True, the solution steps are as follows:

  1. Log in to the Director server, enter {Director installation directory}/iMC/server/tmp, find the 546_Spine.template configuration template file, and manually modify the template _white_list_check = False. The modified template should be a template with a normal [Enter symbol]. If you lose the [Enter symbol], please reconfigure.

  2. Log in to the Spine device and execute the download template command, and confirm that the new template field has taken effect.

    <Spine-203.126> tftp 172.31.203.4 get 546_spine.template flash:/546_spine.template  vpn-instance vpn-default.

    <Spine-203.126>more 546_spine.template

    As shown below:

    https://zhiliao.h3c.com/uploads/t/20200603/15911658994420.png

 

Step 2: Stop the entire network automation process on the Director2000 controller.

Step 3: Upgrade all switches with reference to the version matching the latest solution. And follow the upgrade order of Access device, then Leaf device, and finally Spine device. If you do not have a network-wide upgrade plan or cannot follow a fixed upgrade sequence, you must submit a network changing flow in advance to evaluate the feasibility.

 

Step 4: Turn on the automation function as needed. If there is a site that needs to use the automatic whitelist function in the future, please consult the ADNET Solution Support Department for a detailed change plan.

0 个评论

该案例暂时没有网友评论

编辑评论

举报

×

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

侵犯我的权益

×

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

泄露了我的隐私

×

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

侵犯了我企业的权益

×

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

抄袭了我的内容

×

原文链接或出处

诽谤我

×

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

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

×

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

不规范转载

×

举报说明

提出建议

    +
<

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

确定

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