Here is a wierd one I am hoping someone has heard of before.
We have a LocalDirector 416 running 4.2.5. There are problems where customers are reporting timeouts when trying to access applications on our internal network. These timeouts seem to be very brief and very intermittent.
Here is the strange part. A packet capture shows that the LocalDirector is sometimes inserting a source MAC address of a device it has learned about through the E0 interface into the packet as it's own. Obviously it is not hard to see why communication would fail when the server tries to repond to an invalid address. Has anyone seen any bugs or scenario where LocalDirector has done this before?
Any help would be greately appricated.
Thanks,
Jody