BCS MWR Product Management

Alarm Converter System Technical Description and Specification

CODE: ISSUE/UPDATE: VERSION SOURCE:

TD-310806-1 July 2009 2.1 COO BCS MWR Product Management

BCS MWR Product Management

Index
Index..............................................................................................................................2 Introduction....................................................................................................................3
Scope......................................................................................................................................................3 Related Documents................................................................................................................................3 Revision Information..............................................................................................................................3

System Overview...........................................................................................................4 Main Functionalities.......................................................................................................5

Input Station Alarms..............................................................................................................................5 Output Station Alarms............................................................................................................................5 Communication between Remote Alarm Converters .............................................................................5 Alarm remotization scenarios................................................................................................................7

Management................................................................................................................10
Fault management................................................................................................................................10 Local history log..................................................................................................................................10

Security........................................................................................................................11
Access..................................................................................................................................................11 Accounting log.....................................................................................................................................11

Synchronization ..........................................................................................................11 Ports used for communications with NMS..................................................................11 Technical Specifications..............................................................................................13
Mechanical data...................................................................................................................................13 Power consumption..............................................................................................................................13 External interfaces...............................................................................................................................13
Power Supply interface.........................................................................................................................................13 I/O interfaces........................................................................................................................................................13 Ethernet interface.................................................................................................................................................14 RS-232 interface..................................................................................................................................................14

Environmental conditions....................................................................................................................14 Electromagnetic compatibility.............................................................................................................15

BCS MWR Product Management

Introduction
Scope Scope of this document is to give an overview of Alarm Converter appliance focusing on architectural aspects and main features. Related Documents For a complete description of the available features for each Software Version Release please refer to the latest version of Customer Feature List and Customer Release Note

Revision Information The here listed configuration and feature are related to the last SVR released. Issue 1.0 2.0 2.1 Date August 2006 November 2006 July 2009 Author BCS MWR PLM BCS MWR PLM BCS MWR PLM Notes First Issue Revision Revision with TCP/UDP ports to be opened

BCS MWR Product Management

System Overview
Alarm Converter is a device which collects 24 external alarms and provides 24 output commands. The Alarm Converter, 1/2 U high, adopts a monolithic architecture, consisting of a single replacement unit, supplied with dedicated brackets suitable for assembly in 19" or ETSI N3 racks. On the front panel the following connectors are present: - 1 sub-D 3W3 connector for the -48V power supply - 1 RJ-45 connector for the Ethernet interface (Q interface) - 1 sub-D 9 connector for LCT interface (F interface) - 1 sub-D 25 connector for the 24 inputs - 1 sub-D 25 connector for the 24 outputs A dual-color LED (green/red) is available on the front panel to indicate power On/ Card Fail condition.

UH
LCT (RS-232) Q-LAN (10/100BaseT) 24 OUPUT Alarms 24 INPUT Alarms Power Supply (-48V DC)

Figure 1- Frontal Panel At application level, the interface towards the NMS (Network Management system) is provided by a SNMP agent, whereas the interface towards LCT (Local Craft Terminal) is provided by a HTTPS server.

Alarm Converter
Alarm Converter database

NMS

LCT

SNMP manager

SNMP agent UDP IP

HTTPS server TCP

HTTPS client

SNMP v2 Ethernet

HTTPS

Figure 2- Alarm Converter Management Applications and protocol stack

BCS MWR Product Management

Main Functionalities
Input Station Alarms
Alarm Converter collects 24 external alarms, called Station alarms. Each station alarm is associated to a fixed Alarm ID (from 1 to 24) which identifies the alarm wire position. The status of 24 input lines and each station alarm variation is notified to NMS and/or to a remote Alarm Converter via Ethernet interface (Q) through DCN (Data Communication Network). User customizes each station alarm by setting the following parameters via LCT:

Name Polarity (ground/floating: input physical level when the alarm is active) Severity (Critical, Major, Minor, Warning, Indeterminate) Destination: alarm notifications can be sent alternatively to NMS, to a remote Alarm Converter or to both of them according to LCT setting. IP destination address of the remote Alarm Converter receiving the station alarm.

Output Station Alarms

Alarm Converter provides 24 output lines, called output commands. Each output command can be forced to a fixed value by LCT (as telecommand) or can remotely report a station alarm input issued by a remote Alarm Converter. Each output command is associated to a fixed Command ID (from 1 to 24) which identifies the output command wire position. For each output command the following parameters are available via LCT:

Name Polarity ( ground/floating: output physical level when the alarm is active) Source (LCT or Remote Converter).

Communication between Remote Alarm Converters

Communication between remote alarm converters uses a proprietary protocol over TCP/IP (connection oriented: safe alarm transfer is guaranteed by TCP). TCP connection status is monitored by LCT.

BCS MWR Product Management

Source Alarm Converter sends a message to the remote appliance only when there is a station alarm input variation (when no alarm variations occur only TCP keep alive messages are sent). Up to 48 connections are be managed, 24 for station alarms and 24 for output commands. Source Alarm Converter sends to Destination Alarm Converter not all alarm notifications but only those associated by configuration to that specific remote appliance.

BCS MWR Product Management

Alarm remotization scenarios

Alarms are collected through the dedicated pin of the alarm port; each station alarm variation is sent via Ethernet interface (Q) through DCN towards NMS and/or towards one or more remote Alarm Converter devices, which restitute them through the output command interface. DCN network is used as IP transport network: it routes IP packets received by the Alarm Converter ignoring the content of IP packets Alarm Converter can be connected to the DCN through the QLAN interface of SRAL XD/SRA 4 (also VLAN port of SRAL XD can be used). Different examples of appliance scenarios concerning Alarm remotization are shown in the following figures.
SRAL XD/ SRA4 V/QLAN
MICROWAVE DCN Network

SRAL XD/SRA4 V/QLAN

SRAL XD/ SRA4 V/QLAN INPUT ALARMS

ALARM CONVERTER

OUTPUT ALARMS

ALARM CONVERTER

SITE C
INPUT ALARMS
ALARM CONVERTER

SITE A

SITE B
Figure 3: Alarms Remotization from site A, B to site C

The connection between Nodes A, B, C in Figure 3 represents the remotisation of station alarms from one site to another site. The alarms that are collected on one site (A, B in the picture) can be remotised to another site (C in the picture). This kind of application could be used, for example, in networks where station alarms are always collected by the Alarm Board of a BTS/Node B (or other apposite devices): in those sites where the Alarm Board is not present (Node A, B in the picture) the alarms are collected and transported towards the nearest NodeB/BTS in the network (Node C) and they are restituted by the remote Alarm Converter through output commands.

BCS MWR Product Management

SRAL XD/ SRA4 V/QLAN

MICROWAVE DCN Network

NMS
ALARM CONVERTER INPUT ALARMS Figure 4: Remote Management via IP DCN

In Figure 4, alarm converter is configured in order to notify the alarms to NMS only.

NMS

SRAL XD/ SRA4 V/QLAN

MICROWAVE DCN Network

SRAL XD/SRA4 V/QLAN

SRAL XD/ SRA4 V/QLAN INPUT ALARMS

ALARM CONVERTER

OUTPUT ALARMS

ALARM CONVERTER

SITE C
INPUT ALARMS
ALARM CONVERTER

SITE A

SITE B
Figure 5: Alarms Remotization from site A, B to site C and to NMS

In Figure 5, Alarm Converters of sites A and B are configured in order to notify the alarms to NMS and at the same time to remotize them to site C through another alarm converter. Summarising, the following configurations for alarm transfer are available:

BCS MWR Product Management

remotisation to an alarm converter notification to NMS remotisation to an alarm converter and notification to NMS

BCS MWR Product Management

Management
Fault management
Alarm Converter is fault monitored by NMS (via SNMP traps over UDP/IP protocol) and LCT (via HTTPS server in the embedded SW). Alarms are classified as: Physical Alarm type, when an HW failure occurs (substitution of the unit is required). Card fail is the only Physical alarm (Critical). Functional Alarm type, which brings to loss of functionality. Time server missing is the only Functional alarm (Minor). Station Alarm type: the configurable alarms are collected via 24 input lines. In the LCT window, there is a summarized status indication for each severity: each indication is red if at least one (or possibly) more alarms with the corresponding severity are active. Multiple indications can be red at the same time. In the communication towards NMS, severity is sent within the trap for each station alarm separately. An example of LCT Alarm window is shown in the figure.
Alarm Collector Alarms Physical Alarms Card Fail Station Alarms 1 Alarm Name

Functional Alarms ! Time server Missing 24 Alarm Name

Figure 4 -LCT Alarms window

Local history log

BCS MWR Product Management

This feature supports the visualization of the recent history of the appliance on a WEB page on LCT. More than 4000 events (Alarm state changes) are recorded and visualized.

Security
Access
Alarm Converter configurations can be modified only by LCT, whose access (via HTTPS) is protected by encrypted user and password. Three classes of users are foreseen: Administrator, Read/write and Read/only. NMS users have only Read Only privileges.

Accounting log
This feature supports the visualization of the list of users which have accessed LCT recently. A list of up to 120 records relevant to LCT log actions (login or logout) performed by users is stored in non volatile memory. Such information is available uploading a file via FTP.

Synchronization
When an alarm arises a SNMP TRAP is sent to NMS including an Alarm Id and time stamp field. System clock is synchronized to the network clock in order to provide the time stamp synchronous with the NMS clock. NTP is the protocol used to support Alarm Converter synchronization. If NTP is disabled, Alarm Converter date and time can be manually configured by LCT.

Ports used for communications with NMS

The following ports need to be opened on the DCN network (e.g. on routers or firewalls) between Alarm Converter and NMS: Application SNMP v2 HTTPS server FTP server Proprietary Peer-to peer connection Application SNMP v2 - Trap Local Listening Ports 161/UDP 443/TCP 21/TCP (control) -20/TCP (data) 49160/TCP Remote Listening Ports (on server) 162/UDP

BCS MWR Product Management

NTP client Proprietary peer-to peer connection

123/UDP 49160/TCP

BCS MWR Product Management

Technical Specifications
Mechanical data
Height Width Depth Weight 22mm 442mm 115mm ~1kg

Power consumption
The maximum power consumption in Watt [W] over the whole operational voltage range is 3W (typical) and 3,5W (guaranteed).

External interfaces
Power Supply interface
Connector type: sub-D-3W3, 3 poles, with golden power pins

Electrical definition Input voltage range (A3 pin relative to A1 pin) Abnormal voltage range (high level) Automatic power-up voltage (low level) Automatic shutdown voltage (low level) Protection against reversal of battery polarity -38,4V -57,6V -57,6 V -72V -37,5V 0,5V -36,5V 0,5V yes

I/O interfaces
Connector type: Electrical definition Input lines OPEN criterion CLOSED criterion Output lines Sub-D 25 poles with golden contacts.

-3V +2V voltage to ground with 60k series -3V +2V voltage to ground with 200 series

BCS MWR Product Management

OPEN criterion Potential negative/positive to ground (from external source) Max. voltage 72V Max. sinking current 0,1 mA CLOSED criterion Potential negative/positive to ground (from external source) Max. voltage 72V Max. continuous current 60 mA Residual voltage (on the contact) 2V

Ethernet interface
Connector type: regulations) RJ-45, 8 poles, gold plated finishing ( according to FCC 68

Bit rate: 10/100Mbit/s autosensing Connections 100 balanced Connector: RJ45

10BaseT Electrical interface: IEEE 802.3 Bit-rate 10Mbit/s Line coding: Manchester 100BaseT Electrical interface: IEEE 802.3u Bit-rate 100Mbit/s Line coding: MLT3

RS-232 interface
Bit rate: 38.4Kbit/s Electrical interface: V.24 (RS-232 C) Connector: Sub-D 9pin with golden contacts

Environmental conditions
Environmental conditions along with the relevant maximum temperature range are reported in the following table. Location ETSI Cla Max Temperature range Recommenda ss

BCS MWR Product Management

tion Stationary use Transportat ion Storage EN 300 019-13 EN 300 019-12 EN 300 019-11 5C +55C with guaranteed performance; 10C +60C with no permanent damages 40C +70C 40C +70C

3.2 2.3 1.3

Electromagnetic compatibility
Compliant with Emission and Immunity requirements according to EN 301489-1, EN 301- 489-4 and EN-61000-4.