HP-UX Serviceguard Heartbeat Configuration Solutions

IMPORTANT: You should take into account the fact that devices may vary in their

maximum bandwidth and processor consumption requirements.

For example, highly utilized interfaces will tend to consume more processor cycles than

lower utilized interfaces. Also, interfaces with high speeds (e.g., 1 Gbps vs 100 Mbps

interfaces) can consume more bandwidth and cycles due to the higher throughput of the

interface.

CPU consumption can be measured by through tools such as TOP or GlancePlus.

2. Moving an interrupt.

Enter the following intctl command:

/usr/contrib/bin/intctl -M -H <hardware path> -I 1 -c <cpu ID>

Where <hardware path> is the hardware path of the device using the format

#/#/#/#, and <cpu ID> is the target processor to move.

3. Save the current processor assignments after completing the interrupt migration for the

system by entering the following command:

/usr/contrib/bin/intctl -s /etc/interrupt_migration_conf

This information will be saved in the file /etc/interrupt_migration_conf.

IMPORTANT: You must run /usr/contrib/bin/intctl -r

/etc/interrupt_migration_conf after each subsequent bootup to ensure that the

heartbeats are assigned as per your selected changes.

Changes to I/O, such as adding or deleting cards, will probably affect the current

processor assignments so the /etc/interrupt_migration_conf file should be

regenerated after any I/O change.