Specifications

AR System Gateway
Network Configuration Requirements
SPECTRUM Software Release Notes Page 51
• The arsgated does not read changes in the .arsgrc dynamically. On
the Solaris platform, to have the arsgated reread the .arsgrc, you
can send a “kill -USR1 <pid>” signal (from a script, for example).
This will cause the arsgated to reread both the .arsgrc and
.filterc files. You can get the pid from the .arspid file, where the
arsgated writes it at startup. If the arsgated is not running, then the
pid is 0.
This solution will not work on the NT platform, since there is no sig-
nalling in Windows NT.
• If contact with the AR System Server is interrupted, an error is sent to
the UNIX syslog file or the Windows NT Event Viewer. Any trouble
tickets generated by the SPECTRUM AR System Gateway between the
time contact is interrupted and then reestablished are lost.
• Beginning with 6.0, the gateway will be started by processd. In order
for a successful start, a SpectroSERVER needs to be already running.
Network Configuration Requirements
If you are using the base level AR System Gateway (the AR System
Gateway without SANM) to generate automatic trouble tickets in a
distributed SpectroSERVER environment, you need to set up the network
configuration following these general rules:
• The system where you install the AR System Gateway should have
both SpectroGRAPH and the AR System Client tools
1
on it.
• Install one AR System Gateway for each SpectroSERVER generating
trouble tickets.
Each copy of the Gateway connects one SpectroSERVER to one AR
System Server. In order for n SpectroSERVER(s) to generate trouble
tickets, you need n AR System Gateway(s) and n system(s) with
SpectroGRAPH(s) and AR System Client tools. Since each SPECTRUM
1. On the Solaris platform, the AR System Client tools must be downloaded from Remedy’s
web site. On the NT platform, the tools can be installed directly from the Remedy AR System
installation CD.