Home

HP Web-Based Enterprise Services 4.5 User's Manual

1. DEC AXPVMS VMS731_LAN V6 0 DEC AXPVMS VMS V7 2 2 If you continue recovery data for the patches listed above will be deleted The deletion of recovery data does not affect the installation status of patches applied to products that are not participating in this operation However continuing with this operation prevents you from uninstalling these patches at a future time by use of the PRODUCT UNDO PATCH command FF ox Overall WEBES Release Notes 1 6 WEBES Known Issues Do you want to continue NO YES The messages appear because of a new feature that allows OpenVMS patches to be removed You only see these messages if you have installed the new OpenVMS PCSI patch that adds the feature or you are running a newer version of OpenVMS that includes the feature and you have installed OpenVMS patches that use the feature The new feature has a limitation making it impossible to preserve patch recovery data when a product such as WEBES is installed or uninstalled because installing or uninstalling WEBES in an operation not involving patches that alters the product database Prior to the addition of the feature OpenVMS patches could not be removed Nevertheless note that installing WEBES will prevent you from using the new feature to remove any OpenVMS patches listed Otherwise you can safely ignore the messages and continue with WEBES installation 1 6 4 6 Upgrade Requires Same Node as Install Upgrades require t
2. Support for sending a subset of WEBES call out reports as SNMP Service Type 3 Traps to HP SIM Systems Insight Manager e Support for storing entitlement data for the following types of managed entities in addition to EVAs which were provided in previous WEBES releases Command View EVA Servers running in SMA or Server mode on Windows A redesigned Installation Configuration Wizard for Windows that no longer requires the launching of a Web browser WEBES health checks that can alert the user upon failures enabled for Windows Pentium only so far Virtual Library System VLS VLS support in WEBES facilitates improved uptime for customers entitled by warranty or an appropriate support contract ID including lower failure to repair time and higher first time fix rates VLS supports automated event monitoring using custom rules including verification of monitoring connectivity WEBES detects actionable field replaceable unit FRU failures including reporting to customers and engaging the HP backend as needed WEBES supports automatic entitlement of VLS nodes subject to new bundled product labelling Rev 9 8 06 1 6 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 5 New in this Release Note The preliminary implementation of HP ISEE Virtual Library System VLS Support is disabled in WEBES 4 5 by default A message will display if you try to configure support of VLS devices The Beta program wi
3. 1 6 1 3 WEBES Installation Issue on ISEE OSEM Host 0 0 000000 eese 1 9 1 6 1 4 Intermittent Socket EOS 6 55555 6 UE nirre mk RUE bir kurt pkoi didit 1 9 1 6 1 5 WEBES Configuration Information Not Restored 00 0000 ss 1 10 1 6 1 6 WEBES Output Log Files Grow Without Bound eec ete 1 10 1 6 1 7 WEBES Temporary Files Use Disk Space cse mmm 1 11 16 18 Backward Compatibility sais euge stoperi ere IUD VER Oso tub pre tiin 1 11 1 6 1 9 Director Process Not Responding 2 015 ooo ese eke ete erine 1 12 1 6 1 10 Director Process Stopping When Qut of Memory ici o s erp nme cese 1 12 1 6 1 11 Upgrade Requires Reinitialized Log 0 0 0 eee 1 12 1 6 1 12 Errors When the Director or WCCProxy is Restarted Too Soon 1 13 1 6 1 15 Service Cockpit Compatibility sree ool sus Rem rmn 1 13 1 6 1 14 Upgrading Versions Older Than Two Releases sees 1 13 1 6 1 15 WEBES Uninstall Affects ISEE Client WCCProxy 00 00008 1 13 1 6 1 16 Changing Time Zone Causes Incorrect Report Time 0 00 1 14 1 6 1 17 Errors From desta sicllqsap on Commands 00 00 0000 ee ee eee 1 14 1 6 2 Windows WEBES ISSUES ciy enai ra EEE toe eo opu ER Ropa etna cp EP EHE cmi DR Ceu deci 1 15 1 6 2 1 ClassNotFoundExceptions in Director Log 1 0 0 eese 1 15 1 6 2 2 WEBES Installation Appears to Hang iis yx veo biased mera orm Sib ye binw k iiss 1 16 1
4. ISSUES ii enre nees renes ies CREER e EROR CE ea ER RR RE ROS 1 22 1 6 4 1 Set ODS 5 Attributes Before Issuing WEBES CLI Commands 1 22 1642 JBEX BEITODS ic pissed terne eser aom dee ech RoR Ee aa ee m eee Rn 1 23 164 3 Cannot Get Local Host Name srece onner enur tiap ioe ERE PEN Soma pore Dee 1 23 1 6 4 4 Continuous CPU Usage After Daylight Savings Time Change 1 24 1 6 4 5 New OpenVMS Patch Removal Feature 0 0 00 cee eee ee eee 1 24 1 6 4 6 Upgrade Requires Same Node as Install cen rrr roe ree 1 25 1 6 4 7 Alternate Boot Start and Stop Methods 00 0 0 eee eee eee eee 1 25 1 6 4 8 Cannot Get SMTP Notification on OpenVMS 0 0 0 0 1 25 LT Further InfOrmabOh 45 424 decewas terse tocat ree ne po uos UR ue ene a o3 ease samege 1 27 2 System Event Analyzer 2 1 2 1 Sutnmaty 22cm e 9re E RRERROHE Y t EE e RR EAR e Pg dep ared Renee eedys 2 2 2 2 Supported PLOGUCUS uis eps doe rene reee ugue ike i Rupeok E apie Bep DEC RUE n 2 2 2 3 SEA Known ISSUES 22 eot erre somone Coates Meee OE oed ug ete E dev bep b wie Gow 2 4 2 1 General SEA S8UGS 2 donus xg agp p D RARE RR e omo ace teu XR RR HR ce Ru Reina 2 4 2 3 1 1 System Error Log Initialization while Director is Running Causes Errors 2 5 2 3 12 Backward Compatibility ess ssor tee iter Eh bora elg er iie BRI pee balle REGE 2 5 2 3 1 3 Serial Number Prevents Rules from Working 0 000 000 e
5. Program FilesNsomeDirectoryMdisk read errors errlog Windows interprets it as C gt wsea trans input C Program FilesNsomeDirectoryMdisk read errors errlog Furthermore with Windows if a backslash character is placed at the end of a double quoted directory the double quote following the backslash is treated as part of the text passed to the program This causes Windows to treat all characters including spaces before the end of the line as a single argument For example if you enter the following arguments C Program Files someDirectory C anotherDirectory They are interpreted by the Windows command interpreter as C Program Files someDirectory C anotherDirectory Rev 9 8 06 Web Based Enterprise Services Release Notes 2 9 System Event Analyzer 2 3 SEA Known Issues The second double quote is considered part of the literal line of characters and the third double quote is added by Windows Thus the two arguments are passed to the program as a single argument with a embedded double quote character C Program Files someDirectory C anotherDirectory There are two ways to avoid this problem Do not place a trailing backslash character following a double quoted directory name Place two consecutive backslash characters at the end of the double quoted directory name For example you could replace the following path C Program Files someDirectory C anotherDirectory With either of th
6. causes WEBES to log a great deal of information into the logs the log files could in the worst case fill up the system s disk space Also if you have changed the logging level to produce more debug output see SEA User s Guide section 2 5 Log Files the log file sizes can grow significantly even under normal operation On OpenVMS and Windows a new copy of the Director log file is created each time the Director is started A copy of the previous Director log file is retained while older logs if any are deleted On the UNIX variants the log files are appended with each Director start and are never deleted A future WEBES version will monitor and limit the sizes of these log files Rev 9 8 06 1 10 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issues Workaround If you run out of disk space check the WEBES output log files If the logging level has not been increased from WARNING to INFO or DEBUG follow these steps 1 Stop the Director and WCCProxy see SEA User s Guide section 2 3 Processes 2 Ifthe reason for the problem is not evident from the log files and you cannot resolve it zip and send all the files in the specific webes logs and specific wccproxy logs directories to WEBES support 3 Delete all the files in these directories 4 Restart the Director and WCCProxy If the log files continue to grow quickly with errors then stop the Director and WCCProxy u
7. 0 0 0 0000 2 26 2 3 7 3 WEBES Commands Return Error Activating Image 00000 2 27 2 3 7 4 Slow Response Generating Other Logs List 2 2 t erus tiri Piki 2 27 2 3 7 5 Exclude Node Names trom Filespecs ss s soiiaac ar pk e pr erersrerepees qs 2 28 2 3 7 6 CA Agent Processes Created But Not Disappearing 0 0004 2 28 2A Further Intormanon lt E CP EUER 2 28 3 Computer Crash Analysis Tool 3 1 3 1 Sumit afys shore ee parie dob e Vg he ea Rr ev qus HOA e EE v pee qub P Tia REP 3 2 3 Supported Products dios ma Dp T Io Fn xDD CDU IR op ua RR uS TO GOpala ina unde YDa QAI op R P ENE 3 2 3 3 CCAT Known ISSUES 5 xveci me eR RRRPRYUGG RUE Re Op E Eq Ee PpEXG qe ERU IER ERR 3 2 3 5 General ECCA TISSUES 2 ooa eicana s bibo deba dU Wig are dried oipuii Bob anti ede Gre gene 3 2 3 3 1 1 CCAT IVP File Not Found 1 2 rr me beer em eme eme eR edes 3 3 3 9 2 Windows CCAT ASSUGS masterne eo pd A T E ne A POR ipo udin 3 3 3 3 2 1 WEBES Directory Tree Missing Or Access Denied 000000005 3 3 3 35 22 CLI Commands Not Recognized ss oa wot Co ek nk gerbe s We bik 3 3 3 3 2 3 Empty Start Ment erroe er tti tle doer E ah eased ree redo dead papas 3 3 3 3 3 Open V MS CC AT 88868 aote hoo UE Ecce Por equae up Riad dain Meee dede gans cori 3 4 3 3 3 1 Insufficient Privilege or File Protection Violation 0 000000 00 3 4 3 3 3 2 Inability To Execute CLI Commands 2 irme Cobb op
8. 3 Operating System Requirements This version of WEBES can be installed on the following operating systems Microsoft Windows Windows 2000 Windows Server 2003 Web Edition Standard Edition and Enterprise Edition for 32 bit Enterprise Edition for 64 bit Itanium based Systems Windows XP Professional 32 bit Edition HP OpenVMS Alpha versions 7 3 1 or higher Note WEBES v4 4 3 will install and function on OpenVMS Alpha v7 3 1 and above The next version of WEBES will only install and function on v7 3 2 and above You can install and run WEBES on HP UX and Linux but currently it does not analyze native error logs for events occurring on those platforms You can however copy an error log from another system Windows or OpenVMS to an HP UX or Linux system for manual analysis there HP UX PA RISC version 11 00 11 11 or higher HP UX Integrity Server 11 23 or higher Red Hat Enterprise Linux Application Server 3 0 and 4 0 Red Hat Enterprise Linux Enterprise Server 3 0 and 4 0 This version of WEBES is NOT supported on the following versions of Windows e Windows ME 98 95 3 1 or earlier Windows NT Windows 2000 Datacenter Server Windows 2003 Datacenter Small Business Server or Storage Server Editions Windows XP Home Media Center or Tablet PC Editions Rev 9 8 06 Web Based Enterprise Services Release Notes 1 3 Overall WEBES Release Notes 1 4 Test Environment Windows XP Professional 64 bit I
9. Administrative Tools Services Start the Windows Management Instrumentation WMI service if it s running Or b Issue the command net start winmgmt from a Command Prompt window 1 6 2 4 WEBES Configuration is Not Migrated for Windows Itanium Note The following affects Windows Itanium only The WEBES kits for Windows Pentium migrate configuration data correctly When upgrading WEBES from an earlier version to v4 5 some WEBES configuration data may not be migrated to v4 5 correctly Likewise you may choose to save configuration data during the uninstall process of any earlier version of WEBES However in such a case while installing WEBES v4 5 some configuration data from the previous installation of WEBES may not be migrated to the new v4 5 installation correctly Workaround After completing the upgrade or installation of WEBES v4 5 review all the configuration data in the following files and update them as required to restore the previous values e DESTA REG e NotifyCA txt e CCATNotify txt profile txt They are all located in installed directory specific desta config directory In addition Managed entity EVA related configuration information is not migrated Re enter their data after WEBES has been upgraded or installed using either the CLI or Web interface Rev 9 8 06 Web Based Enterprise Services Release Notes 1 17 Overall WEBES Release Notes 1 6 WEBES Known Issu
10. CPU 899 MHz RAM 2 GB HP UX B 11 11 Not patched 1 4 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 5 New in this Release HP PA RISC 9000 889 MHz CPU 899 MHz RAM 2 GB HP UX 11 00 Not patched RedHat Linux not Patched Intel Pentium IV CPU 2 79 GHz RAM 512 MB RHEL AS 4 0 Intel Pentium IV CPU 2 79 GHz RAM 512 MB RHEL ES 4 0 Intel Pentium IV CPU 2 79 GHz RAM 512 MB RH ES AS 3 0 Intel Pentium IV CPU 2 79 GHz RAM 512 MB RH 7 3 Intel Pentium HI CPU 733 MHz RAM 128 MB RH 8 0 OpenVMS AlphaServer 1200 AlphaServer 2100 AlphaServer 4x00 OpenVMS 7 3 1 HP AlphaServer GS1280 HP AlphaServer GS160 Compaq AlphaServer ES40 OpenVMS 7 3 2 AlphaServer DS20 OpenVMS 8 2 HP rx2600 OpenVMS Integrity Itanium 8 2 1 HP AlphaServer ES47 OpenVMS 8 2 Mixed Cluster These release notes list tested systems for informational and troubleshooting purposes only However you always can obtain support from Hewlett Packard for any supported platform see Sections 1 2 and 1 3 regardless of the individual configurations listed as the test environment 1 5 New in this Release Storage Systems Support for EVA Command View 6 0 Added a note in the full description field when an ELC Event Log Collection is sent with the report Increased the number of ELC attachments by sending an ELC during any proactive disk drive failure and certain other disk failure reports Rev 9 8 06 Web
11. Stopping DESTA system on this machine md gc init could not allocate heap of size file USER2S JFEX JFEX VM SRC SYS ALPHA GCINIT C 1 line 130 Director still running waiting 30 seconds Director did not stop process killed 1 6 4 3 Cannot Get Local Host Name If you are using the MultiNet TCP IP product from Process Software and the Director does not start check the Director log file SVCTOOLS_HOME COMMON WEBES LOGS DESTA_DIR LOG for errors similar to the following WARNING on October 4 2002 10 42 27 AM EDT 0 726 sec elapsed Can t get the Local host name Current Thread Thread 2 com hp svctools desta core CommonDirector 5 ma EXCEPTION java net UnknownHostException myhost mycorp com at java net InetAddress getAllByNameO0 java lang String boolean InetAddress java 571 pc 51 These errors can appear when the MultiNet UCX driver has been disabled Although the driver is enabled by default it can be disabled using configuration options Verify that the UCX driver has not been disabled since it must be enabled in order to run WEBES If the driver has been disabled you can re enable it using the following steps Rev 9 8 06 Web Based Enterprise Services Release Notes 1 23 Note This information also appears in the MultiNet v4 4 Installation and Administrator Guide For more details on configuring MultiNet see the MultiNet documentation 1 Start the configuration program
12. WCCProxy and select Properties d Disable the service 3 Delete the following folders if still present and all of its contents if any C Program Files MhpNsvctools C Program FilesMHewlett PackardNsvctools 4 Reboot the Windows XP system 5 Uninstall the existing WCCProxy program via Control Panel Add or Remove Programs if it is still shown in the list 6 Install the latest WEBES installation kit 1 6 2 8 Installation Internal Error Before installing first copy the WEBES kit to a local drive The installation results in an error when mapping a drive letter to another system where the kit resides for example Internal Error 2755 3 F path toNWEBESVA31BL322KIT2 Jan 28 2004 Windows MSI 1 6 2 9 Uninstall of Previous WEBES May Hang While uninstalling the previous version of WEBES the uninstall process may hang or stop processing without using any CPU time If the Task Manager shows a java exe process running and no other Java based applications are running on your system and nothing else is Rev 9 8 06 Web Based Enterprise Services Release Notes 1 19 Overall WEBES Release Notes 1 6 WEBES Known Issues using CPU time click on the java exe process and then click End Process Killing this process may enable the rest of the uninstallation to continue 1 6 2 10 desta msg chgport Command The CLI command desta msg chgport hangs the Director process Workaround Enter Ctrl C to restore the com
13. attributes set file attr rfm stmlf rat cr filename SEA does not generate an error message when you process a file that was transferred in ASCII mode or was transferred in binary mode but left with incorrect attributes but it may skip some events show corruption in translated events and produce unreliable analysis results 2 3 1 7 Duplicate Callouts with both DECevent and WEBES Installed Note This issue is most likely to occur when newer Alpha platforms with WEBES such as the GS160 are connected to clusters containing older Alpha platforms with DECevent such as the GS60 Turbolaser However the issue is not necessarily limited to those scenarios Rev 9 8 06 2 6 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues Running DECevent and WEBES on the same machine results in duplicate callouts to the CSC when event notification occurs To resolve this problem you can choose to only start one of the applications at boot time OpenVMS To prevent DECevent from starting on an OpenVMS platform use the following procedure Edit the startup script sys startup decevent startup com 2 Insert the following code at the beginning of the file Note Verify the existence and format of the syssNopz logical before performing this operation node FSTRNLNM SYSSNODE IF node EQS nodenamel THEN EXIT 1 Replace nodename1 with the name of the node that shoul
14. desta sicl on Note DSNlink has been retired and is no longer supported by Hewlett Packard Use ISEE desta isee on off instead for service provider notification Who should receive responses for logged calls john smith mycompany com java io FileNotFoundException No such file or directory Workaround 1 Execute the desta command again The problem is intermittent If that does not succeed 2 2 Editthe svctools specific desta config DESTA REG file with any text editor 3 Look for a line beginning notification Type 4 Addeither ACHS for SICL DSNLink notification unsupported by HP and or QSAP to the line separated by spaces so that the line looks similar to this example Rev 9 8 06 1 14 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issues notification Type SMTP LOG ISEE ACHS QSAP 5 Look for the following lines and replace them with the appropriate information or add the lines if they do not exist case sensitive If enabling QSAP OSEM CSG PRS desta QSAP mymachine company com the machine running OSEM or PRS desta QSAPport 2069 the port number OSEM PRS is listening on 209 by default If enabling ACHS SICL DSNLink CA ACHSProfile usr opt hp svctools specific desta config profile txt change this to the location appropriate for your operating system ccat ACHSProfile usr opt hp svctools specific desta confi
15. enable verbose information for SMTP notification you will need to stop and restart both the SMTP service and the DESTA Director Following are the steps to enable SMTP debug information 1 Run the following commands define sys tcpip smtp log level 5 define sys tcpip smtp recv debug 5 define sys tcpip smtp recv trace 1 desta msg log debug desta stop Qsys startup tcpip smtp shutdown Qsys startup tcpip smtp startup 2 Ensure that the following fields are set up as required in the file Xr uxuruxurur SVCTOOLS HOME SPECIFIC DESTA CONFIG NOTIFYCA TXT SERVER SMTP server name or an MX Lookup entry FROM lt sea dns domain com gt TO lt your mail id gt An MX LOOKUP entry is a pointer to a list of SMTP mail servers Refer to the OpenVMS documentation for details on MX LOOKUP 3 Restart the Director desta start 4 Wait for 5 minutes for the Director to switch to automatic analysis mode Before this time no new live events will be processed 5 Issue the following command which writes a test event to the system ERRLOGSYS file for SEA to process It generates one problem report resulting in one email notification via SMTP wsea test 6 Check the Director log file for SMTP entries with TYPE or EDIT READ or SEARCH The entire process may take about 10 15 minutes until the customer receives an email notification This is because SMTP is a store and forward mechanism and has no time const
16. microsoft com default aspx scid kb en us 183097 SEA reads the Application log file SSystemRoot system32 config AppEvent evt 2 3 4 5 XP Internet Explorer Does Not Have Java On Windows XP and Windows 2003 Microsoft no longer supplies a Java VM for Internet Explorer You must download and install a Sun JRE instead target _blank gt http java sun com get java 2 3 4 6 Incomplete Uninstall of Older Version If you encounter problems with general WEBES operation on Windows which is not solved by an existing Release Note particularly in the area of the Director starting stopping hanging or crashing and you had a version of WEBES prior to V4 1 installed perform these steps to clear a possible problem in previous WEBES uninstallation 1 Uninstall the current version of WEBES 2 Restart the machine 3 Reinstall WEBES The current WEBES uninstall is more comprehensive and clears everything from previous WEBES versions as well as the current version but a restart is required so that the operating system can release file service and registry references WEBES is completely removed after the system is restarted Rev 9 8 06 2 20 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues 2 3 4 7 Test Command Generates Error 1502 If you run the wsea test command when the Windows Application error log is full the following error occurs Windows Error 1502 Command failed Could not w
17. of ERRLOG SYS The total retry time is 342 seconds or about 5 7 minutes Workaround If the above error is seen in the Director log or in the CLI output copy SYS ERRORLOG ERRLOGSYS 1 or whichever file version is desired to another file and manually analyze that file 2 3 7 2 Insufficient Privilege or File Protection Violation If you are not a member of the SYSTEM group your user ID does not have all privileges or you have not issued the SET PROCESS PRIV ALL command you cannot access or see any directories or files under the WEBES directory tree pointed to by the SVCTOOLS HOME logical SYS COMMON HP by default If this is the case you see errors similar to the following examples dir svctools home 000000 SDIRECT E OPENIN error opening SVCTOOLS COMMON 000000 as input Rev 9 8 06 2 26 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues RMS E PRV insufficient privilege or file protection violation dir svctools home common bin SDIRECT E OPENIN error opening SVCTOOLS COMMON COMMON BIN as input RMS E PRV insufficient privilege or file protection violation dir sys common hp Directory SYSSCOMMON HP SDIRECT E OPENIN error opening SYSSCOMMON HP NODES as input RMS E PRV insufficient privilege or file protection violation SDIRECT E OPENIN error opening SYSSCOMMON HP SVCTOOLS as input RMS E PRV
18. s secereseirewereeRerI Aw REPE 2 20 2 3 4 6 Incomplete Uninstall of Older Version 0 0 0 0 eee eee eee eee 2 20 2 347 Test Command Generates Error L302 r rerrines tr rost E PER EIEE E Wai SOMOS ER 2 21 2 3 4 8 WEBES Directory Tree Missing or Access Denied 0 0005 2 21 2 34 9 WEBES Commands Not Recognized 52 22 EREEeFaRgcgoek qu oer aergedue exa 2 21 2 3 4 10 Hewlett Packard Service Tools Entry on Start Menu is Empty 2 21 2 514 NAPP Error Description 5 623 oh FERHeRESEERPERERIGUEAa DES ae 2 22 2 3 4 12 Newly Added EVA Not Listed in SEA Web Interface 0 0 2 22 2 3 4 13 Resuming from Standby Loses Network Resources in XP SP2 2 23 2 9 2 HPUX SEA ISSUES caca erbe PERSTO RET Ede vade N ede Aum aree dea us 2 23 2 3 5 NING Binary Event WOR neer ide ER Ine EENE NORIS SORS ERR oS Puit S MEI qn Rug 2 23 2 3 6 LEMUR SEA SSUES o px es i r er ees Paesi P avb ep dh S ed esti ice a EC edic 2 24 2 3 6 1 C C Runtime Libraries Version 6 1 1 or Later Required 0 2 24 2 3 0 2 No Binary Event L08 ret ewe E IRAE EC E RE ERR DER IPS 2 24 2 3 6 3 Adding Managed Entities Corrupts Director llle 2 24 2 3 7 Open V MS SEX SSU amp S aps piper ad qum pare EROR aped Boat PS aoa Race Rois 2 25 2 3 7 1 ERRFMT May Create New Version of ERRLOG SYS During WEBES Processing 2 25 2 3 7 2 Insufficient Privilege or File Protection Violation
19. the SEA Web interface and that remote node is running a different version of WEBES than the node to which your browser is connected Running a local copy of WEBES for analysis only on that local system does not present a problem Likewise connecting directly to a remote system via the SEA Web Interface URL for example without having WEBES installed on your local system is not a problem To avoid a compatibility issue make sure that the exact same version of WEBES is installed on all systems that connect to one another as within a given site or enterprise In any clustered environment it is especially important to have the same version installed on every node Backward compatibility will be introduced in a future WEBES release 2 3 1 3 Serial Number Prevents Rules from Working The system serial number on certain GS80 GS160 and GS320 systems was not set correctly at the factory and SEA rules only function if the serial number is set correctly See the pre installation procedures for OpenVMS in the WEBES Installation Guide for details 2 3 1 4 Fields Contain Unavailable This note applies to DS10 DS10L DS20 DS20E ES40 and TS202c products When a valid configuration tree event is accessible information appears in the Part Number Serial Number and FW Rev Level fields If a valid configuration tree event could not be accessed these fields are reported as Unavailable 2 3 1 5 File Not Found Error In DESTA Log File The
20. 6 2 3 Installation Prompts When File Fails to Delete llle eese 1 16 1 6 2 4 WEBES Configuration is Not Migrated for Windows Itanium 1 17 1 6 2 5 CCAT Not Available on Windows Itanium sees eee eese 1 18 1 6 2 6 Directories and Registry Keys Left Behind by WEBES Itanium Removal 1 18 Rev 9 8 06 Web Based Enterprise Services Release Notes v Contents 1 6 2 7 WCCProxy Incompatibility Issue on Windows XP WOW Configuration Machines 1 19 1 6 2 8 Installation Internal Error iix 5 25 Gane PREX nes weet Re eS PR ERR ES 1 19 1 6 2 9 Uninstall of Previous WEBES May Hang 0 ee ee eee ee eee 1 19 16 2510 desta mse chpport Commands resiste areia e wien see amo eS RARE eed 1 20 1 6 2 11 PATH Update Required on Terminal Server Installation 1 20 1 6 2 12 Windows Itanium WEBES Removal Leaves Files Behind 1 20 1 6 2 13 Installation may not set the PATH variable if PATH is not defined before installing WEBS secs gh tarde ad cR egt epe oet canton em pem tane Te RAL See ERREUR So RR eG 1 20 1 6 2 14 Windows Itanium Installation may interrupt if PATH variable is 256 characters or longer 1 21 16 3 eins WEBESISSUGS x s mses cong trdiaerteethageerhea trian ao bbe ess ES 4a 1 21 1 6 3 1 Director May Require Restarts 22e kart trm ak eee EEEE ERRE is 1 21 1 6 3 2 Segmentation Fault Error Message esse e eR ee m re 1 21 1 64 OpenVMS WEBES
21. 9 8 06 3 6 Web Based Enterprise Services Release Notes
22. Agents root 30091 28666 0 15 17 pts 3 kill 9 29823 2 Remove the xml file representing the added managed entity s 500 g 00 00 00 grep svctools Rev 9 8 06 2 24 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues rm rf usr opt hp svctools specific desta data managedentities xml 3 Remove the DESTA stat file rm rf usr opt hp svctools specific desta data DESTA stat 4 4 Restart the WEBES Director process usr sbin desta start 2 3 7 OpenVMS SEA Issues These issues apply to SEA on OpenVMS 2 3 7 1 ERRFMT May Create New Version of ERRLOG SYS During WEBES Processing When the WEBES Director has the ERRLOGSYS file open to do its processing even though WEBES opens the file read only VMS considers the file locked The lock prevents the VMS ERRFMT from writing a new event to the file Normally this is not a problem because ERRFMT will retry the write repeatedly for up to about 6 minutes Usually the Director only has ERRLOGSYS open for a short time to read the last event just written or the last few events written since the Director was stopped If however the ERRLOGSYS file is large and the Director has the ERRLOGSYS file open long enough for all of the ERRFMT retries to fail more than 6 minutes after the time ERRFMT initially tries to write a new event then ERRFMT will create a new file version of ERRLOG SYS The cases that can cause
23. Based Enterprise Services Release Notes 1 5 Overall WEBES Release Notes 1 5 New in this Release Enhanced CSR Customer Self Repair procedure information and added SML links Added a note in the FRU field to indicate if part needs to be RoHs Reduction of Hazardous Substances Enhanced disk drive check condition rules Based on analysis of field data the error threshold levels for numerous ASC ASCQ values have been adjusted to predict drive failures more effectively Updated analysis rules for supported server and storage products SSL encryption security for communications between WEBES and Command View EVA e Support for HP EVA XL and HP EVA XL Lite Disk Arrays Integrity Servers WEBES 4 5 is the first WEBES release to be supported on HP UX Integrity Servers Analysis support of WBEM indications for Integrity servers running HP UX v11 23 with Hardware Enablement HWE patches version 0603 later Support for the following new HP Integrity Servers that use the new Intel Itanium 2 processors 1 6 GHz with 6 MB L2 cache HP Integrity Servers rx7620 rx8620 SD16 SD32 and SD64 with Windows Server 2003 Enterprise Edition and OpenVMS v8 2 and later HP Integrity Servers rx7640 rx8640 SD16B SD32B and SD64B with Windows Server 2003 Enterprise Edition and OpenVMS v8 3 and later HP Integrity Servers rx3600 and rx6600 with Windows Server 2003 Enterprise Edition and OpenVMS v8 3 and later Miscellaneous
24. E Client installation to succeed Windows 2003 does not have MS JVM by default SNMP services must be installed and enabled for monitoring VLS nodes Fully integrated with the WEBES and ISEE solution Promotes improved up time for customers entitled by warranty or an appropriate support contract ID by facilitating lower failure to repair time and higher first time fix rates Automated event monitoring using custom rules Detection of actionable Field Replaceable Unit FRU failures with reporting to customers and to the HP backend Automatic entitlement of VLS nodes subject to new product labeling SEA will collect the data from the VLS to be sent to HP customer support via ISEE to allow for better problem diagnosis by HP Problem reports sent to HP will also contain a URL link to data within the internal HP environment This link provides HP support with event history on the VLS device and will not be accessible outside of HP WEBES users will not notice any change in problem reports notified either to the Web interface SMTP email OSEM or any other routes besides ISEE because of this new feature Rev 9 8 06 Web Based Enterprise Services Release Notes 1 7 Overall WEBES Release Notes 1 6 WEBES Known Issues WBEM Server Web Based Enterprise Management is a standard method of communicating management data and operations WBEM provides an integration point through which management and event sources are accessed By providing a u
25. EA does not send notifications because it does not process live events wsea test The only exception is that wsea test will write its test event to var adm binary errlog creating the file when it does not exist This is possible because SEA creates a log even though Linux normally does not have one For now the log is only for SEA test events SEA processes the tests and sends notifications for them as expected In the future expanded problem report creation for additional events may be added to the Linux version of SEA 2 3 6 3 Adding Managed Entities Corrupts Director If a new managed entity is added using either the desta entity add command or using the SEA web interface then the Director will no longer function To correct the situation 1 Kill the DESTAProcessWrapper process name this is the Director process In this situation the Director probably cannot be stopped normally with the desta stop command ps ef grep svctools root 29141 0 14 53 pts 3 00 00 00 usr opt hp svctools common wccproxy share WCCProxy root 29408 28521 0 14 54 pts 0 00 00 00 tail f usr opt hp svctools specific webes logs desta dir log root 29823 1 1 15 09 pts 3 00 00 08 usr opt hp svctools common jre bin i386 native threads java noverify DSvctools Home usr opt hp svctools DSwcc Home var adm Xmx300m com compaq svctools desta util DESTAProcessWrapper root 30027 L 0 15 13 pts 3 00 00 00 usr opt hp svctools common wccproxy share CA
26. G60 HSG80 HSZXX OpenVMS HSG60 HSG80 Windows KGPSA CA KGPSA BC KGPSA B Y KGPSA CB KGPSA CX KGPSA CY FCA2384 FCA2354 FCA2404 FCA2406 Smart Array 5304 Controller OpenVMS Modular SAN Array 1000 OpenVMS EMA 16000 MA8000 EMA 12000 MA6000 RA8000 ESA12000 e I O Devices Bit To Text Translation only RA3000 KZPSC KZPAC KZPBA KZPCM KZPS A KZPCC KSPEA KGPSA CA KGPSA BC KGPSA B Y KGPSA CB KGPSA CX KGPSA CY FCA2384 FCA2354 FCA2404 FCA 2406 OpenVMS CCMAB AA CIPCA BA Storage Systems Analysis and Bit To Text Translation Supports HP Storage Works EVA4000 EVA6000 and EVA8000 products with XCS v6 000 and older Supports HP Storage Works EVA3000 and EVA5000 products with VCS v4 005 and or v3 028 and older Storage System Components Analysis and Bit To Text Translation Rev 9 8 06 Web Based Enterprise Services Release Notes 2 3 System Event Analyzer 2 3 SEA Known Issues StorageWorks SAN 1 Gbps Switches DSGGA AA 8 port StorageWorks Fibre Channel switch DSGGA AB 16 port StorageWorks Fibre Channel switch DSGGB AA 8 port StorageWorks SAN switch 8 DSGGB AB 16 port StorageWorks SAN switch 16 DSGGC AA 8 port SAN Switch 8 EL DSGGC AB 16 port SAN Switch 16 EL DSGGS SAN Switch Integrated 32 and 64 ports e StorageWorks SAN 2 Gbps Switches DS DSGGD AA 16 port SAN Switch 2 16 DS DSGGD AB 32 port SAN Switch 2 32 DS DSGGD AC 8 port SAN Switch 2 8 EL DS DSSGD AD 16 port SAN Switch 2 16 EL DS DSGGD BB 32 port
27. Packard Service Tools However you may still see choices for other installed Hewlett Packard service tools that are Rev 9 8 06 Web Based Enterprise Services Release Notes 2 21 System Event Analyzer 2 3 SEA Known Issues not part of WEBES such as Service Cockpit or SmartScope See the System Event Analyzer User Guide for information on the permissions required to use WEBES tools 2 3 4 11 NAPP Error Description NAPP uses the parse file to decode the binary data of the EVA controller event log The parse file name identifies the specific version and builds for VCS The check for this is made by comparing the VCS version and a build number in the event packets to a set of parse files provided in C Program Files Hewlett Packard svctools common napp NAPP returns an error if the controller log contains events written by VCS with version or builds other than the versions provided in this version of NAPP Error generating storage spreadsheet from storage cell Frankenprise on node sesanman7 Please make sure Frankenprise is a valid storage cell alias and that sesanman is one of the storage platforms supported by System Event Analyzer The version of NAPP 2 63 included with the current release of WEBES includes officially released parse files up to and including version 3 020 of VCS These parse files are located in the above directory within the WEBES directory structure When installing new releases of VCS copy the new parse fil
28. SAN Switch 2 32 DS DSGGD DB 32 port SAN Switch 2 32 DS DSGGE xx 64 port Core Switch 2 64 2 3 SEA Known Issues The System Event Analyzer User Guide includes appendices that address performance and browser usage If you think SEA is performing less than optimally or if you are using the web interface you should familiarize yourself with the appendices The issues described in the following sections are specific to SEA 2 3 1 General SEA Issues 2 3 2 SEA Command Line Interface Issues 2 3 3 SEA Web Interface Issues 2 3 4 Windows SEA Issues 2 3 5 HP UX SEA Issues 2 3 6 Linux SEA Issues 2 3 7 OpenVMS SEA Issues See Section 1 6 WEBES Known Issues for overall suite issues 2 3 1 General SEA Issues These issues apply to SEA on all operating systems Rev 9 8 06 2 4 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues 2 3 1 1 System Error Log Initialization while Director is Running Causes Errors If the system error log is re initialized while the Director is running events may be missed or processed incorrectly To avoid this problem either reinitialize the system error log before the Director is started or stop the Director before modifying the system error log 2 3 1 2 Backward Compatibility Connections between systems that are running different versions of WEBES may produce unpredictable results This can happen if for example you add a remote node to your list of nodes in
29. SDCL E OPENIN error opening _NUTESDKAO sys0 syscommon hp svctools common bin desta com as input SDCL E OPENIN error opening _NUTESDKAO sys0 syscommon hp svctools common bin wsea com as input SDCL E OPENIN error opening _NUTESDKAO sys0 syscommon hp svctools common wccproxy bin wccproxy co m as input RMS E DNF directory not found SYSTEM W NOSUCHFILE no such file WEBES CLI commands on OpenVMS have not yet been developed to be case sensitive for ODS 5 support Rev 9 8 06 1 22 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issues 1 6 4 2 JFEX Errors The following JFEX errors occur when the correct quota minimums are not set On a cluster the correct minimums must be set for all nodes in the cluster Be sure to apply prerequisite minimums to all applicable nodes when installing WEBES See the WEBES Installation Guide for details Example errors desta status The Director is running wsea tra md gc init could not allocate heap of size file USER2S JFEX JFEX VM SRC SYS ALPHA GCINIT C 1 line 130 wsea ana md gc init could not allocate heap of size file USER2S JFEX JFEX VM SRC SYS ALPHA GCINIT C 1 line 130 wsea md gc init could not allocate heap of size file USER2S JFEX JFEX VM SRC SYS ALPHA GCINIT C 1 line 130 desta stop
30. STEM CurrentControlSet Services Eventlog Applicatio n CA TEST HKEY_LOCAL_MACHINE SOFTWARE Hewlett Packard SVCTOOLS There should not be any entries or subkeys in these keys after WEBES is removed None of the directories or keys will affect future installations of WEBES or any other products if left in place Rev 9 8 06 1 18 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issues 1 6 2 7 WCCProxy Incompatibility Issue on Windows XP WOW Configuration Machines On Windows XP systems that have the Netherlands WOW image installed WEBES is not installed correctly and will not operate properly This information is valid for the WOW v8 image that contained WEBES v4 4 1 No later WOW image has been tested by the WEBES team Workaround As a workaround to this problem perform the following steps to return WEBES to a working state This procedure has been tested by the WEBES team by remotely operating a WOW v8 machine 1 Uninstall the existing HP WEBES via Control Panel Add or Remove Programs This will remove WEBES The uninstall script will likely leave WCCProxy installed and running rather than removing it as it should due to the improperly installed WEBES in the WOW image 2 Stop and then disable the WCCProxy service as follows a Go to Control Panel Administrative Tools Services b Select WCCProxy and click on Stop c Right click on
31. This can happen if for example you are running your locally installed SEA and then use it to add and analyze a remote node that has another version installed Rev 9 8 06 Web Based Enterprise Services Release Notes 1 11 Overall WEBES Release Notes 1 6 WEBES Known Issues Running a local copy of WEBES for analysis only on that local system does not present a problem Likewise connecting directly to a remote system via the CLI or web URL for example without having WEBES installed on your local system is okay To avoid a compatibility issue make sure that the exact same version of WEBES is installed on all systems that will connect to one another as within a given site or enterprise In any clustered environment it is especially important to have the same version including dot release or Service Pak installed on every node Backward compatibility will be introduced in a future WEBES release 1 6 1 9 Director Process Not Responding If one of the WEBES components is not responding or giving an error it may be that the Director process is not responding To correct this problem see the Director chapter in the WEBES User Guide It includes a section on troubleshooting an unresponsive Director process 1 6 1 10 Director Process Stopping When Out of Memory If the Director hangs or terminates unexpectedly check the Director log files see the WEBES User Guide for more information on log files If the log files contain errors mentioni
32. Web Based Enterprise Services Release Notes This document provides an overview and describes known issues for this release of HP Web Based Enterprise Services WEBES on Windows 2000 Windows 2003 and Windows XP HP UX Linux and HP OpenVMS systems To access the latest revision of this document containing updated information please visit the WEBES Web site http www hp com services webes Rev 9 8 06 WEBES 4 5 is not supported on OpenVMS Alpha systems and OpenVMS Integrity Servers Operating Systems Microsoft Windows 2000 Windows Server 2003 and Windows XP HP UX PA RISC version 11 00 11 11 or higher HP UX Integrity Server 11 23 or higher Red Hat Enterprise Linux Application Server 3 0 and 4 0 Red Hat Enterprise Linux Enterprise Server 3 0 and 4 0 Software Version WEBES Version 4 5 h Hewlett Packard Company if Technical Publications 305 Rockrimmon Boulevard South invent Colorado Springs Colorado 80919 U S A Rev 9 8 06 September 2006 2006 Hewlett Packard Company Microsoft Windows and Windows NT are US registered trademarks of Microsoft Corporation Intel is a US registered trademark of Intel Corporation UNIX is a registered trademark of The Open Group Java is a US trademark of Sun Microsystems Inc Confidential computer software Valid license from Hewlett Packard required for possession use or copying Consistent with FAR 12 211 and 12 212 Commercial Computer Software Computer Software Docu
33. ally occurs if CCAT is not installed Now run the following commands for specific platforms OpenVMS desta exec com compaq svctools desta configuration ChangeEnrollments unenroll ConfigDefaultsCAOpenVMS txt HP UX desta exec com compaq svctools desta configuration ChangeEnrollments unenroll ConfigDefaultsCADUnix txt Windows desta exec com compaq svctools desta configuration ChangeEnrollments unenroll ConfigDefaultsCAWindows txt Linux desta exec com compaq svctools desta configuration ChangeEnrollments unenroll ConfigDefaultsCALinux txt Ignore the error messages that result from this command This typically occurs if SEA is not installed Then run the following commands for all platforms desta start desta status Repeat the command until The Director is running is displayed If it is not displayed after 10 minutes contact HP Services for WEBES support Rev 9 8 06 2 16 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues desta msg chgconf global 6 300000 i im desta stop desta exec com compaq svctools desta configuration ChangeEnrollments enroll ConfigDefaultsCCAT txt Ignore the error messages that result from this command This typically occurs if CCAT is not installed Change the unenroll parameter to enroll and re issue the desta exec command for SEA CA services Ignore the error messages that result from this command This t
34. as input RMS E PRV insufficient privilege or file protection violation SDIRECT E OPENIN error opening SYSSCOMMON HP SVCTOOLS as input RMS E PRV insufficient privilege or file protection violation NODES DIR 1 SVCTOOLS DIR 1 Total of 2 files 3 3 3 2 Inability To Execute CLI Commands If your user ID does not have the privileges specified in the WEBES Installation Guide you will not be able to execute any WEBES CCAT CLI commands You will see errors such as the following desta status SDCL W ACTIMAGE error activating image SVCTOOLS HOME COMMON BIN DESTA CMD EXE CLI E IMGNAME image file NUTESDKAO SYSO SYSCOMMON HP SVCTOOLS COMMON BIN DESTA_CMD EXE RMS E PRV insufficient privilege or file protection violation svctools_home common bin ccat gui SDCL E OPENIN error opening SVCTOOLS SPECIFIC COMMON BIN CCAT COM as input RMS E PRV insufficient privilege or file protection violation Rev 9 8 06 3 4 Web Based Enterprise Services Release Notes Computer Crash Analysis Tool 3 4 Further Information 3 4 Further Information See the Computer Crash Analysis Tool User Guide for more details about CCAT Kits updates and documentation for WEBES are available at the following URL http www hp com services webes Rev 9 8 06 Web Based Enterprise Services Release Notes 3 5 Computer Crash Analysis Tool 3 4 Further Information Rev
35. ase Notes System Event Analyzer 2 3 SEA Known Issues 2 3 3 12 Services Fail to Start When the system is heavily loaded or on very slow machines such as the AlphaServer 1000 the Director may have problems starting its services If any service fails to start the Director automatically shuts down and records an error in the Director log under svctools home specific webes 10ogs similar to the following FATAL ERROR on July 22 2003 12 39 27 PM MDT 144 002 sec elapsed The following services failed to start com compaq svctools ca services analysis EvtAnalyzer Current Thread main 5 main or the following the service name may vary and is not usually important FATAL ERROR on February 14 2005 10 11 42 AM GMT 08 00 85 879 sec elapsed The following services failed to start com compaq svctools ca services web SEAWebServic To allow the services enough time to start up increase the ctrlrStartupTimeout value in the Director Settings However it may be noted that the Director must be running in order to change this time out value which has been identified as a potential problem Follow these steps to update the Director Settings Tip When updating the Director Settings be sure to start the Director when the system is not under heavy load 1 Open SEA in a browser window and click the SEA Settings button 2 Select the Director Settings tab at the bottom of the window The WEBES Services listbox automatica
36. authorized service provider s consent Upon termination of the services customer will at Hewlett Packard s or its service provider s option destroy or return the software and associated documentation in its possession Examples used throughout this document are fictitious Any resemblance to actual companies persons or events is purely coincidental ii Web Based Enterprise Services Release Notes Change Summary The following table summarizes the changes to this document Revision Description 25 08 06 A Initial 4 5 copy Rev 9 8 06 Web Based Enterprise Services Release Notes iii Contents Title Page i Copyright Statement ii Change Summary iii 1 Overall WEBES Release Notes 1 1 EI Samma ER ET 1 2 1 2 Hatdware Requirements ee caes mer emer RERBRRIEY RUE ROI RUE EEE Ree eee ET Reo 1 2 1 3 Operating System Requirements 5 5 ok deese sok anisole Esel Rede rou Em cpu leds 1 3 1 4 Test Environment cocos cw erre duke ether RS Sb he gos ed ede ord ew red ele voe ow er dps 1 4 TS Newanthis Release cuota Ie qae oon nego Raub CORSO Ris db n E phe ce R pin Roni tu d cere 1 5 1 6 WEBES Known Issues c 0060 00 ge eee mde eme xa yere wee E Rene ere eq 1 8 16 1 Genera WEBES SSUES eu cops seirab eunte RR ROC RR bore Ed adn Sebi kee AG 1 8 1 6 1 1 Installing WEBES on Unsupported Platforms 0 0 0 0 e eee eee eee 1 8 1 6 1 2 Error During Reading of Obligation Information 000000000005 1 9
37. ay see JavaScript errors You can safely ignore these errors Depending on the error dialog box that appears respond in one of the following ways Click the OK button on the error dialog box Ifthe dialog box asks if you want to continue running scripts click the Yes button Upgrading a system from one version of WEBES to another may result in rare JavaScript errors caused by the web browser caching information from previous Web interface sessions with the older version of WEBES Clearing your browser s cache can often eliminate future JavaScript errors 2 3 3 9 JavaScript Error When Viewing Director Settings If your browser is configured to display all script errors you see a JavaScript error when you click the Director Settings tab This error does not impact the operation of SEA and can be safely closed To avoid seeing the error in the future configure your browser so that it does not display every script error 2 3 3 10 Time out Issue If you consistently receive time out notifications when using the web interface for a specific function use the same function in the Command Line Interface as a workaround 2 3 3 11 Multiple Sessions using Mozilla and Netscape 7 Avoid opening the web interface in multiple windows using Netscape 7 and Mozilla A frame update in one window can adversely affect the same named frame in another window Instead use tabs to run multiple sessions Rev 9 8 06 2 14 Web Based Enterprise Services Rele
38. ces as well as other issues 1 6 1 15 WEBES Uninstall Affects ISEE Client WCCProxy WEBES and the ISEE Client both require the WCCProxy In some cases you may decide to uninstall WEBES but leave an ISEE Client on the system If so you must manually restart the WCCProxy after WEBES uninstallation because removing WEBES will leave the WCCProxy in a stopped state Windows C gt net start wccproxy UNIX variants usr sbin wccproxy start OpenVMS wccproxy start Rev 9 8 06 Web Based Enterprise Services Release Notes 1 13 Overall WEBES Release Notes 1 6 WEBES Known Issues 1 6 1 16 Changing Time Zone Causes Incorrect Report Time Note When the Director is running System time zone changes are not reflected in the Report Time field of WEBES problem reports You have to restart the Director again so that System time zone changes are reflected in the Report Time field of WEBES problem reports 1 6 1 17 Errors From desta sicl qsap on Commands Intermittently on some systems it has been observed on HP UX so far you may receive errors attempting to enable OSEM PRS or SICL DSNLink notification using these commands desta qsap on desta sicl on The errors displayed may look like this desta qsap on What is the name of the Open Service Event Manager OSEM formerly CSG QSAP node localhost What is the port number the OSEM node is listening on 2069 Error 354 File I O error Unable to create or write to
39. command parsing errors OpenVMS does not expand wildcards before passing arguments to a program and as a result OpenVMS cannot find any files that match the given argument For example the following command does not work and results in the given error wsea n analyze svctools common common ca examples zpd Error During Command Parsing Cannot find the file dir svctools common common ca examples zpd To input all files in a directory enter the directory path alone without wildcard characters Most commands automatically search for and process all files that have the following recognized error log filename extensions errlog zpd sys evt To specify multiple input files put them in a comma separated list after the input parameter There must be a space after each comma e Scrolling Output in Terminal Display When you enter a CLI command in a command window the resulting output scrolls continuously in the terminal display To set a screen pause after each output page modify the command as shown in the following example PIPE command TYPE PAGE SAVE SYSSINPUT Where command is the CLI command that you want to pause You need to enter the command for all CLI outputs you want to pause To simplify the process you can save this stream to a variable by entering the following line in the login script more TYPE PAGE SAVE SYSSINPUT Once this variable is established in the login script or at th
40. d Thread 29 5 main EXCEPTION java lang NullPointerException at com compaq svctools desta services notification transport ISEETransport sendParcel 2 3 4 3 Microsoft HotFix Corrects Application Event Log Corruption Problem There is a problem in how Windows 2000 writes to the Application Event Log that can cause corrupted events to be written to the log in some cases SEA may not be able to analyze the corrupt events which may be analyzable EVA events for example and thus will not generate the proper problem notifications Microsoft has made a patch available through a limited means For information from Microsoft refer to Rev 9 8 06 Web Based Enterprise Services Release Notes 2 19 System Event Analyzer 2 3 SEA Known Issues http support microsoft com default aspx scid kb en us 829246 This hotfix should be applied to all HP StorageWorks Management Appliances especially ones with ISEE or WEBES installed You can obtain the patch from your HP Customer Support representative 2 3 4 4 Windows Event Log May Not Grow to Configured Size On all Windows versions there is a 300 MB limit to the size that a binary event log will grow regardless of any higher limit you may define in the Event Viewer for that log If the log is configured to Do not overwrite events new events will not be written after the file reaches 300 MB For more information refer to http support
41. d not run DECevent If there are multiple cluster nodes that need to be modified add a similar IF line for each affected cluster node To prevent WEBES from starting on an OpenVMS platform use the following procedure Edit the startup Script sys startup desta startup com 2 Insert the following code at the beginning of the file node FSTRNLNM SYSSNODE IF node EQS nodenamel THEN EXIT 1 Replace nodename1 with the name of the node that should not run WEBES If there are multiple cluster nodes that need to be modified add a similar zr line for each affected cluster node 2 3 1 8 Upgrading to an Operating System that Supports Drape or Indictment Some versions of OpenVMS do not support the Drape or Indictment services If you upgrade from a version that does not support the services to a version that does you must modify your WEBES installation See the System Event Analyzer User Guide for information on modifying the installation Rev 9 8 06 Web Based Enterprise Services Release Notes 2 7 System Event Analyzer 2 3 SEA Known Issues 2 3 1 9 SEA Problem Reports Not Received by OSEM You may see an error similar to the following in the Director error log see the section on log files in the WEBES User Guide Chapter 2 RECOVERED FROM ERROR on January 13 2004 4 48 05 PM GMT 00 00 254 912 sec elapsed IOException Current Thread Thread 29 com compaq svctools desta
42. e SendPckAndIn tData PrivInterface java 014 gt at com compaq svctools ca services JNIRoot EvtInterface RequestEvtSet Ev tInterface java 619 gt at com compaq svctools ca services eventreaders connections EvtProxyFile Connection retrieveEvent EvtProxyFileConnection java 216 gt at com compaq svctools ca services analysis engine AnaEngineAuto analyze Event AnaEngineAuto java 301 ewe RECOVERED FROM ERROR on November 23 2005 4 19 25 AM MST 1129 665 sec elapsed gt AnaEngineAuto analyzeEvent 6 Null buffer returned from retrieveEven t EventDescriptor CEH event gt originID 1 gt fieldNotFound false As a result WEBES may not process all of the events in the ERRLOGSYS 1 previous file version It should not harm subsequent SEA automatic analysis of new events In a future version WEBES will copy the ERRLOGSYS file to process large amounts of data without keeping the file open which will minimize the chances of this problem occurring The exact retry scheme that ERRFMT uses is as follows After each write failure it will wait for retry number 2 seconds before retrying the write So it will wait 2 seconds before the first retry If the write fails again it will wait 4 seconds before the second retry etc ERRFMT will retry up to 17 times including waiting 36 seconds after the 17th retry before creating a new file version
43. e command line you can use the following command to set a screen pause PIPE command more 2 3 3 SEA Web Interface Issues These issues apply to the SEA web interface on all operating systems Note The Undo Changes button on the Managed Entity screen may not undo the changes made Another way to undo changes is to navigate to a different page of the SEA Web interface without clicking the Apply Changes button Rev 9 8 06 Web Based Enterprise Services Release Notes 2 11 System Event Analyzer 2 3 SEA Known Issues 2 3 3 1 overwrite file if exists Option in SEA WUI is not Working while Creating New Binary Error Log When you click on the New Binary Error Log Creation icon in the SEA WUI tool bar add a new file in the Add File to Input List tab create a new binary with the same name as created in the first attempt and select the option overwrite file if exists a dialog appears as Output file exists and the overwrite option was not selected The original file was not overwritten is displayed Workaround To avoid this problem manually delete the existing file before re creating it or choose a different file name 2 3 3 2 Enabling Text Entry in Other Logs Pane When enabled the text entry field in the Add Logs screen allows users to add log files by entering the path and filename for an event log located anywhere in the file system In order to enter a file name into the text entry field the log file m
44. e following link for more information on the bug http support microsoft com kbid 890042 amp SD tech 2 3 5 HP UX SEA Issues These issues apply to SEA on HP UX 2 3 5 1 No Binary Event Log HP UX has no binary event log to analyze like the log on Windows or OpenVMS Because of this SEA currently offers no automatic analysis on HP UX Without automatic analysis many SEA functions such as Real Time Monitoring and Full View and commands such as wsea test and wsea report have no effect In addition SEA never sends notifications because it does not process live events In the future binary event log capability or analysis of other event logs may be added to the HP UX version of SEA Rev 9 8 06 Web Based Enterprise Services Release Notes 2 23 System Event Analyzer 2 3 SEA Known Issues 2 3 6 Linux SEA Issues 2 3 6 1 C C Runtime Libraries Version 6 1 1 or Later Required Your Linux system must have version 6 1 1 or later of the C C runtime libraries installed for SEA to run Normally this is the case for Red Hat 7 3 or later systems This dependency will be removed in a future WEBES release 2 3 6 2 No Binary Event Log Linux has no binary event log to analyze like the log on Windows or OpenVMS Because of this SEA currently offers no automatic analysis on Linux Without automatic analysis many SEA functions such as Real Time Monitoring and Full View and commands such as wsea report have no effect In addition S
45. e following paths C Program Files someDirectory C anotherDirectory C Program Files someDirectory C NanotherDirectory OpenVMS The following issues apply when entering commands on OpenVMS systems Invalid Directory Error Message When you use the analysis or translation commands and specify a directory as or the process generates an Error During Command Parsing Can t find the file dir error message and quits To avoid this problem specify the directory or directories explicitly Maximum Character Length Error Message If you enter a lengthy CLI command you may exceed the OpenVMS maximum command character length As a result OpenVMS may return a command error message RMS W TNS terminator not seen that refuses the number of characters that you have used The user can use the lengthy CLI command by entering at the end of each line without space between the last character of the command and This facilitates the command to continue even if it is longer than the maximum command character length To avoid this error shorten the parameters in the CLI command For example you can substitute a lengthy absolute file path with a shortened relative path for a file s directory Wildcards Not Expanded Rev 9 8 06 2 10 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues Filenames containing wildcards characters are not expanded and result in
46. e larger than this If WEBES is installed or upgraded when ISEE is already installed then WEBES raises this limit to allow the SEA collections to be sent to HP by ISEE If ISEE is installed or upgraded after WEBES however then the limit remains the default 1 5 MB 2 WEBES raises the limit to 3 MB It is possible that SEA created a zip file larger than 3 MB We do not anticipate this occurring on any possible EVA configuration If either reason seems feasible then raise the limit by following these steps 1 Ina Command Prompt window cd to the directory containing the script which raises the limit that can vary depending on where you installed WEBES For example cd C Program Files Hewlett Packard svctools specific ca config 2 Execute the following command cscript changeFileSizeLimit js 10 This will change the file size limit to 10 MB which is the maximum 3 A log file is created in the current directory named changeISEEFileLimit log Open this log file in an editor such as Notepad to see whether the script is executed successfully or not 2 3 4 2 Error while Entering Product Serial Number and Product Number for EVA Managed Entities The following error messages will be seen when entering the product serial number and the product number for EVA managed entities They are harmless and should be ignored RECOVERED FROM ERROR on May 4 2005 1 36 02 PM PDT 268 162 sec elapsed Error sending ISEE Notification Current Threa
47. ease Notes Overall WEBES Release Notes 1 6 WEBES Known Issues If you install WEBES Windows Pentium kit on Windows Itanium or WEBES Windows Itanium kit on Windows Pentium it will prompt the same error messages as mentioned in section 1 6 1 1 Installing WEBES on Unsupported Platforms above as applicable Hence please ensure that you obtain the right kit before installing WEBES 1 6 1 2 Error During Reading of Obligation Information The following error message may be seen in the Director log when the WEBES Service Obligation period is close to expiring They can be ignored The problem will be corrected in a future WEBES release RECOVERED FROM ERROR on May 4 2005 9 28 15 AM PDT 76952 898 sec elapsed lt local gt 3459688795090195548 com compaq svctools desta services web compo nent DefaultWebInterfaceServer 4 com compaq svctools desta messages serv ices ProblemReportMessage Error processing message because java lang NullPointerException Current Thread Thread 11 com compaq svctools desta services web component Defaul tWebInterfaceServer 5 main 1 6 1 3 WEBES Installation Issue on ISEE OSEM Host If you are using OSEM to send ISEE notifications and you are installing WEBES v4 4 4on the same system where the ISEE Client is installed follow these steps before installing WEBES v4 4 4 to ensure that leftover processes started by previous OSEM calls to WCCProxy do not prevent proper WEBES v4 4 4 insta
48. ector and WCCproxy services After the command to stop one of these services completes such as desta stop or net stop desta service the operating system sometimes requires a few more seconds to stop all WEBES related processes and release their resources such as sockets On rare occasions restarting too soon after stopping can result in errors in the Director log file and the services also may fail to restart To avoid this issue wait 10 more seconds before restarting after the command completes In Windows this means you also must avoid cycling the services using the one step restart option available within the Services Manager because it stops and restarts a service too quickly Instead take separate steps in the Services Manager to stop the service wait 10 seconds and then start the service 1 6 1 13 Service Cockpit Compatibility Hewlett Packard Service Cockpit is not compatible with WEBES 4 2 or higher In other words Service Cockpit does not successfully launch WEBES tools on systems running WEBES version 4 2 or higher including this version 1 6 1 14 Upgrading Versions Older Than Two Releases If you have already installed a WEBES version that is more than two releases older than the latest version you need to uninstall the existing version and install the latest version There are known problems with migrating previous data when upgrading older versions which may result in undesired changes in notification preferen
49. ee e eee eee 2 5 2 3 1 4 Fields Contam Unavailable i5 ue eoakp od ro RE RE HPPPRSETE QR ER ES 2 5 2 3 1 5 File Not Found Error In DESTA Log File 250506c00csci mmm 2 5 2 3 1 6 Transfers Files With FIP uuo seek SEES tod pede Buh a ope Eri 408 oe n d wie 2 6 2 3 1 7 Duplicate Callouts with both DECevent and WEBES Installed 2 6 2 3 1 8 Upgrading to an Operating System that Supports Drape or Indictment 2 7 2 3 1 9 SEA Problem Reports Not Received by OSEM 0 06 66 wees nw sea ree recess 2 8 2 3 2 SEA Command Line Interface Issues veo tbe EE bob siiip inbe EUR Sobald 2 8 2 3 2 1 ca Command Changed to wsea sc ssese eer deret ease s 2 8 2 9 2 2 Bntermp Comma 2 3 ptos tos cp pd oU S e Pant T VR ce EAD Roe gos Pan 2 8 2 3 3 SEA Web Interface SSues iesees ee hee mr REPRE red gre E ques 2 11 2 3 3 1 overwrite file if exists Option in SEA WUI is not Working while Creating New Binary Efor LOS 2e 99 e Eee pu bete pedea eh cere tide ede Reems 2 12 2 33 2 Enabling Text Entry an Other Logs Pane cuc dish Simian Bias T REIHE T RR RE 2 12 2 3 3 3 Node Name Change Causes Connection or Notification Failure 2 12 2 3 3 4 Cannot Activate a Running Node i2 b commas saute n v bdot bor eb wie Dinie akin 2 13 2 3 3 5 High Volume of Events Hangs Interface sees se scr Res 2 13 2 3 3 0 Frame Opensun New WIDdOW 22 2 ote turie nep ERR TERIS ERI E ENSE GE 2 13 2 3 3 7 Null Pointet E
50. es For more information on the CLI commands See section Managed Entities SMA EVA WBEM Server and VLS Commands of WEBES User Guide For more information on the Web based management interface See section Managed Entities of WEBES User Guide Any changes that users have made to the User Settings or the Director Settings in the Web interface may have to be changed again after WEBES has been upgraded or installed Use the Web interface to check the values and restore any changes that are not migrated 1 6 2 5 CCAT Not Available on Windows Itanium The Computer Crash Analysis Tool CCAT is not available as an installable component in the WEBES kit on Windows Itanium WEBES will not process any crash dumps No CCAT support is currently planned for Windows Itanium 1 6 2 6 Directories and Registry Keys Left Behind by WEBES Itanium Removal Certain directories installed by WEBES for Windows Itanium and Windows Pentium will not be removed on WEBES uninstallation They are harmless and may be deleted manually if desired C Program FilesMHewlett PackardNsvctoolsNcommon C Program Files Hewlett Packard svctools specific There should not be any files or subdirectories within these directories after WEBES is removed Certain Windows Registry keys installed by WEBES for Windows Itanium and Windows Pentium will not be removed on WEBES uninstallation They are harmless and may be deleted manually if desired HKEY_LOCAL_MACHINE SY
51. es from the VCS directory C hsvmafiles to the above NAPP directory within WEBES An example of a parse file name is HSV110_event_cr04bb_3020 txt If errors are still returned contact HP Services for assistance 2 3 4 12 Newly Added EVA Not Listed in SEA Web Interface If you add a new EVA to the system after WEBES is installed please configure it according to WEBES Install Guide section 2 3 6 Adding an EVA After Installing WEBES Rev 9 8 06 2 22 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues 2 3 4 13 Resuming from Standby Loses Network Resources in XP SP2 A Microsoft bug in Windows XP Service Pack 2 may affect WEBES SYMPTOMS You resume your Microsoft Windows XP based computer from standby while your network is either disconnected or down After network connectivity is restored you lose access to your network resources Additionally if your Windows XP based computer is moved to a different network while the computer is on standby you lose access to network resources when you resume the computer CAUSE These problems may occur when all of the following conditions are true You have installed Microsoft XP Service Pack 2 SP2 on the computer You use a smart card to log on to your computer RESOLUTION Hotfix information A supported hotfix is now available from Microsoft but it is only intended to correct the problem that is described in this article Check th
52. following error message may appear in the DESTA log file when using the Microsoft JVM in Internet Explorer Rev 9 8 06 Web Based Enterprise Services Release Notes 2 5 System Event Analyzer 2 3 SEA Known Issues Could not find file WCCAppletl02BeanInfo class It is safe to ignore this message since it does not impact the performance stability or functionality of SEA 2 3 1 6 Transferring Files with FTP If you move files using FTP it is important to use the appropriate settings for the transfer Windows Make sure the FTP transfer mode used for binary error logs is binary rather than ASCII SEA does not generate an error message when you process a file that was transferred in ASCII mode but it may skip some events show corruption in translated events and produce unreliable analysis results OpenVMS Make sure the FTP transfer mode used for binary error logs is binary rather than ASCII In addition the file attributes must be restored after the file is transferred to an OpenVMS machine In order to preserve the correct file attributes SEA files should be formatted as Stream LF with the CR control character This file formatting restriction applies to binary event log files and all other SEA files containing binary non text data When you are using FTP to transfer files to an OpenVMS system FTP does not preserve the correct file attributes Use the following command after the transfer has completed to restore the correct
53. g profile txt change this to the location appropriate for your operating system CA ACHSContact me mymachine company com change this to the appropriate email address ccat ACHSContact me mymachine company com change this to the appropriate email address CA ACHSRoute SICL enter this verbatim 6 Future notifications should be sent to the appropriate places Restarting the Director or WCCProxy should not be necessary The problem is expected to be fixed in a future WEBES release 1 6 2 Windows WEBES Issues 1 6 2 1 ClassNotFoundExceptions in Director Log If you have previously removed WEBES but kept your configuration information then upon re install choose a different combination of WEBES components SEA and or CCAT or choose a different install directory for WEBES the saved configuration data will not be valid and WEBES may fail One possible symptom may be ClassNotFoundExceptions shown in the DESTA Director log file installed directory svctools specific Webes logs director_err txt This problem will be fixed in a future release Rev 9 8 06 Web Based Enterprise Services Release Notes 1 15 Overall WEBES Release Notes 1 6 WEBES Known Issues Workaround Stop the Director net stop desta service delete the file installed directory svctools specific desta config Configuration dat then restart the Director net start desta service 1 6 2 2 WEBES Installation Appears to Hang When installing WEBES certain
54. hat you run the WEBES installer webes install only on the same cluster node from which you originally installed WEBES The upgrade section in the WEBES Installation Guide contains instructions for determining which node is the original 1 6 4 7 Alternate Boot Start and Stop Methods Normally installing WEBES sets up VMS system logicals required for proper WEBES operation and optionally sets up the WCCProxy and DESTA Director processes to start shortly after booting and to shut down as part of the site specific shutdown process The WEBES installer uses the VMS facility MCR SYSMAN STARTUP for this setup If you prefer to control the startup and shutdown yourself see the updated WEBES Installation Guide which includes new post installation guidelines for tailoring the startup and shutdown process 1 6 4 8 Cannot Get SMTP Notification on OpenVMS If there is a problem in the SMTP configuration of an OpenVMS system WEBES SMTP email notification may not work even if regular SMTP email on the system appears to be working You can increase the verbosity of the SMTP conversation to help diagnose the problem by following the procedures below WEBES calls Java API code to send SMTP email On OpenVMS the Java API uses the SMTP receiver which may be different from how other SMTP email is handled on the OpenVMS system Rev 9 8 06 Web Based Enterprise Services Release Notes 1 25 Overall WEBES Release Notes 1 6 WEBES Known Issues To
55. installed in the future it will not attempt to use the old hostname Instead it will replace the line with the correct current hostname Rev 9 8 06 2 12 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues If WEBES is upgraded or uninstalled saving configuration data and later installed then the recovered wccPRoxv nEc file in installed directory specific wccproxy config containing the old hostname can cause WEBES to send no notifications other than to the SEA Web interface To correct this after upgrading or installing WEBES remove the following line from WCCPROXY REG beginning with WCCProxy owner Then stop both the Director and the WCCProxy and restart both 2 3 3 4 Cannot Activate a Running Node If you cannot activate a node that is currently running it may be too busy to respond Click on the Activate Node entry in the navigation tree later which may activate the node If you suspect that the Director process is not running on that node you can verify it by issuing the desta status command on that node 2 3 3 5 High Volume of Events Hangs Interface If you are viewing the Events tab on the Real Time Monitoring display of a node and a rush of events are added to the event log the web interface may hang The problem is caused by SEA attempting to refresh the Events frame multiple times and dramatically impacting response time To clear the condition click Refresh in your browse
56. insufficient privilege or file protection violation NODES DIR 1 SVCTOOLS DIR 1 Total of 2 files If your user ID does not have all privileges or has not issued the SET PROCESS PRIV ALL command you cannot execute any WEBES CLI commands If you attempt to run WEBES commands with insufficient permissions you see errors similar to the following examples desta status DCL W ACTIMAGE error activating image VCTOOLS HOME COMMON BIN DESTA CMD EXE CLI E IMGNAME image file UTESDKAO SYS0 SYSCOMMON HP SVCTOOLS COMMON BIN DESTA CMD EXE RMS E PRV insufficient privilege or file protection violation wsea n status DCL W ACTIMAGE error activating image VCTOOLS HOME COMMON BIN CA CMD EX CLI E IMGNAME image file UTESDKAO SYSO SYSCOMMON HP SVCTOOLS COMMON BIN CA CMD EXE RMS E PRV insufficient privilege or file protection violation Zlwnovemil Z il wm oe Note that it is not enough to be a member of the SYSTEM group to execute commands you must have all privileges If you have all privileges it is not necessary be a member of the SYSTEM group See the System Event Analyzer User Guide for more information on the permissions required to view the WEBES directory tree and execute WEBES commands 2 3 7 3 WEBES Commands Return Error Activating Image If your account lacks sufficient permissions to ru
57. layed by SEA The messages may appear to be errors but are ignorable artifacts of SEA processing Kits updates and documentation for WEBES are available at the following URL http www hp com services webes Rev 9 8 06 Web Based Enterprise Services Release Notes 1 27 Overall WEBES Release Notes 1 7 Further Information Rev 9 8 06 1 28 Web Based Enterprise Services Release Notes 2 System Event Analyzer This chapter contains information that applies specifically to System Event Analyzer SUI iaty urea peti aei rb equ DER LES Po Soke pede peda ada pelos page 2 2 Supported Products 2 993 P petu pre sg d pipa E acted page 2 2 SEA Known ISSUES perse brodo Bere srk UE ded IR GR PO PERIL Aa PS dee wares 988 page 2 4 P trtber Intormatoni seprono ddp IPOD a EP Fl PRG A RIO UR eee page 2 28 Rev 9 8 06 Web Based Enterprise Services Release Notes 2 1 System Event Analyzer 2 1 Summary 2 1 2 2 Summary System Event Analyzer SEA is a fault analysis utility included with the Web Based Enterprise Services WEBES service tools Each WEBES based service tool adds functionality to the Director a process or set of processes that executes continuously SEA provides the Director with the capability to capture and interpret hardware events The analysis of events can be performed automatically or when requested by an outside process SEA provides background automatic analysis by monitoring the active binary event log and
58. lease follow these steps 1 Close any applications that may have WEBES files open including OSEM ISEE Client and file editors such as Notepad 2 Stop the Windows Management Instrumentation WMI service either via the Start Control Panel Administrative Tools Services utility or by issuing the following command in a Command Prompt window net stop winmgmt If the system prompts you about dependent services allow it to stop those services too 3 Close the Services utility window that you may have opened above 4 Delete the above file yourself manually 5 Click the Yes button below After WEBES setup completes you can restart the WMI service if it was running and any dependent services that were running Rev 9 8 06 1 16 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issues Have you performed the above steps and are you ready to continue with the installation now Answering No will abort the WEBES setup program Yes No After you stop the service and any other applications that have the WEBES files open and delete the offending WEBES file shown in the popup window you can answer Yes to the popup window prompt and the WEBES installation should continue successfully After the install completes you can restart the WMI service if you stopped it earlier by either a Go into Control Panel
59. ll validate the preliminary implementation prior to official release After Beta ISEE VLS support will be available to all VLS customers with products under warranty or an appropriate support contract Through Subcriber s Choice HP will notify VLS customers when ISEE VLS support is enabled by default in a WEBES release or if needed how to enable it See the Subscribe link on the bottom of the www hp com home page Please contact isee vIsbeta hp com if you are interested in participating in the Beta program The Managed Device Entitlement section covers the data entry needed to configure or optimize support for VLS devices in WEBES Supports HP StorageWorks VLS6105 VLS6109 VLS6510 VLS6518 VLS6840 and VLS6870 with firmware version 1 0 12 or later Requires WEBES installations on HP Proliant 32 bit Windows 2000 Server and Windows Server 2003 not supported on Windows XP or 64 bit Windows or non Windows platforms An HP ProLiant Intel 32 bit machine can support multiple VLS devices This machine may also be a System Management Server SMS Storage Management Appliance SMA or Network Attached Storage NAS that is also supported by Command View TL However as of this writing these have not been fully tested Install HP ISEE Client or upgrade to version A 03 95 or later Microsoft JVM 5 00 3810 or later reboot after installing and run Windows update to acquire the JVM patch must already be installed for an HP ISE
60. llation Shut down OSEM and the ISEE Client Remove the existing WEBES version do not upgrade it Kill any remaining WCCProxy exe WCCAgents exe or CAAgents exe processes Install WEBES v4 4 4 mom 1 6 1 4 Intermittent Socket Errors Occasionally CLI commands such as desta stop Or wsea auto off that connect to the Director will display errors or cause errors to be written to the Director log file The errors may include expecting code Or socket closed signifying that the socket connection was disconnected before the disconnect handshaking protocol between the CLI process and the Director or WCCProxy was completed The error can be ignored since the required functions have been completed before the disconnect handshaking started The error will be corrected in a future release Examples of this error which can be ignored are RECOVERED FROM ERROR on April 14 2005 2 45 49 PM GMT 08 00 6 346 sec elapsed Socket has a problem Expecting code lt local gt 101331133349757508 EXCEPTION java io EOFException Expecting code WARNING on August 11 2005 7 03 41 PM GMT 05 30 6626 84 sec elapsed Rev 9 8 06 Web Based Enterprise Services Release Notes 1 9 Overall WEBES Release Notes 1 6 WEBES Known Issues Socket close problem lt local gt 40790387440747720 EXCEPTION java net SocketException Socket closed EXCEPTION java io IOException Broken pipe at java net SocketOutputStream s
61. lly selects the Director s Global Attributes 3 Select ctrlrStartupTimeout from the bulleted list By default the value is set to 60000 milliseconds 1 minute 4 Enter a new time out value in milliseconds in the textbox Increasing the value to 300000 milliseconds 5 minutes provides the services with more than enough startup time 5 Click Change If you cannot connect to a Web interface but can start the Director successfully at a point of time such as when the machine is not heavily loaded issue the following command while the Director is running to increase the time out desta msg chgconf global 6 300000 i im Rev 9 8 06 Web Based Enterprise Services Release Notes 2 15 System Event Analyzer 2 3 SEA Known Issues If you cannot start the Director at all at any time because it does not successfully start within the time out period then issue the following series of commands to disable the SEA CCAT services Start the Director without the commands which should start within the time out change the Director s time out value and then re enable the SEA CCAT services Note SEA was formerly CA and this acronym remains in certain places in the code Run the following commands for all platforms desta stop wccproxy stop wccproxy kill desta exec com compaq svctools desta configuration ChangeEnrollments unenroll ConfigDefaultsCCAT txt Ignore the error messages that result from this command This typic
62. mand prompt then enter net stop desta service to kill the Director process Enter net start desta service to restart the Director 1 6 2 11 PATH Update Required on Terminal Server Installation When installing WEBES from a client onto a Terminal Server installing from a Remote Desktop open and close the system PATH environment variable as described in the WEBES Installation Guide Opening and closing sets the PATH so that commands such as desta or wsea can work without specifying the full svctools common bin path to the command 1 6 2 12 Windows Itanium WEBES Removal Leaves Files Behind After WEBES is removed the WEBES kit for Windows Itanium leaves some WEBES files present in the directory tree By default the installed directory is SSystemDrive Program Files Hewlett Packard svctools These files can cause problems if WEBES is later re installed to the same directory Future WEBES kits will remove all WEBES files upon WEBES removal Workaround Before re installing WEBES manually delete the entire tree of files under the WEBES installed directory sSystemDrive Program FilesMHewlett PackardNsvctools by default 1 6 2 13 Installation may not set the PATH variable if PATH is not defined before installing WEBES In such a scenario the PATH variable contains only the WEBES path and WCCProxy commands do not work Rev 9 8 06 1 20 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issue
63. member of the Administrators group as described in the WEBES Installation Guide you will not see any choices for any of the WEBES tools under the menu Start Programs Hewlett Packard Service Tools You may see choices for other installed Hewlett Packard service tools that are not part of WEBES such as Service Cockpit or SmartScope Rev 9 8 06 Web Based Enterprise Services Release Notes 3 3 Computer Crash Analysis Tool 3 3 CCAT Known Issues 3 3 3 OpenVMS CCAT Issues The following known issues affect CCAT on OpenVMS 3 3 3 1 Insufficient Privilege or File Protection Violation If you are not a member of the SYSTEM group or your user ID does not have the privileges specified in the WEBES Installation Guide you will not be able to access or see any directories or files under the WEBES CCAT directory tree pointed to by the SVCTOOLS HOME logical SYS COMMON HP by default You will see errors such as the following dir svctools home 000000 SDIRECT E OPENIN error opening SVCTOOLS COMMON 000000 as input RMS E PRV insufficient privilege or file protection violation dir svctools home common bin SDIRECT E OPENIN error opening SVCTOOLS COMMON COMMON BIN as input RMS E PRV insufficient privilege or file protection violation dir sys common HP Directory SYSSCOMMON HP SDIRECT E OPENIN error opening SYSSCOMMON HP NODES
64. mentation and Technical Data for Commercial Items are licensed to the U S Government under vendor s standard commercial license Hewlett Packard shall not be liable for technical or editorial errors or omissions contained herein The information is provided as is without warranty of any kind and is subject to change without notice The warranties for Hewlett Packard products are set forth in the express limited warranty statements accompanying such products Nothing herein should be construed as constituting an additional warranty This service tool software is the property of and contains confidential technology of Hewlett Packard Company or its affiliates Possession and use of this software is authorized only pursuant to the Proprietary Service Tool Software License contained in the software or documentation accompanying this software Hewlett Packard service tool software including associated documentation is the property of and contains confidential technology of Hewlett Packard Company or its affiliates Service customer is hereby licensed to use the software only for activities directly relating to the delivery of and only during the term of the applicable services delivered by Hewlett Packard or its authorized service provider Customer may not modify or reverse engineer remove or transfer the software or make the software or any resultant diagnosis or system management data available to other parties without Hewlett Packard s or its
65. n WEBES commands you may see an activating image error This error has the same cause as those described in Section 2 3 7 2 2 3 7 4 Slow Response Generating Other Logs List Due to a Java performance limitation on OpenVMS the list of other log files in the web interface may take a long time to display from 20 seconds to over a minute depending on your system In some cases the web interface may time out waiting for the file list displaying this error Error encountered creating file list The director may be busy Try clicking the link again or manually entering the file path in the text box below Rev 9 8 06 Web Based Enterprise Services Release Notes 2 27 System Event Analyzer 2 4 Further Information 2 4 If you see this error add and set the ca wur oLmMsgwait key in the Desta Registry to 90 seconds 1 Add the key if it does not already exist desta dri add CA WUI OLMsgWait 2 Setthe key to 90 seconds desta dri set CA WUI OLMsgWait 90 2 3 7 5 Exclude Node Names from Filespecs SEA does not accept OpenVMS node names when included as part of a filespec such as when specifying an input or output file name For example filespecs similar to those shown below would not work because the node name is included NODE1 password USERDISK USERNAME MYFILE TXT NODE 1 USERDISK USERNAME MYFILE TXT when no authentication is needed NODE2 SYSSERRORLOG ERRLOG S YS 2 3 7 6 CAAgent Processes Created Bu
66. ng out of memory conditions one of the following conditions may apply Your system has run out of memory or paging space The Director process has reached its Java memory limits These limits are set during WEBES installation but may be overridden by a user If the Java memory limits are responsible for the problem you can raise the memory limits applied to the Director process and its subprocesses After the limits have been increased you can restart the Director and perform the actions that caused the out of memory error The limits can be set as high as necessary and are only constrained by the memory and paging space available on the system Refer to the WEBES User Guide for details on adjusting the memory limits 1 6 1 11 Upgrade Requires Reinitialized Log If you are running SEA formerly Compaq Analyze reinitialize the system error log as described in the platform specific sections of the WEBES Installation Guide before performing a WEBES upgrade Otherwise up to seven days of repeat previously seen problem reports may appear This behavior occurs because of an issue where SEA re scans the entire log after the upgrade Normally SEA scans the entire log only after a fresh installation Rev 9 8 06 1 12 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 6 WEBES Known Issues 1 6 1 12 Errors When the Director or WCCProxy is Restarted Too Soon This release note applies to both the desta Dir
67. niform model it complements and extends existing management protocols and instrumentation such as Simple Network Management Protocol SNMP and Desktop Management Interface DMI As of the WEBES 4 5 release you can add a WBEM Server in the Managed Entity page to receive WBEM indications 1 6 WEBES Known Issues The issues described in the following sections apply to the overall WEBES suite e 1 6 1 General WEBES Issues 1 62 Windows WEBES Issues 1 6 3 Linux WEBES Issues 1 6 4 OpenVMS WEBES Issues See Section 2 3 SEA Known Issues for information specific to SEA See Section 3 3 CCAT Known Issues for information specific to CCAT 1 6 1 General WEBES Issues These issues apply to WEBES on all operating systems 1 6 1 1 Installing WEBES on Unsupported Platforms If you install the Windows Pentium kit on unsupported platforms see Section 1 3 Operating System Requirements for a list of unsupported platforms it will prompt the following error message This WEBES kit supports only 32 bit platforms Please contact HP support for WEBES kit for your processor type If you install the Windows Itanium kit on unsupported platforms see Section 1 3 Operating System Requirements for a list of unsupported platforms it will prompt the following error message This installation package is not supported by this processor type Contact your product vendor Rev 9 8 06 1 8 Web Based Enterprise Services Rel
68. ntil you receive an answer from WEBES support 1 6 1 7 WEBES Temporary Files Use Disk Space At times WEBES can write many or large temporary files to its installed directory tree when it is working The number and sizes of these files depend on the binary event log files and crash data files being processed by SEA and CCAT respectively Workarounds 1 To ensure that orphan temporary files no longer needed by WEBES are removed a Stop the Director and WCCProxy see SEA User s Guide section 2 3 Processes b Delete any files in the WEBES installed directory tree within any directory named temp such as specific ca temp c Restart the Director and WCCProxy 2 Toreduce the amount of SEA automatic analysis being performed on the system perform the steps under 1 above Before restarting the Director and WCCProxy clean the system s binary event log as described in WEBES Install Guide section for the specific operating system Archiving and Cleaning the Error Log 3 Do not leave SEA Web interface sessions running when they are not in use Closing the Web browser that is connected to your SEA Web interface allows cleaning up of temporary files after sometime Future WEBES releases will manage and limit their temporary file storage needs 1 6 1 8 Backward Compatibility Connections between systems that are running different versions of WEBES including different dot releases or Service Paks may produce unpredictable results
69. ocketWrite Native Method 1 6 1 5 WEBES Configuration Information Not Restored In some cases WEBES configuration information such as contact names email addresses notification enablements and managed entity XML data may not be restored on an upgrade to WEBES either through 1 Uninstalling an older version of WEBES and later installing a newer version even if you choose to save the WEBES information during WEBES uninstallation or 2 Upgrading WEBES while an older version is installed The WEBES team is investigating this problem We intend to fix such cases in future releases of WEBES Workaround 1 On reinstallation of WEBES re enter the data when prompted 2 After upgrading WEBES change any necessary configuration items as described in the SEA User s Guide and the CCAT User s Guide WEBES upgrades are mostly silent and do not prompt the user for configuration information 1 6 1 6 WEBES Output Log Files Grow Without Bound The WEBES Director and WCCProxy text output log files in the specific webes logs and specific wccproxy logs directories see SEA User s Guide section 2 5 Log Files grow without bound The processes append text logging information to those files and do not as yet control their size Normally this is not a problem since WEBES processes write very little to these log files when there are no internal WEBES errors to report However if an error situation arises that
70. pop up dialog windows that prompt for user information may not appear in front of other existing windows This may give the appearance that the WEBES installation has hung This problem will be fixed in a future release Workaround Look for a new window entry in the Windows Task Bar and click on it to bring it in front of other windows so you can enter the information and continue the WEBES installation 1 6 2 3 Installation Prompts When File Fails to Delete In certain cases particularly on SMA systems certain WEBES files can be locked by Windows even though no more WEBES processes are running In that case the WEBES uninstaller will not be able to delete these WEBES files within the svctools directory tree and thus will not be able to install new files of the same names The problem can affect any version of WEBES because the Windows Management Instrumentation WMI service operates this way by Windows design WEBES development feels that it is unwise to summarily stop the WMI service in order to delete these files because the WMI service may be performing other tasks for Windows or other applications at the time Therefore if such a lock exists WEBES v4 4 3 and later installers will detect the situation and prompt the user with a popup window containing text similar to the following WEBES setup failed to delete the above file It may be open and thus locked by the Windows Management Instrumentation service or some other process P
71. processing events as they occur The events in the binary event log file are checked against the analysis rules If one or more of the events in the binary event log file meets the conditions specified in the rules the analysis engine collects the error data and creates a problem report containing a description of the problem and any corrective actions required Once the problem report is created it is distributed in accordance with the customer s notification preferences SEA supplies a web based user interface that connects to the Director and can perform a variety of tasks from a remotely connected web browser In addition a set of command line tools enable diagnosis of binary event logs without connecting to the Director Supported Products Although WEBES can be installed on any of the hardware and operating system combinations shown in Chapter 1 SEA only supports event bit to text translation and event analysis on the following set of HP products The list grows with each subsequent SEA release The following list includes the products that SEA supports This list also is available in the WEBES User Guide In the event of any discrepancy between this list and the WEBES User Guide the release notes take precedence Note Do not confuse the supported products with the systems where WEBES can be installed as explained in the Section 1 2 Hardware Requirements WEBES 4 5 includes support for HP UX 11 23 WEBEM notifications on all Itani
72. r or close the browser and re connect to the web interface 2 3 3 6 Frame Opens in New Window If you click on different areas of the web interface quickly while it is updating a frame may appear in a new window Close the window and re click on the button or link to update the correct frame in the web interface 2 3 3 7 Null Pointer Errors If a NullPointerException error occurs while using the web interface click your browser s Refresh button If you continue using SEA without refreshing you may encounter additional errors or unexpected behavior 2 3 3 7 1 Null Pointer Errors from Large Log Files In some cases if you add an Other Log to the web interface for manual analysis and click on it to analyze it a time out can occur after 10 minutes if the binary event log has a very large Rev 9 8 06 Web Based Enterprise Services Release Notes 2 13 System Event Analyzer 2 3 SEA Known Issues number of events tens of thousands or more You may be encountering this time out if other smaller logs are processed correctly You can increase this time out by issuing the following commands desta dri add desta AutoLaunch Timeout desta dri set desta AutoLaunch Timeout nnnn Replace nnnn with the number of milliseconds to set the time out value The default is 10 minutes 600000 You can effectively remove the time out by setting a large value like 1 hour 36000000 2 3 3 8 JavaScript Errors During heavy processing you m
73. raints or expectations on when a particular email will be delivered The Director log can be found at SVCTOOLS HOME SPECIFIC WEBES LOGS DESTA_DIR LOG 7 Run the following commands to stop the debug logging for the DESTA Director and copy the log files desta msg log warning desta stop copy desta dir log desta dir debug nodename log desta start 8 Run the following commands to stop the SMTP debug logging deassign sys tcpip smtp log level deassign sys tcpip smtp recv debug deassign sys tcpip smtp recv trace Qsys startup tcpip smtp shutdown Qsys startup tcpip smtp startup Xr uuu Rev 9 8 06 1 26 Web Based Enterprise Services Release Notes 1 7 Overall WEBES Release Notes 1 7 Further Information 9 Examine the above DESTA_DIR LOG file search for SMTP and the following SMTP log files The sySSSPECIFIC TCPIP SMTP TCPIPSSMTP_LOGFILE LOG generally logs activity once a job is placed on a queue for execution The SYSS SPECIFIC TCPIP SMTP the TCPIP receiver 10 Ifthe problem is not evident from the log files send the desta dir debug nodename 1og file to HP Services to be examined by WEBES Support CPIPSSMTP RECV RUN LOG generally logs activity of Further Information See the WEBES Installation Guide for more details about WEBES See also the SEA Users Guide Appendix D Known Messages in SEA for messages that may be disp
74. rite the event To resolve the problem do one of the following Preferred Modify the When maximum logsize is reached setting in the Windows event viewer utility Change it from Do not overwrite events to one of the Overwrite events settings Increase the size of the log Delete some of the events in the log 2 3 4 8 WEBES Directory Tree Missing or Access Denied If your user ID is not a member of the Administrators group you cannot access or see any directories or files under the WEBES directory tree C Program Files hp svctools by default See the System Event Analyzer User Guide for information on the permissions required to view the directory tree 2 3 4 9 WEBES Commands Not Recognized If your user ID is not a member of the Administrators group you cannot execute any WEBES CLI commands If your user ID does not have sufficient permissions you see errors similar to the following C Program Files Mhp desta desta is not recognized as an internal or external command operable program or batch file C Program Files hp gt svctools common bin desta status Access is denied See the System Event Analyzer User Guide for information on the permissions required to use WEBES commands 2 3 4 10 Hewlett Packard Service Tools Entry on Start Menu is Empty If your user ID is not a member of the Administrators group the menu options for the WEBES tools do not appear in the Start menu Start Programs Hewlett
75. rrectly on those new files You can obtain the previous set of examples from an installed WEBES v4 4 1 kit or contact HP Customer Support 2 3 4 Windows SEA Issues Internet Explorer on Windows 2000 includes its own Java VM 1 1 4 but no Java is included in IE on Windows XP Windows 2003 and Microsoft no longer supplies a Java VM You must download and install a Sun JRE instead 2 3 4 1 SEA EVA Collections Too Big for ISEE to Send to HP The following applies to HP customer support representatives or customers who have been informed by HP customer support that their EVA collections are not being received at HP If EVA collections are not appearing at the HP ISEE server it could be because the zip file created by SEA is larger than the limit specified for ISEE You can verify this case by examining the following file C Program Files Hewlett Packard ISEE logs submitProxiedData log Look for errors similar to the following Tue Dec 27 03 20 00 UTC 0100 2005 ERROR 125484 Incident not submitted File too large c progra l hewlet 1 svctools specific wcecproxy data s500 1 zip This can occur for one of two reasons Rev 9 8 06 2 18 Web Based Enterprise Services Release Notes System Event Analyzer 2 3 SEA Known Issues 1 ISEE was installed or upgraded after WEBES was installed or upgraded By default there is a file size limit of 1 5 MB in ISEE SEA often creates zip files containing EVA collection data that ar
76. rrors 2 0020 ehem RR RRRRERSR RR HRRRUR RR EXER EEEE EEY 2 13 2 3 3 7 1 Null Pointer Errors from Large Log Piles peress s0 000scs4ee4 Rete yeh 2 13 Rev 9 8 06 vi Web Based Enterprise Services Release Notes Contents 2 3 3 8 NAVA SCHL BITODS ue io Scu ro URS REPE MUNI boas satya E IURE tapa AR 2 14 2 3 3 9 JavaScript Error When Viewing Director Settings 005 2 14 2 3 9 310 Tamie out 8886 5 ernst Rd pP RR RETIRER pP eb ROSAS SEES Res 2 14 2 3 3 11 Multiple Sessions using Mozilla and Netscape 7 000000000008 2 14 23 312 SCUVICES Fall TO Sta cisco oet roe pd Rp doe tp C up dado dug lee gradus 2 15 2 3 3 13 Multiple Java Installs May Affect Web Interface lesse 2 17 2 3 3 14 Web Interface Hangs on Startup After CommandView EVA Stops or Restarts 2 17 2 3 3 15 Old SEA Example File Names Migrated But Inaccessible 2 18 2 34 Windows SEA ISSUES uo rues TP a sob ie Som aed RUM PR dE beach E RopxU Ps PORE PURA 2 18 2 3 4 1 SEA EVA Collections Too Big for ISFE to Send to HP eese eee 2 18 2 3 4 2 Error while Entering Product Serial Number and Product Number for EVA Managed EET EEL Sea ae eorr tetto vr mee ie eR RU em E tbe Buy aaa RHE E 2 19 2 3 4 3 Microsoft HotFix Corrects Application Event Log Corruption Problem 2 19 2 3 4 4 Windows Event Log May Not Grow to Configured Size 00004 2 20 2 3 4 5 XP internet Explorer Does Not Have Java
77. rsion bundled in WEBES Stopping the WCCProxy usr sbin wccproxy line 122 10052 Segmentation fault Rev 9 8 06 Web Based Enterprise Services Release Notes 1 21 Overall WEBES Release Notes 1 6 WEBES Known Issues You can safely ignore this message There is no impact to WEBES or WCCProxy installation or operation 1 6 4 OpenVMS WEBES Issues These issues apply to WEBES on OpenVMS 1 6 4 1 Set ODS 5 Attributes Before Issuing WEBES CLI Commands The following applies only if your system disk or the disk to which you have installed WEBES is an ODS 5 disk Before issuing any WEBES CLI command desta wsea wccat or wccproxy issue the following command to assign certain ODS 5 settings required for the WEBES command to operate properly SET PROCESS CASE BLIND PARSE TRADITIONAL After completing the WEBES command you can revert to your previous settings for CASE and PARSE using the above command with different keywords To find out your current settings before changing them issue the following command partial output shown SHOW PROCESS CASE PARSE Newer ny Parse Style Traditional Case Lookup Blind This is only an example Your output may show the Sensitive or Extended keywords instead If you do not issue the above SET command and you have Case Sensitive or Parse Style Extended settings on your process WEBES CLI commands will return errors such as the following
78. s Workaround Define system PATH variable with some value not null before installing Manually add WCCProxy path to PATH after installation 1 6 2 14 Windows Itanium Installation may interrupt if PATH variable is 256 characters or longer In case of Windows Itatium if the system PATH variable is 256 characters or longer then during the WCCProxy installation an error dialog box pops up Failed to get PATH The reason behind is that post installation the PATH variables only contains WEBES path WCCProxy path is not added As a result of this WCCProxy commands like wccproxy status do not work Workaround Remove junk entries from PATH Manually add WCCProxy path to PATH after installation 1 6 3 Linux WEBES Issues These issues apply to WEBES on Red Hat Linux 1 6 3 1 Director May Require Restart If the system is configured to restart in graphical user interface mode run level 5 the desta Director may not always automatically restart For run level 5 always restart the Director manually after any type of system restart desta start Linux systems that restart in command line mode run level 3 correctly restart the desta Director automatically whenever the system restarts 1 6 3 2 Segmentation Fault Error Message If you had installed an ISEE Client containing WCCProxy 1 0 when installing WEBES you may see the following error message when the WCCProxy is stopped so that it can be replaced with the newer ve
79. services notification HTTPNotification 5 main EXCEPTION java net ConnectException Connection refused at java net PlainSocketImpl socketConnect Native Method One cause is when WEBES cannot connect to the OSEM host because OSEM Viewer access has been restricted This is a known issue from the latest OSEM release notes Workaround Any time that you restrict access by adding at least one system to the Enabled Clients list in the OSEM Viewer you also must add WEBES systems as enabled clients before problem reports from those systems can appear To add enabled clients see the controlling access section in the latest OSEM user guide To verify that OSEM is receiving SEA problem reports use the SEA wsea test nosystem command to generate a simulated problem report 2 3 2 SEA Command Line Interface Issues These issues apply to the SEA CLI on all operating systems 2 3 2 1 ca Command Changed to wsea The command prefix used with the command line interface has changed from ca to wsea In this version commands can be entered using either prefix however future releases will not support the ca prefix 2 3 2 2 Entering Commands Because of differences in the command prompts on each operating system CLI commands may not be exactly the same across systems The following instructions describe special formatting issues for each operating system Rev 9 8 06 2 8 Web Based Enterprise Services Release Notes S
80. t Not Disappearing If you are monitoring system processes you may encounter a situation where CAAgent processes are accumulating and never going away This is a known issue where each time you start and stop the Director another CAAgent process will accumulate To work around this issue stop the Director and then run the wccproxy stop command which will kill any leftover CAAgent processes Further Information See the WEBES User Guide for more details about SEA Kits updates and documentation for WEBES are available at the following URL http www hp com services webes Rev 9 8 06 2 28 Web Based Enterprise Services Release Notes System Event Analyzer 2 4 Further Information Rev 9 8 06 Web Based Enterprise Services Release Notes 2 29 3 Computer Crash Analysis Tool This chapter contains information that applies specifically to Computer Crash Analysis Tool SUIT at yi resp ote iS eiua DER MEI pix TRU PERSP eRa Re pe Oe page 3 2 Supported Products ressorteer OSM Pp ep E UE pipe eg ae edt page 3 2 CCAT Known Issues iiss i eom prb reote e DE PR Ose be ES dee babe DDeOD p 5 page 3 2 Further In OFT3tlols s occas npe dup See deri x qot qe perde ep d dts page 3 5 Rev 9 8 06 Web Based Enterprise Services Release Notes 3 1 Computer Crash Analysis Tool 3 1 Summary 3 1 Summary Computer Crash Analysis Tool CCAT is a software application that enables Hewlett Packard Customer Services engineers and system administra
81. tanium Edition Although WEBES is not yet supported on this operating system the Itanium kit may install and operate correctly but the Pentium kit can not be installed Windows Vista 32 bit Beta Edition formerly known as Longhorn Any Editions for the x64 platform See section 1 6 1 1 Installing WEBES on Unsupported Platforms for related error messages if you install WEBES on non supported platforms See the previous section 1 2 Hardware Requirements for the types of hardware that WEBES can be installed upon Although WEBES can be installed on any of these hardware and operating system combinations SEA only supports event bit to text translation and event analysis on a certain set of HP product See Section 2 2 Supported Products for the list of products that SEA supports 1 4 Test Environment This WEBES version passed QA testing when installed on the following specific test configurations Windows Windows 2000 Patched Proliant DL380 RAM 256 MB Proliant DL380 RAM 256 MB Intel Pentium III CPU 1133MHz RAM 1 GB Windows XP Patched Intel Pentium II CPU 398MHz RAM 128 MB Intel Pentium IV CPU 1 59 GHz RAM 448 MB Windows 2003 Patched Intel Pentium II CPU 398MHz RAM 192 MB Intel Pentium III CPU 549 MHz RAM 128 MB Intel Pentium IV CPU 2 79 GHz RAM 512 MB Windows 2003 Itanium 64 Bit Patched Itanium2 CPU 900MHz RAM 1GB Itanium2 CPU 733MHz RAM 1GB HP UX Rev 9 8 06 HP PA RISC 9000 889 MHz
82. ted rie SWR eae 3 4 Rev 9 8 06 Web Based Enterprise Services Release Notes vii 3 4 Further Information 1 Overall WEBES Release Notes This chapter contains information that applies to the entire WEBES suite SUMMA aaa ka EN Pace dain Hats dg VER Eq PUR RU E ENEE RS Peta pel Oe page 1 2 Hardware Requitemellts 25 93 21 29 9 9909 9p Pd Haire dht aa ee tie a pe NOH opas page 1 2 Operating System Requirements eios cbe etii te RIPE Ue ae RON Q Ue Eg page 1 3 Test EDViFonmeflt 55 2 9 3 pp EDT SL del aE meee meade QUAEQUE dU RENE aoe FO page 1 4 New it this Reledse aiite urbi LII Ut Sq Pd dv Ped iud Pedir guide page 1 5 WEBES Known ISSUES pc dp aU CEP PE edd e ptio pda eps page 1 8 Further Information 522219 ars 2 19 5 44 0 08 EH n HE e DO HEN DE oO ded page 1 27 Rev 9 8 06 Web Based Enterprise Services Release Notes 1 1 Overall WEBES Release Notes 1 4 Summary 1 1 Summary 1 2 Web Based Enterprise Services WEBES is a suite of system diagnostic tools WEBES consists of a master installation kit that allows you to install any or all of the following components System Event Analyzer SEA for remote system event monitoring Computer Crash Analysis Tool CCAT for remote operating system failure analysis In addition WEBES always installs the following background components that are required in order for the suite to function as a integrated product WEBES common components WCC WCCProxy Hard
83. this are 1 the initial automatic analysis of the entire log file for the first time after WEBES is installed requiring processing of the entire log file or 2 ifthe Director has been stopped for a long time and many events have been written to ERRLOGSYS while the Director was not running then it can take a while to process the new unprocessed events 3 manual analysis of ERRLOGSYS either using the CLI wsea ana or the SEA Web Interface Full View The threshold of how large an ERRLOGSYS file or how many events will trigger this condition varies depending on the speed and load of the VMS machine Since the Director only reads the latest file version it can lose its place at the moment the new file version is created An error message similar to the following may be logged to the Directors DESTA_DIR LOG file or in the CLI output gt gt WARNING on November 23 2005 4 19 25 AM MST 1129 661 sec elapsed gt Error retrieving event EventDescriptor CEH event gt originID 1 gt fieldNotFound false ice EXCEPTION com compaq svctools desta services JNIRoot PrivException java n et SocketException broken pipe Rev 9 8 06 Web Based Enterprise Services Release Notes 2 25 System Event Analyzer 2 3 SEA Known Issues gt at com compaq svctools desta services JNIRoot PrivInterface SendPckHdr P rivInterface java 587 gt at com compaq svctools desta services JNIRoot PrivInterfac
84. ting with WEBES 5 Check the browser configuration to ensure that it is using the new JRE you have installed See C 2 Browser Setup for the procedure to verify that Java is enabled 2 3 3 14 Web Interface Hangs on Startup After CommandView EVA Stops or Restarts If CommandView EVA CV EVA is stopped or restarted while the WEBES Director or WCCProxy is running then the WEBES SEA web interface may hang attempting to connect to CV EVA To clear this situation stop and restart both the WEBES Director and the Rev 9 8 06 Web Based Enterprise Services Release Notes 2 17 System Event Analyzer 2 3 SEA Known Issues WCCProxy This problem was fixed late in the WEBES v4 4 4 release cycle so please alert HP Customer Support if you encounter this problem 2 3 3 15 Old SEA Example File Names Migrated But Inaccessible As of WEBES v4 4 4 a new smaller set of SEA examples is provided with more descriptive names of previous examples taking up less disk space on the user s system If you have added any of the old example file names to your web interface user profile in v4 4 1 or earlier and you migrated to WEBES v4 4 4 or later those filenames will be retained and migrated in your profile but the files will no longer exist on your system It is recommended that you manually delete all of the old example file names from your user profile You can add any of the new set of examples to your user profile at any time and manual analysis will work co
85. tors to analyze operating system crashes CCAT matches information collected about a crash against a set of operating system specific rules to determine if the footprint of the collected crash data matches any known crash data footprints for which a solution or corrective action has been found Once the footprint has been created CCAT can perform the following functions automatically Email information about the crash to the system administrator or other designated local addressee Analyze the crash file and produce a results file CCAT also can be run at any time as a GUI see the CCAT User Guide for details 3 2 Supported Products CCAT can analyze crashes on the following operating systems Note that WEBES can be installed on additional operating systems such as HP UX and Linux but that CCAT does not yet analyze crashes native to those systems Microsoft Windows 2000 Windows server 2003 any edition and Windows XP Professional edition only HP OpenVMS Alpha versions 7 3 1 or higher 3 3 CCAT Known Issues The issues described in the following sections are specific to CCAT e 3 32 Windows CCAT Issues 3 3 3 OpenVMS CCAT Issues See Section 1 6 WEBES Known Issues for overall suite issues 3 3 1 General CCAT Issues The following known issues affect CCAT on Windows Rev 9 8 06 3 2 Web Based Enterprise Services Release Notes Computer Crash Analysis Tool 3 3 CCAT Known Issues 3 3 1 1 CCAT IVP File Not Fo
86. um servers Platforms Analysis and Bit To Text Translation HP Integrity Servers rx1600 rx1620 rx2600 rx2620 rx 4640 Windows Server 2003 Enterprise Edition manual analysis only no automatic and OpenVMS v8 2 and later HP Integrity Servers rx5670 zx6000 and zx2000 Windows Server 2003 Enterprise Edition manual analysis only no automatic only Rev 9 8 06 2 2 Web Based Enterprise Services Release Notes System Event Analyzer 2 2 Supported Products HP Integrity Servers rx3600 rx6600 rx7620 rx 7640 rx8620 rx8640 automatic analysis and bit to text and Integrity Superdome SD16A SD32A SD64A SD32B SD64B on Windows 2003 Server Enterprise Edition and OpenVMS 8 3 Coming soon in future SEA releases HP Integrity Servers rx7620 and rx8620 and SuperDome platforms SD16 SD32 and SD64 Windows Server 2003 Enterprise Edition manual analysis only no automatic and OpenVMS v8 2 and later HP AlphaServer DS10 DS10L DS15 DS20 DS20E DS25 OpenVMS HP AlphaServer ES40 ES45 OpenVMS HP AlphaServer GS80 GS160 GS320 OpenVMS HP AlphaServer TS80 ES47 ES80 GS 1280 GS 1280 M64 OpenVMS HP AlphaServer TS20 TS40 OpenVMS HP AlphaServer TS202C OpenVMS Memory Channel II OpenVMS Platforms Bit To Text Translation only HP AlphaServer DS20L OpenVMS I O Devices Analysis and Bit To Text Translation Disk Storage based on SCSI specification OpenVMS and Windows EZ4X EZ6X OpenVMS EZ5X EZ7X OpenVMS HS
87. und The following message that appears in the Director log shortly after installation is a known issue and expected It causes no harmful effects and the message will be removed in a future release The directory path and filename will vary by operating system but it will always end in RULES CCAT IVP CMP An example is WARNING on May 27 2004 6 10 45 AM IST 150 351 sec elapsed CCATRuleMain decrypt Q gt IOException java io FileNotFoundException usr opt hp svctools common ccat data Tru64 Unix RULES CCAT IVP CMP no such file or directory 3 3 2 Windows CCAT Issues The following known issues affect CCAT on Windows 3 3 2 1 WEBES Directory Tree Missing Or Access Denied If your user ID is not a member of the Administrators group as described in the WEBES Installation Guide you will not be able to access or see any directories or files under the WEBES directory tree by default installed to C Program Files hp svctools 3 3 2 2 CLI Commands Not Recognized If your user ID is not a member of the Administrators group as described in the WEBES Installation Guide you will not be able to execute any WEBES CLI or CCAT CLI commands You will see errors such as the following C Program Files Mhp desta status desta is not recognized as an internal or external command operable program or batch file C Program Files hp gt svctools common bin desta status Access is denied 3 3 2 3 Empty Start Menu If your user ID is not a
88. ust have a sys evt zpd Or errlog extension The text field can only be enabled for users you specify in the ca wur oLtext key It cannot be enabled for all users unless you list each user individually The list of usernames assigned to the ca wur orrexc key corresponds to the user profile entered by the user at the SEA logon screen SEA profiles and usernames are not related to the id a user enters to log onto a machine and they are not authenticated by SEA during the logon process It is therefore the responsibility of those with knowledge text entry enabled user profiles to protect them from unauthorized use i e not allowing open access to event logs anywhere on the system For more information see Section 7 7 3 in the System Event Analyzer User Guide 2 3 3 3 Node Name Change Causes Connection or Notification Failure If the network name of a system changes the change must be reflected in the web interface After a node s network name changes the old network name remains in the web interface and the connection to the node is lost This occurs even if the name change occurs on the localhost Thus for name changes on any node click on the node s group icon in the navigation tree and delete the old node name Then add the node again using the new name In addition remove the line beginning wccProxy owner from the file installed directory svctools specific wccproxy config WCCPROXY REG SO that whenever WEBES is upgraded or re
89. ware Requirements This version of WEBES can be installed on the following hardware platforms 32 bit Intel based systems manufactured by HP such as the ProLiant or the HP OpenView Storage Management Appliance Note that WEBES usually will operate on any industry standard 32 bit Intel based system However because HP does not qualify WEBES on third party products functionality on such systems is provided on an as is basis only HP Integrity systems built on the 64 bit Intel Itanium platform Note that WEBES may operate on other non HP Itanium based systems However because HP does not qualify WEBES on third party products functionality on such systems is provided on an as is basis only HP AlphaServer systems HP 9000 series systems Note This version of WEBES is NOT supported on the x64 platform such as 64 bit Xeon based systems and AMD systems based on the AMD64 Opteron Athlon or Turion 64 bit chipsets Rev 9 8 06 1 2 Web Based Enterprise Services Release Notes Overall WEBES Release Notes 1 3 Operating System Requirements See the next section 1 3 Operating System Requirements for the operating systems that WEBES can be installed upon Although WEBES can be installed on any of these hardware and operating system combinations SEA only supports event bit to text translation and event analysis on a certain set of HP products See Section 2 2 Supported Products for the list of products that SEA supports 1
90. with the following command MULTINET CONFIGURE INTERFACE NET CONFIG gt 2 Enable the MultiNet UCX driver interface with the following command NET CONFIG SET LOAD UCX DRIVER TRUE 3 Exit the configuration program with the following command NET CONFIG gt EXIT 4 Edit your system startup command procedure to invoke MultiNet before starting DECwindows 5 Reboot the system to start MultiNet with the UCX QIO driver loaded 1 6 4 4 Continuous CPU Usage After Daylight Savings Time Change On OpenVMS 7 3 and higher when the time is moved forward or back for the Daylight Savings Time adjustment multi threaded processes can go into a tight CPU loop Applications subject to this behavior include DCPS symbiont DECevent and anything using the Java runtime such as the DESTA director Stopping and restarting the processes desta stop followed by desta start corrects the problem To resolve this issue install the patch VMS73 TDF V0100 or VMS731 TDF VO0100 Otherwise the behavior will happen again at each Daylight Savings Time adjustment 1 6 4 5 New OpenVMS Patch Removal Feature During WEBES installation you may see messages similar to the following The following product has been selected DEC AXPVMS WEBES V4 2 0 Platform product suite Information has been saved to allow you to uninstall the following patches RECOVERY DATA SET 001 created 25 JUL 2003 00 06 16 52 PATCH APPLIED TO
91. ypically occurs if SEA is not installed You should now be able to restart the Director successfully on respective platforms Windows net start desta service All others desta start 2 3 3 13 Multiple Java Installs May Affect Web Interface If you independently not as part of WEBES install uninstall and reinstall different versions of the Java JDK SDK and JRE the browser may reach a state where it no longer loads the web interface correctly If SEA web pages do not load and you suspect that Java was installed multiple times you may need to follow these steps to resolve any Java conflicts that are affecting the web interface 1 Close all the Web browser windows 2 Uninstall all Java versions on the system Do not remove the Java Runtime Environment JRE that is embedded in WEBES in svctools common jre or any JRE embedded in any other products 3 Manually delete all directories left behind that contained Java directories and files This is particularly important on Windows For example if you have Sun s Java 2 Runtime Environment SE v1 4 2 10 installed at C Program FilesJavaV2rel 4 2 10 then after removing the Java product from Add Remove Programs manually delete the directory C Program FilesJavaV2rel 4 2 10 and all of its remaining contents 4 Reinstall the desired JRE See the Java Requirements in WEBES User Guide section C 1 Supported Web Browsers The latest JRE from Sun should always work for browsers communica
92. ystem Event Analyzer 2 3 SEA Known Issues Windows When you are entering paths in the CLI on a Windows system you must pay special attention to any space characters If you specify a path that contains spaces it must be wrapped in double quotes However the Windows shells do not expand path wildcards wrapped with double quotes For example C Program Files someDirectory zpd does not expand to all the zpd files in the directory C Program Files someDirectory To avoid this problem change to a directory in which you do not have to use double quotes and execute the command For instance in the example do either of the following C gt ed C Program Files C gt wsea trans input someDirectory zpd or C gt ed C Program Files someDirectory C gt wsea trans input zpd Windows On Windows systems commands that contain an argument with a comma must enclose the argument in quotation marks If the argument is not in quotation marks Java does not interpret the comma and you may receive undesired results The exact placement of the quotation marks is not critical and both of the following examples show valid commands wsea n ana index s 1 e 1 wsea n ana index s 1 e 1 When you are entering commands be aware that Windows does not require a second double quote around parameters since it automatically completes the set of quotes Thus if you enter the following command C gt wsea trans input C

HP Web-Based Enterprise Services 4.5 User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents