Specifications

SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.5.1
Page 15
Document 0743
Revision 14
June 2002
SPECTRUM Alarm Notification Manager (SANM)
General Operational Considerations
Item Description
1 When a new policy is defined with the Policy Administrator, the policy is saved on
the initial SpectroSERVER. If the initial SpectroSERVER shuts down while defining
a new policy, you cannot save the policy or create other policies.
Known Anomalies: SPECTRUM Alarm Notification Manager
Item Description Solution
1 On Solaris, when you run SANM-enabled
AlarmNotifier with the option -ts set
lower than the number of models you are
filtering, the swap space is eventually
exhausted causing SpectroSERVER to
shut down (e.g., You have 1000 models
and you set the -ts option to 999 or
lower).
When setting up the trace file, be careful
about its size relative to the number of
models specified in the policy filter. To be
safe, accept the default size of 10000.
2 In a distributed SpectroSERVER
environment, scheduled associations fail
if:
- Policies are created and stored on
different SpectroSERVERs when running
Policy Administrator against different
initial SpectroSERVERs, and
-Schedules are created to associate
these policies with a particular
application.
To operate the Policy Administrator
against the initial SpectroSERVER and
ensure all policies are stored on a single
SpectroSERVER, edit the
POLICY_LANDSCAPE= resource in both the
.sanmrc file and the .alarmrc file with
the corresponding landscape handle.
3 On Windows NT, users selected to
receive e-mail notification data cannot
receive the e-mail. This occurs when the
user login ID is used by default to
identify the recipient for e-mail
notification.
Manually enter the complete e-mail
address(es) of the user(s) selected to
receive e-mail in the Notification Data
field in the Policy Administrator; do not
just enter the login ID(s) of the user(s).
This issue will be corrected in a future
release of SPECTRUM.