Allied Telesis AlliedView-EMS 4.0 INSTALLATION - Manual (Page 16)

AlliedView™-EMS 4.0 INSTALLATION GUIDE Page 16 of 29
If a device icon is displayed as a computer in SNMPc, double clicking it may not launch Device
Manager. In this case, poll the device to change its icon to an ATI product icon then double click the
icon again.
Note - SNMPc v7.0.16 and later versions do not allow spaces in device object names. As a result, ATI
devices whose system name contains spaces will not be discovered correctly. Labels for such devices
will show the device’s system name instead of its IP address. Furthermore, launching Device Manager
to connect to these devices will result in the error message: “Request/Poke failed. Error 0x10”.
Device Manager will then hang at this point.
To prevent this from happening, the name-value pair “UseSysName=No” can be added to the Polling
Agent section of the snmpc.ini file. This will force SNMPc to use the IP address of devices as labels.
Note - When SNMPc discovers two or more devices with the same system name, a device icon will
be displayed for each. However, all these device icons will have the same label and will be pointing to
the same specific device – the first one that was discovered.
To prevent this from happening, the name-value pair “NoDupNames=Yes” can be added to the
SNMPcConfig section of the snmpc.ini file. This will configure SNMPc to append a unique number to
the non-unique labels in order to make them unique.
Note - SNMPc, by default, has the ability to recognize the AT-8224XL device as an Allied Telesis
device. This means that, upon discovery of this device, SNMPc automatically displays an ATI device
icon for it. However, integrating AlliedView-EMS with SNMPc alters the reference to the AT-
8224XL. As a result, after uninstalling AlliedView-EMS, SNMPc no longer recognizes the AT-8224XL
as an Allied Telesis device.
Note - AlliedView-EMS temporarily removes the ati6875.mib file from the SNMPc MIB database
during integration with SNMPc. This MIB file will be returned upon uninstalling AlliedView-EMS.
7 INTEGRATING ALLIEDVIEW-EMS 4.0 WITH OPENVIEW
The AlliedView-EMS 4.0 installer automatically detects if HP OpenView is installed and will perform
the necessary integration so that AlliedView-EMS 4.0 can be started from within OpenView. After
integration, the “AlliedView-EMS” submenu is added to the “Tools” menu. “AlliedView-EMS”
contains the options “Device Manager” and “AMIGO”.