DX Unified Infrastructure Management

  • Private Community
 View Only

  • 1.  I can't discovery a device with snmpcollector

    Posted Sep 11, 2019 11:16 AM
    Hi all.
    I have a device Fortinet FortiSandbox v2.5,build0320,130621 but snmpcollector indicate "SNMP Credentials are not valid...."

    The configuration is ----> SNMPv3 -->  autentication : SHA1 - privacy : AES128

    I am testing the snmpv3 with sapwalk and the credentials is working but I see this error after some minuts----->

    #sapwalk2: ver 2.14
    #Copyright (c) 1994-2013 SIMPLESOFT Inc.
    #Address=172.26.51.41, StartOid=1.3.6.1
    #TimeOut=90000, MaxRetries=3, CompareFlag=0
    #args: -i 172.26.51.41 -v v3 -s 1.3.6.1 -u xxxxx -l AP -xt SHA -xa xxxxx -xp xxxxx -xe AES128 -o PruebasForti.walk
    1.3.6.1.2.1.1.1.0 , OctetString ,
    1.3.6.1.2.1.1.2.0 , ObjectID , 1.3.6.1.4.1.12356.118.1.30007
    1.3.6.1.2.1.1.3.0 , TimeTicks , 67702057
    1.3.6.1.2.1.1.4.0 , OctetString ,
    1.3.6.1.2.1.1.5.0 , OctetString , FSA2KE3117000268
    1.3.6.1.2.1.1.6.0 , OctetString ,
    1.3.6.1.2.1.1.7.0 , Integer , 78
    1.3.6.1.2.1.1.8.0 , TimeTicks , 0
    1.3.6.1.2.1.1.9.1.1.1 , Integer , 1
    1.3.6.1.2.1.1.9.1.2.1 , ObjectID , 0.0.0
    .
    .
    .
    .
    1.3.6.1.4.1.12356.118.5.1.9.0 , Integer , 0
    1.3.6.1.4.1.12356.118.5.1.10.0, Integer , 0
    1.3.6.1.4.1.12356.118.5.1.11.0, Integer , 10
    #Got endOfMIBView. Making sure no more oids left. Trying 1.3.6.1.4.1.12356.118.5.1.12
    #Got endOfMIBView. Making sure no more oids left. Trying 1.3.6.1.4.1.12356.118.5.2
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.1.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.2.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.3.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.4.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.5.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.6.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.7.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.8.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.9.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.10.0, Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.11.0, Integer , 10
    #Agent is broken. Getnext returned request oid. Trying 1.3.6.1.4.1.12356.118.5.1.11
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.11.0, Integer , 10
    #Agent is broken. Getnext returned request oid. Trying 1.3.6.1.4.1.12356.118.5.2
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.1.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.2.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.3.0 , Integer , 0
    #ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.4.0 , Integer , 0

    This error maybe it's the cause of the problem?
    Does anyone know this error and what could be happening?
    What can I do?


  • 2.  RE: I can't discovery a device with snmpcollector

    Posted Sep 11, 2019 02:32 PM
    As per this KB MAX_BATCH may help. 
    https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=100122

    If not the poller.log may be most helpful.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 3.  RE: I can't discovery a device with snmpcollector

    Posted Sep 13, 2019 01:28 PM
    Hi @David Michel thanks for you comments.
    I have max_batch = 6 from long time.
    The problem is only with a device and when i try tested with sapwalk, generate this error

    ​#ERROR:LEXORDER:1.3.6.1.4.1.12356.118.5.1.11.0, Integer , 10
    #Agent is broken. Getnext returned request oid. Trying 1.3.6.1.4.1.12356.118.5.1.11

    I don't know if this is the problem for discover in snmpcollector and I posted my problem thinking that maybe someone on the community went through this
    Original Message


  • 4.  RE: I can't discovery a device with snmpcollector

    Posted Sep 13, 2019 01:54 PM
    Miller,
    At this point from my perspective the next step is to engage the network engineer who owns that Fortinet device. 

    From above it goes from 
    1.3.6.1.4.1.12356.118.5.2
    to 
    1.3.6.1.4.1.12356.118.5.1.1.0

    oids in a mib go up so next should be 5.2.1xx or 5.3, not down to 5.1.1

    First thing to check is for an updated mib, next firmware, after that off to support.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 5.  RE: I can't discovery a device with snmpcollector

    Posted Sep 11, 2019 03:54 PM
    Hi Miller,

    Try making a restart to the snmpcollector probe. And in some times you will need restart the robot were the probe was installed.

    Regards

    Jose
    Original Message


  • 6.  RE: I can't discovery a device with snmpcollector

    Posted Sep 11, 2019 04:15 PM
    Rather than 'restart' a deactivate, activate is better since it will completely stop snmpcollector and clear all of its threads in memory.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------

    Original Message


  • 7.  RE: I can't discovery a device with snmpcollector

    Posted Sep 13, 2019 01:29 PM
    Hi all, I maked this procedure but the problem is the same.

    Some other sugerence ?
    Original Message