[j-nsp] Re: VLAN tagging

[Thomas Salmen]

> 
> 
> VLAN tagging is set on the physical and then
> you break it into logical units on the M series.
> You shouldn't be able to do this without a commit
> error:
> 

Aye, below is pretty much what I'd tried - but as you say, it won't commit.
I was hoping there was some other way of doing it that wasn't immediately
obvious from the junos docs.


> ---snip---
> router# show interfaces fe-0/0/1
> vlan-tagging;
> unit 0 {
>     family inet {
>         address 192.168.1.1/30;
>     }
> }
> unit 100 {
>     vlan-id 100;
>     family inet {
>         address 10.100.100.1/30;
>     }
> }
> unit 200 {
>     vlan-id 200;
>     family inet {
>         address 10.200.200.1/30;
>     }
> }
> 
> [edit]
> router# commit check
> [edit interfaces fe-0/0/1]
>   'unit 0'
>      VLAN-ID must be specified on tagged ethernet interfaces
> error: configuration check-out failed
> 
> ---snip---
> 
> regards
> -Craig
> 
> * Thus spake Thomas Salmen (tsalmen at orcon.net.nz):
> 
> >
> > Hello,
> >
> > On a Cisco router, it is possible to do this:
> >
> > interface FastEthernet4/0
> >  ip address 192.168.1.1 255.255.255.252
> > !
> > interface FastEthernet4/0.100
> > encapsulation dot1Q 100
> >  ip address 10.100.100.1 255.255.255.252
> > !
> > interface FastEthernet4/0.200
> > encapsulation dot1Q 200
> > ip address 10.200.200.1 255.255.255.252
> >
> > That is, add VLAN-tagged logical subinterfaces to a non-tagged physical
> > interface.
> >
> > Does anyone know if this can be duplicated on an M-series?
> >
> > Cheers,
> > Thomas
> >
> >
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp