After upgrading Junos on MX series routers, the Syslog messages with keywords, 'jnh_init_cassis_mem' and 'cassis_index_alloc_pool_create' are seen repeatedly and frequently flooding the device.
'jnh_init_cassis_mem'
'cassis_index_alloc_pool_create'
Logs from Syslog:
Aug 9 12:02:41.690 Router_RE0 fpc4 cassis_index_alloc_pool_create: SVC NH 0x40700000[0] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.691 Router_RE0 fpc4 jnh_init_cassis_mem(2645): PFE 0 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced.
After upgrading (for example, from 17.4 to 18.4R1) the following messages may be seen repeating frequently indicating next-hop pool size and memory details :
Aug 9 12:02:41.690 Router_RE0 fpc14 cassis_index_alloc_pool_create: SVC NH 0x40700000[0] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.690 Router_RE0 fpc4 cassis_index_alloc_pool_create: SVC NH 0x40700000[0] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.691 Router_RE0 fpc4 jnh_init_cassis_mem(2645): PFE 0 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.691 Router_RE0 fpc14 jnh_init_cassis_mem(2645): PFE 0 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.693 Router_RE0 fpc4 cassis_index_alloc_pool_create: SVC NH 0x40700000[1] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.693 Router_RE0 fpc14 cassis_index_alloc_pool_create: SVC NH 0x40700000[1] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.694 Router_RE0 fpc4 jnh_init_cassis_mem(2645): PFE 1 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.694 Router_RE0 fpc14 jnh_init_cassis_mem(2645): PFE 1 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.696 Router_RE0 fpc14 cassis_index_alloc_pool_create: SVC NH 0x40700000[2] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.697 Router_RE0 fpc14 jnh_init_cassis_mem(2645): PFE 2 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.697 Router_RE0 fpc4 cassis_index_alloc_pool_create: SVC NH 0x40700000[2] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.698 Router_RE0 fpc14 cassis_index_alloc_pool_create: SVC NH 0x40700000[3] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.698 Router_RE0 fpc4 jnh_init_cassis_mem(2645): PFE 2 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.699 Router_RE0 fpc14 jnh_init_cassis_mem(2645): PFE 3 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced. Aug 9 12:02:41.700 Router_RE0 fpc4 cassis_index_alloc_pool_create: SVC NH 0x40700000[3] poolsize 0x000fffc0 is not a multiple of blk_sz 0x00001000. Aug 9 12:02:41.701 Router_RE0 fpc4 jnh_init_cassis_mem(2645): PFE 3 Services NH 0x40700000 - 0x40800000 mem_pool j_do_not_del forced.
These messages are non-impacting in nature and does not cause any impact. The messages can be safely ignored or suppressed. You can either configure your NMS systems to ignore the messages or prevent them from writing to Syslog. Refer to KB9382 - How to prevent certain syslog messages from being written to the log file [juniper.net]
This issue is resolved on devices running the versions below: