Issues with 4 stacked 6248's

One of the first things I would suggest is to ensure all the switches are on the same firmware , and it is current.

www.dell.com/.../DriverFileFormats

After the firmware update If there are still issues I would look at a couple things.

Has this issue always been present? Or has It started since making any recent changes?

Try and narrow it down, is it traffic on one specific switch, or certain ports, or a certain Vlan?

Or is it all traffic?

Let us know what you find and we can bounce around ideas.

Thanks.

this has not always been an issue, it just started and there have not been any changes made.  Will firmware updates lose the config?  I am not the person who originally set up this switch and i am worried about having to redo everything.

Updating the firmware will not affect the current configuration. You can always back up the configuration if you wanted to.

Not your exact switches, but gives you some ideas.

www.dell.com/.../app_note_12.pdf

support.dell.com/.../ReleaseNotes.pdf

Thanks

I just deployed a stack of 4, 6248's as my core, and things are good.  Are these performance issues occuring on VLANs inside of the stack, and crossing over to other VLANs?  ...or is it all traffic.  You might want to share your config here so that you could get more feedback.

Hi, We have a similar sounding problem over here. A stack of 2x 6224s working fine until we had a spike in traffic, now we've been unable to manage the stack except via the console for the last two weeks. A ping will occasionally get a reply, but only about 1 in 50. The suggestion from Dell tech support was to initiate a failover - we have a maintenance window to do this today, so I'll report back afterwards.

The stack is already on the latest firmware and has been running for about a month before this incident. There don't seem to be any other issues with the stack - traffic appears to be passing through fine - just can't access the web UI, SNMP or telnet / SSH.

An update on the above - we initiated a failover during our maintenance window and issues connecting to management functions have been resolved. Interestingly, while we were experiencing issues we were getting the following output on the console. I'm guessing this is when the stack is trying to contact the ntp server.

<187> FEB 15 11:50:32 172.16.123.241-1 DNS_CLIEN[216402816]: dns_client_txrx.c(371) 49935 %% DNS Client: osapiSocketRecvFrom returned error for addr 0xCE60A90. Indicates there is a stack error in receiving the DNS response packet from the server.