[j-nsp] EX4200 filter buggy?

[Charlie Allom]

Hello,

has anyone else seen these messages:

Dec  2 13:29:43  sw0.cll fpc0 Invalid prev page id 101 and next page id 101 for fw -559038737 
Dec  2 13:29:45  sw0.cll fpc2 Invalid prev page id 101 and next page id 101 for fw -559038737 
Dec  2 13:29:50  sw0.cll fpc1 Invalid prev page id 100 and next page id 100 for fw -559038737 
Dec  2 13:29:51  sw0.cll fpc0 Invalid prev page id 102 and next page id 102 for fw -559038737 
Dec  2 13:29:54  sw0.cll fpc2 Invalid prev page id 102 and next page id 102 for fw -559038737 
Dec  2 13:29:58  sw0.cll fpc1 Invalid prev page id 101 and next page id 101 for fw -559038737 
Dec  2 13:29:59  sw0.cll fpc0 Invalid prev page id 103 and next page id 103 for fw -559038737 
Dec  2 13:30:02  sw0.cll fpc2 Invalid prev page id 103 and next page id 103 for fw -559038737 
Dec  2 13:30:03  sw0.cll mib2d[843]: LIBJSNMP_NS_LOG_WARNING: WARNING: AgentX master agent failed to respond to ping.  Attempting to re-register. 
Dec  2 13:30:06  sw0.cll fpc1 Invalid prev page id 102 and next page id 102 for fw -559038737 
Dec  2 13:30:08  sw0.cll fpc0 Invalid prev page id 104 and next page id 104 for fw -559038737 
Dec  2 13:30:10  sw0.cll fpc2 Invalid prev page id 104 and next page id 104 for 

...repeating for up to an hour on a commit on firewall filters? pfem
process also runs at 100% cpu and starts to impact things like SNMP.

JTAC just can't or wont advance on my case. I'm beginning to think one
of the PFE's is broken somehow..


Is there a way to know what firewall filter "-559038737" is?


Regards,
  C.
-- 
 020 7729 4797
 http://playlouder.com/