Aaron Thanks a lot
Our problem is related to pass more than one vlan to the same vpls instance. We have some projects here that depends of it We will talk with juniper TAC and PLM to see the software roadmap of this box There is no chance to use this box in projects with this limitation, because other vendors with the same chipset have this feature running ok. It looks like to be a junos feature missing not a technical limitation ... Hope so !!! Thanks a lot anyway Att Giuliano Sent from my iPhone > On Feb 5, 2016, at 02:07, Aaron <[email protected]> wrote: > > Hi Giuliano, > > I'm new to Juniper and learning as I go....but I'll at least show you what > is in my lab. I have a functioning vpls routing-instance that is working > with ... ACX5048, MX104, Cisco ASR9006, Cisco ME3600... > > My acx5048 looks like this... here's some bits from the config... > > gvtc@eng-lab-acx5048-1> show version > fpc0: > -------------------------------------------------------------------------- > Hostname: eng-lab-acx5048-1 > Model: acx5048 > Junos: 15.1X54-D20.7 > > set interfaces ge-0/0/1 speed 100m > set interfaces ge-0/0/1 encapsulation ethernet-vpls > set interfaces ge-0/0/1 unit 0 family vpls > > (not shown here is the required, IGP (ospf), MPLS, ldp... that was simple) > > set protocols bgp group ibgp type internal > set protocols bgp group ibgp local-address 10.101.12.245 > set protocols bgp group ibgp family inet-vpn unicast > set protocols bgp group ibgp family l2vpn auto-discovery-only > set protocols bgp group ibgp neighbor 10.101.0.254 local-as 64512 > > gvtc@eng-lab-acx5048-1> show configuration | display set | match > "routing-instances vlan100" > set routing-instances vlan100 instance-type vpls > set routing-instances vlan100 interface ge-0/0/1.0 > set routing-instances vlan100 route-distinguisher 10.101.12.245:32768 > set routing-instances vlan100 l2vpn-id l2vpn-id:65535:10100 > set routing-instances vlan100 vrf-target target:65535:10100 > set routing-instances vlan100 protocols vpls no-tunnel-services > > gvtc@eng-lab-acx5048-1> show vpls connections brief > Layer-2 VPN connections: > .... > Instance: vlan100 > L2vpn-id: 65535:10100 > Local-id: 10.101.12.245 > Remote-id Type St Time last up # Up trans > 10.101.0.254 rmt Up Feb 5 05:59:29 2016 1 > 10.101.12.246 rmt Up Feb 5 05:59:29 2016 1 > 10.101.12.248 rmt Up Feb 5 05:59:29 2016 1 > 10.101.12.250 rmt Up Feb 5 05:59:29 2016 1 > 10.101.12.251 rmt Up Feb 5 05:59:29 2016 1 > > Aaron > > -----Original Message----- > From: juniper-nsp [mailto:[email protected]] On Behalf Of > Giuliano Medalha > Sent: Thursday, February 4, 2016 9:17 PM > To: [email protected] > Subject: [j-nsp] Acx5048 vpls vlan-id > > People > > We are trying to configure vpls routing-instance in a ACX5048 box > > But the following command does not work after commit ... > > Routing-instances { > VPLS-1 { > instance-type vpls; > ## > ## Warning: statement ignored: unsupported platform (acx5048) > ## > vlan-id all; > ## > ## Warning: vlan-id-range is specified for this logical interface; > 'vlan-id all' should also be enabled > ## > interface ae0.50; > route-distinguisher .... > > > Is there another way to configure this feature ? > > Because on MX works OK and it is pretty simple > > Thanks a lot > > Giuliano > _______________________________________________ > 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
