SolarWinds - How to Create a Static Route Between Orion Failover Engines Servers Deployed in a LAN in Different Subnets

Follow

Summary

This article provides information on how to set up static routing between Orion Failover Engine servers deployed in a LAN with different subnets.


More Information

When configured for LAN deployment with different subnets for the primary and secondary servers, the SolarWinds Channel IP will require a persistent static route to maintain continuous communications between servers independent from traffic on the principal network. SolarWinds recommends against implementing routing that uses Interface IDs (appears as a number starting with 0x on a route print result), because an interface id is dynamic and can change when a server is restarted or a NIC is disabled and re-enabled.

Note: Microsoft Windows supports only one gateway per server.


Procedure

It is necessary to create a static route using the destination (channel of other server), a locked down mask of 255.255.255.255 with a default gateway for the channel subnet (this means that only the channel NIC can contact the other channel IP and nothing else). In order for the static routes to be implemented, use the following procedure on both servers.

Note: Before starting this procedure, verify that the Routing and Remote Access service (RRAS) is started and set to Automatic on all servers.

  1. From Administrative Tools , select Routing and Remote Access , and select the server name.
  2. From the Action menu, select Configure and Enable Routing and Remote Access. The configuration wizard starts.
  3. Select Custom Configuration and LAN routing. Verify that the RRAS service is started.
  4. Select the server, navigate to IP Routing , and select Static Routes .
  5. From the Action menu, select New Static Route .
  6. Select the channel NIC, enter the secondary servers channel IP address followed by the subnet mask 255.255.255.255 and the default gateway for the channel subnet.
  7. Repeat steps 1 through 6 to configure a static route from the secondary server to the local primary server.

Test the channel routing from both sides using the following command to ensure that all packets are sent thorough the channel IP and not the primary IP:

pathping -n Channel_IP

On Windows Server 2008 with the IIS Service Installed

On Windows Server 2008, the Routing and Remote Access service (RRAS) is dependent on the HTTP service. When the IIS service is installed on an Orion Failover Engine server group, the plug-in will stop the HTTP service on the secondary server. This causes the Routing and Remote Access (RRAS) service to stop and results in dropping the channel. To resolve this issue, use the ROUTE ADD command from the command line as shown below:

  1. Click Start > Run, type CMD , and click OK to open a command prompt window.
  2. From the command prompt type:

ROUTE ADD [DestinationIPAddress] MASK [netmask] [Gateway] METRIC [metric] IF [Interface] -p

For example:

ROUTE ADD 157.0.0.0 MASK 255.255.255.255 157.55.80.1 METRIC 3 IF 2 -p

  1. Close the command prompt window.

For further information, please contact your SolarWinds Support Representative.


Applies To

All versions


Related Information

Microsoft TechNet article — Add a static IP route

KBID-2206

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.