Lucent Technologies PortMaster - Manual (Page 66)

Setting Static Routes
3-28 PortMaster Configuration Guide
Note – Static routes use the netmask table entries that are in effect when the routes are
added. If the netmask table is changed, the static route must be deleted from the route
table and added again.
Example of Applying Static Netmasks
Note – Lucent recommends that you use OSPF in this circumstance instead of static
routes.
This static netmask example assumes the following:
• You have anywhere between 8 and 250 PortMaster routers.
• You assign all the user addresses from the dynamic address assignment pools on the
PortMaster routers.
• You are using 27-bit subnets of these three class C networks 192.168.207.0,
192.168.208.0, and 192.168.209.0.
• You are using the 192.168.206.0 network for your Ethernet.
• All PortMaster routers involved are running ComOS 3.1.2 or later.
• You do not use proxy ARP. Instead, you use your 192.168.206.0 network for the
Ethernet, and divide your other networks up among the PortMaster routers.
• Each network provides 30 addresses for the assigned pool of each PortMaster.
To create the subnets defined in this example, enter the following commands on all the
PortMaster routers:
Command> set Ether0 address 192.168.206.X (for some value of X)
Command> set gateway 192.168.206.Y (where Y points at your gateway)
Command> add netmask 192.168.207.0 255.255.255.224
Command> add netmask 192.168.207.0 255.255.255.224
Command> add netmask 192.168.207.0 255.255.255.224
Command> set Ether0 rip on
Command> save all
The netmask table collapses routes on the boundaries specified. As a result, if one
PortMaster has an assigned pool starting at 192.168.207.33, it broadcasts a host route to
192.168.207.32 instead of broadcasting a route to the 192.168.207.0 network. The other
PortMaster routers consult their own netmask tables and convert that route back into a
subnet route to 192.168.207.33 through 192.168.207.32.
✍