I’m fine either way, but the counterpoint to Andrew’s comment is that if an ASN is affected [25%], has chosen not to upgrade yet [I’m in that boat], peered with both RS and doing next-hop-self, service impacts should be negligible other than annoying syslogs or perhaps undo burden on RS1 while things are in this state.

 

It doesn’t seem like there are too many MICE members vocal about this within the last 24 hours so I’m not sure I would great it as an emergency.  I wouldn’t upgrade both members of a redundancy pair essentially at the same time unless there was a critical impact to services.   I’d hate to be the guy that says “update RS1 right now” and then things go south on both this weekend.

 

-Michael

 

From: Andrew Hoyos <hoyosa@gmail.com>
Sent: Friday, October 24, 2025 1:58 PM
To: Richard Laager <rlaager@wiktel.com>
Cc: mice-discuss@lists.micemn.net
Subject: Re: MICE RS2 Bird Update

 

I’d be all for pushing updates to RS1 as well, and an alert/alarm free weekend :)



Andrew Hoyos

hoyosa@gmail.com

 

 



On Oct 24, 2025, at 12:51, Richard Laager via mice-discuss <mice-discuss@lists.micemn.net> wrote:

 

I updated rs2. For IPv4, there are 40 more sessions up now than before the upgrade, so this clearly helped with the BGP attribute issue that's going on right now.

Opinions on whether I should upgrade rs1 sooner (i.e. today) vs waiting until Monday, given the active issue? At a minimum, I'll wait a few hours to ensure rs2 is stable.

On 2025-10-24 10:08, Jay Hanke via mice-discuss wrote:

MICE will be upgrading BIRD on RS2 (Ridgeview) at 12:00 PM Central
time today to resolve the malformed BGP update issues causing flapping
BGP sessions.
We expect the upgrade to be less than 30 minutes. All sessions to RS2
will drop during this time. Sessions to RS1 will be unaffected.
MICE is planning to apply the same patch to RS1 (511) on Monday.


--
Richard
_______________________________________________
mice-discuss mailing list -- mice-discuss@lists.micemn.net
To unsubscribe send an email to mice-discuss-leave@lists.micemn.net