Centered Logic, LLC
 Network and Element Management Systems and Solutions

ElementCenter 3.2

ElementCenter is an EMS platform and developer framework based on popular open source and proprietary technologies. ElementCenter provides EMS developers with a collection of critical EMS components and functionality such as Alarms, Events, Configuration, and EMS administration. ElementCenter provides 80% of the functionality that your system needs, so your team can focus on developing the functionality that is unique to your system.


At the heart of ElementCenter is a modeling and code generation system. ElementCenter shares a data model with the device it's controlling. It can consume many versions of the device model for many device types. ElementCenter uses the models to drive not only the device communications, but also the internal data objects, configuration screens, status objects, and historical statistics. As a result, EMS systems based on ElementCenter are reliable and accurate, and developing one requires a fraction of the effort required by "coding by hand".


ElementCenter is a modular system that can can be enhanced to communicate with devices over open or proprietary protocols. Out of the box, ElementCenter 3.2 supports popular device protocols including SNMP, NETCONF, SOAP and XML/RPC.


The 3.2 Release of ElementCenter provides many new features, and enhancements and optimizations to current popular features..


Event Processing
The event system now uses time sharded database tables to provide unprecedented performance and reliability. Additionally, the platform can now warehouse orders of magnitude more records than previously possible.


NETCONF
Our NETCONF client (netconfX) has been enhanced to support more RFCs including.


Solaris Support
Solaris has been added as a supported platform.


Graphical Device View
A new Graphical Device View framework has been added that supports multi-perspective device views. Users can choose to look at the front or back, or other perspectives of a device.


Enhancements
At the request of our customers, Release 3.2 provides enhancements and refinements to many existing features including the Topographical map, alarms summary, main screen, modeling system and others.




ElementCenter 3.2 Feature List

Modeling System

  1. XML model shared with devices to maintain accurate common object schema
  2. System can accommodate different versions of each device model, to enable multi version device management.
  3. Enhancement model allows modifying the device model without over-writing it.
  4. 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.
  5. Supplemental models enhance the main data model to support model driven Configuration GUI, Database support, Online help, Device Communications.
  6. The primary model drives the system that provides a number of value-add services, such as code-generation, automatic validation and auto-UI creation.

 

NETCONF Support

  1. Centered Logic’s NetconfX Native Java Client NETCONF interface provides communications to NETCONF devices.
  2. Object2Netconf layer driven by the common Yang/Yin model from the device
  3. Support for configuration and notification RFCs.
  4. NetconfX client provides device-wide and network-level transactional support.
  5. Built in SSH layer provides security.

 

SNMP Support

  1. Native Java Client SNMP interface provides communications to SNMP devices (using the SNMP4J SNMP stack)..
  2. Object2SNMP layer driven by the common device model as defined by the MIBs supported by the device.
  3. Support for traps/notifications from devices.

 

Web 2.0 GUI

  1. Zero client install or administration
  2. ElementCenter’s User Interface is implemented using GWT - the latest Web 2.0 technology from Google
  3. Provides the user an “application” like experience right in a web page.
  4. No client administration, nor even browser plug-in required.
  5. Dynamic functionality to display the latest status and state of network components.
  6. HTTP and HTTPS support

 

Topographical Map

  1. Drag and Drop ability in a browser using GWT
  2. Create submaps that are also represented in the device tree
  3. Link Management
  1. Link Manager keeps track of links and link state
  2. Link State visible on map through colored link lines
  3. Redundant and multiple links supported through clickable links
  1. Link table shows all links between two linked objects including alarm LED to show link state.
  1. Alarm Rollups - Alarms that are in a submap are propagated up the tree to the highest level
  2. Multiple Views
  1. Create as many topographical maps as necessary
  2. Shared between users
  3. Lockable
  1. Right Click Menus on icons link to configuration, status, and other functionality
  2. Editable Map Details
  1. Upload and specify custom map icons
  2. Set Custom background images and colors
  3. Icon and image management system which allows customer to upload and manage their own images and backgrounds.
  1. Tight Integration between Tree and Map as well as context driven components in the main screen.
  1. Clicking an icon in the Tree will open the map and select the icon in the map.
  2. Clicking on an icon in the Map will select the icon in the tree.
  3. A selected icon in either the tree or map will propagate the Device Specific Toolbar and Device View.

 

Application GUI Framework

  1. Enable fast creation of common Application GUIs with out GWT or Web programming
  2. Tables automatically support filtering, server side pagination, and sorting
  3. Export to CSV support on any table.

 

SOAP Interface

  1. Automatically generated using the common model used for all aspects of the system, including the Web GUI
  2. Based on objects defined in DDM/EDDM and interfaces specified by the Service Model.
  3. Effectively provides a north-bound interface that is fundamentally driven from the device model (Yin/Yang, SNMP)

 

Configuration System

  1. Configuration screens automatically generated form the device model
  2. Screens can be enhanced using a GUI model to supplement device data model
  3. Permissions can be assigned per config object type
  4. Status fields and screens are updated dynamically by configurable refresh
  5. Offline config system enables user to create and store configuration for a device offline
  6. Device active configuration can be stored in an offline backup
  7. Offline config data can be uploaded to many devices.

 

Graphical Device View

  1. Quickly build a dynamic device view using the device view framework
  2. GWT Web 2.0 device view provides dynamic view of device components state
  3. components reflect alarm or other states
  4. device view provides roll over pop-up info
  5. Context menus on each component provide quick access to status, statistics, or configuration of each component.
  6. 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.

 

Security System

  1. Complete GUI form managing EMS security provided
  2. Permissions can be assigned per device, or even per configuration object type
  3. Security groups are configured for permissions across collections of devices
  4. Users can belong to one or many security groups.
  5. Users can also log in through AAA system such as LDAP

 

Event/Alarm System

  1. Event System logs events from both Devices and the EMS itself
  2. Events can be raised through Notifications
  1. Netconf Notifications
  2. SNMP Traps
  1. Multiple alarm event types supported.
  1. Config Events - A configuration has occurred, what object was configured
  2. State Events - Something interesting has occurred
  3. Alarm Events - An event has occurred which needs to be looked at
  4. Other types can be defined if the current set is not sufficient
  1. Alarm Correlation based on Alarm Events
  1. Alarms raised and cleared based on severity
  1. Alarm Rules
  1. Rules allow user to create Alarm Events for any event type.
  1. Could create a rule to raise an alarm when a configuration has changed
  1. Alarm Summary
  1. How many alarms have been raised that have not been acknowledged
  2. Counts per severity allows administrator to see that important alarms are raised
  3. Alarm Summary Table is once click away from Alarm Summary Widget
  1. Alarm Overrides
  1. Allows an administrator to take automatic action on an alarm
  1. Automatically clear
  2. Automatically acknowledge
  3. Change the severity of alarms being raised
  4. Can be for a single device or for the entire network
  1. Allows for ability to change or define the Recommended Actions sections of the Alarm Details
  1. Alarm forwarding
  1. Alarms can be forwarded as traps to external (trap-based) systems,
  2. Traps so generated can be customized for the product.
  1. Alarm system supports maintenance mode
  1. The device will still be configurable but will not raise alarms.
  1. Event/Alarm system archival
  1. Archives into CSV files
  2. Archive file management purges old archive files
  1. Alarms integrated into many components in the system
  1. Config Tables - Config objects can display alarm leds to show highest alarm state of object
  2. Map
  1. Device Icons show highest level severity using Alarm LED
  2. Alarm Rollups on Map and Submaps
  3. Links Show alarm state through color
  1. Link Table available to show which links are down
  1. Alarm LEDs click-able to bring up table of relevant alarms

 

Statistics System

  1. Rapid integration through modeling
  2. Based on device and system data models, derived from Device Model (automatic support for NETCONF Yang/Yin and SNMP)
  3. Binning system available to collect data on 15 minute boundaries
  1. enabled through modeling.
  2. Supports Value Deltas between bins
  1. EMS Performance Status
  1. Database request Statistics
  2. User Request Statistics
  3. Login/Logout Requests
  4. Alarm Statistics
  1. Per Device
  2. Aggregate for Entire System
  1. Internal Messaging Statistics
  1. Tracks messages passed between internal components of system and GUI updates
  1. Statistics Archival

 

Device Upgrade Framework

  1. Image Management
  1. Administrators can keep a library of device images on EMS
  2. Images can be uploaded to EMS from administrator desktop
  1. Upgrade Framework
  1. Icons and Functionality provided in EMS, Developer need only supply a plugin to apply image to device.
  2. Upgrade Status screens available to multiple users at once.
  1. Multi-device Operations
  1. Devices can be upgraded as a group/set.
  2. This allows an entire network of devices to be upgraded to a new version at the same time.

 

LDAP Support

  1. Users can be authenticated through LDAP
  2. User permissions can be specified in LDAP attributes, or default permission groups
  3. Flexible LDAP schema support

 

Security Audits

  1. All significant user-initiated operations are audited by the system.
  2. The audit information contains information about the user, the machine they are logging in from as well as the operation, time to execute and success status.
  3. The set of auditable operations is controlled using meta data in the service model.

 

Persistence Layer

  1. The system comes bundled with PostgreSQL, providing performant and reliable database functionality.
  2. Since Hibernate (and JDBC) are used for database communications, it is very simple to support other databases
  3. Some sample plug-ins for other databases (e.g. Derby, HSQL) are provided.
  4. No database code needs to be written, all artifacts needed for Hibernate to run are automatically generated based upon the models.
  5. 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.
  6. System comes with a backup/restore utility that can be used for disaster recovery (or in multi-EMS server configurations)

 

Licensing System

  1. System can be licensed on a per-installation basis.
  2. Licenses can be tied to hardware aspects of the system so that they are not transferable between systems..
  3. Specific features can be licensed individually (i.e. features can be turned on or off based upon the license).
  4. A license can control access/scale - e.g. it can restrict the maximum number of concurrent users.
  5. Public-private keys and encryption are used for license management, so as to maintain high level of security.
  6. 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.
  7. The underlying framework allows easy addition of licensable features to enable rapid development as well as migration from one version to another.

 

Other built-in tools/libraries (to aid rapid development)  

  1. XML parsing/processing
  2. File handling
  3. Networking (FTP, SSH, XML-RPC, SNMP)
  4. Process and thread handling
  5. Caches

 

Network Applications

  1. “Application Module” Framework for extending core functionality
  2. App Modules can supply modeling, services, and even permissions
  3. Create Apps that work across different devices of different types in one operation
  4. App Modules can access all internal components including alarm system, messaging system, configuration, and Device Controllers.

 

Messaging

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

 

Installation

  1. ElementCenter comes bundled with an installation/upgrade package
  2. The installation allows you to install and run the product as a service that can start automatically and can be managed using the platform’s standard service management.
  3. Supported platforms are RedHat Linux, CentOS and Windows server.

 

Log storage/viewing

  1. Framework for collecting and storing logging data from devices
  2. Log data is stored in CSV files, and automatically aged out after a configured amount of time
  3. A GUI is provided for viewing collected log data - can be filtered by date