Professional Documents
Culture Documents
www.alphion.in
COPYRIGHT
Copyright © 2018 Alphion India Pvt Ltd.
AGEMS-NBI
TRADEMARKS
All of the Alphion names, brand names, and product names referred to in this Document, in particular, the
name “Alphion” and its logo, are either registered trademarks or trademarks of the Alphion India Private Ltd.
All other registered trademarks or trademarks are the property of their respective owners.
LIMITED WARRANTY
Alphion warrants that this Document has been delivered free of all rightful claims of any third person by way of
infringement or the like of any copyright, trade secret, or trademark. THIS DOCUMENT AND THE
PRODUCTS DESCRIBED THEREIN (COLLECTIVELY, THE “DELIVERABLES”) ARE PROVIDED “AS
IS” AND ALPHION MAKES NO OTHER WARRANTIES, EXPRESSED OR IMPLIED, AND DISCLAIMS
ANY AND ALL OTHER WARRANTIES WITH RESPECT TO THE DELIVERABLES, OR ANY
MODIFICATIONS THERETO, IN WHOLE OR IN PART, INCLUDING, WITHOUT LIMITATION, ANY
IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL ALPHION OR ANY ALPHION EMPLOYEE BE LIABLE FOR THE ACCURACY OR
COMPLETENESS OF THE DELIVERABLES.
EMS gives operators the view of selected sub-networks/rings controlled by the EMS.
By zooming-in or through user friendly GUI commands, the operators could drill down
up to the card level in each NE (network element) for configuration and fault
management. EMS could also drill down to the individual element, then to subsystem,
then to card and then to port level configuration template from the domain-map by
clicking on the icon of the network element.
Alphion also provides LCT (local craft terminal). Both Alphion LCT and central EMS
terminals can display:
Alphion EMS uses MySQL Database server for storing network element related data
along-with the log information and performance information.
EMS Server will be installed at the centralized NOC. The servers will be configured in
High Availability cluster mode. The EMS server will be installed at a DR site as well
which will also be configured in High Availability Cluster Mode.
AEMS Architecture
Alphion EMS adopts a client-server based architecture. The server component is based
on J2EE and the client is a Swing based thick client. The client communicates with the
server using RMI calls and JMS(Java Messaging System). JMS communication is used
to pass messages such as traps, events and EMS messages to clients asynchronously.
The client makes use of RMI calls to communicate with the server.
The high level AEMS architecture is captured in the block diagram below.
Figure 1: AEMS Architecture
The AEMS client is a Java Swing based thick client which encapsulates the user
interfaces to perform various operations related to the Network element as well as to the
EMS. All FCAPS functionality is supported by the EMS client. User friendly menus
and interfaces are exposed to users for efficient and easy usage.
The server tier runs in the JBOSS application container. It contains the following sub
elements:
South-Bound Interface
North-Bound Interface
South-Bound Interface
Communication between the EMS server and the Network elements is handled by this
layer. SNMP(Simple Network Management Protocol) is used as the primary means to
retrieve and sent information from the EMS to the Network element(s). TFTP/FTP
protocls are used to send/retrieve files from the Network elements.
North-Bound Interface
The north bound interface layer consists of CORBA componenets which aid in
communication with Network Management Systems(NMS). The North bound interface
is developed based on the TMF814 standards. The North bound interface components
talks to the South-Bound interfaces and EMS Core components to perform tasks
requested by the NMS systems.
Scheduling tasks
Database operations
High availability of the AEMS system is achieved using Operating system level
clustering. The AEMS Software is deployed on multiple servers which in turn has
redundant hardware modules. The database is deployed on a central storage which is
configured using RAID. This ensures that data is available in case of disk failures.
To counter situations where a complete data centre has to be taken offline or goes
offline due to conditions like power and ups outage or a flood or fire, then the AEMS
system can also be setup at a disaster recovery(DR) site. The configuration at the DR
site, if kept similar to the primary site, will make the AEMS application highly available
at the DR location as well.
The block diagram below describes the various components and the bonding of a
AEMS high availabilty setup.
Figure 2: AEMS High Availability components
A Storage device
The storage device is also selected with an aim to provide inbuilt failover capabilities.
Dual power supply, dual controller configurations, storage capacity and RAID are the
main considerations when selecting a storage device.
The AEMS server software resides on each of the EMS servers. The database files
reside on the storage device. RAID configurations are used to preserve data on the
storage device to ensure that failure of any single disk does not stop end users from
performing their regular operations.
The servers are connected to the storage device with fibre cables. Multiple fibre channel
paths are defined on each server connected to the storage using multipathing software.
This enables the server to parallelize operations to improve performance or to select
alternate paths in case of failure of any one path.
The servers are interconnected to each other with multiple network cables for the
heartbeat cluster mechanism.
Clustering software is installed on both the servers and cluster and resource group
configurations are made. Logical IP cluster configurations are done so that the EMS
clients can connect to the EMS server using a single IP address and clients need not be
aware of the underlying configuration.
Realtime database replication is setup among the database applications on the primary
and the disaster recovery locations. In case of a failure at the primary location, the
application on the active DR node is started manually. Clients can connect to the DR
location and continue with regular operations.
The DR location IP address would be different from that of the primary location. Hence
clients should be aware of the secondary IP address in this case.
Use Case Id 1
Use Case Id 3
Use Case Id 5
Use Case Id 7
Use Case Id 8
Use Case Id 1
All use cases from the “Primary Cluster Use cases” section will also be applicable for
the DR location.
Technical Specification for EMS server & Client for
100,000 ONTs and 1000 OLTs
SL.
No. Description Requirements
1 Server Hardware Qty: 2
2 Processors with 32
a Processor Cores each, 4.13 Ghz
SPARC T7-2 (Preferrable/Other
vendors can also be selected if
b Server Model/Family desired)
c RAM 256 GB
d HDD 600 GB * 4
1. Clustering has been deployed at BSNL separately for 2 different zones. This
includes two Primary setups and 2 Disaster recovery setups.
2. Clustering has also been deployed at MTNL Delhi with only a Primary setup(as per
requirements).
3. Database: MySQL
3. Database: MySQL
3. Database: MySQL
3. Database: MySQL
4. OS: Sun Solaris 10, Solaris Cluster Suite.