sorry! i ve not seen ur subz interfaces earlier... my bad :) Regards, Masood
> > > Masood, > > Do you think its possible to configure anything other than unit 0 > without vlan-tagging? I hope that answers your question. > >> ge-1/1/0.1 up up inet 1.1.1.0/31 <-- >> ge-1/1/0.2 up up inet 2.2.2.0/31 <-- > > > > Thanks & Regards, > Tarique A. Nalkhande > > -----Original Message----- > From: mas...@nexlinx.net.pk [mailto:mas...@nexlinx.net.pk] > Sent: Thursday, July 09, 2009 9:46 PM > To: Nalkhande Tarique Abbas > Cc: Bit Gossip; Juniper List > Subject: Re: [j-nsp] vlan-id 0 > > Your configuration is missing "vlan-tagging" > Is behaviour remains the same if you add "vlan-tagging" under interface > configuration. > > Regards, > Masood > Blog: http://weblogs.com.pk/jahil/ > > >> >> Hi >> >> AFAIK, basically a unit 32767 is created implicitly when > "vlan-tagging" >> is enabled to pass untagged control traffic (like STP, LACP ... etc). >> When a unit with vlan-id 0 is configured, this unit itself is used to >> send the control traffic. So the unit 32767 then gets deleted. >> >> >> >> ge-1/1/0 up up >> ge-1/1/0.1 up up inet 1.1.1.0/31 >> ge-1/1/0.2 up up inet 2.2.2.0/31 >> ge-1/1/0.32767 up up >> >> r...@sulfur# show | compare >> [edit interfaces ge-1/1/0] >> + unit 0 { >> + vlan-id 0; >> + } >> >> l...@sulfur> show interfaces terse | match ge-1/1/0 >> ge-1/1/0 up up >> ge-1/1/0.0 up up >> ge-1/1/0.1 up up inet 1.1.1.0/31 >> ge-1/1/0.2 up up inet 2.2.2.0/31 >> >> >> >> Thanks & Regards, >> Tarique A. Nalkhande >> >> >> -----Original Message----- >> From: juniper-nsp-boun...@puck.nether.net >> [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Bit Gossip >> Sent: Thursday, July 09, 2009 6:13 PM >> To: Juniper List >> Subject: [j-nsp] vlan-id 0 >> >> Experts, >> do you know what is the meaning of vlan-id 0? >> According to: http://en.wikipedia.org/wiki/IEEE_802.1Q >> "VLAN Identifier (VID): a 12-bit field specifying the VLAN to which > the >> frame belongs. A value of 0 means that the frame doesn't belong to any >> VLAN; in this case the 802.1Q tag specifies only a priority and is >> referred to as a priority tag" >> >> How would I match this Juniper config: >> >> show configuration interfaces ge-0/0/0 >> vlan-tagging; >> unit 0 { >> vlan-id 0; >> family inet { >> address 1.1.1.1/30; >> } >> } >> >> on a cisco device on the other end of the cable where vlan starts from >> 1? >> >> r2(config-subif)#encapsulation dot1Q ? >> <1-4094> IEEE 802.1Q VLAN ID required >> >> Thanks, >> bit >> >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> _______________________________________________ >> juniper-nsp mailing list juniper-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/juniper-nsp >> > > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp