[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference lassie::ucx

Title:DEC TCP/IP Services for OpenVMS
Notice:Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:ucxaxp.ucx.lkg.dec.com::TIBBERT
Created:Thu Nov 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5568
Total number of notes:21492

5528.0. "Errors; ROUTEERROR & DUPRECORD when adding route" by KAOT01::WATTERS () Thu May 22 1997 15:18

Getting errors when adding networks to a route IF the address
starts w/ 10.x.x.x
In the following example, I can add a destination route to 10.61.1.0
w/o a problem but when I add another 10.'something' it fails.



UCX> sh route

                             DYNAMIC database

Type           Destination                           Gateway

AH    127.0.0.1                             127.0.0.1
AN    128.45.80.0                           128.45.80.240
AN    128.45.100.0                          128.45.80.38
UCX> set route 10.61.1.0/gatew=128.45.80.66/netw
UCX> sh route

                             DYNAMIC database

Type           Destination                           Gateway

AH    127.0.0.1                             127.0.0.1
AN    128.45.80.0                           128.45.80.240
AN    10.61.1.0                             128.45.80.66
AN    128.45.100.0                          128.45.80.38

UCX> set route 10.61.2.0/gatew=128.45.80.66/netw
%UCX-E-ROUTEERROR, Error processing ROUTE request
-UCX-E-DUPRECORD, Duplicate information
-UCX-I-DESTGATE, Destination: 10.61.2.0   , Gateway: 128.45.80.66
-SYSTEM-F-FILALRACC, file already accessed on channel
UCX> set route 10.1.2.0/gatew=128.45.80.66/netw
%UCX-E-ROUTEERROR, Error processing ROUTE request
-UCX-E-DUPRECORD, Duplicate information
-UCX-I-DESTGATE, Destination: 10.1.2.0    , Gateway: 128.45.80.66
-SYSTEM-F-FILALRACC, file already accessed on channel
UCX> set route 11.1.2.0/gatew=128.45.80.66/netw
UCX>
UCX>
UCX> set route 11.1.2.0/gatew=128.45.80.66/netw
%UCX-E-ROUTEERROR, Error processing ROUTE request
-UCX-E-DUPRECORD, Duplicate information
-UCX-I-DESTGATE, Destination: 11.1.2.0    , Gateway: 128.45.80.66
-SYSTEM-F-FILALRACC, file already accessed on channel
UCX>

Same happens w/ a Class B address:

UCX> set route 145.1.2.0/gatew=128.45.80.66/netw
UCX> set route 145.1.1.0/gatew=128.45.80.66/netw
%UCX-E-ROUTEERROR, Error processing ROUTE request
-UCX-E-DUPRECORD, Duplicate information
-UCX-I-DESTGATE, Destination: 145.1.1.0   , Gateway: 128.45.80.66
-SYSTEM-F-FILALRACC, file already accessed on channel

..but
UCX> set route 145.2.1.0/gatew=128.45.80.66/netw
...works!

The reason he wants to do this is that he may want 145.1.2.0 and 145.1.1.0
to go thru one gateway while access to network 145.1.3.0 may be thru another
network. 

I can see that's the way it works but I also understand what the customer
wants to do. What kind of technical reasoning could I give him????


Andy
T.RTitleUserPersonal
Name
DateLines
5528.1UTRTSC::KNOPPERSOswald KnoppersTue May 27 1997 03:3620
>UCX> set route 10.61.2.0/gatew=128.45.80.66/netw
>%UCX-E-ROUTEERROR, Error processing ROUTE request
>-UCX-E-DUPRECORD, Duplicate information
>-UCX-I-DESTGATE, Destination: 10.61.2.0   , Gateway: 128.45.80.66
>-SYSTEM-F-FILALRACC, file already accessed on channel

I dont understand, you are using the same gateway here as for the already
existing route to the other subnet in network 10... If you specify another
gateway you will not get the duprecord error.

On the other hand, because this UCX system doesn't have an interface
defined in network 10 it isn't aware of the subnetting used. So UCX will
not treat these routes as different. What you can do is define a pseudo
interface on this UCX host in a not used subnet of network 10 and specify
the correct mask. That way UCX will start treating these routes as
different routes.

Regards,

Oswald