Re: SG300-52 Ports with printers connected

andrewreynolds · ‎10-16-2018

We have an SG300-52 unit that is working fine with the exception of 4 ports GE9, GE24, GE32 and GE37...each of these ports have a printer connected to it and these are the only ports that I get Packets with errors on, they are also the only ports that come up in the Ram memory log files (ports up and down)

2147483622	2018-Oct-16 10:57:37	Warning	%STP-W-PORTSTATUS: gi37: STP status Forwarding
2147483623	2018-Oct-16 10:57:37	Warning	%STP-W-PORTSTATUS: gi32: STP status Forwarding, aggregated (1)
2147483624	2018-Oct-16 10:57:33	Informational	%LINK-I-Up: gi37
2147483625	2018-Oct-16 10:57:33	Informational	%LINK-I-Up: gi32, aggregated (1)
2147483626	2018-Oct-16 10:57:27	Warning	%LINK-W-Down: gi37
2147483627	2018-Oct-16 10:57:27	Warning	%LINK-W-Down: gi32, aggregated (2)
2147483628	2018-Oct-16 10:56:36	Warning	%STP-W-PORTSTATUS: gi32: STP status Forwarding, aggregated (1)
2147483629	2018-Oct-16 10:56:32	Informational	%LINK-I-Up: gi32, aggregated (1)
2147483630	2018-Oct-16 10:55:35	Warning	%STP-W-PORTSTATUS: gi37: STP status Forwarding, aggregated (1)
2147483631	2018-Oct-16 10:55:31	Informational	%LINK-I-Up: gi37, aggregated (1)
2147483632	2018-Oct-16 10:55:26	Warning	%LINK-W-Down: gi37, aggregated (1)
2147483633	2018-Oct-16 10:54:21	Warning	%STP-W-PORTSTATUS: gi32: STP status Forwarding
2147483634	2018-Oct-16 10:54:16	Informational	%LINK-I-Up: gi32
2147483635	2018-Oct-16 10:54:11	Warning	%LINK-W-Down: gi32
2147483636	2018-Oct-16 10:52:06	Warning	%STP-W-PORTSTATUS: gi37: STP status Forwarding, aggregated (1)
2147483637	2018-Oct-16 10:52:02	Informational	%LINK-I-Up: gi37, aggregated (1)
2147483638	2018-Oct-16 10:51:59	Warning	%STP-W-PORTSTATUS: gi24: STP status Forwarding
2147483639	2018-Oct-16 10:51:56	Warning	%LINK-W-Down: gi37, aggregated (1)
2147483640	2018-Oct-16 10:51:54	Informational	%LINK-I-Up: gi24
2147483641	2018-Oct-16 10:51:49	Warning	%LINK-W-Down: gi24
2147483642	2018-Oct-16 10:49:17	Warning	%STP-W-PORTSTATUS: gi37: STP status Forwarding
2147483643	2018-Oct-16 10:49:16	Notice	%COPY-N-TRAP: The copy operation was completed successfully
2147483644	2018-Oct-16 10:49:13	Informational	%LINK-I-Up: gi37
2147483645	2018-Oct-16 10:49:11	Informational	%COPY-I-FILECPY: Files Copy - source URL running-config destination URL flash://startup-config
2147483646	2018-Oct-16 10:49:07	Warning	%LINK-W-Down: gi37
2147483647	2018-Oct-16 10:49:03	Notice	%SYSLOG-N-CLEARLOGGING: clear messages from the internal logging buffer.

andrewreynolds · ‎10-16-2018

I have tried changing the port to 100mbps full duplex but that made things worse... checked cables (all CAT6) and did a Fluke test on the permanent link ...all if good.

Seb Rupik · ‎10-16-2018

Hi there,

I have once seen similar behaviour with managed-print printers. If we had a powercut and the switches reloaded but the printers remained online, by the time network connectivity was restored the printers would go into this type of interface reload death cycle and never recover.

The only solution was to manually reload the printers.

We were never given a reason by the printer vendor (konica-minolta) as to why they behaved like this!

Cheers,

Seb.

andrewreynolds · ‎10-18-2018

Hi Seb,

thanks for your reply... I'm not sure I totally understand your solution though, I have unplugged both the network and power plugs to reset the printers but the issue is still there. I have also mapped out out network to make sure we have NO loops in our network to no avail.

The oinly thing all these printers have in common is they are HP printers. We have just purchased a new one and will be adding it to the network later today and will see if it also becomes a problem.

Seb Rupik · ‎10-18-2018

Are the printer ports configured with STP portfast. It could be that the printers are impatiently waiting for the interface to come up whilst they are waiting to issue a DHCP request.

Or are the printers statically assigned an IP address?

andrewreynolds · ‎10-18-2018

they are all static ip's

Seb Rupik · ‎10-18-2018

What does you running config look like?

I am wondering why STP is reporting those links as aggregated.

andrewreynolds · ‎10-18-2018

To be honest I have no idea how to save the running config and send paste it here... I'm using the GUI interface

Seb Rupik · ‎10-18-2018

Do you have a TFTP service available?

https://sbkb.cisco.com/CiscoSB/GetArticle.aspx?docid=4114f793e6324e9989fde69281da6573_Configuration_of_Download_and_Backup_Configuration_and_Logs_.xml&pid=2&converted=0

andrewreynolds · ‎10-18-2018

not really I have Putty installed but haven't used it in so long

Other issue is not seeing running config as an option

andrewreynolds · ‎10-18-2018

I just realized a firmware update is probably in order....

Seb Rupik · ‎10-19-2018

Upgrading firmware to current recommended versions would always be Cisco TACs list of initial suggestions.

I wrote a blog post on upgrading pre v1.3.5 switches. The instructions are for CLI if you fancy it:

https://configif.wordpress.com/2017/08/03/cisco-200-300-and-500-series-pre-v1-3-5-upgrade-procedure-via-cli/

Let us know if it fixes things.

andrewreynolds · ‎10-19-2018

Hey Seb,

Personally I haven't touched the CLI in probable 10 years (pre-GUI) so I don't think I'll take a change there but thanks and your article is very well written.

As for the Firmware I guess it will have to wait till I can schedule some downtime (probably around Xmas)

I really appreciate your help on this matter

andrewreynolds · ‎10-19-2018

Hey Seb,

right now on Cisco's site I can only see 1.1.2.0 then it jumps to 1.4.1.03 and then to 1.4.9.4... I see nothing in the 1.3.5.06 range... it it safe to go from 1.1.1.8 to 1.1.2.0 then 1.4.9.4?

Seb Rupik · ‎10-19-2018

Have a look a bit lower in the menu tree, under 'all releases'.

For you current version you have to go via the v1.3.5.06 boot file. You will find this under '1.3.5.58' .

cheers,

Seb.