Symptoms

-- Log message written to TMM log file: panic: ../kern/page_alloc.c:736: Assertion "vmem_hashlist_remove not found" failed.

Impact

Traffic disrupted while tmm restarts.

Conditions

-- Virtual Server using a traffic-matching-criteria (TMC) with a destination-port-list, with multiple distinct ranges of ports. -- Config changes to virtual server with traffic-matching criteria can cause memory corruption which can lead to delayed TMM crashes.

Workaround

Do not use Traffic Matching Criteria with destination port lists. TMM restart is required in case the virtual server is modified with traffic-matching-criteria related config.

Fix Information

TMM no longer crashes under these conditions.

Behavior Change