Specifications

SpectroSERVER (VNM)
Known SpectroSERVER Anomalies in SPECTRUM 6.0.2
SPECTRUM Software Release Notes Page 104
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.
Problem 3: External List-type Attributes which have an OID Reference
display with, “[ ]” in the Attribute Browser, but you are not required to
enter an instance to access its value as required for other Attributes
displayed with “[ ].”
Solution: Ignore the “[ ]” indicator in the Attribute Browser when
accessing External List-type Attributes that have an OID Reference.
Aprisma will investigate this inconsistency.
Problem 4: On the Windows NT server, the Archive Manager could take
up most memory after running for a period of time. SpectroSERVER could
also fail or cause an “out of memory” error message.
Solution: If this is a problem for you, do the following: Set the server
optimization from the default of “maximize throughput for file
sharing” to “balance” under the Properties tab located in Control Panel-
> Network-> Services->Server->Properties.
Problem 5: The Event Log and Alarm Manager will give you misleading
connection status. If the Archive Manager runs with the wrong landscape
handle, it will correctly generate an orange alarm indicating that no
connection has been established. Yet, the connection status dialog in
Alarm Manager and Event Log is green indicating that they are connected
to the Events Service.
Solution: The Alarm Manager receives its alarms from SpectroSERVER’s
landscape. When an attempt is made to connect to the Archive Manager to
get the events associated with the selected alarm, that connection is routed
to the “default service” which is the SpectroSERVER. The SpectroSERVER
supports the default, but the requests will fail. However, the connection to
the server as the event service (default) is up/established - thus, the
connection dialog shows the green connection to events. The default
service is in place as all service was previously defaulted to the
SpectroSERVER.