Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-62 CS3 and MMS3
The problem is trying to capture a host config with an ECM template
containing only the host config for a HubCAT1400 fails. The error
message received is: "Capture Failed" and clicking on the Details
button shows the message, "Cannot find error code in ECM_ERROR
file: 0x200000c". Also, closing the Details button and then clicking on
it again produces a core dump of the ECM. The following is a
customer quoted explanation: "This hardware (the c1400, and its
smaller brother the c1100), are an old design, that Cisco inherited
when they brought Crescendo many years ago. For some reason, these
devices store the config on module 3. Module 3 is not and actual
module, it is the processor inside the device. The only insertable
modules are the FDDI/CDDI port modules which can go in slots 1 & 2.
You should also be aware that the SwCat1200 operates in the same
way as the c1400/c1100 and therefore you are also unable to store
configs via the current version of ECM."
The resolution was to incorporate a check to find out if the model type
against which ECM was run was HubCat1400 or SwCat1200. If it
was then the module value setting in CAT_TFTP_MODULE is set to 3
else the module setting remains at 1. For HubCat1400/Swcat1200
devices, host configuration operations can only be performed using
ECM. Scmbg cannot be used. For all other Catalyst devices, the model
handle specified should be that of the corresponding CatStack app,
when using Scmbg.
--
The problem is with ECM. If a scheduled verify of a host configuration
fails, the failure causing line(s) in the host configuration cannot be
identified in the ecmbg.log. There is an incorrect attribute preventing
the log functionality from working correctly. Also, the ecmbg.log is
difficult to read and understand.
The resolution is to correct the attribute name preventing log
functionality. Also, the ecmbg.log formatting is improved.
--
The problem is trying to load an ECM host configuration to more than
one model will fail with the error message: "Not Loaded" with no
explanation. The problem arises due to the way ECM handles results,
in the case of multi load/captures.
The resolution is to change the function of the host configuration
loading so that it will load even when there are no attributes to load.