Use existing account.


Community discussion.


New users click here.


Talk With Us Live

Press Releases
Current Headlines
Historical Archive


\ RSS Feed<


December 5, 2003 Contact
Kyle Lussier
408-627-7680
lussier@autonoc.com

FOR IMMEDIATE RELEASE

AutoNOC 2.3: Introducing the
Operations Interpreter (OI)

Our tenacious pursuit of leadership in network operations technology has yielded yet another new innovation. AutoNOC 2.3 introduces the Operations Interpreter (OI) TCP/IP socket API and promises to create new opportunities for users to make use of AutoNOC's operations kernel.

Who Needs the AutoNOC Operations Interpreter?

The AutoNOC OI is ideal for network service and Managed Service Provider (MSP) organizations that wish to use the multiprocessing asynchronous AutoNOC operations kernel as part of their own internal or external re-branded web portal or intranet. OI opens up the AutoNOC data structures and makes them easily available to end users. Customers can use OI to integrate AutoNOC with their own branded managed services offerings.

What is the Operations Interpreter?

The Operations Interpreter is a service that runs on TCP/IP port 34 on the AutoNOC server. The API works much the way common internet protocols such as POP3 and SMTP work. You connect to the port programmatically (or with telnet) and submit commands to the OI service which executes them in the AutoNOC kernel.

The OI interface is a feature-rich, live, dynamic, high performance interpreter implemented in fully optimized multiprocessing C++. It supports asynchronous network connections from many different IP addresses and is integrated within AutoNOC's parallel data acquisition engine.

The OI interpreter language itself is the same language used to create user customized probes within AutoNOC. It is similar to C++, Perl and PHP. OI supports user defined variables, complex logic, a full mathematics engine, and many other capabilities such as the ability to automate discovery of devices, maintenance of operations models, and other features needed in production service provider environments.

What Can a User do with the Operations Interpreter?

The following screenshot shows the logon when telnetting to OI socket 34.

Typically a user will log on to the shell within a user program authored in PHP, C++, ASP, or in a different language, extract data from the operations model, and then log off. It works in a manner similar to a SQL server port interface.

AutoNOC users can programmatically render graphs, retrieve data, get service levels, process expressions, run tests, make modifications to the AutoNOC model, and other things within the OI API. OI sessions have access to the full operations model in terms of what the user's security allows.

A novel aspect of the OI API architecture is the high performance live interface to AutoNOC's recoiling database and infinite histories. Users can dynamically and programmatically extract the necessary data for a given calculation, compute customized reports for billing, and do other custom, live, on the fly integrations without having to manage the very large data sets monitoring typically creates.

About AutoNOC LLC

AutoNOC LLC was organized in Atlanta, Georgia in 1999 by commercial software veteran Kyle Lussier to develop and market the AutoNOC core network operations platform. AutoNOC LLC is first to market with a cost effective, robust, fully integrated, Web based solution for network operations and systems management. For more information, visit AutoNOC’s Web site at http://www.autonoc.com.

(C) 2007 - All Rights Reserved - AutoNOC LLC
      Call me!