[j-nsp] Fwd: MX80 Q-in-Q
Bjørn Skovlund
skovlund at gmail.com
Tue Jan 22 01:57:10 EST 2013
Your question is still a bit ambiguous.
If you have an inner-list and want to bind it to a L3 interface, then you
need to make a bridge domain and attach the IRB to that.
Alternatively, depending on what you want, we're doing something along the
lines of the below, where we bind customers together in DHCP groups and
relay them to a DHCP server with option-82, so we know which customer gets
what IP - again, not sure if it's customers or what that you're trying to
stitch together ;-)
Cheers, Bjørn
unit 301 {
proxy-arp restricted;
vlan-tags outer 1198 inner 42;
family inet {
mac-validate strict;
unnumbered-address lo0.0 preferred-source-address x.x.x.x;
}
}
and under forwarding-options dhcp-relay:
group data {
active-server-group data;
overrides {
always-write-option-82;
}
relay-option-82 {
circuit-id {
use-interface-description logical;
}
}
interface ge-0/0/0.301;
......
}
On Mon, Jan 21, 2013 at 11:23 PM, lppmaster at yandex.ru <lppmaster at ya.ru>wrote:
> Thanks for the reply.
> I need to terminate Q-in-Q with multiple internal tags.
> inner-list
> Junos 11.4R1.14
> Allows you to create only if the interface will be family bridge,
> I need a L3 interface.
>
> 21.01.2013, 18:55, "sthaug at nethelp.no" <sthaug at nethelp.no>:
>
> >> Does MX ambiguous vlan?
> > Please rephrase the question.
> >
> > If you're asking whether the MX80 supports dual port Ethernet
> > traffic, the answer is yes. E.g.
> >
> > ge-1/0/0 {
> > flexible-vlan-tagging;
> > encapsulation flexible ethernet services;
> > unit 11 {
> > vlan tags outer 1063 inner 900;
> > family inet {
> > address 10.9.130.1/30;
> > }
> > }
> > }
> >
> > Steinar Haug, Nethelp consulting, sthaug at nethelp.no
>
> -------- Завершение пересылаемого сообщения --------
> _______________________________________________
> 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