> > However the RR concept is quite flexible, a RR itself can be a client of > > another RR ( hierarchically or at peer level) > > No, I'm not talking about hierarchy. Let's consider a setup with two > redundant RRs in the same cluster. They are certainly not each other's > clients, but they must have a session between them, and an identical > client-id on both. How would you configure this?
You normally don't. Each RR in its own cluster has been best practice for quite a while. Steinar Haug, Nethelp consulting, sth...@nethelp.no _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
