ElementCenter Feature List

Architecture

 

Modeling

  • Data Models shared with devices to maintain accurate and consistent common object schema.
  • Built in processors for SNMP MIBs and NETCONF YANG models.
  • Enhancement model allows tailoring the device model for management without over-writing it.
  • These models drive the systems that provide a number of value-add services, such as code-generation, automatic validation and auto-UI creation.
  • System can accommodate different versions of each device model, to enable multi-version device management.
  • New models can be introduced in an installed system, without requiring a recompile or upgrade. All relevant artifacts are automatically re-generated at system start up.
  • Supplemental models enhance the data models to support model driven Configuration GUI, Database support, Online help, Device Communications and Service APIs.

 

Modules

  • ElementCenter is designed as a set of modules that interface to one another via well-defined APIs.
  • Adding functionality (either to the core system) or to a customizable product is as simple as adding one or more modules.
  • A Device module provides the means to manage and communicate with a specific type of device.
  • An Application (or Service) module provides functionality to the system that allows it to span multiple devices or enhance the system’s behavior by extending the core .
  • Any Module corresponds to a bundle which is composed of models (which provide the metadata), code (which contains the business logic) and resources (such as icons, web pages and strings).

 

High Availability

  • ElementCenter processes are monitored by a watchdog to  ensure resilience to process termination.
  • Runs as native platform service that automatically restarts upon system startup.
  • Multiple systems can be installed in an Active-Standby configuration with automatic fail-over and fail-back.
  • Use of shared IP address ensures consistent external access to system.
  • HA-aware GUI rides through fail-overs without user interruptions.

 

Messaging

  • Messaging infrastructure for internal components and module.
  • Clients can subscribe by message type, action and/or object type
  • Decouples components facilitating modular, plug-and-play construction.

 

Persistence

  • System comes bundled with PostgreSQL, providing performant and reliable database functionality.
  • Can be tailored to support other Relational Databases using simple plug-in mechanism.
  • Sample plug-ins for other databases (SQL Server, MariaDB) provided.
  • Uses Hibernate (and JDBC)  for persisting Java objects.
  • No database code needs to be written – all artifacts required for Hibernate are automatically generated based upon the models.
  • System provides a set of libraries (including a canonical Query API) that allows any code in the system to quickly and effectively access the database.
  • System provides a backup/restore utility that can be used for disaster recovery (or in multi-server configurations)

 

Licensing

  • System provides support for licensing on on a per-installation basis.
  • Licenses can be tied to hardware aspects of the system so that they are not transferable between systems..
  • Specific features can be licensed individually (i.e. features can be turned on or off based upon the license).
  • A license can control resource access/scale – e.g. it can restrict the maximum number of concurrent users.
  • Public-private keys and encryption are used for license management, so as to maintain high level of security.
  • Licenses can be timed to expire, with every feature having a post-expiration value, so that the system can run in a degraded state, if necessary.

 

Security

 

AAA

  • Built-in rich EMS security model with user/group management.
  • Permissions can be assigned based upon devices, actions or configuration object type.
  • Security groups can configured for permissions across collections of devices.
  • Permissions can be dynamically introduced into the system by modifying the XML Service models.
  • System provides integration with external LDAP and RADIUS AAA servers.

 

Audit

  • All relevant user-initiated operations are audited by the system.
  • Operations are audited consistently, regardless of how they are initiated – via the GUI or though the north-bound interfaces.
  • Every audit record contains detailed information information – such as the operation, the user, source machine they are logging in from, time to execute and success status.
  • The set of auditable operations can be controlled using meta-data in the service model.

 

External Integration

 

SOAP/REST

  • Rich and easily extendable Northbound interfaces allows ElementCenter systems to participate in service orchestration.
  • Interfaces are automatically generated using the data and services models.
  • Programmer API documentation automatically generated for quick reference.
  • Provides a north-bound interface that lets external applications (such as OSS/BSS systems) control the EMS/NMS as well as the devices it manages.
  • Applies the same controls as a GUI-based user to provide a consistent security framework.

 

SNMP

  • System can be configured as an SNMP agent which can be managed by an external SNMP manager.
  • Can be configured as an SNMP trap sender to send notifications as traps to external systems.
  • Allows product to implement custom MIB support for system.

 

LDAP/RADIUS

  • Users can be authenticated through external LDAP or RADIUS servers.
  • User permissions can be specified in LDAP/RADIUS attributes, or default permission groups.
  • Security accounting provided for RADIUS servers.
  • Flexible LDAP schema and RADIUS attribute support.

 

Device Protocols

 

NETCONF

  • NetconfX Native Java Client for NETCONF provides communications to NETCONF-based devices.
  • Automatic marshaling and un-marshaling of Java objects driven by the common Yang model (shared with the device).
  • Provides support for configuration and notification standards (RFC 6241 and 5277).
  • Provides framework to enable device-wide as well as network-level transactions.
  • Dynamically adjusts to device capabilities.

 

SNMP

  • Native Java Client for SNMP provides communications to SNMP-based devices.
  • Supports SNMP versions V1, V2c and V3.
  • Automatic marshaling and un-marshaling of Java objects driven by the supported device MIBs.
  • Provides handling of traps/notifications from devices.

 

ENEA Element (XML-RPC)

  • Native Java Client provides XML-RPC based communications to devices running the ENEA Element embedded manager.
  • Provides supports for management of configuration as well as operational data.
  • Includes session and transaction support as provided by ENEA Element.
  • Provides handling of notifications from devices.

 

Other

  • Well-defined APIs allow a developer to plug in proprietary protocols for device communications.
  • System can act as a Syslog server – with support for RFC 3164 and RFC 5424.
  • Built-in libraries provided for many standard additional protocols – hH, SCP, FTP, HTML.

 

User Interface

 

Rich GUI

  • Browser-based UI – zero client install or administration, not even a plug-in is required.
  • Implemented using GWT to provide rapid development with support for all major browsers.
  • Includes support for iPad devices.
  • Provides the user an “application” like experience from within in a web page.
  • Dynamic update functionality to display the latest status and state of network and device components.
  • Provides support for HTTP and HTTPS.

 

Topographical Map

  • Provides Drag and Drop ability in a browser using GWT.
  • Allows the use of unlimited nested sub-maps that are mirrored in a device tree.
  • Supplies a Link Manager maintain and manage links and link state using colored lines.
  • Redundant and multiple links supported through clickable links.
  • Supports Alarm roll-ups – alarms that are generated by a device in a sub- map are automatically propagated up the hierarchy (or tree) to the highest level.
  • Automatically manages context across the map, tree and menu options (device-specific toolbar and device view) on the main screen.
  • Multiple Views allow creation of as many topographical maps as necessary.
  • Views can be shared between users and locked against changes.
  • Map resources (such as map icons, background images, colors) can be customized as well as tailored by end-users on a per-install basis.
  • Provides framework for Right-Click menus on all icons to configuration, status, and other customizable functionality.
  • Provides support to use Google Maps in lieu of built-in topographical map system.

 

Graphical Device View

  • Allows the programmer to quickly build a dynamic device view using the device view framework.
  • Provides dynamic view of a device components state with components reflecting alarm or other conditions.
  • Provides roll over pop-up info for quick views of components.
  • Context menus on each component provide quick access to status, statistics, or configuration.
  • Views can offer multiple “perspectives” for the user to choose, to support muli-chassis devices, or viewing of the front and back of a device.

 

Application GUI Framework

  • Enables rapid creation of common Application user interfaces without resorting to direct GWT or Web programming.
  • Supplies a rich set of UI widgets to dramatically improve programmer productivity.
  • Supports generic tables that automatically provide filtering, server side pagination, sorting and exporting to CSV files.

 

Device Management

 

Configuration

  • Configuration screens are automatically generated form the device model to provide out-of-the-box configuration without additional coding.
  • Automatic screens can be enhanced and new screens defined using a GUI model to supplement device data model.
  • Configuration system honors permissions, which can be assigned per config object type.
  • Screens containing status fields are updated dynamically by a configurable refresh mechanism.
  • System provides an offline configuration mechanism which enables users to create and store any number of configurations for a device within the EMS.
  • Device configurations can be stored in an offline backup, to be reapplied at future points in time.
  • Offline configurations can be maintained for template data that can be uploaded to multiple devices across a network.

SSH

  • Built in SSH terminal enables device SSH sessions in browser window
  • SSH sessions tunneled to target device through the ElementCentere sever to enable accessing devices behind firewalls.

Upgrades

  • System provides a framework to handle software/firmware upgrades on a device.
  • To support a new device, all the developer needs to do is provide a plugin for the specific device type.
  • Provides Image Management to upload images from the client to the device image library.
  • Allows scheduling of upgrades to run at times of minimal network impact.
  • Supplies Upgrade Status screens to monitor progress of currently running updates as well as old jobs.
  • Support multi-device upgrade operations so that devices can be upgraded as a group at the same time.

 

Files

  • Provides a framework for file management on devices.
  • Each device type can support any number of file types to manage.
  • Allows downloading files from devices and staging them on the EMS server, to be brought down to the client.
  • Allows uploading files from clients to stage on the EMS server, and thereon to the devices.
  • Provides UIs and handling for life-cycle management of staged files.

 

Log storage/viewing

  • Provides a framework for collecting and storing logging data from devices.
  • Permits storage of Log data in CSV files, that are automatically aged out after a configured amount of time.
  • Supports viewing of collected log data by scanning CSV files such that they can be filtered by date – typically used for viewing on-device debug/trace information.

 

Service Orchestration

 

  • System defines an Application or Service Module Framework that allows a developer to provide application-level or service-level functionality.
  • Application modules can work across multiple devices of different types to provide end-to-end functionality, such as service-level orchestration and provisioning.
  • Application Modules supply modeling, services and permissions in addition to business logic.
  • Built-in support for global transactions allows application modules to perform atomic transactional operations across multiple entities within the system.
  • Application Modules have access to all internal components such as the alarm system, messaging system, configuration  framework and all device controllers.
  • Application Modules can expose their service functionality to the north-bound SOAP/REST interface – this allows external systems to provision and control a Service as part of a larger application.

 

Monitoring

 

Event/Alarm System

  • Event System logs events from Devices (e.g. SNMP or NETCONF) and the EMS itself.
  • Events API allows code in any subsystem to  generate event notifications triggered by any other mechanism.
  • Events can be viewed as a running log in real-time, or as historical events stored in the database.
  • Historical Events can be filtered and searched using standard search methods.
  • Multiple Event types supported including Alarm, Config, State, and custom types
  • Alarm Correlation is based on Alarm Events – Alarms raised and cleared based upon (customizable) severity.
  • User Configurable Alarm Rules allow user to create Alarm Events for any event type.
  • Alarm Summary displays count of alarms active and/or unacknowledged.
  • User Configurable Alarm Overrides enabled a user to control alarm clearing, severity, etc.
  • Alarms can be forwarded as traps to external (trap-based) systems using a NorthBound SNMP agent.
  • Alarm status of devices and objects are visible throughout user interface – config tables, map, device views.
  • Map /tree icons reflect most severe alarm status of contained devices and links in a rolled-up fashion.
  • Events and Alarms are automatically aged and archived into CSV files to control storage space.

 

Performance (Statistics)

  • System provides a declarative statistics system – with collection behavior based upon device and system data models.
  • Statistics classes are automatically generated from the data models (Yang/Yin and MIBs for devices).
  • Binning system available to collect data on periodic minute boundaries, automatic deltas optionally configurable.
  • EMS Performance values enables monitoring of system parameters – e.g. database requests, Alarm activity, message processing, resource (CPU/memory) usage and more.
  • Alarms can be generated (set and cleared) on statistic threshold value transitions.
  • Line Graphing of historical statistics and bar graphing of running stats generated automatically.
  • Historical performance data is automatically aged out and archived for controlled storage.

 

Platforms

  • Runs on Red Hat Enterprise Linux, CentOS, Windows server and Solaris 10 (on SPARC).
  • Comes bundled with installation/upgrade utilities for all supported platforms.
  • Runs as an installed service and can be managed using the platform’s native service management framework.