Teldat VisorALARM PLUS 2U User manual

VisorALARM
PLUS 2U
Installation Manual
Doc. DM374-I Rev. 1.0
May, 2007

- ii -
INDEX
CHAPTER 1 INTRODUCTION...........................................................................................................................1
1. VISORALARM PLUS 2U INTRODUCTION ...................................................................................................2
2. INSTALLATION SCENARIO.............................................................................................................................3
3. OPERATING MODE........................................................................................................................................6
3.1. Monitoring ..........................................................................................................................................6
3.2. Sending of Alarms...............................................................................................................................7
4. ADDITIONAL FEATURES................................................................................................................................9
5. CONFIGURATION AND MANAGEMENT ........................................................................................................10
CHAPTER 2 INSTALLATION ..........................................................................................................................11
1. INTRODUCTION ...........................................................................................................................................12
1.1. General installation conditions.........................................................................................................12
1.2. Connection ........................................................................................................................................14
1.3. Switching on the device.....................................................................................................................17
CHAPTER 3 CONFIGURATION......................................................................................................................19
1. INTRODUCTION ...........................................................................................................................................20
2. COMMON CONFIGURATION .........................................................................................................................21
3. CHANGING THE IP PROTOCOL CONFIGURATION.........................................................................................25
4. CONFIGURING THE NTP CLIENT.................................................................................................................26
5. ARLY ALARM RECEPTION INTERFACE .......................................................................................................28
5.1. Alarm Receiver..................................................................................................................................28
5.2. Communicating with the Automation Server ....................................................................................30
5.3. Communication parameters with the printer....................................................................................30
5.4. Communicating with the mIP/IPDACTs...........................................................................................31
5.5. Network Backup Parameters ............................................................................................................31
5.6. Maintenance Receiver.......................................................................................................................33
5.7. User Configurable Events.................................................................................................................33
5.8. Configuration pattern .......................................................................................................................34
5.9. Upload/Download operation ............................................................................................................37
6. FINAL ADJUSTMENTS .................................................................................................................................40
7. EXAMPLE....................................................................................................................................................41
CHAPTER 4 APPENDICES................................................................................................................................57
1. TROUBLESHOOTING....................................................................................................................................58
2. CONNECTING THE CONNECTORS .................................................................................................................59
2.1. LAN1/LAN2 connections (RJ45).......................................................................................................59
2.2. AUT/PRN Connectors.......................................................................................................................59
2.3. VisorALARM Expansion Card Connectors.......................................................................................60
2.4. AUX port Connections ......................................................................................................................61
3. TECHNICAL SPECIFICATIONS ......................................................................................................................61
4. UL COMPLIANCE INSTALLATION ................................................................................................................63
4.1. Requirements prior to installation....................................................................................................63
4.2. Installation requirements..................................................................................................................64
4.3. Configuration requirements..............................................................................................................65
5. ALARM PRINTING FORMAT .........................................................................................................................68
6. AUTOMATION SOFTWARE...........................................................................................................................69
6.1. Frame formats...................................................................................................................................69
6.2. SIS Software......................................................................................................................................71

Chapter 1
Introduction

VISORALARM - Introduction
I - 2 Doc.DM374-I
Ver. 1.0
1. VisorALARM PLUS 2U Introduction
The IP VisorALARM PLUS 2U receiver (Model VisorALARM PLUS 2U) isacommunications
device developed by Teldat for security environments. The IP VisorALARM PLUS 2U receiver’s
principal task is to receive alarms over an IP network and to subsequently send them to an automation
software (SwAut). The functionality of the Teldat VisorALARM PLUS 2U is similar to any other
alarm receiver which receives alarms over the telephone line.
The IP VisorALARM PLUS 2U receiver operates together with the IP Module (mIP/IPDACT), which
receives the alarms from the alarm control panels and sends them to the Teldat VisorALARM PLUS
2U over an IP network. Additionally, the Teldat VisorALARM PLUS 2U monitors connectivity with
all the registered mIP/IPDACTs. Should connectivity fail then the VisorALARM PLUS 2U generates
alarms to the SwAut.
The VisorALARM PLUS 2U IP receiver has the network backup functionality added, which permits
an mIP/IPDACT the possibility of IP backup towards another IP receiver. The main (or primary)
receiver and the backup receiver are always synchronized at the configuration level.
The VisorALARM PLUS 2U is supplied with adisplay and akeypad in order to validate the signals
received and monitor the device. The VisorALARM PLUS 2U includes interfaces to connect to an
Automation Software and to a printer.
The user can access to the device configuration through an asynchronous serial data connection by
using aserial terminal emulator. The configuration is atext level and permits the copy/paste
functionality.
Figure 1. VisorALARM PLUS 2U 2U Receiver

VISORALARM - Introduction
I - 3 Doc.DM374-I
Ver. 1.0
2. Installation Scenario
Atraditional security scenario consists of acontrol panel (CP), located in the client environment and
an alarm receiver center (ARC) located in the security company’s control center. The CP contains a
group of sensors which trigger a series of alarms or events which, when produced, are sent to the ARC
to be processed.
Communication between the above is traditionally carried out over the telephone line so that both ends
can initiate acall to the remote end: the CP in order to notify events and the ARC for bi-directional
tasks (activation, teleloading and general control).
Public Telephony
Switched Network
Alarm
Control Panel
Client
Alarm Receiver
Sur-Gard/Radionics Automation SW
IBS/ MAS/MicroKey
Fax
Alarm Receiver Center
Figure 2. Traditional security scenario
The communication protocol varies depending on the manufacturers who usually tend to use their own
solutions.
The CP is placed as the first connection element to the PSTN so that it can prioritize the customer’s
telephone line.
Within the general user scenario, the device in question is located in the client area, next to the control
panel, intercepting the telephone line. This is displayed in Figure 3. The arrow in the figure
demonstrates the preferred path to send alarms from the CP; in aBurglary application (using mIP
devices) the telephone line is used as abackup in case there is acommunication malfunction in the IP
network. In a Fire Application (using IPDACT devices) a second telephone line is used as a backup.

VISORALARM - Introduction
I - 4 Doc.DM374-I
Ver. 1.0
Figure 3. Teldat VisorALARM PLUS 2U and mIP/IPDACT operating scenario
There is athird scenario, thanks to the network backup functionality. In the previous scenario, if
communications between the IP Module and the VisorALARM PLUS 2U fails, the former tries to
send the alarms over the telephone network, as in atraditional scenario. Network backup permits you
to add a second VisorALARM PLUS 2U configured as backup and which would be a second option of
sending alarmsin cases where the main VisorALARM PLUS 2U fails. If the probe over the main
fails, the mIP/IPDACT (from release 2.2 onwards) tries to establish communications with the backup
VisorALARM PLUS 2U. If this is achieved, the mIP/IPDACT will maintain the probe with latter and
sends the alarmswhich are produced. In the meantime, the mIP/IPDACT continues to poll the main
VisorALARM PLUS 2U until this becomes accessible once more. At this point the mIP/IPDACT
returns from backup and reestablishes all the communications with the main VisorALARM PLUS 2U.
In cases where the backup VisorALARM PLUS 2U also fails, the mIP/IPDACT will release the
telephone line so that the control panel, from this point, will take over and directly sends the alarms.

VISORALARM - Introduction
I - 5 Doc.DM374-I
Ver. 1.0
It’s advisable that the VisorALARM PLUS 2U devices have different gateways and different Internet
access servers to ensure efficient network backup.
Figure 4. Operating scenario with network backup

VISORALARM - Introduction
I - 6 Doc.DM374-I
Ver. 1.0
3. Operating Mode
The IP Mode (mIP/IPDACT) connected to the client control panel carries out two tasks:
1) Capture the alarms sent by the control panel and send them over the IP network to which it is
connected. These alarms are then received by the Teldat VisorALARM PLUS 2U in order to
be sent to the corresponding automation software (SwAut).
2) Generate monitoring traffic so that both ends of the security environment check the IP
connectivity, as it is this that permits the above task to be carried out.
3.1. Monitoring
The mIP/IPDACT is adevice that intercepts the control panel telephone connection with two aims:
firstly to detect when the panel sends an alarm in order to capture it and retransmit over the connected
IP network and secondly to allow the telephone line to be used at the same time as sending alarms.
The interception of the telephone line takes place ONLY in cases where connectivity with the Teldat
VisorALARM PLUS 2U has been verified. The mIP/IPDACT - VisorALARM PLUS 2U connectivity
is checked through atraffic monitor which the mIP/IPDACT periodically sends and to which the
Teldat VisorALARM PLUS 2U responds. If this exchange of messages does not occur during the
configured time, the mIP/IPDACT tries to resend. If, after aconfigurable number of attempts
(between 1and 9),asatisfactory response is not received, the connectivity is presumed lost. The time
between polling messages is programmable between 0and 90 seconds, atypical value being 15
seconds. The time between retries is also configurable, between 3 and 9 seconds.
If anetwork backup scheme is running, the mIP/IPDACT has asecond IP receiver to establish
communications and send alarms. If this second receiver does not respond to the communication
established with it by the mIP/IPDACT (again after aconfigurable number of attempts), the telephone
line access is returned to the control panel as if the mIP/IPDACT is no longer operative at the alarm
level. Fromthis point on, the mIP/IPDACT will try to re-establish communications with both the
main Teldat VisorALARM PLUS 2U as well as the backup, if there is one. As soon as this is re-
established with either of the two VisorALARM PLUS 2U, the mIP/IPDACT will once more intercept
the telephone line.
The monitoring traffic is encrypted UDP traffic. The Ethernet frame size does not exceed 70 bytes.
The monitoring interval, the number of retries and time between retries are all configurable, both for
the main VisorALARM PLUS 2U as well as for the backup. The time between retries is an important
parameter as it influences the global traffic supported by the VisorALARM PLUS 2U (polling over all
the devices). You also need to bear in mind that polling is atool to control the state of both the alarm
reception center and the mIP/IPDACT. Along interval between polls can give rise to situations where
the VisorALARM PLUS 2U delays in detecting aproblem with the mIP/IPDACT and consequently a
problem in aclient. Finally, if the mIP/IPDACT accesses Internet via adevice which executes NAT,
traffic coming from the VisorALARM PLUS 2U (configuration for example) will not reach the
mIP/IPDACT if the period between polls is inferior to the outgoing router NAT tables refresh time (a
typical refresh value is 5 minutes).
The Teldat VisorALARM PLUS 2U received monitoring messages from the mIP/IPDACTs. If these
are registered, they are assumed alive and an acknowledgement response is sent to them;if the
mIP/IPDACTs are not registered, they are ignored. Periodically the status of all the registered
mIP/IPDACTs is checked and an alarm is generated for all those which have not notified their
availability (i.e. those which have not responded since the last check). This is a 350 code alarm from
the Contact-ID protocol (Communication trouble)which is received inthe SwAut. From release
10.1.27 onwards, the event code is configurable. Default is 350. As each mIP/IPDACT can have a

VISORALARM - Introduction
I - 7 Doc.DM374-I
Ver. 1.0
different polling time with the center, the VisorALARM PLUS 2U checks the status of each
mIP/IPDACT starting with the polling time value for all of them.
In order to prevent the Teldat VisorALARM PLUS 2U from sending hundreds or thousands of
communication failure alarms when faced with asituation of general failure of IP traffic reception, the
device itself monitors the network access through ICMP echo packets (ping) to a known address: if the
echo packets towards this address fail then a code 356 alarmis generated from the Contact-ID protocol
(Loss of central polling). From release 10.1.27 onwards, the event code is configurable. Default is
356.
Apart from the previous codes, the Teldat VisorALARM PLUS 2U with network backup functionality
generates other codes that do not directly correspond with those pre-established by the CONTACT-ID
protocol. These have default values which can be changed via the console.
Aseries of these codes are grouped indicating the states the VisorALARM PLUS 2U passes through.
The device configured as main on startup sends a396 restore code indicating that the device is active.
The device configured as backup must send code 398 restore code indicating that the device is active.
Once the main and backup VisorALARM are connected by polling, the main device sends a358
restore code to indicate the backup device is up and the backup device sends a399 restore code to
indicate the main device is up. Both the main and the backup VisorALARM PLUS 2U can have
communication problems (Loss of central polling) and consequently pass to a down state sending code
event 396 for main and 398 for backup. If the backup device detects communication failure with the
main device it will assume that as it cannot communicate with the VisorALARM PLUS 2U then nor
will the mIP/IPDACTs. The backup will then activate sending a 399 event code (Primary
VisorALARM is down) and the mIP/IPDACT polls should go to this device. Lastly, the main
VisorALARM PLUS 2U can detect and indicate through a358 code that the polls fromthe backup
VisorALARM PLUS 2U are not reaching it and consequently there is aproblemeither with
communications with the backup or with the main VisorALARM PLUS 2U device itself.
In addition to the above codes, we need to add a further two which provide information over particular
cases. If in the mIP/IPDACT configuration there is an error where the main address is in fact the
backup address, all communications from this mIP/IPDACT will be routing to the backup. The
backup device, through a395 code, will indicate this error by sending the code after each two
programmed keep-alives have been executed. The second case indicates asituation where an
mIP/IPDACT in backup is polling the backup device but this latter is not active, consequently there is
acommunication error between the mIP/IPDACT and the main VisorALARM PLUS 2U. This
problem is indicated with a 394 code.
3.2. Sending of Alarms
When the mIP/IPDACT has connectivity with the Teldat VisorALARM PLUS 2U, the former
intercepts the telephone line and processes all the incoming and outgoing calls taking place fromthe
alarm panel.
The supported alarm sending protocol is Contact-ID. This format sends alarms through DTMF digits
complying with the following format:
AAAA MM QEEE GG CCC S
where AAA is the client number, MM the type of message, Qan event qualifier, EEE the type of alarm,
GG the group or partition number, CCC the zone number and lastly Sis the frame validation digit.
When the panel opens to send an alarm, the mIP/IPDACT provides power and emits the dialing tone.
When the control panel dials the alarm center telephone number, it issues the Contact-ID handshake
and receives the alarm frame. From this point, the mIP/IPDACT sends this alarm to the
VisorALARM PLUS 2U.

VISORALARM - Introduction
I - 8 Doc.DM374-I
Ver. 1.0
The control panel is not given the frame sent acknowledgement (kissoff)until the said
acknowledgement is received from the automation software. Ifthe mIP/IPDACT does not receive the
acknowledgement within 2seconds, this carries on resending aconfigured number of times (between
5and 10), after which connection with the Teldat VisorALARM PLUS 2U is assumed lost. As in the
case of supervision where the alarm send fails, this can be sent again this time to the backup
VisorALARM PLUS 2U if this functionality is configured. If communications also fail with the
backup then the control panel sends the alarm over the telephone line. Fromthis point, the
mIP/IPDACT tries to re-establish communication with the two VisorALARM PLUS 2U as previously
described.
The IP VisorALARM PLUS 2U receiver on receiving an alarm from an mIP/IPDACT stores this in a
non-volatile internal memory. When the operation has successfully finished, it sends the
acknowledgement to the mIP/IPDACT originating the alarm so that this in turn sends to the associated
control panel. If the alarm storage memory cannot store the alarm, no acknowledgement is given.
As regards the SwAut, the Teldat VisorALARM PLUS 2U behaves as an alarm receiver that sends
alarms received through aserial port. The Teldat VisorALARM PLUS 2U can emulate aSur-Gard, a
Radionics 6500 receiver or an Ademco 685. The serial line parameters are configurable as well as
those relative to the emulated receiver (link-test, receiver and line identifier, start and end frame
characters, etc.)

VISORALARM - Introduction
I - 9 Doc.DM374-I
Ver. 1.0
4. Additional Features
In order to simplify installation and updating of the registered mIP/IPDACTs, the IP VisorALARM
PLUS 2U receiver has additional facilities.
To install new mIP/IPDACTs, the Teldat VisorALARM PLUS 2U possesses configuration patterns
associated to installer passwords. These permit you to automatically register new mIP/IPDACTs in
the supported mIP/IPDACT list and at the same time enable the mIP/IPDACT to request the necessary
configuration for start up. The device can simultaneously have multiple patterns; the choice of one or
other depends on the installer password used in the mIP/IPDACT to request the service.
From release 10.1.27 onwards, when anew mIP/IPDACT is registered an event is generated and sent
to the automation software. The code for this event is configurable, default being 633 (Module
Added).
In order to maintain and update the registered mIP/IPDACTs base, the Teldat VisorALARM PLUS
2U has commands available to remotely update one or multiple configuration parameters used by the
mIP/IPDACTs.

VISORALARM - Introduction
I - 10 Doc.DM374-I
Ver. 1.0
5. Configuration and Management
The IP VisorALARM PLUS 2U receiver can be configured and monitored through a local console and
also remotely (telnet). In both cases, the access is restricted to users who are identified by a user name
and a password. The configuration is displayed in text mode consequently editing and support in other
platforms is simpler and more comfortable.
There are three types of users with different privilege levels to gain access to the configuration:
1. Manager: This sort of user can change the configuration and monitoring.
2. Supervisor: This user can only change the day and the time configuration and has total access
to the monitoring.
3. Operator: This user can only access the monitoring.
The default login and password for the manager user is “manager/24680”.
The VisorALARM PLUS 2U is supplied with adisplay and keypad. The display is the means through
which the user can access the signal information. The signals can be validated by using the keypad.
For further information on using the keypad and the information showed on the display, please see
manual “VisorALARM Operating Instructions”.

Chapter 2
Installation

VISORALARM - Installation
II - 12 Doc.DM374-I
Ver.1.0
1. Introduction
The IP VisorALARM PLUS 2U receiver is designed to be both adesktop and arack device. In either
case, in order to achieve correct installation, please follow the recommendations given below:
BEFORE CONNECTING THE DEVICE PLEASE READ THE FOLLOWING
INSTRUCTIONS CAREFULLY.
1.1. General installation conditions
Conditions
Bear in mind the following recommendations:
1. If the installation is UL listed, install the device in a19” rack or box with alocking rear
access door.
2. Excessive cold and heat should be avoided, as should humidity and dust. Direct exposure to
sunlight should be avoided as well as other heat sources. The device should not be placed
amongst papers, magazines or other elements that could hinder natural air circulation.
3. The device should not be placed very close to strong electromagnetic fields such as speakers,
engines, etc.
4. Knocks and/or strong vibrations should be avoided during transport, operation and storage.
Power supply
The VisorALARM PLUS 2U device does not require special conditions as regards voltage stability or
protection against power malfunctions as it is already protected.
To avoid electric shocks, residual current circulation and other unwanted effects, also affecting
communications, the following is recommended:
•It is highly recommended that all interconnected communication devices be plugged
to THE SAME GROUNDED POWER OUTLET, which should at the same time be
of good quality (lower than 10ohms).
•Whether the workplace is provided with an uninterrupted power supply system
(UPS), regulated supply or it is independent from the rest (such as lighting, etc.); it
is highly recommended that all data devices should be connected to the same power
source. This will avoid operating and premature aging problems of drivers and
other components.
•For UL listed installations the device must be installed in an Alarm Central which is
UL Listed where an independent generator provides uninterrupted power supply to
all the equipment. It is also necessary to connect an uninterrupted power system to
the device which permits it to carry on operating for at least 15 minutes.

VISORALARM - Installation
II - 13 Doc.DM374-I
Ver.1.0

VISORALARM - Installation
II - 14 Doc.DM374-I
Ver.1.0
Figure 5. 19” rack installation and device power connections
WARNING: Electric supply current, telephone and communication cables are dangerous. To
prevent electric shock while installing, moving or opening the device covers, cables should
be disconnected and connected as follows:
To connect the VisorALARM PLUS
2U To disconnect the VisorALARM PLUS 2U
•Make sure that the device power supply
switch is OFF. •Switch off the device.
•Connect all the data cables. •Disconnect the power supply cable.
•Connect the power supply cable. •Disconnect the data cables.
•Switch on the device.
1.2. Connection
a) LAN Ethernet connection
The device has two Ethernet 100baseT LAN interfaces to connect to the IP network.This LAN
interface has afemale RJ45 connector in order to connect to the Ethernet 10BaseT networks through a
shielded twisted pair (STP) or unshielded (UTP) cables. These cables are not supplied with the
equipment; please consult your supplier with regard to this.
Depending on the design of the Network, the connection is carried out through aHUB or directly to
another terminal device Ethernet interface through acrossover cable (please consult your supplier for
information on crossover Ethernet cables).
When the VisorALARM is connected to the Ethernet through the LAN1 connector, the LED on the
front panel labeled LAN1 will light up in green. If there is no connection, the LED will light up in red.
The same thing will happen with the other LAN2 Ethernet connector. Please note that in the factory
configuration only the LAN1 connection is configured.
IMPORTANT: For UL listed installations it is mandatory to connect the VisorALARM
ethernet interface to the ethernet building installatation through the device ESD-100
ethernet data line protector (Alerton Technologies, UL listed UUKL.S8105).
b) Connecting to the alarm server
Data connection to the alarm automation server is carried out through the serial interface labeled AUT
in the device. This serial interface complies with the V.24 norm, behaves as DCE and has afemale
DB25 connector. You need to use a DB25 male serial cable to a DB9 female in order to connect to the
server.
IMPORTANT: Do not use a null modem cable.
When the VisorALARM is connected to the Automation Server, the LED on the front panel labeled
AUT will light up in green. If there is no connection, the LED will light up in red.

VISORALARM - Installation
II - 15 Doc.DM374-I
Ver.1.0
c) Connecting the printer
Connection to the printer is carried out through the serial interface labeled PRN in the device. This
serial interface complies with the V.24 norm, behaves as DCE and has a female DB25 connector. You
need to use a DB25 male serial cable to a DB9 female in order to connect to the printer.
IMPORTANT: Do not use a null modem crossover cable.
WARNING: in UL Listed Installations, always use a UL Listed printer.
When the VisorALARM is connected to aprinter, the LED on the front panel labeled PTN will light
up in green. If there is no connection, the LED will light up in red.
d) VisorALARM Expansion Card
The VisorALARM PLUS 2U is supplied with three slots where three VisorALARM Expansion Cards
can be plugged in (Labeled as VA-UD in the rear panel). The device is supplied with one VA-UD in
the factory configuration.
The following figure shows the VA-UD connectors:
Figure 6. VA-UD Connectors
•Connectors COM1 and COM2
The data connection to Uploading/Downloading Software is carried out through these two connectors.
The serial interface complies with the V.24 norm, behaves as a modemand has afemale DB25
connector. At the same time two separate data connections can be made for each VA-UD.
•Connector I/0
The following figure shows the arrangement of the connector outputs and inputs.
VA
-
UD

VISORALARM - Installation
II - 16 Doc.DM374-I
Ver.1.0
Figure 7. Arrangement of inputs/outputs in ConnectorI/O (VA-UD)
The two outputs are relays with arated voltage of 30 volts CC and arated amperage of 2A CC. The
relays are normally open.
qOutput1: This output is dedicated for watchdog indication.
qOutput2: This is a general purpose output. The factory configuration for this output is to close
the relay in cases where some unrestored trouble alarm s(3XX CONTACT-ID code) exist with
account 0, i.e., an trouble alarm signaled by the VisorALARM and not restored.
The two inputs have RS-232 levels (-12V/+12V, -12V input inactive, +12V input active).
qInput1: This is ageneral purpose input. The factory configuration for this input is to detect a
failure in the AC main signaled by a UPS device.
qInput2: This is ageneral purpose input. The factory configuration for this input is to detect a
low battery signaled by a UPS device.
e) Configuration connection
The IP VisorALARM PLUS 2U receiver routers have afemale DB-9 connector in the rear panel
referred to as “AUX”which provides access to the device local console for configuration and
monitoring purposes. In order to use this, you must connect to the “AUX”port to an asynchronous
terminal (or to a PC with terminal emulation).
COM
Toprevent electric shock,
donot remove cover.
CAUTION!
100-240 V~;1-0.5 A
47-63 Hz
∼
AC INPUT
WAN 1 AUX.
SLOT 1
Computer

VISORALARM - Installation
II - 17 Doc.DM374-I
Ver.1.0
Figure 5. Connection for configuration/monitoring via console
The configuration of the terminal must be:
- Speed: 9600 bps
- Eight data bits
- No parity bit
- One stop bit
- No type of flow control
Also expressed as 9600 8N1. The connection to the configuration port can be carried out with DB-9
female-DB-9 male cable provided with the equipment. In cases where the asynchronous terminal has
DB25 connectors, you must use an additional DB9F-DB25F adapter (not included with the
equipment).
1.3. Switching on the device
Once the device has been installed in the workplace following the steps previously given, you can
switch on the device. Once this has been carried out, aprocess of auto-test and initialization,
explained below, takes place.
Firstly, the device carries out abrief auto-test where it checks that the startup program is correct and a
brief detection and initialization of the SDRAM present in the device. If any problems are detected
the process stops and the TRB LED flashes in red. Once this process has completed, the console is
available and begins to show data.
Once the booting process has terminated, an auto-test and auto-detection test of the motherboard
hardware takes place. If the test is successful the TRB LED remains green. If any malfunctions are
detected, the corresponding LED remains lit up in red and once the auto-test has completed, depending
on the problem, the device resets and repeats the process or permits you to operate through the console
in order to resolve the problem. (Note that once the VisorALARM is running, if the device has
unrestored System Trouble Signals the TRB LED remains lit up in red while these signals remain
unrestored).
Once the firmware decompression process is completed the application executes, the configuration is
read and the access login is displayed.
If you have aterminal or aPC with terminal emulation connected to the device console, booting
information similar to that shown below can be displayed:

VISORALARM - Installation
II - 18 Doc.DM374-I
Ver.1.0
**************************************************
**************************************************
**************************************************
BOOT CODE VERSION: 01.10 Oct 30 2006 17:17:43
gzip Oct 30 2006 17:08:44
P.C.B.: 75 MASK:0A01 Microcode:0070
START FROM FLASH
BIOS CODE DUMP.....................
BIOS DATA DUMP....
End of BIOS dump
Boot-stack used: 0x00000788
Boot-stack free: 0x00001878
BIOS CODE VERSION: 01.10
CLK=294912 KHz BUSCLK=65536 KHz PCICLK=32768 KHz L1
Date: 11/20/06, Monday Time: 17:28:05
SDRAM size: 128 Megabytes
BANK 0: 128 Megabytes (detected)
I_Cache: ON
D_Cache: ON Write-Back
FLASH: 16 Mb.
NVRAM: 128 Kb.
EEPROM: 2048 Bytes.
DPRAM: 16384 Bytes.
WAN1: DCE
WAN2: DCE
ISAC
RDSI_B
RDSI_B
FAST ETHERNET 1
FAST ETHERNET 2
PCI device: Host bridge
(Bus: 0, Device: 0, Function: 0)
(Subs. Vendor: 0x0000, Subs. Device: 0x0000)
Slot 1 - PCI device: bridge
(Bus: 0, Device: 10, Function: 0)
(Subs. Vendor: 0x5444, Subs. Device: 0x2301)
Current production date: 06 05
Current software license: 6 120
Current serial number: 472/05898
BIOS MAC Add: 00-a0-26-70-17-0a
>>
........
TRYING APP CODE DUMP
(CONFIGURED) cit.bin ver.: 0.10.6.27 0.0.0.0 ................................
................................................................................
.........................................................................
APP DATA DUMP...................................................................
............
Bios-stack used: 0x1498
Bios-stack free: 0x2B68
Aux-stack used: 0x124
Aux-stack free: 0x1EDC
Running application
Flash configuration read
Initializing
Press any key to get started