Expand Configuration and Management Manual (H06.21+, J06.10+)

Subsystem Description
Expand Configuration and Management Manual — 529522-013
17 - 73
Multi-CPU Considerations
modifier and one or more the existing paths are in a multi-CPU path, then the new path
joins the multi-CPU path. If there is no preexisting multi-CPU path, then a multi-CPU
path is created with the new path as its sole member.
When a path comes up, it negotiates its multi-CPU membership with the Expand line-
handler process on the other end of the connection. Both sides of the connection must
be configured with the SUPERPATH_ON modifier or neither the local nor the remote
Expand line-handler process is considered to be a member of the multi-CPU path.
Multi-CPU Considerations
Consider these when configuring the Expand multi-CPU feature:
•
You cannot configure more than 32 multi-CPU paths in a system.
•
Each multi-CPU path can consist of up to 16 paths.
•
Expand-over-ServerNet line-handler processes cannot be part of a multi-CPU path.
•
Extended packets (L4EXTPACKETS_ON modifier) must be configured for Expand
line-handler processes that are part of a multi-CPU path. Not specifying extended
packets will cause an error message.
•
HP recommends that you specify the congestion control feature
(L4CONGCTRL_ON modifier) when configuring Expand line-handler processes
that are part of a multi-CPU path.
For more information on configuring extended packets, see
L4EXTPACKETS_OFF/L4EXTPACKETS_ON on page 16-14. For more information on
configuring the congestion control feature, see Congestion Control Feature on
page 17-69.