Duplicate model alarms in Spectrum's Virtual Host Manager (VHM).
search cancel

Duplicate model alarms in Spectrum's Virtual Host Manager (VHM).


Article ID: 8620


Updated On:


CA Spectrum


We are we seeing duplicate model alarms, in Spectrum for Virtual Host Manager (VHM) models, with systemEdge agents.

e.g. Duplicate model detected. or Duplicate IP with different MAC detected.


This problem can be seen at any version. In this example we are using:

vCenter 5.5.VC AIM 

SystemEdge 5.9.0.

Spectrum 10.2.1


A netstat of the host where the SE agent is installed, which showed the Nagios system agent is also installed and listening on port 5666.

This was the mib entry causing the problem.



Change the port that the Nagios system agent uses.

This now allows us to walk the mib and no new duplicates get created in Virtual Host Manager (VHM).

Additional Information

How to remove duplicate models from Spectrum VHM.



Known issues with duplicate models in Spectrum VHM.


other useful troubleshooting

There can be various reasons for this and if the documented solution below does not work, the cause may be outside of the Spectrum application. 
If we consider the other elements that are required to discover virtual models in VHM, then we should also look at the SNMP agent, providing the virtual functionality. 

Is it possible to get an SNMP walk of the agent? 

In this example, a SNMP walk of the SystemEdge agent with the Sapwalk application, showed the agent had an SNMP problem, with the following error.

#Agent is broken. Getnext returned request oid. Trying
#ERROR:LEXORDER:, Integer , 0
#ERROR:LEXORDER:, Integer , 0
#ERROR:LEXORDER:, Integer , 0
#ERROR:LEXORDER:, Integer , 0
#ERROR:LEXORDER:, Integer , 0
#ERROR:LEXORDER:, Integer , 0
#ERROR:LEXORDER:, Integer , 0
#Agent is broken. Current walk stopped to prevent looping. Trying
#ERROR:LEXORDER:, Integer , 0
#ERROR: Walk ended to prevent continued looping in broken lexicographical ordering. Max allowable lexi errors exceeded.

To rule out a SapWalk problem, WalkTree was also used, to walk the mib which also got stuck in a loop at OID:

Reinstalling the agent gave the same result.


Where can we get further information:
If the port161 (or port1691) directory from the same host, that the walk was generated against, contains logs.

If they do not provide a root cause, then debug data, can be generated, by adding the following lines, in the /port161/sysedge.cf file.

sysedge_logfile sysedge.log 20000 6
sysedge_loglevel debug3

Save the file and restart the SystemEdge services.
After the problem reoccurs, the /port1691/sysedge.log files can be analyzed.