The first is caused by the Hikvision devices being trash and not supplying the correct oids to be able to detect duplicates. Mike might have a workaround for these.
The second is seemingly caused by those two devices having identical snmpEngineIDs and entPhysicalSerialNums. This is very unlikely, have you checked the DNS for these is correct? It seems to be returning the sysName of the existing device, so it’s almost certainly a broken dns/hosts entry.
Adam.
From: observium <observium-bounces@observium.org> On Behalf Of Steven Rixon via observium
Sent: 10 September 2020 20:09
To: observium@observium.org
Cc: Steven Rixon <steven.rixon@wtlholdings.com>
Subject: [Observium] Error Adding Host
Hi
I am trying to add a new device but receiving the following error
Try to add lam-nvr-057.example.com:
Trying v2c community *** [0] ...
Already got device with SNMP-read sysName () and other system Oids (lam-nvr-047.example.com).
The device is a hikvision nvr and I do have multiple Hikvision nvr’s already monitored
I have also experienced this on a completely different install of observium while adding a cisco AP but unlike on the first install this is the only AP being monitored
Adding SNMPv2c host rix-ap-05.example.com port 161
×
Trying v2c community *** [0] ...
Already got device with SNMP-read sysName (rix-sw-02), 'snmpEngineID' = 8000113D0304097399A298 and 'entPhysicalSerialNum' = CN7BK3Q04W (rix-sw-02.example.com).
The results are the same from both the gui or cli
Thanks
Steven
|
