[f-nsp] NetIron 5.8f feedbacks

[Youssef Bengelloun-Zahr]

@David : No new CAM profiles. I too need to resize in order to accomodate IPv6 DFZ growth.

@Martijn : yep, the nasty IPSec bug was corrected, with a couple others we were impacted by. Need to lab it a bit, but I think it's the one.

BR.



> Le 16 déc. 2016 à 19:20, David Hubbard <dhubbard at dino.hostasaurus.com> a écrit :
> 
> Curious if there are any new cam profiles available?  Ideally to max out ipv4 + ipv6 but leave room for one VRF (mgmt).
> 
> Thanks if anyone knows
> 
> On 12/16/16, 1:14 PM, "foundry-nsp on behalf of i3D.net - Martijn Schmidt" <foundry-nsp-bounces at puck.nether.net on behalf of martijnschmidt at i3d.net> wrote:
> 
>    Hi Youssef,
> 
>    The 5800 code train has been working well for us over the last couple of
>    months. We weren't impacted by the IPsec packet linecard crash bug that
>    was introduced and fixed a couple of letter releases ago since we had
>    already locked everything down with receive ACL's to begin with. But
>    other than that, smooth sailing!
> 
>    Best regards,
>    Martijn
> 
>>    On 12/16/2016 06:42 PM, Youssef Bengelloun-Zahr wrote:
>> All,
>> 
>> It came out à few weeks ago and seems it to be the lucky charm... At least for us. It was also designated as the new official target path.
>> 
>> Any feedbacks from out there ? Any head acks in perspective ?
>> 
>> Thank you.
>> _______________________________________________
>> foundry-nsp mailing list
>> foundry-nsp at puck.nether.net
>> http://puck.nether.net/mailman/listinfo/foundry-nsp
> 
>    _______________________________________________
>    foundry-nsp mailing list
>    foundry-nsp at puck.nether.net
>    http://puck.nether.net/mailman/listinfo/foundry-nsp
> 
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp