Hi RK,
I agree that it is not terribly well documented.
NetScreens keep software and hardware sessions. When a route changes (either dynamically, or bystatic route changes) a process goes through the software sessions, and changes the next hop mac address. The hardware sessions are then deleted, so that subsequent packets are directed to the CPU, and the software session is copied back into the hardware, so packets can be processed by ASIC again.
So in answer to your question, if a route changes (or indeed an arp address) the session will continue, and an internal process will direct the packets to the new next hop. This does raise the CPU load though.
The only exception to this is where the new next hop is in a different zone to the old one, in which case a whole first packet processing flow may be required.
Sam.
#session#screenos#Route