Re: [j-nsp] Prepending customer AS results in AS23456

23456 was reserved as a compatibility ASN to sort of make things compatible with 2-byte implementations. There is a lot of information on the interweb so I wont go into detail here. Phil From: Markus Sent: ‎Wednesday‎, ‎May‎ ‎21‎, ‎2014 ‎5‎:‎33‎ ‎PM To: juniper-nsp@puck.nether.net List

[j-nsp] ACX Series Routers (BGP MPLS L3 VPN RFC 2547bis)

​People, Does anyone using ACX Series considering BGP MPLS L3 VPN (RFC 2547 bis) ? It has some limitation ? Any feature not available ? And about the scalability ? It works fine ?​ Could you please share some practical and real experience ? How many VRF ? Max PPS ? The ASX does use any

Re: [j-nsp] Prepending customer AS results in AS23456

PS: On a second thought, of course as-path-prepend will make the session get dropped by the remote router, because my AS is not first in the path anymore. My mistake, so please ignore that. I checked some more looking glasses in the meantime and I can see my-upstream my-asn 22 at some of t

[j-nsp] Prepending customer AS results in AS23456

Hi list! I'm trying to prepend a customers 4-byte ASN to their prefixes. JunOS 12.3R2.5 on M7i. This is my config, simplified: [routing-options static] route a.a.a.a/22 { next-hop b.b.b.b; readvertise; } [policy-options] policy-statement UPSTREAM-OUT { term 1 { from {

Re: [j-nsp] MACsec on EX switches

Looks like this topic is not very popular :( For EX4200 you need to have MACSec enabled uplink module! You also need Controlled version of Junos which should be obtained from your representative in Juniper and is not downloadable from the web. If you face any bugs it could potentially take longer