On Tue, 6 Mar 2012, Greg T. Grimes wrote:
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
Probably should be
switchport trunk allowed vlan add xxx,xxx tagged
if you're trying to limit
On Tue, 6 Mar 2012, Alan Bryant wrote:
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
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 trouble
On 3/6/12 4:33 PM, Joe Greco wrote:
I don't think the 1655 and the 5324 share ancestry.
I'm pretty sure they don't either, but never know.
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 Fou
On Mar 6, 11:53 am, david peahi wrote:
>
> Why don't you replace the Dell switches with Cisco 3560s, and that way you
> are working with a single implementation of the IEEE 802.1q trunking
> standard? I think the very existence of this email thread proves that much
> time and effort is wasted in
> 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
On 3/6/12 9:07 AM, Alan Bryant wrote:
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
cool!
On Tue, Mar 6, 2012 at 7:10 PM, Alan Bryant 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 t
On Tue, Mar 06, 2012 at 09:32:33PM +, Jonathon Exley wrote:
> If it's still not working, try capturing traffic from the Dell switches with
> Wireshark and then send traffic from the Cisco switch and also capture that.
> Compare the frames and check that the salient parts line up - e.g. Ethert
Ehiwe [mailto:petereh...@gmail.com]
Sent: Wednesday, 7 March 2012 5:40 a.m.
To: Alan Bryant
Cc: nanog@nanog.org
Subject: Re: VLAN Troubles
yep , verify how dell tags the vlans , it may use a proprietory tagging method
for the trunk.
On Tue, Mar 6, 2012 at 5:36 PM, Alan Bryant wrote:
> Thank you
It is best to configure the Dell using the Web interface on it.
You will have to use IE to access it , (need less to say it also needs a
management interface '[).
I find the CL to be a bit confusing , but that is me
Speaking only for the Dell Side config.
Comparing your config to some of m
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 ad
"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 wrote:
> +1 on show interface trunk, which will probably tell you that only vlan 1
> is allowed on your
ything was clear-cut and easy?
Jason
On 3/6/2012 11:53 AM, david peahi wrote:
-- Forwarded message --
From: david peahi
Date: Tue, Mar 6, 2012 at 9:47 AM
Subject: Re: VLAN Troubles
To: Alan Bryant
Why don't you replace the Dell switches with Cisco 3560s, and that way you
a
+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 vl
-- Forwarded message --
From: david peahi
Date: Tue, Mar 6, 2012 at 9:47 AM
Subject: Re: VLAN Troubles
To: Alan Bryant
Why don't you replace the Dell switches with Cisco 3560s, and that way you
are working with a single implementation of the IEEE 802.1q trunking
standa
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
p
yep , verify how dell tags the vlans , it may use a proprietory tagging
method for the trunk.
On Tue, Mar 6, 2012 at 5:36 PM, Alan Bryant wrote:
> Thank you for the suggestions, unfortunately none of them are working.
>
> I have tried with the uplink in general & trunk mode. I have allowed
> all
Thank you for the suggestions, unfortunately none of them are working.
I have tried with the uplink in general & trunk mode. I have allowed
all vlans and allowed only the specific vlans I am using tagged and
untagged, but it is still not passing vlan 12.
Verify what protocol the dell switch uses to tag the traffic(from the
datasheet) , i have seen some switches that wont trunk .1q with cisco
On Tue, Mar 6, 2012 at 5:07 PM, Alan Bryant wrote:
> I hope everyone is having a better workday so far than I am.
>
> I am trying to clean up the network f
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
21 matches
Mail list logo
