Although configuration of a redundant redirect server is optional, we recommend that you configure redundancy to maintain high availability for the server.
Before you configure the redirect server, review configuration prerequisites. See Before You Configure Redundancy for a Redirect Server.
Use the following configuration statements to configure redundancy for the redirect server:
- redirect-server {
- redundancy;
- }
- redirect-server monitor {
- redundant-host-ip-address redundant-host-ip-address;
- virtual-ip-address virtual-ip-address;
- real-ip-address real-ip-address;
- primary-server;
- check-interval check-interval;
- virtual-routers virtual-routers;
- }
To configure redundancy for the redirect server:
- user@host# edit redirect-server
- [edit redirect-server]
- user@host# set redundancy
- [edit redirect-server]
- user@host# edit redirect-server monitor
- [edit redirect-server]
- user@host# set redundant-host-ip-address redundant-host-ip-address
- [edit redirect-server]
- user@host# set virtual-ip-address virtual-ip-address
- [edit redirect-server]
- user@host# set real-ip-address real-ip-address
When a primary redirect server is started, it dynamically establishes and maintains a static route on the client router to which it connects. The static route directs traffic destined for the virtual IP address of the server to the real IP address of the active redirect server.
- [edit redirect-server]
- user@host# set primary-server
- [edit redirect-server]
- user@host# set check-interval check-interval
A shorter time in the range leads to faster detection of problems and results in higher consumption of CPU resources.
- [edit redirect-server]
- user@host# set virtual-routers vrName@routerName, vrName@routerName ...