Problems with printer after upgrade MS Switches 225 to latest release

[rwiesmann]

Well last week I upgraded the Switches from a customer to the latest release.

MS225-24P from MS 15.21.1 to MS 17.2.1.1

The setup:

I have a main site with about 15 branches. On all sites I have MS225 and also AP's.

After the upgrade users have problems with printing. The print server is in the main site. Each site has some printers, different vendors.

The problem is that some printers (differnet models) do not respond any more. For failing printers some of them the ports on the switch will suddenly disconnect, but not all of them. In the event of failing the printer also do not respond to ping, even the dashboar shows still connected.

For the ports which are disconnected, I see this in the event log. but no reason. for the ports staying up, but still problems with the printers...no event log.

Recycle or disabling/enabling the port solves the problem for an undefinded time.

did someone experience such problems with printers with the current release MS 17.2.1.1?

For me it looks that there are some problems with the negogiation between the switch port and the printer.

I will rollback two sites this evening to see if the problems dissapear with the old release again.

Any idea or help is appreachiated.

Roger

[alemabrahao]

There are some reports of issues with this version, I think the best thing to do is open a support case to let them know about the issue and help find a solution.

[cmr]

I have stuck with 17.1.4 on sites with older switches, some as I had no choice (MS220-8p), but it does look like it is geared to the newer switches.

[RWelch]

I (too) have had issues with MS 17.2.1.1 and raised a support case yesterday.  Unfortunately I've gone too far to rollback to a previous version (without supports assistance) and so I'm ready for a new MS firmware to come out (hopefully soon).

[ww]

Wouldnt even install this version with these kind of bugs

MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted

In rare circumstances MS225 switches may encounter a software crash that results in a reboot

[Brash]

😲 I must have missed those! They don't sound like kind bugs!
The first one is the kind of thing you pull your hair out trying to diagnose.

We've just moved to 17.2.1.1 at some pilot locations so we'll see how that goes...
Was about to upgrade a critical site to 17.2.1.1 to investigate a separate multicast issue but hard nope on that now! I'll take the wait and see approach to this release.

[PhilipDAth]

Are these 48-port switches?

Does it happen by chance only to printers plugged into the second group of 24 ports?

[rwiesmann]

What is it about the upper ports...is there some bug? Something is ringging in my head..not sure but i think a colleague had one problems wirh some upper ports...

[cmr]

There was a bug relating to ports 25-48, mainly on the MS220s and MS320s from memory, but might well affect other models.

[PhilipDAth]

Internally, the 48-port switch is two 24-port switches.  There are two main ASICs that each control 24 of the ports.  Those two ASICs are then networked together.

[rwiesmann]

This are 24 port switches.

And yes, we have connected the printer to the upper ports. So 13 to 24. And yes I have only feedback that printers have an issue.

[rwiesmann]

short update, I went back to to old version for 2 location and see...the printer problems for this two location have been gone...so it seems to be a bug in my opinion. See what the next new releases will bring.