add another cisco router to HP-UX 10.2 system

[Stuart Johnson_2]

I have bought two new Cisco 801 routers to put a remote site onto a main HP-UX site.

The routers are up and running after a fashion over ISDN. BUT

The remote router cannot see the main machine. (Cannot ping it either).

The HP system already has one router set up as the default gateway so how do I add the address of the second router.

I can log in to each of the routers by telnet and can even log in to the main system through the routers via telnet. The customer does not have any sophisticated networking product only standard HP-UX.

[Sridhar Bhaskarla]

Hi Stuart,


Your setup is bit unclear to me. May be a small drawing may help.

If the default router has routes to the remote router, then you don't need to add the remote router to the HP system as the default router will take care of it. You need to make sure that the default router and the remote router communicate.

Otherwise, you need to use 'route' command.

route add net network (mask) router hop_count.

Look at the 'route' man page.

-Sri

[Stuart Johnson_2]

Hi Sri,

Thanks for starting help for me.

ok.

hp-ux system called d320
192.1.1.220
I
__________I_____________________
I I
I I
hemel router hemelb router
192.1.1.223 192.1.1.200
255.255.255.0 255.255.255.0
I I
I(Kilostream) I(Isdn)
I I
ramsgate router sls router
193.1.1.224 194.1.1.202
255.255.255.0 255.255.255.0
I I
HUB HUB
I I
PC PC
194.1.1.150
255.255.255.0
Default Gateway 194.1.1.202
Not a good diagram!
BUT it is the hemelb / sls side that is not working.
Attached is file of detail on route table, lanscan,if config and netconf files.

Could you help me with route commands needed and edit of netconf file if possible. I am not an engineer!! Cisco have been helpful on their side but of course can't really help once routers are up.

all routers are in /etc/hosts file and so is pc.

Thanks

Look forward to your answers.

Stuart

[Stuart Johnson_2]

Sri,

Attached is a bit map image of the network I am talking about. The text version I tried to draw in the previous message came out with garbage as you can see.

The hemel / ramsgate side has been up a long time and works fine. This is probably because the default gateway on the HP box is set to 192.1.1.223 (see previous attachments).

The new hemelb / sls side is the problem. There is no mention of 192.1.1.200 or 194.1.1.202 on the HP box except in the /etc/hosts file.

All that is attached at sls end are the router and some pc's and printers all in the same hub.

Help with any commands to do this will be greatly appreciated. Also if I need to do them at the console with no one on system, will it work live or will system need to be shutdown? I would prefer not to shut down system if possible. Production machine! They have no test machine.

Thanks

Stuart J

[Volker Borowski]

Hi Stuart,

with this setup, IP-Routing will not work at all!

The problem is, that you use 192.1.1.0 as a class C network on both sites. You need diffrent nets !

If you have no chance to change the networkadresses at one site, you might consider bridging. But I do not know, if the 801 is capable of this (Depending on the IOS it should be able to).

Basicly it would be easiest, to reconfigure the remote site as a 192.1.2.0 net, and then add static routes on both sides.
I can go in to detail on this, but if there is no chance to reconfigure the remote site, you need to track http://www.cisco.com for sample configs on bridging (I never did this, Sorry).

Let me know, what is possible
Volker

[Volker Borowski]

Ooops,

soory, just re-checked the drawing...
it is 194... sorry,sorry, sorry,...

So on the d320 (the left one), you need to

route add net 194.1.1.0 255.255.255.0 192.1.1.200 1

If both ciscos can ping each other, as the 194.1.1.150 PC has a correct default gateway, the PC should be able to ping the HP then

Volker

[Stuart Johnson_2]

Hi Volker,

Thanks for your help on this. It's great to know there are people out there trying to help people like me.

Questions??:
1) Will it be alright if I log into the d320 remotely by dial-up modem and make this change?
2) Will it take effect immediatly or do I have to reboot the machine before it works?
3) Are there changes to make to netconf file to make it permanent?

Thanks

Stuart

[Sridhar Bhaskarla]

Hi Stuart,

Sorry for getting back to you later. Your configuration should work. And you just need to add a static route with 192.1.1.200. The command has already been given by Volker.

1. Yes.
2. It will take effect immediately and it will start working as soon as you complete the command.
3. Yes. You need to make changes to your netconf file as follows.

ROUTE_DESTINATION[2]="net 194.1.1.0 "
ROUTE_MASK[2]="255.255.255.0"
ROUTE_GATEWAY[2]="192.1.1.200"
ROUTE_COUNT[2]="1"

-Sri

[Sanjay_6]

Hi,

you have to set the local router to route the traffic for the remote server to the port/modem to which the remote router/server are connected.

Hope this helps.

Regds

[Stuart Johnson_2]

Sri, Volker, Sanjay

I have tried the route add command and get an error message as below any thoughts please??

The routes are up as i can telnet to them from central machine, logging in as I go. See below for info.

I am sure we are getting there and appreciate your help.

Why "Network is unreachable" ????

Thanks

Stuart

# route add net 194.1.1.0 255.255.255.0 192.1.1.200 1
add net 194.1.1.0: gateway 255.255.255.0: Network is unreachable

# netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface Pmtu PmtuTime
127.0.0.1 127.0.0.1 UH 0 184 lo0 4608
192.1.1.220 127.0.0.1 UH 0 1760951 lo0 4608
default 192.1.1.223 UG 0 8901499 lan0 1500
192.1.1 192.1.1.220 U 337848017 lan0 1500
#
# ping 192.1.1.200
PING 192.1.1.200: 64 byte packets
64 bytes from 192.1.1.200: icmp_seq=0. time=4. ms
64 bytes from 192.1.1.200: icmp_seq=1. time=1. ms
64 bytes from 192.1.1.200: icmp_seq=2. time=2. ms
64 bytes from 192.1.1.200: icmp_seq=3. time=2. ms
64 bytes from 192.1.1.200: icmp_seq=4. time=2. ms
64 bytes from 192.1.1.200: icmp_seq=5. time=2. ms
64 bytes from 192.1.1.200: icmp_seq=6. time=1. ms
64 bytes from 192.1.1.200: icmp_seq=7. time=1. ms

----192.1.1.200 PING Statistics----
8 packets transmitted, 8 packets received, 0% packet loss
round-trip (ms) min/avg/max = 1/1/4
# telnet 192.1.1.200
Trying...
Connected to 192.1.1.200.



xxxxxxxx#telnet 194.1.1.202
Trying 194.1.1.202 ... Open


User Access Verification

Username:
Password:
zzzzzzzz>en
Password:
zzzzzzzz#ping 192.1.1.220

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.1.1.220, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
zzzzzzzz#exit

[Connection to 194.1.1.202 closed by foreign host]
xxxxxxxx#exit
Connection closed by foreign host.

[Sridhar Bhaskarla · Accepted solution]

Hi Stuart,

The command is

# route add net 194.1.1.0 netmask 255.255.255.0 192.1.1.200 1

Look at the netmask keyword.

-Sri

[Ron Kinner]

Since the HP already has a default route to the 1603 router the real problem is that either the 1603 does not know how to get to the 194.1.1.0 network or the 801 at 194.1.1.202 does not know how to get to the 192.1.1.0 network.

Do:

traceroute 194.1.1.202

and see where the reply comes from. If it's the 1601 then it needs a route.

conf t
ip route 194.1.1.0 255.255.255.0 192.1.1.200
end
wr me


If it's the first 801 then the second 801 does not know how to get back to the 192.1.1.0 network. The route statement is a bit trickier since I don't know how they have it configured. You could try
conf t
ip route 194.1.1.0 255.255.255.0 bri0
end
wr me

You might need to substitute dialer1 for bri0 or there may be an IP address on the ISDN link on HEMELB that you should use.

Post the config of the router if you need help.

Capture the output of:
term le 0
sh run.

You will probably want to duplicate this for the 193.1.1.0 network too if you want the SLS router to talk to RAMSGATE. Either that or use 0.0.0.0 0.0.0.0 (Cisco speak for default gateway)on SLS instead of the 192.1.1.0 255.255.255.0.

Ron

[Sanjay_6]

Hi Stuart,

I was suggesting to configure the route on the router and not on the hp. you hcan have the default gateway/route set on the hp side with the ip address of the router. now on the router you have to configure the route so that when it receives a request for an ip on the remote network, it will route the info to the remote router. So you have to configure the router to allow the info on network port to go through the port through which your remoter router is connected. you will have to look at the router configuration.

Hope this helps.

Regds

[Sanjay_6]

Hi Stuart,

Try this link on step by step guide to configure your router.

http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/827/827swcfg/routcfig.htm

Hope this helps.

regds

[Stuart Johnson_2]

Hi Ron,Sanjay, Sri, Volker,

Sri,
Thanks for revised route command that went in ok on d320.

We are definitely getting somewhere now.

Not quite there but moving forward.

Results are:-

1) Can ping the remote (sls) router 194.1.1.202 now when logged onto d320 computer.
2) Can telnet directly to remote (sls) router.

But

When "telneted" down onto remote (sls) router cannot ping 192.1.1.220 (d320).

I attach following file for perusal by Ron,Sanjay or whoever to look at please.
it contains:

1) remote sls router config
2) central hemelb router config
3) Traceroute output
3) netstat -rn

All help would be appreciated.
Going to remote site tommorrow!!

Thanks

Stuart

[Ron Kinner]

When you ping from SLS, you send out packets with a source address equal to that of the interface that the packet leaves the router on. In this case, 192.168.50.2. This address is apparently also not known to the 1600 router which is the default for the HP box.

If you want this to work you have two choices: Add another route to the HP or another route to the default router. Same syntax as before just now we are going to 192.168.50.0

You can do an extended ping from SLS and change the source address to that of the Ethernet port and it will work. You do an extended ping by just typing
ping
ip
192.1.1.220
and then accepting the defaults until you get to where the default is "n". Change this to a "y" and the next prompt will be source address. Type in the 194 address and accept the rest of the defaults.

Worked didn't it?

Ron

[Stuart Johnson_2]

Sri, Volker, Sanjay, Ron,

Thanks all of you for your great help in this matter.

I have been on-site and all is working well now.

I could not have done it without your help.

I have awarded points ( I hope fairly!).

Hope to here from you again sometime.

Once again thanks.


Regards

Stuart Johnson