INAS

Element Management System

Operation Guide
Part 1. Introduction
Introduction Operation Guide
INAS EMS
2



























Copyright 2012 DASAN Networks, Inc.
Issued by Technical Documentation Team
Korea
Technical modifications possible.
Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

Operation Guide Introduction
INAS EMS
3
Contents of Update
Issue No. 1.0
Chapter/Section Reason for Update
All Initial release

Issue History
Issue
Number
Date Update
Issue 1 11/2012 Initial release

Introduction Operation Guide
INAS EMS
4
Contents
1 Overview .............................................................................................. 5
1.1 Control Centralization ............................................................................ 5
1.2 Roles-based Discovery of Devices ........................................................ 5
1.3 Polling/Listening .................................................................................... 6
1.4 TMN (Telecommunication Management Network) Recommendations ... 6
1.5 EMS & NMS Detail Feature Concept ..................................................... 7
1.6 Operation Support Systems (OSS) ........................................................ 8
1.7 High Availability ..................................................................................... 9
2 Network Architecture ........................................................................ 10
3 Software Architecture ....................................................................... 11

Operation Guide Introduction
INAS EMS
5
1 Overview
The Integrated Network Administrator System (INAS) Element Management System
(EMS) is a comprehensive network management system with an intuitive graphical user
interface. Service providers can optimize network usage, reduce operating costs and
implement new services quickly and easily.
The INAS EMS is designed to meet the demanding operating and security requirements
of large operators while delivering the same benefits to mid-size and smaller services
providers. The Dasans EMS allows you to control your network to efficiently discover
your network, roll out new equipment, provision and activate services, as well as
diagnose key issues. It provides subscribers with progressive service levels, value adding
premium services such as Virtual LANs and intuitive auto-provisioning capabilities, robust
policy settings.
Using IP-based management for network discovery in real-time, the EMS detects network
failovers, and helps to monitor and maintain a stable network environment. It also
provides the real-time fault management and configuration for all SNMP available nodes,
and displays the status of their port, slot and power.
1.1 Control Centralization
The INAS EMS's control is centralized by an INAS EMS Server and one or more Clients.
The Server has capability to perform management and monotoring of numbers of nodes
(equipments), and allows one or more Clients to access itself, and stores configurations
and informations in a connected database. The following is a sample structure of
controlling nodes through INAS EMS. The figure below shows the diagram of control by
access to INAS EMS Server via INAS EMS Client.

1.2 Roles-based Discovery of Devices
Especially, the INAS EMS performs roles-based discovery process when it discovers
devices on the network, which helps determine the type of device based on the device
attributes. The device roles do two things: specify the criteria that a device must match to
be identified as the device role; and specify the monitoring configuration that is applied to
the device when it is added to INAS. After devices are discovered, you can add them to
the INAS database and view monitored devices as a list of devices or as a graphical map.
Introduction Operation Guide
INAS EMS
6
1.3 Polling/Listening
The INAS EMS actively polls devices to determine their status. Performance monitors
track device performance by checking and reporting on device resources, such as CPU
and interfaces.
1.4 TMN (Telecommunication Management Network)
Recommendations
There are five management layers defined in TMN: Business Management Layer, Service
Management Layer, Network Management Layer, Element Management Layer, and
Network Element Layer. The INAS EMS implements the functionalities at the Network
Management Layer and Element Management Layer as the figure below shows.

The INAS EMS implements the FCPS functions of the Element Management Layer and
ensures the Network Management Layer functionalities and the management of the
services and functions provided by each node. The node management system and
network management system are integrated seamlessly together to provide complete
services for users.
The major NML functions of INAS EMS are:
- The discovery performs network scans to identify network devices and the role each
device performs on the network.
- The INAS EMS can configure map, or create other device groups and configure maps
for these groups as you see fit.
- Shows status of network link lines.
The figure below shows the details of functionalities on Network Management Layer,
which are supported by Dasans EMS.
Operation Guide Introduction
INAS EMS
7

The major EML functions of INAS EMS are:
- Configuration Management: Management of equipment configuration, card configuration,
service configuration, Ethernet port configuration.
- Fault Management: Management of current alarms, alarm history and alarm attributes.
- Performance Management: Collection and reporting of performance data; supports the
daily, weekly, monthly and yearly historical graph to get the system resources utilization.
- Security Management: Establishment of user accounts with specific access rights and
tracking of account activity.
1.5 EMS & NMS Detail Feature Concept
EMS Feature
System Management
- Upgrade, Backup/Restore, Hardware, SFP, DMI, SSH, Login, Time, System, Slot
Management
- Alarm, LED, SNMP, Syslog, RMON
Bridge
- Filter, LAG, Security, Port, QinQ, STP, VLAN
Multicast & QoS
- IGMP, Snooping, MVR, Flow, Class, Policer, Policy
GPON
- OLT, ONU, Profile (Traffic, ONU, DBA, PM, MC, VoIP, TDM), Extended VLAN
NMS Feature
Configuration
- NE Discovery, Node (Virtual), Group, Model, Topology
Fault
- SNMP Trap Define, Alarm Window/Sound, Real-time Event, Severity, Effect
Performance
- Traffic/CPU/Memory Monitoring, Day/Week/Month/Year Report
Security
- User, Group, Authority, License Policy

Introduction Operation Guide
INAS EMS
8
1.6 Operation Support Systems (OSS)
The INAS EMS can be integrated in external operation support systems (OSS) via a
northbound interface (NBI). The online interface on INAS EMS is open CORBA. If you
require not only fault management integration but also the option of managing the
network elements directly from the OSS, you must use the CORBA interface of INAS
EMS. With the CORBA interface, it is possible to provide service provisioning, service
assurance and inventory data management to an external OSS. The CORBA interface of
INAS EMS is defined in accordance with TMF 513/608/814 specifications.


Operation Guide Introduction
INAS EMS
9
1.7 High Availability
The INAS EMS provides a scalable NMS depending on the network size and designed
architecture as required by the customer. The cluster on the server is used together with
the 3rd-party products, to build an infrastructure for high availability at site. It restarts
applications in response to a variety of hardware or software failures. The redundancy
mechanism is the most prevalent for providing HA through application failover.


Introduction Operation Guide
INAS EMS
10
2 Network Architecture
Various OS Support (Solaris, Windows)
RDBMS DB Support (Oracle)
Framework (Client & Server Framework)
Supports All Features as Plug-in type
Various Libraries including Dasans own Library
Supports Active Standby Redundancy (third-party) with Multiple Servers and External Storage
Northbound Interface (CORBA)
IP-based Management via Gigabit Ethernet Interface of Switch


Operation Guide Introduction
INAS EMS
11
3 Software Architecture
Framework name: Motive (based on JAVA Language)
High-Modular, High-Flexibility
Enables to do Low Customization
Reduces Development Term
Distributed Processing