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

Troubleshooting
Expand Configuration and Management Manual — 529522-013
20 - 28
Multi-CPU Path Problems
Multi-CPU Path Problems
This subsection provides multi-CPU path troubleshooting guidelines and identifies
common multi-CPU path problems.
Troubleshooting Check List
Table 20-16 provides general suggestions to help you solve problems with multi-CPU
paths.
Table 20-16. Multi-CPU Path Problem Resolution Procedures
Task Procedure
Check that the multi-CPU path is
en
abled.
Use this SCF command to see if the paths you expect
to be part of the multi-CPU path are actually
configured:
INFO PROCESS $NCP, LINESET
If some of the paths do not display an “S” next to the
LINESET number
, then either the local or remote
Expand line-handler process does not have the
SUPERPATH modifier enabled. Use this SCF
command on both the local and remote Expand line-
handler processes to determine which line-handler
process configuration is in error:
INFO PATH $device_n
ame, DETAIL
Determine if the traffic is balanced
over all p
aths in the multi-CPU
path
Use this SCF command to find the base time factor
(TF) effective time factor (ETF) for all paths that are
part of the multi-CPU path:
INFO PATH $NCP, SUPERPATH
The load factors (LFs) of all the paths in the multi-CPU
p
ath should be roughly the same. (The LF is the ETF
divided by the base TF.) If they are not, rebalance the
paths using this SCF command:
ACTIVATE PROCESS $NCP, REBALANCE
\sys
tem_name
where system_n
ame identifies the multi-CPU path to
be rebalanced.
Caution. A Superpath rebalance can introduce a temporary disruption in the
network, similar
to but in general less than that caused by an Expand path change. For that reason we
recommend limiting rebalances to off-peak hours unless an imbalance is clearly causing
immediate problems.