[j-nsp] ccc interface in logical-systems
Eduardo Schoedler
listas at esds.com.br
Wed May 25 14:51:39 EDT 2016
2016-05-25 6:15 GMT-03:00 Mark Tinka <mark.tinka at seacom.mu>:
>
>
> On 25/May/16 11:10, Anand Anand wrote:
>
>> Hi,
>>
>> Im trying to test l2vpn in logical system. when configuring vlan-ccc for
>> the interface within the logical system, i get an error. if i do the same
>> in the global configuration, it commits fine.
>>
>> missing anything?
>>
>> lab# show logical-systems pe1 interfaces ge-0/0/3
>> unit 0 {
>> encapsulation vlan-ccc;
>> vlan-id 512;
>> family ccc;
>> }
>>
>> [edit]
>> lab# show interfaces ge-0/0/3
>> vlan-tagging;
>> encapsulation flexible-ethernet-services;
>>
>> [edit]
>> lab# commit check
>> [edit logical-systems pe1 interfaces ge-0/0/3 unit 0]
>> 'family'
>> Only the CCC family is allowed on CCC interfaces
>> error: configuration check-out failed
>
> Looks alright.
>
> The only I'd try is "flexible-vlan-tagging" instead of "vlan-tagging".
Hi,
Hijacking a little bit this thread, can I provide a vpls with irb
interface from a logical-system to use it into the "main system"
(outside the logical system)?
How can I do this?
login at jnpr> show configuration logical-systems TEST-MPLS
interfaces {
ge-1/1/0 {
unit 0 {
family inet {
mtu 1500;
address 192.168.0.1/30;
}
family mpls;
}
}
irb {
unit 666 {
family inet {
address 10.x.x.20/24;
}
}
}
lo0 {
unit 666 {
family inet {
address 172.16.2.2/32;
}
}
}
}
routing-instances {
TRANSPORT {
instance-type vpls;
vlan-id 666;
routing-interface irb.666;
protocols {
vpls {
no-tunnel-services;
vpls-id 1122;
neighbor 172.16.1.1;
connectivity-type irb;
}
}
}
}
This configuration is working.
Thank you.
--
Eduardo Schoedler
More information about the juniper-nsp
mailing list