| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1788.1 | SWISS PTT | ULYSSE::LEFOL | Laurent LEFOL @VBO ULYSSE::LEFOL 828-5008 EIC-Valbonne | Wed Nov 27 1991 08:26 | 62 |
| > - SW configuration and SW distribution
> - Fault management and event logging
> - Security management (user profiles and user access)
> - Accounting for the applications usage
> - Performance control
Fault management :
Did you consider either CHOPS or CHOX. We are currently
discussing with Telecom Engineering to see how to cooperate to port CHOPS to
DECmcc and PNMP.
Security management :
DCRU (Data Center Resource Usage) might help you. This is
going to be an ASSETS. It monitors from a central point
Objective
DCRU allows system operations personnel to manage a large number of VAX/VMS ac-
counts over a network and to implement related Company security policies.
Description
2 main functionalities: System management and Security management
System management :
�captures VMS accounts characteristics such as privileges, expiration dates, identifiers...
�checks and records evolution of these characteristics along time
�Compares some accounts characteristics with information from Personnel file (cost cen-
ter, user name, user function)
�Collects data on disk utilization : disk quota...
�Collects data on node: memory size, system type...
Security management : collects and reports on:
�all network accesses: DECnet, remote, dial-up
�login failures
DCRU uses VAXmail to report on potential security issues to each user account. Security
personnel can also query DCRU to access the stored data. Reports can be individual mes-
sages sent to users or to system managers or complete reports to Site Security manager
Environment
DCRU runs on any VAX/VMS system. DCRU is a client/server software where each node
runs a monitoring task that feeds the central RDB database.
DCRU is written in Pascal.
References
DCRU is used internally by Digital IS operations and Security personnel.
Marketing
DCRU has been submitted to ASSETS.
|
| 1788.2 | You're question is awfully big | BLUMON::SYLOR | Architect = Buzzword Generator | Wed Nov 27 1991 16:21 | 12 |
| In .0, you asked about management of applications (which is different from
management applications). Applications which have to be managed should just
be EMA entities, like anything else that has to be managed.
You also reference the 5 functional areas of management - there's lots
of work underway in those areas. I'm sure you've found the EMA Public directory
at
FILES::EMA$:[Public]
There's general EMA specs and such there...
Mark
|
| 1788.3 | Use DMS Baselevel 2 | FRAMBO::MUELLER | | Thu Nov 28 1991 06:06 | 28 |
| Edgar,
it seems that Management of applications will be able with DECmcc using DNA
CMIP and the Base Level Kit of the DMS/Common Agent. I'm just on my way to
implement a prototype of a DECvoice Management Agent and it works fine.
As mentioned in the earlier replies, the aspects of management are currently
under work. If you want to use DECmcc (I think you should) as director and
you don't want to spend too much work with the aspects (that means writing
your own Function Modules) you should go to get the future plans of DECmcc
and wait for their implementation.
I can recomment the DMS Baselevel Kit. It's easy to use and I just needed
two one and a half day for getting my first responses from DECvoice (In fact
most of the time was spend for getting used with DECvoice).
There is a notes conference at PV1201 called DMS-IFT. Perhabs it will be usefull
to put an entry there.
Another usefull tool for managing an application is the DATA COLLECTOR AM and
the DATA COLLECTOR API (on the Agent's side).. You will be able to send your
own events to DECmcc using just simple calls. I've tried it too and it works
fine (In fact I haven't seen my events because my sink is over in the states,
but my "host" told me it works. Thanks Jean).
Questions are welcome.
ChriS
|
| 1788.4 | | RIVAGE::SILVA | Carl Silva - Telecom Eng - DTN 828-5339 | Thu Nov 28 1991 06:50 | 7 |
| RE: .1,
The PNMP platform has its own trouble ticketing and alarm
reporting/collection system for fault management. For more information, the
PNMP notes file is TAEC::PNMP.
Carl
|
| 1788.5 | A little clarification on PNMP trouble ticketing | RIVAGE::SILVA | Carl Silva - Telecom Eng - DTN 828-5339 | Thu Nov 28 1991 06:56 | 21 |
| RE: .1,
>Fault management :
>
>Did you consider either CHOPS or CHOX. We are currently
>discussing with Telecom Engineering to see how to cooperate to port CHOPS to
>DECmcc and PNMP.
The PNMP platform has its own trouble ticketing and alarm
reporting/collection system for fault management. For more information, the
PNMP notes file is TAEC::PNMP. This functionality will be available in the
first version of PNMP by next spring/summer. The product manager is Claude
Hary (@VBE or TAEC::) and the engineering manager is Marc Flauw (TAEC::).
There have been discussions around whether CHOX could be used by the
TNMP program but there remains to be discussion about if/when/how CHOX could
be integrated technically with the PNMP product. This may or may not be done
at some time in the future. For more info on what is part of the TNMP,
contact Vincent Jullien (TNMP Program Manager) at VBE or TAEC::.
Carl
|