Oh, further elaboration on the DHCP issues I've had. I set up a trunk
between the router and the switch, and had it running VLAN traffic over one
link. Works perfect, except DHCP takes a few minutes when you plug into a
port assigned to any of those VLANs that are using DHCP. It caused issues
with some of the devices we were plugging in, so I had to move it to a
physical untagged port on the router and run that straight to those
devices. DHCP worked fine then. Again, the router is plugged into the
Dell, not the Cisco. I think Jeremy might be right here, this Dell is
probably causing more issues than it's worth.
On Wed, May 4, 2011 at 10:29 PM, Chris Jones <techmaster@gmail.com> wrote:
> I have DHCP issues on the same switch that the router (dhcp server) is
> plugged directly into. I don't think it has anything to do with the bridge
> or the trunk. No unusual ping times, I get the usual 10ms ping time. I've
> browsed across it to a server, and moved large files around, it was like a
> typical wired 100Mb network, across the bridge. So I think the bridge
> itself is fine. I'm wondering if maybe there's some kind of encapsulation
> math I'm missing. Like with some internet connections, you have to lower
> MTU to make up for some encapsulation that the ISP's equipment does. Is
> there somewhere that maybe I have to tune something such as this, an MTU for
> a trunk link? I'm getting the feeling that if I ditch the Dell and get a
> second Linksys/Cisco Small Business switch (3000 something was the model I
> think) it might solve every one of my problems. Stackable switches are made
> to be EASILY stackable, but with one caveat: you have to stack the same
> make/model of switch. I didn't have that luxury this time, but it might be
> worth it for me to make a push for it. Everything worked perfectly in the
> dry run at our office, too.
>
>
> On Wed, May 4, 2011 at 7:16 PM, Jimmy Hess <mysidia@gmail.com> wrote:
>
>> On Wed, May 4, 2011 at 5:32 PM, Chris Jones <techmaster@gmail.com> wrote:
>> > Yes, vlan10 even works. I can ping the cable modem with a laptop on the
>> > other switch. The one weird thing I'm seeing is dhcp takes a few
>> minutes to
>> > give out an ip.
>>
>> Are you looking at the latency you get back when you ping? Anything
>> unusual there?
>> eg. 64 bytes from XX.YY.ZZ.WW: icmp_seq=1 ttl=64 time=0.617 ms
>>
>> I would consider the existence of a wireless bridge on a trunk link a
>> suspect in regards to DHCP performance issues.
>>
>> Perhaps some ping tests, to verify delay, latency stability, and ping
>> loss numbers
>> between the two switches would be in order.
>>
>>
>> Trunk links should be full duplex at both ends, but if there was a
>> mismatch,
>> congestion or instability of the link, there could be high delay/loss
>> of traffic;
>> including DHCP traffic.
>>
>> --
>> -J
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
>
>
___________________
Nolug mailing list
nolug@nolug.org
Received on 05/04/11
This archive was generated by hypermail 2.2.0 : 05/05/11 EDT