спасибо за конфиг,
я переделал его под свои нужды. Задача такая:
необходимо 1 маршрут проходить через 1 провайдер а все другие маршруты (дефолт) через 2 провайдер. Ну естессно когда есть связь, если пропадает хоть на одном то идет переключение на другой провайдер.
Однако трак не поднимается и дает таймаут. Переключение между 1 и 2 траком работает без проблем а вот 3 и 4 ый отвечающие за дефолт маршруты не пашут.usm#sh track
Track 1
Response Time Reporter 1 reachability
Reachability is Down
1 change, last change 02:29:09
Latest operation return code: Timeout
Tracked by:
STATIC-IP-ROUTING 0
Track 2
Response Time Reporter 2 reachability
Reachability is Up
10 changes, last change 00:05:58
Latest operation return code: OK
Latest RTT (millisecs) 45
Tracked by:
STATIC-IP-ROUTING 0
Track 3
Response Time Reporter 3 reachability
Reachability is Down
2 changes, last change 00:15:43
Latest operation return code: Timeout
Tracked by:
STATIC-IP-ROUTING 0
Track 4
Response Time Reporter 4 reachability
Reachability is Down
2 changes, last change 00:15:44
Latest operation return code: Timeout
Tracked by:
STATIC-IP-ROUTING 0
вот конфиг:
track 1 rtr 1 reachability
track 2 rtr 2 reachability
track 3 rtr 3 reachability
track 4 rtr 4 reachability
ip sla 1
icmp-jitter ZZ.ZZ.ZZ.39 source-ip YY.YY.YY.26 num-packets 5
timeout 500
frequency 5
ip sla schedule 1 life forever start-time now
ip sla 2
icmp-jitter ZZ.ZZ.ZZ.39 source-ip XX.XX.XX.227 num-packets 5
timeout 500
frequency 5
ip sla schedule 2 life forever start-time now
ip sla 3
icmp-jitter ZZ.ZZ.ZZ.42 source-ip YY.YY.YY.26 num-packets 5
timeout 500
frequency 5
ip sla schedule 3 life forever start-time now
ip sla 4
icmp-jitter ZZ.ZZ.ZZ.42 source-ip XX.XX.XX.227 num-packets 5
timeout 500
frequency 5
ip sla schedule 4 life forever start-time now
ip local policy route-map PING_POLICY
ip route FF.FF.FF.0 255.255.224.0 YY.YY.YY.254 50 track 1
ip route 0.0.0.0 0.0.0.0 YY.YY.YY.254 50 track 3
ip route FF.FF.FF.0 255.255.224.0 XX.XX.XX.225 100 track 2
ip route 0.0.0.0 0.0.0.0 XX.XX.XX.225 100 track 4
ip nat inside source route-map ISP1 interface FastEthernet0 overload
ip nat inside source route-map ISP2 interface FastEthernet1 overload
ip nat inside source route-map ISP3 interface FastEthernet0 overload
ip nat inside source route-map ISP4 interface FastEthernet1 overload
ip access-list extended PING1
permit icmp host XX.XX.XX.227 host ZZ.ZZ.ZZ.39
ip access-list extended PING2
permit icmp host YY.YY.YY.26 host ZZ.ZZ.ZZ.39
ip access-list extended PING3
permit icmp host XX.XX.XX.227 host ZZ.ZZ.ZZ.42
ip access-list extended PING4
permit icmp host YY.YY.YY.26 host ZZ.ZZ.ZZ.42
access-list 1 permit 172.22.31.0 0.0.0.255
route-map PING_POLICY permit 10
match ip address PING2
set interface FastEthernet1
set ip next-hop YY.YY.YY.254
route-map PING_POLICY permit 20
match ip address PING1
set interface FastEthernet0
set ip next-hop XX.XX.XX.225
route-map PING_POLICY permit 30
match ip address PING4
set interface FastEthernet1
set ip next-hop YY.YY.YY.254
route-map PING_POLICY permit 40
match ip address PING3
set interface FastEthernet0
set ip next-hop XX.XX.XX.225
route-map ISP2 permit 10
match ip address 1
match interface Dialer0
route-map ISP1 permit 10
match ip address 1
match interface FastEthernet0
route-map ISP3 permit 10
match ip address 1
match interface Dialer0
route-map ISP4 permit 10
match ip address 1
match interface FastEthernet0
YY.26 первый айпи
YY.254 айпи первого гейтвея
XX.225 второй айпи
XX.227 айпи второго гейтвея
zz.9 пинг проверка 1 пути
zz.42 пинг проверка 2 пути
