Primary And Secondary Routes; Static Routes; Dynamic Routes Using Rip - 3Com corebuilder 3500 Implementation Manual

Primary and
Secondary Routes

Static Routes

Dynamic Routes
Using RIP
If an interface goes down, routes are temporarily removed from the
routing table until the interface comes back up.
Static routes take precedence over dynamically learned routes to the
same destination. You can have a maximum of 32 static routes.
When you use the IPX route remove option to remove a route, that
route is immediately removed. All servers that depend on the removed
route are also removed from the Server Information Table, including all
static servers.
When you use the IPX route flush option to remove dynamically
learned routes from the IPX routing table, all dynamically learned
routes are immediately removed. All dynamic servers that depend on
these routes are also removed from the Server Information Table.
You can set up both Primary and Secondary routes in the routing table.
To set up routes in the routing table, see the IPX chapter in the Command
Reference Guide.
You manually configure a static route. Static routes are useful in
environments in which no routing protocol is used or when you want to
override a routing protocol's generated route.
Static routes do not change until you change them, and they do not time
out. Because static routes do not change in response to network
topology changes, manually configure only a small number of reasonably
stable routes.
A router uses RIP to exchange its routing table with other routers at
regular intervals. This automatic method of learning routes helps you
keep up with a changing network environment and allows you to
reconfigure routes quickly and reliably. Interior Gateway Protocols (IGPs),
which operate within intranetworks, provide this automated learning.
The system uses RIP (one of the most widely used IGPs) to dynamically
build routing tables.
IPX Routes 431