Configuring Ipv4 Routing And Addresses - Cisco 7604 Configuration Manual

Configuring IPv4 Routing and Addresses

Command
Step 4
Router(config-subif)# encapsulation dot1q vlan_ID
[native]
Step 5
Router(config-if)# exit
1. type = ethernet, fastethernet, gigabitethernet, tengigabitethernet, or ge-wan
Configuring IPv4 Routing and Addresses
For complete information and procedures, refer to these publications:
•
•
When configuring IPv4 routing and addresses, follow these guidelines and restrictions:
•
•
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
22-4
Cisco IOS IP and IP Routing Configuration Guide, Release 12.2, at this URL:
http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/fipr_c.html
Cisco IOS IP and IP Routing Command Reference, Release 12.2, at these URLs:
http://www.cisco.com/en/US/docs/ios/12_2/ipaddr/command/reference/fipras_r.html
http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/fiprrp_r.html
For information about the maximum paths command, refer to the Cisco IOS Master Command List,
Release 12.2SX publication.
The Policy Feature Card (PFC) and any Distributed Feature Cards (DFCs) provide hardware support
for policy-based routing (PBR) for route-map sequences that use the match ip address, set ip
next-hop, and ip default next-hop PBR keywords.
When configuring PBR, follow these guidelines and restrictions:
– The PFC provides hardware support for PBR configured on a tunnel interface.
– The PFC does not provide hardware support for PBR configured with the set ip next-hop
keywords if the next hop is a tunnel interface.
– If the MSFC address falls within the range of a PBR ACL, traffic addressed to the MSFC is
policy routed in hardware instead of being forwarded to the MSFC. To prevent policy routing
of traffic addressed to the MSFC, configure PBR ACLs to deny traffic addressed to the MSFC.
Any options in Cisco IOS ACLs that provide filtering in a PBR route-map that would cause
–
flows to be sent to the MSFC to be switched in software are ignored. For example, logging is
not supported in ACEs in Cisco IOS ACLs that provide filtering in PBR route-maps.
PBR traffic through switching module ports where PBR is configured is routed in software if
–
the switching module resets. (CSCee92191)
Any permit route-map sequence with no set statement will cause matching traffic to be
–
processed by the MSFC.
– In Cisco IOS Release 12.2(33)SXF16 and later releases, for efficient use of hardware resources,
enter the platform ipv4 pbr optimize tcam command in global configuration mode when
configuring multiple PBR sequences (or a single PBR sequence with multiple ACLs) in which
more than one PBR ACL contains DENY entries. In earlier releases, we recommend avoiding
this type of configuration. (CSCsr45495)
In Cisco IOS Release 12.2(33)SXH4 and later releases, the BOOTP/DHCP traffic will be
–
dropped unless explicitly permitted. In Cisco IOS Release 12.2(18)SXF, BOOTP/DHCP
packets are not subjected to a PBR configured in the ingress interfaces and the BOOTP/DHCP
packets are forwarded to the BOOTP/DHCP server, although they are not explicitly permitted.
Chapter 22
Purpose
Configures 802.1Q encapsulation for the subinterface.
Returns to global configuration mode.
Configuring Layer 3 Interfaces
OL-4266-08