DX NetOps

Hello,

I'm a problem for discover an updated element.

Version SNMP : V2c

Search :
The engine ID has create with EngineBoot and EngineTime, RFC 2274, 2.2.2

RFC 2274 - User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3) 

When i make a discovery, my server send a first packet SNMP with options :
I'm look this with Wireshark :

EngineID = 800***
EngineBoot = 1
EngineTime = 4502540

My element, it's a switch and return an error SNMP in OID:

1.3.6.1.6.3.15.1.1.2.0 : usmStatsNotInTimeWindows
And options :
Same EngineID
EngineBoot = 1
EngineTime = 65000

The RFC 2274 display 

The Time Window is a value that specifies the window of time in
which a message generated on behalf of any user is valid. This
memo specifies that the same value of the Time Window, 150 seconds,
is used for all users.  ==> Diff EngineTime option between switch and eHealth.

For reset the sync, i have a solution, but, he have reset the configuration SNMP on switch, who increment the EngineBoot of 1,  the EngineTime is resync and the synchronization is done

But, i don't have a solution for eHealth. I don't have a privilege on switch for reset the configuration SNMP.
It's possible to reset the cache SNMP configuration of eHealth ?
For the first discovery, ehealth use EngineBoot at 0 and EngineTime 0.
With a command or isql command ?

Thank for your regard !

Hello Iskow,

We're not quite sure how the brassd tool remembers the engineID for a device. Not sure if maybe a restart of brassd might trigger a reset, or at least a validation and update where needed for engine ID changes.

You would need to reach out to the support team for that software at support@snmp.com to get more details about that.

From the eHealth side I supposed you could attempt to retire and rediscover, or even delete and rediscover, to try and resolve the problem. Not sure if it would help or not without knowing more about how brassd is keeping the engineID.

Hope that helps you move forward here.

Thanks,

Michael

Hello Michael,

Thank for your help, i have restart the brass service, and the rediscover has been completed.

for everyone, who had a same problem with answer. 

My configuration :
OS : centOs
Version eHealth : 6.4
Agent SNMP : brass

For restart service, i use theses commands in root :
search the brass service :
ps -ef
kill "the number of service" 
/opt/Snmpri/DSSP/brass/bin/brassd -subagent -wbufnum 4096

Rediscover your equipment.

Doc
Setup ehealth to support SNMPV3 discovery, reporting and polling 
Polls using SNMP v3 take a long time to complete (Legacy KB ID CNC TS31264 ) 
https://search.ca.com/assets/SiteAssets/TEC1612625_External/SNMPv3_with_eHealth.pdf