[j-nsp] Logical Interfaces 802.1ad

[Onam Rubio]

I just made this configuration but I can't see neighboor (x450 summit) I check the following information.

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 at 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 at 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.dewell at gmail.com
> Date: Sun, 18 Oct 2009 18:07:25 -0700
> CC: juniper-nsp at puck.nether.net
> To: onamrubio at 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
> 
> On Oct 18, 2009, at 5:30 PM, Onam Rubio wrote:
> 
> >
> > Hi experts,
> >
> > 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 juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
 		 	   		  
_________________________________________________________________
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline