Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Tracking state remains down -- 1811W

Hi everyone

I am having an issue were the tracking state does not change to up after a simulated fail and the only way to change it to reachability up is by doing a reload.

So any ideas what am i doign wrong?

!

ip sla 1

icmp-echo 68.87.76.178 source-interface FastEthernet0

timeout 1000

threshold 800

frequency 10

ip sla schedule 1 life forever start-time now

!

!

ip sla 2

icmp-echo 69.110.95.110 source-interface FastEthernet1

timeout 1000

threshold 500

frequency 10

ip sla schedule 2 life forever start-time now

11 REPLIES
New Member

Re: Tracking state remains down -- 1811W

Am i posting in the wrong forums?

Hall of Fame Super Bronze

Re: Tracking state remains down -- 1811W

Can we see some verification output such as:

sh ip sla monitor operational-state

sh ip sla monitor statistics

sh track

Before and After the failure.

__

Edison.

New Member

Re: Tracking state remains down -- 1811W

Hi edison thx for your reply.

I solved the issue by reducing the

threshold from 40 to 20. What does the threshold do exacly?

I have my isp1 connection to Fastethernet0 and my isp2 connection to Fastethernet1.

I had the isp2 modem off but when i did a relaod on the router and the router stoped working after the reboot till I unpluged the isp2 cable and only then the isp1 connection fastethernet0 started working again.

Any idea why it would do that?

My second question is I have an exchange server with a local ip of 192.168.1.20 how do I configure the router to use isp1 by default but if isp1 fails use isp2?

Thank you very much for your help.

Hall of Fame Super Bronze

Re: Tracking state remains down -- 1811W

What does the threshold do exacly?

The threshold is an optional entry and it's used for proactive monitor within the SLA. If you decided to place a value to the threshold, there is more configuration that needs to be done. I suggest you read this document

http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hsthresh.html

I had the isp2 modem off but when i did a relaod on the router and the router stoped working after the reboot till I unpluged the isp2 cable and only then the isp1 connection fastethernet0 started working again.

Any idea why it would do that?

I can't tell what the problem may be based on one paragraph. Please post some outputs when the problem occur such as show ip route, show ip int brief, show ip nat trans. Were you trying to reach the internet from behind the router or from the router itself? Etc....

My second question is I have an exchange server with a local ip of 192.168.1.20 how do I configure the router to use isp1 by default but if isp1 fails use isp2?

This is very tricky and requires you do to some work not only at the router itself but with your ISP. Your incoming mail is pointing to an external MX record which is hosted by your DNS provider. This MX record needs to be updated to include ISP1 IP address along with ISP2 IP address.

At the router side, this is something I never personally done (static NAT with track).

__

Edison.

New Member

Re: Tracking state remains down -- 1811W

This is after a reload with both wans plugged in but dsl modem is offline. I cannot access the internet or ping 70.xx.xx.xx until I shutdown fa1.

isp1=70.xx.xx.xx

isp2=69.xx.xx.xx

Cisco-1811#sh track

Track 10

Response Time Reporter 1 reachability

Reachability is Up

1 change, last change 01:15:19

Delay up 10 secs, down 15 secs

Latest operation return code: OK

Latest RTT (millisecs) 1

Tracked by:

STATIC-IP-ROUTING 0

Track 20

Response Time Reporter 2 reachability

Reachability is Down

2 changes, last change 01:14:35

Delay up 10 secs, down 15 secs

Latest operation return code: Timeout

Tracked by:

STATIC-IP-ROUTING 0

show ip route

Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2

i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

ia - IS-IS inter area, * - candidate default, U - per-user static route

o - ODR, P - periodic downloaded static route

Gateway of last resort is 70.xx.xx.xx to network 0.0.0.0

69.xx.xx.xx/xx is subnetted, 1 subnets

C 69.xx.xx.xx is directly connected, FastEthernet1

70.xx.xx.xx/xx is subnetted, 1 subnets

C 70.xx.xx.xx is directly connected, FastEthernet0

C 192.168.0.0/24 is directly connected, Vlan1

S* 0.0.0.0/0 [1/0] via 70.xx.xx.xx, FastEthernet0

Cisco-1811#sh ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0 70.xx.xx.xx YES NVRAM up up

FastEthernet1 69.xx.xx.xx YES NVRAM up up

FastEthernet2 unassigned YES unset up up

FastEthernet3 unassigned YES unset up down

FastEthernet4 unassigned YES unset up down

FastEthernet5 unassigned YES unset up down

FastEthernet6 unassigned YES unset up down

FastEthernet7 unassigned YES unset up down

FastEthernet8 unassigned YES unset up down

FastEthernet9 unassigned YES unset up down

Dot11Radio0 unassigned YES NVRAM administratively down down

--More-- Dot11Radio1 unassigned YES NVRAM

Hall of Fame Super Bronze

Re: Tracking state remains down -- 1811W

I cannot access the internet or ping 70.xx.xx.xx until I shutdown fa1.

From the router itself or from a device sitting behind the router?

Can you ping the next hop 70.x.x.x while Fa1 is up from the router ?

New Member

Re: Tracking state remains down -- 1811W

woa well this is interesting.

With Fa1 up everything is fine but when i turn off the modem for fa1, I can ping from the router and i can browse the web just fine the interesting part is i cannot telnet to it anymore with fa1 down and if i ping the 70.xx.xx.xx from an outside computer it fails.

Hall of Fame Super Bronze

Re: Tracking state remains down -- 1811W

It makes no sense. I would like to see the show ip interface brief and show ip nat trans while that's occuring...

New Member

Re: Tracking state remains down -- 1811W

show ip interface brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0 70.xx.xx.xx YES NVRAM up up

FastEthernet1 69.xx.xx.xx YES NVRAM up up

FastEthernet2 unassigned YES unset up up

FastEthernet3 unassigned YES unset up down

FastEthernet4 unassigned YES unset up down

FastEthernet5 unassigned YES unset up down

FastEthernet6 unassigned YES unset up down

FastEthernet7 unassigned YES unset up down

FastEthernet8 unassigned YES unset up down

FastEthernet9 unassigned YES unset up down

Dot11Radio0 unassigned YES NVRAM administratively down down

Dot11Radio1 unassigned YES NVRAM administratively down down

Vlan1 192.168.0.1 YES NVRAM up up

Async1 unassigned YES NVRAM down down

NVI0 unassigned NO unset up up

Cisco-1811#show ip nat translations

Pro Inside global Inside local Outside local Outside global

icmp 70.xx.xx.xx:512 192.168.0.3:512 209.73.170.243:512 209.73.170.243:512

Hall of Fame Super Bronze

Re: Tracking state remains down -- 1811W

I don't see any odd behavior here.

1) Both interfaces are up

2) NAT is translating for 70.x.x.x which is preferred.

What's exactly the problem?

Were you able to connect to the internet while you took those outputs?

You should be able to as I see an ICMP translation.

New Member

Re: Tracking state remains down -- 1811W

FastEthernet1 69.xx.xx.xx YES NVRAM up up --> the modem is off the hook on this one to simulate failure.

I can browse the web and i can ping anything from inside but if i try to ping the 70.xx.xx.xx from an outside computer it fails... maybe its by design.

thank you for you help.

192
Views
0
Helpful
11
Replies
CreatePlease to create content