|
APPANAH Ravi wrote:
1. Please do not post with all uppercase subjects.
Uppercase letters are only for shouting.
2. This is a routine problem. There is nothing
urgent about it. Remember the story about
"The Boy who cried Wolf"
> Is director's default gw 2 hops away and is director one hop away on the
> path to the director's gw?
> YES
where do you get this string "YES" from? There is no string "YES" in the script
the script is executing the block for "no".
> error: the path to the director's default gw does not go through the
> director.
> hops to director's gw 30
> hops to director 1
> this vs-nat LVS will not work.
Thanks for the attached files.
The script appears not to be parsing the output of traceroute correctly.
I assume that the placement of output of your commands is different to
mine.
The command that isn't working as I expect are (from your rc.lvs_nat script)
HOPS_TO_DIRECTOR=`traceroute 10.0.144.32 2>/dev/null | grep "(192.168.1.1)" |
cut -c0-4`
so that I can figure out what is happening,
please run these commands and send the output to me
1. traceroute 10.0.144.32
2. traceroute 10.0.144.32 2>/dev/null
3. traceroute 10.0.144.32 2>/dev/null | grep "(192.168.1.1)"
4. traceroute 10.0.144.32 2>/dev/null | grep "(192.168.1.1)" | cut -c0-4
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
