Specifications

SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.5.1
Page 26
Document 0743
Revision 14
June 2002
Known Anomalies: AR System Gateway
Item Description Solution
1 On Windows NT/2000: If (for some
reason) the arsgated.exe stops
running, the PERL process that started
the gateway continues to run. If a user
runs the reconfig tool during this time
frame, then stops and restarts the
gateway once the changes are complete,
reconfig starts a second PERL process,
which, in turn, starts another
arsgated.exe. If the original
arsgated.exe was monitored by
processd, it was automatically
restarted. This results in two
arsgated.exe programs running along
with their associated PERL processes.
If the user finds two arsgated.exe tasks
running after having run the reconfig
tool, the administrator needs to run the
reconfig tool again and change at least
one setting of the Automatic Submission
settings.
Note: By entering the same filename for
the output file, the reconfig file sees this
as a change to the settings. Save the
changes and have reconfig stop and
restart the gateway. This stops both of
the existing tasks and restarts only one.
2 On Solaris, when you run SANM-enabled
AR System Gateway with the option -ts
set lower than the number of models you
are filtering (for example, you have 1,
000 models and you set the -ts option to
999 or lower), the swap space is
eventually exhausted and
SpectroSERVER shuts down.
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.
3 On Windows NT, if you modify filters
when the Automatic Trouble Ticket
Generator (arsgated) is running without
SANM, the modifications are not
recognized by the arsgated.
This issue will be corrected in a future
release of SPECTRUM.
4 When running the arsgated, if the AR
System Server password is not entered
on the command line or is not present in
the resource file, you are not prompted
for a password.
The AR System Server password must be
entered either on the command line or in
the resource file.
This issue will be corrected in a future
release of the AR System Gateway.
5 If an alarm is generated on a model with
no name, then a trouble ticket is
submitted from the Alarm Manager, the
trouble ticket for that model is not visible
in the list of all tickets. This occurs when
displaying all trouble tickets. The AR
System Gateway uses the impacted
object’s model name as the name in the
list.
This issue will be corrected in a future
release of SPECTRUM.