[c-nsp] IP SLA - "dns operation: Error code=4"

Dean Smith dean at eatworms.org.uk
Tue Feb 5 06:13:31 EST 2008


I had one similar where the source IPs being used from CLI and SLA were
different.

The CLI source was correctly set to a mgmt loopback which did have access to
DNS & the internet. The SLA monitor was using a source that didn't - fixed
by specifying the source for the SLA probe.

Regards
Dean

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Giles Coochey
Sent: 05 February 2008 10:07
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] IP SLA - "dns operation: Error code=4"

Hello,

I'm testing various aspects of IP SLA, and have been trying to set up an
HTTP get url operation - unsuccessfully.

My configuration is as follows:

ip sla monitor 300
 type http operation get url http://www.example.com name-server
<name-server> cache disable
 threshold 5000
 frequency 300
ip sla monitor schedule 300 life forever start-time now

On doing a sh ip sla monitor operational-state 300 I get:

Latest operation return code: Internal error

On enabling trace and error debugging for this monitor, I see the
following:

Feb  5 10:52:05.167: IP SLA Monitor(300) Scheduler: Starting an
operation
Feb  5 10:52:05.167: IP SLA Monitor(300) http operation: Starting http
operation
Feb  5 10:52:05.167: IP SLA Monitor(300) dns operation: Starting dns
operation
Feb  5 10:52:05.167: IP SLA Monitor(300) dns operation: Query name -
www.example.com
Feb  5 10:52:05.167: IP SLA Monitor(300) dns operation: actual target
queried = www.example.com
Feb  5 10:52:05.167: IP SLA Monitor(300) dns operation: Error code=4
Feb  5 10:52:05.167: IP SLA Monitor(300) Scheduler: Updating result
Feb  5 10:52:05.167: IP SLA Monitor(300) http operation: Wait DNS -
incorrect event

The DNS name-server I am using is the same as is configured in main IOS
configuration, and I can successfully ping www.example.com by name from
the IOS CLI.

URLs queried by IP address do work, but for monitoring it would be nice
to have the DNS latency information. Googling the debug lines & errors
doesn't appear to produce anything useful. Any ideas?

This is with 12.2(31)SB10.


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/



More information about the cisco-nsp mailing list