On 7/8/13 3:00 PM, Tom Storey wrote:
The thing thats confusing me is, who on earth presents a service to a
customer as a tagged service? Ive never come across such a thing.
entirely appart from the case of metro-e/pbb/spb if you're doing L2 or L3 vpn, on the PE you can differentiate between tunnels/services provided to the customer by helpfully tagging them with a vlan-id.
If you're plugged in to a router interface on the providers side, why is
there a need to add VLAN tagging on top? Similarly, if you're plugged in to
a switch, normally the switch port is just an access port, not a trunk.

Someone help me out here... :-)


On 8 July 2013 22:47, Michael Loftis <[email protected]> wrote:

vlan-tagging tells JunOS to treat the interface as multiple separate
L3 interfaces, identified by VLAN ID.  Their end is almost certainly
similarly configured (maybe as a MPLS PE)

On Mon, Jul 8, 2013 at 10:26 AM, Keith <[email protected]> wrote:
Have this setup in the lab on some srx's but want to get some info
on this.

We have an upstream provider that we use a config:

set interfaces ge-0/1/0 vlan-tagging
set interfaces ge-0/1/0 encapsulation flexible-ethernet-services
set interfaces ge-0/1/0 unit 1500 vlan-id 1500
set interfaces ge-0/1/0 unit 1500 family inet address x.x.x.x/30


We are turning up a second connection to them that will be terminated on
a
10G
link and want us to use the same thing, vlan 1500, just a different IP
address.

Will this cause a problem by having the same vlan id on both links to the
same provider? (I am guessing we are being terminated on different
routers
on their side).

My lab router didn't complain so I'm guessing its probably ok.

Thanks,
Keith

_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp


--

"Genius might be described as a supreme capacity for getting its possessors
into trouble of all kinds."
-- Samuel Butler
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp


_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to