Configure Static Routing

Information for Static Routing:

Routers forwards packets applying both route data via route table entries which you hand configure or perhaps the route data that is certainly determined applying dynamic course-plotting algorithms.

Static tracks, which determine very revealing pathways between a couple routers, are not routinely up to date; you should hand reconfigure static tracks whenever system changes come about. Static tracks use less bandwidth compared to dynamic tracks. Absolutely no CPU rounds are utilized to be able to calculate and also analyze course-plotting revisions.

It is possible to health supplement dynamic tracks with static tracks exactly where proper. It is possible to redistribute static tracks straight into dynamic course-plotting algorithms and you are not able to redistribute course-plotting data determined by means of dynamic course-plotting algorithms into the static course-plotting table.

You should utilize static tracks within circumstances exactly where system targeted traffic is actually foreseeable and also the spot that the system design is simple. You can't use static tracks within big, continually transforming communities because static tracks are not able to react to system changes. Most communities use dynamic tracks to be able to talk between routers nevertheless might have a couple static tracks set up pertaining to particular situations. Static tracks may also be great for specifying the entrance of past resort (a default router to be able to which most unroutable packets tend to be sent).

Directly Connected Static Routes:

You need to stipulate only this result interface (the interface on what most packets usually are deliver to this getaway network) in a very right related static route. Your router presumes this getaway will be right that come with this result interface and also the supply getaway is needed since the next-hop handle. Your next jump almost always is an interface, only for point-to-point interfaces. Intended for transmitted interfaces, the next jump need to be a IPv4/IPv6 handle.

Floating Static Routes:

Any sailing static path can be a static path which the router employs to be able to support some sort of dynamic path. You must configure some sort of sailing static path using a increased administrative range than the dynamic path who's backs way up. However, your router wants some sort of dynamic route to some sort of sailing static path. You should use some sort of sailing static path as an alternative when the dynamic path will be missing.

Configering a Static Routes:

Ensure that you are in the correct VDC (or use the switch vdc command)

Summery Types:

1.configure terminal

2.ip route {ip-prefix | ip-addr/ip-mask} {[next-hop | nh-prefix] | [interface next-hop | nh-prefix]} [name nexthop-name] [tag tag-value] [pref]

or

ipv6 route ip6-prefix {nh-prefix | link-local-nh-prefix} | {nh-prefix [interface] | link-local-nh-prefix [interface]} [name nexthop-name] [tag tag-value] [pref]

3.(Optional) show {ip | ipv6} static-route

4.(Optional) copy running-config startup-config

This example shows how to configure a static route for a null interface:

switch# configure terminal

switch(config)# ip route 1.1.1.1/32 null 0

switch(config)# copy running-config startup-config

Use the no {ip | ipv6} static-route command to remove the static route.