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
Identity Router Network Interfaces and Default Ports 244Number of Views ManageEngine ADSelfService Plus - RADIUS Configuration - RSA Ready Implementation Guide 1Number of Views CrowdStrike Falcon Identity Protection - RSA Ready Implementation Guide 20Number of Views Deploying an Identity Router (Video) 14Number of Views View Network Diagnostics on an Identity Router 35Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle