10-24-2022 11:26 PM
We have a multi EAPS ring. What is the best practise how to upgrade the swtiches to prevent to create a loop?
11-04-2022 07:44 AM
Ok, so the shared port(s) are not connected to the EAPS master(s)? If you upgrade within a major EXOS release, I believe you should be fine (within EXOS 30.x for instance), but bigger hops may be troublesome. I would get some advice from the TAC in that case. As a baseline, upgrade everything to the latest in the master release (latest 22.x if you're on EXOS 22) and then upgrade to the latest in the next step (30.x in that case) and so on until you reach the desired release. Landing on the latest in each subsequent major release will give you maximum feature parity with the next major release.
If you want to play it safe, disable ports so no loops can occur when a switch is rebooted. You will lack redundancy anyway during the reboot. Do the disable port in an adjacent switch, not in the switch being rebooted. Also disable a strategic port in the second ring as well while rebooting the switches in the first one and vice versa. That will prevent any strange mishaps.
On a general note, I often like to reboot the units before an upgrade if the units have been up for quite some time. That gives you the most stable state in terms of memory leaks and other bugs.
10-28-2022 05:07 AM
Master node first and then transit node for each ring. So the master will remain the master after the reboots
10-30-2022 11:58 PM
How do I treat the partner and controller switches of the shared-port?
10-31-2022 01:13 AM
Example :
1. Update Master Node
2. Reboot Master Node (Wait till eaps ring is up again)
3. Update Partner Node
4 Reboot Partner Node (The Old master should now be the current Master again)
5. Update and Reboot all Transit Nodes (This can happen in one step and you dont have do do it one by one)