Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Creating a static route for the VMware Channel (1023026)

Last Updated: 3/20/2024Categories: How toTotal Views: 7554Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article provides steps to add a static route for the VMware Channel when deployed in a WAN environment.

Resolution

When configured for WAN deployment, the VMware Channel IP addresses at the remote (disaster recovery) site are in a different subnet than those in a LAN and therefore require persistent static routes to maintain continuous communications between servers independent from traffic on the Principal (Public) Network.

VMware does not recommend implementing routing that uses Interface IDs (appears as a number starting with 0x on a print route 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.

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).

For the static routes to be implemented, perform these steps on both servers:

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

To workaround this issue for Windows 2000 and 2003:

From Administrative Tools, click Routing and Remote Access, and select the server name.

From the Action menu, click Configure and Enable Routing and Remote Access. The configuration wizard starts.

Click Custom Configuration > LAN routing. Verify that the RRAS service is started (in Windows 2000, select Manually Configured Server).

Select the server, navigate to IP Routing, and select Static Routes.

From the Action menu, click New Static Route.

Select the VMware Channel NIC, enter the remote VMware Channel IP, followed by the mask 255.255.255.255 and the local machine gateway.

To ensure that all packets are sent through the Channel IP and not the Primary (Public) IP, test the Channel routing with the command:

pathping -n Channel_IP

Repeat steps 1 through 7 to configure a static route from the remote host to the local host.

To workaround this issue for Windows 2008 and 2008 R2:

Click Start > Run, type cmd, and click OK. The Command Prompt window opens.

Run this command on both the Primary and Secondary servers where you want to add the route:

netsh interface ipv4 add route Subnet_IP/32 "Adapter_Name" Channel_IP

For more information, see Using Netsh.

To ensure that all packets are sent thorough the Channel IP and not the Primary (Public) IP, test the Channel routing using this command:

pathping -n Channel_IP

Repeat these steps on the secondary server if necessary.

Related Information

vCSHB-Ref-1679

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Heartbeat

Related Versions:

VMware vCenter Server Heartbeat 6.4.x

VMware vCenter Server Heartbeat 6.3.x

VMware vCenter Server Heartbeat 5.5.x

Take Our Survey

Support Assistant