Clustred servers see remote printer differently

[John Donaldson]

I have two clustered K Class servers on one subnet and a printer on another subnet connected via a frame relay link. I have my routers configured correctly so that I can ping and traceroute to the printer from my 2000 workstation, the router, and my secondary HP-UX server that is NOT running the package. I cannot ping or traceroute from the primary server running the serviceguard package and my database that I need to print from. How do I get my primary server to clear and update it's routing table to know the correct route to my other subnet?

[John Poff · Accepted solution]

Hi,

The only difference might be that your primary server is running a package and could have a package IP address, depending on how you have configured it. I can't see how that would really make a difference, unless the package IP is conflicting with something else, and that would be pretty obvious.

Do both boxes have the same default route in their routing tables? Can you give us some examples of IP addresses and maybe the output from 'netstat -rn' from each box?

JP

[John Donaldson]

John,

Thanks for the reponse. I found the problem. The particular printer I was trying to reach had a very old default gateway assigned in the network devices control panel in sam. I switched it to the current default gateway and immediately was able to print. Thanks again. - JD