Specifications

Corrected and Known Anomalies
SpectroSERVER (VNM)
Software Release Notes Page 125
9 On the Windows NT platform, the processd no longer causes a
segmentation fault within a fault tolerant environment when you
attempt to start and stop SpectroSERVER through the Control Panel.
Known SpectroSERVER Anomalies in SPECTRUM 6.0
Problem 1: On the NT platform, SPECTRUM will not recognize NT user
accounts even though they exist in the SPECTRUM User Database.
Solution: Ensure that the SPECTRUM user name and NT account name
are spelled identically and have the same case.
Problem 2: On the NT platform with User Auditing turned on, every action
is audited resulting in many entries to the EventLog, and causing the
workstation to become extremely slow.
Solution: Cabletron suggests that NT’s User Auditing not be turned on as
it will hinder system performance and SPECTRUM may not work as
intended. User Auditing can be disabled in
Start|Programs|Administrative Tools(Common)|User
Manager|Policies|Audit.
Problem 3: SPECTRUM 6.0 does not log External List-type Attributes that
have an OID Reference. If you have set the Logged flag in the Model Type
Editor for an Attribute that has the External flag set (that is a List-type
with an OID Reference) you cannot access data for the Attribute using Data
Export, Reports, or a GIB Graph.
Solution: Create a SpectroWATCH for the Attribute that simply logs the
value of the Attribute. Then use the Watch’s destination Attribute ID in
place of the original Attribute’s ID in any Report, Data Export definition, or
GIB graph. Alternatively, you can use the Model Type Editor to create an
Attribute that is a duplicate of the Attribute you intend to log, but not make
it List-type. Then use this duplicate in place of the original Attribute. This
problem will be corrected in a future release of SPECTRUM.