Troubleshooting logical interconnects

I/O bay occupancy errors

Symptom Possible cause and recommendation

Symptom	Possible cause and recommendation
Change in interconnect state	Interconnect state errors can be caused by: Interconnect missing from an IO bay (Interconnect state is `Absent`) Unsupported interconnect model found in an IO bay (Interconnect state is `Unsupported`) Unable to manage interconnect in IO bay due to unsupported firmware (Interconnect state is `Unmanaged`) Mismatch between the interconnect type and the type specified by logical interconnect group Mismatch of horizontally adjacent interconnect modules

Change in interconnect state

Interconnect state errors can be caused by:

Interconnect missing from an IO bay (Interconnect state is Absent)
Unsupported interconnect model found in an IO bay (Interconnect state is Unsupported)
Unable to manage interconnect in IO bay due to unsupported firmware (Interconnect state is Unmanaged)
Mismatch between the interconnect type and the type specified by logical interconnect group
Mismatch of horizontally adjacent interconnect modules

Uplink set warnings or errors

Symptom	Possible cause and recommendation
Uplink set not operational	Uplink set not operational due to: One or more uplinks are not in operation due to a bad cable, no cable, lack of transceiver, or invalid transceiver No networks assigned DCBX information is missing for an FCoE network Verify that the following prerequisites are met: At least one network is defined You have Network administrator privileges or equivalent to manage networks. For more information, see About user roles. DCBX information is required for FCoE networks Verify that the data you entered on the Add Uplink Set screen is correct, and that the uplink set name is unique. Retry the operation.

Symptom

Possible cause and recommendation

Uplink set not operational

Uplink set not operational due to:

One or more uplinks are not in operation due to a bad cable, no cable, lack of transceiver, or invalid transceiver
No networks assigned
DCBX information is missing for an FCoE network

Verify that the following prerequisites are met:
- At least one network is defined
- You have Network administrator privileges or equivalent to manage networks. For more information, see About user roles.
- DCBX information is required for FCoE networks
Verify that the data you entered on the Add Uplink Set screen is correct, and that the uplink set name is unique.
Retry the operation.

Physical interconnect warnings or errors

Symptom	Possible cause and recommendation
Interconnect-level warnings or errors	Interconnect warnings or errors can be caused by: Downlink with a deployed connection is not operational Incorrect firmware version (different from firmware baseline version) Configuration error Hardware fault Lost communication Administratively disabled ports

Firmware update errors

Symptom Possible cause and recommendation

Symptom	Possible cause and recommendation
Firmware update fail entries shown in the Activity log	Interconnect firmware errors can be caused by: Restarting interconnect modules while a firmware update is in progress. Starting a firmware update while another firmware update is already in progress. An interconnect in the Logical Interconnect is not in a `Configured` state before starting the upgrade. HPE OneView cannot communicate with the Onboard Administrator for the enclosure. Recommendations Do not restart interconnect modules while a firmware update is in progress. Check the Activity Log for more information about the root cause. If staging firmware failed, check the Activity Log, correct the problem and restart the update. If activating firmware failed, check the Activity Log, and then manually activate the firmware. Then confirm the VC interconnect firmware versions in HPE OneView are the same versions shown in OA. Make sure that all interconnects in the Logical Interconnect are in the `Configured` state before starting the upgrade. If a firmware update persistently fails, see the online help to create a logical interconnect support dump file and contact your Hewlett Packard Enterprise support representative.

Firmware update fail entries shown in the Activity log

Interconnect firmware errors can be caused by:

Restarting interconnect modules while a firmware update is in progress.
Starting a firmware update while another firmware update is already in progress.
An interconnect in the Logical Interconnect is not in a Configured state before starting the upgrade.
HPE OneView cannot communicate with the Onboard Administrator for the enclosure.

Recommendations

Do not restart interconnect modules while a firmware update is in progress.
Check the Activity Log for more information about the root cause.
1. If staging firmware failed, check the Activity Log, correct the problem and restart the update.
2. If activating firmware failed, check the Activity Log, and then manually activate the firmware. Then confirm the VC interconnect firmware versions in HPE OneView are the same versions shown in OA.
Make sure that all interconnects in the Logical Interconnect are in the Configured state before starting the upgrade.
If a firmware update persistently fails, see the online help to create a logical interconnect support dump file and contact your Hewlett Packard Enterprise support representative.

Pause flood condition detected on a Flex-10 physical port

Symptom	Possible cause and recommendation
All Flex-10 logical ports associated with physical ports are disabled	When pause flood protection is enabled, this feature detects pause flood conditions on server downlink ports and disables the port. The port remains disabled until an administrative action is taken. The administrative action involves the following steps: Resolve the issue with the NIC on the server causing the continuous pause generation. This might include updating the NIC firmware and device drivers. Rebooting the server might not clear the pause flood condition if the cause of the pause flood condition is in the NIC firmware. In this case, the server must be completely disconnected from the power source to reset the NIC firmware. Re-enable the disabled ports by resetting the pause flood protection. You can reset pause flood protection from the Actions menu on the Interconnects screen.

Symptom

Possible cause and recommendation

All Flex-10 logical ports associated with physical ports are disabled

When pause flood protection is enabled, this feature detects pause flood conditions on server downlink ports and disables the port. The port remains disabled until an administrative action is taken. The administrative action involves the following steps:

Resolve the issue with the NIC on the server causing the continuous pause generation. This might include updating the NIC firmware and device drivers.

Rebooting the server might not clear the pause flood condition if the cause of the pause flood condition is in the NIC firmware. In this case, the server must be completely disconnected from the power source to reset the NIC firmware.
Re-enable the disabled ports by resetting the pause flood protection.

You can reset pause flood protection from the Actions menu on the Interconnects screen.

See also

Troubleshooting (top of chapter)

prev	up	next
Troubleshooting licenses	home	Troubleshooting logical switches