[j-nsp] MX bridge-domains

Keegan Holley keegan.holley at sungard.com
Fri Feb 4 14:57:58 EST 2011


Where do you need to transport them? Also, are you running mpls?  I would
probably use some mpls based service, L2VPN, VPLS, EoMPLS etc.  If not I'd
probably just use generic switches, juniper or no.  The cost per port is
much lower.


On Fri, Feb 4, 2011 at 2:45 PM, Bill Blackford
<BBlackford at nwresd.k12.or.us>wrote:

> I considered holding off on this question until I gained a better
> understanding on what I really need but then thought I'd like to head down
> the right path before I get too deep.
>
> The scenario:
> I have a need to carry customers on individual tags though the network to
> provide IP on the far end. Basically a simple access exchange. The UNI
> handoff could be an 'access' port or in some cases an NNI handoff from a NSP
> that's 'trunked'. In either case, I'm passing the customer tags through my
> network via 'vlan-bridge' and the use of 'bridge-domains'.
>
> The question:
> Should I place each customer in its own bridge-domain/vlan-id/unit # or
> would it make more sense to use a single bridge-domain and 'vlan-id-list'?
>
> Thank you,
>
> -b
>
>
>
> --
> Bill Blackford
> Senior Network Engineer
> Technology Systems Group
> Northwest Regional ESD
>
> Logged into reality and abusing my sudo priviledges
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>


More information about the juniper-nsp mailing list