Static Routes
AM 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 AM instance to an AM 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 AM 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 AM 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:
Related Articles
Deploying an Identity Router (Video) 15Number of Views View Network Diagnostics on an Identity Router 35Number of Views ITIM Collector fails with 'java.net.BindException: Address already in use' error in RSA Identity Governance & Lifecycle 64Number of Views Deploying an Identity Router - Advanced Setup 122Number of Views Identity Router Network Interfaces and Default Ports 283Number of Views
Trending Articles
Unable to login to RSA Authentication Manager Security Console as super admin Authentication Manager Administration Server with operations console service Fails to Start with "No config.xml Was Found"… Authentication Manager Security Console and Operations Console Inaccessible After Certificate Update How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA Authentication Manager Upgrade Process