CONFIG CHEAT SHEET... LEARN TO CONFIGURE AND MONITOR YOUR ROUTER IN 20 MINUTES!

(Note: these are commands to be issued using a terminal and console cable, not for QuickConfig or GUI.)

To get a router to work, you need to have devices configured and addressed. To get started on ANYTHING, here's the gist of the router command set-up. Look at the router as a command tree. At the top of the tree is the OPCON*. Here's a diagram:

*T (talk to process) # Ex: '5' is to monitor, see what's happening in real time. T6 is to configure or change. That is, to change either the devices or protocol info and then restart the router to have the changes take effect.

ex.
*t5 (or M for Monitor)
CGW Operator Console
+li i

+
At the + and Config> prompts, you get the status and or the configuration of the router.
From the + prompt, you can:

+?	(shows you all the commands. Some of those are shown below.)
+ li c	(the revision of code. The state of the interfaces [up, down, not installed, testing])
+ li mem	(The amount of memory available, presently working, in the router.)
+ li up	(How long it's been up. Number of restarts/reloads)
+ li util	(What is the utilization on a per network basis?)
+ li i #	(The # is the interface LAN or WAN number. This gives all of the stats for this interface card. If you type just the letter I, you get an overall feel for all the interfaces.)
+ li s #	(Same as I command, but you get statistics [packets in/out], instead.)
+ <control p>	gets you back to the * prompt. You need to get there is you want to go to another T(alk) process.

T(alk) process 6 gives you a Config> prompt.
At the Config> prompt,
Config> list? Shows you what you can list. Anytime you're lost, try a '?'.
Config> li(st) de (vices) shows you what interface cards you have.
Config> del (ete) int(erface) # (This gets rid of that interface # device.)
Ex. *t 6

Gateway user configuration
Config> li de
lfc 0 (Ethernet): CSR 81600, CSR2 800C00, vector 94
lfc 1 (WAN PPP): CSR 81620, CSR2 80D00, vector 93
ldc 2 (PPP Dial Circuit): CSR 0, vector 0
Config>

O.K., now you go one level deeper on the command tree. From either +, or Config>. if you type: 'P ipx' you'll go down to the IPX prompt. To get back to the '+' or 'Config>' prompt, Type: 'ex' and return or enter. Let's use the symbol '>' to stand for <return>. When you go back top the '+' or 'Config>' prompt, you can go back down, this time to a different protocol. You can't be at the IPX> or IPX Config> prompt and type: p ip and go to the IP> or IP Config> prompt. You have to IPX>ex(it) first.

Now, let's take a stab at the Config> side.
Config> p ip
IP Config> (see how that happened?) Here, you can see what's configured, or change what is there. (Remember to 'restart' after you're through configuring to let it take effect.)
IP Config> ad(d) ad(dress) Here, you'll be prompted for which interface, what address, what mask. (note: our interfaces start at zero, not interface 1.)
IP Config> ad(d) ro(ute) to set up static route to some other address, normally not needed.
IP Config> se(t) de(fault) ne(twork) lets you add a place for the router to send stuff if it doesn't recognize the network.address to which you send the data.
IP Config> en(able) rip (enables Routing Interior Protocol. You may be using this to let you router know where every available network is.)

So, now you've added your addresses and enabled RIP. If IP is your only routing protocol, you can type 'ex' at the IP Config> prompt, get to the Config> prompt, type <control P>.
This gets you back up top to the '*' prompt. At the '*' type: r(estart)> Then you'll be asked is you really want to restart the router. Type 'y.' You'll be back at the '*' prompt in a second or twoÑready to route IP.
Just as an aside, here's basically what you need for addressing in I(nternet) P(rotocol).

We'll show a typical set up where your router will route between an ethernet, over a phone line, to another site that has a router serving a token ring:

Notice how, in all cases, the third octet (section) differs from the net to net. Note how the mask stays the same throughout the whole internetwork. Notice how the network itself is numbered. xxx.xxx.xxx.0. The network is described by the last '0'. Every machine on the network has a unique 'host', or 'node' number on that network. So that last section always has to be unique.

If the network is written 122.22.51.0, a STATION ON THAT NETWORK IS 122.22.51.4.

That's really all you need to know about IP addressing.
Note also that the phone line can be a leased line, dedicated line, frame relay, or dial-up link.
O.K., so, type at the IP Config> ex>
Config> p ipx (This example is for code older than version 3)
IPX Config> en ipx> (GLOBALLY ENABLES ipx)
Ipx Config> en(able) in(terface) #> (Do this for all your IPX interfaces)
IPX Config> set net(work) # > (Do this for all your IPX interfaces)

Following the prompts, you'll realize you're specifying an interface number and then will be prompted to configure an IPX network number. You need to make these unique throughout your IPX network. L(ocal) A(rea) N(etwork)s need to take their numbers from the server's IPX network #, not their internal network number. If you DO have a serial link, you want both routers to see the same network # on the serial interface that joins them. Serial lines also require you to:

Say the network you're configuring looks like the diagram above. You'll only need to enable the conversion on ONE router. Remember, too, that Serial Lines can have either TB or SRB behavior. In the box where TB meets SRB, enable SR-TB.)

Now you can restart the box to make the config take effect. To do so: ASTR Config> ex> (or you can skip a step and just <control P>)
Config> <control P>
*res
Are you sure you want to restart the gateway (Y or N)? Y>
*

Well, you've started the router and are ready to route IP, IPX, and to bridge as well. You might want to wait until you've configured any other protocols your network needs to route. That'll work fine, too. But, you're back to having been restarted and here's your prompt:
*t 5>
+c> (This will give you an indication of whether your interfaces are UP and will give you valid information to monitor.)
+p ip>
IP> int (Will shoe the active and properly addressed IP addresses you've assigned to the interfaces. If they're not addressed the way you wan them, then,
IP> <control P>
*t6>
Config> p ip>
IP Config> ch(ange) ad(dress) [old address] [new address] > and follow the prompts and restart.
t 5
+ p ip
IP> du(mp) (Will show what IP addresses the box knows about)
IP> ping 122.22.12.51> (Will send an 'echo request' to that machine and expect an 'echo reply' from it. If the machine is reachable and 'alive' you'll see 64 bytes repeatedly echo on to your console screen.)
IP> coun(ters) (shows you what's been happening on IP)
IP> ex
+ p ipx
IPX> con(figuration) (Shows what the addresses are, etc.)
IPX> slist (shows what services are available and ready to serve to end-stations on the net)
IPX> du (same as in IP)
IPX> ex
+ p asrt
ASRT> li br
ASRT> li po
ASRT> li ? (shows what else you can list)

Now that we've touched on IP, IPX, and bridging, a brief overview of DECnet follows: DECnet is a protocol that addresses in AREAs and NODEs. It determines participation by the STATE of the CIRCUITS. To get to the place in the router which will allow you to configure DECnet, start at the '*'.
*t 6 >
Config> p 4
NCP Config> def(ine) exec(utor) state on> (Note the use of the term, DEFINE. This command will effect a permanent change in the configuration. 'SET' will only temporarily effect a change. After a restart, change will revert to those parameters set using the DEFINE command.

The Command just shown globally enables DECnet.

NCP Config> de(fine) Circuit ETH/0 state on> (This enables the first ethernet to play DECnet. The second ethernet would read: eth/1. The first TKR is tkr/0, the second serial link is sl/1.)

NCP Config> de(fine) exec(utor) address 123> (defines the executor node address to be AREA1.NODE23.

After you define the executor state to be ON, you will be prompted for a lot of stuff. Take all defaults, except maybe for the MAX AREA ADDRESS> The number should be as large as the largest node address. MAX BROADCAST NON-ROUTERS equals the largest number of users in the network.

Look at the choices for TYPE of ROUTER. Rule of thumb is: TYPE AREA means it's a level 2 router and will talk to other areas.

TYPE ROUTING_IV means it wants to only do business in its area.

O.K. So that's all you need to configure DECnet. Now to look at what you've done and how it's doing.

NCP> show exec char> (This shows what's been configured.)
NCP> ex
Config> <control P>
*t5
+p4
NCP> From here, you SHOW active circuits, nodes, areas, and their status.

Some words about Appletalk. Instead of AREAs and NODEs, Appletalk deals with ZONEs and NODEs. Instead of having DESIGNATED ROUTERS, or ROOT BRIDGES, the routers in the Appletalk net who hold the most information are SEEDED routers. UNSEEDED routers will get their information from the SEEDED ones. To make a router into a SEEDED router, you need only assign a NET_RANGE. Let's go through the steps to enable and configure APPLETALK>

*t6

Config> p ap2

AP2 Config> en ap2 (globally enables appletalk II)
AP2 Config> en I(nterface) 0> (enables each interface, in turn. This time, it was the interface 0.)

AP2 Config> s(et) node 0 23 > (sets a node number for interface 0 to be 23. Each interface should have a unique node address. Don't ever use zero for anything.)

AP2 Config> s net((work-range) 0 30-31 (signs a network range to a given interface. Remember , this will allow you to send RIP routing information [rtmp2]. The network need not have all SEEDED routers...It just needs some.)

Optionally: AP2 Config> add zone> (This is analogous to other protocols' AREAs. So, if on your interface 2 you have zone-name 'fritz', your command is:

AP2 Config> add zone 2 fritz> (are allowed to add more than one zone per interface.)

AP2 Config> list (will show you what you've configured.)

AP2 Config> ex>

Config> <control p> *t5

+p ap2
AP2> cou(nters) (Shows what's been happening per interface)
AP2> du(mp) (Shows the routes available through the router)
AP2> int(erface) (Shows the per interface configuration)
AP2>ex >
+ <control P>
*r(estart)
Are you sure you want to restart the gateway (YN) ? Y

Well, there you have it. If you'd like more information, please give me a call.

Thanks,
Bill Holmberg
Proteon Customer Support

Please note: This information has been assembled and formatted by the author and should in no way be construed to have been sanctioned or edited by OpenROUTE or its partners, or affiliates. All command are valid through revision 16.1a software, OpenROUTE 2.1.