About SRRD: - CPU usage: beware of PR1170656. Told to be fixed in 14.2R7 15.1R4 15.1F6. - Mem usage: beware of PR1187721. Told to be fixed only in future or service releases (14.2R8 15.1R5 15.1F6-S2 16.1R3).
> On 25 oct. 2016 at 14:23, Mark Tinka <mark.ti...@seacom.mu> wrote : > On 25/Oct/16 14:16, sth...@nethelp.no wrote: >> We see significantly higher rpd CPU usage for a while after IPfix flow >> export is enabled. However, it seems to settle down to normal levels. > > Yes, that's normally SRRD (Sampling Route-Record Daemon) starting up and > making sure all is well for the collection and export of the flows. > > We've seen issues where SRRD can hang the box quite badly if a number of > BGP sessions are de-activated in one go (and vice versa). In such cases, > the only fix was to reboot the box. This was on the MX80. > > SRRD seems reasonably fragile (and buggy), particularly in high > route-churn situations. You want to stay on top of it, i.e., fix bugs > when they are announced, e.t.c. > > Otherwise, under normal conditions, exporting will be done inline, so it > won't touch the RE. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
