Specifications

Enterprise Configuration Manager (ECM)
Known ECM Anomalies in SPECTRUM 6.0.2
SPECTRUM Software Release Notes Page 73
Known ECM Anomalies in SPECTRUM 6.0.2
Problem 1: The ECM cannot use External List-typed Attributes that have
OID References within configurations. If you create or capture a
configuration in ECM you receive the error message, “No instance exists.”
for any External List-type Attributes that have an OID Reference.
Solution: Use the Model Type Editor to create an identical Attribute to the
one you need to use in configurations, but not make it List-type. Then use
that new Attribute in configurations to access and set the value on the
device. This problem will be corrected in a future release of SPECTRUM.
Problem 2: When switching between specific, and shared configuration
modes and vice versa, the Configuration window may not show an
expanded list.
Solution: In the Configuration window, click the specific/desired mode
under the View menu. The list of configurations will be appropriately
refreshed. This problem will be corrected in a future release of SPECTRUM.
Problem 3: The Detail Result windows of Load, Capture, or Verify, do not
show friendly strings for enum attributes. This is the same for the ecmbg
log.
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 4: When you install SPECTRUM 6.0.0 on a Windows NT
workstation that previously had SPECTRUM 5.0 installed, the Enterprise
Configuration Manager (ECM) will show no data for a load or capture if you
fail to use the appropriate tftpserv executable, even though the tftp server
popup window says, “completed transfer” and the ECM view states,
“Success.”
Solution: When you install SPECTRUM 6.0.0 on an NT workstation
where a previous SPECTRUM 5.0 existed, you must use the following
tftpserv executable for a successful capture or load in the ECM:
$SPECHOME/tftpboot/tftpserv.exe