Troubleshooting Static Routing; Monitoring The Routing Table - HP ProCurve Secure 7000dl Series Basic Management And Configuration Manual

Secure router procurve 7000dl series

Hide thumbs Also See for ProCurve Secure 7000dl Series:

Table of Contents

For example:

ProCurve(config)# int eth 0/1

ProCurve(config-eth 0/1)# no ip route-cache

Fast caching is forcibly disabled when you use the following processes:

the ProCurve Secure Router OS firewall

any firewall processes, such as ACLs and ACPs

policy based routing (PBR)

If you enable the firewall, the ProCurve Secure Router must use process

switching because firewall features require the router to make more-extensive

computations than simple route determination, including checks for attacks

and packet filtering according to an access policy. Similarly, PBR requires the

router to screen packets to determine whether to route them according to a

route map or according to the routing table.

To optimize packet switching for firewall processes, the ProCurve Secure

Router uses a separate table so that it does not have to check long ACLs

each time it receives a packet. This table speeds up firewall computations.

Troubleshooting Static Routing

When you receive reports that traffic is not reaching its destination, first

attempt to ping the destination from the router to verify that a host or other

network node is not the root of the problem. If the ping confirms that the router

cannot reach the destination, next view the routing table.

The show and debug commands described in the following sections are

enable mode commands. You can also enter the commands from configuration

mode contexts by adding the do option.

To view the routing table, enter this enable mode command:

Syntax: show ip route

IP Routing—Configuring Static Routes

Troubleshooting Static Routing

Table of Contents