DIGITAL Software Product Description ___________________________________________________________________ PRODUCT NAME: TeMIP Framework V3.2-A for DIGITAL UNIX[R] SPD 54.17.07 DESCRIPTION TeMIP Framework is a complete, prepackaged Product Family distributed management system for multivendor, multi-protocol networks. It pro- vides access to, and management functions for, open networks and the network environments of DIGITAL (TCP/IP, DECnet-Plus and DECnet Phase IV). The TeMIP Framework is a modular and distributed software prod- uct that can be extended through the addition of other TeMIP products, third party, or user-developed software modules. The TeMIP distribution features enable users to transparently distribute access at user level through Client systems, and at Network Element level through Access Module server systems. TeMIP distribution pro- vides the scalability and geographical span requirements of telecom- munication or corporate networks by sharing the communication traf- fic and CPU load over multiple geographically disseminated systems. In addition to its Distributed Framework, the TeMIP product set pro- vides you with telecommunication and large voice/data network manage- ment capabilities through the following TeMIP Fault and Trouble Man- agement applications and Development Toolkits: o TeMIP Alarm Handling, for the management of ISO-formatted alarms information (a specific type of event in ISO terminology), enables users to define comprehensive alarm filtering and low level cor- relation, real-time monitoring and recording. o TeMIP Event Logging, enables users to define single or multiple col- lection and recording of events for a domain which represents the entire or selected portions of the network. October 1998 AE-Q9H5H-TE o TeMIP Trouble Ticketing, enables the initiation and efficient co- ordination of network problem solving and maintenance activities. For more information about the TeMIP Fault and Trouble Management ap- plications, refer to the TeMIP Fault and Trouble Management Software Product Description (SPD) 45.24.xx. o The TeMIP OSI Management Toolkit allows a TeMIP management system to act as either a Manager, using the OSI Access Module, or as an Agent using the OSI Agent Presentation Module. The toolkit provides access to the Open Systems Interconnection (OSI) Q3/CMIP environ- ment in accordance with Telecommunications Management Network (TMN) recommendations. It provides the means to maintain and manage the Guidelines for the Definition of Managed Objects (GDMO) models of managed objects and integrate them into the TeMIP run-time envi- ronment without recompiling. It uses the standard and commercially available XMP API to access the TMN Q3 stack. For more information, refer to the TeMIP OSI Management Toolkit Software Product Descrip- tion (SPD 51.28.xx). o The TeMIP Graphical ASCII Toolkit (GAT) provides access to elements that do not support the standard management interface, but which still use ASCII/TL1 type messages (that is, legacy systems and ap- plications). For more information, refer to the TeMIP Graphical ASCII Toolkit Software Product Description (SPD 64.82.xx). o The TeMIP Expert System Access (ESA), which provides external Ex- pert System applications with access to TeMIP. Note that ESA is in- dependent of any proprietary Expert System technology and provides a consistent interface to the Expert System application. As a re- sult of this, the application gateway can develop in line with TeMIP. For further information, refer to the TeMIP Expert System Access Software Product Description (SPD 70.40.xx). Available on the DIGITAL UNIX Operating System, TeMIP Framework pro- vides both generic and device-specific management functions, distributed management and language localization capabilities including: o Motif[R] Graphical User Interface (GUI) and Command Line User In- terfaces that provide consistent views and interactions with the 2 management system, regardless of the objects managed or the pro- tocols used to manage them. New and enhanced GUI features are present in this release of the product. o Configuration Management functions that include automated discov- ery and device registration, topology mapping, and user-defined man- agement domains. o Distributed Notification and Alarm functions that enable users to define alarm rules and set up notification, and automated proce- dures to locate existing and potential network problems or events. o Access Control and Logging of Operator Commands features. This al- lows the scope and the authorized operations to be defined easily for each kind of user. The Access Control features are available through a documented API (Security toolkit) to allow integration within your applications. o Language Localization is provided through the TeMIP Framework com- pliance with the XPG4 standard. o Distribution is achieved by means of distributing Management Mod- ules and services across multiple TeMIP systems (also called Di- rectors) by making the the Functions transparently operate across machine boundaries. o A Director Management Application offers services, available from the Motif GUI, to manage the distributed TeMIP system (that is, Event Status monitoring, Director Topology display, Director Configura- tion Consistency checking). o The TeMIP Name Service (TNS) is a network-wide service that makes distribution of TeMIP possible. TNS consists of client and server components (like DECdns). TNS stores information about entities in a highly accessible, distributed and replicated database, from where it can be accessed by any TeMIP director. TeMIP distributed sys- tem configuration data is stored in TNS. The TNS database contains the registered names created for TeMIP global entities, as well as names of child entities, reference data, Managing Director's name for each entity, and a list of the domains of which an entity is a member. 3 TeMIP Framework consists of a set of distributed layered Management Modules supported by an open application programming interface (API), an Executive or operating system-like set of module support functions, and an object-oriented Management Information Repository (MIR) pro- viding data structure and storage functions. Management Modules provide services to users and to one another. There are three types of Management Module: o Function Modules (FMs) provide services such as object registra- tion, statistics generation, fault detection, and notification to users and to one another. o Access Modules (AMs) provide remote protocol support for, and man- agement information about, different classes of managed objects. o Presentation Modules (PMs) provide a consistent user interface for the direct manipulation of managed objects (through AMs) and user access to management operations (through FMs). The Management Modules can be distributed on physically different (that is, remote) machines. It means that a Presentation Module installed and running on one machine can communicate with Function Modules on another machine, that can themselves communicate with Access Modules located on a third machine. o The Executive provides system services that enable Management Mod- ules to be installed and used independently or in combination. o The Applications Programming Interface (API) defines how Manage- ment Modules invoke each other's services. The TeMIP Framework API is open and documented to support DIGITAL, third party, or user- developed modules. o The Management Information Repository (MIR) provides a means to struc- ture and store management information. TeMIP Framework Function Modules 4 The TeMIP Framework includes generic and device-specific FMs that pro- vide a variety of management services to end users and, in combina- tion, to one another. These services include configuration management functions and fault management functions including alarm and notifi- cation services. Generic FM services provide support for devices accessible through the TeMIP Framework AMs, other DIGITAL-developed AMs, or AMs developed and supported by third parties and users. 5 Configuration Management Functions TeMIP Framework Configuration Management functions include both man- ual and automatic registration of managed objects, and support for user- defined domains (groups of managed objects). These functions are pro- vided by the following TeMIP Framework FMs and services: The Registration FM is a generic FM that enables users to enter and manage data identifying each managed object in a network environment. Such information includes object instance data such as network names and addresses, and reference information such as device location, soft- ware revision levels, and contact names. With the Registration FM, users have the option of selecting a local system-level repository, or setting up a distributed, network-wide, globally-available naming service - the TeMIP Name Service (TNS). With TNS, users and applications can assign names to resources (such as nodes, bridges, files, domain names, ...) and then use those resources with- out having to keep track of physical location or network address. The TNS option also enables multiple TeMIP Frameworks to share the same view of managed objects. The Domain FM is a generic FM that enables users to assign managed ob- jects into groups called domains. Domains are subsets of the managed object configuration, which provide user-defined groups that can be based on: equipment type (all switches, multiplexers, TCP/IP hosts, DECnet nodes, geography (all objects within a region, site, or sub- net), personnel levels, or any other user-defined object group. Do- mains can contain or refer to other domains and can be hierarchical or overlapping. Individual managed objects can be contained within mul- tiple domains. Each domain is associated with one Director. Autoconfiguration services automatically locate, register, and map man- aged objects by class. Supported classes include TCP/IP hosts and DEC- net Phase IV nodes. Users can define domains for each class, and set network boundaries. The autoconfiguration functions can request net- work instance data from IP gateways and DECnet routers. As devices are 6 located and management information gathered, the functions automat- ically map them in the appropriate user-defined domains and register management data in the MIR. Note: The TCP/IP SNMP, DECnet Phase IV and DECnet-Plus AMs are included in TeMIP Framework. The IP Reachability Poller FM sends notification to TeMIP Framework Notification Services when a specific IP node changes state (that is, it becomes reachable or unreachable). It provides TeMIP Framework with an efficient manner to determine if IP nodes are reachable or not. Alarm and Notification Services TeMIP Framework alarm and notification services are provided by a com- bination of Management Modules. These modules enable users to create alarm rules that can detect existing or potential network problems, and notification mechanisms for informing users when such problems oc- cur or network events happen. Alarms FM, Data Collector AM and SNMP AM modules support or generate ISO-formatted OSI events that can be treated by the TeMIP Fault and Trouble Management applications (for example, IP reachability, incoming traps and enterprise-specific traps generated by the SNMP AM). The Alarms FM provides facilities for users to write rule-based ex- pressions (alarm rules) that use polled data or unsolicited event mes- sages to trigger alarms. Alarm rules can be written for any managed object or entity class for which there is corresponding Access Mod- ule protocol support (Multiplexers, Cross-connect, OSI, SNMP, DECnet Phase IV NICE, ...). The Alarms FM now benefits fully from the TeMIP filtering and correlation features, see the TeMIP Fault and Trouble Management Software Product Description (SPD 45.24.xx). Alarm rules can be based on state changes, simple arithmetic expres- sions, or occurences (unsolicited event messages received through the appropriate Access Module). Alarm rules can be written for individ- ual managed objects or wildcarding can be used to apply rules to all objects in a domain for a given object class. It supports the ISO alarm type and probable cause fields. 7 In addition to the standard TeMIP Framework notification functions de- scribed below, the Alarms FM allows for the execution of user-written command procedures. Such command procedures can be used to generate terminal broadcast or electronic mail messages, or automated proce- dures that a network manager or operator might implement when a par- ticular alarm condition occurs. Refer to the TeMIP Fault and Trouble Management SPD 45.24.xx for a de- tailed description of the powerful alarms/events management user in- terface. In addition, the TeMIP Framework still provides a specific user interface by means of the Notification PM and other modules. The Notification FM and PM enable users to define the mechanisms used to alert operators when a particular network or system event has occurred. The functions recognize two types of events: configuration events, which are reported by a managed object or TeMIP Framework Module; and alarm events, which are generated by the Alarms FM whenever a rule fires or encounters an error (that is, an exception to the rule). When an event occurs, the Motif/Iconic Map PM displays a color change on the appropriate object icon, and a message in the Notification win- dow. Users can define the severity levels and select colors appropri- ate to the problem level. Notification also enables users to customize event collection and storage through its logging, filter, search, and view capabilities. Notifications (icon, line or text color changes) can be redirected from the object that generates the event to the ob- ject that is the subject of the event by means of the target direc- tive. The Event Collector AM (also known as the Data Collector AM) enables users to collect events from objects not directly managed by TeMIP Frame- work. Users can create customized icons for any object not directly managed by TeMIP Framework and include it in the Iconic Map. TeMIP Framework Security TeMIP Framework delivers the high level of security essential to all telecom or mixed data and voice distributed network operations. Its 8 flexible and powerful Access Control mechanism allows the network man- ager to determine who accesses critical functions, physical or log- ical resources or objects down to the class/instance or directive level. TeMIP Framework Security is provided through the use of: o Access Control, which consists of defining restricted domains of activity (that is, what entity, verb, attribute or argument can be accessed) for each user. o Logging of Operator Commands, which consists of tracking and stor- ing Command Information generated by an operator during a TeMIP Frame- work session. o The Security Development Toolkit allows developers to integrate the TeMIP Framework Security features into specific Presentation Mod- ules or applications. Access Control is a set of mechanisms that prevent a given user from accessing part of the management information when running a Presen- tation Module and is based on: o Access Control (AC) Views that are filters (control rules) that de- termine which operations are allowed or disallowed. o User Profiles that are the association between a user and a set of authorized functions as defined in AC views. o Access Control Management graphical user interface available (for authorized users only) as an Iconic Map launched application. The Logging of Operator Command (LOC) function stores pre-defined com- mands entered by a user into a database that can be examined later. It comprises the Central Command Logging function that applies to all concurrent PM sessions running on the TeMIP Framework system and the User Session Command logging function, providing the same logging and browsing features and allowing the operator to set up his or her own LOC environment before entering his PM session. 9 The Security Development Toolkit provides the AC and LOC Application Programming Interface and a shell application, allowing Presentation Module developers to obtain software library services (APIs) that per- form Access Control against an active AC view as well as runtime Com- mand Logging services. TeMIP Framework Access Modules TeMIP Framework AMs provide access to network and system objects in DIGITAL Network products and other mixed, multivendor network envi- ronments that use the following management protocols: SNMP, CMIP, DEC- net, NICE, DECnet/OSI and IEEE 802.2/Ethernet/MOP. o The TCP/IP SNMP AM includes support for the following Internet Ad- visory Board (IAB) Simple Network Management Protocol (SNMP) RFCs: 1155, 1156, 1157, 1212, and 1213. This includes full MIB II sup- port in addition to support for on-site enrolment of vendor-specific Enterprise MIBs including: - A MIB compiler that automatically checks the syntax of the ASN.1 Concise MIB definition (providing error messages to help iden- tify syntax problems) and translates the data for loading the information into TeMIP Framework's Management Information Repos- itory (MIR). The translation utility supports both SNMPv2 and SNMPv1 syntax and automatically generates on-line HELP. - An event-logging sink for collecting SNMP generic traps (unso- licited TCP/IP event messages): coldStart, warmStart, linkDown, linkUp, egpNeighborLoss, authenticationFailure, and enterpris- eSpecific. Generation of ISO-formatted alarms (for example, IP reachability, incoming traps) and Vendor Specific Traps are also supported with this release of the product. - Ability to perform GET and SET operations on devices supported by SNMP agents. - ICMP ECHO_REQUEST (ping) support for verifying the reachabil- ity of an SNMP managed object at the IP level. 10 - This release provides enhanced features such as SNMPv2C proto- col support, raw SNMP trap data logging support, full support of the ASN.1 IMPORTS clause and a new MIB Translator Utility GUI. o The DECnet-Plus AM provides access to DECnet devices that use the DIGITAL implementation of the standard Common Management Informa- tion Protocol (CMIP). This version of CMIP, implemented on DECnet- Plus devices, provides management operations and data gathering func- tions for DECnet-Plus networks including the ability to sink DEC- net events to the TeMIP Framework. o The DECnet Phase IV AM enables users to manage DECnet Phase IV ob- jects such as nodes, circuits, lines, and adjacencies. With the DEC- net Phase IV AM, users can modify DECnet parameters, set charac- teristics, collect DECnet events, and poll for management data such as counters or status. o The Circuit AM works as a client of management protocol modules to provide management of circuits connecting endpoints compliant with the Network Management Forum (NMF) definitions. Compliant endpoints include DECnet Phase IV and DECnet-Plus nodes, and TCP/IP hosts. Tying together circuit, line, link, and other end-point data, this AM can gather status data and store reference information about sim- ple, point-to-point circuits or complex multi-channel circuits. o The Script AM is a generic Access Module that executes a script (or command procedure) and propagates the output data back into TeMIP Framework as individual attributes. Once integrated, these attributes can take advantage of the alarm generation, notification, and record- ing facilities of TeMIP Framework. The Script AM offers the following advantages: - Allows integration of data into TeMIP Framework quickly and eas- ily. No C code is required to write a script. - Allows management of devices which provide only a command line interface. 11 - Allows integration of any data (as attributes) into TeMIP Frame- work, whether from a Structured Query Language (SQL) command, a system command or by running a script on a remote system. - Allows integration of data from an executable, for which source code is not available. o The Data Collector AM, also called the Event Collector, enables TeMIP Framework to collect events from objects not directly manageable by any other Access Module, or receive events that are not modelled within an already existing Access Module. Events are then made avail- able to the rest of the TeMIP Framework and can benefit from its services, for example, for color changes on the Iconic Map or dis- play in the Notification windows. To send events, the Data Collec- tor AM provides both a programming interface and a command script interface allowing events to be sent from within programs or from command line or shell scripts. The Data Collector AM and the SNMP AM benefit fully from the TeMIP Filtering and Correlation features, that can be made available to any other Access Modules through the Filtering and Correlation Toolkit provided with TeMIP Fault and Trouble Management; refer to SPD 45.24.xx for a detailed description of TeMIP Filtering and Correlation ca- pabilities. Supported transport mechanisms include both UDP/IP and DECnet. Event parameters can include managed object class and name, severity, event name and event text. This interface is available for a variety of client systems including DIGITAL UNIX, Ultrix, VMS and DOS and provides a very simple method of sending events to the Framework. Note: The source 'C' code is available for porting to other client en- vironments as required. The Alarm Generator AM generates OSI alarms or events on any entity in a distributed environment. It supports the Submit_Event directive on any entity class. 12 It uses a separate configuration file for each event type (partition, event id, and the list of mandatory arguments) that extends the Alarm Generator AM functionality to support new types of event, without mod- ifying its code. TeMIP Framework Presentation Modules TeMIP Framework includes two Presentation Modules. The Motif Graph- ical User Interface (GUI) provides an Iconic Map interface with pull- down, pop-up command, application and directive accelerator icon bar, and monitoring windows that consistently present all managed objects and operations. Consistent access is also provided by the Framework Command Line PM (FCL PM). Multiple screen support allows dedicated TeMIP FTM Presentation Modules to be displayed on different screens. The capabilities specific to the Motif GUI presentation style include: o Map windows that display the contents of a managed environment (for example, a domain) using icons to represent managed objects and their subordinate or child objects, as well as status icons. Users can select icons representing managed objects (both entities and sub- entities) and initiate management operations from a map window. Sev- eral map windows can be displayed at one time, each displaying dif- ferent views of domains of a managed environment. It is possible to define virtual domains (for display puroses only) that are in- dependent of the collection activity (collection domains). The de- gree to which the domains for display and those for alarm collec- tion purposes are decoupled, depends only on the way the domains on the director have been configured. It is therefore possible for these visual entities to benefit from the "sub-alarming" feature; new alarms on child entities produce a blinking, shaded area around the parent entity icon or object. The color of the shading shows the highest severity of the alarm(s). o A Shelf View feature, which allows you to describe the contents of an entity (that is, its child entities) using standard Iconic Map drawings and graphical objects instead of the box-based only mode. 13 o Icons can be of XPM format or vector file, thus allowing free form icon definitions, or supporting shape masks. The backdrop images support XBM vector format (Framework format). Through XBM library provided converters, users can get other formats such as GIF for icon building. Automatic TeMIP application startup at Iconic Map PM startup, and application launch facilities are also provided. o A Navigation box and ViewPort window that enable users to view an entire network configuration map at one time. With the ViewPort fea- ture, users can navigate to, zoom in, and select a particular por- tion of the total network environment to display in detail in the Map window. A Top and Bottom navigation area for hierarchical or non hierarchical navigation in the domain tree is also provided. o Management windows that enable users to select, perform, and view the results of management operations. As with map windows, several different management windows can be displayed simultaneously. o An integrated Toolbox window and other customization features that provide users with the ability to create, modify, or delete map icons, connecting lines, text, or other items in a map window. Users can create map icons, add Uniform Resource Locators (URLs) to icons in the map, add geographic maps or other backdrops, and add customized icons to the Toolbox for retrieval and re-use, as well as color cus- tomization of lines and texts. o The TeMIP Framework Dictionary Browser lets you examine the man- agement objects and their definitions stored in the TeMIP Frame- work dictionary. Using the Browser, the user can graphically view the types of entities that are configured for a TeMIP Framework. o Other features such as: - Map layers, which display or hide groups of objects defined as a logical subview. - Map filters, which filter graphical objects (backdrop, entities with alarms, text or graphics). - Domain shortcuts, which provide navigational accelerators (links) between domains. 14 - Graphical object tooltips, support of URLs on graphical objects, support of multi-line text objects... - A TeMIP to Web Browser interface, which provides online context- sensitive help in HTML format. The Framework Command Line PM provides character cell access to TeMIP Framework function and access capabilities. The interface supports only the Command Line mode. Command line recall and editing, abbreviation, online help, symbol sub- stitution, use of control key sequences, line continuation, and the typeahead function are all supported. Command Line mode also supports the use of scripts to automate fre- quently used TeMIP Framework command sequences. Users can set up ini- tialization files through the Command Line mode for establishing de- faults and executing startup directives. In addition, users can log any command to an output file for storage and review or it can be used by maintenance operators in the field via a portable PC and a modem. The Command Line mode provides online help. TeMIP Framework Distribution TeMIP Framework is by design distributed in the sense that it is im- plemented using the concept of Management Modules, which use a set of cooperative UNIX processes. TeMIP Framework distribution allows dis- tribution of these processes across different management systems called directors. However, the aim of the distributed TeMIP Framework is to distribute the services (also called call requests) offered by the var- ious Management Modules at: o Access level (that is, Access Modules) calls are distributed us- ing Entity Access Distribution. The principle of Entity Access distribution is that each global en- tity might have an associated Managing Director to which the Call Access is dispatched. 15 o Function level (that is, Function Modules) calls are distributed using Domain Distribution The principle of Domain distribution is that each domain has an as- sociated Managing Director to which the Call Function is dispatched, based on the value of the domain associated with the call request. Each Director is itself an entity and, as such, is manageable using the TeMIP features. Each instance of a Director has a globally unique name. A Distributed Director allows the forwarding and receipt of manage- ment requests to and from other Distributed Directors for any combi- nation of specified Verb, Entity, Partition at the Call Request In- terface. A Distributed TeMIP system consists of a Local Director and one or more Remote Directors. Three different types of Directors can be distinguished: o Server Director, allows forwarding or receipt of requests to and from other Distributed Directors. It can have either the TeMIP Frame- work Server license or the TeMIP Framework Access Module Server li- censes. o Client only Director, mainly runs Presentation Modules and requires the services of distributed directors as Servers. A Client only Di- rector, cannot receive requests from other directors, it requires the TeMIP Remote Presentation Modules (CLIENT) license. o Non distributed Director, does not allow forwarding or receiving requests to and from other directors, as it does not have any dis- tribution rights. Note: Only the FCL PM can be run on a TeMIP Framework Access Module Server system. TeMIP Name Service The distribution of TeMIP requires the use of the TeMIP Name Service. 16 TNS offers the following features: o Unique network-wide names; all TeMIP users and applications in the network use the same name to access a managed entity. o Use of the TCP/IP stack, instead of the DECnet-Plus communications protocol stack. o Simplified management of network entity names that are stored and maintained by TNS, eliminating the need to update and maintain a local Management Information Repository on each TeMIP director. o Caches, or saves, information obtained from previous requests to look up a name. Caching maximizes overall performance and reduces network traffic. o Security: access to TNS names can be assigned to individuals, or to Access Control groups. It is possible to install the TNS server on a TeMIP V3.2-A director system, or on a separate UNIX system. With TNS, installation of the DECnet software is needed on a TeMIP V3.2- A director only if the following TeMIP components (that make direct use of DECnet) are to be used: o DNA4 (DECnet Phase IV o DNA5 (DECnet-Plus) o TeMIP OSI AM (use of DECnet is optional) o Data Collector AM (use of DECnet is optional) TeMIP Framework Extensibility TeMIP Framework is an extensible management platform to which other TeMIP software modules, option packages, third party, or user-developed Management Modules can be added. 17 Third parties and users can develop software modules for the TeMIP Net- work Management Family of Products to provide access to and manage- ment functions for any manageable object. Software and documentation for the development of integrated TeMIP modules are available as part of TeMIP Framework and the Visual TeMIP Developer's Toolkit. For more information about Visual TeMIP, refer to SPD 60.64.xx. Refer also to the TeMIP Graphical ASCII Toolkit SPD 64.82.xx, the TeMIP OSI Manage- ment Toolkit SPD 51.28.xx and the TeMIP ESA SPD 70.40.xx. TeMIP Framework includes tools that enable on-site enrollment of Man- agement Modules. Documentation required for third party module enroll- ment must be supplied by the module developer. The Presentation Module Toolkit is a set of tools and a library of rou- tines that make possible the different ways of integrating Presenta- tion Modules into the TeMIP Framework Iconic Map (for example, the launch mechanism, enrollable operation, enrollable application, expand field application stand-alone PMs...). Refer to the Visual TeMIP SPD 60.64.xx for further details. HARDWARE REQUIREMENTS DIGITAL UNIX Alpha AXP Processors Supported: AlphaServer 8200 AlphaServer 8400 DEC/4600, DEC/4700 DEC/7600, DEC/7700 DEC/10600 AlphaServer 2000 AlphaServer 2100 AlphaServer 4000 AlphaServer 4100 AlphaStation 600 DEC/3500, DEC/3500S, DEC/3500X DEC/3800, DEC/3800S 18 DEC/3900 AlphaServer 400 AlphaServer 1000 AlphaStation 200 AlphaStation 250 AlphaStation 255 AlphaStation 400 AlphaStation 500 DEC/2300S DEC/2500 DEC/3300, DEC/3300L, DEC/3300X, DEC/3300LX DEC/3400, DEC/3400S DEC/3600, DEC/3600S DEC/3700 Disk Space Requirements: Disk space required for installation: /usr 115,000 Kbytes /var 12 Kbytes Disk space required for use (permanent): /usr 0 Kbytes /var 500 Mbytes 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. Memory Requirements: The minimum memory supported is 96 Mbytes. However, the use of this software in conjunction with increased memory capability improves per- formance. Note that more memory is required if you are operating in multi-user mode. Recommended Configuration For running a TeMIP Framework system: 19 DIGITAL UNIX o AlphaServer 1200 or 400. o 256 MB memory, or more. o RZ28 disks or equivalent disk space. o Ethernet controller. For running TeMIP Client system: o AlphaStation AU. o 96 MB memory, or more. o RZ26 disk or equivalent disk space. o Ethernet controller. For running TeMIP Access Module Server system: o AlphaServer 800. o 128 MB memory. o RZ28 disk or equivalent disk space. o Ethernet controller. Note: Specific network environments may require larger configurations. Optional Hardware For multi-screen support, an extra graphical card (PMAGB-B) must be supplied. SOFTWARE REQUIREMENTS o DIGITAL UNIX Operating System V4.0D o DECwindows Motif Note: DECwindows Motif is compliant with OSF/Motif. 20 o CDE OPTIONAL SOFTWARE o Any other software modules or packages necessary for communication with the managed network elements. o A TNS server kit on UNIX can be installed anywhere on the network to manage DECnet networks. YEAR 2000 READY This product is Year 2000 Ready. The testing used to confirm the Year 2000 readiness of this product included code assessment and system tests to verify transition dates. GROWTH CONSIDERATIONS The minimum hardware/software requirements for any future version of this product may be different from the requirements for the current version. DISTRIBUTION MEDIA This product is also available as part of the UNIX Consolidated Soft- ware distribution on CD-ROM. Please refer to the ordering information for each Software Media reference. ORDERING INFORMATION TeMIP Framework Server This includes all TeMIP Framework distributed Management Modules: Software Licenses: QL-4RCA*-AA Software Media: QA-4RCAA-H8 Software Documentation: QA-4RCAA-GZ 21 Software Product Services: QT-4RCA*-** TeMIP Remote Presentation Modules This is the Client director license. Software License: QL-4REA*-AA Software Product Services: QT-4REA*-** TeMIP Access Module Server This includes all TeMIP Framework distributed Management Modules ex- cept the Iconic Map Presentation Module. Software License: QL-4RDA*-AA Software Media: QA-4RDAA-H8 Software Documentation: QA-4RDAA-GZ Software Product Services: QT-4RDA*-** Software Media and Documentation must be ordered using either: o QA-4RCAA-H8 and QA-4RCAA-GZ or QA-4RDAA-H8 and QA-4RDAA-GZ The QA-*****-H8 part numbers include the QA-*****-GZ documentation kits, but you can order an extra copy of the documentation using the QA-*****- GZ number, if required. Note: * Denotes variant fields. For additional information on avail- able services, or hardware platform tiers, 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 in- formation about the DIGITAL licensing terms and policies, contact your local DIGITAL office. This product uses the FLEXlm Software License Key system. 22 The licensed software can be used up to the limit specified in the li- cense file. The scheme used is trust based, which means that it does not use any machine-specific values or count of users to rigidly en- force license compliance. A FLEXlm key must be obtained using the request form provided with the Cover Letter, temip-license-form.txt. For use with any prior version of TeMIP, the LMF checksum is located on the Software PAK received as deliverable upon order of the Software License. This checksum is only valid for LMF, that is, for versions prior to Version 3.2 of TeMIP for DIGITAL UNIX. SOFTWARE PRODUCT SERVICES A variety of service options are available from DIGITAL. For more in- formation on these services or other available Network Management Ser- vices, contact your local DIGITAL office. SOFTWARE WARRANTY This software is provided by DIGITAL with a 90 day conformance war- ranty in accordance with the DIGITAL warranty terms and applicable to the license purchase. The above information is valid at time of release. Please contact your local DIGITAL office for the most up-to-date information. [R] Motif and OSF/Motif are registered trademarks of Open Software Foundation, Inc. FLEXlm is a registered trademark of GLOBEtrotter Software, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. [TM]The DIGITAL Logo, DEC, DECnet, AlphaStation, AlphaServer, DECwindows, DIGITAL, RZ and TeMIP are trademarks of Digital Equipment Corporation. © 1998 Digital Equipment Corporation. All rights reserved. 23