Managing The Routing Table; Troubleshooting Routing Policy - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - IP SERVICES CONFIGURATION GUIDE 2010-10-01 Configuration Manual

Managing the Routing Table

clear ip routes
ip refresh-route

Troubleshooting Routing Policy

Copyright © 2010, Juniper Networks, Inc.
Table 6: Sample Regular Expressions (continued)
Regular Matched AS-Path or Community
Expression Attribute
_200_ Includes the number 200 (as opposed
to the pattern consisting of numeral 2,
numeral 0, numeral 0)
Our implementation of regular
expressions is not literal. Substring
matching is enabled by default.
Specifying 200 (no underscores) results
in a match on 200 and on 2005. The
underscore metacharacter disables
substring matching.
For information about using AS-path access lists, see "Access Lists" on page 20. For
information about using community lists, see "Community Lists" on page 37.
You can clear all routes from the IP routing table, and then enable the owning
protocols—BGP, OSPF, RIP—to reinstall the routes.
Use to clear all routing entries or a specified entry from the IP routing table.
Example
host1#clear ip routes
There is no no version.
See clear ip routes.
Use to reinstall routes removed from the IP routing table by the clear ip route command.
Example
host1#ip refresh-route
There is no no version.
See ip refresh-route.
You can turn on debugging for routing policy by issuing the log severity debug
ipRoutePolicy command from Global Configuration mode. You can specify different
levels of severity for ipRoutePolicy. For more information about using log commands for
troubleshooting, see Managing the System in JunosE System Basics Configuration Guide.
Chapter 1: Configuring Routing Policy
Example
33 200 422 48^200$
^200 500$
but not
33 20 422 48 51 2005
47