Specifications

SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.5.1
Page 37
Document 0743
Revision 14
June 2002
Known Anomalies: SPECTRUM Configuration Manager (SCM)
Item Description Solution
1 If you create or capture a configuration
that includes external list-type attributes
with an OID reference, it generates the
error message:
No instance exists.
Use the Model Type Editor to:
- Create an identical attribute of the one
you need to use in configurations, but do
not make it list-type, and
- Use the new attribute in configurations
to access and set the value on the
device.
This issue will be corrected in a future
release of SPECTRUM.
2 The Detail Result views for Load,
Capture, or Verify do not show strings for
enumerated attributes. The same is true
for the scmbg log.
This issue will be corrected in a future
release of SPECTRUM.
3 When displaying long attribute values,
the Verify Detail window sometimes
truncates the left portion of the display.
This happens when you:
- Scroll to the right in the Verify Detail
window.
- Cancel out of the window.
or
- Re-enter the Verify Detail window.
If the display truncates, click in the
middle of the horizontal scroll bar. SCM
resets the display so it is left-justified.
4 Some attributes such as AT_Net_Addr
are no longer maintained by the device.
In the MIB, these variables have the
status of Deprecated. Attempts to read
or write to these attributes cause
unpredictable results.
If you have problems reading or writing
to certain attributes, use MIB Tools to
see if the status is specified as
Deprecated. If so, delete the attribute
from the configuration or template.
5 Background Host Configuration
operations fail for HubCat1900 series
devices.
The HubCat1900 does not support the
CAT-STACK-MIB.
6 When the Once frequency is selected to
schedule an operation, the scheduler
performs the task; then updates the
entry in the Scheduled Entries field so
the task is scheduled at the same time
next year.
If you see entries for a future year that
you did not schedule, delete them.
7 Sometimes operations scheduled in the
SCM scheduler do not start at their
specified times.
Stop and restart your cron daemon.
Contact your system administrator for
more details about cron and your
workstation.