Step 1 |
enable
|
Enables privileged EXEC mode.
|
Step 2 |
configure
terminal
Device# configure terminal
|
Enters global configuration mode.
|
Step 3 |
ip access-list { standard | extended} [ access-list-name | access-list-number]
Device# ipv6 access-list acl_vrf1
|
Specifies the IP access list type and enters the corresponding access list configuration mode. You can specify a standard,
extended, or named access list.
|
Step 4 |
[ sequence-number] { permit| deny}protocol source source-wildcard destination destination-wildcard
Device(config-ipv6-acl)# 10 permit ipv6 1333::/64 2000::/64
|
Defines the criteria for which the access list will permit or deny packets. Match criteria can be defined based on IPv6 addresses,
IPv6 address ranges, and other IPv6 packet access list filtering options. Named, numbered, standard, and extended access lists
are supported. You can use all IPv6 access list configuration options in Cisco IOS software to define match criteria.
|
Step 5 |
route-map map-tag [ permit | deny] [ sequence-number]
Device(config-route-map)# route-map vrf1_vrf2_v6 permit 10
|
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing. Enters
route-map configuration mode.
|
Step 6 |
match ip-address { acl-number [ acl-number | acl-name ] | acl-name [ acl-name | acl-number ] }
Device(config-route-map)# match ipv6 address acl_vrf1
|
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list,
and performs policy routing on matched packets.
|
Step 7 |
set ip vrf vrf-name next-hop { ip-address [ ip-address] | }
- set ip default vrfvrf-name next-hop{ ip-address [ ip-address] | }
- set vrfvrf-name
Device(config-route-map)# set ipv6 vrf vrf2 next-hop 1335::1
or
Device(config-route-map)# set ipv6 default vrf vrf2 next-hop 1335::1
or
Device(config-route-map)# set vrf vrf2
|
The set ipv6 vrf vrf-namenext-hopip-address[ip-address] command indicates where to route IPv4 packets that pass a match criteria of a route map using the next-hop specified for
the VRF.
The default keyword verifies the presence of the IP address in the routing table of the VRF. If the IP address is present the packet
is not policy routed but forwarded based on the routing table. If the IP address is absent in the routing table, the packet
is policy routed and sent to the specified next hop.
|
Step 8 |
interface HundredGigE rack/slot/module/port
Device(config-if)# interface HundredGigE1/0/11
|
Configures a Hundred Gigabit Ethernet interface and enters interface configuration mode.
|
Step 9 |
no switchport
Device(config-if)# no switchport
|
Configures the interface as a Layer 3 Ethernet interface.
|
Step 10 |
vrf forwarding vrf-name
Device(config-if)# vrf forwarding vrf1
|
Associates the VRF with the Layer 3 interface.
|
Step 11 |
ip address ip-address subnet-mask
Device(config-if-vrf)# ipv6 address 1000::1/64
|
Enters the IP address for the interface.
|
Step 12 |
ip policy route-map map-tag
Device(config-if)# ipv6 policy route-map vrf1_vrf2_v6
|
Identifies the route map to use for PBR.
|
Step 13 |
end
|
Exits interface configuration mode and returns to privileged EXEC mode.
|
Step 14 |
interface HundredGigE rack/slot/module/port
Device(config)# interface HundredGigE1/0/25
|
Configures a Hundred Gigabit Ethernet interface and enters interface configuration mode.
|
Step 15 |
no switchport
Device(config-if)# no switchport
|
Configures the interface as a Layer 3 Ethernet interface.
|
Step 16 |
vrf forwarding vrf-name
Device(config-if)vrf forwarding vrf2
|
Associates the VRF with the Layer 3 interface.
|
Step 17 |
ip address ip-address subnet-mask
Device(config-if-vrf) ipv6 address 1335::2/64
|
Enters the IP address for the interface.
|
Step 18 |
ipv6 enable
Device(cofig-if) ipv6 enable
|
Enables IPv6 processing on an interface that has not been configured with an explicit IPv6 address.
|