"show vlan" will tell you if the VLAN has been created on the Cisco. The config to create it is easy (and necessary): ! vlan 25 name Radiology ! Aled On 6 March 2012 17:55, Jason Baugher <jason@thebaughers.com> wrote:

+1 on show interface trunk, which will probably tell you that only vlan 1 is allowed on your trunk interfaces.

I find it easy to forget that a Cisco switch will not pass tagged traffic for a vlan if that vlan isn't created on the switch. Even if you do something like "switchport trunk allow vlan 12" on a trunk port, it won't create the vlan on the switch unless you specifically create it or you add it to an access port like "switchport access vlan 12".

Jason

On 3/6/2012 11:04 AM, Greg T. Grimes wrote:

...

On the cisco, do a 'show interface trunk'. Be sure that it thinks it's supposed to pass those VLANs. Make sure "Vlans allowed on trunk" includes the VLAN. Same for "Vlans allowed and active in management domain". Then the important one is "Vlans in spanning tree forwarding state and not pruned". If it's not there then it's being pruned. Also on your Dell uplink add the following line to the uplink port:

switchport access vlan add 12,22

See what that does for you.

On Tue, 6 Mar 2012, Alan Bryant wrote:

I hope everyone is having a better workday so far than I am.

...

I am trying to clean up the network for the Hospital I work for, and part of that is creating two VLAN's for two separate subnets on our network. Before, it was not separated by VLANs. We are also replacing our aged Juniper firewall with an ASA.

I'm very new to VLAN's, so I am hoping this is something simple that you guys can help me out with.

We have two switches that do not seem to be passing VLAN traffic. The two switches are a Dell Powerconnect 5324 & a Cisco 3560G. The Cisco switch appears to be functioning fine, but the Dell switch is only passing traffic to the Cisco that is on the default untagged VLAN1. Our second VLAN is not getting passed to the Cisco at all, I am not seeing any packets tagged with the particular vlan in Wireshark.

I have Port 1 on the Dell switch connected to port 29 on the Cisco switch, and port 1 on the Cisco switch connected to the ASA.

I have the following config on the relevant ports on the Cisco switch:

interface GigabitEthernet0/1 description ASA 5505 switchport trunk encapsulation dot1q switchport mode trunk

interface GigabitEthernet0/29 description Radiology Switch switchport trunk encapsulation dot1q switchport mode trunk

Here is the config for the Dell switch:

interface ethernet g1 speed 1000 duplex full exit interface ethernet g2 speed 1000 duplex full exit interface ethernet g3 speed 1000 duplex full exit interface ethernet g4 speed 1000 duplex full exit interface ethernet g5 speed 1000 duplex full exit interface ethernet g7 speed 1000 duplex full exit interface ethernet g9 speed 1000 duplex full exit interface ethernet g10 speed 1000 duplex full exit interface ethernet g12 speed 1000 duplex full exit interface ethernet g14 speed 1000 duplex full exit interface ethernet g15 speed 1000 duplex full exit port jumbo-frame interface ethernet g1 switchport mode trunk exit interface ethernet g24 switchport mode trunk exit vlan database vlan 12,22 exit interface range ethernet g(2,4,7,12,14-15) switchport access vlan 12 exit interface vlan 12 name Radiology exit interface vlan 22 name Guest exit interface vlan 1 exit

Anyone have any ideas or pointers? Is there more information that I need to provide? Vlan1 works just fine, of course. It is Vlan 12 that is not working. Everything on the Dell switch is communicating with each other just fine on the same subnet.

cool! On Tue, Mar 6, 2012 at 7:10 PM, Alan Bryant <alan@alanbryant.com> wrote:

Just wanted to say a quick thank you to everyone who chimed in. Like I thought, it turned out to be something very simple and routine. I had not added the vlan to the Cisco switch. I had added it during testing, but I removed all testing config from the switch before I went to vlan's and did not add it back.

On top of that, right before I saw the message to run sh vlan, I attempted to upgrade the firmware on the Dell switch and followed Dell's instructions to the T, but it appears that the switch is now non-functional. It is in a continuous reboot cycle and I can't even get anything over the console.

Thankfully I had another switch ready and swapped it out and we are running strong with vlans.

Again, thank you so much for all of your help, and hopefully one day I will be at the level to help someone else out on here.

-- Warm Regards Peter(CCIE 23782).

I can confirm similar issues between our older Dell Poweredge 1655 and a Cisco 3550. Took me a while to figure this one out, considering the aggro trunks weren't working right either. Switching it to etherchannel solved the trunking issue, but I still had some major issues with VLANs even after that.

I have yet to move the 1655 (since we still use it for lab purposes) to the 6503.

I hate to put it this way, but I'd love to know what crack Dell was doing when they decided to use the software/hardware switch stuff they did.

I don't think the 1655 and the 5324 share ancestry. Dell does what lots of companies do: they outsourced. The Dell 5_2_24 was a catastrophic device that was based on the same hardware platform as the Foundry Edgeiron 24G and the SMC 8624T, 3Com's 3824 ... the only difference in many cases being paint and firmware. All of these were actually made by Accton, who sold it as the ES4624, and the early revisions had a catastrophic failure mode that would result in the two halves of the switch losing communications with each other, or something like that, hopefully I'll be forgiven for the technical handwaving, and eventually firmware workarounds "fixed" the switch, but (I think?) Foundry led the pack on that, and so you'd come across Dell gear with Foundry firmware or stuff like that, done by people desperate to stop their switches from going wonky every few weeks. I don't think I ever did identify the source of the 5324 fully, I think I concluded that it was somewhat unique to Dell. It lacked most of the other quirks common to cheap switches like the Accton (broadcast domain issues, anyone?) and was, at the time, probably one of the best deals in managed switching. It only had a few goofs that I could complain about, including the lack of 64-bit interface counters and the Ciscoesque-but- not-quite syntax. For the most part, I've heard that their newer products are pretty good too, though usually there are tradeoffs. obDisclosure: We run a bunch of 5324's, and don't seem to have any issues with them. ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "We call it the 'one bite at the apple' rule. Give me one chance [and] then I won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN) With 24 million small businesses in the US alone, that's way too many apples.

I've never had problems setting up multiple VLANs on a link between Cisco, HP, Dell switches, IBM mainframes, VMWare servers, 3COM/Nortel, Polycom Phones, Linux servers, etc. If both ends supported 802.1q, it just worked, if the admin read the manual for both pieces of gear and knew how to troubleshoot problems. Sure, one vendor can be nice a lot of the time - even cheaper once support costs are factored in. But making VLANs work between different vendor's equipment is a pretty basic networking skill. So I'm kind of astonished at the "sell what you have and buy new from one vendor" responses. I've not used the specific Dell switches mentioned, but I've used others and have plenty of opinions on the management interface of them. But for a wiring closet or top of rack switch, I can't say that I would suggest to replace them with something new just because I wanted a different management interface (that said, I very well might write some scripts to manage the uglier interfaces).