cancel
Showing results for 
Search instead for 
Did you mean: 

Failed to upgrade X690 and X440-G2 from 31.7.1.4-patch1-77 -> 32.6.1.5-patch1-2

Failed to upgrade X690 and X440-G2 from 31.7.1.4-patch1-77 -> 32.6.1.5-patch1-2

markus_of
New Contributor III

Hello,

we had some problems with the upgrade to 32.6.1.5-patch1-2 over the weekend. I wanted to ask if this is the case for you too.

When we updated the X690 the 40G ports no longer came up. They were active but we see no connection to the other switch. All 1G ports are working, only the 40G doesen't work. We use the new Image x690-32.6.1.5-patch1-2.xos  (not ONIE). After we roll back .. everything is working. 

When we updated the X440-G2 for some reason, the ssh service was no longer active after the upgrade restart. As soon as it was reactivated via the console port it worked.

Does anyone know the problem?

Best regards,

Markus

 

2 ACCEPTED SOLUTIONS

markus_of
New Contributor III

I found an article that could be our solution to the X690 problem.

Cause

This is a known issue, caused by a Forward Error Correction (FEC) mode being applied during the insertion of 100G optic that then conflicts with the 40G optic.

https://extreme-networks.my.site.com/ExtrArticleDetail?an=000116340&q=X690%20upgrade%20

View solution in original post

James_A
Valued Contributor

Once I hit it a few times, I enabled telnet before the upgrade so I could get in that way, regenerate ssh and then disable telnet again.

View solution in original post

10 REPLIES 10

markus_of
New Contributor III

Thank you James!

I see in my logs ..

01/30/2024 01:14:04.78 <Info:AAA.LogSsh> Msg from Master : Loaded Private Key of size 1679 from System

01/30/2024 01:14:05.80 <Erro:cm.sys.LoadApplCfgObjFail> "exsshd" application failed to load "exsshdPrivKey" configuration object: Error reading SSH key.

01/30/2024 01:14:05.80 <Info:AAA.LogSsh> Msg from Master : Invalid Private Key used. Please use new key.

01/30/2024 01:14:05.80 <Info:AAA.LogSsh> Msg from Master : Error:Private Key is invalid . Public key generation failed

But it honestly can't be the case that when I update 15 switches I have to make corrections on 8 on site to rebuild the ssh key.

 

 

James_A
Valued Contributor

Once I hit it a few times, I enabled telnet before the upgrade so I could get in that way, regenerate ssh and then disable telnet again.

markus_of
New Contributor III

This is a solution that we have also considered. 😎

markus_of
New Contributor III

the ports were all active and ready

Stefan_K_
Valued Contributor

That's why I stay with 31.7 until there is a new stable LTS Release in the 32.x branch.

Did the ports come up on both sides of the line or only on the X690? Was the port "blocked on the vlan"? Did you see lldp neighbors or mac addresses on the port?

GTM-P2G8KFN