Nod, I found that out when trying to trunk a Foundry FastIron II to a
Cisco router. You can however change the native vlan to something like
say "50", and then that will allow you to use vlan 1 (just not 50).
Brian
On Mon, 4 Dec 2000, Elias Aggelidis wrote:
> When you are using 802.1q
> DO NOT use the management VLAN (I mean VLAN 1)
>
> Vlan 1 on the ISL trunks is used only for management (as CISCO says)
> and Vlan 1 is the default Trunk Vlan on 802.1q.
>
> If you use VLAN 1 on the 802.1q you will find out that big packets (> 1482 )
> would not be processed correct !!
>
> Regards
>
> Elias
>
> P.S.
> I have found out this with the hard way. After 4 hours trying to make the Cat
> 4000
> to switch big packets on the VLAN 1, I have found out that VLAN 1 when it is
> used for trunking connections it can not switch big packets.
> ----- Original Message -----
> From: "Brian" <[EMAIL PROTECTED]>
> To: "Ben Hockenhull" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, December 04, 2000 12:42 AM
> Subject: Re: 802.1q between HP and Cisco
>
>
> >
> > Don't use vlan 1, the native vlan, for trunking to the 4000. Use vlans
> > 2-9 instead of 1-8
> >
> > On Sun, 3 Dec 2000, Ben Hockenhull wrote:
> >
> > > Folks,
> > >
> > > I have a Cat6509 here that I'm trying to configure to do 802.1q VLAN
> > > trunking between itself and an HP ProCurve 4000M switch.
> > >
> > > I've run into a problem, though. I have 8 vlans configured on both
> > > switches, 802.1q ID 1-8. The vlan *names* on either end match except for
> > > the first vlan. On the HP, it's 'vlan1'. On the Cat, it's 'default'
> > > because it cannot be changed, which is annoying. The vlan IDs match
> > > throughout.
> > >
> > > I can ping devices on any of the vlans except for vlan 1, from the Cat. I
> > > cannot get any connectivity from the Cat to the HP on vlan1. If I disable
> > > tagged vlans on the HP, I can get ping to vlan1, even while 802.1q is
> > > enabled on the Cat.
> > >
> > > Just for fun, I changed the name of vlan1 on the HP to 'default' and it
> > > had no effect, so it doesn't seem to be some weirdness with plain english
> > > identifiers.
> > >
> > > Now for the really weird part. If I configure the trunk on the HP to be
> > > untagged on vlan1 and tagged on all other vlans, I seem to get
> > > connectivity to all vlans from the Cat.
> > >
> > > Is there something inherently funky about vlan 1 on the cisco stuff? It's
> > > really odd that all the other vlans work if configured to be tagged at
> > > both ends, and the config for all 8 vlans is the same at both ends.
> > >
> > > This is driving me crazy.
> > >
> > > Ben
> > >
> > > --
> > > Ben Hockenhull
> > > [EMAIL PROTECTED]
> > >
> > > _________________________________
> > > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> > >
> >
> > -----------------------------------------------
> > Brian Feeny, CCNP, CCDP [EMAIL PROTECTED]
> > Network Administrator
> > ShreveNet Inc. (ASN 11881)
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
>
> _________________________________
> FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
-----------------------------------------------
Brian Feeny, CCNP, CCDP [EMAIL PROTECTED]
Network Administrator
ShreveNet Inc. (ASN 11881)
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
