[j-nsp] Viability of EX4300 in a primarily l3 environment?

Tyler Christiansen tyler at adap.tv
Wed Aug 6 13:07:29 EDT 2014


On Wed, Aug 6, 2014 at 6:59 AM, Paul S. <contact at winterei.se> wrote:

> That lower arp limit is precisely why we're looking at the 4300, though.
>
> Which, by the way, does anyone happen to know if the arp limit stays the
> same when the 4200s are put into VC mode -- or do they increase at all?
>
​
I believe ARP is handled by the RE, so in a virtual chassis, the ARP limit
would be the same.  I could be wrong, though.

--tc
​


> On 8/6/2014 午後 10:31, Scott Granados wrote:
>
>> +1 on the 4200.
>>
>> Had very good luck with the 4200 series.  Also had good luck with the
>> 4300 but there were some bugs.  In a basic operation mode though they are
>> quite stable.  That being said I was really pleased with the 4200 and you
>> might want to check them out assuming the lower arp limit isn’t an issue.
>>
>> On Aug 6, 2014, at 7:30 AM, Yucong Sun <sunyucong at gmail.com> 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
>>> own
>>> 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 at 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
>>>> jtac
>>>> to try solve it
>>>>
>>>> Sent from my iPhone
>>>>
>>>>  On 06/08/2014, at 07:15, Sebastian Wiesinger <
>>>>> juniper-nsp at ml.karotte.org>
>>>>>
>>>> wrote:
>>>>
>>>>> * Paul S. <contact at 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
>>>>> B9CE)
>>>>> 'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE
>>>>> THE
>>>>>
>>>> SCYTHE.
>>>>
>>>>>            -- Terry Pratchett, The Fifth Elephant
>>>>> _______________________________________________
>>>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>>>
>>>> _______________________________________________
>>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>>
>>>>  _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>



-- 

*Tyler Christiansen | Technical Operations*
tyler <http://adap.tv/>@adap.tv <http://adap.tv/> | www.adap.tv
*m :* 864.346.4095


More information about the juniper-nsp mailing list