This knowledge base article contains the following information regarding this log message: 1. Issue 2. Purpose 2. Impact 3. Solution
This message is logged in to the syslog file, you might see a process(PFEM) spike for some time when you do the commit.
These error can get reported when a new rule is added between two existing rules in a firewall. The function which is responsible to find an empty page in TCAM between previous rule and the next rule returns this error when the previous rule name and next rule name are the same. Impact:
There are no implications to this error because after this error is dumped, the same function is called to find an empty page anywhere in the TCAM, and then the previous and the next rules are moved correspondingly. Thus, the behavior would correct itself in this next step. The page_id's for both the previous and the next rule is the same, but the entry_id is different signifying that both the rules occupy a different hw-index in TCAM. This is not an error condition and is correct behavior as per design, even though an error is being dumped it is not an error condition.
The methodology to find new empty pages when a new rule is added has been optimized in Junos Releases 10.1, and later. These errors will not be visible after Junos Release 10.1, and all later releases.