|
*********************
* * D I G I T A L * * INTEROFFICE MEMORANDUM
*********************
To: VMS Interest List Date: 11-February-1993
UNIX Interest List From: Laura Gawronski Horn
Dept: TNSG NSM
DTN : 297-2040
LOC/MS: MRO1-2/S43
Enet: HYEND::LHORN
Subject: POLYCENTER Console Manager V1.1 -- Phase 0 Is Open!
***DIGITAL CONFIDENTIAL***
****************************************************************************
* Phase 0 for the POLYCENTER Console Manager V1.1 is now officially open. *
****************************************************************************
The objective of Digital's Fault Management Strategy is to provide
integrated capabilities for handling events detected at many sources
(systems, applications, networks) across multiple platforms. Console
Management is an integral part of this strategy. The POLYCENTER Console
Manager will be the foundation for all future POLYCENTER console
management functionality.
For those of you who haven't heard about POLYCENTER Console Manager (CM)
V1.0, CM provides consolidated console management for up to 200
systems/devices in a globally distributed environment. Systems/devices
that can be managed must send ASCII data over an RS232C line, have an
EIA console port, support XON/XOFF and I/O buffering. CM supports LAT,
TELNET and direct (hardwired) connections. CM V1.0 runs on a RISC
ULTRIX host platform.
From a single terminal or workstation display, a system manager or
operator can perform all the console functions (including booting systems)
for each serviced system/device, examine current as well as historical
console data, view events as they occur or be notified of critical events
as they occur.
An OSF/Motif interface provides an iconic display of the systems/devices
being managed. The color of an icon can change to signify the occurrence
of an event. Additional information can be obtained by clicking on the
relevant system icon.
By using CM, system managers can support up to 200 system/devices from
one central point!
Page 2
The primary goals for POLYCENTER Console Manager V1.1 are:
- to provide the same console management functionality across
multiple platforms
- these host platforms include Alpha/VMS, Alpha/OSF, VAX/VMS
and RISC ULTRIX (yes, all 4 are targeted for V1.1)
- provide VAXcluster Console System (VCS) customers with an
upgrade path. VCS is a console management product that currently
runs on a VAX/VMS host platform.
A Product Requirements Input Form is attached to this memo for your
use in submitting requirements. Please return your completed
form to: HYEND::LHORN or Laura Horn @ MRO
NO LATER THAN 12-Mar-1993
Please be as specific as possible in defining your requirements, and
when appropriate, provide as much justification as you can for their
inclusion in POLYCENTER Console Manager.
Although all requirements are welcome, time and resource constraints
will force us to prioritize each requirement. All outstanding
requirements will be reviewed for inclusion in the next release.
Additionally, I welcome your nominations for both internal and external
field test candidates.
***DIGITAL CONFIDENTIAL***
POLYCENTER CONSOLE MANAGER V1.1
Product Requirements Input Form
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Directions:
----------
Please complete this form by providing all requested information.
Submit the completed form to HYEND::LHORN no later than Friday,
12-Mar-1993 to ensure consideration of your requirements
during POLYCENTER Console Manager V1.1 Phase 0.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
1. Submittor:
DTN:
Node:
Loc/MS:
Position:
2. Customer, Engineering or Support Group issuing request:
Include name and brief description of group.
3. Abstract:
Include brief, single-paragraph description of requirement.
4. Description:
Include detailed description of requirement and an indication of
expected result if requirement is included.
5. Schedule:
Note any schedule concerns caused by products on which this
requirement would be dependent. Include availability dates for
specifications, prototypes, field tests, and FRS when appropriate.
6. Benefit:
Description of benefit, including substantiating data.
7. Impact of not meeting request:
Describe impact to Digital if request is turned down. Please
explain this in terms of lost opportunities and markets.
Page 2
8. Justification:
Include here any other reasons for including this request.
9. Rating:
Rate the importance of including the requirement using the
following scale:
1 - ESSENTIAL 3 - IMPORTANT 5 - DESIRABLE
10. Known issues:
Include statement of risks to either schedule or content.
11. Support documents:
Identify any documents that add detail to the request.
|
| I was mailed this, I see no reason why everyone else shouldnt see it too.
Please Direct any questions to Steve Englert or Mike Young.
DO NOT post questions in this conference, the PCM team are in no way
involved in the PEM effort.
Cheers,
Phil
From: ZEKE::ENGLERT "In any event...what is it? 28-Jun-1995 1715" 29-JUN-1995 02:50:12.32
To: ZENDIA::NSM,@NT-CONTACTS
CC: @UNIXINTEREST,@VMSINTEREST,SELF
Subj: POLYCENTER Event Manager (PEM) V1.0 for Windows NT
This is the formal announcement of.....
POLYCENTER Event Manager (PEM) V1.0 for Windows NT.
The Product Requirements (PR) phase is now open.
We will close PR on 7/11/95.
Product Description
POLYCENTER Event Manager for Windows NT will provide consolidated event
and console management functions similiar to POLYCENTER Console Manager
and POLYCENTER System Watchdog. (Essentially PEM V1.0 will merge these two
products into one.)
It is the goal of this project to provide a consolidated event management
product that can interoperate with other value added management products,
both internal and external, and evolve into a complete and comprehensive
event management solution that can be scaled from a collection of LAN's to
the enterprise. The components of this product will be:
- a console management function
- an event distribution function
- an event log (database)
- an event definition database
- event collection agents
- a GUI
- an event dispatcher
- a diagnostic function (rules based/correlation)
PEM will be integrated with existing POLYCENTER products such as POLYCENTER
NetView on Windows NT, AssetWORKS, and Performance Expert.
In it's first release, the product will provide the following:
- PCM functionality
- Event Management (similar to PSW)
- Windows NT GUI
- New event management agents (WNT & NetWare)
- Hooks into the exisiting PSW consolidator
- Integration with PNV
- An SQL compliant database.
PEM V1.0 is currently scheduled for FRS in Q3FY96.
Future releases will add coverage (agents) for other UNIX platforms,
rules-based diagnositics, continued integration with other applications,
continued code improvements, a correlation engine, and others as
appropriate.
New releases will occur approximately every six months.
The current Product Requirements document is posted in the PEM public
directory, as with all the PEM documents, you will find them in:
SNOLPD::WINO:[PEM]
or as a PathWORKS share in:
\\SNOLPD\PEM.
Location of PEM Notesfile:
HASTUR::PEM
PEM contacts:
Product Manager: Steve Englert ZEKE::ENGLERT
Engineering Supervisor: Mike Young ZENDIA::YOUNG
|