Specifications

Enterprise Configuration Manager (ECM)
Special Requirements for NT Users
SPECTRUM Software Release Notes Page 71
Considerations
You should be aware of the following considerations when using ECM:
• ECM cannot successfully capture a device’s attributes unless the
community string matches the community string in the SNMP-
managed device itself. Likewise, ECM cannot successfully load
external attributes to a device unless the community string matches
the community string that has write permission in the SNMP-managed
device itself. If you need to change the device’s community string, you
can do so by loading a new configuration with the correct
Community_Name attribute value to the device.
• ECM may not successfully capture attributes that require instance IDs
if you are working with early management modules (in particular,
those that support Cabletron proprietary protocol devices such as the
IRM). If you need to capture a configuration from one of these devices,
create a configuration manually (without a template) containing only
attributes that do not require instance IDs. Then manually insert the
attributes with the known instance IDs and the attribute values in the
configuration.
• If you are working in a distributed SpectroSERVER environment, make
sure you manually add your user account to each landscape on which
you intend to perform ECM functions. ECM will not be able to contact
a landscape if the landscape lacks the proper user accounts.
• If configurations are created for an extremely large number of models,
the scrollable box located in the Overview list, to the left of the
Configuration list, will disappear from view if dragged downward, and
the Overview list will not appear scrollable. appui000400
• Host Configuration operations will only work for Cisco Catalyst devices
after navigating to the CatStack application.
• Background operations for Cisco Catalyst devices will only work if the
model handle used is that of the CatStack application, not of the
device itself.