> i have a problem on one of our M10i. > System log continously shows following errors: > > Jan 19 15:59:03 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 3 (PREFIX > CHANGE) failed, err 5 (Invalid) > Jan 19 15:59:03 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 1 (PREFIX > ADD) failed, err 6 (No Memory) > Jan 19 15:59:07 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 3 (PREFIX > CHANGE) failed, err 6 (No Memory) > Jan 19 15:59:15 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 1 (PREFIX > ADD) failed, err 6 (No Memory) > Jan 19 15:59:23 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 3 (PREFIX > CHANGE) failed, err 5 (Invalid) > Jan 19 15:59:27 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 1 (PREFIX > ADD) failed, err 6 (No Memory) > Jan 19 15:59:27 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 3 (PREFIX > CHANGE) failed, err 5 (Invalid) > Jan 19 15:59:30 MYROUTER /kernel: %KERN-1-RT_PFE: RT msg op 1 (PREFIX > ADD) failed, err 6 (No Memory) > > But there is no traffic impact.... > I tried further investigation with some commands i found in older mailings. > But without success... > > u...@myrouter> start shell pfe network cfeb0 > vty: connect: Connection refused
This probably doesn't work precisely because there is insufficient CFEB memory. We have seen exactly this happen. Sooner or later it probably *will* impact traffic. > I could imagine that a reload will clear the problem, but i would like > to avoid it... A reload is probably the only fix. And you *really* want to monitor your CFEB memory utilization (show chassis cfeb). We are in the process of upgrading all our M7i/M10i CFEBs to 256 MB. Steinar Haug, Nethelp consulting, sth...@nethelp.no _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
