ViPR SRM: Duplicate Array Appears Only in Topology

Сводка: ViPR SRM: Duplicate Array Appears Only in Topology.

Данная статья применяется к Данная статья не применяется к Эта статья не привязана к какому-либо конкретному продукту. В этой статье указаны не все версии продуктов.
Ознакомьтесь с другими ресурсами

Симптомы

When troubleshooting a port issue, an array was removed from the Discovery Center, readded to the Discovery Center with a different name and finally put back into the Discovery Center with the original name when the port issue was resolved.

The array with the new name appeared as a duplicate in topology maps. The array did not appear as a duplicate in any reports. Below is an example with VNX-L3 as the duplicate:
duplicate array

Причина

N/A

Разрешение

  1. Stop the Topology-Mapping-Service on each collector
  2. Stop the Topology-Mapping-Service and the Topology-Service on the primary backend
  3. PuTTy into the primary backend
  4. cd /opt/APG/Backends/Topology-Service/Default/data/topology
  5. mv topology.jnl <to somewhere there is enough space, like /tmp>
  6. Restart the Topology-Mapping-Service on each collector
  7. Restart the Topology-Mapping-Service and the Topology-Service on the primary backend
  8. Ensure the .jnl is rebuilt in /opt/APG/Backends/Topology-Service/Default/data/topology Depending on the size of the configuration, this may be immediate or it may take a couple hours
  9. Check the topology map

Дополнительная информация

To Diagnose:
Open the topology diagnostic UI for the primary backend: 
https://<Primary BE host name>:48443/Backends/Topology-Service/Default/diagnostics/ui
login as admin/changeme
At the bottom of the page, in the Feeding Topology-Mapping-Services, ensure that the Last Recieved Times are all current; If any of the date or times are old, especially for the collector collecting the metrics for the array in question, clear all the data. Check the topology map.

If the date or times are current, open the topology diagnostic UI on the collector collecting the metrics for the array: 
https://<collector_hostname>:48443/Backends/Topology-Mapping-Service/Default/diagnostics/ui
login as admin/changeme

Scroll down to the Forced Metric Delete section and click 'view list of known devices'. Search the list for the name of the duplicate array. (If the name is not there, a search on the other collectors may be done as a precaution.)  If the name is found on the list of known devices, delete it. Check the topology map.

If the name is not found, go back to the topology diagnostic UI for the primary backend:

https://<Primary BE host name>:48443/Backends/Topology-Service/Default/diagnostics/ui
login as admin/changeme

Click the Launch Explore button in the Object Explore section. Since this example is of a duplicate array, choose Type, StorageSystem, with Attribute, displayName contains the name of the duplicate array. In this example, the name is VNX-L3 (see above screenshot). More than likely the array name is found here.

Свойства статьи
Номер статьи: 000161887
Тип статьи: Solution
Последнее изменение: 21 Aug 2025
Версия:  4
Получите ответы на свои вопросы от других пользователей Dell
Услуги технической поддержки
Проверьте, распространяются ли на ваше устройство услуги технической поддержки.