Support > Knowledge Base
Knowledge Base

Search the Knowledge Base: |
Search the Knowledge Base: |
Adding a static route to an ESX host for an extra service console
Symptoms
- Packet loss when using two service consoles
- Intermittent packet loss with two service consoles
- IP requests arrive at second service console IP but do not return because there is only one configurable gateway for service consoles
Resolution
You must add a static route so that traffic responds from the correct service console interface.
Note: In the following commands:
- 142.121.56.0/23 is the remote IP trying to communicate with the second service console.
- 224.58.175.75 is the second service consoles IP.
- 224.58.175.1 is the Gateway IP for the second service console.
Configure the route using the command:
route add -net 142.121.56.0 netmask 255.255.254.0 gw 224.58.175.1
Add the following line to /etc/rc.local so that route is set on boot:
/sbin/route add -net 142.121.56.0 netmask 255.255.254.0 gw 224.58.175.1
If route does not hold on reboot, create an executable file.
To create an executable file:
- cd to the directory /etc/init.d.
- Create a file called routes with the command:
vi routes
- Make the file executable with the command:
chmod 777 routes
-
Add the following code to the file:
##! /bin/bash # case "$1" in 'start') echo "Adding additional routes... "
/sbin/route add -net 172.31.3.0 netmask 255.255.255.0 gw 172.31.8.1 echo ;; *) echo "Usage: $0 { start }" ;; esac -
Save and exit out of VMware Infrastructure Client.
-
cd to the directory /etc/rc3.d.
-
Create a symbolic link to that file, then reboot.
Additional Information
For more information, see How do I configure static routes in Red Hat Enterprise Linux version 3? in the Red Hat Knowledge Base.
Note: The preceding link was correct as of July 29, 2009. If you find the link is broken, provide feedback and a VMware employee will update the link.
Feedback
Actions
- KB Article: 1005212
- Updated: Aug 20, 2009
- Products:
VMware ESX

