search cancel

Snmpcollector probe regularly failing (becoming non-responsive)

book

Article ID: 229312

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Snmpcollector probes regularly failing, and becoming non-responsive.

 

Cause

auto discovery time interval seem to be too short

Environment

Release : 20.3

Component : UIM - SNMPCOLLECTOR

Resolution

Turning Hours between discovery to 0  in configuration setup resolved issue or this can also be increased to a higher number

depending on the amount of devices been discovered could also help if customer wants to leave auto discovery on.

<setup>
    pollInterval = 300
    currentFilter = All Devices
    debug_ctd_transform_disabled = false
    pollConfigStatus = Poll configuration completed
    validate_credentials_on_add = true
    starts = 603
    logsize = 40960
    snmptimeout = 2000
    hoursBetweenRediscovery = 0
    discoveryServerImportStatus = 
    numDevicesUntilPartialProfiles = 100
    perfLoggingEnabled = false
    autoTemplate = false
    bulkConfigStatus = 19 Template(s) applied successfully to 17 device(s) in 2 seconds.
    repushMonitorsOnStartup = false
    debug_ctd_publish_disabled = false
    build = 803
    debug_ctd_generate_fake_monitors = false
    deviceDiscoveryStatus = Discovered 17 device(s) in 12 seconds
    publishByHostName = true
    configVersion = 404
    debug_ctd_generate_timing_logs = false
    debug_ctd_use_full_graphs = false
    CTD_TRANSFORM_PROCESS_UNCACHED_ITEMS = false
    loglevel = 5
    snmpretries = 3
    POLLER_THREAD_MULTIPLIER = 12
</setup>

Additional Information

Tech document has more information on this setting

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/snmpcollector-snmp-data-monitoring/snmpcollector-ac-configuration.html