[c-nsp] MST config on single 3560

[Manu Chao]

the standard is ieee 802.1s

don't change anything to your interface config
mst instance and vlan association is a global config

if you planned to migrate to mst on your side, make sure you will migrate to
mst with your client ;)

On Tue, Jul 14, 2009 at 6:57 AM, <mb at adv.gcomm.com.au> wrote:

> Hi,
>
> We have existing 3560's with multiple trunk ports to clients+upstreams - We
> will go very close to hitting the 128 STP instance limit, therefore MST
> looks to be like an option(Without upgrading the switches).
>
> The 3560's also have a trunk port to 7200's(For dot1q subints), for clients
> that require L3 connectivity.
>
> I'm just a little unsure how to group vlans into seperate instances(Or if
> it is entirely necessary?)
>
> i.e. GE0/1 (From Provider A) has:
>
> interface GigabitEthernet0/1
> description GIGE_ICAP_INTERNETCONNECT_TO_PROVIDER_A
> switchport trunk allowed vlan
> 112,172,208,211,240,309,315,385,537,547,550-552
> switchport trunk allowed vlan add
> 554,623,635,687,690,694,696,697,867,879,980
> switchport mode trunk
>
> These vlan's are allocated by provider and represent individual services -
> These vlans are then either presented on client trunk ports for L2 services,
> or added to trunk port to 7200 for L3 services.
>
> So as you can see, there is no "standard" for how the individual vlan's are
> treated, nor which trunk port they may be presented on.....hoping someone
> can provide guideance on how best to manage this?
>
> Thanks in advance.
>
> -------------------------------------------------------------------------
> This e-mail was sent via GCOMM WebMail http://www.gcomm.com.au/
>
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>