[j-nsp] ipv4/ipv6-flow-table-size

[Scott Harvanek]

Scott,

Thanks, my next question then with that is - how/why is the default of 
ipv4 15 and ipv6 1?  That would break that constraint of 15 total?

Scott H.
Login Inc.

On 8/25/14, 3:53 PM, Scott Granados wrote:
> When ever you set the flow table size you initiate a reboot of the FPC.  The table size is a combined value of v4 and v6 so 15 total a subset of which is IPV4 and the remainder is IPV6.
>
> Thanks
> Scott
>
> On Aug 25, 2014, at 3:02 PM, Scott Harvanek <scott.harvanek at login.com> wrote:
>
>> I'm wondering if anyone can clarify something for me from docs:
>>
>> "
>>
>>   * Any change in the configured size of flow hash table sizes initiates
>>     an automatic reboot of the FPC.
>>   * The total number of units used for both IPv4 and IPv6 cannot exceed 15.
>>
>> "
>>
>> - Does the initial config entry of ipv4/ipv6-flow-table-size cause the
>> FPC to reboot or only if the configured value is changed?
>>
>> -- I.e. the default for IPv4 size is 15, if that gets changed [ not
>> currently set in config ] does that cause a reboot?
>>
>> Also, is 15 the maximum aggregate or is it per table:
>>
>> -- Can you have 15 units assigned to IPv4 and IPv6 at the same time? or,
>> is 15 the maximum between the two?
>>
>> Thanks!
>> -SH
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp