CCIE Pursuit Blog

May 14, 2009

Named Static Routes

Filed under: Cisco,Cisco Certification,IOS — cciepursuit @ 10:29 am
Tags: , , , ,

This might be old news to many of you, but I found out the other day that you can name static routes:

Rack1R1(config)#ip route name ?
WORD  Name of the next hop

Rack1R1(config)#ip route name PR0N_SERVER

This comes in very handy when troubleshooting – especially if your network documentation is crap.  Have you ever traced a path only to find that one(or more) of the hops are static routes…but you have no idea WHY there was a static route configured nor WHERE it’s pointing to?  With named static routes the engineer can at least leave a clue for future troubleshooters:

Rack1R1(config)#do sh run | i ip route
ip route name DEFAULT_ROUTE_SUCKERS!!!
ip route name PR0N_SERVER

Unfortunately, the name does not appear in the routing table:

Rack1R1(config)#do sh ip route static is subnetted, 1 subnets
S [1/0] via
S* [1/0] via

Rack1R1(config)#do sh ip route
Routing entry for
Known via “static”, distance 1, metric 0
Routing Descriptor Blocks:
Route metric is 0, traffic share count is 1

You will need to find the route in the running configuration in order to see the name:

Rack1R1#sh run | i
ip route name PR0N_SERVER


1 Comment »

  1. I want that for static NAT entries!

    Comment by TabTwo — May 16, 2009 @ 7:31 am | Reply

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Blog at

%d bloggers like this: