From: John Gibson (johngibson1541@yahoo.com)
Date: Fri May 18 2007 - 15:37:14 ART
I think 1 solution is to disable STP on those common
vlans, "no spanning-tree vlan vlan-id". Let the
service provider PVST enjoy being root of the common
vlans.
Our MST will be numbed about the fact that some
vlans are rooted at PVST side while our vlans are
rooted in our local MST domain, and no inconsistent
errors will be reported in the join points.
Not sure how service provider's PVST process thinks
about our local vlans. PVST surely doesn't care about
some vlans in 1 domain and some vlans in another
domain.
Is "no spanning-tree vlan vlan-id" the command my
manager is pushing me to learn? Is that all? He didn't
have go through such harsh route to do this.
I am still afraid if my MST switch will pick on me
about some vlans are not rooted in my domain even
though I tell my MST process not to take care of
those common vlans.
To many people push and push me. Even the MST
process (not human!) picks on me. What am I ? Lower
species than silicon(stone !) ?
Maybe I have to do root guard on my local vlans to
make my manager happy. When SP tries to be root of
my local vlans. My switches will block the joins.
Now I have to pray that when my switches block the
joins, they don't block the common vlans.
I am better this time. I am praying to god. Not
some silicon chips.
John
--- Wink <dwinkworth@wi.rr.com> wrote:
> The solution is to terminate the ethernet service
> with a router.
>
> ----- Original Message -----
> From: "John Gibson" <johngibson1541@yahoo.com>
> To: <ccielab@groupstudy.com>
> Sent: Thursday, May 17, 2007 3:10 PM
> Subject: Re: If service provider insists being root
> for common vlans running
> PVST, and our local manager insists being root for
> local vlans running MST.
> Solution exists ?
>
>
> > Actually, for the 3rd paragraph, I originally
> > thought about the service provider insists
> > no local secret vlans allowed. They have to
> > have the vlan numbers of our local vlans and
> > the join points be trunks. Then our local
> > manager insists no complicated MAC filtering.
> >
> >
> >
> > --- John Gibson <johngibson1541@yahoo.com> wrote:
> >
> >> I know when a MST domain is adjunct to a PVST
> >> domain,
> >> either MST has to take over all vlans' root or
> >> PVST has to take over all vlans' root.
> >>
> >> When the service provider and our local manger
> >> contend for their ideas, I can think of 1
> solution
> >> is to make the joint points access-ports. This
> way
> >> service provider is not aware of our local vlans.
> >> We don't send BPDUs to service provider and
> neither
> >> do they send us BPDUs. And we manually keep the
> >> common vlans free of looping in our domain.
> >>
> >> However, if our manager also insists the join
> points
> >> trunk ports. Is there a solution? I think there
> is
> >> - MAC filtering. However, if our local manager
> >> insists again no complicated MAC filtering. What
> >> can we do ?
> >>
> >>
> >>
> >>
> >
>
This archive was generated by hypermail 2.1.4 : Fri Jun 01 2007 - 06:55:21 ART