HP-UX Secure Resource Partitions (SRP) A.02.02 Release Notes

• The correct state is reported by srp –status.

In HP-UX SRP A.02.01 or earlier, the state reported by the srp -status command was

inconsistent with the actual status of the SRP.

Defect number: QXCR1001063622

• The Secure Shell server can now be re-started in the INIT compartment via

/sbin/init.d/secsh.

NOTE: This requires HP-UX Secure Shell version A.05.50 or later. You can download HP-UX

Secure Shell from

http://software.hp.com.

Defect number: QXCR1001063627

1.7 Known Issues in HP-UX SRP A.02.02

HP-UX SRP A.02.02 contains the following known issues:

• Network route selection not optimized for INIT compartment

Intermittent loss of connectivity from the INIT compartment to a remote host after a local SRP

on an isolated network unsuccessfully attempts to connect to the same host.

Workaround:

Avoid attempting to connect to unreachable hosts from an SRP. Consider decreasing the

cache entry hold time if the problem occurs frequently, as follows:

# ndd -set /dev/ip ip_ire_flush_interval 60000

• Unable to connect to a clone of a local SRP on a remote server after a system

failure or net start

Attempting to connect to the SRP IP address after a system failure or execution of

/sbin/init.d/net start will fail, even after the remote instance of the SRP is started. This

problem most frequently occurs when Serviceguard manages the SRP as a Serviceguard package

and the SRP is not configured to allow Serviceguard to manage the IP Address of the SRP.

Workaround:

Start and then stop the SRP to make the IP address of the SRP inaccessible. If using Serviceguard,

consider configuring Serviceguard to manage the IP address of the SRP and remove the IP

address of the SRP and related configuration from the /etc/rc.config.d/netconf file.

• SRP IP Address remains enabled after a system failure/reboot.

IP addresses for SRPs that are active at time of system failure will be active after the system is

restarted, even if the SRP is not restarted.

Workaround:

To prevent remote systems from accessing the affected IP addresses, do the following:

1. Edit the /etc/rc.config.d/netconf file and change the INTERFACE_STATE

for all the SRP IP addresses that are not in the STARTED state to down.

2. Run the /sbin/init.d/net start command.