Static Routes

Document created by RSA Information Design and Development on Jun 13, 2017Last modified by RSA Information Design and Development on Jun 13, 2017
Version 2Show Document
  • View in full screen mode

Authentication Manager supports the creation of IPv4 and IPv6 static routes. Static routes send data through a network on a fixed, predictable path.

For example, you can create an IPv4 static route for all network traffic from an Authentication Manager instance to an Authentication Manager web tier. The default route to an internal router would be used for other network traffic from the instance. If the static route to the web tier becomes unavailable, the network traffic intended to take that route is not sent.

You can create persistent and non-persistent static routes:

  • A persistent static route is not deleted if the Authentication Manager instance is rebooted or if the interface with which the static route is associated is unavailable.

  • A non-persistent static route is deleted if the Authentication Manager instance is rebooted or if the interface with which the static route is associated is unavailable. A non-persistent static route might be used to test a network route, or as a temporary path if part of the network is being repaired or restored.

To add a static route, see the appropriate instructions for your network:

To delete a static route, see the appropriate instructions:

 

 


Attachments

    Outcomes