[FADCA] DNIC setup

[Chuck Hast]

On Fri, 19 Nov 2004 18:06:18 -0500, bud thompson <budt at cfl.rr.com> wrote:
> ----- Original Message -----
> 
> 
> From: "Chuck Hast" <wchast at gmail.com>
> To: "FADCA" <fadca at mailman.qth.net>; <fpac at f6fbb.org>
> Sent: Friday, November 19, 2004 17:40
> Subject: [FADCA] DNIC setup
> 
> > Do any of you remember how to add another DNIC to the routing tables in
> > DOS FPAC (it is the same as ROSE and i did it years ago when we did the
> > network in Costa Rica ) I was trying to set up the routing tables in the
> > switch
> > down town so connections to DNIC 2080 would be routed to my switch
> > and from there of course on over the France (DNIC 2080). I now have the
> > axip link to Paris up and running with the help of Lucien and Bernard,
> > I am linked presently to Bernard's switch. I am working on getting to
> > Lucien's switch.
> > Once I can get the DNIC routing remembered (Russ, do you have old
> > routing files for when we had the 10m link between CR and US?)
> > I will get the switch down town set up, then of course each switch along
> > the route will have to aim the 2080 DNIC at Tamp. I was at the switch
> > site trying to remember how to set it up but kept on fubar'ing it. It has
> > been WAY too long since I did the DNIC piece.
> >
> > It is a shame because we should be using the DNIC to route certain
> > specialty traffic.  More on that in another e-mail. I just need to
> > remember
> > how to route the DNIC's in ROSE/FPAC DOS...
> >
> > --
> > Chuck Hast
> 
> * * *
> Chuck:  I manage two FPAC and one ROSE switch here and am the main
> consultant on two other FPACs.
> 
> I don't even know what DINC means! Har.
> 
> But my switches work...
> 
> I've cc: Paul Miller N4WKQ who is my ROSE guru - maybe he can help.
> 
> Keep up the good work. and let us know the answer when you find it.
> 

Bud,
the X.121 address consist of 2, 3 or 4 parts, depending on how you look at it
they are as follows:

1. DCC            
2. Network ID  
3. NNX
4. CO code

The last two maybe looked on as a single piece therefore 3 parts. Most people do
not realize the first part of the address which you do not see much
of, actually ID's
the country that the network resides in. In the US we have 310 to 316
identified,
but I believe that the assignment actually goes to 319.

Here is a ITU document that shows the assignments:
http://www.itu.int/ITU-T/inr/forms/dnic.html

The DCC plus the Network ID make up the DNIC. Our switches all are ID'd as
DNIC 3100, and you have probably seen it in the config files and also when the
connection is established. As I pointed out the DNIC is actually two parts, we
could easily have parallele networks by assigning certain parts of the network
to a DNIC of 3101, 3102, 3103, etc. Or it could be 3110, 3111, anything within
the US DCC assignment. 

You are familiar with the rest of the addressing the NNX code (area code) and
the CO assignments.

As of this morning we got our axip link to france up and running so from my
switch here in tampa you can make a connection using following format
c call v 2080,nnxccc
You normally make a call using the following format
c call v nnxccc
But we now add the DNIC to the mix in order to tell the switches where to direct
the call in this case to the link that connects our network to France. Years ago
Russ and i had a link between here and Costa Rica, on 10M when the path was
open it was neat to set somewhere on the network and make a connect to someone
on the far end of that link. During the time we had the link running
when the path
was there we did a lot of linkage. Indeed that is how I got the ROSE
binary files
to update the switches. Tom Moulton would e-mail them to me over the packet
network as multiple files, we had a program that would collect them and rebuild
the original bin file. We had a lot of fun back in those days, and
doing the LINUX
stuff is sort of bringing it back. 

Anyhow. I am hoping someone still has old ROSE config files that had the added
DNIC in them to route calls across the network to JAX and from there
to Costa Rica,
a quick look at that would tell me how to set up the FPAC DOS machines. I know
how to do it under FPAC Linux, but it has been too many moons ago for ROSE/FPAC
dos.

Back on the DNIC usage. We could use a additional DNIC overlay to route 
disaster communications from EOC to EOC and to special ports which could
be rapidly turned on or off based on emergency needs, of course this ability
to manipulate the ports is with the Linux version, DOS is not that flexible and 
the changes would be possible but might demand a visit to the switch site.

DOS FPAC of course will allow for the additional overlay, it would just be more
dificult to turn the ports on and off. 





-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."