Conference azur::mcc

5536.0. "Remote Agent" by UTROP1::HARTKAMP_R (Rob Hartkamp @UTO) Wed Aug 25 1993 11:56

Remote Agent for Polycenter Network Manager 

The Remote Agent can be applied to manage multiple distributed Systems via wide 
area network connections. 
This is especially the case when no (extended) LAN is available to connect a 
System "locally" to Polycenter Network Manager.

The remote agent was initially develloped to manage PABX's, but can also be used 
to manage systems of different nature. 

Benefits
The Remote Agent will save network and operating costs by: 
- Remote management 
- Unattended operation
- Multiple systems can be managed by a single management station and operator
- Standard API used to interface with Polycenter Network Manager
- Efficient network usage
- Different types of WANs can be used

Configuration
The Remote Agent consists of a MS-DOS Personal Computer (without display and 
keyboard) which is connected locally to the System. The Remote Agent software is 
running in an unattended way.
The Remote Agent is plugged in to interface with Polycenter Network Manager in a 
DECnet network (via switched or leased line or X.25). 

The network manager identifies the Systems in the network by means of the DECnet 
nodename of the Remote Agent.

Operation

The Remote Agent software consists of three independant running processes:

. Directive agent.
	Provides remote processing of commands from Polycenter Network Manager.
	Commands are separated in System commands and Remote Agent commands. 
	The Remote Agent accepts all existing System commands. All System 
	operator commands and responses are passed transparantly between the 
	System and Polycenter Network Manager.

. Alarm Agent
	System alarms are received by the Polycenter Network Manager 
	Datacollector via a standard remote collector API.
	The Alarm Agent scans System alarms every 5 minutes (default) and sends 
	changes of System alarms to the remote datacollector. When the Remote 
	Agent fails to send an alarm within the scan cyclus (default 3 retries) 
	and the alarm is cleared by a System operator within this cyclus, the 
	alarm will be lost.
	At software generation time the address can be specified where event 
	messages are stored.
	The Alarm Agent makes efficient use of the network by:
	- sending information only on change of System alarms
	- polling for alarms by the Remote Agent in stead of polling over the     
	  network.

. Accounting Collector
	If a System generates real-time accounting data (such as a PABX), the 
	accounting collector stores accounting records from the System in a 
	file. 
	Efficient use of the network is obtained by buffering the 
	accounting data. Purge time can be specified.
	On request of Polycenter Network Manager this information is transferred 
	periodically. 

Security
Access to the Remote Agent (via DECnet) can be protected by a password.


Prerequisites

hardware:
PC 386SX 20Mhz, no keyboard or display required
Internal memory:1 Mb 
System interface:COM1: accounting data
		 COM2: operator port
hard disk: 	 minimum 20Mb, 
External storage requirement is dependant on amount accounting data.
and storage duration.
WAN interface: 	X.25 or ethernet 
		For async DECnet: serial port (not yet tested)

software:
MS-DOS V5.0
DECnet-DOS V4.1.4
for Alarm mode: Task-tot-Task program  V4.1 (TTT.EXE)
Transparant Network Task Control V4.1 (TNT.EXE)
optional: X.25 software


Further Information
Implementations of other functions or adaptions to this software can be realised 
on project basis. Support can be obtained from:

Digital Equipment 
Enterprise Network Services
POB 9064
3506 GB UTRECHT 
Netherlands

Rob Hartkamp @UTO
DTN 8382203
tel. +31(30)832203
fax. +31(30)833066

For technical questions contact Wim Zwama @UTO