Updated: Oct 5, 2005 OVO 7.5 Architecture Instrumentation Common Features
This matrix shows OVO for Windows 7.5
1. Supported Agent Platforms 2. Supported Management Server Platforms 3. Supported Console Platforms 4. Supported Web Console Platforms 5. Supported Databases 6. Solution Integrations 7. High Availability Support Matrix 8. SPI Integrations / Gallery SPIs 9. Windows Terminal Server and Citrix MetaFrame 10. VMWare and MS Virtual Server 11. Miscellanous Notes
Attention: For orange entries please contact Technical Marketing ([email protected]) for verification Please check the SPI support matrix for information what platforms are supported with the SPIs including the OS SPIs - this matrix only shows the platforms for the foundation
Legal Notices
Warranty
Hewlett-Packard makes no warranty of any kind with regard to this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Copyright Notices
©Copyright 2005 Hewlett-Packard Development Company, L.P., all rights reserved. No part of this document may be copied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this material is subject to change without notice.
Trademark Notices
HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. Intel386, Intel80386, Intel486, and Intel80486 are U.S. trademarks of Intel Corporation. Intel Itanium ™ Logo: Intel, Intel Inside and Itanium are trademarks or registered trademarks of Intel Corporation in the U.S. and other countries and are used under license. Java™ is a U.S. trademark of Sun Microsystems, Inc. Microsoft™ is a U.S. registered trademark of Microsoft Corporation. MS-DOS™ is a U.S. registered trademark of Microsoft Corporation. Netscape™ and Netscape Navigator are U.S. trademarks of Netscape Communications Corporation. OpenView™ is a registered U.S. trademark of Hewlett-Packard Company. Oracle™ is a registered U.S. trademark of Oracle Corporation, Redwood City, California. OSF, OSF/1, OSF/Motif, Motif, and Open Software Foundation are trademarks of the Open Software Foundation in the U.S. and other countries. Pentium™ is a U.S. registered trademark of Intel Corporation. SQL*Plus™ is a registered U.S. trademark of Oracle Corporation, Redwood City, California. UNIX™ is a registered trademark of the Open Group. Windows NT™ is a U.S. registered trademark of Microsoft Corporation. Windows™ and MS Windows™ are U.S. registered trademarks of Microsoft Corporation. All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.
Naming Conventions a) 'X' = Platform supported b) 'SP' = Service Pack c) OVOW_xxxxx = OVO for Windows patch number (or newer) xx, xxx = OVO for Windows patch number (or newer) d) OVR_xxxxx = Reporter patch number (or newer) e) xxx(yy, zz) = OVO for Windows patch number OVOW_00xxx (or newer) f) SD_xxxxx = Service Desk Service Pack number For detailed patch info check the hp OpenView software patches webpage: http://support.openview.hp.com/patches/patch_index.jsp Processors x86 - Intel x86 (=IA-32), and x64 processors (Xeon EM64T, AMD Opteron etc.) running a 32-bit OS version x64 - AMD Opteron, Intel Xeon EM64T etc. running a 64-bit OS IA-64 - Itanium architecture running a 64 bit OS PA-RISC - HP PA-RISC architecture power3-5: IBM power3, power4 and power 5 Note: If 64 bit OS is supported, corresponding 32 bit OS versions are implicitly supported
Visibility ESP Keyword: SUPMTRX Access to the HP OpenView Support Matrix: For HP Internal: http://ovsdweb.cnd.hp.com/ovchannel/matrix.htm http://ovbu.fc.hp.com/ovchannel/matrix.htm For HP Channel Partner: http://partners.openview.hp.com/contact/partner_how/index.html For HP Customers: http://support.openview.hp.com/tech_docs/ovo-win/OVOWSuppMatrix.pdf
Hint: To blind in / out a grouped section of this document use the + / - signs on the left side and on top of this document.
1. Supported Agent Platforms
G3 Version Directory Architecture OVO for Windows 7.5 Common Features for Instrumentation G1 G4 Operating Japanese Versions English
OS Korean
System Agent S-Chinese Manual Discovery Processor Embedded Installation Interception Comm Type SNMP Event Performance Component
Windows and Linux NT 4.0 Workstation/Srv/EntprEd. W6 Windows NT\4.0 32 32 x86 SP6A G2 SP6A G2 DCE X X X X 2000, all editions Windows 2000\5.0 32 32 x86 SP1, 2 W2, 3, 4W5 SP1, 2 W2, 3, 4W5 DCE X X X X Server 2003, all editions Windows Server 2003\5.2 64 32 IA-64 X, SP1 X, SP1 DCE X X X X Windows W1, W4 Server 2003, all editions Windows Server 2003\5.2 64 32 x64 OVOW_00194 OVOW_00194 DCE X X X X Storage Server 2003 on Windows Server 2003\5.2 32 32 x86 X X DCE X X X X HP ProLiant Storage Servers W7 XP Prof Windows XP\5.1 32 32 x86 X, SP1, SP2 X, SP1, SP2 DCE X X SP1W3 X
Notes for Windows W1 See chapter 9, "Windows Terminal Services and Citrix MetaFrame" for more details W2 MS hotfix Q306274 that addresses a WMI problem is required for W2K SP2 W3 Windows XP SP1 required for SNMP trap interception and MIB monitoring W4 MS Hotfixes: HP endeavors to stay abreast of changes in the Microsoft ecosystem. HP has no prior knowledge of when Microsoft will choose to release a hotfix for one of its products. In the event that Microsoft does release a hotfix that has implications for an HP OpenView product, HP commits to investigating the impact of the hotfix, and if necessary provide a patch for the affected HP product to retain its intended functionality. W5 Microsoft has introcuced a new security setting in the local security policy or group policy that restricts the ability of a user to impersonate another user. The new setting, SeImpersonatePrivilege, is introduced in Windows 2000 Service Pack 4. See Microsoft KB at http://support.microsoft.com/default.aspx?kbid=821546 for more information. This change will impact the OpenView agent process if the agent is running as a non-administrative user, or if the SeImpersonatePrivilege is removed from the Local Administrators group or SYSTEM account on a managed node. If this privilige is removed, Tools/Actions/Policies impersonating other users will not run correctly. Using default MS security settings with SP4 (where SeImpersonatePrivilege is granted to Administrators and SYSTEM) will have no impact on the OpenView agent running as system or HP ITO Account. However, if the security policies in the environment removes the SeImpersonatePrivilege from the agent's identity (LocalSystem or HP ITO Account), Tools/Actions/Policies will fail with access denied errors. To resolve this, you must either use the default SeImpersonatePrivilege granted to Local Administrators and System, or explicity GRANT the privilege to the user that the OpenView agent runs as. Note: It would be highly unusual to remove the SeImpersonatePrivilege from the SYSTEM account, so running the agents as SYSTEM remains the preferred identity for the agent. In the case the privilege is removed from SYSTEM, the agent should be configured to run as a user account with the privilege granted to it. W6 The OVO agent on NT 4 is supported, however if a problem is found that is related to the OS, the customer needs an NT 4 extended support contract, and needs to contact Microsoft directly (not HP) to get the problem fixed. W7 HP ProLiant DL100 - DL580 G2 Storage Server (formerly HP NAS Systems 1200s - 9000s) systems are supported See http://h18006.www1.hp.com/storage/nastostorageservermatrix.html for a mapping to the new names. Remote deployment requires the "Remote Registry" service for the agent on HP ProLiant Storage servers be running. Note, per default this service is set to "Manual" instead of "Automatic" on any NAS* system.
6.4 (2.2.x | x>=14) LINUX\SuSE 6.X 32 32 x86 7.0 (2.2.x | x>=16) LINUX\SuSE 7.X 32 32 x86 X G2 DCE X X X 7.1 (2.2.x | x>=18, 2.4.x | x>=0) LINUX\SuSE 7.X 32 32 x86 7.2 (2.4.x | x>=4) LINUX\SuSE 7.X 32 32 x86 X G2 DCE X X X G2 SuSE Linux 7.3 (2.4.x | x>=10) LINUX\SuSE 7.X 32 32 x86 X DCE X X X 8.0 (2.4.x | x>=18) LINUX\SuSE 8.X 32 32 x86 X G2 DCE X X X 8.1 (2.4.x | x>=19) LINUX\SuSE 8.X 32 32 x86 X DCE X X X 9.0 (2.4) LINUX\SuSE 9.X 32 32 x86 X DCE X X X 9.1 (2.6) LINUX\SuSE 9.X 32 32 x86 X DCE X X X 9.2 LINUX\SuSE 9.X 32 32 x86 187 DCE 176 198 X 32 32 x86 X DCE X X X 8.0 (2.4) LINUX\SuSE Server 8 64 32 IA-64 L4 X DCE X 192 X SuSE Linux 64 32 x64 187+192 DCE X 192 X Enterprise Server 32 32 x86 X DCE X X X 9.0 (2.6) LINUX\SuSE Server 9 64 32 IA-64 L4 X DCE X 192 X 64 32 x64 187+192 DCE X 192 X
6.2/J (2.2.x | x>=14) LINUX\Red Hat 6.X 32 32 x86 X G2 X G2 DCE X X X 7.0 / 7.0.1J (2.2.x | x>=16) LINUX\Red Hat 7.X 32 32 x86 X G2 X G2 DCE X X X 7.1 (2.4.x | x>=2) LINUX\Red Hat 7.X 32 32 x86 X G2 X G2 DCE X X X RedHat Linux 7.2 (2.4.x | x>=7) LINUX\Red Hat 7.X 32 32 x86 X G2 X G2 DCE X X X 7.3 (2.4.x | x>=18) LINUX\Red Hat 7.X 32 32 x86 X G2 X G2 DCE X X X 8.0 (2.4.x | x>=18) LINUX\Red Hat 8.X 32 32 x86 X G2 X G2 DCE X X X 9.0 (2.4) LINUX\Red Hat 9.X 32 32 x86 X G2 X G2 DCE X X X 32 32 x86 X X DCE X X X WS/AS/ES 2.1 (2.4) LINUX\Red Hat EL 2.1 64 32 IA-64 187+192 187+192 DCE X 192 X RedHat Enterprise 32 32 x86 X X DCE X X X L5 LINUX\Red Hat EL 3.0 L5 32 IA-64 L6 L6 DCE X 192 X Linux WS/AS/ES 3.0 (2.4) 64 X X 64 L5 32 x64 187+192 187+192 DCE X 192 X 32 32 x86 WS/AS/ES 4.0 LINUX\Red Hat EL 4.0 187+192 187+192 DCE X 192 X 64 32 x64
3.0 (2.4.x | x>=18) LINUX\Debian 3.X 32 32 x86 X DCE X X X Debian Linux 3.0r2 (2.4) LINUX\Debian 3.X 32 32 x86 X DCE X X X
9.2 (2.4) LINUX\Mandrake 9.X 32 32 x86 X G2 X G2 DCE X X X Mandrake Linux L3 10 (2.6) LINUX\Mandrake 10.X 32 32 x86 X X DCE X X X
Linux Miracle 3.0 LINUX\Miracle v3.0 32 32 x86 X X DCE X
6.1J (2.2.x | x>=15) LINUX\Turbo 6.X 32 32 x86 X G2 DCE X X X G2 Turbo Linux 6.5J (2.2.x | x>=??) LINUX\Turbo 6.X 32 32 x86 X DCE X X X 7.0J (2.4.x | x>=5) LINUX\Turbo 7.X 32 32 x86 X G2 DCE X X X 8.0J (2.4) LINUX\Turbo 8.X 32 32 x86 X DCE X X X Turbo Linux Ent. Server 8.0J (2.4) LINUX\Turbo 8.X 32 32 x86 X DCE X X X
Notes for Linux For all Linux OS: Only kernel versions (in brackets()) by original distribution for the requested OS are supported L1 Problem Symptom: The deployment of some policies using certain Japanese characters might fail on RH 6.2J/7.0J with the following error message: cannot read template file. Problem Reason: On RH 6.2J and 7.0J we are experiencing problems with certain character conversions, due to a problem in the iconv function embedded in the OS. Problem Resolution: As RedHat officially has obsoleted those versions, there is no possibility for HP to fix this problem or get any patch from RedHat to resolve this issue. The only policy affected by this problem which is shipping with OVO/Win 7.2 and its SPIs is "OvSvcDiscErrorLog_jp". As a workaround you can either use the English equivalent "OvSvcDiscErrorLog" or you will need to update to RH 7.1J or higher L2 L3 Mandrake Linux node platform type and operating system are not automatically discovered and will show up as "Other". Must be set manually prior to agent deployment L4 The following symbolic links are required to support IA-64: cd /opt/OV/jre/bin ; ln -s i386 ia64; cd /opt/OV/jre/lib ; ln -s i386 ia64 L5 For RedHat, RedHat EL 3 Update 2 is required, see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=111716 It is recommended to install Linux kernel 2.4.21-32.6 that solves the kernel panic problem on RHEL 3 (U3 and U4) on IA64. (The problem was diagnosed with kernels 2.4.18-e.47, e.52 and e.56, also > e.47). L6 RHEL 3.0 IA-64 U3 and U4 also require patch OVOW_00187.
5.0 32 32 x86 X 5.1 32 32 x86 X Novell NetWare N1 N/A 6.0 32 32 x86 X 6.5 32 32 x86 X N2
Notes for Novell N1 Proxy monitoring only N2 NLMs will still report version 6.0, but is supported to run on Netware 6.5
HP 11.0 H2 HPUX\B.11.00 32 32 PA-RISC X G2 X G2 DCE X X X X 11.11 (11i v1.0) HPUX\B.11.11 32 32 PA-RISC X X DCE X X X X HP-UX 11.22 (11i v1.6) HPUX\B.11.22 64 32 PA-RISC H1 X G2 X G2 DCE X X X X 11.23, 11.23 PI (11i v2.0) HPUX\B.11.23 64 32 IA-64 H1 X X DCE X X X X 11.23 PI HPUX\B.11.23 PI 64 32 PA-RISC H1 X X DCE X X X X
Notes for HP-UX H1 IA-64 is supported, OVO agent is compiled as a native 32 bit application on an IA system. File size limitations apply on 64 bit. H2 EOS (End-Of-Support) for HP-UX 11.0 is Dec 2006
4.0F Tru64\4.0F 32 32 alpha X G2 X G2 DCET2 X X X 4.0G Tru64\4.0G 32 32 alpha X G2 X G2 DCET2 X X X 5.0A Tru64\5.0A 32 32 alpha X G2 X G2 DCET2 X X X Tru64 UNIX T1 5.1 Tru64\5.1 32 32 alpha X G2 X G2 DCET2 X X X 5.1A Tru64\5.1A 32 32 alpha X X DCET2 X X X 5.1B Tru64\5.1B 32 32 alpha X X DCET2 X X X
Notes for Tru64 T1 DCE Base library has to be purchased separately. In case of Tru64 version 5.10, DCE RPC runtime has to be purchased from Entegrity solutions Inc. (former Gradient) T2 Supported DCE versions for Tru64: Tru64 4.0F / 4.0G DCE 2.x, x>1; DCE 3.0 Tru64 5.0A DCE 4.0 (Maintenance) Tru64 5.1 DCE 4.1.x, x<4 (by Entegrity) Tru64 5.1A DCE 4.2.x (by Compaq) Tru64 5.1B DCE 4.3 (by Compaq?)
7.3-1 O1 OpenVMS\V7.3-1 32 32 alpha X G2, O4 DCE x O2 X OpenVMS 7.3-2 OpenVMS\V7.3-2 32 32 alpha X O4 DCE39 x O2 X 8.2, 8.2-1, E8.2 OpenVMS\V8.2 O3 64 32 IA-64 X O4 DCE39 x O2 X
Notes for OpenVMS O1 For OpenVMS Alpha 7.3-1: Patches VMS731_UPDATE V2.0 or later, VMS731_PCSI V1.0 or later, DCE_030SSRT3608 V1.0 required O2 Performance Management capabilities are available via the OpenVMS SPI, not via the Embedded Performance Component O3 Version string differs per architecture: 32 bit is "OpenVMS\V8.2", 64 bit is "OpenVMS (itanium)\V8.2" O4 Not supported with the OVOW 7.5 Limited Edition
SUN 2.6 Solaris\2.6 32 32 sparc X G2 X G2 DCE X X X X 7 Solaris\7 32 32 sparc X X DCE X X X X Solaris 8 Solaris\8 32 32 sparc X X DCE X X X X 9 Solaris\9 32 32 sparc X X DCE X X X X 10 Solaris\10 32 32 sparc X S1 X S1 DCE X X X X
Notes for SUN S1 Official support statement for the OS SPI on Solaris 10 expected shortly
IBM 4.3.1 AIX\4.3.1 32 32 power3-5 X G2 X G2 DCE A2 X X X X 4.3.2 AIX\4.3.2 32 32 power3-5 X G2 X G2 DCE A2 X X X X A1 G2 G2 A2 AIX 4.3.3 AIX\4.3.3 32 32 power3-5 X X DCE X X X X 5L (5.1) AIX\5L 5.1 64 32 power3-5 X X DCE A2 X X X X 5L (5.2) AIX\5L 5.2 64 32 power3-5 X X DCE A2 X X X X 5L (5.3) A4 AIX\5L 5.3 64 32 power3-5 X X DCE A2 X X X X
Notes for AIX A1 DCE Base library has to be purchased separately, list price $150 per client for AIX. A2 Supported DCE versions: 2.1, 3.1, 3.2. Support for (Dascom) DCE 3.2 extended up to 04/30/2006 IBM AIX DCE versions can be purchased and patches downloaded from the following location: http://www-306.ibm.com/software/network/dce/support/ A3 A4 Official support statement for the OS SPI on AIX 5.3 expected shortly
2. Supported Management Server Platforms
Architecture OVO for Windows 7.5
Operating Japanese Versions English Korean System OS Server S-Chinese Processor
G2 G2, W5 G2 G2, W5 W1, W4 2000 Srvr./Adv./DC Ed. 32 32 x86 SP3 , SP4 SP3 , SP4 Windows Server 2003, Std./Ent./DC Ed. 32 32 x86 X, SP1 C1 X, SP1 C1
Notes for Management Server W1, W4, W5 See notes for Windows agent C1 See notes for Console
3. Supported Console Platforms
Architecture OVO for Windows 7.5
Operating Japanese Versions English Korean System OS
Console S-Chinese Processor
2000 Prof / Server 32 32 x86 SP3 G2, SP4 G2, W5 SP3 G2, SP4 G2, W5 W1, W4 Windows Server 2003, all Ed. 32 32 x86 X, SP1 C1 X, SP1 C1 XP Prof. 32 32 x86 X, SP1, SP2 C1 X, SP1, SP2 C1
Notes for Console W1, W4, W5 See notes for Windows agent C1 Please apply updated instructions in Firewall WP version 2.6 or later, chapter 6.1.1 "Using the console on systems with enabled Windows firewall (WF)" Note, the most recent version of the Firewall WP can be downloaded from http://ovweb.external.hp.com/lpe/doc_serv. Select product: "Operations for Windows", versions: "a.07.21" or "a.07.50"
4. Supported Web Console Platforms
Webbrowser VERSIONS OVO for Windows 7.5 5.5 G2 Internet Explorer X 6.* X Netscape 7.1 or later X Mozilla 1.5 or later X
5. Supported Databases
Database D2 Architecture OVO for Windows 7.5 MSDE / 2000 (embedded) D1 32 32 x86 SP3a G2, SP4 D3 Microsoft ® SQL Server 2000 D1 32 32 x86 SP3, SP3a, SP4 D3
Notes for Database D1 Support for MSDE 2000 and Microsoft SQL Server 2000 will end by 2007. D2 See also notes for Windows Agent Platform D3 The upgrade to Service Pack 4 will change the start type of the SQLAgent$OVOPS service from Automatic to Manual. To correct this problem, logon to the server again and launch Administrative Tools --> Services. Pick service SQLAgent$OVOPS and set its startup type back to Automatic and start the service. 6. Solution Integrations
OVO for Windows 7.5 I4
Solution Versions English Japanese, etc.
Reporter I1 3.6 X X I2
I7 I10 I10 I3,9 7.01 X X NNM/ Windows I12 7.5 X X
SIP 3.2 X I13 X I13
4.x X X OVPM 5.0 X X
3.x X X OVPA I6 4.0 X X
5.2 X I13 X I2, I13 Internet Services 6.0 X I14 6.01 I15
I5 Service Desk 4.5 SD_12, 13 I11 SD_12, 13 I11
7.10 X X OVO/U I8 8.0 X X 8.10 X X
Notes for Solution Integrations I1 Supporting Crystal version 8.5 I2 Includes some set of reports, that only operate under English or European locales I3 When NNM on XP is used, the OVO agent must be deployed prior to the NNM adapter installation I4 Warning: Not all solution products are supported on Windows 2003 I5 OVO for Windows - SD integration needs special setup to avoid JRE problems. The SD agent startup has to be configured to use the path of the JRE 1.3 version. See workaround described in NSMbb62896 for more details. Support for clustered OVOW 7.5 installations require SD SP16 (expected Oct 15, 2005). I6 Graphing of OVPA data is only supported with OVPM I7 Both NNM Starter and NNM Advanced Editions are supported I8 Bi-directional message synchronization requires OVO for Windows 7.50 I9 Please follow instructions in Firewall WP ver 2.3, chapter 6.5.1 "Using the NNM Adapter on systems with enabled Windows firewall (WF)" QXCR1000219581: If NNM is installed on top of OVO for Windows, remove the right "Everyone->Full Control" from the installation directory and all subfolders. After installing NNM and OVO for Windows on the same system, add read and write permissions on the installation directory for the "IUSR_
7. High Availability Support Matrix a) agent = agent runs on each physical node in the cluster b) aware = agent runs on each physical node in the cluster, and is cluster aware in terms of enabling/disabling monitoring of the HA application c) server = management server runs as on MSCS as a high-availability resource group
Architecture OVO for Windows 7.5 Common Features
agent / aware/
Cluster Version supported OS G1 OS
OVO server Manual Discovery Processor Embedded Installation Component Component Interception Comm Type SNMP Event Performance 10.10+ 32 32 PA-RISC aware HP-UX 10.20 MC/ SG MC/ SG 11.12 32 32 PA-RISC aware HP-UX 11.0/11.11 11.16 64 32 PA-RISC, IA-64 aware HP-UX 11.23 PI OVOW_00172
2.2 E3 32 32 sparc aware Solaris 2.6/ 7 Suncluster E4 3.0 32 32 sparc aware Solaris 8/ 9
1.3.0 32 32 sparc aware Solaris 2.6/ 7/ 8 VCS E5 2 32 32 sparc aware Solaris 7/ 8 3.5 32 32 sparc aware Solaris 7/ 8/ 9
4.2.2 32 32 power3-5 agent AIX 4.3.1 - 4.3.3 HACMP 4.3.1 32 32 power3-5 agent AIX 4.3.1 - 4.3.3 4.4.1 32 32 power3-5 agent AIX 5L 5.1/5.2
TruCluster TruCluster 32 32 alpha agent E2 5.1/ 5.1A/5.1B
NT Cluster Server 32 32 x86 aware Server / Enterp. Ed. Microsoft Clusters W4 2k Cluster Service 32 32 x86 aware Adv Server / DC Srv Windows 2003 Cluster Service 64 32 IA-64 E1 aware, server E6, Ent. Srvr, DC Srv
Notes for High Availability Support W4 See notes for Windows agent E1 Only agent is certified on IA-64 clusters, no support for management server E2 Cluster awareness can be enabled using instructions in online help. No coexistence of OVO agent versions 7.* with other OpenView products that are based on L-Core E3 Volume Managers: Veritas 3.0.2 E4 Volume Managers: Veritas 3.1.1 E5 Volume Managers version: >=3.0.4 E6 Windows 2003 SP1 is certified on IA-64 only with OVO Agent 7.30/7.31. Needed patch for OVOW 7.5 is OVOW_00186.
8. SPI Integrations / Gallery SPIs
Architecture OVO for Windows 7.5 See SPI matrix for SPI Version numbers as per SPI more details CD 2005.1
Foundation SPI English Japanese, etc.
SPI for MS Windows B.08.75 B.08.75 (J/C/K) SPI for Unix OS B.03.15 B.03.15 (J) SPI for Web Services B.04.31 B.04.31 P2 NDAOM - Integr. with PD of NNM B.02.00 B.02.00 P2
SPI Integration SPI for Microsoft Exchange (Server) B.09.00 B.09.00 SPI for Microsoft SQL (Server) B.09.01 B.09.01 SPI for Microsoft Enterprise Servers B.04.51 B.04.51 SPI for Microsoft AD B.03.10 B.03.10 SPI for Microsoft Virtual Server B.01.00 B.01.00 SPI for SAP B.09.01 B.09.01? SPI for BEA Tuxedo B.02.55 SPI for BEA WebLogic B.04.01 B.04.01 SPI for IBM WebSphere 4.0 B.04.01 B.04.01 SPI for IBM DB2 B.02.10 SPI for Remedy B.01.10 SPI for PeopleSoft B.02.20 SPI for Oracle B.09.01 B.09.01 SPI for Informix B.09.01 SPI for Sybase B.09.01
Gallery SPIs SPI for BEA WebLogic 1.0 SPI for Checkpoint FireWall-1 1.0
Other HP SPIs SPI for Storage Area Manager SPI for HP NonStop Server - OVNM - OV NonStop Management X SPI for DP 5.0, 5.1
Third Party SPIs SPI for AS/400 (Eview) X SPI for VMware (nWorks) P1 1.75 SPI for Lotus Notes (nWorks) X ESQ: Managing Tandem nonstop systems X SPI for Citrix MetaFrame XP (HSL) B.01.10 SPI for OpenVMS (AppMind) X SPI for Siebel (HSL) X OVNM: OpenView NonStop Server Management 3.1, 3.2 3.1, 3.2
Notes for SPI Integrations P1 Support for VMware ESX server 2.x P2 SPI works in Japanese etc. environments (=internationalized), but is not localized.
9. Windows Terminal Server and Citrix MetaFrame
OVO for Windows will support Windows Terminal Services (TS) under the conditions stated below: NOTE: This statement is only valid for the original Windows TS shipped with Windows 2000 (SP1 or later) and 2003. Windows 2000 TS will be supported for use with OpenView operations for Windows 7.* and newer. Windows 2003 TS will be supported for use with OpenView operations for Windows 7.21 and newer. Troubleshooting: When troubleshooting an OVO/W console issue that may be related to Windows Terminal Server, please verify the matter without running TS prior to contacting OV support or CPE teams. OV support will try to solve issues that ONLY occur when TS is used as well, but if the problem is caused by TS, then OV support might not be able to provide a fix for it, as this lies in the responsibility of Microsoft. TS remote administration mode: Operating the console: We support Windows Terminal Services in remote administration mode, which limits users to 2 concurrent sessions, with the following hardware: Management Server: PC with dual / multi 800 MHz Intel Pentium III (or compatible) processor, 768MB RAM, at least 20GB Disk, CD-ROM drive, dedicated system that is not a domain controller. Installing other OV components: Agent is supported in TS remote administration mode (both Windows 2000 TS and Windows 2003 TS). The Management server and the remote console may be installed via a Windows Terminal Services session in remote administration mode, but setup.exe has to be started from the local file system on the target server (not from the CD). SPIs and patches cannot be installed via a Windows Terminal Services session in remote administration mode - they have to be installed using a normal login on the management server directly. TS application mode: Operating the console: Operating the console on Windows Terminal Services in application mode (max. 8 concurrent sessions) is supported. In addition to the remote administration mode HW requirements, 48 MB physical and 64 MB virtual memory must be added for each connected terminal service user. Installing the OVO agent is supported: - if Windows 2003 Terminal Services is used (for Windows 2000 TS - only remote admin mode is supported) - if the manual agent is version 7.20 or newer - if the management server is version 7.20 or newer - if the installation source is available locally (local CD or hard disk), and not from a share - if the TS install mode is selected (e.g. change user /install) - installation does not work with the manual agent InstallShield wrapper "setup.exe" - installation works if the agent is installed via "Add New Programs->Floppy or CD" or by executing the following msi packages directly: (A) msiexec.exe /I "isscript.msi" (B) msiexec.exe /I "HP OpenView Operations for Windows Agent A.07.20.msi" /qn (for newer agents adapt the version number) Installing other OV components version 7.20 or older OVO/W management server, console, SPI components and patches CANNOT be installed if TS is running in application mode. Therefore, - all OVO/W and SPI components, including patches, have to be installed prior to installing Terminal Services in application mode or - TS has to be temporarily switched back to remote administration mode in order to install OVO for Windows, NNM Adapter, Adapter, SPIs or patches. See installation notes for remote administration mode above.
OVO for Windows 7.21 or newer will support Citrix MetaFrame XP Presentation Server 3.0 (short: Citrix MetaFrame XP or MetaFrame Server) under the conditions stated below: One of the following MetaFrame product families is used: - Citrix MetaFrame XPs (Feature Pack 3 or newer ) - Citrix MetaFrame XPa (Feature Pack 3 or newer ) - Citrix MetaFrame XPe (Feature Pack 3 or newer ) The MetaFrame Server is installed on: - Windows 2000 Server operating system (Server, Advanced Server or Datacenter Server) at Service Pack 3 or newer or - Windows Server 2003 (Standard Server, Enterprise Server or Datacenter Server). OpenView Operations MMC console and/or the Web consoles have been installed and configured as published applications according to the instructions in the respective Citrix MetaFrame Administrator’s Guide. Remote Access to the OpenView Operations console on the MetaFrame Server is only supported via the Citrix ICA clients. HP has tested a maximum of 8 concurrent remote sessions connected from one Citrix MetaFrame server to an OpenView Operations Management Server. There is no specific physical limitation to the number of concurrent remote session connections; however, until further performance testing is completed, HP will only support 8 concurrent connected sessions per server. The following use cases are not supported: - Access via the MetaFrame Web Interface - Automatic installation of the OpenView Operations MMC or Web console as application package using the MetaFrame Installation Manager Troubleshooting: When troubleshooting an OpenView Operations console issue that may be related to MetaFrame, please verify the matter on a console not running on MetaFrame prior to contacting the OVEC or CPE teams. OV support will try to solve issues that ONLY occur when MetaFrame is used as well, but if the problem is caused by MetaFrame, then OV support might not be able to provide a fix for it, as this lies in the responsibility of Citrix.
10. VMWare and Virtual Server
VMWare is supported with OVO/W 7.10 and newer for the (Windows and Linux) agent, management server and remote console, if potential problems can be reproduced outside of VMWare. Note, running the OVO/W management server as VMware session is not recommended other than in demo environments as it will compete for CPU and memory resources against other virtual machines and the host system itself. Supported are the following versions of VMWare guest systems, not host systems: VMWare workstation 2.x, 3.x and 4.x, VMWare GSX server 2.5.x and 3.x, VMWare ESX server 1.5.x and 2.x (latest release is 2.01)
Microsoft ® Virtual Server 2005 is supported with OVO/W 7.10 and newer for the (Windows and Linux) agent, management server and remote console, if potential problems can be reproduced outside of Virtual Server. Note, running the OVO/W management server as Virtual Server session is not recommended other than in demo environments
11. Miscellaneous Notes
(G1) For 64bit OS running a 32bit agent, the embedded performance component reports wrong values for gbl_machine & gbl_machine_model. (G2) Discontinued with next release (e.g. OVO for Windows 8.0) (G3) Full path name of instrumentation directory is "...\Program Files\HP OpenView\Instrumentation\" followed by the contents of this column (G4) If an English message is sent to both an English and a Japanese node the message is properly displayed on both nodes. If a Japanese message is sent to both an English and a Japanese node the message does not properly display on the English node. Problem is related to the English node running under the English system locale. Problem can be reproduced by sending a Japanese message via the Win OS SPI tools "net send