| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 426.1 | How to get DECmcc SPDs | DELNI::HEBENSTREIT | | Mon Oct 22 1990 10:16 | 4 |
| Tom, I suggest you contact Daniel Holland (DELNI::D_Holland) about
those SPDs. The should be in VTX this week, but if you need them asap,
Daniel is the right person to see. Regards, mark
|
| 426.2 | DECmcc Toolkit v1.0 SPD | DELNI::D_HOLLAND | | Fri Oct 26 1990 10:59 | 352 |
| If you copy or extract THIS text version of the SPD for a
customer please be advised it is PRELIMINARY until it
appears on VTX or with the software kit from manufactur-
ing.
PRODUCT NAME: DECmcc Developer's Toolkit V1.0 SPD 32.49.00
DESCRIPTION
The DECmcc Developer's Toolkit is a VMS layered product used for the
development of application-specific DECmcc access modules. The development
tools run on any host VAX computer under VMS Operating Systems.
The DECmcc Developer's Toolkit is for experienced network managers and
system software developers.
The DECmcc Director or Basic Management System software is required for
enrolling, testing and operating access modules developed using the
Toolkit. The DECmcc system software simplifies the design and implementation
of application-specific access modules by offering a runtime kernel executive,
various service programs, and source code for a Sample Access Module.
The Toolkit includes documentation and several software development
utilities and testing tools.
^ Documentation
The DECmcc Developer's Toolkit documentation provides information to assist
in the design and development of access modules. It includes the following
documents:
- Enterprise Management Architecture General Description
- EMA Entity Modeling
- The DECmcc System Reference Manual
- DECmcc Management Module Programming
- The DECmcc Developer's Toolkit Reference
The DECmcc Module Reference, available on-line only, provides specifications
of the services offered and required by each DECmcc management module.
DEVELOPMENT UTILITIES/TOOLS
^ DECmcc Design Framework
The DECmcc Design framework is a set of generic software components,
including a modular and extensible starter access module. The starter
access module may be used to build a starter application-specific access
module. The Design framework uses proven development techniques that
minimise coding errors, expedite development, and reduce coding ambiguities
that can arise during the course of access module design.
^ Management Specification Language (MSL)
The MSL Translator Utility translates application-specific management
specification information into input suitable for the DECmcc dictionary
administrator program (DAP).
The following utilities are included in the DECmcc Director and Basic
Management System software and are necessary for enrolling
application-specific access modules and related files into the DECmcc
system.
- Dictionary Administrator Program (DAP) Utility,
- Parse Table Builder (PTB) Utility,
- Test Bed Driver (TBD) Utility,
- Help File Builder (HFB) Utility
These utilities allow on-site enrollment of access modules. The DECmcc
Developer's Toolkit Reference (AA-PD5MA-TE) describes each utility in
detail.
HARDWARE REQUIREMENTS
VAX, MicroVAX, or VAXstation configurations as specified in the System
Support Addendum (SSA 32.49.00A)
SOFTWARE REQUIREMENTS
VMS Operating System
Layered Products:
DECmcc Director or
DECmcc Basic Management System
VAX C for VMS
DECnet-VAX to match VMS Operating System
DECdns Server to match VMS (must be somewhere in network)
For Workstations Running DECwindows
VMS Operating System (and necessary components of DECwindows)
Please refer to the System Support Addendum (SSA 32.49.00A) for
required versions of prerequisite or optional software.
ORDERING INFORMATION
Software License: QL-YSWA9-AA
Software Media: QL-YSWAA-H5
Software Documentation: QL-YSWAA-GZ
Software Product Services: QT-YSWA*-**
* Denotes variant fields. For additional information on available
licenses, services and media refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of DIGITAL's
Standard terms and conditions. For more information about DIGITAL's
licensing terms and policies, please contact your local DIGITAL
office.
LICENSE MANAGEMENT FACILITY
This product supports the VMS License Management Facility (LMF).
License units for this product are allocated at a flat price basis,
regardless of User/Activity or processor type.
For more information on the LMF refer to the VMS Operating System
Software Product Description (SPD 25.01.xx) or the LMF manual of the
VMS Operating System documentation set.
For more information about DIGITAL's licensing terms and policies,
please contact your local DIGITAL office.
SOFTWARE PRODUCT SERVICES
o Layered Product Support (LPS)
Layered Product Support provides the right-to-use new versions of
layered software. It also extends the level of support provided on
the kernel software to include coverage of the layered software
product. Layered Product Support is required for all Digital layered
software running on a system covered by Full Support. LPS is a
prerequisite for the service options listed below.
o Media and Documentation Distribution Service (MDDS)
Ensures customers have access to the latest software versions of
media and documentation updates. MDDS is ordered on a per product
basis.
o Documentation Update Service
Ensures that users receive documentation updates for software manuals
as they are released.
o Initial Software Installation
Installation by Digital of newly purchased software on a per product
basis.
Other Network Management Services are also available. These include,
but are not restricted to, the following:
o Network Management Operations Services
o Network Management Planning and Design Services
o Network Management Implementation Services
o Network Management Training
For local availability, please contact your Digital Sales Office.
SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL with the
purchase of a license for the product as defined in the Software
Warranty Addendum of this SPD.
September 1990
--------------------------------------------------------------------------
SYSTEM SUPPORT ADDENDUM
PRODUCT NAME: DECmcc Developer's Toolkit, V1.0 SSA: 32.49.00-A
MINIMUM HARDWARE REQUIRED
VAX :
VAX 6000 Model 200 Series,
VAX 6000 Model 300 Series,
VAX 6000 Model 400 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350,
VAX 8500, VAX 8530, VAX 8550, VAX 8600,
VAX 8650, VAX 8700, VAX 8800, VAX 8810,
VAX 8820, VAX 8830, VAX 8840, VAX 8842,
VAX 8974, VAX 8978
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX :
MicroVAX II, MicroVAX 2000, MicroVAX 3300, MicroVAX 3400, MicroVAX
3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation :
VAXstation II, VAXstation 2000, VAXstation 3100 Series
VAXstation 3200, VAXstation 3500, VAXstation 3520,
VAXstation 3540,
VAXserver :
VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600,
VAXserver 3602, VAXserver 3800, VAXserver 3900, VAXserver 6210,
VAXserver 6220, VAXserver 6310, VAXserver 6320
Processors not supported:
VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I,
VAXstation 8000
A TK50 Tape Drive is required for stand-alone MicroVAX 2000 and
VAXstation 2000 systems.
Block space requirements (Block Cluster Size = 1):
Disk space required for installation: 26500 blocks
Disk space required for use (permanent): Not Applicable
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's
system environment, configuration, and software options.
OPTIONAL HARDWARE
None
International Support:
None
CLUSTER ENVIRONMENT
This layered product is fully supported when installed on any valid
and licensed VAXcluster* configuration without restrictions. The
MINIMUM HARDWARE section of this product's Software Product
Description and System Support Addendum detail any special hardware
required by this product.
* V5.x VAXcluster configurations are fully described in the VAXcluster
Software Product Description (29.78.xx) and include CI, NI and Mixed
Interconnect configurations.
PREREQUISITE SOFTWARE
For Systems Using Terminals (No DECwindows Interface)
VMS Operating System V5.3
Layered Products:
DECmcc Director V1.0
DECmcc Basic Management System V1.0
DECnet-VAX V5.0 - V5.3
DECdns V1.2
VAX C to match VMS Operating System
For Workstations Running DECwindows
VMS Operating System v5.3 (and necessary components of DECwindows)
Layered Products:
DECmcc Director V1.0
DECmcc Basic Management System V1.0
DECnet-VAX V5.0 - V5.3
DECdns V1.2
VAX C to match VMS Operating System
VMS Tailoring
The following VMS classes are required for full functionality of this
layered product:
VMS REQUIRED SAVESET
NETWORK SUPPORT
PROGRAMMING SUPPORT
UTILITIES
For more information on VMS classes and tailoring, refer to the
VAX/VMS Operating System Software Product Description (SPD 25.01.xx).
OPTIONAL SOFTWARE
VAX Language-Sensitive Editor (VAXLSE) V3.0
GROWTH CONSIDERATION
The minimum hardware and software requirements for any future version
of this product may be different from the minimum hardware and
software requirements for the current version.
DISTRIBUTION MEDIA
TK50 Streaming Tape
ORDERING INFORMATION
Software License: QL-YSWA9-AA
Software Media: QL-YSWAA-H5
Software Documentation: QL-YSWAA-GZ
Software Product Services: QT-YSWA*-**
* Denotes variant fields. For additional information on available
licenses, services and media refer to the appropriate price book.
The above information is valid at time of release. Please contact
your local DIGITAL office for most up-to-date information.
September 1990
|
| 426.3 | DECmcc Director v1.0 SPD | DELNI::D_HOLLAND | | Fri Oct 26 1990 11:04 | 469 |
| If you copy or extract THIS text version of the SPD for a
customer please mention that it is PRELIMINARY until it
appears on VTX or with the software kit from manufactur-
ing.
PRODUCT NAME: DECmcc Director, V1.0 SPD 32.46.00
DESCRIPTION
The DECmcc(TM) software implements Digital's Enterprise Management
Architecture (EMA) director model, consistent with the ISO/OSI
management framework. The DECmcc Director software, initially
implemented under VMS Operating Systems, lets users control, monitor,
and test manageable objects (entities) in a network.
The EMA Director Model defines a management platform, called a
director and cooperating but independent software components named
'management modules'. The DECmcc Director is comprised of a director
and management modules of the following types.
- Access Modules (AMs) provide access to and information about
different classes of entities.
- Function Modules (FMs) provide high-level management functions
for managed entities.
- Presentation Modules (PMs) provide a consistent user interface
for Function modules.
The core of the DECmcc software is the Executive which consists of a
management kernel and a set of 'function modules'. The Executive also
includes includes a Management Information Repository (MIR) which
defines a consistent structure for viewing management data. Together
they form DECmcc's operating environment for co-existence and
interoperation of management modules.
The DECmcc Director software allows a user to observe and control a
selected group of DECnet-VAX Phase IV and many other entities from a
common command syntax and a consistent user interface. The DECmcc
command syntax is compliant with Digital's Network Control Language
(NCL), the command line syntax used for network management commands.
Other classes of entities may be managed through additional access
modules enrolled in the DECmcc Director software.
With proper planning, deployment, and use, DECmcc management systems
are scalable to the size of the network, ranging from a small,
homogeneous local area network to an enterprise-wide, multivendor,
distributed environment. DECmcc software supports either, or both,
centralised or distributed management styles.
The DECmcc Director is a single-license product consisting of
EMA-compliant DECmcc Executive and Management Modules. The following
is a list of the software components and modules that comprise the
DECmcc Director.
EXECUTIVE
The DECmcc EXECUTIVE provides the environment in which DECmcc software
management modules operate, allowing them to communicate with each
other and with management information stored in the MIR. The DECmcc
EXECUTIVE consists of the management kernel, function modules, and the
MIR.
^ Management Kernel
The management kernel provides the operating environment, and
dispatching services for 'access' and 'function' modules. The
operating environment consists of a multi-threaded processing system,
contained within VMS processes, along with a set of callable
procedures.
^ EXECUTIVE Function Modules
- Control FM
The Control FM makes access to primitive directives for observation
and control of entities in the network available. It also makes data
available to end-users for arbitrary entities, with arbitrary
directives and attributes. The Control FM supports a pre-defined list
of basic directives, plus a small set of generic directives that can
be used for different purposes by different AMs.
- Registration FM
The Registration FM, in conjunction with the Distributed Name
Server (DECdns) manages data identifying each entity in a network.
It also defines and manages a set of common reference attributes for
all entities. The Registration FM uses DECdns as the DECmcc instance
repository, this allows multiple DECmcc systems to share the same
view of entity configurations.
^ MIR
The MIR is an integrated repository that contains definitions of
entity classes, entity instances, entity attributes, lists of specific
entities, and private or miscellaneous data required by individual
management modules. The MIR provides storage and access routines for
maintaining management information with within DECmcc software. Data
stored in the MIR is structured according to the EMA entity model,
which is consistent with the ISO/OSI Structure of Management
Information (SMI).
ACCESS MODULES
^ DECnet Phase IV AM
The DECnet Phase IV AM lets you manage DECnet Phase IV entities such
as nodes, circuits, lines, and objects. The DECnet Phase IV AM
provides an access path to and information about the entities it
supports. The DECnet Phase IV AM supports one global entity class,
NODE4, and a number of child entity classes. Typical management
operations include creating a NODE4 entity's knowledge of a child
entity, displaying information about an entity, and modifying an
entity's attributes.
^ Sample AM
A Sample Access Module is included as part of the DECmcc Director.
The Sample AM implements a single management directive, the SHOW
directive, for the DECnet Phase IV node entity and associated line
subentity. The SHOW directive displays various Characteristic,
Status and Counter attributes for each entity. The Sample Access
Module implements a SHOW and TEST management directive to manage the
Access Module itself to illustrate the "management of management"
concept. Including the Sample AM with the DECmcc Director is intended to
ensure proper end-user licensing of access modules developed using source
code provided in the DECmcc Toolkit (SPD 32.49.XX).
PRESENTATION MODULES
^ Command Line
The terminal presentation module is a terminal based user interface,
using command line input and output techniques. It is a command-line
interface compliant with Digital's NCL, the command line syntax used
for network management commands.
The terminal presentation module is available from any terminal or
workstation compatible with Digital's VT220 terminal. It supports
command-line recall and editing, abbreviation support, on-line help,
symbol substitution, support of control key sequences, line
continuation, and typeahead.
The user interface structure also allows a VMS DCL process to be
"spawned".
^ Forms Interface
The forms interface is an extension of the command-line interface that
provides a screen based user interface, using forms and list input and
output techniques. It is available from any terminal or workstation
compatible with Digital's VT220 terminal.
The screen format contains two regions. One region is for entering
data to input fields for issuing DECmcc commands or 'directives'. The
other region is for viewing data or output resulting from DECmcc
directives. Arrow keys, Previous and Next screen keys may be used for
reviewing the data in the output region.
UTILITIES
Several utilities are included that enable on-site enrollment of access
modules not provided with the DECmcc Director. Documentation required
for such module enrollment is supplied by the module developer. The
utilities are:
- Dictionary Access Program (DAP) Utility,
- Parse Table Builder (PTB) Utility,
- Test Bed Driver (TBD) Utility,
- Help File Builder (HFB) Utility
The DECmcc Developer's Toolkit Reference (order number AA-PD5MA-TE) manual
describes each of the tools in detail.
ON-LINE HELP INFORMATION
DECmcc includes extensive online information similar to VMS HELP.
Help information is provided in the following four categories: Entity
information, Function information, Presentation information, and
Tutorial information.
HARDWARE REQUIREMENTS
VAX, MicroVAX, or VAXstation configurations as specified in the System
Support Addendum (SSA 32.46.00A)
SOFTWARE REQUIREMENTS
VMS Operating System
Layered products:
DECnet-VAX to match VMS
DECdns Server to match VMS (must be somewhere in network)
For Workstations Running DECwindows
VMS Operating System (and necessary components of DECwindows)
Please refer to the System Support Addendum (SSA 32.46.00A) for
required versions of prerequisite or optional software.
ORDERING INFORMATION
Software License: QL-VM9A9-AA
Software Media: QL-VM9AA-H5
Software Documentation: QL-VM9AA-GZ
Software Product Services: QT-VM9A*-**
* Denotes variant fields. For additional information on available
licenses, services and media refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of DIGITAL's
Standard terms and conditions. For more information about DIGITAL's
licensing terms and policies, please contact your local DIGITAL
office.
LICENSE MANAGEMENT FACILITY
This product supports the VMS License Management Facility (LMF).
License units for this product are allocated at a flat price basis,
regardless of User/Activity or processor type.
For more information on the LMF refer to the VMS Operating System
Software Product Description (SPD 25.01.xx) or the LMF manual of the
VMS Operating System documentation set.
For more information about DIGITAL's licensing terms and policies,
please contact your local DIGITAL office.
SOFTWARE PRODUCT SERVICES
o Layered Product Support (LPS)
Layered Product Support provides the right-to-use new versions of
layered software. It also extends the level of support provided on
the kernel software to include coverage of the layered software
product. Layered Product Support is required for all Digital layered
software running on a system covered by Full Support. LPS is a
prerequisite for the service options listed below.
o Media and Documentation Distribution Service (MDDS)
Ensures customers have access to the latest software versions of
media and documentation updates. MDDS is ordered on a per product
basis.
o Documentation Update Service
Ensures that users receive documentation updates for software manuals
as they are released.
o Initial Software Installation
Installation by Digital of newly purchased software on a per product
basis.
Other Network Management Services are also available. These include,
but are not restricted to, the following:
o Network Management Operations Services
o Network Management Planning and Design Services
o Network Management Implementation Services
o Network Management Training
For local availability, please contact your Digital Sales Office.
SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL with the
purchase of a license for the product as defined in the Software
Warranty Addendum of this SPD.
September 1990
--------------------------------------------------------------------------
SYSTEM SUPPORT ADDENDUM
PRODUCT NAME: DECmcc Director, V1.0 SSA: 32.46.00-A
MINIMUM HARDWARE REQUIRED
VAX :
VAX 6000 Model 200 Series,
VAX 6000 Model 300 Series,
VAX 6000 Model 400 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350,
VAX 8500, VAX 8530, VAX 8550, VAX 8600,
VAX 8650, VAX 8700, VAX 8800, VAX 8810,
VAX 8820, VAX 8830, VAX 8840, VAX 8842,
VAX 8974, VAX 8978
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX :
MicroVAX II, MicroVAX 2000, MicroVAX 3300, MicroVAX 3400, MicroVAX
3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation :
VAXstation II, VAXstation 2000, VAXstation 3100 Series
VAXstation 3200, VAXstation 3500, VAXstation 3520,
VAXstation 3540,
VAXserver :
VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600,
VAXserver 3602, VAXserver 3800, VAXserver 3900, VAXserver 6210,
VAXserver 6220, VAXserver 6310, VAXserver 6320
Processors not supported:
VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I,
VAXstation 8000
A TK50 Tape Drive is required for stand-alone MicroVAX 2000 and
VAXstation 2000 systems.
Processors not supported:
VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I,
VAXstation 8000
Block space requirements (Block Cluster Size = 1):
Disk space required for installation: 44500 blocks
Disk space required for use (permanent): 43377 blocks
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's
system environment, configuration, and software options.
OPTIONAL HARDWARE
None
International Support:
None
CLUSTER ENVIRONMENT
This layered product is fully supported when installed on any valid
and licensed VAXcluster* configuration without restrictions. The
MINIMUM HARDWARE section of this product's Software Product
Description and System Support Addendum detail any special hardware
required by this product.
* V5.x VAXcluster configurations are fully described in the VAXcluster
Software Product Description (29.78.xx) and include CI, NI and Mixed
Interconnect configurations.
PREREQUISITE SOFTWARE
VMS Operating System V5.3
Layered Products:
DECnet-VAX V5.0 - V5.3
DECdns V1.2
For Workstations Running DECwindows
VMS Operating System V5.3 (and necessary components of
DECwindows)
Layered Products:
DECnet-VAX V5.3
DECdns V1.2
VMS Tailoring
The following VMS classes are required for full functionality of this
layered product:
VMS REQUIRED SAVESET
NETWORK SUPPORT
PROGRAMMING SUPPORT
UTILITIES
For more information on VMS classes and tailoring, refer to the
VAX/VMS Operating System Software Product Description (SPD 25.01.xx).
OPTIONAL SOFTWARE
DECmcc Site Management Station v2.0
DECmcc Enterprise Management Station v2.0
GROWTH CONSIDERATION
The minimum hardware and software requirements for any future version
of this product may be different from the minimum hardware and
software requirements for the current version.
DISTRIBUTION MEDIA
TK50 Streaming Tape
ORDERING INFORMATION
Software License: QL-VM9A9-AA
Software Media: QL-VM9AA-H5
Software Documentation: QL-VM9AA-GZ
Software Product Services: QT-VM9A*-**
* Denotes variant fields. For additional information on available
licenses, services and media refer to the appropriate price book.
The above information is valid at time of release. Please contact
your local DIGITAL office for most up-to-date information.
September 1990
|
| 426.4 | DECmcc Basic Mgt System v1.0 SPD | DELNI::D_HOLLAND | | Fri Oct 26 1990 11:13 | 493 |
| If you copy or extract THIS text version of the SPD for a
customer please mention that it is PRELIMINARY until it
appears on VTX or with the software kit from manufactur-
ing.
PRODUCT NAME: DECmcc Basic Management System, V1.0 SPD 32.48.00
The DECmcc(TM) software implements Digital's Enterprise Management
Architecture (EMA) director model, consistent with the ISO/OSI
management framework. The DECmcc Basic Management System (BMS) software,
initially implemented under VMS Operating Systems, lets users control,
monitor, and test manageable objects (entities) in a network.
The EMA Director Model defines a management platform, called a
director and cooperating but independent software components named
'management modules'. DECmcc BMS V1.0 is comprised of a director and
management modules of the following types.
- Access Modules (AMs) provide access to and information about
different classes of entities.
- Function Modules (FMs) provide high-level management functions
for managed entities.
- Presentation Modules (PMs) provide a consistent user interface
for Function modules.
The core of the DECmcc software is the Executive which consists of a
management kernel and a set of 'function modules'. The Executive also
includes includes a Management Information Repository (MIR) which
defines a consistent structure for viewing management data. Together
they form DECmcc's operating environment for co-existence and
interoperation of management modules.
The DECmcc BMS software allows a user to observe and control a selected
group of DECnet-VAX Phase IV and many other entities from a common
command syntax and a consistent user interface. The DECmcc command
syntax is compliant with Digital's Network Control Language (NCL), the
command line syntax used for network management commands. Other
classes of entities may be managed through additional access modules
enrolled in the DECmcc BMS software.
With proper planning, deployment, and use, DECmcc management systems
are scalable to the size of the network, ranging from a small,
homogeneous local area network to an enterprise-wide, multivendor,
distributed environment. DECmcc software supports either, or both,
centralised or distributed management styles.
The DECmcc BMS is a single-license product consisting of
EMA-compliant DECmcc Executive and Management Modules. The following
is a list of DECmcc software components and modules that comprise
DECmcc BMS.
EXECUTIVE
The DECmcc EXECUTIVE provides the environment in which DECmcc software
management modules operate, allowing them to communicate with each
other and with management information stored in the MIR. The DECmcc
EXECUTIVE consists of the management kernel, function modules, and the
MIR.
^ Management Kernel
The management kernel provides the operating environment, and
dispatching services for 'access' and 'function' modules. The
operating environment consists of a multi-threaded processing system,
contained within VMS processes, along with a set of callable
procedures.
^ EXECUTIVE Function Modules
- Control FM
The Control FM makes access to primitive directives for observation
and control of entities in the network available. It also makes data
available to end-users for arbitrary entities, with arbitrary
directives and attributes. The Control FM supports a pre-defined list
of basic directives, plus a small set of generic directives that can
be used for different purposes by different AMs.
- Registration FM
The Registration FM, in conjunction with the Distributed Name
Server (DECdns) manages data identifying each entity in a network.
It also defines
and manages a set of common reference attributes for all entities.
The Registration FM uses DECdns as the DECmcc instance repository, this
allows multiple DECmcc systems to share the same view of entity
configurations.
^ MIR
The MIR is an integrated repository that contains definitions of
entity classes, entity instances, entity attributes, lists of specific
entities, and private or miscellaneous data required by individual
management modules. The MIR provides storage and access routines for
maintaining management information within the DECmcc software. Most
data stored in the MIR is structured according to the EMA entity
model.
ACCESS MODULES
^ DECnet Phase IV AM
The DECnet Phase IV AM lets you manage DECnet Phase IV entities such
as nodes, circuits, lines, and objects. The DECnet Phase IV AM
provides an access path to and information about the entities it
supports. The DECnet Phase IV AM supports one global entity class,
NODE4, and a number of child entity classes. Typical management
operations include creating a NODE4 entity's knowledge of a child
entity, displaying information about an entity, and modifying an
entity's attributes.
^ Ethernet Station AM
The Ethernet Station AM provides looptest and display of generic
Ethernet devices that support: MOP REQID, MOP SYSID, MOP Counters,
Ethernet V2 LOOPBACK, IEEE802.3 XID, or IEEE802.3 TEST. The
Ethernet Station AM also provides Ethernet control and monitoring
functions that can be used by other management modules within the
DECmcc system.
^ Bridge AM
The Bridge AM enables users to control and monitor any Digital LAN
Bridge 100, 150 or 200 in an extended LAN environment. In addition,
this module provides an executable procedure to aid in the populating
of the DECmcc software database with information contained in an
existing Remote Bridge Management Software (RBMS) database.
^ Sample AM
A Sample Access Module is included as part of the DECmcc BMS.
The Sample AM implements a single management directive, the SHOW
directive, for the DECnet Phase IV node entity and associated line
subentity. The SHOW directive displays various Characteristic,
Status and Counter attributes for each entity. The Sample Access
Module implements a SHOW and TEST management directive to manage the
Access Module itself to illustrate the "management of management"
concept. Including the Sample AM with the DECmcc BMS is intended to
ensure proper end-user licensing of access modules developed using source
code provided in the DECmcc Toolkit (SPD 32.49.XX).
FUNCTION MODULES
^ Alarms FM
The Alarms FM provides the ability to notify network managers that
alarm conditions have been detected in the network. The DECmcc Alarms
FM can detect alarm conditions about any entity that has an
appropriate access module. When an alarm condition is detected, a
user-written command procedure is queued for execution. The DECmcc
Alarms FM includes sample rules for alarm conditions and sample
command procedures that can be used directly (e.g., to log, broadcast
and mail alarms) or used as examples that can be modified.
PRESENTATION MODULES
^ Command Line
The terminal presentation module is a terminal based user interface,
using command line input and output techniques. It is a command-line
interface compliant with Digital's NCL, the command line syntax used
for network management commands.
The terminal presentation module is available from any terminal or
workstation compatible with Digital's VT220 terminal. It supports
command-line recall and editing, abbreviation support, on-line help,
symbol substitution, support of control key sequences, line
continuation, and typeahead.
The user interface structure also allows a VMS DCL process to be
"spawned".
^ Forms Interface
The forms interface is an extension of the command-line interface that
provides a screen based user interface, using forms and list input and
output techniques. It is available from any terminal or workstation
compatible with Digital's VT220 terminal.
The screen format contains two regions. One region is for entering
data to input fields for issuing DECmcc commands or 'directives'. The
other region is for viewing data or output resulting from DECmcc
directives. arrow keys, previous and next screen keys may be used for
reviewing the data in the output region.
UTILITIES
Several utilities are included that enable on-site enrollment of access
modules not provided with the DECmcc BMS. Documentation required for such
module enrollment is supplied by the module developer. The utilities are:
- Dictionary Administrator Program (DAP) Utility,
- Parse Table Builder (PTB) Utility,
- Test Bed Driver (TBD) Utility,
- Help File Builder (HFB) Utility
The DECmcc Developer's Toolkit Reference (order number AA-PD5MA-TE) manual
describes each of the tools in detail.
ON-LINE HELP INFORMATION
DECmcc includes extensive online information similar to VMS HELP.
Help information is provided in the following four categories: Entity
information, Function information, Presentation information, and
Tutorial information.
HARDWARE REQUIREMENTS
VAX, MicroVAX, or VAXstation configurations as specified in the System
Support Addendum (SSA 32.46.00A)
SOFTWARE REQUIREMENTS
VMS Operating System
Layered products:
DECnet-VAX to match VMS Operating System
DECdns Server to match VMS (must be somewhere in network)
For Workstations Running DECwindows
VMS Operating System (and necessary components of DECwindows)
Please refer to the System Support Addendum (SSA 32.46.00A) for
required versions of prerequisite or optional software.
ORDERING INFORMATION
Software License: QL-YSUA9-AA
Software Media: QL-YSUAA-H5
Software Documentation: QL-YSUAA-GZ
Software Product Services: QT-YSUA*-**
* Denotes variant fields. For additional information on available
licenses, services and media refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of DIGITAL's
Standard terms and conditions. For more information about DIGITAL's
licensing terms and policies, please contact your local DIGITAL
office.
LICENSE MANAGEMENT FACILITY
This product supports the VMS License Management Facility (LMF).
License units for this product are allocated at a flat price basis,
regardless of User/Activity or processor type.
For more information on the LMF refer to the VMS Operating System
Software Product Description (SPD 25.01.xx) or the LMF manual of the
VMS Operating System documentation set.
For more information about DIGITAL's licensing terms and policies,
please contact your local DIGITAL office.
SOFTWARE PRODUCT SERVICES
o Layered Product Support (LPS)
Layered Product Support provides the right-to-use new versions of
layered software. It also extends the level of support provided on
the kernel software to include coverage of the layered software
product. Layered Product Support is required for all Digital layered
software running on a system covered by Full Support. LPS is a
prerequisite for the service options listed below.
o Media and Documentation Distribution Service (MDDS)
Ensures customers have access to the latest software versions of
media and documentation updates. MDDS is ordered on a per product
basis.
o Documentation Update Service
Ensures that users receive documentation updates for software manuals
as they are released.
o Initial Software Installation
Installation by Digital of newly purchased software on a per product
basis.
Other Network Management Services are also available. These include,
but are not restricted to, the following:
o Network Management Operations Services
o Network Management Planning and Design Services
o Network Management Implementation Services
o Network Management Training
For local availability, please contact your Digital Sales Office.
SOFTWARE WARRANTY
Warranty for this software product is provided by DIGITAL with the
purchase of a license for the product as defined in the Software
Warranty Addendum of this SPD.
September 1990
--------------------------------------------------------------------------
SYSTEM SUPPORT ADDENDUM
PRODUCT NAME: DECmcc Basic Management System V1.0 SSA: 32.48.00A
VAX :
VAX 6000 Model 200 Series,
VAX 6000 Model 300 Series,
VAX 6000 Model 400 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350,
VAX 8500, VAX 8530, VAX 8550, VAX 8600,
VAX 8650, VAX 8700, VAX 8800, VAX 8810,
VAX 8820, VAX 8830, VAX 8840, VAX 8842,
VAX 8974, VAX 8978
VAX-11/750, VAX-11/780, VAX-11/785
MicroVAX :
MicroVAX II, MicroVAX 2000, MicroVAX 3300, MicroVAX 3400, MicroVAX
3500, MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation :
VAXstation II, VAXstation 2000, VAXstation 3100 Series
VAXstation 3200, VAXstation 3500, VAXstation 3520,
VAXstation 3540,
VAXserver :
VAXserver 3300, VAXserver 3400, VAXserver 3500, VAXserver 3600,
VAXserver 3602, VAXserver 3800, VAXserver 3900, VAXserver 6210,
VAXserver 6220, VAXserver 6310, VAXserver 6320
Processors not supported:
VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I,
VAXstation 8000
A TK50 Tape Drive is required for stand-alone MicroVAX 2000 and
VAXstation 2000 systems.
Processors not supported:
VAX-11/725, VAX-11/730, VAX-11/782, MicroVAX I, VAXstation I,
VAXstation 8000
Block space requirements (Block Cluster Size = 1):
Disk space required for installation: 50500 blocks
Disk space required for use (permanent): 48954 blocks
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's
system environment, configuration, and software options.
OPTIONAL HARDWARE
None
International Support:
None
CLUSTER ENVIRONMENT
This layered product is fully supported when installed on any valid
and licensed VAXcluster* configuration without restrictions. The
MINIMUM HARDWARE section of this product's Software Product
Description and System Support Addendum detail any special hardware
required by this product.
* V5.x VAXcluster configurations are fully described in the VAXcluster
Software Product Description (29.78.xx) and include CI, NI and Mixed
Interconnect configurations.
PREREQUISITE SOFTWARE
For Systems Using Terminals (No DECwindows Interface)
VMS Operating System V5.3
Layered Products:
DECnet-VAX V5.0 - V5.3
DECdns V1.2
For Workstations Running DECwindows
VMS Operating System V5.3 (and necessary components of
DECwindows)
Layered Products:
DECnet-VAX V5.0 - V5.3
DECdns V1.2
VMS Tailoring
The following VMS classes are required for full functionality of this
layered product:
VMS REQUIRED SAVESET
NETWORK SUPPORT
PROGRAMMING SUPPORT
UTILITIES
For more information on VMS classes and tailoring, refer to the
VAX/VMS Operating System Software Product Description (SPD 25.01.xx).
OPTIONAL SOFTWARE
None
GROWTH CONSIDERATION
The minimum hardware and software requirements for any future version
of this product may be different from the minimum hardware and
software requirements for the current version.
DISTRIBUTION MEDIA
TK50 Streaming Tape
ORDERING INFORMATION
Software License: QL-YSUA9-AA
Software Media: QL-YSUAA-H5
Software Documentation: QL-YSUAA-GZ
Software Product Services: QT-YSUA*-**
* Denotes variant fields. For additional information on available
licenses, services and media refer to the appropriate price book.
The above information is valid at time of release. Please contact
your local DIGITAL office for most up-to-date information.
September 1990
|
| 426.5 | When will we receive the new documentation (SRM, MM-PROGRAMMING, etc) ? | BYBLOS::TAMER | | Wed Oct 31 1990 09:58 | 3 |
| When will the internal AM developers receive the new documentation, especially
the SRM and the MM-PROGRAMMING guide ?
|
| 426.6 | DECmcc SMS V2.0 SPD/SSA | DELNI::L_FELICE | | Tue Nov 20 1990 08:53 | 790 |
| If you copy or extract THIS text version of the SPD for a
customer, please mention that it's PRELIMINARY until it's
on VTX or with the software kit from manufacturing.
DECmcc(TM) Site Management Station, Version 2.0 SPD 31.87.01
DESCRIPTION
DECmcc Site Management Station (DECmcc SMS) is a network management
software product designed to provide network managers with a complete set of
applications to manage wide area heterogeneous networks.
The DECmcc Site Management Station consolidates Digital Equipment
Corporation's network management applications within a DECwindows environment
and provides the capability of running all applications on a single system.
It consists of products that are compliant with Digital's Enterprise Management
Architecture (EMA) as well as products that are not EMA-compliant. As such,
DECmcc SMS is a transition vehicle to an EMA-compliant product set within
a single software product.
DECmcc SMS V2.0 consists of the following Digital network management products:
o DECmcc Basic Management System (BMS)
o LAN Traffic Monitor (LTM) VMS
o Extended LAN Management Software (DECelms)
o NMCC/VAX ETHERnim
o Terminal Server Manager (TSM)
DECelms supersedes Remote Bridge Management Software (RBMS) in DECmcc SMS V2.0.
Also new to DECmcc SMS V2.0 is the DECmcc Basic Management System (BMS), a
product consisting of EMA-compliant software modules.
In addition to containing the products listed above, DECmcc SMS supports
the ability to install and run other VMS layered products within a DECwindows
environment. DECmcc SMS also provides access to non-Digital management
products that are based on X11 standards. Such products can be installed
on the same or separate processors as DECmcc SMS for the purpose of
consolidating interfaces on a single workstation display. Also included with
the DECmcc SMS components is the Network Troubleshooting Guide. Available
through the Bookreader application, the Network Troubleshooting Guide provides
DECmcc SMS users with a systematic, on-line approach to solving some of the
most common problems that occur on DECnet-VAX, DECnet-ULTRIX, Ethernet, and
TCP/IP networks.
DECmcc Basic Management System
The DECmcc Basic Management System (BMS) is a set of EMA-compliant products
based on an implementation of the EMA Director Model. EMA, which is consistent
with the the ISO/OSI management framework, defines a model for a management
system. The EMA-compliant DECmcc software enables users to control, monitor,
and test manageable objects (entities) in a network.
The EMA Director Model defines a management platform, called a director, and
cooperating but independent software components named Management Modules.
DECmcc BMS is comprised of a director and management modules of the following
types.
o Access Modules (AMs) provide access to and information about
different classes of entities.
o Function Modules (FMs) provide high-level management functions
for managed entities.
o Presentation Modules (PMs) provide a consistent user interface
for Function modules.
The core of the EMA-compliant DECmcc software is the Executive, which
consists of a management kernel and a set of 'function modules'. The
Executive also includes a Management Information Repository (MIR),
which defines a consistent structure for, and storage of management data.
Together they form DECmcc's operating system-like environment for co-existence
and interoperation of management modules.
DECmcc BMS consists of EMA-compliant DECmcc Executive and Management
Modules, and is available both as a standalone product and as a component
of DECmcc SMS. The following is a list of the EMA-compliant components and
modules that comprise DECmcc BMS.
o Executive -- provides the environment in which DECmcc software management
modules operate, allowing them to communicate with each other and with
management information stored in the MIR. The DECmcc Executive consists
of the management kernel, function modules, and the MIR.
- Management Kernel: the management kernel provides the operating
environment and dispatching services for management modules.
The operating environment consists of a multi-threaded processing system,
contained within VMS processes, along with a set of callable procedures.
- Executive Function Modules (Control FM and Registration FM): the Control
FM makes available to users primitive directives for observation and
control of entities in the network. It also makes data available to
end-users for arbitrary entities, with arbitrary directives and
attributes. The Control FM supports a pre-defined list of basic
directives, plus a small set of generic directives that can be used for
different purposes by different AMs. The Registration FM, in conjunction
with the Digital Distributed Name Server (DECdns (TM)) manages data
identifying each entity in a network. It also defines and manages a set
of common reference attributes for all entities. The Registration FM
uses DECdns as the DECmcc instance repository, which allows multiple
DECmcc systems to share the same view of entity configurations.
- Management Information Repository (MIR): the MIR is an integrated data
base that contains definitions of entity classes, entity instances,
entity attributes, and private or miscellaneous data required by
individual management modules. The MIR provides storage and access
routines for maintaining management information within DECmcc software.
Most data stored in the MIR is structured according to the EMA Entity
Model.
o DECnet Phase IV Access Module -- enables users to manage DECnet Phase
IV entities and child entities such as nodes, circuits, lines, and
objects. The DECnet Phase IV AM provides an access path to and information
about the entities it supports. The DECnet Phase IV AM supports one global
entity class, NODE4, and a number of child entity classes. Typical
management operations include creating a NODE4 entity's knowledge of a
child entity, displaying information about an entity, and modifying an
entity's attributes.
o Ethernet Station Access Module -- provides looptest and display of generic
Ethernet devices that support: MOP REQID, MOP SYSID, MOP Counters,
IEEE802.2 XID, or IEEE802.2 TEST. The Ethernet Station AM also provides
Ethernet control and monitoring functions that can be used by other
management modules within the DECmcc system.
o Bridge Access Module -- enables users to control and monitor any
Digital LANbridge 100, 150 or 200 in an extended LAN environment. In
addition, this module provides an executable procedure to aid in the
populating of the DECmcc software database with information contained in
an existing Remote Bridge Management Software (RBMS) database.
o Sample Access Module -- is included as part of the DECmcc BMS. The sample
AM implements a single management directive, the SHOW directive, for the
DECnet Phase IV node entity and associated line subentity. The SHOW
directive displays various Characteristic, Status, and Counter attributes
for each entity. The Sample Access Module implements a SHOW and TEST
management directive to manage the Access Module itself to illustrate
the "management of management" concept. Including the Sample AM with the
DECmcc BMS is intended to ensure proper end-user licensing of access
modules developed using source code provided in the DECmcc Toolkit
(SPD 32.49.XX).
o Alarms Function Module -- provides the ability to notify network managers
that alarm conditions have been detected in the network. The DECmcc
Alarms FM can detect alarm conditions about any entity that has an
appropriate access module. When an alarm condition is detected, a user-
written command procedure is queued for execution. For example, it may be
useful to write command procedures that trigger the local system's mail
facility to deliver alarm messages. The DECmcc Alarms FM includes sample
rules for alarm conditions and sample command procedures that can be used
directly (e.g., to log, broadcast and mail alarms) or used as examples that
can be modified.
o Command Line Presentation Module -- supports a terminal based user
interface, using command line input and output techniques. It is a
command-line interface compliant with Digital's NCL, the command line
syntax used for DECnet/OSI Phase V network management commands. The
Command Line Presentation Module is available from any terminal or
workstation compatible with Digital's VT220 terminal. It supports
command-line recall and editing, abbreviation support, on-line help,
symbol substitution, support of control key sequences, line continuation,
and typeahead. The user interface structure also allows a VMS DCL process
to be 'spawned'.
o Forms Interface Presentation Module -- is an extension of the
command-line interface that provides a screen-based user interface, using
forms and list input and output techniques. It is available from any
terminal or workstation compatible with Digital's VT220 terminal.
The screen format contains two regions. One region is for entering data to
input fields for issuing DECmcc commands or 'directives'. The other region
is for viewing data resulting from DECmcc directives.
o Utilities -- Several utilities are included that enable the on-site
enrollment of management modules not provided with the DECmcc BMS.
Documentation required for such enrollment is provided by the module
developer. The utilities are:
- Dictionary Administrator Program (DAP) Utility
- Parse Table Builder (PTB) Utility
- Test Bed Driver (TBD) Utility
- Help File Builder (HFB) Utility
The DECmcc Developer's Toolkit Reference Manual (order number AA-PD5MA-TE)
describes each of the tools in detail.
LAN Traffic Monitor VMS
The LAN Traffic Monitor VMS (LTM) is the software portion of a fully
distributed monitor that can support the capture and presentation of
traffic data from an extended Ethernet. A LAN Bridge 100 or LAN Bridge
150, downline loaded with monitoring software, is attached to the Ethernet
cable and transmits information to a VMS layered application software program
located on any VAX in the extended LAN. Multiple users, from different nodes
on the extended Ethernet, may access the traffic data. LAN Traffic Monitor
also works with Chipcom's(R) Broadband Bridges called Ethermodem(TM) III
Bridges.
LAN Bridge hardware can run either as a LAN Traffic Monitor or as a LAN
Bridge, i.e., the primary building block of the Extended LAN (Local Area
Network) architecture. An Extended LAN is a collection of LANs that are
interconnected and logically appear as one large Local Area Network.
Note that when a bridge is used as a monitoring device or listener, it does
not function as a bridge. Users can remotely switch a bridge between
monitoring and standard bridge modes using Digital's DECelms (Extended LAN
Management Software).
With the LAN Bridge designed to work at full Ethernet speed, the LAN
Traffic Monitor can provide real-time data on Ethernet LAN throughput
and utilization, allowing a customer to actively monitor their Ethernet
usage. The ability to collect data on any protocol type (i.e. LAT,
802.3, DECnet, TCP/IP, etc.) on the Ethernet is provided.
LAN Traffic Monitor contains the LTM Listener software (which counts
and classifies Ethernet traffic using a LAN Bridge as a monitoring
device) and the LTM User Interface (which collects and displays data
received from the LTM Listener).
The LTM Listener periodically reports traffic statistics to the LTM User
Interface located on a VAX host. The LTM User Interface receives
unsolicited Ethernet datagrams generated by the LTM Listener, and
through the menu structure, the user can also ask the LTM Listener for
additional data not found in the unsolicited messages. A single LTM host
can be used in conjunction with multiple LTM listeners.
The LTM User Interface performs the necessary data reduction and
presents the statistics in logical groupings. Summary displays, which
are presented in tabular format include Network Traffic, Top Ten Talkers, and
Throughput and Utilization. LTM also displays Lists of Nodes, Multicast
Addresses, Protocols Used by Nodes, Node Traffic by Protocol Type, Multicast
Traffic by Protocol Type, and Protocol Type Traffic.
In addition, LAN utilization based on the most recent traffic data received
from the LTM Listener may be displayed graphically in intervals of one, four,
eight, twelve, twenty-four, or forty-eight hours.
DECelms
DECelms (Extended Local Area Network Management Software) enables users to
configure, manage, monitor, control, and observe any LAN Bridge and FDDI
Wiring Concentrator in an extended Ethernet/802.3 LAN and FDDI network
environment. Supported devices include Digital's LAN Bridge 100, LAN Bridge
150, LAN Bridge 200, DECbridge 500, DECconcentrator 500, METROwave, and
Chipcom's Ethermodem Broadband Bridge. DECelms is comprised of VAX host
software and corresponding firmwear that resides in the LAN Bridges and FDDI
DECconcentrators.
A superset of RBMS V2.0 functions, DECelms provides remote management
capabilities for FDDI and Ethernet devices. Using DECelms, users can:
o Observe, monitor, and control interoperable FDDI and Ethernet networks.
o Display and modify a devices, lines, physical ports, and forwarding database
characteristics.
o Enable and disable lines and physical ports.
o Automatically build a host registry of all reachable FDDI DECconcentrators
and LAN Bridges within extended LAN and FDDI environments.
o Automatically or manually poll the devices stored in the host registry
for faults, errors, and changed information.
o Display error conditions to an alarms window and record detailed information
in an error log file.
o Process the logfile keying off time or type of faults.
o Use standard VMS utilities like print, type, search, etc, on the ASCII
formatted versions of the DECelms error log file.
o Display data-link counters, status and characteristics.
o Modify parameters such as operational state, forwarding database,
and spanning tree characteristics.
o Remotely invoke a device's self-test capabilities.
o Associate ASCII names with specific device physical addresses for ease of
use in management commands.
o Display the logical FDDI network topology through ring mapping.
DECelms also provides simultaneous access by more than one user, supports
command line recall, and password protection for setable parameters on Digital
LAN Bridge 150s, 200s, 500s, and FDDI DECconcentrators.
NMCC/VAX ETHERnim
NMCC/VAX ETHERnim is a network management application that
provides the network manager with a tool to gather information about
Ethernet nodes, verify reachability of nodes, provide a graphical
display of local area network topology and monitor Ethernet traffic.
NMCC/VAX ETHERnim consists of two categories of software, one of which
must be installed on a VMS system set up as the Host, and the other
which can be optionally installed on Target systems running VMS. In
this context, the Host is defined as the node on which the NMCC/VAX
ETHERnim application runs, while the Target systems are those DECnet
nodes on the Ethernet segments which are being tested at the User (task)
level. The optional software installed on the Target system is referred
to as the Remote Files.
The Host software requires Phase IV DECnet software on a VMS system.
When this software has been installed, the network manager has the
ability to:
o Build a permanent database containing basic information about each node
directly connected to the Ethernet local area network through user commands
and automatic procedures.
o Manually construct and maintain a topological view of the network,
including transparent network devices (e.g., DEMPR, DELNI, DEREP).
o Test the Ethernet network to help isolate and identify problems
o Test the communications path to each node up to the DNA
application layer by performing a loopback test to a specified
user account. This feature is available only for VMS Target
systems.
o Monitor the network to determine which nodes are the top talkers
and which nodes are the top listeners; sort/display traffic by
protocol type or multi-cast address; focus on traffic to/from a
specified node.
o Perform information access to properly configured DECnet nodes on the
Ethernet to determine the remote nodes's system type, hardware
configuration, and software configuration.
Terminal Server Manager
Terminal Server Manager VMS (TSM) software allows suitably privileged
users at a VAX host to control and observe terminal servers anywhere in
the extended local area network. TSM provides centralization and
increased flexibility in configuring, monitoring, and controlling
Digital's family of terminal servers.
Among the features supported by TSM are:
o Support for the 3270 Option Software for the CXM04 line card. This line
card provides capability of connectivity of 3270 class of terminals to
systems on Ethernet.
o Keyboard mapping, which enables the terminal server manager to customize
3270 keyboard tables supplied with the 3270 Option Software by changing the
way individual 3270 keyboard keys are mapped to Digital's VT220 keys.
o Wildcarding, which extends the wildcarding capability for server names by
allowing a wildcard character such as * and % to replace a server name
any place it appears in the syntax.
o A management directory that contains the name, Ethernet address,
terminal server type, and other fields for each server to be managed.
Through the TSM directory, the user need only to refer to the name of
the server in order to gain access.
o The ability to define logical groups of servers. A command can then be
executed for all servers in the partition. TSM provides a predefined
partition called ALL that includes all servers in the directory.
o Access to and manipulation of the database associated with each server
within its jurisdiction, including their characteristics and parameters.
o Management of the volatile characteristics for all terminal server types.
o Management of permanent NVRAM characteristics for the DECserver 100,
DECserver 200, and MUXserver 100. For the Ethernet Terminal Server and
DECserver 500, TSM modifies the permanent attributes contained within
the image files which are down-line loaded.
o Automated updates of the DECnet database for servers to match the
DECnet related information in the management directory. Users need no
longer employ a separate DSVCONFIG or TSVNCP configuration program.
o TSM server and directory commands may be issued as DCL commands; the
syntax follows DCL conventions.
o A USE command to allow selection of the server or servers to be managed
or the directory to be referenced. A single server, a user specified group
of servers (a partition), or all servers known via the management
directory can be selected with the USE command.
o Maintenance of command files outside of TSM (e.g., by use of a VMS
editor). This command file support allows values of characteristics
to be stored on the host, effectively creating a copy of the permanent
database that may be used to configure new servers. Server
maintenance is also enhanced by allowing the terminal server to be
easily box swapped, and parameters reset. Up to eight parameters may
be passed to TSM command files. Additionally, command files may
operate on a single server, on a logical group (a partition) of
servers or on all servers.
o Trouble shooting within the terminal server network through the ability
ability to centrally read traffic status and counters in addition to error
status and counters. With the PASTHRU command, the user can also connect
directly to the server without using TSM, allowing isolation of problems
between TSM and the server.
Network Troubleshooting Guide
The Network Troubleshooting Guide provides an on-line, systematic approach to
solving any network problem. Available through the Bookreader application,
its text can be displayed in a window within a DECmcc Management Station
environment. The Network Troubleshooting Guide gives specific step-by-step
instructions for solving some of the most common network problems that
occur on DECnet-VAX, DECnet-ULTRIX, Ethernet, and TCP/IP networks.
The Network Troubleshooting Guide incorporates information from various
sources into a single manual -- minimizing the documentation required for
solving network problems.
The Network Troubleshooting Guide covers:
o Background information on DECnet and TCP/IP networks.
o How to use a standard troubleshooting methodology to solve any
network problem.
o How to use network tools such as DECmcc Management Station for
ULTRIX, Network Control Program (NCP), NMCC/DECnet Monitor,
NMCC/VAX Ethernim, and LAN Traffic Monitor (LTM).
o How to use ULTRIX commands such as netstat, ping, and uerf.
o How to use log files and counters to gather information for
problem solving.
o How to trace a network path to isolate the source of a problem.
o How and when to perform loopback tests.
o In explicit step-by-step instructions, how to solve nearly 30 of
the most common network problems, including:
- Network partner exited (DECnet networks)
- Permission denied (TCP/IP networks)
- LAT Print Queue Problems (Ethernet networks)
INSTALLATION
Only experienced customers should attempt the installation of this
product. Digital recommends that all other customers purchase Digital's
installation and consulting services. These services provide for the
planning, implementation (product setup and startup) and customer
orientation on the product by an experienced Digital Software
Specialist. Customers should consult their local Digital offices to
obtain information of installation and start-up services available in
their locations.
HARDWARE REQUIREMENTS
VAX, MicroVAX, VAXstation or VAXserver configuration as specified in the
System Support Addendum (SSA 31.87.01-*).
LANbridge 100/150 for LTM Listener
SOFTWARE REQUIREMENTS*
For Systems Using Terminals (No DECwindows Interface):
VMS Operating System
DECnet-VAX
DECdns Server (must be somewhere in network)
For Workstations Running DECwindows:
VMS Operating System (and necessary components of DECwindows)
DECnet-VAX
DECdns Server (must be somewhere in network)
* Refer to the System Support Addendum (SSA 31.87.01-*) for
availability and required versions of prerequisite/optional
software.
ORDERING INFORMATION
Software Licenses: QL-YGLA9-AA
Software Media and Documentation: QA-YGLAA-H*
Software Documentation: QA-YGLAA-GZ
Software Product Services: QT-YGLA*-**
* Denotes variant fields. For additional information on available
licenses, services, and media, refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of Digital
Equipment Corporation's Standard Terms and Conditions. For more
information about Digital's licensing terms and policies, contact your
local Digital office.
LICENSE MANAGEMENT FACILITY SUPPORT
This product supports the VMS License Management Facility (LMF). License
units for this product are allocated at a flat price basis, regardless of
User/Activity or processor type.
For more information on the License Management Facility, refer to the
VMS Operating System Software Product Description (SPD 25.01.xx) or the
License Management Facility manual of the VMS Operation System
documentation set.
For more information about Digital's licensing terms and policies,
contact your local Digital office.
SOFTWARE PRODUCT SERVICES
o Layered Product Service (LPS) -- provides the right-to-use new versions
of layered software. It also extends the level of support provided on
the kernel software to include coverage of the layered software product.
LPS is required for all Digital layered software running on a system
covered by Full Support. LPS is a prerequisite for the following service
options.
- Media and Documentation Distribution Service (MDDS) -- ensures customers
have access to the latest software versions of media and documentation
updates. MDDS is ordered on a per product basis.
- Documentation Update Service -- ensures that users receive documentation
updated for software manuals as they are released.
- Initial Installation Service -- provides installation by Digital of
newly purchased software on a per product basis.
OTHER DIGITAL NETWORK SERVICES
To assist you in planning, designing, implementing, managing and
evolving your network, Digital offers a comprehensive portfolio of
network management services. These address, but are not restricted to,
the following:
o Network Planning and Design
o Physical Network Implementation
o Network Start-up and Implementation
o Network Performance Consulting
o Fault and Configuration Management
o Network Products' Training
o Shared NETsupport
o NETsupport
For local availability, please contact your Digital Sales Office.
SOFTWARE WARRANTY
Warranty for this software product is provided by Digital with the
purchase of a license for the product as defined in the Software
Warranty Addendum of this SPD.
November 1990
AE-PAWBB-TE
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation. Chipcom is a registered trademark of the Chipcom Corporation.
(TM) DECmcc, Ethernet, ETHERnim, DECnet, RBMS, DECelms, VAX, VMS, MicroVAX,
VAXstation, VAXserver, and VAXcluster are trademarks of Digital Equipment
Corporation. Ethermodem is a trademark of the Chipcom Corporation.
DECmcc Site Management Station, Version 2.0 SSA 31.87.01A
HARDWARE REQUIREMENTS
VAX: VAX 9000 Series, VAX 6000 Model 200 Series, VAX 6000 Model 300 Series,
VAX 6000 Model 400 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550,
VAX 8600, VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830,
VAX 8840, VAX 8842, VAX 8974, VAX 8978
VAX-11/780, VAX-11/785
MicroVAX: MicroVAX 3100, MicroVAX 3300, MicroVAX 3400, MicroVAX 3500,
MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation: VAXstation 3100 Series, VAXstation 3200, VAXstation 3500,
VAXstation 3520, VAXstation 3540
VAXserver: VAXserver 3100, VAXserver 3300, VAXserver 3400, VAXserver
3500, VAXserver 3600, VAXserver 3602, VAXserver 3800,
VAXserver 3900, VAXserver 6000-210, VAXserver 6000-310,
VAXserver 6000-410, VAXserver 6000-420
Processors Not Supported
VAX: VAX-11/725, VAX-11/730, VAX-11/750, VAX-11/782
MicroVAX: MicroVAX I, MicroVAX II, MicroVAX 2000
VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXstation
8000
OTHER HARDWARE REQUIRED
A DECwindows supported color monitor is required; otherwise, a VT24X,
VT330, or a VT340 terminal is required for systems with no DECwindows
interface.
To run the LTM Listener, one of the following is required:
o LAN Bridge 100 with ROM ECO Revision E or later
o LAN Bridge 150
o Chipcom(R) Ethermodem(TM) III Bridge [part #'s 8318BS (18Mhz) or
8312BS (12Mhz)]
Block Space Requirements (Block Cluster Size = 1):
Disk space required for installation
63,300 blocks
Disk space required for use (permanent): 60,600 blocks
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's
system environment, configuration, and software options.
Minimum Recommended Configuration
A VAXstation 3100, Model 38 or 48, with 32-Mbyte of memory and one RZ56
(665-Mbyte) disk drive.
OPTIONAL HARDWARE
In large network configurations where performance of the network
management system is critical, it is highly recommended that additional
memory and additional disk space be utilized.
CLUSTER ENVIRONMENT
This layered product is fully supported when installed on any valid and
licensed VAXcluster* configuration without restrictions. The HARDWARE
REQUIREMENTS sections of this product's Software Product Description and
System Support Addendum detail any special hardware required by this
product.
* V5.x VAXcluster configurations are fully described in the
VAXcluster Software product Description (29.78.XX) and include CI,
Ethernet and Mixed Interconnect configurations.
SOFTWARE REQUIREMENTS
For Systems Using Terminals (No DECwindows Interface):
VMS Operating System V5.3 - V5.4
DECnet-VAX V5.3 - V5.4
DECdns V1.2
For Workstations Running DECwindows:
VMS Operating System V5.3 - V5.4
DECnet-VAX V5.3 -V5.4
DECdns V1.2
This product may run in either of the following ways:
o Stand-alone execution--running the X11 display server and the
client application on the same machine.
o Remote execution--running the X11 display server and the client
application on different machines.
VMS DECwindows is part of the VMS Operating System but must be installed
separately. Installation of VMS DECwindows gives you the option to
install any or all of the following three components:
o VMS DECwindows Compute Server (Base kit; includes runtime support)
o VMS DECwindows Device Support
o VMS DECwindows Programming Support
For stand-alone execution, the following DECwindows components must be
installed on the machine:
o VMS DECwindows Compute Server
o VMS DECwindows Device Support
For remote execution, the following DECwindows components must be
installed on the machine:
Server Machine
o VMS DECwindows Compute Server
o VMS DECwindows Device Support
Client Machine
o VMS DECwindows Compute Server
o VMS DECwindows Device Support
VMS Tailoring
The following VMS classes are required for full functionality of this layered
product:
VMS Required Saveset
Programming Support
Network Support
Secure User's Environment
Utilities
For more information on VMS classes and tailoring, refer to the VMS
Operating System Software Product Description (SPD 25.01.xx).
OPTIONAL SOFTWARE
The following Digital VMS Layered Software Products may be optionally installed
with DECmcc SMS and run in the SMS DECwindows environment. Note that individual
product memory and CPU requirements may vary. Refer to the appropriate SPDs for
information about these products.
VAX DATATRIEVE V4.2
DECnet/SNA 3270 Terminal Emulator for VMS V1.5
GROWTH CONSIDERATIONS
The minimum hardware/software requirements for any future version of
this product may be different from the minimum requirements for the
current version.
Additional LAN Bridge units can be purchased and configured with LTM
Listener software after LAN Traffic Monitor VMS has been installed. By
creating a separate VMS process (or subprocess), a single user account
on the VAX host may simultaneously be collecting data from multiple LTM
Listener units. The LTM Listener can be started in either private mode
(sending to a single destination Ethernet address) or shared mode
(multicasting its traffic reports).
Also, while multiple hosts may simultaneously view a single LTM Listener
unit (thereby requiring additional licenses of the software be purchased
for each additional processor), multiple accounts on a single host may
NOT simultaneously view a single LTM Listener unit.
DISTRIBUTION MEDIA
Tape: 9-track 1600 BPI Magtape (PE), TK50 Streaming Tape
This product is also available as part of the VMS Consolidated Software
Distribution on CDROM.
ORDERING INFORMATION
Software Licenses: QL-YGLA9-AA
Software Media and Documentation: QA-YGLAA-H*
Software Documentation: QA-YGLAA-GZ
Software Product Services: QT-YGLA*-**
* Denotes variant fields. For additional information on available
licenses, services, and media, refer to the appropriate price book.
The above information is valid at the time of release. Please contact
your local Digital office for the most up-to-date information.
November 1990
AE-PAWCB-TE
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation. Chipcom is a registered trademark of Chipcom Corporation.
(TM) DECmcc, Ethernet, ETHERnim, DECnet, VAX, VMS, MicroVAX, VAXstation,
VAXserver, and VAXcluster are trademarks of Digital Equipment
Corporation. Ethermodem is a trademark of Chipcom Corporation.
|
| 426.7 | DECmcc EMS V2.0 SPD/SSA | DELNI::L_FELICE | | Tue Nov 20 1990 08:56 | 851 |
| If you copy or extract THIS text version of the SPD for a
customer, please mention that it's PRELIMINARY until it's
on VTX or with the software kit from manufacturing.
DECmcc(TM) Enterprise Management Station, Version 2.0 SPD 31.88.01
DESCRIPTION
DECmcc Enterprise Management Station (DECmcc EMS) is a network management
software product designed to provide network managers with a complete set of
applications to manage wide area heterogeneous networks.
The DECmcc Enterprise Management Station consolidates Digital Equipment
Corporation's network management applications within a DECwindows environment
and provides the capability of running all applications on a single system.
It consists of products that are compliant with Digital's Enterprise Management
Architecture (EMA) as well as products that are not EMA-compliant. As such,
DECmcc EMS is a transition vehicle to an EMA-compliant product set within
a single software product.
DECmcc EMS V2.0 consists of the following Digital network management products:
o DECmcc Basic Management System (BMS)
o NMCC/DECnet Monitor
o LAN Traffic Monitor (LTM) VMS
o Extended LAN Management Software (DECelms)
o NMCC/VAX ETHERnim
o Terminal Server Manager (TSM)
DECelms supersedes Remote Bridge Management Software (RBMS) in DECmcc EMS V2.0.
Also new to DECmcc EMS V2.0 is the DECmcc Basic Management System (BMS), a
product consisting of EMA-compliant software modules.
In addition to containing the products listed above, DECmcc EMS supports
the ability to install and run other VMS layered products within a DECwindows
environment. DECmcc EMS also provides access to non-Digital management
products that are based on X11 standards. Such products can be installed
on the same or separate processors as DECmcc EMS for the purpose of
consolidating interfaces on a single workstation display. Also included with
the DECmcc EMS components is the Network Troubleshooting Guide. Available
through the Bookreader application, the Network Troubleshooting Guide provides
DECmcc EMS users with a systematic, on-line approach to solving some of the
most common problems that occur on DECnet-VAX, DECnet-ULTRIX, Ethernet, and
TCP/IP networks.
DECmcc Basic Management System
The DECmcc Basic Management System (BMS) is a set of EMA-compliant products
based on an implementation of the EMA Director Model. EMA, which is consistent
with the the ISO/OSI management framework, defines a model for a management
system. The EMA-compliant DECmcc software enables users to control, monitor,
and test manageable objects (entities) in a network.
The EMA Director Model defines a management platform, called a director, and
cooperating but independent software components named 'management modules'.
DECmcc BMS is comprised of a director and management modules of the following
types.
o Access Modules (AMs) provide access to and information about
different classes of entities.
o Function Modules (FMs) provide high-level management functions
for managed entities.
o Presentation Modules (PMs) provide a consistent user interface
for Function modules.
The core of the EMA-compliant DECmcc software is the Executive, which
consists of a management kernel and a set of 'function modules'. The
Executive also includes a Management Information Repository (MIR),
which defines a consistent structure for, and storage of management data.
Together they form DECmcc's operating system-like environment for co-existence
and interoperation of management modules.
DECmcc BMS consists of EMA-compliant DECmcc Executive and Management
Modules, and is available both as a standalone product and as a component
of DECmcc EMS. The following is a list of the EMA-compliant components and
modules that comprise DECmcc BMS.
o Executive -- provides the environment in which DECmcc software management
modules operate, allowing them to communicate with each other and with
management information stored in the MIR. The DECmcc Executive consists
of the management kernel, function modules, and the MIR.
- Management Kernel: the management kernel provides the operating
environment and dispatching services for management modules.
The operating environment consists of a multi-threaded processing system,
contained within VMS processes, along with a set of callable procedures.
- Executive Function Modules (Control FM and Registration FM): the Control
FM makes available to users primitive directives for observation and
control of entities in the network. It also makes data available to
end-users for arbitrary entities, with arbitrary directives and
attributes. The Control FM supports a pre-defined list of basic
directives, plus a small set of generic directives that can be used for
different purposes by different AMs. The Registration FM, in conjunction
with the Digital Distributed Name Server (DECdns (TM)) manages data
identifying each entity in a network. It also defines and manages a set
of common reference attributes for all entities. The Registration FM
uses DECdns as the DECmcc instance repository, which allows multiple
DECmcc systems to share the same view of entity configurations.
- Management Information Repository (MIR): the MIR is an integrated data
base that contains definitions of entity classes, entity instances,
entity attributes, and private or miscellaneous data required by
individual management modules. The MIR provides storage and access
routines for maintaining management information within DECmcc software.
Most data stored in the MIR is structured according to the EMA Entity
Model.
o DECnet Phase IV Access Module -- enables users to manage DECnet Phase
IV entities and child entities such as nodes, circuits, lines, and
objects. The DECnet Phase IV AM provides an access path to and information
about the entities it supports. The DECnet Phase IV AM supports one global
entity class, NODE4, and a number of child entity classes. Typical
management operations include creating a NODE4 entity's knowledge of a
child entity, displaying information about an entity, and modifying an
entity's attributes.
o Ethernet Station Access Module -- provides looptest and display of generic
Ethernet devices that support: MOP REQID, MOP SYSID, MOP Counters,
IEEE802.2 XID, or IEEE802.2 TEST. The Ethernet Station AM also provides
Ethernet control and monitoring functions that can be used by other
management modules within the DECmcc system.
o Bridge Access Module -- enables users to control and monitor any
Digital LANbridge 100, 150 or 200 in an extended LAN environment. In
addition, this module provides an executable procedure to aid in the
populating of the DECmcc software database with information contained in
an existing Remote Bridge Management Software (RBMS) database.
o Sample Access Module -- is included as part of the DECmcc BMS. The sample
AM implements a single management directive, the SHOW directive, for the
DECnet Phase IV node entity and associated line subentity. The SHOW
directive displays various Characteristic, Status, and Counter attributes
for each entity. The Sample Access Module implements a SHOW and TEST
management directive to manage the Access Module itself to illustrate
the "management of management" concept. Including the Sample AM with the
DECmcc BMS is intended to ensure proper end-user licensing of access
modules developed using source code provided in the DECmcc Toolkit
(SPD 32.49.XX).
o Alarms Function Module -- provides the ability to notify network managers
that alarm conditions have been detected in the network. The DECmcc
Alarms FM can detect alarm conditions about any entity that has an
appropriate access module. When an alarm condition is detected, a user-
written command procedure is queued for execution. For example, it may be
useful to write command procedures that trigger the local system's mail
facility to deliver alarm messages. The DECmcc Alarms FM includes sample
rules for alarm conditions and sample command procedures that can be used
directly (e.g., to log, broadcast and mail alarms) or used as examples that
can be modified.
o Command Line Presentation Module -- supports a terminal based user
interface, using command line input and output techniques. It is a
command-line interface compliant with Digital's NCL, the command line
syntax used for DECnet/OSI Phase V network management commands. The
Command Line Presentation Module is available from any terminal or
workstation compatible with Digital's VT220 terminal. It supports
command-line recall and editing, abbreviation support, on-line help,
symbol substitution, support of control key sequences, line continuation,
and typeahead. The user interface structure also allows a VMS DCL process
to be 'spawned'.
o Forms Interface Presentation Module -- is an extension of the
command-line interface that provides a screen-based user interface, using
forms and list input and output techniques. It is available from any
terminal or workstation compatible with Digital's VT220 terminal.
The screen format contains two regions. One region is for entering data to
input fields for issuing DECmcc commands or 'directives'. The other region
is for viewing data resulting from DECmcc directives.
o Utilities -- Several utilities are included that enable the on-site
enrollment of management modules not provided with the DECmcc BMS.
Documentation required for such enrollment is provided by the module
developer. The utilities are:
- Dictionary Administrator Program (DAP) Utility
- Parse Table Builder (PTB) Utility
- Test Bed Driver (TBD) Utility
- Help File Builder (HFB) Utility
The DECmcc Developer's Toolkit Reference Manual (order number AA-PD5MA-TE)
describes each of the tools in detail.
NMCC/DECnet Monitor
NMCC/DECnet Monitor is a network monitoring application for Phase IV/IV+
DECnet network nodes. It runs as a layered application on VMS Systems
and does not require any additional hardware or software on the remote
DECnet nodes to be monitored. NMCC/DECnet Monitor collects and monitors
data concerning the DECnet network. NMCC/DECnet Monitor enables the user
to store, distribute, analyze, and evaluate the data into useful and
comprehensible information, and to present the data either as a screen
display or as a printed report.
NMCC/DECnet Monitor consists of software modules, the Kernel and User Interface,
which combine to form a comprehensive monitoring system. The central
component of NMCC/DECnet Monitor is the Kernel, a data acquisition process,
which collects data from the network using polling and/or event logging.
Polling can be used to obtain status, characteristics, and traffic/error
counters. Event logging can be set up to cause remote nodes to log events
automatically to the kernel, including status changes and traffic/error
counters as they occur.
The network manager has full control over which nodes are polled, the
polling rates, and which remote nodes log events. The Kernel processes
the raw data and creates a log file of statistical data which is then
available to the NMCC/DECnet Reports subsystem for the production of
network reports.
Through access to the log files, users can gather the following reports:
network summary, system, and line error reports; network summary, system, and
line traffic reports; configuration reports.
The User Interface subsystem provides an easy-to-use command interface
to the NMCC/DECnet Monitor. It provides on-line graphic and lexical
video displays of selected error statistics, traffic statistics, and
status information. The displays are designed hierarchically so that
the user can select the network components, information types, and levels
of detail in a consistent and easy to use manner. The graphic displays
include histograms, linear scales, and a network map.
The User Interface subsystem also provides the user with the capability
to build and manipulate various databases maintained by NMCC/DECnet
Monitor, including a network component reference database. This
contains a description of all nodes and physical links in the network.
It includes such details as CPU type, type and version of operating
system, name and telephone number of system manager, and name and telephone
number of customer service contacts. Display commands are provided to
retrieve this information. The user interface to these commands is consistent
with the operational interface of the product.
LAN Traffic Monitor VMS
The LAN Traffic Monitor VMS (LTM) is the software portion of a fully
distributed monitor that can support the capture and presentation of
traffic data from an extended Ethernet. A LAN Bridge 100 or LAN Bridge
150, downline loaded with monitoring software, is attached to the Ethernet
cable and transmits information to a VMS layered application software program
located on any VAX in the extended LAN. Multiple users, from different nodes
on the extended Ethernet, may access the traffic data. LAN Traffic Monitor
also works with Chipcom's(R) Broadband Bridges called Ethermodem(TM) III
Bridges.
LAN Bridge hardware can run either as a LAN Traffic Monitor or as a LAN
Bridge, i.e., the primary building block of the Extended LAN (Local Area
Network) architecture. An Extended LAN is a collection of LANs that are
interconnected and logically appear as one large Local Area Network.
Note that when a bridge is used as a monitoring device or listener, it does
not function as a bridge. Users can remotely switch a bridge between
monitoring and standard bridge modes using Digital's DECelms (Extended LAN
Management Software).
With the LAN Bridge designed to work at full Ethernet speed, the LAN
Traffic Monitor can provide real-time data on Ethernet LAN throughput
and utilization, allowing a customer to actively monitor their Ethernet
usage. The ability to collect data on any protocol type (i.e. LAT,
802.3, DECnet, TCP/IP, etc.) on the Ethernet is provided.
LAN Traffic Monitor contains the LTM Listener software (which counts
and classifies Ethernet traffic using a LAN Bridge as a monitoring
device) and the LTM User Interface (which collects and displays data
received from the LTM Listener).
The LTM Listener periodically reports traffic statistics to the LTM User
Interface located on a VAX host. The LTM User Interface receives
unsolicited Ethernet datagrams generated by the LTM Listener, and
through the menu structure, the user can also ask the LTM Listener for
additional data not found in the unsolicited messages. A single LTM host
can be used in conjunction with multiple LTM listeners.
The LTM User Interface performs the necessary data reduction and
presents the statistics in logical groupings. Summary displays, which
are presented in tabular format include Network Traffic, Top Ten Talkers, and
Throughput and Utilization. LTM also displays Lists of Nodes, Multicast
Addresses, Protocols Used by Nodes, Node Traffic by Protocol Type, Multicast
Traffic by Protocol Type, and Protocol Type Traffic.
In addition, LAN utilization based on the most recent traffic data received
from the LTM Listener may be displayed graphically in intervals of one, four,
eight, twelve, twenty-four, or forty-eight hours.
DECelms
DECelms (Extended Local Area Network Management Software) enables users to
configure, manage, monitor, control, and observe any LAN Bridge and FDDI
Wiring Concentrator in an extended Ethernet/802.3 LAN and FDDI network
environment. Supported devices include Digital's LAN Bridge 100, LAN Bridge
150, LAN Bridge 200, DECbridge 500, DECconcentrator 500, METROwave, and
Chipcom's Ethermodem Broadband Bridge. DECelms is comprised of VAX host
software and corresponding firmwear that resides in the LAN Bridges and FDDI
DECconcentrators.
A superset of RBMS V2.0 functions, DECelms provides remote management
capabilities for FDDI and Ethernet devices. Using DECelms, users can:
o Observe, monitor, and control interoperable FDDI and Ethernet networks.
o Display and modify a devices, lines, physical ports, and forwarding database
characteristics.
o Enable and disable lines and physical ports.
o Automatically build a host registry of all reachable FDDI DECconcentrators
and LAN Bridges within extended LAN and FDDI environments.
o Automatically or manually poll the devices stored in the host registry
for faults, errors, and changed information.
o Display error conditions to an alarms window and record detailed information
in an error log file.
o Process the logfile keying off time or type of faults.
o Use standard VMS utilities like print, type, search, etc, on the ASCII
formatted versions of the DECelms error log file.
o Display data-link counters, status and characteristics.
o Modify parameters such as operational state, forwarding database,
and spanning tree characteristics.
o Remotely invoke a device's self-test capabilities.
o Associate ASCII names with specific device physical addresses for ease of
use in management commands.
o Display the logical FDDI network topology through ring mapping.
DECelms also provides simultaneous access by more than one user, supports
command line recall, and password protection for setable parameters for Digital
LAN Bridge 150s, 200s, 500s, and FDDI DECconcentrators.
NMCC/VAX ETHERnim
NMCC/VAX ETHERnim is a network management application that
provides the network manager with a tool to gather information about
Ethernet nodes, verify reachability of nodes, provide a graphical
display of local area network topology and monitor Ethernet traffic.
NMCC/VAX ETHERnim consists of two categories of software, one of which
must be installed on a VMS system set up as the Host, and the other
which can be optionally installed on Target systems running VMS. In
this context, the Host is defined as the node on which the NMCC/VAX
ETHERnim application runs, while the Target systems are those DECnet
nodes on the Ethernet segments which are being tested at the User (task)
level. The optional software installed on the Target system is referred
to as the Remote Files.
The Host software requires Phase IV DECnet software on a VMS system.
When this software has been installed, the network manager has the
ability to:
o Build a permanent database containing basic information about each node
directly connected to the Ethernet local area network through user commands
and automatic procedures.
o Manually construct and maintain a topological view of the network,
including transparent network devices (e.g., DEMPR, DELNI, DEREP).
o Test the Ethernet network to help isolate and identify problems
o Test the communications path to each node up to the DNA
application layer by performing a loopback test to a specified
user account. This feature is available only for VMS Target
systems.
o Monitor the network to determine which nodes are the top talkers
and which nodes are the top listeners; sort/display traffic by
protocol type or multi-cast address; focus on traffic to/from a
specified node.
o Perform information access to properly configured DECnet nodes on the
Ethernet to determine the remote nodes's system type, hardware
configuration, and software configuration.
Terminal Server Manager
Terminal Server Manager VMS (TSM) software allows suitably privileged
users at a VAX host to control and observe terminal servers anywhere in
the extended local area network. TSM provides centralization and
increased flexibility in configuring, monitoring, and controlling
Digital's family of terminal servers.
Among the features supported by TSM are:
o Support for the 3270 Option Software for the CXM04 line card. This line
card provides capability of connectivity of 3270 class of terminals to
systems on Ethernet.
o Keyboard mapping, which enables the terminal server manager to customize
3270 keyboard tables supplied with the 3270 Option Software by changing the
way individual 3270 keyboard keys are mapped to Digital's VT220 keys.
o Wildcarding, which extends the wildcarding capability for server names by
allowing a wildcard character such as * and % to replace a server name
any place it appears in the syntax.
o A management directory that contains the name, Ethernet address,
terminal server type, and other fields for each server to be managed.
Through the TSM directory, the user need only to refer to the name of
the server in order to gain access.
o The ability to define logical groups of servers. A command can then be
executed for all servers in the partition. TSM provides a predefined
partition called ALL that includes all servers in the directory.
o Access to and manipulation of the database associated with each server
within its jurisdiction, including their characteristics and parameters.
o Management of the volatile characteristics for all terminal server types.
o Management of permanent NVRAM characteristics for the DECserver 100,
DECserver 200, and MUXserver 100. For the Ethernet Terminal Server and
DECserver 500, TSM modifies the permanent attributes contained within
the image files which are down-line loaded.
o Automated updates of the DECnet database for servers to match the
DECnet related information in the management directory. Users need no
longer employ a separate DSVCONFIG or TSVNCP configuration program.
o TSM server and directory commands may be issued as DCL commands; the
syntax follows DCL conventions.
o A USE command to allow selection of the server or servers to be managed
or the directory to be referenced. A single server, a user specified group
of servers (a partition), or all servers known via the management
directory can be selected with the USE command.
o Maintenance of command files outside of TSM (e.g., by use of a VMS
editor). This command file support allows values of characteristics
to be stored on the host, effectively creating a copy of the permanent
database that may be used to configure new servers. Server
maintenance is also enhanced by allowing the terminal server to be
easily box swapped, and parameters reset. Up to eight parameters may
be passed to TSM command files. Additionally, command files may
operate on a single server, on a logical group (a partition) of
servers or on all servers.
o Trouble shooting within the terminal server network through the ability
ability to centrally read traffic status and counters in addition to error
status and counters. With the PASTHRU command, the user can also connect
directly to the server without using TSM, allowing isolation of problems
between TSM and the server.
Network Troubleshooting Guide
The Network Troubleshooting Guide provides an on-line, systematic approach to
solving any network problem. Available through the Bookreader application,
its text can be displayed in a window within a DECmcc Management Station
environment. The Network Troubleshooting Guide gives specific step-by-step
instructions for solving some of the most common network problems that
occur on DECnet-VAX, DECnet-ULTRIX, Ethernet, and TCP/IP networks.
The Network Troubleshooting Guide incorporates information from various
sources into a single manual -- minimizing the documentation required for
solving network problems.
The Network Troubleshooting Guide covers:
o Background information on DECnet and TCP/IP networks.
o How to use a standard troubleshooting methodology to solve any
network problem.
o How to use network tools such as DECmcc Management Station for
ULTRIX, Network Control Program (NCP), NMCC/DECnet Monitor,
NMCC/VAX Ethernim, and LAN Traffic Monitor (LTM).
o How to use ULTRIX commands such as netstat, ping, and uerf.
o How to use log files and counters to gather information for
problem solving.
o How to trace a network path to isolate the source of a problem.
o How and when to perform loopback tests.
o In explicit step-by-step instructions, how to solve nearly 30 of
the most common network problems, including:
- Network partner exited (DECnet networks)
- Permission denied (TCP/IP networks)
- LAT Print Queue Problems (Ethernet networks)
INSTALLATION
Only experienced customers should attempt the installation of this
product. Digital recommends that all other customers purchase Digital's
installation and consulting services. These services provide for the
planning, implementation (product setup and startup) and customer
orientation on the product by an experienced Digital Software
Specialist. Customers should consult their local Digital offices to
obtain information of installation and start-up services available in
their locations.
HARDWARE REQUIREMENTS
VAX, MicroVAX, VAXstation or VAXserver configuration as specified in the
System Support Addendum (SSA 31.88.01-*).
LANbridge 100/150 for LTM Listener
SOFTWARE REQUIREMENTS*
For Systems Using Terminals (No DECwindows Interface):
VMS Operating System
DECnet-VAX
VAX Rdb/VMS (Run-Time Option)
DEC GKS for VMS (Run-Time Option)
DECdns Server (must be somewhere in network)
For Workstations Running DECwindows:
VMS Operating System (and necessary components of DECwindows)
DECnet-VAX
VAX Rdb/VMS (Run-time Option)
DEC GKS for VMS (Run-time Option)
DECdns Server (must be somewhere in network)
* Refer to the System Support Addendum (SSA 31.88.01-*) for
availability and required versions of prerequisite/optional
software.
ORDERING INFORMATION
Software Licenses: QL-YFVA9-AA
Software Media and Documentation: QA-YFVAA-H*
Software Documentation: QA-YFVAA-GZ
Software Product Services: QT-YFVA*-**
* Denotes variant fields. For additional information on available
licenses, services, and media, refer to the appropriate price book.
SOFTWARE LICENSING
This software is furnished under the licensing provisions of Digital
Equipment Corporation's Standard Terms and Conditions. For more
information about Digital's licensing terms and policies, contact your
local Digital office.
LICENSE MANAGEMENT FACILITY SUPPORT
This product supports the VMS License Management Facility (LMF). License
units for this product are allocated at a flat price basis, regardless of
User/Activity or processor type.
For more information on the License Management Facility, refer to the
VMS Operating System Software Product Description (SPD 25.01.xx) or the
License Management Facility manual of the VMS Operation System
documentation set.
For more information about Digital's licensing terms and policies,
contact your local Digital office.
SOFTWARE PRODUCT SERVICES
o Layered Product Service (LPS) -- provides the right-to-use new versions
of layered software. It also extends the level of support provided on
the kernel software to include coverage of the layered software product.
LPS is required for all Digital layered software running on a system
covered by Full Support. LPS is a prerequisite for the following service
options.
- Media and Documentation Distribution Service (MDDS) -- ensures customers
have access to the latest software versions of media and documentation
updates. MDDS is ordered on a per product basis.
- Documentation Update Service -- ensures that users receive documentation
updated for software manuals as they are released.
- Initial Installation Service -- provides installation by Digital of
newly purchased software on a per product basis.
OTHER DIGITAL NETWORK SERVICES
To assist you in planning, designing, implementing, managing and
evolving your network, Digital offers a comprehensive portfolio of
network management services. These address, but are not restricted to,
the following:
o Network Planning and Design
o Physical Network Implementation
o Network Start-up and Implementation
o Network Performance Consulting
o Fault and Configuration Management
o Network Products' Training
o Shared NETsupport
o NETsupport
For local availability, please contact your Digital Sales Office.
SOFTWARE WARRANTY
Warranty for this software product is provided by Digital with the
purchase of a license for the product as defined in the Software
Warranty Addendum of this SPD.
November 1990
AE-PAW9B-TE
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation. Chipcom is a registered trademark of the Chipcom Corporation.
(TM) DECmcc, Ethernet, ETHERnim, DECnet, RBMS, DECelms, VAX, VMS, MicroVAX,
VAXstation, VAXserver, and VAXcluster are trademarks of Digital Equipment
Corporation. Ethermodem is a trademark of the Chipcom Corporation.
DECmcc Enterprise Management Station, Version 2.0 SSA 31.88.01A
HARDWARE REQUIREMENTS
VAX: VAX 9000 Series, VAX 6000 Model 200 Series, VAX 6000 Model 300 Series,
VAX 6000 Model 400 Series
VAX 8200, VAX 8250, VAX 8300, VAX 8350, VAX 8500, VAX 8530, VAX 8550,
VAX 8600, VAX 8650, VAX 8700, VAX 8800, VAX 8810, VAX 8820, VAX 8830,
VAX 8840, VAX 8842, VAX 8974, VAX 8978
VAX-11/780, VAX-11/785
MicroVAX: MicroVAX 3100, MicroVAX 3300, MicroVAX 3400, MicroVAX 3500,
MicroVAX 3600, MicroVAX 3800, MicroVAX 3900
VAXstation: VAXstation 3100 Series, VAXstation 3200, VAXstation 3500,
VAXstation 3520, VAXstation 3540
VAXserver: VAXserver 3100, VAXserver 3300, VAXserver 3400, VAXserver
3500, VAXserver 3600, VAXserver 3602, VAXserver 3800,
VAXserver 3900, VAXserver 6000-210, VAXserver 6000-310,
VAXserver 6000-410, VAXserver 6000-420
Processors Not Supported
VAX: VAX-11/725, VAX-11/730, VAX-11/750, VAX-11/782
MicroVAX: MicroVAX I, MicroVAX II, MicroVAX 2000
VAXstation: VAXstation I, VAXstation II, VAXstation 2000, VAXstation
8000
OTHER HARDWARE REQUIRED
A DECwindows supported color monitor is required; otherwise, a VT24X,
VT330, or a VT340 terminal is required for systems with no DECwindows
interface.
To run the LTM Listener, one of the following is required:
o LAN Bridge 100 with ROM ECO Revision E or later
o LAN Bridge 150
o Chipcom(R) Ethermodem(TM) III Bridge [part #'s 8318BS (18Mhz) or
8312BS (12Mhz)]
Block Space Requirements (Block Cluster Size = 1):
Disk space required for installation
(Includes NMCC/DECnet Monitor database installation):
108,300 blocks
Disk space required for use (permanent): 105,600 blocks
These counts refer to the disk space required on the system disk. The
sizes are approximate; actual sizes may vary depending on the user's
system environment, configuration, and software options.
Minimum Recommended Configuration
A VAXstation 3100, Model 38 or 48, with 32-Mbyte of memory and one RZ56
(665-Mbyte) disk drive.
OPTIONAL HARDWARE
In large network configurations where performance of the network
management system is critical, it is highly recommended that additional
memory and additional disk space be utilized.
CLUSTER ENVIRONMENT
This layered product is fully supported when installed on any valid and
licensed VAXcluster* configuration without restrictions. The HARDWARE
REQUIREMENTS sections of this product's Software Product Description and
System Support Addendum detail any special hardware required by this
product.
* V5.x VAXcluster configurations are fully described in the
VAXcluster Software product Description (29.78.XX) and include CI,
Ethernet and Mixed Interconnect configurations.
SOFTWARE REQUIREMENTS
For Systems Using Terminals (No DECwindows Interface):
VMS Operating System V5.3 - V5.4
DECnet-VAX V5.3 - V5.4
VAX Rdb/VMS V3.1B (Run-Time Option)
DEC GKS for VMS V4.1 (Run-Time Option)
DECdns V1.2
For Workstations Running DECwindows:
VMS Operating System V5.3 - V5.4
DECnet-VAX V5.3 - V5.4
VAX Rdb/VMS V3.1B (Run-Time Option)
DEC GKS for VMS V4.1 (Run-Time Option)
DECdns V1.2
This product may run in either of the following ways:
o Stand-alone execution--running the X11 display server and the
client application on the same machine.
o Remote execution--running the X11 display server and the client
application on different machines.
VMS DECwindows is part of the VMS Operating System but must be installed
separately. Installation of VMS DECwindows gives you the option to
install any or all of the following three components:
o VMS DECwindows Compute Server (Base kit; includes runtime support)
o VMS DECwindows Device Support
o VMS DECwindows Programming Support
For stand-alone execution, the following DECwindows components must be
installed on the machine:
o VMS DECwindows Compute Server
o VMS DECwindows Device Support
For remote execution, the following DECwindows components must be
installed on the machine:
Server Machine
o VMS DECwindows Compute Server
o VMS DECwindows Device Support
Client Machine
o VMS DECwindows Compute Server
o VMS DECwindows Device Support
VMS Tailoring
The following VMS classes are required for full functionality of this layered
product:
VMS Required Saveset
Programming Support
Network Support
Secure User's Environment
Utilities
For more information on VMS classes and tailoring, refer to the VMS
Operating System Software Product Description (SPD 25.01.xx).
OPTIONAL SOFTWARE
The following Digital VMS Layered Software Products may be optionally installed
with DECmcc EMS and run in the DECwindows environment. Note that individual
product memory and CPU requirements may vary. Refer to the appropriate SPDs for
information about these products.
VAX DATATRIEVE V4.2
VAX DECgraph V1.5
VAX CDD/Plus V4.0 - V4.1
DECnet/SNA 3270 Terminal Emulator for VMS V1.5
GROWTH CONSIDERATIONS
The minimum hardware/software requirements for any future version of
this product may be different from the minimum requirements for the
current version.
Additional LAN Bridge units can be purchased and configured with LTM
Listener software after LAN Traffic Monitor VMS has been installed. By
creating a separate VMS process (or subprocess), a single user account
on the VAX host may simultaneously be collecting data from multiple LTM
Listener units. The LTM Listener can be started in either private mode
(sending to a single destination Ethernet address) or shared mode
(multicasting its traffic reports).
Also, while multiple hosts may simultaneously view a single LTM Listener
unit (thereby requiring additional licenses of the software be purchased
for each additional processor), multiple accounts on a single host may
NOT simultaneously view a single LTM Listener unit.
DISTRIBUTION MEDIA
Tape: 9-track 1600 BPI Magtape (PE), TK50 Streaming Tape
This product is also available as part of the VMS Consolidated Software
Distribution on CDROM.
ORDERING INFORMATION
Software Licenses: QL-YFVA9-AA
Software Media and Documentation: QA-YFVAA-H*
Software Documentation: QA-YFVAA-GZ
Software Product Services: QT-YFVA*-**
* Denotes variant fields. For additional information on available
licenses, services, and media, refer to the appropriate price book.
The above information is valid at the time of release. Please contact
your local Digital office for the most up-to-date information.
November 1990
AE-PAWAB-TE
(R) The DIGITAL Logo is a registered trademark of Digital Equipment
Corporation. Chipcom is a registered trademark of Chipcom Corporation.
(TM) DECmcc, Ethernet, ETHERnim, DECnet, VAX, VMS, MicroVAX, VAXstation,
VAXserver, and VAXcluster are trademarks of Digital Equipment
Corporation. Ethermodem is a trademark of Chipcom Corporation.
|
| 426.8 | sorry for the delay, re .5 | GOSTE::CALLANDER | | Tue Nov 20 1990 14:27 | 11 |
| re .5
Phil, We are still waiting on them ourselves. The SRM will not be
available on line, but must be ordered. Due to the nature and size
of the rewrites a complete new SRM is needed, updates just won't
do it. Also the number of additions to the SRM has caused the manual
to swell to two books. As for the programming guide I would suggest
that you send mail to took::d_black for an answer to that one.
jill
|
| 426.9 | DECdns v1.2? | TROA01::DLOTEN | Semper ubi sub ubi. | Tue Dec 18 1990 09:01 | 8 |
|
re .7
Lisa, the SPD lists in the SOFTWARE REQUIREMENTS that DECdns v1.2 is
required. Is that referring to the CLERK software delivered in VMS
5.3? The current DECdns server is v1.1A (available only on CD).
-doug
|
| 426.10 | SMS distribution query | SUBURB::HARWOODJ | Judy Harwood - REO - 830 2879 | Wed Jan 29 1992 07:37 | 9 |
| I have just been looking at the current SPD for DECmcc SMS (31.87.02)
and it gives the distribution media as being
"9-track 6250 BPI Magtape (PE), TK50 Streaming tape."
Is the 6250 BPI a misprint for 1600 BPI or not. Who can confirm
this for me ?
Judy
|
| 426.11 | SMS distribution media answer! | DELNI::J_SILVER | | Fri Jan 31 1992 14:10 | 6 |
| The SMS SPD is correct. We decided to use one magtape at 6250 bpi
instead of using two magtapes at 1600 bpi. Is that a problem for you??
Junell Silver
Product Manager
|
| 426.12 | Not if part numbers are different | SUBURB::HARWOODJ | Judy Harwood - REO - 830 2879 | Tue Feb 04 1992 07:48 | 20 |
|
It could possibly be a problem for any customers who only have tape
drives capable of reading 1600 BPI tapes.
I assume that the media part number we are talking about is
QA-YGLAA-HA, or something similar. (-HA being media on 9 track 6250
bpi tape according to my info.)
For many years now the 9 track offering has more usually been
for 1600 BPI ( -H5 code), so provided we can make folks aware of
this difference it should be OK.
Any one with a 6250 BPI drive can also use read a 1600 BPI tape,
but the reverse is not possible.
Hence my concern
Many thanks
Judy
|