oh yeah, i've brought down the active node, and connectionless, icmp traffic fails over, but with a slight hit as i beleive the sessions are quickly re-created in the backup/now-active node. tcp telnet however does *not* failover and hangs.

here's my config portions of which you've shown.... differences being, i don't use a loopback nor a route instance.  you think that matters?

root@srx01> show configuration chassis high-availability local-id
1;
local-ip 172.21.0.0;

root@srx01> show configuration chassis high-availability peer-id 2
peer-ip 172.21.0.1;
interface ae3.0;
liveness-detection {
    minimum-interval 400;
    multiplier 5;
}

root@srx01> show configuration chassis high-availability services-redundancy-group 0
peer-id {
    2;
}

-------------------------------------------------------------------------------------

root@srx02> show configuration chassis high-availability local-id
2;
local-ip 172.21.0.1;

root@srx02> show configuration chassis high-availability peer-id 1
peer-ip 172.21.0.0;
interface ae3.0;
liveness-detection {
    minimum-interval 400;
    multiplier 5;
}

root@srx02> show configuration chassis high-availability services-redundancy-group 0
peer-id {
    1;
}


-Aaron

_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to