not sure if this will help, or is the problem.

I noticed on  1/g24 you do not have the following like on 1/g23:

switchport mode general

 

 

interface ethernet 1/g23
switchport mode general
switchport general pvid 172
no switchport general acceptable-frame-type tagged-only
switchport general allowed vlan add 172 untagged
!
interface ethernet 1/g24
description "Trunk to core"
switchport mode trunk
switchport trunk allowed vlan add 10,20,172
exit

Thanks Starlog.

 

I think on 1/g23 I just have the switchport mode set to general because I would like that interface acces to other VLANs on the network.

 

The 1/g24 is switchport trunk mode to access my core switch for routing.

 

I think the Dell's allow for 3 types of switchport modes:

 

switchport mode general

switchport mode trunk

switchport mode access

 

Thanks

 

Mason

Welp,

 

I figured it out. It was STP. I had a redundant link from my Core coming back into the switched network. So, I checked 'show spanning-tree" and it shows the uplink from the new switch to 172 network in a blocked state. :O Yay, I love it when I eat WeeTarDed sandwitches

 

Mason

Mason,

 

Thanks for the post back, I was suffering from WeTarded also..

Finally got ours to receive dhcp from a different segment, now, to work on the other VLANs. OH, and also all the 5324 switches down stream that need new vlans added to them.. Oh the hard work we IT guys put in for our companies, if they only knew.

Np Starlog,

 

That sounds interesting. did you setup the PVID per VLAN ID for each segment then setup the DHCP filtering? I was about to do that and just hammer through this switch. If you have any advise, thanks :) I was just going to do this on the interface connected to my switched network

 

interface ethernet 1/g23
description "to switched network with DHCP 172 scope"
ip dhcp filtering trust

switchport mode general

switchport general pvid 172

no switchport general acceptable-frame-type tagged-only
switchport general allowed vlan add 172 untagged

 

Sound right?

 

Thanks

 

 

I haven't gotten that deep into it yet. I hope to get back on it Thursday, as we had other issues today.

Keep in mind this is all on a test bench setup, as we will start to deploy this in about 3 weeks.

We have the 6224 connected as follows:

 

Vlan1 - 192.168.1.x management

Vlan2 - 192.168.111.x servers with one dhcp, DC, and exchange server.

Vlan3 - 192.168.115.x  connects to a 5324 switch for client PC's,

Vlan5 - 192.168.117.x connects to a 5324 switch for client PC's,

 

I have several ports designated  for each vlan, the client PC's can plug into their respective switches, and receive a IP from the dhcp server.

We are using dhcp relay and pointing to our dhcp server 192.168.111.37.

 

I will get the config Wednesday and post it, for that. Soon as I can get back to it, will keep you posted.

Sweet Starlog,

 

I have been hammering this switch hard. And its eatting my brain. Unfortunatley, i don't have a test bench area. I am being baptised in flames right now. Its a tough cookie right now. I have setup a Core switch and it just does routing.....wait a second. i'll come back to this...

 

OK, so...here we are, I have it like this Core-6224 and a Distribution-6224 connected by a trunk link with only 2 VLANS. and 2 networks. a 172.16.0/24 and 10.10./24. These seperate networks are 2 companies!! lol which mean, 2 AD, 2 DCHP, 2 Forests....everything in x2's. Now, trying to merge them has been quite the spiderweb dance.

 

I was able to get both networks to ping each others ip range. But only the static ip's. Like servers and firewalls. So, it would seem like L3 access works fine. So, once that was done, I tried to to get to a network share on a server on the destination network. WHAM, nothing. I dont get L4. TCP/UDP just laughs in my face... ugh... I have no idea what the heck im doing i suppose... lol.

 

Ok, back to the begining. So my Core does routing, right? well, i just read that in the "Users Guide" under VLAN Routing section, it says this "

A port can be either a VLAN port or

a router port, but not both. However, a VLAN port may be part of a VLAN that is itself a router

port." Maybe since I have a trunk running between the Core and Distribution its messing things up. Because its carrying L2 traffice across the Core switch, when it should just be all routing... ahhhhh HA!!! KAAaaa-CHHOOOWWWWwwwWWW!!!!! we'll see tommrrow. We'll need to talk more Starlog. I appreciate all your help and info

 

Mason

Mason,

 

I did not get to work this as planned, so I called for tech support. The problem for me was getting the multiple vlans from the 6224 to the 5324's down stream. notice the 6224 is general, and the 5324 is trunk. This is a real thought process, hope this code helps below:

 

On the 6224, after adding the members of the port channel, # being the VLAN number to add to the port:
 
Console(config)# interface port-channel 1
Console(config-if)# switchport mode general
Console(config-if)# switchport general PVID # (Typically 1)
Console(config-if)# switchport general allowed vlan add # tagged (repeat for more VLANs)
Console(config-if)# exit
 
On the 5324:
 
Console(config)# interface port-channel 1
Console(config-if)# switchport mode trunk
Console(config-if)# switchport trunk allowed VLAN add #
Console(config-if)# exit