[173797] in North American Network Operators' Group
Re: [j-nsp] Viability of EX4300 in a primarily l3 environment?
daemon@ATHENA.MIT.EDU (Yucong Sun)
Wed Aug 6 08:01:44 2014
X-Original-To: nanog@nanog.org
In-Reply-To: <53E21770.9040205@winterei.se>
From: Yucong Sun <sunyucong@gmail.com>
Date: Wed, 6 Aug 2014 20:01:03 +0800
To: "Paul S." <contact@winterei.se>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
it appears not, ospf + ipv4 was not mentioned here:
http://www.juniper.net/techpubs/en_US/junos11.4/topics/concept/ex-series-so=
ftware-licenses-overview.html#jd0e135
On Wed, Aug 6, 2014 at 7:54 PM, Paul S. <contact@winterei.se> wrote:
> Correct me if I'm wrong, but doesn't OSPF require the AFL license anyway
> to be 'legitly' ran?
>
> Price difference might be a lot smaller depending on that.
>
>
> On 8/6/2014 =E5=8D=88=E5=BE=8C 08:30, Yucong Sun wrote:
>
>> I used ex4200 to do exactly what you did before. ex4200 releases is
>> pretty
>> rock solid, feature extensive, although with lower arp entry limits.
>>
>> Given the price difference maybe you can connect each l2 domain to its o=
wn
>> ex4200 and have them do ospf routing among selves, which maybe give you
>> better failure tolerances compare to a single core.
>>
>>
>> On Wed, Aug 6, 2014 at 6:35 PM, Giuliano Cardozo Medalha <
>> giuliano@wztech.com.br> wrote:
>>
>> we are using ex4300 with the last release available
>>>
>>> the setup is pretty simple using virtual chassis, lag, L3 and poe
>>>
>>> it works pretty fine and we do not have any serious problems
>>>
>>> sometimes the poe controller goes down but we have a case oppened in jt=
ac
>>> to try solve it
>>>
>>> Sent from my iPhone
>>>
>>> On 06/08/2014, at 07:15, Sebastian Wiesinger <
>>>> juniper-nsp@ml.karotte.org>
>>>>
>>> wrote:
>>>
>>>> * Paul S. <contact@winterei.se> [2014-08-02 05:18]:
>>>>
>>>>> Hi folks,
>>>>>
>>>>> We're considering the EX4300 to run routing (l3) for a few
>>>>> hypervisors of ours that are connected via l2.
>>>>>
>>>>> Primarily interested due to the rather massive arp limit (64, 000)
>>>>> on the switch, but we've been told (and searched for ourselves to
>>>>> find out) that the 4300 platform has been plagued by random issues
>>>>> since launch.
>>>>>
>>>> I don't have hands-on experience but I looked at the EX4300 platform
>>>> for a new deployment. If you look at the current release notes:
>>>>
>>>>
>>>> http://www.juniper.net/techpubs/en_US/junos13.2/
>>> information-products/topic-collections/ex-qfx-series/
>>> release-notes/ex-qfx-series-junos-release-notes-13.2X51-D25.pdf
>>>
>>>> There are a lot of (serious) bugs still getting fixed so I'm not sure
>>>> how mature this platform is. One big reason for that is probably
>>>> because EX4300 uses other chips than the rest of the 4xxx series
>>>> (Broadcom).
>>>>
>>>> Regards
>>>>
>>>> Sebastian
>>>>
>>>> --
>>>> GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A 9D82 58A2 D94A 93A0 B9C=
E)
>>>> 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE T=
HE
>>>>
>>> SCYTHE.
>>>
>>>> -- Terry Pratchett, The Fifth Elephant
>>>> _______________________________________________
>>>> 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
>>
>
>
