SilentKnight System IP traffic patterns and network integration highlights - Manual (Page 7)

6
ANNEX: ARC BANDWIDTH DIMENSIONING
In this section we are going to analyze the mIP/IPDACT-VisorALARM system traffic. This analysis should
be used as a basis in order to size the IP communications in the alarms reception center.
The incoming and outgoing IP traffic in the VisorALARM depends on:
• The number of mIP/IPDACT devices being served. Each VisorALARM is capable of
managing up to 3000 mIP/IPDACTs. In High-availability ARC setups, a Backup
VisorALARM is added, but the limit of 3000 mIP/IPDACT accounts is kept.
• The poll time (i.e. the keep-alive time interval) configured in the mIP/IPDACT. The
minimum configurable poll time is 10 seconds. More traffic is generated with a shorter poll
time.
• Alarms sent by the mIP/IPDACT modules.
• Traffic generated by the configuration synchronizations between the VisorALARM devices.
If we fix the poll time to the minimum configurable value of 10 seconds, we can estimate the maximum
throughput required for the ARC IP service:
umber of
mIP/IPDACT
Incoming traffic in the
VisorALARM
Outgoing traffic from the
VisorALARM
500 600 Kbps 550 Kbps
100 950 Kbps 900 Kbps
1500 1300 Kbps 1250 Kbps
2000 1700 Kbps 1650 Kbps
2500 2100 Kbps 2050 Kbps
3000 2500 Kbps 2450 Kbps
Chart 1. Maximum ARC throughput as a function of the amount of served mIP/IPDACT’s
The poll time in UL-listed mIP and IPDACT devices is limited to a minimum of 90
seconds, complying with UL specifications.
The values in Chart 1 were measured assuming a traffic pattern of a typical ARC, where 55% of the IP
traffic corresponds to user alarms, 35% corresponds to account supervision and the rest is used for the Main
and Backup VisorALARM Data Base synchronization in High Availability scenarios. The traffic
breakdown is illustrated in Chart 2.