8-47
Configuring Demand Routing for Primary ISDN Modules
Using Demand Routing for ISDN Connections
Note ProCurve Networking recommends that you use static routes for ISDN con-
nections, rather than a dynamic routing protocol. Because routing protocols
regularly exchange updates, these updates frequently initiate the ISDN con-
nection, resulting in higher cost for your company’s ISDN line. (If you want to
send routing updates over the ISDN link, you can configure the ACL that
defines interesting traffic so that it does not include routing updates. You can
then apply an ACL or ACP to the demand interface to allow the routing updates
if the ISDN connection is already established. For more information, see
“Applying an ACP or Another ACL to the Demand Interface” on page 8-27.)
You can view the type of information the ProCurve Secure Router stores in its
routing table by entering the following command from the enable mode
context:
ProCurve# show ip route
Figure 8-12 shows the type of information that is displayed.
Figure 8-12. Routing Table with Static Routes
To configure a static route, enter the following command from the global
configuration mode context:
Syntax: ip route <destination A.B.C.D> <subnet mask | /prefix length> <next hop
A.B.C.D | forwarding interface ID>
Replace <destination A.B.C.D> with the IP address for the far-end network.
For example, the far-end network might be network 192.168.7.0. Next, either
specify the complete subnet mask (such as 255.255.255.0) or enter the prefix
length (such as /24). Then, specify the forwarding interface as demand
<number>. To configure a route to network 192.168.7.0 /24 through demand
interface 1, enter:
ProCurve(config)# ip route 192.168.7.0 /24 demand 1
ProCurve# show ip route
C 10.2.2.0/30 is directly connected, ppp 1
C 10.3.3.0/30 is directly connected, demand 1
C 192.168.20.0/24 is directly connected, eth 0/1
S 192.168.30.0/24 [1/0] via 10.2.2.2, ppp 1
S 192.168.7.0/24 [1/0] via 0.0.0.0, demand 1
To Next Page
Loading...
Need help?
General
