кто знает как пофиксить траблу с дублированием SNMP устрйоств? Удаляю оба объекта, обратно добавляю IP в список для discovery и по прошествию нескольких дискавери вижу дублирующие записи...

Device Key - это ключевой атрибут сетевого устройства

Как правило device Key = MAC

https://social.technet.microsoft.com/Forums/en-US/4b68462c-09eb-41ae-97a8-4c35a05d691c/duplicate-network-device?forum=operationsmanagergeneral
типа такого?

Спасибо.

И тебе тоже

Хотел еще уточнить по поводу конфига на сколько он оптимален

текущие
значения
MinimumDemandGet = TRUE
Использовался только IPv6DiscoveryEnabled = FALSE
PreferIPv4 = TRUE
SNMPGetBulkEnabled = TRUE

много всякого интересного, кстати :)

true admin :)

/help@SystemCenter_Bot

есть 3 записи в базе и только у одной пропиcан mac в Name

Рабочий вариант

UPDATE BaseManagedEntity
SET isdeleted=1
from BaseManagedEntity where BaseManagedEntityId in (select BaseManagedEntityId from BaseManagedEntity where name like '%mac adress of 10.10.30.23%')

👍

Forcing anything to IsDeleted is NEVER supported and there are MUCH better ways to handle this.  There are way too many support cases where support guys do this and it is almost always wrong.  We have internally developed SQL scripts and stored procedures to handle manual deletes from the database in a much safer fashion.  We DO have scenarios where customers had to restore their databases from forcing BME’s to IsDeleted=1. (c) Kevin Holman

😁

--Query 1
--First get the Base Managed Entity ID of the object you think is orphaned/bad/needstogo:
select * from BaseManagedEntity
where fullname like '%computername%'


--Query 2
--Next input that BaseManagedEntityID into the delete statement
--This will delete specific typedmanagedentities more gracefully than setting IsDeleted=1
DECLARE @EntityId uniqueidentifier;
DECLARE @TimeGenerated datetime;
-- change "GUID" to the ID of the invalid entity
SET @EntityId = 'GUID';
SET @TimeGenerated = getutcdate();
BEGIN TRANSACTION
EXEC dbo.p_TypedManagedEntityDelete @EntityId, @TimeGenerated;
COMMIT TRANSACTION


--Query 3
--Check to make sure the IsDeleted field of your BME now = 1
select * from BaseManagedEntity
where fullname like '%computername%'


--Query 4
--Get an idea of how many BMEs are in scope to purge
SELECT count(*)
FROM BaseManagedEntity
WHERE IsDeleted = 1


--Query 5
--This query statement for SCOM 2012 will purge all IsDeleted=1 objects immediately
--Normally this is a 2-3day wait before this would happen naturally
--This only purges 10000 records.  If you have more it will require multiple runs
--Purge IsDeleted=1 data from the SCOM 2012 DB:
DECLARE
      @TimeGenerated DATETIME,
      @BatchSize INT,
      @RowCount INT
SET @TimeGenerated = GETUTCDATE()
SET @BatchSize = 10000
EXEC p_DiscoveryDataPurgingByRelationship @TimeGenerated, @BatchSize, @RowCount
EXEC p_DiscoveryDataPurgingByTypedManagedEntity @TimeGenerated, @BatchSize, @RowCount
EXEC p_DiscoveryDataPurgingByBaseManagedEntity @TimeGenerated, @BatchSize, @RowCount

Maxim привет :)