[j-nsp] MX80 BGP performance after reboot

[Sebastian Wiesinger]

Hi,

I noticed that a MX80 takes quite a long time after reboot to put all
routes into the KRT. Is that normal for that box? It takes around 10
minutes after BGP is established to get all the routes into the KRT
and in the meantime we get messages like that every few seconds:

/kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 953500. States to be processed - 21526
rpd[1298]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available
/kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2, rtsm_id 5, msg type 2
/kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 953500. States to be processed - 21545
rpd[1298]: RPD_KRT_Q_RETRIES: Route Update: No buffer space available
/kernel: rt_pfe_veto: Too many delayed route/nexthop unrefs. Op 2, rtsm_id 5, msg type 2
/kernel: rt_pfe_veto: Possible slowest client is sampled. States processed - 953500. States to be processed - 21558
/kernel: rt_pfe_veto: Possible second slowest client is xdpc0. States processed - 1064571. States to be processed - 23

Oh and DDOS protection is also acting up:

jddosd[1323]: DDOS_PROTOCOL_VIOLATION_SET: Protocol TTL:aggregate is violated at fpc 0 for 1 times, started at 2013-02-11 23:50:39 CET, last seen at 2013-02-11 23:50:39 CET
jddosd[1323]: DDOS_PROTOCOL_VIOLATION_CLEAR: Protocol TTL:aggregate has returned to normal. Violated at fpc 0 for 1 times, from 2013-02-11 23:58:14 CET to 2013-02-11 23:58:14 CET

Any experiences from anyone else here?

Regards

Sebastian

-- 
GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0 B9CE)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.
            -- Terry Pratchett, The Fifth Elephant