Understanding Nexus -- Part 17 -- Static Routing

Static routing is quite simple than Dynamic routing. Static routes define explicit paths between two routers. It cannot be automatically updated; you have to manually reconfigure static routes when network change occurs. Static routes use less no bandwidth unlike the dynamic routes. No CPU cycles are used to calculate and analyze routing updates.

You can use a fully specified static route, when the output interface is a multi-access interface and, you need to identify the next-hop address.

By default, a router prefers a static route because a static route has a smaller administrative distance than a dynamic route.

Static routes support Virtual Routing and Forwarding instances (VRFs).

If the next-hop address for a static route is unreachable, the static route will not be added to the routing table.

Static Route

switch# config t
switch(config)# ip route 192.0.2.0/8 192.0.2.10

OR

switch(config)# ip route 192.0.2.0 255.0.0.0 192.0.2.10

OR

switch(config)# ip route 192.0.2.0/8 ethernet 1/2 192.0.2.4

To Check
 

switch(config)# show ip static-route