Daniel,
I am afraid you are confusing the Policy Based Routing (PBR) with route-map based NAT. Each one of them is different. PBR is a tool that allows you to perform routing decisions based on other criteria than just the destination IP address. Route-map based NAT is an extension to NAT to select appropriate translation rule depending not only on the source address but also depending on the outgoing interface for the traffic. There is a similarity between them but they are in fact independent.
You have said that you want to route the data traffic out Gi0/2 and the voice traffic out Gi0/1. This is an application for the PBR. I will make one assumption here: I will consider the entire address space 10.0.0.0/8 to be used internally in your network, and packets both sourced and destined in this address space will not be subject to PBR. However, packets from this address space going to destinations outside 10.0.0.0/8 will be subject to PBR.
ip access-list extended NotLocal
deny ip 10.0.0.0 0.255.255.255 10.0.0.0 0.255.255.255
permit ip 10.0.0.0 0.255.255.255 any
!
route-map PBR-Data permit 10
match ip address NotLocal
set ip next-hop 192.168.63.1
!
route-map PBR-Voice permit 10
match ip address NotLocal
set ip next-hop 172.20.62.1
!
interface GigabitEthernet0/0.20
ip policy route-map PBR-Voice
!
interface GigabitEthernet0/0.30
ip policy route-map PBR-Data
This alone will make sure that if data traffic enters Gi0/0.30 and is destined somewhere out the 10.0.0.0/8 range, it will be routed through the next hop 192.168.63.1. Similarly, if the voice traffic enters Gi0/0.20 and goes to targets outside the 10.0.0.0/8 network, it will be forwarded via 172.20.62.1.
While I am not entirely certain why you want to do it this way, that would be the configuration to accomplish that.
Now, obviously, doing NAT on top of this PBR-ed traffic is another task you need to accomplish. What you need to do is to make sure that the voice traffic is NATted behind the range from the pool-20 while the data traffic is NATted behind the range from the pool-30. However, because the PBR is set up so that data traffic will always go out Gi0/2 and voice traffic will always go out Gi0/1, there is no further need to use route-maps in the NAT to verify the outgoing interface. The only thing is to simply write the NAT rules as usual:
ip access-list standard Voice
permit 10.20.0.0 0.0.0.255
!
ip access-list standard Data
permit 10.20.10.0 0.0.0.255
!
ip nat inside source list Voice pool pool-20
ip nat inside source list Data pool pool-30
Remove the existing ip nat inside source commands from your config, please, and you can also remove the ACLs 120, 130, and route-maps MAP-20 and MAP-30.
Feel welcome to ask further!
Best regards,
Peter
