Accelar --450 blocking DHCP

[simonspivey]

After a recent DHCP server hardware replacement (W2K-SP4, MS-DHCP same IP, on (A) below) users on a 450 stack (sw C, below) have not been able to renew DHCP leases. I have only one subnet (10.1.0-3.x/22) and no vlans (or all one vlan?).

If I set both ends of the link to 'trunk'/tagged, all hosts on (C) renew successfully, but all hosts on (D) lose connectivity to (C), even those with fixed IP addresses.

Up to now, Accelars have been running fine as layer2 switches, and were configured as such. Any ideas?

Switches:
(A) 1100R-A + 2x 2port1000 fibre MDA
(B) 1100 + 1x 4port100 fibre MDA
(C) 2x450 in stack, linked to (A) with 450-SR MDA
(D) 1x350 linked to (B) with 400-2FX MDA
(A) and (B) linked over copper crossover cable)

 

[jimbopalmer]

I am not sure why you would want to be tagged if you only have one VLAN. (Tagging preserves seperatee VLAN numbers accross common trunks) But changing tagging on the accelar will force the port back to VLAN 1 while changing VLANs on the 450 must be co-ordinated with the PVID of each port.

In your scenario (as I understand it) I would be all in VLAN 1, all untagged, all access ports.

I tried to remain child-like, all I acheived was childish.