I want to make logical interfaces on a physical interface ge-0/2/0 of a Juniper M10 router to connected to a the trunk port of a Summit Extreme x450 with the ethertype 0x88a8 (IEEE 802.1ad).
I have the following configuration on the router.
ge-0/2/0 {
vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50;
family inet {
address 192.168.175.169/28;
}
}
}
I made the test with the 802.1q and it works but with 802.1ad didn't work.
Best regards.
_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx
_______________________________________________
juniper-nsp mailing list junip...@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Physical interface: ae0, Enabled, Physical link is Up
Logical interface ae0.50 (Index 73) (SNMP ifIndex 133)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.50 ] Encapsulation: ENET2
onam@M10# run show interfaces terse | match ae0
ge-0/2/0.50 up up aenet --> ae0.50
ge-0/2/0.32767 up up aenet --> ae0.32767
ae0 up up
ae0.50 up up inet 192.168.175.169/28
ae0.32767 up up
That is dot1q so I configure to 0x88a8 ethertype.
onam@M10# show interfaces ae0
vlan-tagging;
aggregated-ether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50;
family inet {
address 192.168.175.169/28;
}
}
Logical interface ae0.50 (Index 75) (SNMP ifIndex 133)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x88a8.50 ] Encapsulation: ENET2
And I would like to know why is strange enviorement, I think is good opotunity to improve.
Thanks.
> Subject: Re: [j-nsp] Logical Interfaces 802.1ad
> From: aaron....@gmail.com
> Date: Sun, 18 Oct 2009 18:07:25 -0700
> CC: junip...@puck.nether.net
> To: onam...@hotmail.com
>
>
> If you're using 802.3ad, you'll need something more like this:
>
> chassis {
> aggregated-devices {
> ethernet {
> device-count 1;
> }
> }
> }
> interfaces {
> ae0 {
> vlan-tagging;
> unit 50 {
> vlan-id 50;
> family inet {
> address 192.168.175.169/28;
> }
> }
> ge-0/2/0 {
> gigether-options {
> 802.3ad ae0;
> }
> }
> }
>
> i.e. you need to create the logical bundle interface (aggregated
> ethernet, ae0), then tie ge-0/2/0 into the bundle, and do your
> configuration on the bundle (ae0). There's no need to override the
> tag-protocol-id or the outer tag unless you're in a really strange
> environment.
>
> Aaron
_________________________________________________________________
Connect to the next generation of MSN Messenger
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
onam@M10> show configuration interfaces ge-0/2/0
gigether-options {
802.3ad ae0;
}
onam@M10>
what kind of strange situations?
I read at j-nsp that M series is 802.1q bye default and J series is 0x9100.
onam@M10>
> Subject: Re: [j-nsp] Logical Interfaces 802.1ad
> From: aaron....@gmail.com
> Date: Sun, 18 Oct 2009 19:49:36 -0700
> CC: junip...@puck.nether.net
> To: onam...@hotmail.com
>
>
> The ethertype should be automatic except in strange situations. it
> should be unneeded to configure that.
>
> Also, make sure you have removed other configuration from ge-0/2/0,
> the only thing there should be gigether-options 802.3ad ae0.
I made some test before with this ethertype and it works. The Extreme x450 use both of them 0x8100 for VLAN and 0x88a8 for VMAN so if i do that the VMAN will become a VLAN.
I see that by default the Juniper router M10 use ethertype 0x8100, but when I try to use ethertype 0x88a8 the devices doens't see each other, I run a ping to the other side with no response.
> Date: Mon, 19 Oct 2009 09:58:23 +0300
> From: evg...@ip.datagroup.ua
> To: onam...@hotmail.com
> CC: junip...@puck.nether.net
> Subject: Re: [j-nsp] Logical Interfaces 802.1ad
>
> Hello Onam,
> try to change ethertype from Summit side:
>
> configure vman ethertype 0x8100
>
> best regards,
> --
> Evgeniy Aikashev
> network engineer
> JSC DATAGROUP
evgeniy@mx480> show configuration interfaces xe-4/1/0
description "=== Summit X650 test ===";
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 100 {
description "=== Summit X650 test ===";
vlan-tags outer 4092 inner 100;
family inet {
address x.x.x.x/30;
}
}
and from Summit side
configure vman ethertype 0x8100
>so if i do that the VMAN will become a VLAN.
You simply change tag and VMAN won't became a vlan. IMHO
I'll try to change ethertype from Juniper and work default from Summit.
best regards,
--
Evgeniy Aikashev
network engineer
JSC DATAGROUP
> Get news, entertainment and everything you care about at Live.com. Check it out!
I will try this configuration.
If I chance the ethertype of the VMAN, this will chance the etherype of all my VMAN's and the other's Summit won't reach this one. IMHO
Best regards.
> Date: Mon, 19 Oct 2009 10:34:11 +0300
> From: evg...@ip.datagroup.ua
> To: onam...@hotmail.com
> CC: junip...@puck.nether.net
> Subject: Re[2]: [j-nsp] Logical Interfaces 802.1ad
_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us
{master}[edit interfaces xe-4/1/0]
evgeniy@mx480# show
description "=== Summit X650 test ===";
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 100 {
description "=== Summit X650 test ===";
vlan-tags outer 0x88a8.4092 inner 100;
family inet {
address x.x.x.x/30;
}
}
Summit:
enable jumbo-frame ports all
best regards,
--
Evgeniy Aikashev
network engineer
JSC DATAGROUP
> Get news, entertainment and everything you care about at Live.com. Check it out!
Maybe there is something I am doing wrong.
Best regards.
> Date: Mon, 19 Oct 2009 10:47:16 +0300
> From: evg...@ip.datagroup.ua
> To: onam...@hotmail.com
> CC: junip...@puck.nether.net
> Subject: Re[2]: [j-nsp] Logical Interfaces 802.1ad
>
_________________________________________________________________
Discover the new Windows Vista
http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
configure vman ethertype 0x8100
best regards,
--
Evgeniy Aikashev
network engineer
JSC DATAGROUP
Monday, October 19, 2009, 3:30:51 AM, Onam wrote:
In the diagram topology I am working with the VMAN tag 50. I made some test with a CISCO router and it works.
I check the jumbo-frame at the summit side and is enable to all ports.
> Date: Mon, 19 Oct 2009 10:47:16 +0300
> From: evg...@ip.datagroup.ua
> To: onam...@hotmail.com
> CC: junip...@puck.nether.net
> Subject: Re[2]: [j-nsp] Logical Interfaces 802.1ad
>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0 192.168.38.60/30
-------
|=A0=A0=A0=A0 |
|=A0=A0=A0=A0 |.61=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 _____=
__=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 _______=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 .62 _________
| M10 |ge-0/2/0.50=A0 P50(T) |=A0=A0=A0=A0=A0=A0 |P49(T)P49|=A0=A0=A0=A0=A0=
=A0 |P4(T)=A0 f0/0.50=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0 |
|=A0=A0=A0=A0 |<------------------>| x450=A0 |<------->| x450=A0 |<--------=
------> | c1751=A0=A0 |
|=A0=A0=A0=A0 |=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |_=
______|=A0=A0=A0=A0=A0=A0=A0=A0 |_______|=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0 |_________|
-------=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=20
=A0=A0=A0=A0=A0=A0>----Doesn't work----<=A0=A0=A0=A0=A0=A0>----------------=
-It works--------<
> From: onam...@hotmail.com
> To: evg...@ip.datagroup.ua
> Date: Mon=2C 19 Oct 2009 10:49:26 -0600
> CC: junip...@puck.nether.net
> Subject: Re: [j-nsp] Logical Interfaces 802.1ad
>=20
>=20
> Hello Experts=2C
>=20
> In the diagram topology I am working with the VMAN tag 50. I made some te=
st with a CISCO router and it works.
>=20
> I check the jumbo-frame at the summit side and is enable to all ports.
>=20
>> Date: Mon=2C 19 Oct 2009 10:47:16 +0300
>> From: evg...@ip.datagroup.ua
>> To: onam...@hotmail.com
>> CC: junip...@puck.nether.net
>> Subject: Re[2]: [j-nsp] Logical Interfaces 802.1ad
>>=20
>> Also works fine:
>>=20
>> {master}[edit interfaces xe-4/1/0]
>> evgeniy@mx480# show
>> description "=3D=3D=3D Summit X650 test =3D=3D=3D"=3B
>> flexible-vlan-tagging=3B
>> encapsulation flexible-ethernet-services=3B
>> gigether-options {
>> ethernet-switch-profile {
>> tag-protocol-id 0x88a8=3B
>> }
>> }
>> unit 100 {
>> description "=3D=3D=3D Summit X650 test =3D=3D=3D"=3B
>> vlan-tags outer 0x88a8.4092 inner 100=3B
>> family inet {
>> address x.x.x.x/30=3B
>> }
>> }
>>=20
>> Summit:
>> enable jumbo-frame ports all
>>=20
>>=20
>> best regards=2C
>> --=20
>> Evgeniy Aikashev
>> network engineer
>> JSC DATAGROUP
>>=20
>> Monday=2C October 19=2C 2009=2C 10:17:22 AM=2C Onam wrote:
>>> Hello Evgeniy=2C
>>=20
>>> I made some test before with this ethertype and it works. The Extreme x=
450 use both of them
>>> 0x8100 for VLAN and 0x88a8 for VMAN so if i do that the VMAN will becom=
e a VLAN.
>>=20
>>> I see that by default the Juniper router M10 use ethertype 0x8100=2C bu=
t when I try to use
>>> ethertype 0x88a8 the devices doens't see each other=2C I run a ping to =
the other side with no response.
>>=20
>>=20
>>>> Date: Mon=2C 19 Oct 2009 09:58:23 +0300
>>>> From: evg...@ip.datagroup.ua
>>>> To: onam...@hotmail.com
>>>> CC: junip...@puck.nether.net
>>>> Subject: Re: [j-nsp] Logical Interfaces 802.1ad
>>>>=20
>>>> Hello Onam=2C
>>>> try to change ethertype from Summit side:
>>>>=20
>>>> configure vman ethertype 0x8100
>>>>=20
>>>> best regards=2C
>>>> --=20
>>>> Evgeniy Aikashev
>>>> network engineer
>>>> JSC DATAGROUP
>>>>=20
>>>> Monday=2C October 19=2C 2009=2C 3:30:51 AM=2C Onam wrote:
>>>>=20
>>>>> Hi experts=2C
>>>>=20
>>>>> I want to make logical interfaces on a physical interface ge-0/2/0 of=
a Juniper M10 router to
>>>>> connected to a the trunk port of a Summit Extreme x450 with the ether=
type 0x88a8 (IEEE 802.1ad).
>>>>=20
>>>>> I have the following configuration on the router.
>>>>=20
>>>>> ge-0/2/0 {
>>>>> vlan-tagging=3B
>>>>> gigether-options {
>>>>> ethernet-switch-profile {
>>>>> tag-protocol-id 0x88a8=3B
>>>>> }
>>>>> }
>>>>> unit 50 {
>>>>> vlan-tags outer 0x88a8.50=3B
>>>>> family inet {
>>>>> address 192.168.175.169/28=3B
>>>>> }
>>>>> }
>>>>> }
>>>>=20
>>>>> I made the test with the 802.1q and it works but with 802.1ad didn't =
work.
>>>>=20
>>>>> Best regards.
>>>>>=20
>>>>> _________________________________________________________________
>>>>> News=2C entertainment and everything you care about at Live.com. Get =
it now!
>>>>> http://www.live.com/getstarted.aspx
>>>>> _______________________________________________
>>>>> juniper-nsp mailing list junip...@puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>>=20
>>=20
>>> Get news=2C entertainment and everything you care about at Live.com. Ch=
eck it out!=20
>>=20
> =20
> _________________________________________________________________
> News=2C entertainment and everything you care about at Live.com. Get it n=
ow!
> http://www.live.com/getstarted.aspx
=20
_________________________________________________________________
News=2C entertainment and everything you care about at Live.com. Get it now=
!
http://www.live.com/getstarted.aspx=
.61
.62
|| M10 ||<-ge-0/2/0.50----P49(T)->|| x450 ||<-P50(T)----P50(T)->|| x450 ||<-P4(T)----F0/0.50->|| CISCO_1751 ||
At this envioremente I am using VMAN tag 50.
>From CISCO to Extreme it works.
>From Juniper to Extreme doesn't work.
Best regards.
> Date: Mon, 19 Oct 2009 10:47:16 +0300
> From: evg...@ip.datagroup.ua
> To: onam...@hotmail.com
> CC: junip...@puck.nether.net
> Subject: Re[2]: [j-nsp] Logical Interfaces 802.1ad
>
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
Here, is the information. but the Junipes's don't see each other.
onam@M10_A> show configuration interfaces ge-0/2/0
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50 inner 100;
family inet {
address 192.168.38.58/30;
}
}
onam@M10_A> show interfaces ge-0/2/0.100 | match Encapsulation
onam@M10_Ashow interfaces ge-0/2/0 | match Encapsulation
Flags: SNMP-Traps VLAN-Tag [ 0x0000.0 ] Encapsulation: ENET2
onam@M5_B> show configuration interfaces ge-0/2/0
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50 inner 100;
family inet {
address 192.168.38.57/30;
}
}
onam@MetisM5_B> show interfaces ge-0/2/0.100 | match Encapsulation
onam@MetisM5_B> show interfaces ge-0/2/0 | match Encapsulation
Flags: SNMP-Traps VLAN-Tag [ 0x0000.0 ] Encapsulation: ENET2
Summit
x450_A# sho vman etherType
vman EtherType : 0x88a8
x450_A# # SHO vman "Test_Side_A"
VMAN Interface with name Test_Side_A created by user
Admin State: Enabled Tagging: 802.1Q Tag 50
Virtual router: VR-Default
**Primary IP : 192.168.175.166/28 **(Administration IP address)**
IPv6: None
STPD: None
Protocol: Match all unfiltered protocols
Loopback: Disabled
NetLogin: Disabled
QosProfile: None configured
Egress Rate Limit Designated Port: None configured
Ports: 4. (Number of active ports=3)
Tag: *1(UpLink_x450_B),*46(M10_A_Ge-0/2/0)
Flags: (*) Active, (!) Disabled, (g) Load Sharing port
(b) Port blocked on the vlan, (a) Authenticated NetLogin port
(u) Unauthenticated NetLogin port, (m) Mac-Based port
x450_A#
x450_B # sh vman etherType
Vman Primary EtherType : 0x88a8
x450_B # sho vman "Test_Side_B"
VMAN Interface with name Test_Side_B created by user
Admin State: Enabled Tagging: 802.1Q Tag 50
Virtual router: VR-Default
**Primary IP : 172.16.40.2/24** (Administration IP address)**
IPv6: None
STPD: None
Protocol: Match all unfiltered protocols
Loopback: Disabled
NetLogin: Disabled
QosProfile: None configured
Egress Rate Limit Designated Port: None configured
Flood Rate Limit QosProfile: None configured
Ports: 20. (Number of active ports=15)
Tag: *1(UpLink_x450_A),*45(M5_B_Ge-0/2/0)
Flags: (*) Active, (!) Disabled, (g) Load Sharing port
(b) Port blocked on the vlan, (m) Mac-Based port
(a) Egress traffic allowed for NetLogin
(u) Egress traffic unallowed for NetLogin
x450_B#
Best regards.
> Date: Tue, 20 Oct 2009 11:15:37 +0300
> From: evg...@ip.datagroup.ua
> To: onam...@hotmail.com
> Subject: Re[4]: [j-nsp] Logical Interfaces 802.1ad
>
> Hi Onam,
> I examined you config and at first glance all should works....
> Please show from both Junipers:
> show interfaces xxx.100 | match Encapsulation
>
> From both Summits:
> show vman etherType
> show vman xxx
>
>
>
> best regards,
> --
> Evgeniy Aikashev
> network engineer
> JSC DATAGROUP
>
> Tuesday, October 20, 2009, 9:45:37 AM, Onam wrote:
> > Dear Evgenie,
>
> > Thaks for your help.
>
> > But I configure the juniper as you suggest me, but it doesn't work. I don't know if I'am missing a parameter or something else.
>
> > I sent you the topology, maybe you can check it.
>
> > I just try the same with to Cisco router at the same topology and it works, in fact I test it with 0x88a8 and 0x9100.
>
> > Best regards.
>
> >> Date: Mon, 19 Oct 2009 10:47:16 +0300
> >> From: evg...@ip.datagroup.ua
> >> To: onam...@hotmail.com
> >> CC: junip...@puck.nether.net
> >> Subject: Re[2]: [j-nsp] Logical Interfaces 802.1ad
> >>
> >> Also works fine:
> >>
> >> {master}[edit interfaces xe-4/1/0]
> >> evgeniy@mx480# show
> >> description "=== Summit X650 test ===";
> >> flexible-vlan-tagging;
> >> encapsulation flexible-ethernet-services;
> >> gigether-options {
> >> ethernet-switch-profile {
> >> tag-protocol-id 0x88a8;
> >> }
> >> }
> >> unit 100 {
> >> description "=== Summit X650 test ===";
> >> vlan-tags outer 0x88a8.4092 inner 100;
> >> family inet {
> >> address x.x.x.x/30;
> >> }
> >> }
> >>
> >> Summit:
> >> enable jumbo-frame ports all
> >>
> >>
> >> best regards,
> >> --
> >> Evgeniy Aikashev
> >> network engineer
> >> JSC DATAGROUP
> >>
> >> Monday, October 19, 2009, 10:17:22 AM, Onam wrote:
> >> > Get news, entertainment and everything you care about at Live.com. Check it out!
> >>
>
> > Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it!
>
_________________________________________________________________
Connect to the next generation of MSN Messenger
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
About the sub-interfaces on GigaEthernet interface.
I connect two Juniper back-to-back to make this test, and discard that the summit were the problem.
M5_A<=====>M7i_B
Test 1:
I configure both of them without sub-interfaces and without VLAN, the router's see each other.
Test 2:
I configure both router with sub-interfaces encapsulation dot1q(0x8100), the router's see each other.
Test 3
I configure both router with sub-interfaces encapsulation 802.1ad(0x88a8), the router's don't see each other.
M5_A (Version 8.3R1.5)
ge-0/2/0 {
description "===to M7i Test===";
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50 inner 10;
family inet {
address 192.168.38.57/30;
}
}
}
M7i_B (Version 8.5R4.3)
interfaces {
ge-0/0/0 {
description "===to M5 Test ===";
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x88a8;
}
}
unit 50 {
vlan-tags outer 0x88a8.50 inner 10;
family inet {
address 192.168.38.58/30;
}
}
}
Test 4
I configure both router with sub-interfaces encapsulation QinQ(0x9100), the router's don't see each other.
M5_A (Version 8.3R1.5)
ge-0/2/0 {
description "===to M7i Test===";
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x9100;
}
}
unit 50 {
vlan-tags outer 0x9100.50 inner 10;
family inet {
address 192.168.38.57/30;
}
}
}
M7i_B (Version 8.5R4.3)
interfaces {
ge-0/0/0 {
description "===to M5 Test ===";
flexible-vlan-tagging;
gigether-options {
ethernet-switch-profile {
tag-protocol-id 0x9100;
}
}
unit 50 {
vlan-tags outer 0x9100.50 inner 10;
family inet {
address 192.168.38.58/30;
}
}
}
In the two las test(3,4) I ran a ping to the IP 192.168.38.58 in the router M7i_B, this should response because is in the interface of this router. IMHO, but this one doesn't response.
Thaks for your help.
Best regards.
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
We have QinQ(0x9100) in production here, works fine. Note that you need
a modern SFP based GigE PIC - the old fixed optic PIC don't support the
settable VLAN TPID.
Steinar Haug, Nethelp consulting, sth...@nethelp.no