Configuration Guide for A7000 dl T1 and E1 WAN Interfaces 2005-12

Configuring Routing Information (Static Routes) Understanding SROS Queuing Methods

22 5991-3823

Now, create the access policy to allow the traffic between the LANs and to NAT traffic bound for the

public Internet.

ProCurve(config)#ip policy-class INTERLANwNAT

ProCurve(config-policy-class)#allow list INTERLAN

ProCurve(config-policy-class)#nat source list INTERNET interface ppp 1 overload

ProCurve(config-policy-class)#exit

ProCurve(config)#

Apply the ACPs to the interface(s) to complete the configuration. For our example, the

INTERLANwNAT ACP should be applied to fr 1.16 (PVC to the branch office) and eth 0/1 (local

network connection).

The following command listing applies the ACP to the fr 1.16 and eth 0/1 interfaces:

ProCurve>enable

ProCurve#config terminal

ProCurve(config)#interface fr 1.16

ProCurve(config-fr 1.16)#access-policy INTERLANwNAT

ProCurve(config-fr 1.16)#exit

ProCurve(config)#interface eth 0/1

ProCurve(config-eth 0/1)#access-policy INTERLANwNAT

ProCurve(config-eth 0/1)#exit

ProCurve(config)#

Configuring Routing Information (Static Routes)

SROS products support various routing protocols including static routes, RIP, OSPF, and BGP.

RIP, OPSF, and BGP are all routing protocols which allow routers to share the information contained in

their route tables with other routers in the network. These routing protocols are generally used on networks

that frequently change or contain a large number of nodes. For small applications, manually adding static

routes to the router’s route table is the easiest method of configuration.

Manually adding static routes to the route table requires two steps:

1. Determine the routes needed (destination address and subnet mask as well as the next-hop address or

forwarding interface). Be sure to plan the default route.

2. Use the ip route command to add the route to the route table.

The following lists the complete syntax for the ip route command:

ip route <ip address> <subnet mask> <interface or ip address> <administrative distance>

Specifies the network address (in dotted decimal notation) to add to the route table.

Specifies the subnet mask (in dotted decimal notation) associated with the listed network IP address.

Specifies the gateway peer IP address (in dotted decimal notation) or a configured interface in the unit.

Specifies an administrative distance associated with this router (1 to 255). The administrative distance

provides a way for a router to determine the best route when multiple routes to the same destination exist.

The smaller the administrative distance, the more reliable the route.