Firmware update question on 460's running VRRP
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-05-2017 11:11 AM
Hello,
We have a pair of x460-G2's running VRRP and MLAG at two sites. They are currently running 16.1.3.6, and I would like to apply the current recommended firmware 16.2.2.4. This is the first time I have had to update the firmware while running these 460's in production, and I am just making sure there is nothing special I need to do.
I should be able to update one switch, reboot it, then update the second switch and reboot it, without any downtime, correct?
We have Palo Alto firewalls running in Active/Passive mode, and I need to disable preempt before patching those, so I am just confirming that when using VRRP and MLAG, I don't need to disable anything.
It also looks like with 16.2, we no longer have to apply a separate SSH XMOD - hurray!
We have a pair of x460-G2's running VRRP and MLAG at two sites. They are currently running 16.1.3.6, and I would like to apply the current recommended firmware 16.2.2.4. This is the first time I have had to update the firmware while running these 460's in production, and I am just making sure there is nothing special I need to do.
I should be able to update one switch, reboot it, then update the second switch and reboot it, without any downtime, correct?
We have Palo Alto firewalls running in Active/Passive mode, and I need to disable preempt before patching those, so I am just confirming that when using VRRP and MLAG, I don't need to disable anything.
It also looks like with 16.2, we no longer have to apply a separate SSH XMOD - hurray!
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-05-2017 12:36 PM
Excellent! Thank you so much for the information.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎05-05-2017 11:18 AM
Hello Bruce,
Assuming you don't have any single honed devices there should not be any downtime for devices connected to MLAG enabled ports. You do not need to disable anything. The reboot will be treated like a failure and the necessary transitions will be applied automatically.
As a side note, once you upgrade to 16.2 you can utilize a new feature for VRRP which is known as fabric routing. This will mimic the dual master VRRP scenario we implemented on previous version which works well with MLAG. Here is an article that explains it a little better:
https://gtacknowledge.extremenetworks.com/articles/How_To/An-example-of-VRRP-fabric-routing-configur...
Hope this helps!
Assuming you don't have any single honed devices there should not be any downtime for devices connected to MLAG enabled ports. You do not need to disable anything. The reboot will be treated like a failure and the necessary transitions will be applied automatically.
As a side note, once you upgrade to 16.2 you can utilize a new feature for VRRP which is known as fabric routing. This will mimic the dual master VRRP scenario we implemented on previous version which works well with MLAG. Here is an article that explains it a little better:
https://gtacknowledge.extremenetworks.com/articles/How_To/An-example-of-VRRP-fabric-routing-configur...
Hope this helps!
