Moderator

 • 

9.5K Posts

April 27th, 2015 14:00

Hi René,

It looks like the Ruckus AP is sending an ARP to the broadcast address of each of the subnets. 255.255.255.255 is the broadcast address for 0.0.0.0. Does it work properly? You may want to try updating the firmware. http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=20CPW&fileId=3438916739&osCode=NAA&productCode=networking-n2000-series&languageCode=EN&categoryId=NI

There was nothing in your config that looked like an issue.

1 Rookie

 • 

10 Posts

April 28th, 2015 09:00

Thank you for your help, Josh. After upgrade our switch with this firmware version, we continue to have the same warning. The Ruckus AP is working fine but we have a big problem we thought was generated by the warning.

The problem is every 8/10/12 hours if we ping -t our switch we lost 3/4/5/6 ping with a message "Destination Host Unreachable" and then works fine again. Every 1/2/3 minutes the problem happens again.Just solve the problem when we restart all the DELL switch. In our network we have different types of switch like N2048P, N3024F, PowerConnect 5524P or Nortel, but we only have this problem with N2048P, N3024F. We cannot tracert the switch because only happens a few seconds. We have disabled Spanning Tree but  we continue to have the same problem.

In RAM Log files we don´t have any important message, only the warning that I mentioned before and today we have a new message:

Notice Apr 28 09:06:43 OSAPI Failed to send 59 byte message to ::ffff:10.10.206.30 on socket with fd 31. Error 22 (Invalid argument).

Regards,

René

1 Rookie

 • 

10 Posts

August 31st, 2015 09:00

Torbjorn,

The message we had were caused because of the AP broadcast but our big problem was caused because an AP with a "special voltage", we need to disable PoE in the switch port and connect an external PoE injector. Dell support contact us by e-mail and resolves the problem.

Regards,

René

1 Message

August 31st, 2015 09:00

René,

Have you come up with a solution to this issue?

We have a similiar behaviour in our N3048.

"Failed to send 112 byte message to ::ffff:192.168.13.160 on socket with fd 27. Error 22 (Invalid argument)."

When this happens we can't connect to any server on the same LAN.

Haven't, until now, connected this issue to the Dell switch, so I didn't try restarting it.

Very interested to know how this succeeded for you.

Regards, Torbjorn

3 Posts

August 23rd, 2017 14:00

So, how did you fix the ARP broadcast issue with the Ruckus? We are having the same issue.

No Events found!

Top