ACE: Problem configuring probe snmp

Unanswered Question
Feb 24th, 2009

Hi,

I have a problem when I configure probe snmp and My Server W2K3 dual core, snmp comunity public has an oid cpu .1.3.6.1.2.1.25.3.3.1.2, the output is:

access-list anyone line 8 extended permit ip any any

probe snmp was

interval 4

faildetect 2

passdetect interval 10

receive 2

community public

oid .1.3.6.1.2.1.25.3.3.1.2

threshold 70

rserver host was1

ip address 10.24.8.200

probe was

inservice

rserver host was2

ip address 10.24.8.201

probe was

inservice

serverfarm host servers

rserver was1

inservice

rserver was2

inservice

class-map type management match-any ADM-CONTEX-SERV1

4 match protocol icmp any

5 match protocol snmp any

class-map type http loadbalance match-all Check-Headers

2 match http url .*

3 match http header Host header-value "10.24.16.*"

4 match http header User-Agent header-value ".*MSIE.*"

class-map match-all VIP-10-HTTP

2 match virtual-address 10.24.16.10 tcp eq www

class-map type http loadbalance match-all other-HTTP

2 match http url .*

policy-map type management first-match ADM-CTX-SERV1

class ADM-CONTEX-SERV1

permit

policy-map type loadbalance first-match L7-logic

class Check-Headers

serverfarm servers

class other-HTTP

serverfarm servers

policy-map type loadbalance first-match lb-logic

class class-default

serverfarm servers

policy-map multi-match client-vips

class VIP-10-HTTP

loadbalance vip inservice

loadbalance policy L7-logic

loadbalance vip icmp-reply active

interface vlan 60

ip address 10.24.8.5 255.255.255.0

access-group input anyone

access-group output anyone

service-policy input ADM-CTX-SERV1

no shutdown

interface vlan 233

ip address 10.24.16.5 255.255.255.0

access-group input anyone

access-group output anyone

service-policy input ADM-CTX-SERV1

service-policy input client-vips

no shutdown

ip route 0.0.0.0 0.0.0.0 10.24.16.1

sh probe was detail

probe : was

type : SNMP

state : ACTIVE

description :

----------------------------------------------

port : 161 address : 0.0.0.0 addr type : TRANSPARENT

interval : 4 pass intvl : 10 pass count : 3

fail count: 2 recv timeout: 2

version : 1 community : public

oid string #1 : .1.3.6.1.2.1.25.3.3.1.2

type : PERCENTILE max value : 100

weight : 16000 threshold : 70

--------------------- probe results --------------------

probe association probed-address probes failed passed health

------------------- ---------------+----------+----------+----------+-------

rserver : was1

10.24.8.201 13 13 0 FAILED

Socket state : CLOSED

No. Passed states : 0 No. Failed states : 1

No. Probes skipped : 0 Last status code : 0

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : Server reply - bad SNMP OID

Last probe time : Tue Feb 24 23:22:41 2009

Last fail time : Tue Feb 24 23:20:47 2009

Last active time : Never

Server load : 16000

rserver : was2

10.24.8.200 12 12 0 FAILED

Socket state : CLOSED

No. Passed states : 0 No. Failed states : 1

No. Probes skipped : 0 Last status code : 0

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : Server reply timeout (no reply)

Last probe time : Tue Feb 24 23:22:34 2009

Last fail time : Tue Feb 24 23:20:52 2009

Last active time : Never

Server load : 16000

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
ciscocsoc Wed, 02/25/2009 - 01:08

Hi,

For a multicore processor you need to make a few changes to get the load on each core/processor. You need to have an instance for each core.

Try adding .1 or .2 to the OID to get the load on each core.

Also try doing an snmpwalk on the OID to see what the real structure is.

HTH

Cathy

Actions

This Discussion