Ip nat inside source route-map T1-ISP interface GigabitEthernet0/1 overload Ip nat inside source route-map OPTIMUM-ISP interface GigabitEthernet0/0 overload Ip http timeout-policy idle 60 life 86400 requests 10000 Ip local policy route-map IP-SLA-ROUTE-POLICY Tunnel protection ipsec profile EASY_VPN_IPSec_PROFILE1 Username admin privilege 15 password 7 141F13050806sdfds25242FĬrypto isakmp key # address 173.161.255.241 255.255.255.240Ĭrypto isakmp client configuration group EASY_VPNĬrypto isakmp profile EASY_VPN_IKE_PROFILE1Ĭrypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmacĬrypto ipsec profile EASY_VPN_IPSec_PROFILE1 ! NVRAM config last updated at 20:54:18 UTC Sun by adminĬrypto pki token default removal timeout 0Ĭrypto pki trustpoint TP-self-signed-2562258950 ! Last configuration change at 20:54:18 UTC Sun by admin Someone please review my attached config and advise what is wrong with my config. In my current config, I have added an "P local Policy Route-MAP" and I also changed the IP being tracked to my ISP's DNS address. I have made some modification to my config to see if I can fix this, but it looks like unless I specify a static default route with no tracking option to my ISP A, the traffic keep going through T1. Maybe because the tracking was done on ISP A gateway and that IP was reachable even though the ISP A was down. Yesterday ISP A went down partially and the failover to T1 didin't happened. I have tested the failover in the past by disabling the primary interface and it worked. I have a problem with my IP sla on a router with two ISPs (ISP A and ISP B).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |