User Guide for CISCO models including: Nexus 9000 Series Configuring Static Routing, Nexus 9000 Series, Configuring Static Routing, Static Routing, Routing
Add static route cisco packet tracer
File Info : application/pdf, 8 Pages, 238.38KB
DocumentDocument12
CHAPTER
Configuring Static Routing
This chapter describes how to configure static routing on the Cisco NX-OS device. This chapter includes the following sections: · About Static Routing, page 12-1 · Licensing Requirements for Static Routing, page 12-3 · Prerequisites for Static Routing, page 12-3 · Default Settings, page 12-4 · Configuring Static Routing, page 12-4 · Verifying the Static Routing Configuration, page 12-8 · Configuration Example for Static Routing, page 12-8
About Static Routing
Routers forward packets using either route information from route table entries that you manually configure or the route information that is calculated using dynamic routing algorithms. Static routes, which define explicit paths between two routers, cannot be automatically updated; you must manually reconfigure static routes when network changes occur. Static routes use less bandwidth than dynamic routes. No CPU cycles are used to calculate and analyze routing updates. You can supplement dynamic routes with static routes where appropriate. You can redistribute static routes into dynamic routing algorithms, but you cannot redistribute routing information calculated by dynamic routing algorithms into the static routing table. You should use static routes in environments where network traffic is predictable and where the network design is simple. You should not use static routes in large, constantly changing networks because static routes cannot react to network changes. Most networks use dynamic routes to communicate between routers but might have one or two static routes configured for special cases. Static routes are also useful for specifying a gateway of last resort (a default router to which all unroutable packets are sent).
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
12-1
About Static Routing
Chapter 12 Configuring Static Routing
This section includes the following topics: · Administrative Distance, page 12-2 · Directly Connected Static Routes, page 12-2 · Fully Specified Static Routes, page 12-2 · Floating Static Routes, page 12-2 · Remote Next Hops for Static Routes, page 12-3 · BFD, page 12-3 · Virtualization Support, page 12-3
Administrative Distance
An administrative distance is the metric used by routers to choose the best path when there are two or more routes to the same destination from two different routing protocols. An administrative distance guides the selection of one routing protocol (or static route) over another, when more than one protocol adds the same route to the unicast routing table. Each routing protocol is prioritized in order of most to least reliable using an administrative distance value. Static routes have a default administrative distance of 1. A router prefers a static route to a dynamic route because the router considers a route with a low number to be the shortest. If you want a dynamic route to override a static route, you can specify an administrative distance for the static route. For example, if you have two dynamic routes with an administrative distance of 120, you would specify an administrative distance that is greater than 120 for the static route if you want the dynamic route to override the static route.
Directly Connected Static Routes
You must specify only the output interface (the interface on which all packets are sent to the destination network) in a directly connected static route. The router assumes the destination is directly attached to the output interface and the packet destination is used as the next-hop address. The next hop can be an interface, only for point-to-point interfaces. For broadcast interfaces, the next hop must be an IPv4/IPv6 address.
Fully Specified Static Routes
You must specify either the output interface (the interface on which all packets are sent to the destination network) or the next-hop address in a fully specified static route. 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. The next-hop address must be directly attached to the specified output interface.
Floating Static Routes
A floating static route is a static route that the router uses to back up a dynamic route. You must configure a floating static route with a higher administrative distance than the dynamic route that it backs up. In this instance, the router prefers a dynamic route to a floating static route. You can use a floating static route as a replacement if the dynamic route is lost.
12-2
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
Chapter 12 Configuring Static Routing
Licensing Requirements for Static Routing
Note By default, a router prefers a static route to a dynamic route because a static route has a smaller administrative distance than a dynamic route.
Remote Next Hops for Static Routes
You can specify the next-hop address of a neighboring router that is not directly connected to the router for static routes with remote (nondirectly attached) next-hops. If a static route has remote next hops during data forwarding, the next hops are recursively used in the unicast routing table to identify the corresponding directly attached next hops that have reachability to the remote next hops.
BFD
This feature supports bidirectional forwarding detection (BFD). BFD is a detection protocol designed to provide fast forwarding-path failure detection times. BFD provides subsecond failure detection between two adjacent devices and can be less CPU-intensive than protocol hello messages because some of the BFD load can be distributed onto the data plane on supported modules. See the Cisco Nexus 9000 Series NX-OS Interfaces Configuration Guide for more information.
Virtualization Support
Static routes support virtual routing and forwarding (VRF) instances.
Licensing Requirements for Static Routing
The following table shows the licensing requirements for this feature:
Product Cisco NX-OS
License Requirement
Static routing requires no license. Any feature not included in a license package is bundled with the nx-os image and is provided at no extra charge to you. For a complete explanation of the Cisco NX-OS licensing scheme, see the Cisco NX-OS Licensing Guide.
Prerequisites for Static Routing
Static routing has the following prerequisites: · If the next-hop address for a static route is unreachable, the static route is not added to the unicast
routing table..
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
12-3
Default Settings
Chapter 12 Configuring Static Routing
Default Settings
Table 12-1 lists the default settings for static routing parameters.
Table 12-1
Default Static Routing Parameters
Parameters Administrative distance RIP feature
Default 1 Disabled
Configuring Static Routing
This section includes the following topics: · Configuring a Static Route, page 12-4 · Configuring a Static Route over a VLAN, page 12-5 · Configuring Virtualization, page 12-7 · Verifying the Static Routing Configuration, page 12-8
Note If you are familiar with the Cisco IOS CLI, be aware that the Cisco NX-OS commands for this feature might differ from the Cisco IOS commands that you would use.
Configuring a Static Route
You can configure a static route on the router.
SUMMARY STEPS
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
12-4
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
Chapter 12 Configuring Static Routing
Configuring Static Routing
DETAILED STEPS
Step 1
Command
configure terminal
Step 2
Example: switch# configure terminal switch(config)#
ip route {ip-prefix | ip-addr/ip-mask} {[next-hop | nh-prefix] | [interface next-hop | nh-prefix]} [name nexthop-name] [tag tag-value] [pref]
Example: switch(config)# ip route 192.0.2.0/8 ethernet 1/2 192.0.2.4
ipv6 route ip6-prefix {nh-prefix | link-local-nh-prefix} | (nexthop [interface] | link-local-nexthop [interface]} [name nexthop-name] [tag tag-value] [pref]
Step 3
Example: switch(config)# ipv6 route 2001:0DB8::/48 6::6 ethernet 2/1
show {ip | ipv6} static-route
Step 4
Example: switch(config)# show ip static-route
copy running-config startup-config
Example: switch(config)# copy running-config startup-config
Purpose Enters global configuration mode.
Configures a static route and the interface for this static route. Use ? to display a list of supported interfaces. You can specify a null interface by using null 0. The preference value sets the administrative distance. The range is from 1 to 255. The default is 1. Configures a static route and the interface for this static route. Use ? to display a list of supported interfaces. You can specify a null interface by using null 0. The preference value sets the administrative distance. The range is from 1 to 255. The default is 1.
(Optional) Displays information about static routes.
(Optional) Copies the running configuration to the startup configuration.
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} route command to remove the static route.
Configuring a Static Route over a VLAN
You can configure a static route without next hop support over a VLAN.
BEFORE YOU BEGIN Ensure that the access port is part of the VLAN.
SUMMARY STEPS
1. configure terminal
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
12-5
Configuring Static Routing
Chapter 12 Configuring Static Routing
DETAILED STEPS
2. feature interface-vlan 3. interface vlan vlan-id 4. ip address ip-addr/length 5. ip route ip-addr/length vlan-id 6. (Optional) show ip route 7. (Optional) copy running-config startup-config
Step 1
Command
configure terminal
Step 2
Example: switch# configure terminal switch(config)#
feature interface vlan
Step 3
Example: switch(config)# feature interface-vlan
interface-vlan vlan-id
Example: switch(config)# interface-vlan 10
Step 4 ip address ip-addr/length
Step 5
Example: switch(config)# ip address 192.0.2.1/8
ip route ip-addr/length vlan-id
Step 6
Example: switch(config)# ip route 209.165.200.224/27 vlan 10
show ip route
Step 7
Example: switch(config)# show ip route
copy running-config startup-config
Example: switch(config)# copy running-config startup-config
Purpose Enters global configuration mode.
Enables VLAN interface mode.
Creates an SVI and enters interface configuration mode. The range for the vlan-id argument is from 1 to 4094, except for the VLANs reserved for the internal switch. Configures an IP address for the VLAN.
Adds an interface static route without a next hop on the switch virtual interface (SVI). The IP address is the address that is configured on the interface that is connected to the switch. (Optional) Displays routes from the Unicast Route Information Base (URIB).
(Optional) Copies the running configuration to the startup configuration.
This example shows how to configure a static route without a next hop over an SVI:
switch# configure terminal switch(config)# feature interface-vlan swicth(config)# interface vlan 10 switch(config-if)# ip address 192.0.2.1/8 switch(config-if)# ip route 209.165.200.224/27 vlan 10 <===209,165.200.224 is the IP address of the interface that is configured on the interface that is directly connected to the switch.
12-6
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
Chapter 12 Configuring Static Routing
Configuring Static Routing
switch(config-if)# copy running-config startup-config
Use the no ip route command to remove the static route.
Configuring Virtualization
You can configure a static route in a VRF.
SUMMARY STEPS
1. configure terminal 2. vrf context vrf-name 3. ip route {ip-prefix | ip-addr ip-mask} {next-hop | nh-prefix | interface} [name nexthop-name] [tag
tag-value] [pref] or ipv6 route ip6-prefix {nh-prefix | link-local-nh-prefix} | {next-hop [interface] | link-local-next-hop [interface]} [name nexthop-name] [tag tag-value] [pref] 4. (Optional) show {ip | ipv6} static-route vrf vrf-name 5. (Optional) copy running-config startup-config
DETAILED STEPS
Step 1
Command
configure terminal
Purpose Enters global configuration mode.
Step 2
Example: switch# configure terminal switch(config)#
vrf context vrf-name
Creates a VRF and enters VRF configuration mode.
Step 3
Example: switch(config)# vrf context StaticVrf ip route {ip-prefix | ip-addr ip-mask} {next-hop | nh-prefix | interface} [name nexthop-name] [tag tag-value] [pref]
Example: switch(config-vrf)# ip route 192.0.2.0/8 ethernet 1/2
ipv6 route ip6-prefix {nh-prefix | link-local-nh-prefix} | (nexthop [interface] | link-local-nexthop [interface]} [name nexthop-name] [tag tag-value] [pref]
Example: switch(config)# ipv6 route 2001:0DB8::/48 6::6 ethernet 2/1
Configures a static route and the interface for this static route. Use ? to display a list of supported interfaces. You can specify a null interface by using null 0.
You can optionally configure the next-hop address.
The preference value sets the administrative distance. The range is from 1 to 255. The default is 1.
Configures a static route and the interface for this static route. Use ? to display a list of supported interfaces. You can specify a null interface by using null 0.
You can optionally configure the next-hop address.
The preference value sets the administrative distance. The range is from 1 to 255. The default is 1.
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
12-7
Verifying the Static Routing Configuration
Chapter 12 Configuring Static Routing
Step 4
Command
show {ip | ipv6} static-route vrf vrf-name
Purpose (Optional) Displays information on static routes.
Step 5
Example: switch(config-vrf)# show ip static-route
copy running-config startup-config
Example: switch(config-vrf)# copy running-config startup-config
(Optional) Copies the running configuration to the startup configuration.
This example shows how to configure a static route:
switch# configure terminal switch(config)# vrf context StaticVrf switch(config-vrf)# ip route 192.0.2.0/8 192.0.2.10 switch(config-vrf)# copy running-config startup-config
Verifying the Static Routing Configuration
To display the static routing configuration, perform one of the following tasks:
Command show {ip | ipv6} static-route show ipv6 static-route vrf vrf-name show {ip | ipv6} static-route track-table
Purpose Displays the configured static routes. Displays static route information for each VRF. Displays information about the IPv4 or IPv6 static-route track table.
Configuration Example for Static Routing
This example shows how to configure static routing:
configure terminal ip route 192.0.2.0/8 192.0.2.10 copy running-config startup-config
12-8
Cisco Nexus 9000 Series NX-OS Unicast Routing Configuration Guide, Release 6.x
FrameMaker 2019.0.5 Acrobat Elements 15.0 (Windows); modified using iText 2.1.7 by 1T3XT