Re: [j-nsp] traceroute in mpls vpn's not showing P hops

[Chris Burton]

Given that LSP's are by there very nature unidirectional you will need a 
return LSP unless you plan export your VRF routes into your underlying 
network.  The path that that return LSP takes should not make a 
difference unless you are testing specific return path(s), so it should 
not interfere with your learning of RSVP, actually that operation is no 
different than much of standard L3 routing in the wilds of the Internet, 
you are not guaranteed the same path back as the path taken out beyond 
the first hop or few in most cases.



-C

On 08/23/2017 12:10 PM, Aaron Gould wrote:

Thanks, opps, I forgot to tell y'all I tried "set protocols mpls
icmp-tunneling" already and it didn't work.

Also, I need to mention that the vrf between the (2) CE's is built on top of
a unidirectional rsvp lsp I'm testing rsvp te to learn about it and I
only built the lsp in one direction to influence traffic one-way... So
Chris's comments about "sure you have LSP's in both directions"  makes me
wonder if I do the return rsvp LSP for the underlying rsvp te would that fix
it ? (furthermore, must the return rsvp te lsp follow the exact same path
for traceroutes to work ?! this would seem really limiting)

I mean, I have LDP running in the core also, this might be obvious since the
vrf is functional, and I'm pretty sure I would need the mpls control plane
to work bidirectionally to have the vrf function as it is.

Let me know what y'all think.

Ce---peppppppece

---rsvp te from pe to pe >   this direction only... I
allow the igp to decide the return path in the opposite direction


-Aaron











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

Re: [j-nsp] vlan-ccc between ACX5048 and EX4500

[Jay Hanke]

Thanks for the help!

On Wed, Aug 23, 2017 at 4:32 PM, Pavel Lunin  wrote:
> Yes, EX4500/4550 chipset is not able to treat any additional tags of the
> MPLS packet.
>
> IIRC, they "officially support" (whatever it means) pseudowires and VPLS in
> EX4550 to EX4550 mode only thus it's nowhere documented that it pops the
> vlan tag by default and can't treat the control world.
>
> 23 авг. 2017 г. 11:16 PM пользователь "Jay Hanke" 
> написал:
>
>> Setting the control word worked right away. Is the issue lack of
>> support of the control word on one of the sides?
>>
>> On Wed, Aug 23, 2017 at 8:49 AM, Pavel Lunin  wrote:
>> >
>> >
>> > Try to add no-control-world under your l2circuit/neighbor/interface
>> > config
>> > on both sides (as well the VLAN push/pop on the ACX side).
>> >
>> > 2017-08-23 15:16 GMT+02:00 Jay Hanke :
>> >>
>> >> No luck. Here is the config I tried
>> >>
>> >> unit 517 {
>> >> encapsulation vlan-ccc;
>> >> vlan-id 517;
>> >> input-vlan-map pop;
>> >> output-vlan-map push;
>> >> }
>> >>
>> >>
>> >>
>> >> On Wed, Aug 23, 2017 at 6:38 AM, Enoch Nyatoti 
>> >> wrote:
>> >> > Hi,
>> >> >
>> >> > Can you try the following on your ACX5048 interface:
>> >> >
>> >> > set interfaces xe-0/0/46.517 input-vlan-map pop
>> >> > set interfaces xe-0/0/46.517 output-vlan-map push
>> >> >
>> >> > Best regards
>> >> > Enoch Nyatoti
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke
>> >> >  wrote:
>> >> >
>> >> >
>> >> > I'm having an issue where I'm unable to pass traffic through a
>> >> > vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
>> >> > boxes are working fine. The other circuits are ACX to ACX and EX to
>> >> > EX.
>> >> >
>> >> > PE1 (ex4500)
>> >> >
>> >> >
>> >> > l2circuit {
>> >> > neighbor 10.200.xx.xy {
>> >> > interface xe-0/0/1.517 {
>> >> > virtual-circuit-id 1171;
>> >> > mtu 9000;
>> >> > encapsulation-type ethernet-vlan;
>> >> > }
>> >> > }
>> >> > }
>> >> >
>> >> > xe-0/0/1 {
>> >> > vlan-tagging;
>> >> > mtu 9216;
>> >> > encapsulation vlan-ccc;
>> >> > unit 517 {
>> >> > encapsulation vlan-ccc;
>> >> > vlan-id 517;
>> >> > }
>> >> > }
>> >> >
>> >> > PE2 (ACX5048):
>> >> >
>> >> > l2circuit {
>> >> > neighbor 10.200.xx.xx {
>> >> > interface xe-0/0/46.517 {
>> >> > virtual-circuit-id 1171;
>> >> > mtu 9000;
>> >> > encapsulation-type ethernet-vlan;
>> >> > }
>> >> > }
>> >> > }
>> >> >
>> >> > xe-0/0/46 {
>> >> >
>> >> > vlan-tagging;
>> >> > mtu 9216;
>> >> > encapsulation flexible-ethernet-services;
>> >> >
>> >> > unit 517 {
>> >> > encapsulation vlan-ccc;
>> >> > vlan-id 517;
>> >> > }
>> >> > }
>> >> >
>> >> > I'm learning mac-addresses through the link on the PE2 side.
>> >> >
>> >> > The interface connected on the PE1 side doesn't learn anything.
>> >> >
>> >> > show l2circuit con shows the PW up on both PE devices.
>> >> >
>> >> > I've reloaded software on the EX4500 with the same result. There is
>> >> > one P router between the PE devices.
>> >> >
>> >> > All my existing PW are between EX4500 or between ACX. We don't have
>> >> > any working between systems with different models acting as PE
>> >> > devices. But quite a few working where PE devices are the same type.
>> >> >
>> >> > Any ideas?
>> >> >
>> >> > Jay
>> >> > ___
>> >> > 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
>> >
>> >
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] vlan-ccc between ACX5048 and EX4500

[Pavel Lunin]

Yes, EX4500/4550 chipset is not able to treat any additional tags of the
MPLS packet.

IIRC, they "officially support" (whatever it means) pseudowires and VPLS in
EX4550 to EX4550 mode only thus it's nowhere documented that it pops the
vlan tag by default and can't treat the control world.

23 авг. 2017 г. 11:16 PM пользователь "Jay Hanke" 
написал:

> Setting the control word worked right away. Is the issue lack of
> support of the control word on one of the sides?
>
> On Wed, Aug 23, 2017 at 8:49 AM, Pavel Lunin  wrote:
> >
> >
> > Try to add no-control-world under your l2circuit/neighbor/interface
> config
> > on both sides (as well the VLAN push/pop on the ACX side).
> >
> > 2017-08-23 15:16 GMT+02:00 Jay Hanke :
> >>
> >> No luck. Here is the config I tried
> >>
> >> unit 517 {
> >> encapsulation vlan-ccc;
> >> vlan-id 517;
> >> input-vlan-map pop;
> >> output-vlan-map push;
> >> }
> >>
> >>
> >>
> >> On Wed, Aug 23, 2017 at 6:38 AM, Enoch Nyatoti 
> wrote:
> >> > Hi,
> >> >
> >> > Can you try the following on your ACX5048 interface:
> >> >
> >> > set interfaces xe-0/0/46.517 input-vlan-map pop
> >> > set interfaces xe-0/0/46.517 output-vlan-map push
> >> >
> >> > Best regards
> >> > Enoch Nyatoti
> >> >
> >> >
> >> >
> >> >
> >> > On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke
> >> >  wrote:
> >> >
> >> >
> >> > I'm having an issue where I'm unable to pass traffic through a
> >> > vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
> >> > boxes are working fine. The other circuits are ACX to ACX and EX to
> >> > EX.
> >> >
> >> > PE1 (ex4500)
> >> >
> >> >
> >> > l2circuit {
> >> > neighbor 10.200.xx.xy {
> >> > interface xe-0/0/1.517 {
> >> > virtual-circuit-id 1171;
> >> > mtu 9000;
> >> > encapsulation-type ethernet-vlan;
> >> > }
> >> > }
> >> > }
> >> >
> >> > xe-0/0/1 {
> >> > vlan-tagging;
> >> > mtu 9216;
> >> > encapsulation vlan-ccc;
> >> > unit 517 {
> >> > encapsulation vlan-ccc;
> >> > vlan-id 517;
> >> > }
> >> > }
> >> >
> >> > PE2 (ACX5048):
> >> >
> >> > l2circuit {
> >> > neighbor 10.200.xx.xx {
> >> > interface xe-0/0/46.517 {
> >> > virtual-circuit-id 1171;
> >> > mtu 9000;
> >> > encapsulation-type ethernet-vlan;
> >> > }
> >> > }
> >> > }
> >> >
> >> > xe-0/0/46 {
> >> >
> >> > vlan-tagging;
> >> > mtu 9216;
> >> > encapsulation flexible-ethernet-services;
> >> >
> >> > unit 517 {
> >> > encapsulation vlan-ccc;
> >> > vlan-id 517;
> >> > }
> >> > }
> >> >
> >> > I'm learning mac-addresses through the link on the PE2 side.
> >> >
> >> > The interface connected on the PE1 side doesn't learn anything.
> >> >
> >> > show l2circuit con shows the PW up on both PE devices.
> >> >
> >> > I've reloaded software on the EX4500 with the same result. There is
> >> > one P router between the PE devices.
> >> >
> >> > All my existing PW are between EX4500 or between ACX. We don't have
> >> > any working between systems with different models acting as PE
> >> > devices. But quite a few working where PE devices are the same type.
> >> >
> >> > Any ideas?
> >> >
> >> > Jay
> >> > ___
> >> > 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
> >
> >
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] vlan-ccc between ACX5048 and EX4500

[Jay Hanke]

Setting the control word worked right away. Is the issue lack of
support of the control word on one of the sides?

On Wed, Aug 23, 2017 at 8:49 AM, Pavel Lunin  wrote:
>
>
> Try to add no-control-world under your l2circuit/neighbor/interface config
> on both sides (as well the VLAN push/pop on the ACX side).
>
> 2017-08-23 15:16 GMT+02:00 Jay Hanke :
>>
>> No luck. Here is the config I tried
>>
>> unit 517 {
>> encapsulation vlan-ccc;
>> vlan-id 517;
>> input-vlan-map pop;
>> output-vlan-map push;
>> }
>>
>>
>>
>> On Wed, Aug 23, 2017 at 6:38 AM, Enoch Nyatoti  wrote:
>> > Hi,
>> >
>> > Can you try the following on your ACX5048 interface:
>> >
>> > set interfaces xe-0/0/46.517 input-vlan-map pop
>> > set interfaces xe-0/0/46.517 output-vlan-map push
>> >
>> > Best regards
>> > Enoch Nyatoti
>> >
>> >
>> >
>> >
>> > On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke
>> >  wrote:
>> >
>> >
>> > I'm having an issue where I'm unable to pass traffic through a
>> > vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
>> > boxes are working fine. The other circuits are ACX to ACX and EX to
>> > EX.
>> >
>> > PE1 (ex4500)
>> >
>> >
>> > l2circuit {
>> > neighbor 10.200.xx.xy {
>> > interface xe-0/0/1.517 {
>> > virtual-circuit-id 1171;
>> > mtu 9000;
>> > encapsulation-type ethernet-vlan;
>> > }
>> > }
>> > }
>> >
>> > xe-0/0/1 {
>> > vlan-tagging;
>> > mtu 9216;
>> > encapsulation vlan-ccc;
>> > unit 517 {
>> > encapsulation vlan-ccc;
>> > vlan-id 517;
>> > }
>> > }
>> >
>> > PE2 (ACX5048):
>> >
>> > l2circuit {
>> > neighbor 10.200.xx.xx {
>> > interface xe-0/0/46.517 {
>> > virtual-circuit-id 1171;
>> > mtu 9000;
>> > encapsulation-type ethernet-vlan;
>> > }
>> > }
>> > }
>> >
>> > xe-0/0/46 {
>> >
>> > vlan-tagging;
>> > mtu 9216;
>> > encapsulation flexible-ethernet-services;
>> >
>> > unit 517 {
>> > encapsulation vlan-ccc;
>> > vlan-id 517;
>> > }
>> > }
>> >
>> > I'm learning mac-addresses through the link on the PE2 side.
>> >
>> > The interface connected on the PE1 side doesn't learn anything.
>> >
>> > show l2circuit con shows the PW up on both PE devices.
>> >
>> > I've reloaded software on the EX4500 with the same result. There is
>> > one P router between the PE devices.
>> >
>> > All my existing PW are between EX4500 or between ACX. We don't have
>> > any working between systems with different models acting as PE
>> > devices. But quite a few working where PE devices are the same type.
>> >
>> > Any ideas?
>> >
>> > Jay
>> > ___
>> > 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
>
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] traceroute in mpls vpn's not showing P hops

[Aaron Gould]

Thanks, opps, I forgot to tell y'all I tried "set protocols mpls
icmp-tunneling" already and it didn't work.  

Also, I need to mention that the vrf between the (2) CE's is built on top of
a unidirectional rsvp lsp I'm testing rsvp te to learn about it and I
only built the lsp in one direction to influence traffic one-way... So
Chris's comments about "sure you have LSP's in both directions"  makes me
wonder if I do the return rsvp LSP for the underlying rsvp te would that fix
it ? (furthermore, must the return rsvp te lsp follow the exact same path
for traceroutes to work ?! this would seem really limiting)

I mean, I have LDP running in the core also, this might be obvious since the
vrf is functional, and I'm pretty sure I would need the mpls control plane
to work bidirectionally to have the vrf function as it is.

Let me know what y'all think.

Ce---peppppppece

---rsvp te from pe to pe >   this direction only... I
allow the igp to decide the return path in the opposite direction


-Aaron








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

Re: [j-nsp] mx480, netflow/version9 ipv6 help

[Justin M. Streiner]

On Wed, 23 Aug 2017, John Brown wrote:


yes, sorry I forgot to include that
fpc 1 {
   sampling-instance 1to1;


Be very careful with 1:1 sampling if that's what you are in fact doing. 
In most of the cases that come to mind, 1:1 sampling isn't necessary to 
get the data you need for things like traffic visualization/capacity 
planning.  Beyond perhaps very small traffic levels, it might not be 
supported at all.


jms


   inline-services {

   flow-table-size {

   ipv4-flow-table-size 5;

   ipv6-flow-table-size 5;

   }

   }

}

fpc 2 {

   sampling-instance 1to1;

   inline-services {

   flow-table-size {

   ipv4-flow-table-size 5;

   ipv6-flow-table-size 5;

   }

   }

}


On Wed, Aug 23, 2017 at 9:46 AM, Alvaro Pereira  wrote:

Hi John,

Do you have the following configured on the fpc you have installed?
ATTENTION! THIS WILL AUTOMATICALLY REBOOT THE FPC !!!

https://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/ipv6-flow-table-size.html

Note: Any change in the configured size of the flow hash table sizes
initiates an automatic reboot of the FPC.

set chassis fpc 0 inline-services flow-table-size ipv4-flow-table-size 12
set chassis fpc 0 inline-services flow-table-size ipv6-flow-table-size 3

You might want to play with the numbers depending on your use case.

Alvaro

On Wed, Aug 23, 2017 at 7:17 AM, John Brown  wrote:


Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
error from Junos.
Any help is much appreciated.  THANK YOU

Junos: 14.2R1.9

Error from commit check

 sampling inline configuration error
Can't configure inline output with V5, V8 and V9 collector
configured for family inet6

Config snip

family inet {
output {
flow-server 192.168.1.2 {
port 2055;
version9 {
template {
ipv4;
}
}
}
inline-jflow {
source-address 10.0.0.1;
}
}
}
family inet6 {
output {
flow-server 192.168.1.2 {
port 2055;
version9 {
template {
ipv6;
}
}
}
inline-jflow {
source-address 10.0.0.1;
}
}
}

flow-monitoring {
version9 {
template ipv4 {
ipv4-template;
}
template ipv6 {
ipv6-template;
}
}
___
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


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

Re: [j-nsp] mx480, netflow/version9 ipv6 help

[John Brown]

Not sure my flow collector (a ELK based config) will properly handle IP-FIX

On Wed, Aug 23, 2017 at 9:48 AM,   wrote:
>> Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
>> error from Junos.
>> Any help is much appreciated.  THANK YOU
>
> We are exporting IPv6 netflow info using IPfix - haven't tried v9.
> Seems to work for us. In your config, try replacing all "version9"
> occurrences with "version-ipfix".
>
> Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] mx480, netflow/version9 ipv6 help

[John Brown]

yes, sorry I forgot to include that

fpc 1 {

sampling-instance 1to1;

inline-services {

flow-table-size {

ipv4-flow-table-size 5;

ipv6-flow-table-size 5;

}

}

}

fpc 2 {

sampling-instance 1to1;

inline-services {

flow-table-size {

ipv4-flow-table-size 5;

ipv6-flow-table-size 5;

}

}

}


On Wed, Aug 23, 2017 at 9:46 AM, Alvaro Pereira  wrote:
> Hi John,
>
> Do you have the following configured on the fpc you have installed?
> ATTENTION! THIS WILL AUTOMATICALLY REBOOT THE FPC !!!
>
> https://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/ipv6-flow-table-size.html
>
> Note: Any change in the configured size of the flow hash table sizes
> initiates an automatic reboot of the FPC.
>
> set chassis fpc 0 inline-services flow-table-size ipv4-flow-table-size 12
> set chassis fpc 0 inline-services flow-table-size ipv6-flow-table-size 3
>
> You might want to play with the numbers depending on your use case.
>
> Alvaro
>
> On Wed, Aug 23, 2017 at 7:17 AM, John Brown  wrote:
>>
>> Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
>> error from Junos.
>> Any help is much appreciated.  THANK YOU
>>
>> Junos: 14.2R1.9
>>
>> Error from commit check
>>
>>  sampling inline configuration error
>> Can't configure inline output with V5, V8 and V9 collector
>> configured for family inet6
>>
>> Config snip
>>
>> family inet {
>> output {
>> flow-server 192.168.1.2 {
>> port 2055;
>> version9 {
>> template {
>> ipv4;
>> }
>> }
>> }
>> inline-jflow {
>> source-address 10.0.0.1;
>> }
>> }
>> }
>> family inet6 {
>> output {
>> flow-server 192.168.1.2 {
>> port 2055;
>> version9 {
>> template {
>> ipv6;
>> }
>> }
>> }
>> inline-jflow {
>> source-address 10.0.0.1;
>> }
>> }
>> }
>>
>> flow-monitoring {
>> version9 {
>> template ipv4 {
>> ipv4-template;
>> }
>> template ipv6 {
>> ipv6-template;
>> }
>> }
>> ___
>> 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] mx480, netflow/version9 ipv6 help

[sthaug]

> Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
> error from Junos.
> Any help is much appreciated.  THANK YOU

We are exporting IPv6 netflow info using IPfix - haven't tried v9.
Seems to work for us. In your config, try replacing all "version9"
occurrences with "version-ipfix".

Steinar Haug, Nethelp consulting, sth...@nethelp.no
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] mx480, netflow/version9 ipv6 help

[Alvaro Pereira]

Hi John,

Do you have the following configured on the fpc you have installed? *ATTENTION!
THIS WILL AUTOMATICALLY REBOOT THE FPC !!!*

https://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/ipv6-flow-table-size.html

*Note: *Any change in the configured size of the flow hash table sizes
initiates an automatic reboot of the FPC.

set chassis fpc 0 inline-services flow-table-size ipv4-flow-table-size 12
set chassis fpc 0 inline-services flow-table-size ipv6-flow-table-size 3

You might want to play with the numbers depending on your use case.

Alvaro

On Wed, Aug 23, 2017 at 7:17 AM, John Brown  wrote:

> Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
> error from Junos.
> Any help is much appreciated.  THANK YOU
>
> Junos: 14.2R1.9
>
> Error from commit check
>
>  sampling inline configuration error
> Can't configure inline output with V5, V8 and V9 collector
> configured for family inet6
>
> Config snip
>
> family inet {
> output {
> flow-server 192.168.1.2 {
> port 2055;
> version9 {
> template {
> ipv4;
> }
> }
> }
> inline-jflow {
> source-address 10.0.0.1;
> }
> }
> }
> family inet6 {
> output {
> flow-server 192.168.1.2 {
> port 2055;
> version9 {
> template {
> ipv6;
> }
> }
> }
> inline-jflow {
> source-address 10.0.0.1;
> }
> }
> }
>
> flow-monitoring {
> version9 {
> template ipv4 {
> ipv4-template;
> }
> template ipv6 {
> ipv6-template;
> }
> }
> ___
> 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

[j-nsp] mx480, netflow/version9 ipv6 help

[John Brown]

Hi,  I'm trying to add IPv6 to my flow picture and I'm getting an
error from Junos.
Any help is much appreciated.  THANK YOU

Junos: 14.2R1.9

Error from commit check

 sampling inline configuration error
Can't configure inline output with V5, V8 and V9 collector
configured for family inet6

Config snip

family inet {
output {
flow-server 192.168.1.2 {
port 2055;
version9 {
template {
ipv4;
}
}
}
inline-jflow {
source-address 10.0.0.1;
}
}
}
family inet6 {
output {
flow-server 192.168.1.2 {
port 2055;
version9 {
template {
ipv6;
}
}
}
inline-jflow {
source-address 10.0.0.1;
}
}
}

flow-monitoring {
version9 {
template ipv4 {
ipv4-template;
}
template ipv6 {
ipv6-template;
}
}
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] vlan-ccc between ACX5048 and EX4500

[Pavel Lunin]

Try to add no-control-world under your l2circuit/neighbor/interface config
on both sides (as well the VLAN push/pop on the ACX side).

2017-08-23 15:16 GMT+02:00 Jay Hanke :

> No luck. Here is the config I tried
>
> unit 517 {
> encapsulation vlan-ccc;
> vlan-id 517;
> input-vlan-map pop;
> output-vlan-map push;
> }
>
>
>
> On Wed, Aug 23, 2017 at 6:38 AM, Enoch Nyatoti  wrote:
> > Hi,
> >
> > Can you try the following on your ACX5048 interface:
> >
> > set interfaces xe-0/0/46.517 input-vlan-map pop
> > set interfaces xe-0/0/46.517 output-vlan-map push
> >
> > Best regards
> > Enoch Nyatoti
> >
> >
> >
> >
> > On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke
> >  wrote:
> >
> >
> > I'm having an issue where I'm unable to pass traffic through a
> > vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
> > boxes are working fine. The other circuits are ACX to ACX and EX to
> > EX.
> >
> > PE1 (ex4500)
> >
> >
> > l2circuit {
> > neighbor 10.200.xx.xy {
> > interface xe-0/0/1.517 {
> > virtual-circuit-id 1171;
> > mtu 9000;
> > encapsulation-type ethernet-vlan;
> > }
> > }
> > }
> >
> > xe-0/0/1 {
> > vlan-tagging;
> > mtu 9216;
> > encapsulation vlan-ccc;
> > unit 517 {
> > encapsulation vlan-ccc;
> > vlan-id 517;
> > }
> > }
> >
> > PE2 (ACX5048):
> >
> > l2circuit {
> > neighbor 10.200.xx.xx {
> > interface xe-0/0/46.517 {
> > virtual-circuit-id 1171;
> > mtu 9000;
> > encapsulation-type ethernet-vlan;
> > }
> > }
> > }
> >
> > xe-0/0/46 {
> >
> > vlan-tagging;
> > mtu 9216;
> > encapsulation flexible-ethernet-services;
> >
> > unit 517 {
> > encapsulation vlan-ccc;
> > vlan-id 517;
> > }
> > }
> >
> > I'm learning mac-addresses through the link on the PE2 side.
> >
> > The interface connected on the PE1 side doesn't learn anything.
> >
> > show l2circuit con shows the PW up on both PE devices.
> >
> > I've reloaded software on the EX4500 with the same result. There is
> > one P router between the PE devices.
> >
> > All my existing PW are between EX4500 or between ACX. We don't have
> > any working between systems with different models acting as PE
> > devices. But quite a few working where PE devices are the same type.
> >
> > Any ideas?
> >
> > Jay
> > ___
> > 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
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] vlan-ccc between ACX5048 and EX4500

[Jay Hanke]

No luck. Here is the config I tried

unit 517 {
encapsulation vlan-ccc;
vlan-id 517;
input-vlan-map pop;
output-vlan-map push;
}



On Wed, Aug 23, 2017 at 6:38 AM, Enoch Nyatoti  wrote:
> Hi,
>
> Can you try the following on your ACX5048 interface:
>
> set interfaces xe-0/0/46.517 input-vlan-map pop
> set interfaces xe-0/0/46.517 output-vlan-map push
>
> Best regards
> Enoch Nyatoti
>
>
>
>
> On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke
>  wrote:
>
>
> I'm having an issue where I'm unable to pass traffic through a
> vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
> boxes are working fine. The other circuits are ACX to ACX and EX to
> EX.
>
> PE1 (ex4500)
>
>
> l2circuit {
> neighbor 10.200.xx.xy {
> interface xe-0/0/1.517 {
> virtual-circuit-id 1171;
> mtu 9000;
> encapsulation-type ethernet-vlan;
> }
> }
> }
>
> xe-0/0/1 {
> vlan-tagging;
> mtu 9216;
> encapsulation vlan-ccc;
> unit 517 {
> encapsulation vlan-ccc;
> vlan-id 517;
> }
> }
>
> PE2 (ACX5048):
>
> l2circuit {
> neighbor 10.200.xx.xx {
> interface xe-0/0/46.517 {
> virtual-circuit-id 1171;
> mtu 9000;
> encapsulation-type ethernet-vlan;
> }
> }
> }
>
> xe-0/0/46 {
>
> vlan-tagging;
> mtu 9216;
> encapsulation flexible-ethernet-services;
>
> unit 517 {
> encapsulation vlan-ccc;
> vlan-id 517;
> }
> }
>
> I'm learning mac-addresses through the link on the PE2 side.
>
> The interface connected on the PE1 side doesn't learn anything.
>
> show l2circuit con shows the PW up on both PE devices.
>
> I've reloaded software on the EX4500 with the same result. There is
> one P router between the PE devices.
>
> All my existing PW are between EX4500 or between ACX. We don't have
> any working between systems with different models acting as PE
> devices. But quite a few working where PE devices are the same type.
>
> Any ideas?
>
> Jay
> ___
> 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

[j-nsp] 10Gbps xe interface to 20Gbps ae interface

[Matt Freitag]

Hi all,

I'm wondering if anybody had any issues on an MX480 (13.3R9) moving a
single xe interface to an aggregated ethernet bundle of 2 xe interfaces.
These interfaces go to an EX virtual chassis. I already made the ae
interface on the switch side and assigned all the relevant VLANs.

Specifically my change plan for the MX reads:
top rename interfaces xe-1/0/0 to ae0
top replace pattern xe-1/0/0 with ae0

Generally I'm wondering what people's experiences with this have been.
Good/bad/ugly/indifferent...?

Thanks for the time! Let me know if you need more info.

Matt Freitag
Network Engineer
Information Technology
Michigan Technological University
(906) 487-3696 <%28906%29%20487-3696>
https://www.mtu.edu/
https://www.mtu.edu/it
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] vlan-ccc between ACX5048 and EX4500

[Enoch Nyatoti via juniper-nsp]

Hi,
Can you try the following on your ACX5048 interface:
  set interfaces xe-0/0/46.517input-vlan-map popset interfaces 
xe-0/0/46.517output-vlan-map push 
 Best regards
Enoch Nyatoti




On Wednesday, August 23, 2017, 7:51:21 AM GMT+1, Jay Hanke  
wrote:

I'm having an issue where I'm unable to pass traffic through a
vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
boxes are working fine. The other circuits are ACX to ACX and EX to
EX.

PE1 (ex4500)


l2circuit {
    neighbor 10.200.xx.xy {
        interface xe-0/0/1.517 {
            virtual-circuit-id 1171;
            mtu 9000;
            encapsulation-type ethernet-vlan;
        }
    }
}

xe-0/0/1 {
    vlan-tagging;
    mtu 9216;
    encapsulation vlan-ccc;
    unit 517 {
        encapsulation vlan-ccc;
        vlan-id 517;
    }
}

PE2 (ACX5048):

l2circuit {
    neighbor 10.200.xx.xx {
        interface xe-0/0/46.517 {
            virtual-circuit-id 1171;
            mtu 9000;
            encapsulation-type ethernet-vlan;
        }
    }
}

xe-0/0/46 {

    vlan-tagging;
    mtu 9216;
    encapsulation flexible-ethernet-services;

    unit 517 {
        encapsulation vlan-ccc;
        vlan-id 517;
    }
}

I'm learning mac-addresses through the link on the PE2 side.

The interface connected on the PE1 side doesn't learn anything.

show l2circuit con shows the PW up on both PE devices.

I've reloaded software on the EX4500 with the same result. There is
one P router between the PE devices.

All my existing PW are between EX4500 or between ACX. We don't have
any working between systems with different models acting as PE
devices. But quite a few working where PE devices are the same type.

Any ideas?

Jay
___
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

[j-nsp] vlan-ccc between ACX5048 and EX4500

[Jay Hanke]

I'm having an issue where I'm unable to pass traffic through a
vlan-ccc between an ACX5048 and an EX4500. Other circuits on same
boxes are working fine. The other circuits are ACX to ACX and EX to
EX.

PE1 (ex4500)


l2circuit {
neighbor 10.200.xx.xy {
interface xe-0/0/1.517 {
virtual-circuit-id 1171;
mtu 9000;
encapsulation-type ethernet-vlan;
}
}
}

xe-0/0/1 {
vlan-tagging;
mtu 9216;
encapsulation vlan-ccc;
unit 517 {
encapsulation vlan-ccc;
vlan-id 517;
}
}

PE2 (ACX5048):

l2circuit {
neighbor 10.200.xx.xx {
interface xe-0/0/46.517 {
virtual-circuit-id 1171;
mtu 9000;
encapsulation-type ethernet-vlan;
}
}
}

xe-0/0/46 {

vlan-tagging;
mtu 9216;
encapsulation flexible-ethernet-services;

unit 517 {
encapsulation vlan-ccc;
vlan-id 517;
}
}

I'm learning mac-addresses through the link on the PE2 side.

The interface connected on the PE1 side doesn't learn anything.

show l2circuit con shows the PW up on both PE devices.

I've reloaded software on the EX4500 with the same result. There is
one P router between the PE devices.

All my existing PW are between EX4500 or between ACX. We don't have
any working between systems with different models acting as PE
devices. But quite a few working where PE devices are the same type.

Any ideas?

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