READ THIS FILE COMPLETELY BEFORE BEGINNING PRODUCT INSTALLATION Copyright 2008 HP Product Name: ASAP 3.1 Server Product ID: SE30V3 - G-series HSE30V3 - H-series Component Products: I. Basic Product Installation Instructions 1. Ensure that requirements for using this product are met (see Section IV Product Requirements below). 2. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section V Installation Prerequisites below). 3. Review the file USRGUIDE.PDF (in the subdirectory NSK_SW on this CD) containing the IPSetup User Guide, which provides instructions for using IPSetup, a utility provided on the CD that enables installation of Independent Products. You will need Adobe Acrobat Reader to read or print the IPSetup User Guide. Visit Adobe's website to download the latest Adobe Acrobat Reader: http://www.adobe.com 4. Decide whether you will use DSM/SCM to move files to Installation Subvolumes (ISVs) after files are placed on the workstation. Using DSM/SCM is optional, but is recommended when DSM/SCM is available. 5. Follow the pre-installation instructions in Section II below, if any, before continuing to Step 6. 6. Run IPSetup to place (move files from the CD to the workstation) and install (move NonStop Kernel files to correct ISVs) this product. If TCP/IP and FTP are unavailable, or if you have problems with automatic file placement, use the instructions in the IPSetup User Guide section "Manual Software Placement Using the IPSetup TACL Program" to manually place NonStop Kernel files. This product contains both NonStop Kernel components and workstation components. You must place each component type separately. To restart the installation program after placing the first component type, click SETUP.EXE in the root directory. 7. Follow the post-installation instructions in Section III below, if any, after using IPSetup to place and install this product. II. Pre-Installation Instructions 1. ASAP 3.0 and above are licensed product. Run SYSINFO on each system to be licensed and E-mail the SYSINFO output for each system to License.Manager@HP.Com. Please be sure to obtain and install the license files before attempting to install ASAP 3.0 or any subsequent release. Note this only has to be done once. If you have obtained license files for ASAP 3.0 or subsequent then you do not need to obtain license files for any future release unless the term for the original license has expired. 2. Ensure that requirements for using this product are met (see Section the Required Hardware and Required Software sections above). 3. Ensure that prerequisites for the installation utility and any product-specific installation requirements are met (see Section D Installation Prerequisites below). 4. Review the file USRGUIDE.PDF (in the subdirectory NSK_SW on this CD) containing the IPSetup User Guide, which provides instructions for using IPSetup, a utility provided on the CD that enables installation of Independent Products. You need Adobe Acrobat Reader (available on this CD) to read or print the IPSetup User Guide. 5. Decide whether you will use DSM/SCM to move files to Installation Subvolumes (ISVs) after files are placed on the workstation. Using DSM/SCM is optional, but is recommended when DSM/SCM is available. 6. If you are using the ASAP Extension make a copy of the file $SYSTEM.SYSTEM.ASAPUSER. FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAPUSER, ASAPSAVE.*, SAVEALL 7. If you are upgrading from ASAP 3.0 or an earlier release to ASAP 3.1 then this SPR includes EDL changes for several entities. All records in any old ASAP databases need to be saved prior to installing this version of ASAP. It is very important that you save the records using the old version of ASAP, then restore them using the new version of ASAP. Please follow these instructions to save your current ASAP databases. From the central ASAP collection node: TACL> ASAP +VOLUME $SYSTEM.ASAPSAVE +MONITOR/OUT ASAPOBEY/, OBEYFORM +RANK/OUT ASAPOBEY/, OBEYFORM +MONITOR/OUT ASAPOBEY/ \, OBEYFORM +RANK/OUT ASAPOBEY/ \,OBEYFORM (preceding commands must be done for each remote node) Once data from all nodes has been saved then shutdown ASAP and purge the ASAP objectives database on each node. The objectives database file location is set with the SET OBJECTIVESDB command, or it defaults to $SYSTEM.ZASAP.DBOBJ. 8. If you are upgrading from an earlier version of ASAP please read the following steps. If you have any ASAP3* files, save the ASAP CI and all EDL files. If you have archived data with the old version of ASAP that you would like to view later, you must save the following files: FUP - VOLUME $SYSTEM.SYSTEM - DUP ASAP, ASAPSAVE.*, SAVEALL - DUP ASAP3EDL, ASAPSAVE.*, SAVEALL - DUP ASAP3SYS, ASAPSAVE.*, SAVEALL - DUP ASAP3APP, ASAPSAVE.*, SAVEALL 9. Run IPSetup to place (move files from the CD to the workstation) and install (move NonStop Kernel files to correct ISVs) this product. If TCP/IP and FTP are unavailable, or if you have problems with automatic file placement, use the instructions in the IPSetup User Guide section "Manual Software Placement Using the IPSetup TACL Program" to manually place NonStop Kernel files. 10. Follow the post-installation instructions in Section B below, if any, after using IPSetup to place and install this product. III. Post-Installation Instructions 1) Invoke the INSTALL^TEMPLATES TACL macro to install this NPV's EMS template file(s) in the running system. This TACL macro and instructions for its use are given in Support Note S92067B. The INSTALL^TEMPLATES TACL macro is distributed on the SUT and can be located in the ISV volume: $.ZINSAIDS.TACLMACS. To print the usage notes, LOAD the file containing the macro and, at the TACL prompt, enter: INSTALL^TEMPLATES /OUT /HELP 2) Run ASAP setup to update the ASAP subsystem with the following commands: a) TACL 1 > VOLUME $.ZASAP b) TACL 2 > OBEY INSTALL c) Perform "Full Install on this node" from the central ASAP database node. d) Perform "Remote Monitor Install" for any additional Licensed ASAP nodes that you wish to monitor. See Section 2 of the ASAP manual for detailed information regarding subsystem configuration. e) If you are using the same volume and subvolume location for the ASAP database files, you must delete the ASAP version 1 database files or version 2 database files before starting the ASAP Version 3 environment. f) If you saved ASAP database records prior to the install then reload them now. From the same central node that you saved the data on please enter: ASAP + OBEY $SYSTEM.ASAPSAVE.ASAPOBEY 3. If you are using the ASAP Extension copy the duplicated file from the Pre-Installation instructions Step 1 back to $SYSTEM.SYSTEM. FUP - VOLUME $SYSTEM.ASAPSAVE - DUP ASAPUSER, SYSTEM.*, PURGE, SAVEALL 4. Start the new ASAP version. 5. When looking at ASAP data from earlier ASAP versions please be sure to use the old ASAP CI and EDL files saved to the $SYSTEM.ASAPSAVE subvolume if you performed the save step defined above. 6. Please ignore the "Unknown ASAP config option" message from ASAP Extension if you are using an earlier version of ASAPX with ASAP 3.0. The message does not affect the operation of ASAPX. IV. Product Requirements Required Hardware: NonStop K-series servers NonStop S-series servers HP Integrity NonStop servers Minimum OS Release: NonStop Kernel release G05 or higher Required Software: (S-series NonStop servers) T0346A07^ABO RDF/IMP If using RDF T9050G06 NONSTOP KERNEL T9550G06 SOCKET LIBRARY T9552ACF TCP/IP FTP Required Software: (H-series NonStop servers) T0346H08 RDF/IMP T9050H01 NONSTOP KERNEL T9550H01 SOCKET LIBRARY T9552H01 TCP/IP FTP Microsoft Windows Vista, Microsoft Windows XP, Windows 2000, Microsoft Windows ME, or Windows NT 4.0 or later. Microsoft TCP/IP stack and FTP client Disk Space Requirement: ZASAP subvol 9.0MB $System.system run time files 7.0MB ASAP Dictionary files 1.1MB Refer to the section 2 of the ASAP manual for ASAP database file sizes. Memory Requirement: 16MB per cpu minimum. V. Installation Prerequisites Required Hardware: NonStop K-series servers NonStop S-series servers Communications controller allowing file transfer from PC to HP NonStop Server PC with 486 or higher processor and all of the following: CD-ROM drive VGA or higher-resolution video adapter and monitor Microsoft Mouse or similar pointing device Communications controller allowing file transfer from PC to HP NonStop Server Required Software: Microsoft Windows Vista, Microsoft Windows XP, Microsoft Windows 2000, Microsoft Windows ME, or Windows NT 4.0 or later. Microsoft TCP/IP stack and FTP client VI. Manuals for this CD: To access the documentation for this product, please see the HP NonStop Technical Library at http://techlibrary.cac.cpqcorp.net/ntl/ or your NonStop Technical Library CD/DVD disc VII. CD-ROM Root Directory Contents AUTORUN.INF File containing CD AutoRun commands. AXDIST.EXE Microsoft redistributable library files. IPSETUP.CNT File containing help contents for the CD installation utility IPSetup. IPSETUP.EXE File containing the main executable for IPSetup. IPSETUP.HLP File containing help text for IPSetup. LICENSE.TXT File containing limited-use Software Licensing Agreement with the licensing terms governing this product. README.TXT File containing product and installation information (this file). SETUP.EXE File containing the Launcher executable. NSK_SW Subdirectory containing NonStop Kernel component files, including installation utilities and instructions. WS_SW Subdirectory containing workstation component files (if applicable to this product), including installation utilities if any. SOFTDOCS Subdirectory containing all Initial Product Version / Product Version Update Softdocs. ADDENDUM Overview: ASAP 3.1 is a bug fix release that also includes changes to support NonStop Blades servers. For NonStop Blades servers the Disk entity has been changed to support storage Cluster I/O Module (CLIM) devices; the Process and ProcessBusy entities are changed to support process Affinity, IPU, and CBusy attributes; and the CPU entity is changed to support the number of IPU's for a logical CPU. The CLIM Interface Protocol (CIP) is now supported with a master CIP entity that contains 3 sub-entities: CIPCLIM to show statistics for CLIM devices; CIPMonitor for CIP Monitor processes; and CIPProvider for CIP Provider processes. Minor problems have also been corrected with the Comm, Disk, File, Process, Swap and TCP/IP entities. Refer to the problems corrected section for further information. T0402V03 for S-series/K-series processors is equivalent to T0402H03 for Integrity NonStop servers and NonStop Blades servers. New Feature History: ==================== AAM The CLIM Interface Protocol (CIP) entity and its sub-entities have been added to better support NonStop Blades Servers. AAM Several Blades-specific attributes have been added to the CPU, PROCESS and PROCESSBUSY entities to better support NonStop Blades servers. These include process Affinity, IPU number, CBusy and the count of IPUs. V03 The ASAP server now requires a license per node in order for ASAP to run. To obtain a valid license, run SYSINFO on each system to be licensed and E-mail the SYSINFO output along with the type of license and number of CPUs to license.manager@hp.com. V03 ASAP TCPIP is now included in the ASAP core products T0402V03 and T0402H03. TCP/IP supports v4, v6 in all modes, ICMP, IP, Process, QIO, RTE and UDP, ARP, IGMP, LOOP, MONGQ, SOCK ICMP6, IP6, SubNet, Route and Port stats. Support for TELSERV process, Service and Window stats are also included in ASAP core products. This results in 19 new TCP/IP and TELSERV entities and more than 1000 attributes. V03 Virtual memory (Swap SGP) support has been added. ASAP 3.0 Reports on virtual memory (KMSF) per processor and monitors and reports on all the configured swap files for each CPU. A total of 49 SWAP attributes are now provided in ASAP 3.0. Some of the statistics maintained by the Swap SGP are percent full for all configured swap files, percent full for each individual swap file, reserved memory which is the total virtual memory allocated for the CPU. The Swap SGP also displays the amount of virtual memory allocated for each swap file. See the ASAP Server manual for all of Swap SGP statistics and threshold support, or mouse over the SWAP entity attributes in ASAP client for an explanation of each SWAP attribute. V03 CPU memory statistics have been added. New attributes include memory size, swappable memory, free memory, locked memory, maximum locked memory, and highest locked memory. V03 ASAP can now host real-time local/proxy websites and can now optionally integrate with Systems Insight Manager. New reporting capabilities are highly customizable, eg there are 15 new notify content controls and checkboxes for setting up ASAP's reporting. New HTML entity attribute grid and graph reports that can also send notifications to ASAP users about the overall state of objects. Reports can be sent via Email, wireless phones, or customer websites. Reports can also be integrated with HP Systems Insight Manager (SIM). Refer to the ASAP Client Manual for further detail. V03 New HTML entity attribute grid and graph reports that can notify ASAP users about the overall state of their NonStop servers. Reports can be sent to Email addresses, or wireless phones or to a customers websites. Reports can be integrated with HP's Systems Insight Manager (SIM). V03 ASAP database performance can be greatly improved in high-volume large-record environments. A new SET option allows you to configure the ASAP database to use a Relative database file. The new set option allows ASAP users to control which entity should be configured to use relation files. One possible indication that a relative file DB is needed is when the ASAP Log has a high volume of missed sample log records. To achieve higher ASAP database performance the user simply configures an ASAP collector to create a Relative file by using the new SET PARTITION option. The syntax is SET PARTITION TYPE R. V03 The count of unique batch jobs has been added to the Spooler SGP. A new attribute, UBatch, counts the number of unique batch jobs in a Spooler subsystem. V03 RDF domain name parsing and support has been strengthened, so that MONITOR commands cannot be issued against RDF subdomains. 2.8 ASAP now supports the optional ASAP TCP/IP Plug-in. The TCP/IP SGP monitors 9 new TCP/IP entities and 3 new TELSERV entities. For TCP/IP, the ASAP TCP/IP Plug-in monitors the ICMP, IP, TCP, QIO, RTE and UDP layers of the TCP/IP stack, and also monitors TCP/IP Ports, Routes and Subnets. For TELSERV, the new Plug-in monitors TELSERV Processes, Services and Windows. Taken together the new Plug-in provides a never seen before real-time view of the TCP/IP and TELSERV activity on NonStop Servers. See product SE35V1 for more information on the ASAP TCP/IP Plug-in. 2.8 The CPU SGP reports on the number of Blades that are active and objectives can be set on active Blades count using the GOAL command. For example: GOAL CPU, BLADES = 3 -- Sets objective for TMR system. When the objective is met the client displays Blades as "A B C". When the objective is not met because Blade B is down the client displays Blades as "A C". GOAL CPU, BLADES = 2 -- Sets objective for DMR system. When the objective is not met because Blade A is down the client displays Blades as "B". 2.8 The ProcessBusy SGP now monitors up to 10,000 processes per Cpu to determine the n-busiest process in the CPU. 2.8 The Disk SGP supports 2,000 physical disk devices on a node. 2.8 The Expand SGP allows objectives to be set for the primary Cpu of Expand lines. For Example: GOAL EXPAND, CPU=1 GOAL EXPAND $LHNY, CPU=3 2.8 PROCESS Command and Detail support long abstract names 2.8 A new file ASAPMEAS is now distributed as part of ASAP 2.8 server and beyond. ASAPMEAS provides in-depth Measure and analysis on demand simply by selecting an object in the ASAP client and clicking Show Related Measurement 2.8 APP, FILE, PROCESS, TCPIP, TELSERV commands support new AGE option which allows users (and the ASAP client) to control which objects appear. For example, AGE 15 indicates only objects stats within the last 15 minutes will be displayed. See Also ASAP Client Show Removed Objects checkbox on the General TAB of the 2.8 The EDL language has been enhanced to allow relationships to be defined between entities. This aspect of EDL is often referred to as Relation Definition Language (RDL). RELATION and MAP statements were added to the EDL language. 2.8 Limits on maximum EDL attributes were removed (was 100) 2.7 No New Features 2.6 No New Features Problems Corrected History: =========================== AAM The ASAP Client Graph Object History function sometimes fails when issued against TCP or TELSERV objects or against any other entity where the database is defined as a type relative file, or an ASAP CI command using the TIME option sometimes fails against an entity where the database is defined as a type relative file. AAM Comm SGP could create a saveabend file due to an arithmetic overflow. AAM Goal set on TCP UDP BadHdrLen attribute does not work correctly. AAM ARP abbreviation for TCPARP entity does not work in ASAP CI commands. AAM Errors in the TCP ICMP and ICMP6 entities where XSum and InPackTooBig did not support goals correctly and some ICMP6 data was shown as ICMP data. AAM Cannot display specific APP domains. AAM Intermittent save abend files created for the ASAP process $ZOOK. AAM ASAP monitor generating false 1031 messages intermittently. AAM CPU statistics Pgs%, Pcb%, Pcbx%, TLE%, Seg% and Map values were not displayed correctly. AAM Error 1028 Invalid Sys.Sysname received. When a Monitor System \, ADD is performed from the ASAP CI. AAM SET PARTITION TYPE or SET PARTITION REFRESH are applied to DEFAULT (all entities) instead of the entity specified. AAM The Process entity did not round to the closest decimal point for several attributes in all prior versions of ASAP, resulting in values that weren't as accurate as they could be when very small values were produced. AAM Could not use the MONITOR command to monitor specific TELSERV processes, services or windows. AAM The Comm SGP could report error 4744 device inaccessible messages when there is a large number of monitored communication objects. AAM False EMS alerts "CPU Switch" or "Path switch" against DISK objects could occur under high system load. AAM Disk volume names are truncated for Disk < disk>, Samples command. AAM The Disk SGP could report error 1744 Disk device inaccessible errors. AAM The Disk SGP could abend on J06.02. AAM Swap SGP is not reporting on stopped swap files or when a CPU is down. AAM ASAP Swap SGP may generate "unknown stat^sum^requests" in the ASAPLOG file when more than 5 CPU's are configured on the node. V03 Comm SGP not always setting correct state for the attributes that the user had set goals against. V03 Expand SGP abends when the MONITOR EXPAND, LIST command is entered from the ASAP CI. V03 Disk SGP could abend when volumes are deleted from the configuration. When a large number of disk volumes are deleted from the nodes configuration. V03 Cannot start ASAP collector if the system is a different node than the system where ASAP collector is to be started. V03 False CPU alert notifications being sent and displayed by the ASAP Client. When the monitor sends a request to an SGP and the request times out. The timeout occurs because a CPU SGP is busy. 15:51 \FIELD ASAP ERR Send to SGP $AAA error: 40 V03 ASAP monitor not allowing sufficient time for SGP's to shutdown. SGP processes may be running after the monitor shuts down. V03 Disk Error 3402 generated when volume is configured for different groups. V03 Running in a mixed ASAP version down rev CPU records could have incorrect values for Chits and discs. When sending records to an ASAP 2.8 collector or later collector. V03 ASAP could stop a process not started by ASAP after issuing the shutdown command. V03 Disk SGP reporting error 3402 when using -B path V03 Multiple records could be displayed for the same disk volume when an object was running and then deleted. V03 TMF mounts show as a warning in ASAP Client after they have been removed. V03 TMF Mounttime UP events are not generated when a mount is rejected. V03 Monitoring processes by their object filename is too resource consumptive. V03 TCP SGP consumes too much virtual memory. V03 Some forms of TCP sub-entity names and/ or abbreviations cause ASAP CI to abend. V03 Goals could be applied incorrectly to TCP ICMP, IP, QIO, RTE, UDP domains. V03 GOAL/RANK SERVICE , LIST commands fail if issued from ASAP Client. V03 Updater UP events are not always generated for the RDF entity. V03 ASAPFIL, ASAPPRO and ASAPTCP SGPs can abend if MaxDomains is exceeded. V03 Custom event numbers are not generated when used with CPU entity domains. V03 Custom event numbers are not generated when used with TMF entity domains. V03 Objectives (goals) could mistakenly be applied to the wrong domain. V03 File SGP gives error message 'NoFile' when a large fileset is added to ASAP and when files are continuously deleted from the fileset. 2.8 [AAJ] ASAPNCP SGP could loop/not return end-to-end node statistics. 2.8 [AAJ] CPU SGP's abending after blade/slice integration 2.8 [AAJ] Missed samples being reported for Expand lines. Could also occur with Disk and Comm SGP's 2.8 [AAJ] The ASAPTAP SGP would not monitor all virtual tape drives. 2.8 [AAJ] The ASAPTMF SGP could abend at each interval. 2.8 [AAJ] The ASAPPRO SGP could abend when monitoring certain nonstop processes. 2.8 [AAJ] Comm line status attribute not being shown as EMS event. 2.8 [AAJ] CPU Queue counter is not correct. 2.8 [AAJ] Disk devices not always displaying the warning state for down paths on the Client. 2.8 [AAJ] Disk busy counter not always correct on G and H series nodes. 2.8 [AAJ] Disk Device inaccessible messages when using the backup path on the primary volume or MB path on the mirrored volume. 2.7 [AAH] The canned ASAP rule named SECURE failed to properly re-secure disk files. 2.7 [AAH] The canned ASAP rule named PRIMARY did not work to primary disk paths. 2.7 [AAH] The Process SGP could generate excess activity against the disk process by requesting the program filename at each interval using Process_GetInfoList_ even though it already knew the program filename from a previous request. 2.7 [AAH] The Process SGP would sometimes report incorrect MSent, MRecv and PFaults values for the first interval after a monitored process failed. 2.7 [AAH] The percentage ranking scheme did not work correctly for all ASAP entities when Historical ranking was used. 2.7 [AAH] The MONITOR FILE, LIST, DETAIL and MONITOR PROCESS, LIST, DETAIL commands did not provide useful information about the dynamic object pool size and utilization, and an incorrect default pool size was shown in the help text for HELP SET FILE and HELP SET PROCESS. 2.7 [AAH] The COMM SGP did not report the link level status for X25 lines. The status of the line would be displayed as up when the link status was down or connecting. 2.7 [AAH] The ASAP CI would report an additional comm line from a previous sample whenever a line was no longer being monitored. 2.7 [AAH] The COMM SGP would report Comm lines that were added via SCF when auto-discovery was off. 2.7 [AAH] COMM SGP would not report Comm lines when the IOP was not started. 2.7 [AAH] The DISK SGP would not report the backup path as down for an unmirrored volume when the backup path was downed by the operator or due to a hardware failure. 2.7 [AAH] The EXPAND SGP could report SPI -8 errors when an Expand line is aborted for a long period of time, or could occur if the $zexp is stopped and restarted during an ASAP sample interval. 2.7 [AAH] The ASAP CI could abend after issuing a startup Monitor command. 2.7 [AAH] The DISK SGP reported lines inaccessible on a device subtype 53 when the backup path was being used. 2.7 [AAH] The BUSIEST PROCESS SGP did not display the current priority, but was displaying the initial priority when the process was first started. 2.7 [AAH] The COMM SGP did not display correct rate value, or input/output byte values or input/output data values. Also did not display the correct program object file name for the communication line. Did not always display the correct pin. 2.7 [AAH] The COMM SGP did not always collect line stats when the line was up. 2.6 [H01] ASAP Disk SGP showing invalid flag set for volumes in the up state. 2.6 [H01] ASAP reported last state plus one for an historically ranked domain when an alert continued into the second interval even if the percentage comparison would have produced a higher state. 2.6 [H01] The FILE command would output ordinary filenames with backslash characters instead of period characters and ASAP required the characters to be entered when retrieving information about a specific file. 2.6 [H01] ASAP would fail to automatically create an aggregate-only domain for processes being monitored by a wildcard specifier or object filename if the domain name contained logical prefixes. 2.6 [H01] The ASAP MONITOR command could allow a FILE domain name containing more than 5 levels to be accepted under certain conditions. 2.6 [H01] ASAP did not report that files were SQL/MX tables, views and indexes. 2.6 [H01] ASAP would fail to create obeyform output when the M, OB command was entered. 2.6 [H01] ASAP Disk SGP not returning correct largest fragment state for a down disk. 2.6 [H01] ASAP CPU SGP not displaying correct state value for Breakpoints when the CPU is down. 2.6 [H01] ASAP Client not displaying the correct value for disk block Splits. 2.6 [H01] The SPOOLER SGP could improperly format the <#OBJECT> token in action strings. 2.6 [H01] Actions against FILE objects could fail when the file was monitored using a wildcard name. 2.6 [H01] ASAP would fail to generate an UP event when a TMF transaction duration alert had returned to normal. 2.6 [H01] In certain cases an ASAP SGP could abend if MaxObjectives, as defined in the entity EDL, was exceeded. 2.6 [H01] The ASAP Disk SGP could abend. Occurs when more than 33 volumes are monitored and the collector does not reply within 3 minutes to an update request. 2.6 [H01] The Discrete Objectives Threshold Engine would abend. Would occur when a disk volume was renamed. 2.6 [H01] The ASAP Disk SGP does not display the correct disk path to the client when the -M path is down. Reports that the -MB path is down on the client. Occurs when the Mirror path is down. 2.6 [H01] The ASAP Disk SGP does not display the correct Operational state for a volume that has a configured backup path, and the mirrored disk does not exist. Would occur when the backup controller is configured and the mirrored disk is not configured. 2.6 [H01] Expand SGP would report down EMS events in a multiline environment when the Path for the multilines was not configured on the node. Known Problems Remaining: ========================= NONE