Specifications

9032277-04 Software Superseded by CS3/MMS3
5-37
Patches Issued Since the CS2/MMS2 Release
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.
--
The ECM has been altered so that ECM will not read the community
string of the user. But the SPECTRUM security underneath will
prevent a user from seeing the devices in other domains and hence
prevent users from attempting to load/capture/verify on these devices.
The user must have write access to the devices in his domain for ECM
host config operations to succeed.
--