Configuring Advanced Networking Features - HP Rx2620-2 - Integrity - 0 MB RAM User Manual

Configuring advanced networking features

Table 6-3 Configuring advanced networking features
Problem
All members of the team currently
have a yellow X with a status of
"Active Path Failure" and the team
is degraded (yellow team icon).
An NFT Preference Order Only
with Active Path Failover-enabled
team prefers a team member with
a yellow X over a member without
a yellow X.
The Network Configuration Utility
(NCU) does not show any failures
on the team; however I cannot
reach (ping) the echo node.
An NFT Preference Order Only
with Fast Path Failover team
prefers a team member with a
yellow X over a member without
a yellow X.
The Network Configuration Utility
(NCU) does not show any failures
on the team; however the team
member with the highest path cost
is the Primary adapter instead of
the member with the lower cost.
The Automatic team type with
Active Path Failover enabled team
does not detect an Echo Node
failure.
50 Troubleshooting
Possible Cause
Active Path Failure is a failure
condition of the Active Path Failover
mechanism. If all members of the
team have a yellow X with a status of
"Active Path Failure," this means
none of the members were able to
reach the echo node device.
This may be expected behavior based
on the configured settings.
This may be expected behavior based
on the configured settings.
This may be expected behavior based
on the configured settings.
Possible Solution
Verify the echo node device is on the
same IP subnet as the team.
• If echo node device is not on the same
IP subnet, reconfigure the echo node
settings on the Advanced Redundancy
tab for the team to a device that is on
the same IP subnet. Retest with these
settings.
• If the echo node device is on the same
IP subnet, can you ping the echo
node? If No, check the echo node
device to ensure it is operating and
the IP information is correct.
• If using VLANs, ensure the correct
VLAN is chosen for the Active Path
VLAN ID on the VLAN Tab of the
team.
Open the Network Configuration Utility
(NCU) and go to the Advanced
Redundancy tab for the team. Check the
Mechanism Priority setting.
If Active Path Failover is used in this
team type, it must have a higher
Mechanism Priority than the Preference
Order.
Reconfigure the settings so Active Path
Failover is above Preference Order in the
Mechanism Priority list box.
Open the Network Configuration Utility
(NCU) and go to the Advanced
Redundancy tab for the team. Check the
Mechanism Priority setting.
If Fast Path Failover is to be used in this
team type, it must have a higher
Mechanism Priority than the Preference
Order.
Reconfigure the settings so Fast Path
Failover is above Preference Order in the
Mechanism Priority list box.
Open the Network Configuration Utility
(NCU) and go to the Information tab for
the team. Check the Current Mode.
If the current mode is 802.3ad Dynamic
with Fault Tolerance, this is normal
behavior to ignore the echo node
mechanism. This mechanism is only
applicable if the automatic team type
ends up in TLB (Transmit Load
Balancing) mode.