Specifications

Alarm Notification Manager (SANM)

Known SANM Anomalies in SPECTRUM 6.0.2

SPECTRUM Software Release Notes Page 42

Known SANM Anomalies in SPECTRUM 6.0.2

Problem 1: When you run SANM-enabled AlarmNotifier on the Solaris

platform with the option -ts set less than the number of models you are

ﬁltering (e.g.: if you have 1000 models, you should not set the option -ts

to be 500), the swap space will eventually be used up causing

SpectroSERVER to segmentation fault.

Solution: When setting up the trace file, be careful about its size in

relation to the number of models specified in the policy filter. To be safe,

accept the default size of 10000.

Problem 2: If, in a distributed SpectroSERVER environment, policies are

created and stored on different SpectroSERVERs by running Policy

Administrator against different initial SpectroSERVERs and schedules are

created to associate these policies with a particular application, the

scheduled associations will fail. sanm391

Solution: Ensure that all policies are stored on one SpectroSERVER by

always running Policy Administrator against the same initial

SpectroSERVER.

Problem 3: On Windows NT, users selected to receive e-mail notification

data may not receive e-mail. The users’ login IDs are used by default to

identify to whom notification data is sent.

Solution: Manually enter the complete e-mail addresses (not just the

field in Policy Administrator. This will be corrected in a future release of

SPECTRUM.

Problem 4: The Policy Administrator on Windows NT allows a maximum

of 32,767 models to be displayed in the Add Filter Values view for Model

Names.

Solution: In order to reduce the number of models within a list, filter

models by model type and/or landscape and then by model name.