Mailing List Archive

Hi,

according to Junos documentation, the "no-drift" option makes sure,
that the delay caused in triggering an event does not propagate to the
triggering of the next event. Even without "no-drift", the time which
takes the policy to complete, does not affect the start-time of the
next policy. Under which circumstances the "no-drift" option has an
affect? In addition, what does it do in Junos internally?


thanks,
Martin
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp