Troubleshooting Cisco SG220-26P

[informaticastjoanv]

Hi,

I'm having a strange behaviour in a new bought Cisco SG220-26P. It's connected with multimode fiber transceivers SFP MGBSX1. I've multiple packets with errors in Interfaces Statistics. Changed transceivers, cables... First I thought it was some bad cable but i saw that the transceiver port also have packets with errors. This switch is connected with another CISCO SG300-10SFP and there're no package errors on that switch. Only in the Cisco SG220. The errors are not only on the fiber port. Also many ports have Packets with errors. I'm a bit confused.

I've done:

- Changed transceivers

- Changed cables

- Changed fibers (i've 12 fibers) and still generating packets with errors.

Anyone can help me?

Thanks! 

[Aleksandra Dargiel]

Hi,

Did you manage to get this problem fixed? I have seen also packets with errors but it was not related to the module and we replaced the unit which solved the problem.

Regards,

Aleksandra

[informaticastjoanv]

I've spoke with Radostina Todorova from CISCO about the case SR 634414661. But there doesn't give me a final solution.

I've not resolved the issue. I'm planning discard the switch if issue is not resolved.

Regards,

Ricard.

[halfbyte1]

Which unit did you replace? I have a very similar issue with a SG300-20 talking to a SG220-50, the SG220 is getting increasing input errors on 1 of 2 interfaces (two interfaces in a LACP LAG) connected to the SG300. I have tried different ports, cables, etc. One interface always is producing input errors, and throughput/performance is horrible right now (pings from 13ms - 200ms)

[informaticastjoanv]

Hi,

I've no solution from CISCO. Very very bad support from them. The problem of mine is a SG300-10SFP with a SG220-26P, connected with optic fiber with SFP transceivers. I've contacted with support and they given me to send logs, discussions and after all said that this errors can be "acceptable". I've not see it in any other switch devices from other vendors (I've Netgears and 3com) so my option is buy another switch from other vendors and see what are the results.

Hope this helps.

[halfbyte1]

Did you narrow down it to which switch had the problem yet?  Are you using LACP by chance for your connection?

I have another SG300-20 arriving on Wednesday so I may be able to setup a test and see if the SG300-20 is angry or if the SG220 is angry with the incoming packets.  Either way there is a clear difference in performance, reliability and stability of the link when these incoming packets are being dropped.

When I get some free time I will ring Cisco as well to get their opinion and take on it

[halfbyte1]

I got it to not be so angry... disabled LACP, left just a 'lag' and the errors went away. Time to see if they have a fix :)

[informaticastjoanv]

I think it's not fixable. Think some units (as i see in the forum) have hardware mistakes and think my unit is not good. Hope with the fixes will resolve your problems.

[halfbyte1]

LACP wasn't the fix... :-(

Called Cisco this morning they are going to re-produce it in the lab... I am not holding my breath :(

Hopefully the new SG300-20 that is coming for another project solves the problem, and I will just swap/return/exchange the bad SG300