Subject: | |
From: | |
Reply To: | |
Date: | Thu, 2 Oct 1997 14:29:00 -0400 |
Content-Type: | Text/Plain |
Parts/Attachments: |
|
|
HP3000 network gurus....I need your help.
As we convert our network under a class C network, I have had to make some
changes in the routing tables under NMMGR on 5.5 (we just went up on 5.5
last week on this system)
Anyway, users on the 10.3.24.x network can't get to this system. This is
how nettool presents the situation.
:nettool.net
NETTOOL Version: B0509000
Enter HELP HELP for an explanation of the help facility.
Enter HELP OPERATION for guidance on NETTOOL use.
Commands can be abbreviated, HELP keywords cannot.
Menu-specific commands for the ROOT:
RESOURCE CONFIG NAMEADDR PING STATUS NMDUMP
X25STAT X25CHECK IPCINT XPVAL XPPERF QVALNS
NSTEST LOOPINIT NSLOGON SOCKINFO filters
[1]>>>name
CACHE MAPPINGS ROUTING PATH filters
[2]NAMEADDR>>>rout
ROUTING DELROUTING TOTALS filters
networkfilter gatewayfilter
[3]NAMEADDR.ROUTING>>>rout
Network address filter: @
Gateway address filter: @
Network number Subnet mask Gateway Hops Flags
______________________________________________________________
10.0.0.0 255.0.0.0 192.23.1.163 1 2
10.2.8.0 255.255.255.0 192.23.1.253 **** 2
10.3.24.0 255.255.255.0 192.23.1.163 **** 2
172.16.1.0 255.255.255.0 192.23.1.163 1 2
172.16.2.0 255.255.255.0 192.23.1.163 1 2
172.16.4.0 255.255.255.0 192.23.1.163 3 2
172.16.6.0 255.255.255.0 192.23.1.163 3 2
172.16.8.0 255.255.255.0 192.23.1.163 3 2
172.16.11.0 255.255.255.0 192.23.1.163 1 2
172.16.12.0 255.255.255.0 192.23.1.163 1 2
192.23.2.0 255.255.255.0 192.23.1.228 2 2
204.145.212.0 255.255.255.0 192.23.1.206 1 2
______________________________________________________________
Total number of routings = 12
[4]NAMEADDR.ROUTING>>>
In the past, I have just gone in and deleted (from this prompt in nettool)
the route via the gateway 192.23.1.163. This would make the hops column
all become "****" for all gateways with 192.23.1.163.
I then go out and enter
NETCONTROL UPDATE=INTERNET;NET=LAN1
This would normally fix it. However it stays looking like this. I even
went so far as to go into nmmgr and take out the 10 network entry and
reaload (netcontrol...). It blew my session away on my address 10.1.8.10)
What is interesting is I only have *one* entry for the 10 network in nmmgr
and that would be to the 10.1.0.0 network with the gateway of
192.23.1.163.
I have schedule our operations folks to restart the system tonight. I
would think that stoping and restarting the LAN would take care of it, but
they normally do that evey night *and* the users had the symptoms
yesterday even though I did not look at the routing table until today.
Does anyone have any idea on how to *really* blow away these bad routing
entries?
Thanks in advance
/alan
[log in to unmask]
|
|
|