From: Babylon By The Bay (tech-lists@rexglobal.com)
Date: Sun Jul 27 2003 - 16:24:23 GMT-3
FYI: Just released within the last 48hours was code 12.1.14EA1 but as of yet
no release notes per that code.
I suspect the release notes will be available within the week and if bug
CSCdz22629 is still an issue.
Of course the use of VLAN1 in and of itself is another matter.
----- Original Message -----
From: "Brian McGahan" <bmcgahan@internetworkexpert.com>
To: "'Brian McGahan'" <bmcgahan@internetworkexpert.com>; "'Richard L.
Pickard'" <nettable_walker@comcast.net>; "'Ccielab@Groupstudy. Com'"
<ccielab@groupstudy.com>
Sent: Sunday, July 27, 2003 11:01 AM
Subject: CSCdz22629 Bug Details was RE: only allow one VLAN across trunk on
3550
> Group,
>
> Recant that last posting I just made. After further
> investigation, I have found that the 3550 does not perform as it should
> when editing the allowed vlan list.
>
> When VLAN 1 is removed off a trunk link, most Cisco switches
> still run a feature known as "VLAN 1 minimization". Basically this
> means that CDP and VTP updates are still sent over VLAN 1, but no user
> traffic. 3550, on the other hand, does not conform to this behavior:
>
> <quote>
>
> CSCdz22629 Bug Details
>
>
> Headline CDP / VTP updates not received when vlan1 cleared from trunk
> Product 3550
> Model all
> Component firmware
> Duplicate of CSCdz20942
> Severity 2
> Status Duplicate
> First Found-in Version 12.1(11)EA1
> First Fixed-in Version Version help
>
> Release Notes
>
> When vlan 1 is removed from a trunk on a 3550, we no longer see CDP
> neighbours via that interface.
>
> The desired behavior described by this bug is known as "VLAN 1
> minimization". Until that feature is released on the 3550, follow the
> recommendation in the documentation and do not remove VLAN 1 from trunk
> ports.
>
> </quote>
>
>
> Therefore, VLAN 1 *should not* be removed from the allowed list
> on a trunk link on a 3550. Design wise this is not really an issue,
> since VLAN 1 should never be assigned for any user traffic, including
> management traffic. Also, since pruning will automatically control what
> traffic passes over the trunk, editing the allowed list is not really
> required in practicality.
>
>
> HTH,
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Brian McGahan
> > Sent: Sunday, July 27, 2003 12:41 PM
> > To: 'Richard L. Pickard'; 'Ccielab@Groupstudy. Com'
> > Subject: RE: only allow one VLAN across trunk on 3550
> >
> > Richard,
> >
> > Editing the allowed vlan list does not affect VTP
> > advertisements. The VLANs that exist throughout the VTP domain will
> > still be advertised, but actual user traffic for the VLANs can only
> flow
> > over the link if it is in the allowed list.
> >
> > HTH,
> >
> > Brian McGahan, CCIE #8593
> > bmcgahan@internetworkexpert.com
This archive was generated by hypermail 2.1.4 : Wed Aug 06 2003 - 06:52:55 GMT-3