Specifications

Patches Issued Since the CS2/MMS2 Release

Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1

5-96 CS3 and MMS3

The problem was the customer was continuing to have problems

viewing data and statistics after migrating their database from

SPECTRUM 4.0rev3 to SPECTRUM 5.0rev1. Some of these problems

were originally ﬁxed with Spectrum_5.0rev1.P36. Apparently

SPECTRUM was continuing to cut off the range if it rolled over a year.

The dates of the loaded database prior to the migration were Wed May

27 00:00:00 1998 to Mon Apr 19 14:53:26 1999 and afterward the dates

were: Thu Apr 1 18:36:56 1999 to Mon Apr 19 14:50:48 1999. The

database was becoming truncated.

The resolution was to eliminate the truncation problem and improve

performance.

The problem was when exporting data for a range of "DAY" some

extraneous values outside of this range would appear in the export. If

the range was changed to "CUSTOM" and speciﬁed 00:00 to 23:59, out

of range data points will still appear.

The resolution was to correct the time lapse when exporting data.

The problem was when in a primary and secondary SpectroSERVER

setup -- with Archive Manager running only on the primary -- an

error message will appear after a small period of time (i.e. 15 minutes)

in the ARCHMGR.OUT ﬁle. The error message is:

"May 11 09:26:10 ERROR at CsStatMgr.cc(1393): Stat Log

Manager Invalid stat time."

The resolution was to suppress the error message without changing

any functionality. If the Archive Manager is started without a -debug

ﬂag then the error message will not appear in the ARCHMGR.OUT

log. If the Archive Manager is run with the -debug ﬂag from the

command line then the error messages do appear in the

ARCHMGR.OUT log.

The problem was Link Down events on GnSnmpDev models (event

10308) do not include varbind for iﬁndex. Therefore there is no link

down alarm on the interface speciﬁed by the varbind.