2N ATEUS User manual

ATEUS ® - Remote Control Unit
RCU
User’s Guide
Version: 5.00

CONTENTS
1INTRODUCTION............................................................................................................ 3
1.1 MANAGEMENT ............................................................................................................ 3
1.1.1 Control ............................................................................................................... 3
1.1.2 Monitoring.......................................................................................................... 4
1.2 ACCOUNTING .............................................................................................................. 4
1.2.1 Call Data Record (CDR).................................................................................... 4
1.2.2 Traces ................................................................................................................. 4
1.2.3 Logs .................................................................................................................... 4
1.2.4 Call statistics ...................................................................................................... 5
1.3 EXTERNAL ROUTING ................................................................................................... 5
2THE RCU SYSTEM ........................................................................................................ 7
2.1.1 The basic system................................................................................................. 7
2.1.2 The communication protocols ............................................................................ 7
2.1.3 The Management Services Engines.................................................................... 7
2.1.4 The Management Databases .............................................................................. 8
3INSTALLATION ............................................................................................................. 9
3.1 PRE-INSTALLATION ..................................................................................................... 9
3.1.1 Topology............................................................................................................. 9
3.1.2 Assigning IP addresses....................................................................................... 9
3.2 OS INSTALLATION..................................................................................................... 10
3.2.1 Installation procedure ...................................................................................... 10
4CONFIGURATION ....................................................................................................... 11
4.1 BASIC CONFIGURATION ............................................................................................. 11
4.1.1 E-mail alarms................................................................................................... 12
4.1.2 SMS alarms ...................................................................................................... 12
4.1.3 Call Data Records (billing).............................................................................. 13
4.1.4 The ASR statistics ............................................................................................. 13
4.1.5 Utilization of PRI ports .................................................................................... 13
4.1.6 The PRI GSM gateways.................................................................................... 14
4.1.7 Network Address Translation........................................................................... 15
4.1.8 SNMP Configuration........................................................................................ 15
4.1.9 Binding PRI GSM Gateways to databases....................................................... 15
4.1.10 External routing ............................................................................................... 16
4.1.11 Alarm filtering .................................................................................................. 16
4.2 WEB ACCESS CONFIGURATION .................................................................................. 17
4.3 TESTING .................................................................................................................... 18
4.4 CONFIGURATION EXAMPLE ....................................................................................... 18
4.4.1 IP map Table .................................................................................................... 18
4.4.2 Configuration ................................................................................................... 19
4.4.3 Web pass........................................................................................................... 21
4.4.4 Starting ............................................................................................................. 22
4.4.5 Testing .............................................................................................................. 22
5RCU USAGE .................................................................................................................. 24
1

5.1 WEB ACCESS ............................................................................................................. 24
5.1.1 Welcome Message ............................................................................................ 24
5.1.2 Authentication .................................................................................................. 25
5.1.3 Web Overview .................................................................................................. 25
5.1.4 Web configuration of the gateway.................................................................... 28
5.1.5 Incomming Call Simulation.............................................................................. 28
5.2 SNMP MANAGEMENT .............................................................................................. 29
5.2.1 SNMP Queries.................................................................................................. 29
5.2.2 SNMP Traps ..................................................................................................... 29
5.3 ACCOUNTING ............................................................................................................ 30
6TROUBLESHOOTING................................................................................................. 32
6.1 STARGATE SERVICE .................................................................................................. 32
6.2 GATEWAY CONFIGURATION (SGCONF) ...................................................................... 32
6.3 CHECKING THE DATABASES ...................................................................................... 33
6.3.1 Gateway Databases.......................................................................................... 33
6.3.2 Gateway Terminal (sgterm) ............................................................................. 33
6.3.3 Accessing table main........................................................................................ 33
6.4 STARGATE (BLUESTAR) PROGRAM USING RCU AS A TUNNEL .................................. 35
6.5 TRACING OF THE TRAFFIC ON GATEWAYS .................................................................. 37
7FAQ ................................................................................................................................. 38
APPENDIX 1: THE TRAP TABLE ..................................................................................... 39
2

1 Introduction
Unlike the most of telecommunications devices that come with integrated remote
management modules, PRI GSM gateways produced by 2N Telekomunikace a.s, the ATEUS
® STARGATE (Stargate) and ATEUS ® BLUESTAR (Bluestar) come with a Remote
Control Unit (RCU), a standalone device offering a wider range of management and
accounting capabilities. The RCU was originally developed to provide management of
Stargate. The new version 2.0 supports both types of PRI GSM gateways. This User’s Guide
references to RCU ver. 4.00 and higher. Though the most of commands or database names
remind on Stargate, as the RCU original goal, the RCU could be used for both gateways.
IMPORTANT!!!
RCU ver. 4.00 and higher requests Stargate (Bluestar) firmware version
2.16.43 or higher.
1.1 Management
One RCU can manage up to eight PRI GSM gateways.
1.1.1 Control
The RCU supports a number of methods for querying and or changing the PRI GSM
gateways’ parameters:
• Web interface: From the common web browser, customers can alter configuration
parameters in their PRI GSM gateways on the fly (Web configuration).
• Simple Network Management Protocol (SNMP): Designed to proxy PRI GSM
gateways to most commonly used network management software, The RCU allows
clients to send legacy SNMP queries.
• Secure AT shell: The PRI GSM gateway supports a set of AT commands. To send
these commands to the PRI GSM gateways remotely, one has to use telnet, an
insecure remote login protocol. The RCU nails this problem such that, over the
insecure Internet, telnet traffic is tunneled through Secure Shell (SSH) and only
allowed in the LAN where the climate is relatively friendly. This allows clients to
send configuration or query commands to the managed PRI GSM gateways without
having to worry that an evil cracker could be tapping the communication (see Fig.1).
3

Fig.1: AT command tunneling over SSH
1.1.2 Monitoring
The RCU comes with a number of PRI GSM gateway monitoring methods:
• Web interface: over the WWW, clients can monitor their PRI GSM gateways while
comfortably sitting in their offices. Occurrences of undesired (erroneous) conditions
are promptly indicated by changes of color in the offending modules.
• Simple Network Management System (SNMP): The RCU continuously monitors the
attached PRI GSM gateways and sends an SNMP trap every time a non standard
status is observed
• E-mail: The RCU can be configured to send an email alarm in event that a PRI GSM
gateway or one of its components fails
• SMS: The RCU is also capable of sending an SMS alarm when so configured, to
announce faults in the managed devices.
1.2 Accounting
The RCU is equipped with a number of databases and processes that collect and archive call
accounting data
1.2.1 Call Data Record (CDR)
The RCU periodically collects CDRs from the PRI GSM gateways and stores them in its local
disk. This removes the risk that these records would be overwritten when the PRI GSM
gateway buffers are filled. These CDRs are accessible through the web.
1.2.2 Traces
The RCU automatically reroutes all the PRI GSM gateway call traces to its local disk. These
traces come in handy when troubleshooting a non standard status. They can also be accessed
over the web.
1.2.3 Logs
The RCU also stores status logs on all the PRI GSM gateway management applications.
These are again useful when diagnosing management problems.
4

1.2.4 Call statistics
The RCU stores call summaries. These can be either overall or based on differed modules and
SIM cards. The call statistics are readily available over the web
1.3 External Routing
The PRI GSM gateway is equipped with an additional capability to route calls based on an
external routing database – the so-called External Routing. This design opens the doors to the
PRI GSM gateway, to take advantage of the greater capacities of external routing databases as
opposed to its limited internal routing buffers. The RCU, as we shall see, has a special
database for this purpose. To use this special function, a routing database (LCR) has to be
installed into the RCU. This database contains a table rtlist. Each record in database contains
destination phone number and a number of the outgoing GSM group, the call should be routed
through. If the group number is 0, call will be rejected i.e. that number is on “blacklist”. If the
group number is 9, call will be routed to the second PRI port of the gateway (PRI2).
External routing works in such a way that, when a call comes into the PRI GSM gateway
either from the PRI interface (SETUP) or from the GSM network (RING), the PRI GSM
gateway opens a telnet connection to the RCU and requests for instructions on how to route
the call. This request is of the form *ring: ch,cref,dial,clip where:
• Ch – module number (0-31) or PRI channel 97-111 and 113-127 (timeslot +96)
• Cref – internal call reference number (1-255)
• Dial – called (destination) number
• Clip – callers (source) number
After receiving this message, the first thing the RCU does is that it compares dialed number
against the numbers in the table. If there is a match and group number is 0,then the call is
rejected with a cause (AT^CR=ch, cref,cause). If on the other hand, group number is 1-9,the
RCU returns immediately a return value that contains the group number through which the
call will be routed in the PRI GSM gateway (AT^RG=ch,cref,groups). In the case that “dial”
is not found in the routing table, the PRI GSM gateway timesout and uses its internal LCR to
route the call (Fig.2).
5

Incomming request from
the gateway
*ring: ch, cref, dial,clip
6
Gateway will route the
call according to its
internal settings
Grou
p
number 0 ?
Grou
p
number 1-9 ?
Call is rejected
AT^RG = ch, cref, cause
Call is routed to the group
according to number in the
table
AT^RG = ch, cref, groups
YES
NO
NO
YES
Fig. 2: External routing

2 The RCU System
2.1.1 The basic system
The RCU is made up of a powerful industrial PC running the Linux OS. Linux was
specifically chosen to make the system relatively secure.
On top of the Linux OS are a web server (Apache), a database engine (Postgre) and a set of
PRI GSM gateway Management and Accounting applications.
2.1.2 The communication protocols
The RCU is equipped with two Ethernet cards usually Eth0 and Eth1. Eth1 connects to the
managed PRI GSM gateways’ subnet. The RCU uses this interface to communicate with the
PRI GSM gateways by telnet or to send SMS in the event of a fault. This arrangement
logically isolates the PRI GSM gateways’ subnet from the rest of the network and hence using
telnet does not open security holes. Eth0 is intended to communicate to the rest of world
without making it known that there are PRI GSM gateways hidden on the other side of the
wall! The protocols propagated through the firewall include:
• HTTP for web management
• SNMP to provide legacy network management functionality
• SSH for secure remote login
• SMTP sends an email if something happens (see Fig.3).
Fig.3: The RCU Protocols
2.1.3 The Management Services Engines
The RCU hosts a total of four management services:
• Routing Service Engine (RSE): Serves for external routing
7

• ISDN Trace Service Engine (ITSE): This engine is responsible for downloading ISDN
traces
• Status Service Engine (SSE): Responsible for periodically downloading statuses of the
PRI GSM gateways. If an undesired status is observed, the corresponding status alarm
is generated.
• SMS and E-mail Service Engine (SESE): This service can be invoked to send an alarm
by either an SMS or e-mail
2.1.4 The Management Databases
• Status Database (SDB): Actual PRI GSM gateway statuses are stored here for each
managed PRI GSM gateway. These include databases Stargate0-7
• ISDN traces, CDR and Log database (IC&LDB): Just as the name indicates, this DB
stores ISDN traces, Call Data Records and Management application logs for the
managed PRI GSM gateways
• Routing Database (RDB): Used by RSE for external routing purposes (see Fig. 4.)
• Configuration database (CDB): This database is used for web configuration, a
platform for configuring PRI GSM gateway over the web.
Fig.4: The RCU services and databases
8

3 Installation
3.1 Pre-installation
For a comprehensive and painless installation, a pre-installation preparation is mandatory.
3.1.1 Topology
The RCU can communicate with PRI GSM gateways in any one of the following modes:
• RS-232 serial communication through COM1&COM2. This mode can be used if at
least one of the PRI GSM gateways is within the proximity of the RCU. It is
recommended that this mode be used when only one PRI GSM gateway is to be
managed by the RCU
• Ethernet (10BaseT). There exists, as many logical network topologies, as there are
network technicians. In the following chapter, only those parameters that a technician
needs to know in order to either fit in the RCU into an existing network or to come up
with a network for this purpose will be presented.
3.1.2 Assigning IP addresses
The RCU demands two logical sub-networks.
• The PRI GSM gateway sub-network (SG-SUBNET): Eth1 of the RCU and all the PRI
GSM gateways must belong to the SG-SUBNET. If different PRI GSM gateways are
placed in different logical network segments then you may consider implementing
Network Address Translation (NAT) so that all the PRI GSM gateways will appear
to belong to the same network segment. Majority of network technicians put both
Eth1 and the PRI GSM gateways in to a private LAN (10.0.0.0, 192.168.0.0 etc.).
The communication protocol in this segment is TELNET.
• The Management sub-network (MNGMNT-SUBNET): Eth0 interface on the RCU is
assigned an IP address from this segment. The management station must be reachable
from Eth0. If traffic between RCU and the management station goes through a
firewall, then, depending on the desired services the following protocols may need to
be enabled:
Application protocol Transport Protocol Port
HTTPS TCP 443
SSH TCP 22
SNMP UDP 161,162
SMTP TCP 25
Table1: Protocols to consider allowing through the Firewall
9

Fig.5: The RCU Topology
For each managed PRI GSM gateway, the RCU runs a separate SNMP agent. Each running
SNMP agent requires an IP address to communicate with the SNMP management node. Let
us assume that our RCU will proxy eight PRI GSM gateways (SG0, SG1, …, SG7), The
SNMP agent for SG0 will use Eth0 to communicate with the SNMP management node. The
remaining seven SNMP agents (SG1 – SG7) will need seven additional IP addresses from the
MNGMNT-SUBNET. These seven additional IP addresses are added as aliases to Eth0
(Eth0:1, Eth0:2, …, Eth0:7) see Fig.5.
3.2 OS installation
3.2.1 Installation procedure
• Power the RCU
• Insert the RCU-CD into the CD-ROM
• Press Enter to Boot from the CD-ROM when prompted
• Type “y” to format the HD and to go on and install the RCU SW when prompted
• Wait for the system to eject the RCU-CD and press the “Reset” button to reboot the
system. If you have gone this far, the OS is installed!
• Stand by for the system to reboot and press any key enter HW configuration. Please
pass the screens picking the defaults, this will usually do, alternatively, tweak to taste!
• Type “root“ at the login prompt. “skakal pes pres oves++” is the default password.
10

4 Configuration
4.1 Basic configuration
Type sgsetup at the bash prompt to run the management software configuration script
bash-2.05a#
bash-2.05a# sgsetup
The SGSETUP configuration script will guide you through the entire configuration process
needed to set up the RCU. The text below will take us through the different options
Enter current date [07.08.2003]:
Today’s date
Enter current time [15:01]:
The time now
eth0: IP address [192.168.100.100]:
IP address assigned the Eth0
eth0: Netmask [255.255.255.0]:
Subnet mask for the MNGMNT-SUBNET
eth0: Default gateway [192.168.100.1]:
IP address of the gateway used to reach the network management station (not necessary if the
RCU’sEth0 and the management station are in the same network segment)
eth1: IP address [192.168.10.2]:
IP address assigned to Eth1
eth1: Netmask [255.255.255.0]:
Subnet mask for the SG-SUBNET
SNMP trap IP address (1) [192.168.100.3]:
Management stations IP address
SNMP trap IP address (2) [192.168.100.3]:
Backup management station (The same management station can be used for redundancy)
SNMP community [public]:
Every device managed by SNMP must belong to an SNMP community (Public community is
the default. The same community name must be set in the management node)
11

4.1.1 E-mail alarms
Enable e-mail sending? [YES]:
Answer yes (y) to enable e-mail alarms, no (n) disables this option
E-mail 'FROM' address [[email protected]]:
This entry acts as the sender (source) of the e-mail
E-mail 'TO' address [[email protected]]:
You must enter the e-mail address of the PRI GSM gateway monitoring crew here.
E-mail subject [Test]:
The e-mail alarm subject will always be set to this entry.
SMTP server address [10.254.1.254]:
Please be sure to enter your mail server’s IP address (DO NOT USE YOUR MAIL
SERVER’S HOST NAME, THE RCU DOES NOT USE DNS).
You can select alarms that should be sent by e-mail. That procedure is described in section
Alarm filtering (4.1.10).
4.1.2 SMS alarms
Enable SMS sending? [YES]:
Answer yes (y) to enable alarm SMSs, no (n) disables this option
Destination phone number [[phone]]:
SMS recipients GSM phone number
MS Center number [[phone]]:
The provider’s SMS center number. (Note: Provider’s SMS center number is currently not
implemented, please set a valid SMS center in the selected SIM card.)
SMS0 gateway device number (or type '-' to disable it) [7]:
SMS1 gateway device number (or type '-' to disable it) [-]:
SMS2 gateway device number (or type '-' to disable it) [-]:
The PRI GSM gateway through which the SMS alarm is sent (one of 0 - 7 managed PRI GSM
gateways). Up to three different PRI GSM gateways can be used for this purpose. Typing “–“
disables the particular choice.
SMS0 module number [2]:
SMS1 module number [2]:
SMS2 module number [2]:
The GSM module from which the SMS alarm is sent, Three GSM modules can be set, they
must belong to the PRI GSM gateways selected above.
You can select alarms that should be sent as SMS messages. The procedure is described in
section Alarm filtering (4.1.10)
12

4.1.3 Call Data Records (billing)
The RCU collects Call Data Records (CDR) that contains all important information about
each call that has passed through PRI GSM gateway. These data could be used for billing
purposes. Configuration procedure in sgsetup gives you possibility to enable or disable this
collection for each managed gateway. It is enabled by default, but there are some situation
when it should be disabled. For instance, it must be disabled if the gateway at the same
time uses the SMS Callback Centrum application i.e. you must write Yin that case.
Disable billing from Gateway #0 ? [NO]:
You can find more details about CDR in chapter 5.3 Accounting and in your gateway
documentation.
4.1.4 The ASR statistics
The Answer to Seizure Ratio (ASR) is a statistical parameter used to express call success rate
in world of voice communications. Vendors of the related equipment use various definitions
of ASR. The RCU gives possibility to choose between two definitions. The following values
should be calculated for each SIM card, every 5 minutes according to calls made in that time
interval.
1. [∆(successfull calls) / ∆successfull calls + calls rejected by gateway + calls rejected by
GSM)] x 100
or
2. [∆(successfull calls) / ∆successfull calls + calls rejected by gateway + calls rejected by
GSM + calls dropped by calling party)] x 100
Answer to the following question (from sgsetup) decides which of two should be used
Calls dropped by calling party counted in ASR? [YES]:
If you answer N, the first formula is used. In other case, the second one. The calculated
values are presented through Web in SIM Card Statistics.
Two alarms(traps) are introduced in RCU ver. 2.0 to signalize important changes of ASR.
The first one (specific number 555) is sent when ASR falls under value defined as Low ASR.
The second one is sent when ASR is improved over value defined as Good ASR. These
values are set as response on the following sgsetup question
Low ASR [70]:
Good ASR [80]:
4.1.5 Utilization of PRI ports
The RCU checks every minute number of busy(active) B channels on both PRI ports. This
information is used to generate four traps related to high and low picks of traffic.
B channel high_up limit[29]:
13

B channel high_down limit[28]:
Trap 529 is sent when number of busy channels improves to value over high_up limit, and
trap 530 is sent when this value falls under high_down limit.
B channel low_down limit[3]:
B channel low_up limit[5]:
Trap 531 is sent when number of busy channels falls to value under low_down limit, and trap
532 is sent this number improves over low_up limit.
4.1.6 The PRI GSM gateways
At this stage, we configure the PRI GSM gateways to be managed by the RCU. For each PRI
GSM gateway, five parameters have to be configured as shown below. These five items have
to be repeatedly configured a number of times equal to the number of PRI GSM gateways.
The PRI GSM gateways are numbered from zero, so that, if for example we have eight PRI
GSM gateways, they will be numbered from 0 through 7. This same order will be used to map
the PRI GSM gateways to the different databases and storage tables. It is therefore mandatory
to maintain the same PRI GSM gateway numbering as the one that comes with the RCU CD.
ATTENTION: SWAPPING CPU CARDS BETWEEN PRI GSM GATEWAYS IS NOT
POSSIBLE BECAUSE INDIVIDUAL PRI GSM GATEWAYS ARE BOUND TO
THEIR DATABASES BY THE SERIAL NUMBERS OF THEIR CPUs!
THE RCU HAS BEEN TESTED TO WORK RELIABLY WITH UP TO EIGHT PRI GSM
GATEWAYS. MORE THAN EIGHT PRI GSM GATEWAYS CAN ONLY BE
CONFIGURED AT USER’S RISK.
Enable Gateway #0 ? [YES]:
Enter yes (y) to enable the first Gateway. If SNMP will be used to manage this Gateway then
it will be automatically bound to Eth0. No (n) disables Gateway #0
Enable Gateway LCR #0 ? [YES]:
Yes (y) switches on External Routing, No (n) turns it off
Enter Gateway #0 IP address or '-' [192.168.10.3]:
This parameter has a number of meanings. The first is that we choose the mode of
communication. By entering „-“(dash) we tell the RCU that it will communicate with PRI
GSM Gateway #0 through the serial ports (COM1 and COM2). Make sure that PRI GSM
Gateway #0 is connected to the RCU by serial cables (PRI GSM Gateway COM1 to RCU
COM1 and PRI GSM Gateway COM2 to RCU COM 2). Only one PRI GSM Gateway can
use this form of communication. If however, the RCU will use Ethernet to communicate with
PRI GSM Gateway #0 then this is the right place to enter PRI GSM Gateway #0’s IP address.
Enter Gateway #0 user name [2n]:
Enter Gateway #0 user password [2n]:
If Ethernet is enabled as above, it is mandatory to configure username and password. The
username and password entered here must be the same as the username and password
configured in the PRI GSM Gateway, it will otherwise reject telnet sessions from the RCU.
14

(Username and password are case sensitive!)
These same parameters must be repeatedly set for all the PRI GSM Gateways managed by the
RCU (#1 through #7). See the Example configuration in the next section.
4.1.7 Network Address Translation
A classical Network Address Translation (NAT) is applied here to map the SNMP IP
addresses configured on Eth0 (Eth0, Eth0:1, … Eth0:7) to the IP addresses of the PRI GSM
Gateways usually reachable from Eth1. This parameter can be safely turned off if SNMP will
not be used for management.
Enable network address translation? [YES]:
Yes (y) turns on NAT, no (n) turns it off
4.1.8 SNMP Configuration
IP address of SNMP agent #0: 192.168.20.100
Each managed PRI GSM Gateway has a separate SNMP agent whose task is to proxy the
specific PRI GSM Gateway to the network management node. Each of these SNMP agents
uses the IP addresses set on Eth0. See table below.
Interface Agent Gateway
Eth0 agent #0 Gateway #0
Eth0:1 agent #1 Gateway #1
Eth0:2 agent #2 Gateway #2
. . .
. . .
Eth0:n agent #n Gateway #n
Table2: Interface, SNMP agent and PRI GSM Gateway Mapping
Gateway #0 is automatically bound to Eth0, which is already configured. Gateways #1
through n have to be manually assigned SNMP IP addresses, these are the IP addresses made
for Eth0:1 through Eth0:n, n is the number of Gateways to be managed by the RCU minus 1,
the maximum value n can take is 7.
4.1.9 Binding PRI GSM Gateways to databases
PRI GSM Gateway CPUs are usually bound to the RCU databases before shipping. In this
case no additional binding is required. It may happen however, that the RCU and the PRI
GSM Gateways are shipped separately or that a customer decides to buy additional PRI GSM
Gateways and therefore pre-shipment binding is not done. This subsection is devoted to
binding PRI GSM Gateway CPUs to the RCU databases when this becomes necessary.
For each PRI GSM Gateway CPU that has not already been bound to a database in the RCU,
3 key codes are provided in the acompaning letter received with the RCU , Please prepare
these codes for each PRI GSM Gateway and follow the procedure below.
• Run “chcpusn”
15

bash-2.05a#
bash-2.05a# chcpusn
Enter number of database (0 7)
Pick a database for this PRI GSM Gateway, it must be free (not previously allocated to
another one).
Enter 1. string:
Enter the first key code for this PRI GSM Gateway
Enter 2. string:
Enter the second key code for this PRI GSM Gateway
Enter 3. string:
Enter the third key code for this PRI GSM Gateway
• Test database to PRI GSM Gateway CPU binding
bash-2.05a#
bash-2.05a# sgterm n “ati4”
The output of this AT command is the CPU serial number of the PRI GSM Gateway
bound to database number n (If we chose 5 in Enter number of database (0 7) above, then
use ‘sgterm 5 “ati4”’ to retrieve the CPU serial number for the database Stargate5 and
compare it with the one given in the acompaning letter).
4.1.10 External routing
Before external routing can be activated, the RCU has to be prepared for this. Please follow
the following steps to prepare the RCU for external routing.
• Edit the text file /var/local/stargate/routing_list.txt. This file comes with a default
configuration, which is usually not usable; please edit this file so that the first column
contains the list of dialed numbers. The second column must contain the target groups
through which the PRI GSM Gateway will route the calls. Use groups 1-8 for calls
that will be routed. Numbers that will be blocked should have 0 in the second column.
Be sure to follow the format in the default file.
• Run “sgrt”
bash-2.05a#
bash-2.05a# sgrt
This script uploads the contents of routing_list.txt in to the appropriate tables in the
routing database. Any duplicate entries are removed during this operation. Before you
consider using external routing, make sure you have a fast Ethernet connection between
the PRI GSM Gateway and the RCU.
4.1.11 Alarm filtering
Alarms (traps) sent by RCU could be divided, according to the severity of the reason that
provoked them, in four categories:
16

- critical
- major
- minor
- warning
All alarms with an advice of severity level are contained in The Trap Table (Appendix 1).
You can choose which alarms should be sent as SMS message and/or e-mail (if enabled in
sgsetup!). For this purpose is used file /etc/stargate-traps.conf, where is possible to give
severity level to each alarm(trap) and define sending rules for each severity level. Here we
have an example of its content.
501=warning
502=warning
503=critical
504=major
505=minor
511=major
512=minor
555=critical
556=warning
critical=sms,mail
major=sms,mail
minor=mail
warning=mail
The first part is a list of trap specific numbers (see. Appendix 1) with attached severity levels.
They could corespond to the advised ones in the Appendix 1, but also could be configured due
to users criteria. Traps not mentioned in the list will not be sent as SMS or e-mail at all. The
second part defines rules of sending SMS and e-mails dependant on the severity level. You
can configure it according to your needs.
4.2 Web access configuration
All the PRI GSM Gateways are now available on the web. Only authorized users can however
access this information. To be able to access the individual PRI GSM Gateways over the web,
we will need to create a web username and password for each managed unit. You are advised
to set the same username and password for all the PRI GSM Gateways to avoid errors during
automatic actualization.
bash-2.05a#
At the bash prompt, type ‘webpass’ to invoke the web password configuration script
bash-2.05a# webpass
Gateway num.:
Enter the PRI GSM Gateway Number (0 through n)
Username:
New password:
Re-type new password:
The username and password for the PRI GSM Gateway number set above.
17

This procedure has to be repeated n times to have all n gateways accessible over the web.
4.3 Testing
The first thing to do after configuration is to restart the PRI GSM Gateways services. This
forces them to re-read the current configuration files.
bash-2.05a#
bash-2.05a# service stargate restart
To troubleshoot the stargate service use the commands ”service stargate status “ and „sgconf“
for further information, see the example in the next section.
4.4 Configuration Example
Refer to Fig. 6
4.4.1 IP map Table
PRI
GSM
Gateway
PRI GSM Gateway
IP address
Interface Interface IP address Interface Use
SG0 192.168.10.2 Eth0 192.168.20.2 SNMP SG0, SSH,
SMTP, HTTPS
SG1 192.168.10.3 Eth0:1 192.168.20.3 SNMP SG1
SG2 192.168.10.4 Eth0:2 192.168.20.4 SNMP SG2
SG3 192.168.10.5 Eth0:3 192.168.20.5 SNMP SG3
SG4 192.168.10.6 Eth0:4 192.168.20.6 SNMP SG4
SG5 192.168.10.7 Eth0:5 192.168.20.7 SNMP SG5
SG6 192.168.10.8 Eth0:6 192.168.20.8 SNMP SG6
SG7 192.168.10.9 Eth0:7 192.168.20.9 SNMP SG7
Eth1 192.168.10.1 Telnet, HTTPS, SMS
Table3: IP address and protocol plan
Default gateway 192.168.20.1, Management Station 192.168.30.5
18

4.4.2 Configuration
Fig. 6: An example configuration.
bash-2.05a#
bash-2.05a# sgsetup
Enter current date [07.08.2003]: 09.08.2003
Sat Aug 9 00:00:00 CEST 2003
Enter current time [15:01]: 21.33
Sat Aug 9 21:33:00 CEST 2003
Date and time are updated.
eth0: IP address [192.168.100.100]:192.168.20.2
eth0: Netmask [255.255.255.0]: 255.255.255.0
eth0: Default gateway [192.168.100.1]: 192.168.20.1
eth1: IP address [192.168.10.2]: 192.168.10.1
eth1: Netmask [255.255.255.0]: 255.255.255.0
SNMP trap IP address (1) [192.168.100.3]: 192.168.30.5
SNMP trap IP address (2) [192.168.100.3]: 192.168.30.5
SNMP community [public]: Buster
Configuring network interface eth0 ...
Configuring network interface eth1 ...
Enable e-mail sending ? [YES]: y
E-mail 'FROM' address [[email protected]]: [e-mail]
E-mail 'TO' address [[e-mail]]: [email protected]
E-mail subject [Test]: Stargate watch
19