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
- 0关注
- 0收藏 2467浏览
Problem Description
【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:
Reboot the Spine switch
Interconnect interface of Spine to Leaf being DOWN / UP.
For any of the above two situations, the Leaf device may lose the following configuration:
Global interconnect VLAN configuration of Leaf;
Related VLAN permission configuration of Leaf uplink;
Interconnect VLAN-interface and its IP address configuration.
Cause Analysis
【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.
Circumvention measures/solutions
【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.
If it is True, you need to perform the following modification operations on Spine before performing the second and third steps.
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:
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.
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:
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.
No comments
Add Comments:
✖
案例意见反馈
亲~登录后才可以操作哦!
确定你的邮箱还未认证，请认证邮箱或绑定手机后进行当前操作