Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-09 Thread Adam Vitkovsky


> -Original Message-
> Eric Van Tol
> Sent: 08 July 2015 10:34
 
> unit 10004 {
> description "To Port-Based EoMPLS";
> encapsulation vlan-ccc;
> vlan-id 2123;
> input-vlan-map pop;
> output-vlan-map push;
> family ccc;
> }
Just a side note 
To do the above you'd need to enable flexible-vlan-tagging under the main 
interface (please note it will increase the MTU by 8B to MTU mismatch may 
happen preventing the L2circuit to come up).

adam

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-08 Thread Levi Pederson
All,

And yes I'm using RSVP, LDP, and LLDP and LLDP-med

Thank you,


*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net


On Wed, Jul 8, 2015 at 4:34 AM, Eric Van Tol  wrote:

> > interfaces {
> > ae0 {
> > aggregated-ether-options {
> > lacp {
> > active;
> > }
> > vlan-tagging;
> > encapsulation flexible-ethernet-services;
> > unit 10 {
> > encapsulation vlan-ccc;
> > vlan-id 10;
> > }
> > unit 20 {
> > encapsulation vlan-ccc;
> > vlan-id 20;
> > }
> > }
>
> Additionally, if you need to transport a single VLAN on one side to a full
> port on the other, you need to pop the VLAN on ingress (and push on egress)
> into (and out of) the tunnel:
>
> unit 10004 {
> description "To Port-Based EoMPLS";
> encapsulation vlan-ccc;
> vlan-id 2123;
> input-vlan-map pop;
> output-vlan-map push;
> family ccc;
> }
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-08 Thread Levi Pederson
All,

Thank you all for your help!  It's putting me on the right track!

One thing to note since I'm using EX4550's I do not have "Flexible Ethernet
Services"  Only vlan-ccc and ethernet-ccc

Thank you all for your help!

*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net


On Wed, Jul 8, 2015 at 4:34 AM, Eric Van Tol  wrote:

> > interfaces {
> > ae0 {
> > aggregated-ether-options {
> > lacp {
> > active;
> > }
> > vlan-tagging;
> > encapsulation flexible-ethernet-services;
> > unit 10 {
> > encapsulation vlan-ccc;
> > vlan-id 10;
> > }
> > unit 20 {
> > encapsulation vlan-ccc;
> > vlan-id 20;
> > }
> > }
>
> Additionally, if you need to transport a single VLAN on one side to a full
> port on the other, you need to pop the VLAN on ingress (and push on egress)
> into (and out of) the tunnel:
>
> unit 10004 {
> description "To Port-Based EoMPLS";
> encapsulation vlan-ccc;
> vlan-id 2123;
> input-vlan-map pop;
> output-vlan-map push;
> family ccc;
> }
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-08 Thread Eric Van Tol
> interfaces {
> ae0 {
> aggregated-ether-options {
> lacp {
> active;
> }
> vlan-tagging;
> encapsulation flexible-ethernet-services;
> unit 10 {
> encapsulation vlan-ccc;
> vlan-id 10;
> }
> unit 20 {
> encapsulation vlan-ccc;
> vlan-id 20;
> }
> }

Additionally, if you need to transport a single VLAN on one side to a full port 
on the other, you need to pop the VLAN on ingress (and push on egress) into 
(and out of) the tunnel:

unit 10004 {
description "To Port-Based EoMPLS";
encapsulation vlan-ccc;
vlan-id 2123;
input-vlan-map pop;
output-vlan-map push;
family ccc;
}
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-07 Thread Ben Dale
Hi Levi,

> I've setup an MPLS ring and with your help it's running beautifully. With
> it I can easily make port congruence across the MPLS ring with few issues.
> For example send a single from one side of the MPLS ring to the other if
> the signal lands on a port directly.  I.E a physical interface.

Based on your previous email, I’m assuming your transport labels are all 
RSVP-based.

> Where I'm having trouble now is landing or starting from a logical
> interface such as a VLAN.

For an aggregate interface, make sure you have flexible-ethernet-services 
configure on the physical interface (or vlan-ccc, but if not all units are 
going to be l2circuits, then stick with flexible-ethernet-services), and then 
encapsulation vlan-ccc for all the sub-interfaces you wish to tunnel:

interfaces {
ae0 {
aggregated-ether-options {
lacp {
active;
}
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 10 {
encapsulation vlan-ccc;
vlan-id 10;
}
unit 20 {   
encapsulation vlan-ccc;
vlan-id 20;
}
}
}

To bring up an l2circuit, it’s just a simple matter of assigning and ID to the 
port, and mapping it to a remote PE:

protocols {
l2circuit {
neighbor 1.2.3.4 {<— the far-side PE loopback where you want the 
other end of the tunnel to come out
interface ae0.10 {   <— your local interface
virtual-circuit-id 10;   <— unique identifier
}
}
}
}

Cheers,

Ben
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-07 Thread Mark Tees
Hi Levi,

Can you please post the relevant config?

show configuration protocols l2circuit
show l2ciruit connections
show configuration interfaces

Of course chop out any sensitive bits there.

Cheers,

Mark

On Wednesday, July 8, 2015, Levi Pederson 
wrote:

> All,
>
> I've setup an MPLS ring and with your help it's running beautifully. With
> it I can easily make port congruence across the MPLS ring with few issues.
> For example send a single from one side of the MPLS ring to the other if
> the signal lands on a port directly.  I.E a physical interface.
>
> Where I'm having trouble now is landing or starting from a logical
> interface such as a VLAN.
>
> For example.
>
> I'm receiving the signal onto a port on PE1 and I need to Add it to a Trunk
> Port which is also an aggregate link (ae0 say VLAN 3999).  Each router
> currently holds only 1 switched path to each other PE (3 LSPs per device)
>  4 Devices total.
>
> My thoughts were to use this
>
>
> http://www.juniper.net/documentation/en_US/junos14.1/topics/task/configuration/mpls-l2-circuit-cli.html#jd0e171
>
> That turned out to be incorrect or at least I did something that did not
> agree with he system.
>
> My l2circuit attempts seem to not pull up when attempted.
>
> Any help or direction would be appreciated.  I'm not looking for massive
> l2VPN or anything like that just the simpler l2circuit
>
> I can provide a diagram and documents for those with a serious request to
> help.
>
> Thank you,
>
> *Levi Pederson*
> Mankato Networks LLC
> cell | 612.481.0769
> work | 612.787.7392
> levipeder...@mankatonetworks.net 
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


-- 
Regards,

Mark L. Tees
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] Basic Implementation of VLAN/LogicalPort across MPLS

2015-07-07 Thread Levi Pederson
All,

I've setup an MPLS ring and with your help it's running beautifully. With
it I can easily make port congruence across the MPLS ring with few issues.
For example send a single from one side of the MPLS ring to the other if
the signal lands on a port directly.  I.E a physical interface.

Where I'm having trouble now is landing or starting from a logical
interface such as a VLAN.

For example.

I'm receiving the signal onto a port on PE1 and I need to Add it to a Trunk
Port which is also an aggregate link (ae0 say VLAN 3999).  Each router
currently holds only 1 switched path to each other PE (3 LSPs per device)
 4 Devices total.

My thoughts were to use this

http://www.juniper.net/documentation/en_US/junos14.1/topics/task/configuration/mpls-l2-circuit-cli.html#jd0e171

That turned out to be incorrect or at least I did something that did not
agree with he system.

My l2circuit attempts seem to not pull up when attempted.

Any help or direction would be appreciated.  I'm not looking for massive
l2VPN or anything like that just the simpler l2circuit

I can provide a diagram and documents for those with a serious request to
help.

Thank you,

*Levi Pederson*
Mankato Networks LLC
cell | 612.481.0769
work | 612.787.7392
levipeder...@mankatonetworks.net
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp