[j-nsp] Juniper MX80 IRB
magno
massimo.magnani at gmail.com
Tue Jul 27 09:46:41 EDT 2010
Today Trio only supports the old style config. in the near future, the
new style config will be supported as well.
Cheers
Max
On 27/07/2010, Chuck Anderson <cra at wpi.edu> wrote:
> On Tue, Jul 27, 2010 at 10:40:54AM +0200, Tim Vollebregt wrote:
>> I'm getting errors when changing to this configuration. It is only
>> possible to use encapsulation vlan-bridge on unit 0. And when I
>> change it to unit 0:
>>
>> <message>VLAN Encapsulation: Not allowed on untagged interfaces</message>
>> </xnm:error>
>
> This following commits for me. The point of the exercise is to see if
> MPC Trio cards *require* 9.2-style configurations: using separate
> logical units for each VLAN, encapsulation vlan-bridge, refer to all
> the logical unit interfaces in bridge-domain in order to actually
> function. I.e. do they not work with 9.5+ style VLAN Bundles: family
> bridge, interface-mode access/trunk, vlan-id-list? In my experience
> with testing some new MPC Trio cards, this conclusion is true. A
> perfectly working VLAN Bundle bridging configuration on DPC cards
> failed miserably when copied over to MPC cards until it was
> reconfigured the 9.2 non-VLAN Bundled way.
>
> ge-2/0/1 {
> flexible-vlan-tagging;
> native-vlan-id 200;
> encapsulation flexible-ethernet-services;
> unit 200 {
> encapsulation vlan-bridge;
> vlan-id 200;
> }
> }
> irb {
> unit 200 {
> family inet {
> address 10.11.12.13/24;
> }
> }
> }
> VLAN200 {
> domain-type bridge;
> vlan-id 200;
> interface ge-2/0/1.200;
> routing-interface irb.200;
> }
>
>> This issue seems to be really strange as we have it working the 10.x
>> way on another router. When I configure Ge-1/0/0 as a routed
>> interface it works fine.
>
> Does the other router where this works have the new MPC Trio cards?
> Or is it using the older DPC cards?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list