Only the IP address of the next-hop IPv6 is specified in next-hop static Pv6 route. The exit interface is derived from the next hop. For example, in Figure 1, three next-hop static routes are configured on Router 0.
Before forwarding any packet, the router process must resolve the route to determine the exit interface to use to forward the packet. This is called a router resolvability process.
It will vary depending upon the type of forwarding mechanism being used by the router. CEF (Cisco Express Forwarding) is the default behaviour on most platforms running IOS 12.0 or later.
If CEF is not enabled in the Router1 and packet is destined for the IP address 2001:AD10:110B:0001::/64 network; on Router1 the process should look like:
Router 0 looks for a match in the routing table and finds that it has to forward the packets to the next-hop IPv6 address 2001:AD10:110B:0003::2. Each route that references only a next-hop IPv6 address and does not know an exit interface must resolve using another route in the routing table with an exit interface.
Router 0 must now search for an exit interface to reach 2001:AD10:110B:0003::2; So the router searches a second time looking for a match.
In this case, the IPv6 address matches the route for the directly connected network 2001:AD10:110B:0003::/64; with the exit interface Fast Ethernet 0/0. So, the router lookup Fast Ethernet 0/0 for this network and then forward out the packet to exit interface.
So, the router takes two routing table lookup processes to forward a packet and the router will do routing lookup for each packet any time. When the router has to perform multiple lookups in the routing table before forwarding a packet; it is performing a process known as a recursive lookup.
A recursive static IPv6 route is valid only when the particular next hop resolves; either directly or indirectly, to a valid exit interface. We can verify the ipv6 static route by using the command syntax in the figure.