HP-UX Host Intrusion Detection System Release 4.0 Release Notes for HP-UX 11i v1 | HP-UX 11i v2 | HP-UX 11i v3

# uname -r
It should display B.11.11, B.11.23 , or B.11.31respectively.
• The system must be running either HP-UX 11i v1 HP-UX 11i v2, or HP-UX 11i v3.
• You must be a superuser to do the installation.
Administration System
The system on which you plan to install the administration software must meet the
following requirements:
• You must have 26 MB of free disk space in /opt/ids and space for configuration
files in /etc/opt/ids and log files in /var/opt/ids.
• You must have Java 2 Platform Standard Edition 5.0 (J2SE 5.0) and all the
corresponding Java patches. Java installation is part of these installation
instructions.
Agent Systems
Each system on which you plan to install the agent software must meet the following
requirements:
• You must have 8 MB of free disk space in /opt/ids.
• The memory mapped file (/var/opt/ids/ids_*) is 20 M in size. HP recommends
that you have at least 50 M of free space in /var for the memory mapped files and
log files.
• For HP-UX 11i v1, you must have certain patches for both the operating system
and the kernel audit system. Patch installation is part of these installation
instructions.
• The cron daemon must be enabled. Refer to cron(1M) for more information.
• Virtual memory usage by the idscor process can be as high as 200 M. You may
need to increase the maxdsiz tunable parameter for your system.
Dual System
If a system is both an administration system and an agent system, it must meet the
requirements for both system types.
When Updating from Release 2.x
The templates in Release 4.0 differ significantly from those in 2.x. In order to use existing
2.x schedules, you must first migrate to Release 3.1 and then use the guiSchedConvert
migration tool to convert v2.x schedules to v3.x schedule files. Use the v3.1
adminschedconvert migration tool to convert v2.x text schedule files to v3.x text
schedule files. You must then upgrade to v4.0. The v4.0 System Manager and agent is
backward compatible with v3.x schedules.
When Updating from Release 2.x 21