Patch Name: PHSS_17234 Patch Description: s700_800 10.X OV ITO4.0X NetWare Agent Patch Creation Date: 99/02/10 Post Date: 99/03/09 Hardware Platforms - OS Releases: s700: 10.00 10.01 10.10 10.20 s800: 10.00 10.01 10.10 10.20 Products: OpenView IT/Operations 4.0 Filesets: OVOPC-CLT-ENG.OVOPC-NW-CLT Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_17234 Symptoms: PHSS_17234: - error messages can cause abend (crash) of a NetWare server - better support for maintenance mode - improved queue repair algorithm - support for SNMP communities other than PUBLIC - long usernames supported during installation - resources cleanup PHSS_14181: - NDS (Netware Directory Services) support - Installation supports Novell Netware 4.11 (AKA Intranetware) for depot server PHSS_13382: - The ITO Agent was not installable on Novell SFT III systems. Defect Description: PHSS_17234: 1) Error messages can cause the NetWare server to ------------------------------------------------- abend (crash) ------------- The error messages issued by ITO agents might cause the Novell server to abend. A bug was found in the code, and was fixed. The reason for the abend was an invalid local semaphore handle that was passed to kernel. Resolution: Unique mutex (which contained the local semaphore) is now used throughout the NLM. 2) Better support for maintenance mode ---------------------------------------------------- In the original implementation, upon startup, Control Agent would send an RPC to Management Server, informing it that the software has been installed and that the agents are running. Since this can interfere with maintenance procedures on Management Server, the initial RPC call was removed. As a consequence, an additional step is required after the initial installation of ITO agents. Upon installation, the following commands must be executed on Management Server in order to update the OV database: opcsw -installed Resolution: Initial RPC call to Management Server was removed during startup of the Control Agent. 3) Improved queue repair algorithms ----------------------------------- Algorithms for queue repair have been improved to reduce the chance of agent aborting when the queue file is corrupted. Resolution: Queue header was fixed on disk, but was not read back to memory. Now that has been fixed. 4) Support for other SNMP communities other than PUBLIC ------------------------------------------------------- By default, ITO agents allowed monitoring and using only public SNMP community. Several customers found this constraining, so the code was enhanced to allow for usage of other SNMP communities. The selection of SNMP community is done by setting the value of the SNMP_COMMUNITY variable in OPCINFO file. For example, if the required community is XYZ, the following line should be entered in OPCINFO file: SNMP_COMMUNITY XYZ After restarting the agents, all actions and monitoring, done by Action and/or Monitor Agent, will be done under the SNMP community XYZ. Resolution: VENDOR.NLM, Action and Monitor Agent have been enhanced as to accept SNMP communities different than PUBLIC. 5) Long usernames allowed during installation --------------------------------------------- Usernames up to 240 characters in length can now be used when installing ITO Agents on NetWare server. Resolution: Extended the legth of the Username: field in login object. 6) Resources cleanup -------------------- ITO Agents will no longer leave file and network semaphore handles open when they exit. No warning messages concerning handles will be displayed on the console any more. Also, a significant amount of memory resources has been released, although it is still possible to get warning messages about unreleased memory on the console. This memory is then released by the operating system. Resolution: Closed all opened files and network semaphores in Control, Message and Monitor Agent, as well as Logfile Encapsulator. PHSS_14181: 1) Introduction to NDS ---------------------- NDS (NetWare Directory Services) is a directory or naming service that was introduced with Novell NetWare 4.0. NDS maintains a database of all network resources. This database is called the NetWare Directory (or just Directory for short). NetWare 4.x creates a single, unified network by providing a single point for accessing and managing most of the network resources that are stored in NetWare Directory. User does not need to know on what network server resides a particular network resource. The request to use some resource is simply done by using unique name for it from NetWare Directory. Directory can be partitioned and replicated on multiple servers. It's internal structure is based on distributed database technology and is rather complicated. For an user the Directory represents hierarchical database in the form of the tree that contains all network objects - file servers, users, print servers, groups and so on. One of the greatest advantages of NDS is possibility to login to Directory only once to get access to various file servers - based on privileges and rights. With pre-4.x version user had to login to every file server to access it's file system. In NDS mode user has to provide the login process with it's unique name that is stored in Directory. Let's take a closer look at hypothetical tree: o=hp (organisation) | | +----------------------+-----------------+ | | | | | | ou=ITO ou=DeskJet cn=Admin (organisational unit) (organisational unit) (user) | | | | +------------+ +------------+ | | | | cn=MickeyFS cn=Ted cn=DonaldFS cn=HP890 .... (file server) (user) (file server) (print server) .... Abbreviation CN stands for Common Name and is the name of leaf object in the Directory tree. A specific user can login into this tree as .cn=admin.o=hp or .cn=ted.ou=ITO.o=hp. This notation can be specified with typeless naming like .admin.hp or .ted.ITO.hp. Novell has complicated the naming convention by providing concepts like countries, current context, relative distinguished names. More precise definitions can be found in Novell NetWare manuals and they are not subject of these release notes. 2) NDS related changes in ITO Agent for Netware ----------------------------------------------- 2.1 Changes in the installation program (ITOINST.NLM): Version 2.00 of ITOINST.NLM supports NDS. During the installation after asking user: "Do you want to add ITO management server to SYS:ETC/HOSTS file:" a new prompt is issued to a user "Do you want to use NDS:" 2.1.1 Answer No - Bindery mode: Answering NO to the last question continues installation in the old way. User has to provide usernames and passwords for each server on which he wants to install ITO agent. The login process is done in bindery mode so bindery emulation must be running on all servers that we want ITO agent to install on. Bindery emulation is started on Novell file server if there is a line set bindery context = ou=xxx.o=yyyy present in SYS:SYSYTEM/autoexec.ncf. If such line is missing then bindery emulation is not running and users can login only to Directory tree. 2.1.2 Answer Yes - NDS mode The following dialog appears: "Enter Login Name :" Type in the distinguished name (that is the full path from the root of the tree) of the user which has priviledges to modify the directory tree (usually CN=Admin.O=xyz). After successful login user can select servers targeted for installation. Installation program gives him the list of all NetWare servers that are presented in the same subtree as entered user. In the previous example if "Admin" is provided file server MickeyFS and DonaldFS are shown. Novell has the term CONTEXT to describe an object's position in the Directory tree. Because cn=Admin is positioned in o=hp context (container or subtree) user Admin can access MickeyFS as this object is part of container ou=ITO that is contained in o=hp. Previous example works if privileges and rights are correctly set. User Admin is by default constructed with all rights to all servers when NetWare 4.x is installed and when new servers are inserted into existing tree. After successful login installation procedure works as the old version: of course user does not have to provide any login names and passwords for selected servers. The extra step done by installation is creating special file on each selected server SYS:/OPT/OV/BIN/OPC/INSTALL/NDSINFO that contains context so that ITO agent .NLMs can login to NDS when they are later started. Also user OPC_OP is now inserted into NDS as opposed to older version that used bindery services to process OPC operator and OPC group. 2.2 Username interpretation for Netware ITO applications In order to use Netware ITO applications with ITO Agent for Netware (with new NDS functionality) it is good to know how login information is used. Whenever authentication is requested the agent performs the following steps: - The agent changes the context to the context specified in NDSINFO. If the file does not exist (when the agent is installed in bindery mode) than no change of context is performed; default context is used. - The agent logs in the username using the new context. The username we refer to is the username defined in the "Execute as User/User Name:" field for the action in the ITO GUI. The login procedure reports the following errors: - Invalid username - Invalid password - Other errors concerning the login procedure (not like to happen in normal operation) The concatenation of the context and the username must yield a valid Novell Netware distinguished user name. Concatenation is done using default NDS naming conventions. For example: it is possible to use Trimmed Masking to control the portion of the name context that is appended to the relative distinguished name (the username portion of the full username) by following the username portion with one or more periods. For each period that trails the username, the client agent removes one partial name from the least significant (left) side of the name context, before appending the name context to the input name. For more information regarding Trimmed Masking and other naming conventions see Netware manuals. Some examples: username/name context (NDSINFO)/distinguished name 1. opc_op/O=PRIS_CO/CN=opc_op.O=PRIS_CO 2. CN=opc_op/O=PRIS_CO/CN=opc_op.O=PRIS_CO 3. opc_op.O=PRIS_CO./O=PRIS_CO/CN=opc_op.O=PRIS_CO 4. opc_op// Example 1 shows the default case after installation, example 2 is the same but uses attributes, example 3 shows an example of Trimmed Masking and finaly example 4 show the situation when bindery context is used. 3) Installation notes --------------------- 3.0 Using NDS services with ITOINST.NLM will allow you to install from depot server only servers that are contained in the same container as the logged in user (normally Admin) and the depot server. If network has more Directory trees - e.g. one for production and one for development - you have to make two depot servers (one in each tree) to use ITO agent installation in NDS mode. To shorten time that is needed to prepare depot server (installation of NetBasic, unzipping ITO package) you can merge depot server to the other tree temporarily, perform installation and then merge depot back to the original tree where it was at the beginning. 3.2 To use NDS mode when installing ITO agent for NetWare you do NOT have to remove set bindery context = ... lines from AUTOEXEC.NCF files on various file servers as stated in the ITO Administrator Reference Manual for A.04.00. Installation in NDS mode is done quicker as only one login to Directory tree is enough. Bindery emulation can become obsolete with new version of NetWare. That is why we suggest using NDS mode even if bindery emulation is running as is default case when installing NetWare servers. But care must be taken when providing login name. When bindery emulation is running on NetWare depot server context from "set bindery context = ..." line is made as current context. So only "Admin" string is enough to give to installation procedure. But now context stored into NDSINFO file can be wrong if there are more users Admin in one tree and if bindery context is set to wrong container. To prevent this always enter distinguished user name in the form .cn=admin.ou=xxx.o=yyy when asked for login name. 3.3 During the test we found that installation procedure ITOINST.NLM in NDS mode does not work if depot server was on NetWare 4.10 with older NetBasic version (NBALLRC1.EXE from February 97). Copy file process from depot server to other servers is not working in this environment. We at least suggest NetBasic from February 98 (file NBV6.EXE from HitechSoft www site). This version works also with NetWare 4.11 file servers. So previous restriction that depot server should be only set on NetWare 4.10 or less is no more valid. PHSS_13382: - The ITO Agent was not installable on Novell SFT III systems. SR: 5003402008 Patch Files: /opt/OV/OpC/examples/progs/Makef.nw /opt/OV/OpC/examples/progs/nwopcnlm.c /opt/OV/bin/OpC/nwactions/nwgr_cachebuffers /opt/OV/bin/OpC/nwactions/nwgr_volfree /opt/OV/bin/OpC/nwactions/nwgr_trends /opt/OV/bin/OpC/nwactions/nwgr_logusers /opt/OV/bin/OpC/nwactions/nwgr_allocmem /opt/OV/bin/OpC/nwactions/nwgr_dirtycache /opt/OV/bin/OpC/nwactions/nwgr_lslinpkts /opt/OV/bin/OpC/nwactions/nwgr_lsloutpkts /opt/OV/bin/OpC/nwactions/nwgr_filereads /opt/OV/bin/OpC/nwactions/nwgr_filewrites /opt/OV/bin/OpC/nwactions/nwgr_readKbytes /opt/OV/bin/OpC/nwactions/nwgr_writeKbytes /opt/OV/bin/OpC/nwactions/nwgr_physinpkts /opt/OV/bin/OpC/nwactions/nwgr_physoutpkts /opt/OV/bin/OpC/nwactions/nwgr_physinkbytes /opt/OV/bin/OpC/nwactions/nwgr_physoutkbytes /opt/OV/bin/OpC/nwactions/nwgr_readyjobs /opt/OV/bin/OpC/nwactions/nwgr_readyKbytes /opt/OV/bin/OpC/nwactions/nwgr_queue /opt/OV/bin/OpC/nwactions/nwgr_cachehits /opt/OV/bin/OpC/nwactions/nwgr_freeredirarea /opt/OV/bin/OpC/nwactions/nwgr_memmon /opt/OV/bin/OpC/nwactions/nwgr_codemem /opt/OV/bin/OpC/nwactions/nwgr_cpu /opt/OV/bin/OpC/agtinstall/opcnwping /opt/OV/bin/OpC/agtinstall/opcnwprlg /opt/OV/bin/OpC/agtinstall/opcnwinst /opt/OV/bin/OpC/agtinstall/xconsole /opt/OV/ReleaseNotes/patches/PHSS_13382.ps /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/opc_pkg.Z /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/unzip.nlm /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/unzip.txt /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/vendor.nlm /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/itodown.ncf /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/itoreset.ncf /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/itorsnma.ncf /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/AgentPlatform /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_allocmem /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_cachebuffers /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_cachehits /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_codedatamem /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_conns /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_cpuutil /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_dirtycache /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_filereads /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filewrites /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_diskfree /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuejobwaittime /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_users /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_lslinpckts /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_lsloutpckts /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_ncprequests /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physinkpckts /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physoutkpckts /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physoutpckts /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filekreads /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuereadykbytes /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuereadyjobs /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_volfree /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filekwrites what(1) Output: /opt/OV/OpC/examples/progs/Makef.nw: None /opt/OV/OpC/examples/progs/nwopcnlm.c: None /opt/OV/bin/OpC/nwactions/nwgr_cachebuffers: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_volfree: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_trends: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_logusers: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_allocmem: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_dirtycache: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_lslinpkts: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_lsloutpkts: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_filereads: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_filewrites: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_readKbytes: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_writeKbytes: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_physinpkts: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_physoutpkts: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_physinkbytes: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_physoutkbytes: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_readyjobs: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_readyKbytes: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_queue: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_cachehits: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_freeredirarea: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_memmon: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_codemem: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/nwactions/nwgr_cpu: HP OpenView IT/Operations A.04.00 (07/29/97) /opt/OV/bin/OpC/agtinstall/opcnwping: HP OpenView IT/Operations A.04.12 (01/19/99) /opt/OV/bin/OpC/agtinstall/opcnwprlg: HP OpenView IT/Operations A.04.12 (01/19/99) /opt/OV/bin/OpC/agtinstall/opcnwinst: HP OpenView IT/Operations A.04.12 (01/19/99) /opt/OV/bin/OpC/agtinstall/xconsole: HP OpenView IT/Operations A.04.12 (01/19/99) /opt/OV/ReleaseNotes/patches/PHSS_13382.ps: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/opc_pkg.Z: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/unzip.nlm: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/unzip.txt: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/vendor.nlm: HP_OpenView_IT/Operations_A.04.12_PHSS_17234_(01/19/ 99) libovsnmp mibform/mibtable /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/itodown.ncf: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/itoreset.ncf: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/A.04.12/RPC_SUN_TCP/actions/itorsnma.ncf: None /var/opt/OV/share/databases/OpC/mgd_node/vendor/novell/ intel/nw/AgentPlatform: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_allocmem: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_cachebuffers: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_cachehits: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_codedatamem: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_conns: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_cpuutil: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_dirtycache: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filereads: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filewrites: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_diskfree: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuejobwaittime: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_users: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_lslinpckts: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_lsloutpckts: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_ncprequests: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physinkpckts: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physoutkpckts: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physoutpckts: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filekreads: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuereadykbytes: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuereadyjobs: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/nw_gr_volfree: None /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filekwrites: None cksum(1) Output: 2589312207 1731 /opt/OV/OpC/examples/progs/Makef.nw 513068195 4484 /opt/OV/OpC/examples/progs/nwopcnlm.c 3420833251 11029 /opt/OV/bin/OpC/nwactions/nwgr_cachebuffers 3899899679 11019 /opt/OV/bin/OpC/nwactions/nwgr_volfree 3844242092 11504 /opt/OV/bin/OpC/nwactions/nwgr_trends 2462378874 10996 /opt/OV/bin/OpC/nwactions/nwgr_logusers 3674660468 11009 /opt/OV/bin/OpC/nwactions/nwgr_allocmem 636827678 11030 /opt/OV/bin/OpC/nwactions/nwgr_dirtycache 4038563959 11014 /opt/OV/bin/OpC/nwactions/nwgr_lslinpkts 2662375809 11018 /opt/OV/bin/OpC/nwactions/nwgr_lsloutpkts 3427729363 10987 /opt/OV/bin/OpC/nwactions/nwgr_filereads 3466835296 10991 /opt/OV/bin/OpC/nwactions/nwgr_filewrites 2324180879 11020 /opt/OV/bin/OpC/nwactions/nwgr_readKbytes 1668707500 11024 /opt/OV/bin/OpC/nwactions/nwgr_writeKbytes 1412720976 11062 /opt/OV/bin/OpC/nwactions/nwgr_physinpkts 3632053713 11065 /opt/OV/bin/OpC/nwactions/nwgr_physoutpkts 3815073193 11059 /opt/OV/bin/OpC/nwactions/nwgr_physinkbytes 484238875 11063 /opt/OV/bin/OpC/nwactions/nwgr_physoutkbytes 3114545939 11018 /opt/OV/bin/OpC/nwactions/nwgr_readyjobs 3304978364 11035 /opt/OV/bin/OpC/nwactions/nwgr_readyKbytes 566238709 11131 /opt/OV/bin/OpC/nwactions/nwgr_queue 2304604584 11038 /opt/OV/bin/OpC/nwactions/nwgr_cachehits 539394962 11040 /opt/OV/bin/OpC/nwactions/nwgr_freeredirarea 3053300283 11102 /opt/OV/bin/OpC/nwactions/nwgr_memmon 195429400 11020 /opt/OV/bin/OpC/nwactions/nwgr_codemem 1490779331 11003 /opt/OV/bin/OpC/nwactions/nwgr_cpu 708572804 10627 /opt/OV/bin/OpC/agtinstall/opcnwping 2049746729 11811 /opt/OV/bin/OpC/agtinstall/opcnwprlg 457272824 7336 /opt/OV/bin/OpC/agtinstall/opcnwinst 2899179873 11296 /opt/OV/bin/OpC/agtinstall/xconsole 2895838758 198343 /opt/OV/ReleaseNotes/patches/PHSS_13382.ps 2486779821 2162885 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/A.04.12/RPC_SUN_TCP/opc_pkg.Z 3992377484 136975 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/A.04.12/RPC_SUN_TCP/unzip.nlm 3329730331 498 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/A.04.12/RPC_SUN_TCP/unzip.txt 2605702631 512246 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/A.04.12/RPC_SUN_TCP/actions/ vendor.nlm 59100992 42 /var/opt/OV/share/databases/OpC/mgd_node/vendor/ novell/intel/nw/A.04.12/RPC_SUN_TCP/actions/ itodown.ncf 1371676178 45 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/A.04.12/RPC_SUN_TCP/actions/ itoreset.ncf 780042742 12 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/A.04.12/RPC_SUN_TCP/actions/ itorsnma.ncf 1078953022 3610 /var/opt/OV/share/databases/OpC/mgd_node/ vendor/novell/intel/nw/AgentPlatform 1450639985 424 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_allocmem 262779162 679 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_cachebuffers 2051618301 834 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_cachehits 1988221648 503 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_codedatamem 1102234046 1036 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_conns 3734941396 1541 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_cpuutil 3254379345 1117 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_dirtycache 2833214369 666 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filereads 2215936743 671 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filewrites 1484806384 1200 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_diskfree 3479302734 1791 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_queuejobwaittime 3490074225 1069 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_users 2451158763 708 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_lslinpckts 2427152498 704 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_lsloutpckts 98987806 753 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_ncprequests 3556320696 695 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physinkpckts 2566783219 706 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physoutkpckts 3061872886 709 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_physoutpckts 2879980713 700 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filekreads 514249130 1214 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_queuereadykbytes 1993581372 1216 /var/opt/OV/share/help/C/ovmib/OVW/ Functions/nw_gr_queuereadyjobs 175475582 371 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_volfree 3593849648 707 /var/opt/OV/share/help/C/ovmib/OVW/Functions/ nw_gr_filekwrites Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_13382 PHSS_14181 Equivalent Patches: None Patch Package Size: 3420 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_17234 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_17234.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_17234.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_17234. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. Warning: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_17234.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_17234.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: BEFORE LOADING THIS PATCH... o You may use this patch with the following official ITO releases: A.04.X o DO NOT use this patch with older releases of OpC or ITO, for example versions A.01.X, A.02.X or A.03.X. o This patch provides the HP OV IT/Operations Intelligent Agent to be used with a ITO 4.0x Management Server system, Oracle, English and Japanese version. (A) Patch Installation Instructions ------------------------------- (A1) Install the patch, following the standard installation instructions. Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license restrictions and limitation of liability and warranties, before installing this patch. ------------------------------------------------------ 1. Back up your system before installing a patch. (you may use opc_backup) 2. Login as root. 3. Copy the patch to your /tmp directory and unshar it: # cd /tmp # sh PHSS_17234 4. For a standalone system, run swinstall to install the patch: NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM ADDRESSED BY THIS PATCH IS DISTRIBUTED (either from the ITO Administrator's GUI or from command line using inst.sh) WHILE RUNNING SWINSTALL. # swinstall -x match_target=true \ -s /tmp/PHSS_17234.depot It is recommended that you move the PHSS_17234.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: # dd if=/tmp/PHSS_17234.depot of=/dev/rmt/0m bs=2k NOTE: This patch must be installed on the ITO Management Server system, NOT on an ITO Managed Node directly. Changes will take effect on managed nodes by means of ITO Software Distribution (using 'Force Update' if there is already an agent installed on the managed node). See chapter 2 of the ITO Administrator's Reference manual for more information. (B) Patch Deinstallation Instructions --------------------------------- (B1) To deinstall the patch PHSS_17234 run swremove: NOTE: MAKE SURE THAT NO AGENT OF THE PLATFORM ADDRESSED BY THIS PATCH IS DISTRIBUTED (either from the ITO Administrator's GUI or from command line using inst.sh) WHILE RUNNING SWREMOVE. # swremove PHSS_17234