Understanding
29
Internetwork Packet Exchange
103-000176-001
August 29, 2001
Novell Confidential
Manual
99a
38
July 17, 2001
necessary, connections to the main office need only be low-speed, dial-up
lines. For this reason, the first several minutes of the call should not be taken
up by a flood of routing and service information into a branch office. Nor
should there be a relatively smaller flood of (mostly irrelevant) routing and
service information from a branch office into the main office.
shows a typical configuration for static routes and services over an
on-demand call.
Figure 3
On-Demand Call Between a Branch Office and the Main Office
In this configuration, the branch office router, BRANCH_01_RTR, must
know only the addresses and names of a few servers and services. This small
number of extra routes and services is of minimal burden to the branch office
network. The main office router, MAIN_OFFICE_RTR, must keep track of
only a few networks and services from each branch office. This is significantly
better than being flooded with potentially thousands of extra routes and
services that are of no use to the main office network.
BRANCH_01_RTR
10000000:000000000001:0451
File Service (SAP Service Type 4)
NetWare Workstation
Network = 10000001
Main Office Accounting Server
Name = ACCOUNTS
Internal Network = AA012123
On-Demand Call
Network:
10000001
Configured Static Routes:
10000001 (Workstation Network)
10000000 (Branch Office Router Internal Network)
Configured Static Services:
Configured Static Routes:
AA012123 (Server Internal Network)
AA000000 (Main Office Router Internal Network)
Configured Static Services:
ACCOUNTS
AA012123:000000000001:0451
File Service (SAP Service Type 4)
MAIN_OFFICE_RTR
AA000000:000000000001:0451
File Service (SAP Service Type 4)
Main Office:
1000 Networks,
plus Services
Branch Office:
20 Networks,
plus Services
Branch Office Router
Name = BRANCH_01_RTR
Internal Network = 10000000
Main Office Router
Name = MAIN_OFFICE_RTR
Internal Network = AA000000
