[j-nsp] MX Forwarding Scale/Monitoring

[James Bensley]

On 5 September 2017 at 17:29, Harry Reynolds <harry at juniper.net> wrote:
> The memory is dynamic and can be allocated as needed. I think the key is that NH is limited to a maximum of 11 double mega words. What matters is overall utilization, and then how close NH is to having 11DMW, and if so, how much of that is used. To survive negative events we suggest that no more than 80-85% of the maximum 11 DMW be used.
>
> Here is OP from a box that is getting full. It has near 80% of the 11 DMW maximum allocated and of that, its 84% full.
>
> Regards
>
>
>
> NPC7(gallon vty)# sho jnh 0 poo usage
> EDMEM overall usage:
> [NH//////////////////|FW////////|CNTR///////////|HASH////////////|ENCAPS////|--------]
> 0                    8.0        12.0            18.0             24.7       28.8     32.0M
>
> Next Hop
> [*******************************************************************|------------] 8.0M (84% | 16%)
>
> Firewall
> [*|------------------|RRRRRRRRRRRRRRRRRRRR] 4.0M (3% | 97%)
>
> Counters
> [***********************|------------------------------------] 6.0M (38% | 62%)
>
> HASH
> [*******************************************************************] 6.7M (100% | 0%)
>
> ENCAPS
> [****************************************] 4.1M (100% | 0%)
>
> Shared Memory - NH/FW/CNTR/HASH/ENCAPS
> [**************************************|------------------------------------------] 7.2M (48% | 52%)
>
> DMEM overall usage:
> [-]
> 0 0.0M


Hi Harry,

Sorry for the delay in my response!

I am still plugging away with JTAC with only moderate success so
thankyou kindly for this info it is very useful.

Cheers,
James.