|
| |
Introduction |
ILC produces network management software and supporting
interface hardware products for
communications networks, equipment and facilities. ILC’s
flagship product, MaxView, is the
result of 10 years of development in monitor and control
(M&C) and network management of
hybrid networks. With more than 400 systems delivered
worldwide, ILC’s MaxView Suite has a
proven record of reliability and versatility in a large
number of mission critical environments.
Unrestricted by network or equipment type or age, MaxView
manages equipment either directly
through non-standard and standard interfaces or by accessing
network elements through element management systems.
Providing alarm management, command and control, and
automation for communications networks, MaxView runs
in standard commercial environments such as Windows
and UNIX, while providing real-time status and control.
MaxView is an integrated suite of client-server processes
specifically designed to cost-effectively
operate in small environments as well as large distributed
networks. Allowing users to match
their MaxView investment to current network requirements,
MaxView’s modular design scales
from a single PC managing a small network to dozens
of workstations managing a very large
network
Selected for its ability to automate complex network
operations through an adaptive, user-friendly
interface, MaxView’s open architecture and accompanying
setup tools enable customers to
configure the look and operation of the management system
at any time, without management
system downtime. As a result, ILC sells MaxView as a
turnkey management system including
hardware, integration and software. Because customers
using MaxView can set-up their own
network, customers can simply purchase the software
licenses and provide their own hardware,installation
and integration services.
MaxView...The Management Choice For Any Network.
Take Control. |
| |
| |
| |
1. Product Overview |
ILC tailors a comprehensive M&C or network management
solution to each customer’s needs. MaxView is modular,
so that in its simplest form it provides a complete,
low cost M&C solution, regardless of the size of
the network.
The system can then be enhanced as needed by adding
modules that provide advanced capabilities. It can also
be
expanded to manage larger networks by replicating modules
and distributing them to additional computers and
locations.
MaxView has been developed to manage equipment that
utilizes a variety of physical interface types,
communications protocols and network types. Examples
include networked, serial, GPI/contact closure, analog,
GPIB/IEEE-488, TCP/IP, and many more. MaxView has been
designed to manage legacy and standard interfaces
alike, so that as the network changes the management
system continues to perform without incurring downtime.
It
also can manage other management systems to combine
disparate systems into a single management system.
The MaxView Suite is a distributed processing system;
individual processes can all be hosted on one computer
or spread across many computers. All software modules
are cross-platform compatible, so they can run under
Windows or Unix operating systems.
Among the capabilities and features of the MaxView Suite:
◆ MaxView Aperia™ User Interface: Online Graphics
Editing
- Network views can be edited using MaxView’s internal
editor using universal drawing program tools, such as
drag-and-drop, without
interrupting network management service
◆ MaxView Maestro™ Event Manager: Automation
and Self-Repair
- Configure the system to automatically react to network
events and reconfigure network traffic to repair itself
◆ MaxView InSite™: Report Generator
Browser-based application used to access and analyze
logged
events and create reports
◆ MaxView DDK™: Driver Development Kit
New equipment drivers are created using a graphical
tool for
which no knowledge of computer programming or script
writing is required
◆ MaxView Scenario™: Scheduling System
Ability to schedule network operation commands using
simple
scheduling of commands or a complete booking and reservation
system with conflict resolution
◆ MaxView Chorus™: Trouble Ticketing
Track problem-solving activities through a fully integrated
browser
based trouble ticketing system and knowledge base
◆ MaxView ACE™: Alarm Correlation
Alarms and other events can be correlated for Root Cause
Analysis
(RCA) to pinpoint the source of a network problem
◆ Open Architecture
The MaxView suite is an open architecture product that
allows external third party
products to link to it via SNMP or CORBA
◆ Browser-based System Configuration
Network equipment is added and removed through a browser
|
| |
2. Compliance |
| ILC maintains compliance to the following
U.S. Department of Defense standards: |
◆ Integration and Run Time Specification
(I&RTS) for the Defense Information Infrastructure-Common
Operating Environment (DII-COE), Version 4.1
◆ COE Integration and Runtime Specification
(I&RTS), Version 4.2, dated February 2002
◆ COE User Interface Specification, Version
4.0, October 1999
◆ DoD HCI Style Guide
◆ Joint Technical Architecture-Army (JTA-Army), Version
6.0
ILC’s MaxView software is DII-COE Level 6 Compliant, with
a clear migration path to Levels 7 and 8. |
| |
2.1 Standards |
| ILC employs a number of software programming
languages in the implementation of the MaxView software.
These programming languages include: |
| ◆ C/C++ |
| ◆ Java |
| ◆ Tool Communication Language (TCL) |
| ILC’s MaxView software is compatible with
the following communication interface standards: |
| ◆ Serial (RS-232, RS-422, RS485 asynchronous and synchronous) |
| ◆ GPI (Dry and Wet Contact) |
| ◆ IEEE-488 |
| ◆ Ethernet (10/100BaseT) |
| ◆ SNMP |
| ◆ Internet |
| ◆ TCP/IP |
| ◆ XML |
| ◆ CORBA |
| ◆ UDP |
| ◆ Telnet |
| |
3. System Implementation |
ILC customers can perform all of the tasks required
to install, configure and maintain their MaxView management
system. Tools are included to add and remove equipment
from the management system, draw and edit the views
that the operators use, and even create new drivers for
the system. |
| |
3.1 Configuring the equipment to be managed by MaxView |
One of the most important advantages of the MaxView
system is its flexibility in supporting a variety of devices
and the ease with which devices can be added into the
system. Devices can be added into the management system
without affecting other managed devices and without affecting
the core system execution. Devices are added and configured
into MaxView using a browser-based setup tool. With the
setup and configuration tool, a user is able
to: |
| ◆ Add/Remove Communication Ports |
| ◆ Add/Remove Devices |
| ◆ Monitor Device Communications |
| |
3.2 Drawing views using the online, on-screen
MaxView Aperia Editor |
Once a device is setup using the browser-based tool
described above, the device automatically appears in the
MaxView Aperia User Interface. Using the Aperia Editor,
shown in the figure, an authorized user can simply drag-and-drop
the device onto a network diagram
panel. The newly displayed device is immediately active
and displays current status. |
| |
Custom Symbols - The Aperia Editor
provides a library of prebuilt
stock symbols used to represent common block diagram
components. New and custom symbols can also be created
using the Aperia Symbol Editor. These custom symbols can
be
saved and can be assigned to specific devices configured
in the system. |
| |
 |
| |
ILC Beans - MaxView Aperia uses beans
to represent unique graphic objects in a graphic screen.
ILC has developed numerous objects to represent and display
analog values
such as: |
| - Speed Odometer Gauge |
| - Linear Gauge |
| - Numeric Display |
| - Strip Chart |
| - X-Y Line Chart |
| |
| Custom Device Panels- MaxView Aperia
also provides the capability, via the Aperia Editor, to
create custom device panels as shown in the figure. Custom
device panels simplify device operation by showing information
in the same layout for all devices of the same type. |
| |
3.3 User Management |
| Network administrator can set user access levels and
permissions as follows: |
| |
Users - Authorize users (create, delete
or update); Assign user access to trees and command classes
to grant access to all or any subset of trees or commands
Trees - Populate trees with existing
panels, which contain the network diagrams of devices
being managed
Command Classes
- Create groups of functional commands, either by device(s)
or type(s) of command(s), to limit users’ command capabilities
or assign the same tasks to a group of users without having
to duplicate assignment efforts for each user
Panels - Create and manage the Aperia
screen displays that contain the managed devices and network
diagrams used by the network operator to monitor and control
the network. Panels may be arranged in functional, geographic
or organizational-specific groupings |
| |
4. Operating the System |
| |
4.1 Fault Management |
After detecting a fault in the controlled equipment,
MaxView automatically generates both visual and audible
alarms, initiates appropriate triggered events, and records
the failures in an event database. MaxView categorizes
faults and alarms as two major types: communication-related
or device-related. Faults are associated with devices
(causing a major or minor device alarm);
Communications-related problems generate system (comm)
alarms. Alarms are shown as color-coded flashing device
icons. |
| |
 |
| |
4.2 Fault Display |
Alarm symbols are displayed in the tree view, as flashing
device icons, on the network diagram
panel, in the events grid and as an alarm type in the
summary bar. In addition to visual notification, an operator
may also be alerted audibly via user configurable
sounds and through automated notification capability such
as paging or email. MaxView also supports a variety of
alarm masking functions that provide the ability to suppress
meaningless or nuisance alarms throughout the management
system or at specific workstations. |
| |
4.3 Event Logging |
| Once MaxView detects a system event, it time and date
stamps the event and logs the event to an ODBC SQL database
allowing network statistics to be analyzed and historical
reports to be created. The database can be any ODBC-compatible
database. The event database is user configured to set
current database storage intervals and size limits as
well as archiving and deletion intervals and limits. |
| |
4.4 MaxView InSite - Report Generation |
MaxView InSite is a browser-based application that is
used to access and analyze logged events and create reports.
Operators can print out statistical data and reports on
an extensive variety of system parameters. Events can
be filtered, sorted, plotted and printed. Time parameters
can be set to any period of time. Operators can print
out statistical data and reports such as analog values,
configuration parameters and faults in the system as well
as many
others. |
| |
4.5 MaxView Maestro - Automation |
| Maestro adds an automation and a programmable service
management tool to the MaxView system with capabilities
that include: creating macros to automate and schedule
frequently used commands; setting triggers to automatically
notify personnel about defined network events, defining
super macros to incorporate triggers and macros to automatically
respond to, rectify network problems and verify proper
operation; and creating virtual devices to represent device
groups by customer, service or other criteria to facilitate
network management. |
| |
4.6 MaxView ACE Alarm Correlation and
Root Cause Analysis (RCA) |
| Alarm Correlation and Root Cause Analysis (RCA) is the
component of fault management that consists of determining
the original cause for the received symptoms. There are
many sets of symptoms that the network management system
may receive: A device may generate several alarms due
to a single fault; a fault may be intermittent; or multiple
network objects may detect a single fault. The process
of alarm correlation automatically analyzes the symptoms
in order to diagnose the actual problem and generate a
specific alarm that clearly identifies the problem. |
| |
4.7 MaxView Scenario - Scheduling System |
| Scenario is a turnkey web-based resource allocation
tool. This system allows for the maintenance of a system
database, the submission and review of booking requests,
the review of the allocation schedule and an interface
to the M&C system for execution. The user interface
is through a standard web browser. The system allows for
the detection of conflicts, generation of multiple reports,
and addition and modification of equipment. |
| |
4.8 MaxView Chorus Trouble Ticketing |
| Chorus is a full-featured trouble ticketing module that
tracks faults from detection to repair, providing the
ability to track overall service performance, monitor
the trouble resolution process, and create a stored “knowledge-base”
of information useful for analyzing and resolving future
problems. |
| |
5. Technical Data |
| |
| The MaxView architecture is a logical three-tier design
(consisting of client, server, and database) compressed
into a physical two-tier implementation in which the MaxView
server and COTS Relational Database Management System
(RDBMS) co-reside on a single PC. This proven configuration
is widely used in both commercial and military M&C
applications, and it meets the COE Category 3 compliance
requirement for architectural compatibility. It provides
an effective distributed client-server design offering
performance, flexibility, maintainability, and scalability
while hiding the complexity of distributed processing
from the user. |
| |
| The client element of the MaxView architecture encompasses
the workstation and the corresponding Aperia User Interface
software. These elements allow the operator to monitor
and control the equipment and configuration through the
MaxView server. Any workstation can access the MaxView
server via the workstation access points. Workstations
are independent from the MaxView server, with all data
needed to operate the terminal contained in the server
and downloaded to the workstation upon connection. Therefore,
workstations can be connected and disconnected at any
time without impacting system operations. |
| |
 |
| |
The Aperia User Interface client software that executes
on the workstation is designed to be compliant with the
DII-COE User Interface Specification. Data is presented
to the operator in an intuitive and consistent manner
that facilitates efficient and correct decision-making.
While an identical Aperia client executes on each workstation,
the operational context and user interactions dictate
the screen’s display at each user interface instantiation.
The database element of three-tier architecture is a separable
Structured Query Language (SQL)-Open Database Connectivity
(ODBC) compliant COTS RDBMS that co-resides on the same
processor on which the MaxView server software resides.
This database provides all necessary storage for system
events and alarms, and it facilitates the generation of
both online and offline reports. The database architecture
also meets the COE compliance requirements, with the MaxView
server application integrated with database RDBMS application
as separate
segments executing on a single hardware platform.
Equipment is continuously monitored and controlled by
the ILC NetLink Network Front-End Processors (NFEP). An
NFEP simultaneously polls up to 16 serial ports with connected
devices communicating over RS-232, RS-422, or RS-485 asynchronous
serial ports. The NFEP’s multithreaded polling engine
(communications server) is configured with equipment data
and polling priorities in nonvolatile Flash memory. If
the equipment configuration changes, the
NFEP is easily reconfigured online by the MaxView server
via the Ethernet port, or locally through a (seventeenth)
supervisory serial port.
Discreet I/O-controlled equipment is also polled by the
NFEPs through an intermediate ILC manufactured I/O Link
Intelligent Controller (IC). The I/O Link provides up
to 96 contact closure inputs and outputs that are accessed
via an NFEP serial port.
The MaxView server with the co-resident database connects
to the workstation, and I/O devices through the IEEE 802.3
100Base backbone.
The software processes in the MaxView system are: |
| |
5.1 MaxView Server |
| The MaxView server processes receive status change messages
from one or more communications server processe configured
in the NMS. The MaxView server interprets the change messages,
properly formats the messages and forwards the messages
to the Aperia User Interface and Maestro Event Manager
via TCP/IP socket connections. The MaxView server also
receives commands from both Aperia and Maestro, properly
formats the commands and sends the command to the appropriate
communications server. |
| |
5.2 Communications Server |
The communications server provides the multi-threaded,
real time polling process that uses the device driver
files to directly communicate to the managed devices.
It compares subsequent message polls to determine if a
change of state has occurred in a device. If a change
of state has occurred, then the communications server
sends the change message to the MaxView server via a TCP/IP
socket connection.
Polling
MaxView polls serial, contact closure, analog and IP socket
devices for their settings and processes commands and
faults for these elements. Additionally, it handles TRAPs,
GETs and SETs from SNMP equipment. |
| |
5.3 System Manager |
Manages user interface access to the correct MaxView
server process and provides security and licensing control
to ensure that only properly authorized users (user interfaces)
may access the system.
Event Logging
The Logger logs all network events to an ODBC SQL database.
The events are time and dated stamped stored into a number
of database tables, thus allowing for very flexible sorts
and queries. |
| |
5.4 Aperia User Interface |
| Provides a Java based, cross platform, customizable,
easy-to-use graphical user interface to manage system
devices and respond to events such as alarms. |
| |
5.5 InSite Report Generator |
| The browser-based InSite application is used to access
the logger database and print out statistical data and
reports on the status of analogs, configuration parameters
and faults in the system for user-definable time periods
and parameters. |
| |
5.6 Maestro Event Management |
| |
Macros
Macros enable an operator to create a sequence of commands
for devices in the system. Each Macro can have commands
from any device in the system. The operator may run macros
manually from any workstation or schedule the macro for
a later time.
Triggering Events
Event Triggers are used to automatically take action based
on an event or combination of events. The triggers can
be used to e-mail or page a group of responsible personnel,
open and display restoration procedure instructions on
the operator GUI, or cause an automated response to automatically
recover the service. Event triggers are able to do the
following:
◆ Create triggers to respond to, or cause, changes in
alarms, analogs and other device
parameters
◆ E-mail, page or pop up an alert to notify network management
personnel
◆ Run a program, macro, Super macro or play a wave file
Supermacros
Supermacros extend the Maestro automation capability by
combining the automation features of macros with the network
diagnostic capabilities of triggers to react to a specified
event, automatically initiate a series of device commands,
verify the device has been properly affected after each
command before proceeding to the next function, and verify
proper operation has been restored or escalate the problem.
Scheduling & Notification
Commands, Macros, and Supermacros can be scheduled using
the MaxView Maestro to once run at a later time or repeatedly
at a user-defined interval. The system also provides messaging
and notification capabilities including direct paging,
Internet messaging and computer notification.
Virtual Devices
Virtual devices allow the operator to combine elements
of real devices and associated elements (statuses, alarms,
etc.) into a new logical device. By grouping devices or
parts of devices into a Virtual Device, an operator can
treat signal chains or services as a single entity. For
example, users can create virtual devices (with onscreen
icons) to represent entire Service chains, through which
operators can access subpanels that depicts all related
devices. Within a couple of clicks, operators can access
the exact cause of a problem. Action can be taken to notify
the customer service representative that a customer is
down, show a restoration procedure, or even automatically
move the traffic to an operational link |
| |
| |
5.7 ACE Alarm Correlation |
| Using alarm correlation, faults, events, performance
measurements and configuration settings can be correlated
with one another to establish the root cause of a problem
in the network. The correlation relationships are defined
using a drag and drop editor. Events can be correlated
in time or across areas of the network. |
| |
Alarm Filtering
In addition to automatic alarm correlation to identify
root causes, MaxView incorporates automated alarm filtering
and escalation capabilities. MaxView incorporates four
types of alarm filters that can be combined and configured
to only allow alarms that meet specified criteria: |
A Maintenance filter allows an alarm
to be suppressed for a specified period of time and is
useful when equipment is being repaired or configured
and the associated alarms should be
ignored.
A Cancellation filter allows the system
to report an alarm only after it has been active for a
set period of time; otherwise, it is cancelled.
A Frequency filter allows the system
to report the alarm only after it has appeared a specified
number of times within a given time period. These filters
avoid short, indeterminate or noise
alarms that generally have no meaning unless they are
persistent.
An Escalation filter forces an alarm
that has been active and unacknowledged by an operator
for a set period of time to increase its reported severity
level. As the severity level increases,
different levels of management may be automatically notified
or restoration procedures can
be automatically invoked. |
| |
5.8 Chorus Trouble Ticketing |
| Chorus is a browser-based application that accesses
the MaxView event database. Basic trouble ticket information
includes: |
◆ Unique ticket id incorporating a timestamp and sequential
index
◆ Ticket creation time
◆ Description of Fault
◆ Faulted component(s) based on available inventory database
◆ Location of Fault
◆ Current ticket status
◆ Ticket priority
◆ Assigned technician ID
◆ Services/clients affected by Fault; based on available
database
◆ Fault category |
| The trouble ticketing system also supports a searchable
repository of all information entered by technicians.
Each time a technician enters a comment, the comment is
recorded with the technician’s name along with the date
and time of the entry. These entries form the basis of
the “knowledgebase” and comprise a read-only collection
of information available to all users of the system. |
| |
5.9 Scenario Scheduler |
The MaxView Scenario scheduler is a complete booking
and reservation system for automating the operation of
the network. It works in conjunction with the MaxView
Maestro event manager to put the scheduled activities
into operation.
Scenario is a turnkey web-based resource allocation tool.
This system allows for the maintenance of a system database,
the submission and review of booking requests, the review
of the allocation schedule and an interface to the M&C
system for execution. The human interface is through a
standard web browser. The system allows for the detection
of conflicts, generation of multiple reports, and addition
and modification of equipment
The transmission plan schedule resides in a relational
database that defines the components of a scheduled event
and the launch time of the event. The schedule is built
through a web based front end that presents the operator
with a booking sheet through which the operator selects
the type of booking, execution time and booking parameters.
This front end allows an operator to perform administrative
tasks, request a booking (scheduled event) with the booking
sheet, review the schedule and modify/delete existing
bookings.
Once a booking sheet is filled out, the operator submits
the booking request for approval. The booking system performs
conflict resolution wherein it determines which equipment
is capable of satisfying the booking, and then performs
conflict resolution to select which equipment to use.
If no satisfactory equipment is available for the booking,
the booking is denied. Otherwise it is accepted and acknowledged
to the operator.
|
Web-based booking sheets - MaxView
Scenario Booking System utilizes a web browser interface
so it can run on Unix or Windows computers. It also does
not need to be installed on each computer ? the user runs
a standard web browser to access the system.
Conflict Resolution - MaxView Scenario
Booking System is a transaction based resource management
system. The operator fills out the booking form and requests
the booking. The booking system searches for equipment
that can provide a wireless, wireline or satellite circuit,
and that is available for the requested period. It then
confirms the booking or prompts the user to make a change
if there is a conflict.
Color-coded Playlist
- The user interface shows a play list of events (bookings)
that will be run on the schedule. Color codes indicate
whether the event is current, past or future.
Utilization Report - The user interface
shows a utilization schedule for each piece of equipment
indicating if more equipment should be purchased to ensure
service availability. |
Scenario is designed around a central database. It is
a real-time server application that serves the web interface,
handles conflict resolution and scheduling and interfaces
to a relational database. A browser running on any computer
on the network with the server connects to the server
computer is via a standard network, such as 100 MB Ethernet,
using the TCP/IP suite of network protocols. Access to
the database occurs through the web browser by via connection
to a web server, which in turn interfaces to the database.
Scenario continuously monitors the schedule, and then
launches the events as their schedule times are reached.
It injects the events into the MaxView server to cause
the commands to be sent to the network equipment at the
appropriate time. |
| |
5.10 Device Driver Development Kit (DDK) |
| The Driver Development Kit (DDK) is a custom device
driver development tool developed by ILC. With the DDK
users can create serial, contact closure and SNMP drivers
to connect these devices to MaxView Systems without having
to learn a programming language. Using the DDK requires
no programming or scripting language experience. It is
a simple, user- friendly point and click tool for rapid
creation of MaxView compatible device drivers. |
| |
| |
| |
