Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
Can one run full IGP+MP-BGP VPLS/L2VPN/L3VPN on the ex4300? On Thu, Feb 20, 2014 at 5:08 PM, Ben Dale wrote: > > On 20 Feb 2014, at 6:00 pm, Per Granath wrote: > > > For the mixed VC, the options are EX42+EX4550 or EX43+QFX. > > > > For VC, the EX42 uses VCP-cables, while the EX43 uses QSFP-DAC-cables > (assuming you do not want to waste your 10G ports). > > > > EX42 and EX43 has the same price. > > EX4550 is somewhat cheaper than QFX. > > A word of caution on the "same price" between EX42/43: > > If you want to use the EX4300 for L3 (and lets face it, that's probably > everyone) you'll require the Enhanced Feature License for OSPFv2/3, IGMP > v1/v2, PIM, VRF-Lite, QinQ and OAM. EX4200 includes all this in the base > license. > > Both still require the Advanced Feature License for BGP, ISIS and MPLS. > > If you want to install the Advanced Feature License on EX4300 though, you > need to buy both the EFL *and* AFL. > > All features are still available for testing without licenses, but you get > the nag message every minute in syslog. > > All that said, being able to VC up to 5 of these things together with a > dedicated 40G between any two is pretty darn cool. > > Ben > > > > > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Tim:> ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On Thu, Feb 20, 2014 at 02:31:58PM -0800, ryanL wrote: > weren't the ex4200 VC connections 64/128 Gbps thru the ribbon cable? why is No, 32 Gbps through PCIe x8. Marketing would have you believe it is 128 Gbps, but using their definitions, a 10 GigE port is 40 Gbps. In reality the VCPs each do 32 Gbps full-duplex, and there are two of them per switch. So 2*(32 in + 32 out) = 128 Gbps. > 40G which uses up actual ports all that exciting? maybe i don't see it > because it doesn't apply to my architecture. :-/ 40 Gbps is bigger than 32 Gbps? Standard cabling? ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
The VC cables in EX4200s are 32G half duplex. If we go full duplex we get to 64. Add another VC cable and we get 128. With the 40G interface, we get 80 full duplex and 160 with 2. HTH On 20 February 2014 22:31, ryanL wrote: > weren't the ex4200 VC connections 64/128 Gbps thru the ribbon cable? why is > 40G which uses up actual ports all that exciting? maybe i don't see it > because it doesn't apply to my architecture. :-/ > ___ > 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
weren't the ex4200 VC connections 64/128 Gbps thru the ribbon cable? why is 40G which uses up actual ports all that exciting? maybe i don't see it because it doesn't apply to my architecture. :-/ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On 20 Feb 2014, at 6:00 pm, Per Granath wrote: > For the mixed VC, the options are EX42+EX4550 or EX43+QFX. > > For VC, the EX42 uses VCP-cables, while the EX43 uses QSFP-DAC-cables > (assuming you do not want to waste your 10G ports). > > EX42 and EX43 has the same price. > EX4550 is somewhat cheaper than QFX. A word of caution on the "same price" between EX42/43: If you want to use the EX4300 for L3 (and lets face it, that's probably everyone) you'll require the Enhanced Feature License for OSPFv2/3, IGMP v1/v2, PIM, VRF-Lite, QinQ and OAM. EX4200 includes all this in the base license. Both still require the Advanced Feature License for BGP, ISIS and MPLS. If you want to install the Advanced Feature License on EX4300 though, you need to buy both the EFL *and* AFL. All features are still available for testing without licenses, but you get the nag message every minute in syslog. All that said, being able to VC up to 5 of these things together with a dedicated 40G between any two is pretty darn cool. Ben ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
For the mixed VC, the options are EX42+EX4550 or EX43+QFX. For VC, the EX42 uses VCP-cables, while the EX43 uses QSFP-DAC-cables (assuming you do not want to waste your 10G ports). EX42 and EX43 has the same price. EX4550 is somewhat cheaper than QFX. QFX is the box for VCF and QFabric, if you grow. -Original Message- From: Mark Tinka [mailto:mark.ti...@seacom.mu] Sent: Thursday, February 20, 2014 9:49 AM To: juniper-nsp@puck.nether.net Cc: Per Granath; Aaron Dewell; ryanL Subject: Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3 On Thursday, February 20, 2014 09:01:01 AM Per Granath wrote: > There is also an 8x10G uplink module coming out soon - in the > pricelist already. Mixed VC with EX43 and QFX also means these should > be useful for a very long time. It looks to follow the similar basic concepts of the EX4550, except without the capacity and SFP/SFP+ combined capabilities. Mark. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On Thursday, February 20, 2014 09:01:01 AM Per Granath wrote: > There is also an 8x10G uplink module coming out soon - in > the pricelist already. Mixed VC with EX43 and QFX also > means these should be useful for a very long time. It looks to follow the similar basic concepts of the EX4550, except without the capacity and SFP/SFP+ combined capabilities. Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
There is also an 8x10G uplink module coming out soon - in the pricelist already. Mixed VC with EX43 and QFX also means these should be useful for a very long time. -Original Message- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Aaron Dewell Sent: Wednesday, February 19, 2014 10:48 PM To: ryanL Cc: juniper-nsp Subject: Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3 I don't know if I'd call them issues. Just ELS introduces different configuration hierarchies that is the way things will be in the future. The functionality is still there even if the config bits change some. The main advantage of the 4300 vs. 4200 is 4x10G uplinks instead of 2, and 40G QSFP+ ports which can be either VC or routed. It's a lot more flexible platform and much more compatible with others (read: QFX5100) than the EX4200 will ever be. On Feb 19, 2014, at 2:36 PM, ryanL wrote: > welp, i was about to pull the trigger and order the ex4300's for a new > rack, but i think i'll stick to the ex4200 for now. > > appreciative of people pointing out current issues (even tho i'm not > the original poster). > ___ > 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On 20 Feb 2014, at 11:22 am, Mark Tinka wrote: > On Wednesday, February 19, 2014 10:47:33 PM Aaron Dewell > wrote: > >> The main advantage of the 4300 vs. 4200 is 4x10G uplinks >> instead of 2, and 40G QSFP+ ports which can be either VC >> or routed. It's a lot more flexible platform and much >> more compatible with others (read: QFX5100) than the >> EX4200 will ever be. > > Can anyone speak to buffer sizes and whether egress policing > is supported? > > Mark. >From what I've been able to gather, there is a single PFE on them with 5MB >shared. The feature guide suggests port/queue shaping is available and it mentions policing under Routing Policy/Packet Filtering features, but I suspect this is just the traditional filter-based stuff: http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/concept/ex-series-software-features-overview.html#cos-features-by-platform-table Ben ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On Wednesday, February 19, 2014 10:47:33 PM Aaron Dewell wrote: > The main advantage of the 4300 vs. 4200 is 4x10G uplinks > instead of 2, and 40G QSFP+ ports which can be either VC > or routed. It's a lot more flexible platform and much > more compatible with others (read: QFX5100) than the > EX4200 will ever be. Can anyone speak to buffer sizes and whether egress policing is supported? Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On Wed, Feb 19, 2014 at 12:53 PM, ryanL wrote: > instability while in vc and/or update beyond 30 days kinda sound like > table-stake issues to me. > Yeah, as an early adopter this was a bit spicy, but we had an extended burn-in phase since it was a new platform so it wasn't impactful. That said, JTAC was quick to identify the issue and get a new code rev pushed out. D17 resolved our ~30 day issue (CPU would spike to 100% on one route engine), and now D18 is out. And as others have already pointed out, the 4x10G and 4x40G make it much attractive for future expansion. I've been very pleased with the platform over the last two months. -Jonathan ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
we have a lot of ex4300 working well with D18 ... dont worry about it it has 4 sfp+ and 4 qsfp+ it is a better choice juniper development is very fast about ex4300 code ... a lot of corrections in some much fast way Sent from my iPhone > On 19/02/2014, at 17:36, ryanL wrote: > > welp, i was about to pull the trigger and order the ex4300's for a new > rack, but i think i'll stick to the ex4200 for now. > > appreciative of people pointing out current issues (even tho i'm not the > original poster). > ___ > 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
instability while in vc and/or update beyond 30 days kinda sound like table-stake issues to me. On Wed, Feb 19, 2014 at 12:47 PM, Aaron Dewell wrote: > > I don't know if I'd call them issues. Just ELS introduces different > configuration hierarchies that is the way things will be in the future. > The functionality is still there even if the config bits change some. > > The main advantage of the 4300 vs. 4200 is 4x10G uplinks instead of 2, and > 40G QSFP+ ports which can be either VC or routed. It's a lot more flexible > platform and much more compatible with others (read: QFX5100) than the > EX4200 will ever be. > > On Feb 19, 2014, at 2:36 PM, ryanL wrote: > > welp, i was about to pull the trigger and order the ex4300's for a new > > rack, but i think i'll stick to the ex4200 for now. > > > > appreciative of people pointing out current issues (even tho i'm not the > > original poster). > > ___ > > 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
I don't know if I'd call them issues. Just ELS introduces different configuration hierarchies that is the way things will be in the future. The functionality is still there even if the config bits change some. The main advantage of the 4300 vs. 4200 is 4x10G uplinks instead of 2, and 40G QSFP+ ports which can be either VC or routed. It's a lot more flexible platform and much more compatible with others (read: QFX5100) than the EX4200 will ever be. On Feb 19, 2014, at 2:36 PM, ryanL wrote: > welp, i was about to pull the trigger and order the ex4300's for a new > rack, but i think i'll stick to the ex4200 for now. > > appreciative of people pointing out current issues (even tho i'm not the > original poster). > ___ > 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
welp, i was about to pull the trigger and order the ex4300's for a new rack, but i think i'll stick to the ex4200 for now. appreciative of people pointing out current issues (even tho i'm not the original poster). ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On Tue, Feb 18, 2014 at 8:24 PM, Ben Dale wrote: > > Also, upgrade your code to 13.2X50-D18 right now. No, really. You'll > thank me later. > +1 Anything less that D17 had some serious stability issues when in a virtual chassis and up for more than 30 days. -Jonathan ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
I think the following link can answer it for you:
http://www.juniper.net/techpubs/en_US/junos13.2/topics/task/configuration/getting-started-els.html
Enhanced Layer 2 Software
EX4300 switches
13.2X50-D10
EX9200 switches
12.3R2
QFX3500 switches
13.2X50-D15
QFX3600 switches
13.2X50-D15
QFX5100 switches
13.2X51-D10
Giuliano Cardozo Medalha
Systems Engineer
+55 (17) 3011-3811
+55 (17) 8112-5394
JUNIPER J-PARTNER ELITE
giuli...@wztech.com.br
http://www.wztech.com.br/
WZTECH is registered trademark of WZTECH NETWORKS.
Copyright © 2013 WZTECH NETWORKS. All Rights Reserved.
The information transmitted in this email message and any attachments are
solely for the intended recipient and may contain confidential or
privileged information. If you are not the intended recipient, any review,
transmission, dissemination or other use of this information is
prohibited. If you have received this communication in error, please notify
the sender immediately and delete the material from any computer, including
any copies.
On Wed, Feb 19, 2014 at 3:15 PM, Bill Blackford wrote:
> Next Gen CLI for layer2. This is the same format as the Layer2 Functions
> on the MX. Is this a trend for all EX products or just the NG hardware?
>
>
> On Wed, Feb 19, 2014 at 2:25 AM, Giuliano Cardozo Medalha <
> giuli...@wztech.com.br> wrote:
>
>> ex4300 uses next generation cli for L2
>>
>> instead of use interface vlan you need to use interface irb
>>
>> set vlan TEST vlan-id 20 l3-interface irb.20
>>
>> set interface irb unit 20 family inet address 192.168.20.100/24
>>
>> and now for port mode ( access x trunk ) you need to use
>>
>> interface-mode ...
>>
>> dhcp-relay and rstp changed too ...
>>
>> set forwarding-options dhcp-relay ... and not helpers anymore
>>
>> set protocols rstp interface ge-0/0/0
>>
>> you need to declare every interface under rstp ...
>>
>> wildcard range set protocols ... helps
>>
>> wildcard range set interfaces ... too
>>
>> to see trunk ports
>>
>> > show ethernet-switching interface | except untagged | match tagged
>>
>>
>>
>> Sent from my iPhone
>>
>> > On 19/02/2014, at 00:44, Janusz Wełna wrote:
>> >
>> > Hi,
>> >
>> >
>> > Why when I have below config:
>> >
>> > ge-0/0/44 {
>> >description test;
>> >unit 0 {
>> >family ethernet-switching {
>> >vlan {
>> >members vlan103;
>> >}
>> >storm-control default;
>> >
>> > unit 103 {
>> >description test;
>> >family inet {
>> >address 10.46.163.1/29;
>> >
>> >
>> >vlan103 {
>> >description test;
>> >vlan-id 103;
>> >l3-interface vlan.103;
>> >
>> >
>> >
>> >
>> > I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
>> > server connected to ge-0/0/44
>> >
>> >
>> >
>> >
>> > But when I add below:
>> >
>> >
>> > irb {
>> >unit 103 {
>> >family inet {
>> >address 10.46.163.1/29;
>> >
>> >
>> > and delete :
>> >
>> >
>> > vlan103 {
>> >description SGI;
>> >vlan-id 103;
>> >l3-interface vlan.103
>> >
>> >
>> >
>> >
>> > ping works correctly.
>> >
>> >
>> > On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need
>> on
>> > EX4300 ?
>> >
>> >
>> >
>> > Br,
>> >
>> >
>> > Janusz
>> > ___
>> > 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
>>
>
>
>
> --
> Bill Blackford
>
> Logged into reality and abusing my sudo privileges.
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
Next Gen CLI for layer2. This is the same format as the Layer2 Functions on
the MX. Is this a trend for all EX products or just the NG hardware?
On Wed, Feb 19, 2014 at 2:25 AM, Giuliano Cardozo Medalha <
giuli...@wztech.com.br> wrote:
> ex4300 uses next generation cli for L2
>
> instead of use interface vlan you need to use interface irb
>
> set vlan TEST vlan-id 20 l3-interface irb.20
>
> set interface irb unit 20 family inet address 192.168.20.100/24
>
> and now for port mode ( access x trunk ) you need to use
>
> interface-mode ...
>
> dhcp-relay and rstp changed too ...
>
> set forwarding-options dhcp-relay ... and not helpers anymore
>
> set protocols rstp interface ge-0/0/0
>
> you need to declare every interface under rstp ...
>
> wildcard range set protocols ... helps
>
> wildcard range set interfaces ... too
>
> to see trunk ports
>
> > show ethernet-switching interface | except untagged | match tagged
>
>
>
> Sent from my iPhone
>
> > On 19/02/2014, at 00:44, Janusz Wełna wrote:
> >
> > Hi,
> >
> >
> > Why when I have below config:
> >
> > ge-0/0/44 {
> >description test;
> >unit 0 {
> >family ethernet-switching {
> >vlan {
> >members vlan103;
> >}
> >storm-control default;
> >
> > unit 103 {
> >description test;
> >family inet {
> >address 10.46.163.1/29;
> >
> >
> >vlan103 {
> >description test;
> >vlan-id 103;
> >l3-interface vlan.103;
> >
> >
> >
> >
> > I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
> > server connected to ge-0/0/44
> >
> >
> >
> >
> > But when I add below:
> >
> >
> > irb {
> >unit 103 {
> >family inet {
> >address 10.46.163.1/29;
> >
> >
> > and delete :
> >
> >
> > vlan103 {
> >description SGI;
> >vlan-id 103;
> >l3-interface vlan.103
> >
> >
> >
> >
> > ping works correctly.
> >
> >
> > On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need
> on
> > EX4300 ?
> >
> >
> >
> > Br,
> >
> >
> > Janusz
> > ___
> > 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
>
--
Bill Blackford
Logged into reality and abusing my sudo privileges.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
The CLI changes right now only apply to new hardware — EX9200, EX4300, QFX5100. The other EX products still use the “normal” way, even on the latest code. I’m not sure if they are planning on running the ELS syntax on other EX platforms or not. will On Feb 19, 2014, at 12:00 PM, juniper-nsp-requ...@puck.nether.net wrote: > Message: 3 > Date: Wed, 19 Feb 2014 18:12:37 +0200 > From: Mark Tinka > To: juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3 > Message-ID: <201402191812.37822.mark.ti...@seacom.mu> > Content-Type: text/plain; charset="us-ascii" > > On Wednesday, February 19, 2014 12:25:55 PM Giuliano Cardozo > Medalha wrote: > >> ex4300 uses next generation cli for L2 > > Does all this roll over cleanly into an upgrade if you were > running previous generation CLI with earlier code? > > Mark. > -- next part -- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 836 bytes > Desc: This is a digitally signed message part. > URL: > <https://puck.nether.net/pipermail/juniper-nsp/attachments/20140219/3ff446e6/attachment-0001.sig> > > -- > > Subject: Digest Footer ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
On Wednesday, February 19, 2014 12:25:55 PM Giuliano Cardozo Medalha wrote: > ex4300 uses next generation cli for L2 Does all this roll over cleanly into an upgrade if you were running previous generation CLI with earlier code? Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
ex4300 uses next generation cli for L2
instead of use interface vlan you need to use interface irb
set vlan TEST vlan-id 20 l3-interface irb.20
set interface irb unit 20 family inet address 192.168.20.100/24
and now for port mode ( access x trunk ) you need to use
interface-mode ...
dhcp-relay and rstp changed too ...
set forwarding-options dhcp-relay ... and not helpers anymore
set protocols rstp interface ge-0/0/0
you need to declare every interface under rstp ...
wildcard range set protocols ... helps
wildcard range set interfaces ... too
to see trunk ports
> show ethernet-switching interface | except untagged | match tagged
Sent from my iPhone
> On 19/02/2014, at 00:44, Janusz Wełna wrote:
>
> Hi,
>
>
> Why when I have below config:
>
> ge-0/0/44 {
>description test;
>unit 0 {
>family ethernet-switching {
>vlan {
>members vlan103;
>}
>storm-control default;
>
> unit 103 {
>description test;
>family inet {
>address 10.46.163.1/29;
>
>
>vlan103 {
>description test;
>vlan-id 103;
>l3-interface vlan.103;
>
>
>
>
> I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
> server connected to ge-0/0/44
>
>
>
>
> But when I add below:
>
>
> irb {
>unit 103 {
>family inet {
>address 10.46.163.1/29;
>
>
> and delete :
>
>
> vlan103 {
>description SGI;
>vlan-id 103;
>l3-interface vlan.103
>
>
>
>
> ping works correctly.
>
>
> On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need on
> EX4300 ?
>
>
>
> Br,
>
>
> Janusz
> ___
> 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
Hi Janusz,
You may want to read through this document too:
http://www.juniper.net/techpubs/en_US/junos13.2/topics/task/configuration/getting-started-els.html
there are quite a few changes to the way you're used to doing things with VLANs
and interfaces on EX4300s, which you'll find incredibly frustrating after using
any of the other EXs up until now.
Also, upgrade your code to 13.2X50-D18 right now. No, really. You'll thank me
later.
It's not actually available on the download page, but if you follow the link on
right where it shows JTAC recommended code which redirects you to the
password-protected KB Article on recommended versions, which you can then dig
through to find the link to the specific EX4300 software Technical Services
Bulletin, which lists the 13-odd critical PRs that seemed to make it out the
door and finally the link to the actual software...
or for Hitchhikers fans: "It was on display in the bottom of a locked filing
cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of
the Leopard'."
https://download.juniper.net/software/junos/regressed/13.2X50-D18/jinstall-ex-4300-13.2X50-D18-domestic-signed.tgz
On 19 Feb 2014, at 1:44 pm, Janusz Wełna wrote:
> Hi,
>
>
> Why when I have below config:
>
> ge-0/0/44 {
>description test;
>unit 0 {
>family ethernet-switching {
>vlan {
>members vlan103;
>}
>storm-control default;
>
> unit 103 {
>description test;
>family inet {
>address 10.46.163.1/29;
>
>
>vlan103 {
>description test;
>vlan-id 103;
>l3-interface vlan.103;
>
>
>
>
> I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
> server connected to ge-0/0/44
>
>
>
>
> But when I add below:
>
>
> irb {
>unit 103 {
>family inet {
>address 10.46.163.1/29;
>
>
> and delete :
>
>
> vlan103 {
>description SGI;
>vlan-id 103;
>l3-interface vlan.103
>
>
>
>
> ping works correctly.
>
>
> On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need on
> EX4300 ?
>
>
>
> Br,
>
>
> Janusz
> ___
> 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
Re: [j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
It's a name change. vlan is now irb. It depends on platform, but the newer
ones use irb instead of vlan.
So it doesn't work with vlan.103 because the vlan interface physically does not
exist. But you can configure nonexistent interfaces in JunOS.
On Feb 18, 2014, at 9:44 PM, Janusz Wełna wrote:
> Hi,
>
>
> Why when I have below config:
>
> ge-0/0/44 {
>description test;
>unit 0 {
>family ethernet-switching {
>vlan {
>members vlan103;
>}
>storm-control default;
>
> unit 103 {
>description test;
>family inet {
>address 10.46.163.1/29;
>
>
>vlan103 {
>description test;
>vlan-id 103;
>l3-interface vlan.103;
>
>
>
>
> I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
> server connected to ge-0/0/44
>
>
>
>
> But when I add below:
>
>
> irb {
>unit 103 {
>family inet {
>address 10.46.163.1/29;
>
>
> and delete :
>
>
> vlan103 {
>description SGI;
>vlan-id 103;
>l3-interface vlan.103
>
>
>
>
> ping works correctly.
>
>
> On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need on
> EX4300 ?
>
>
>
> Br,
>
>
> Janusz
> ___
> 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
[j-nsp] VLAN's on EX4300 with 13.2X50-D15.3
Hi,
Why when I have below config:
ge-0/0/44 {
description test;
unit 0 {
family ethernet-switching {
vlan {
members vlan103;
}
storm-control default;
unit 103 {
description test;
family inet {
address 10.46.163.1/29;
vlan103 {
description test;
vlan-id 103;
l3-interface vlan.103;
I cannot ping from EX4300 10.46.163.1 and I cannot ping 10.46.163.1 from
server connected to ge-0/0/44
But when I add below:
irb {
unit 103 {
family inet {
address 10.46.163.1/29;
and delete :
vlan103 {
description SGI;
vlan-id 103;
l3-interface vlan.103
ping works correctly.
On EX3300, EX4200 and EX2200 I not need setup irb interface, why I need on
EX4300 ?
Br,
Janusz
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
