Foundry Networks Switch and Router Installation And Configuration Manual page 886

Foundry Switch and Router Installation and Configuration Guide
USING THE WEB MANAGEMENT INTERFACE
To modify the maximum number of RIP or SAP route entries supported on a router:
1. Log on to the device using a valid user name and password for read-write access. The System configuration
panel is displayed.
2. Select the Max-Parameter link to display the Configure System Parameter Maximum Value table. This table
lists the settings and valid ranges for all the configurable table sizes on the device.
3. Click the Modify button next to ipx-rip-entry or ipx-sap-entry.
4. Enter the new value for the table size. The value you enter specifies the maximum number of entries the table
can hold.
5. Click Apply to save the changes to the device's running-config file.
6. Select the Save link at the bottom of the dialog. Select Yes when prompted to save the configuration change
to the startup-config file on the device's flash memory.
7. Click on the plus sign next to Command in the tree view to list the command options.
8. Select the Reload link and select Yes when the Web management interface asks you whether you really want
to reload the software. Changes to table sizes do not take effect until you reload the software.
Modify RIP and SAP Hop Count Increment
You can modify the incremental value (hop) that the router adds to a RIP or SAP record before propagating the
record to the next interface. By default, a value of one is added to a record before it is broadcast to the next
interface.
In a network of parallel routers, the router that receives a RIP or SAP record with the lowest hop count is seen as
the router with the most optimal information and is seen as the primary router. As primary router, it is elected to
forward the packet to the next interface.
You can manage which router is selected as the primary router by a host by modifying the hop count assigned to
an IPX interface. For example, in Figure 23.2, an administrator wants to ensure that all traffic between server1
and server2 is routed through router 1 and that router 1 is seen as the primary router. To ensure that this occurs,
the administrator can assign higher hop counts (for example, 10) to the router interfaces on router 2.
Link
Activity
Console
Power
Router 2(R2)
Figure 23.2 Using higher hop count assignments to bias traffic away from the router
23 - 12
Hop count = 10
Link
Activity
Hop count = 10
Server1
Hop count = 1
Link Link
Activity Activity
Console
Power
Primary
Router 1(R1)
Hop count = 1
Server2
December 2000