| Symptom | Possible cause and recommendation |
|---|---|
| Notification that modifying an interconnect was unsuccessful |
If interconnect edit is unsuccessful:
When the interconnect has been edited successfully, a notification will display in the banner at the top of the screen, and the desired port setting and port status will be displayed. |
| Symptom | Possible cause and recommendation |
|---|---|
| Interconnect module is in an Inventory state |
The interconnect module is not part of a logical interconnect. To bring the interconnect module into a managed or monitored state:
|
| Interconnect modules are in a Maintenance state |
There is an OA credential caching issue if interconnect modules report their state as If interconnect modules are in a Maintenance state: You have to re-add the enclosure.
This will initiate rediscovery of the enclosure and its components. |
| Interconnect modules are in an Unmanaged state |
Interconnect bay has a mismatch with the expected type The logical interconnect group is expecting a different interconnect than what is in the enclosure.
|
|
Interconnect has firmware installed which is less than the minimum supported baseline version
See the HPE OneView Support Matrix for the complete list of supported firmware versions. |
| Symptom | Possible cause and recommendation | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Interconnect status is Missing or Incompatible |
Interconnect module was in use when it was removed from an enclosure
If a Virtual Connect Fibre Channel module was in use and configured at the time it was physically removed, it must be replaced by a module of the same model and type. A Virtual Connect Fibre Channel module is in use if any of the following conditions exist:
|
||||||||||||
| Interconnect failure | Interconnect failed and must be replaced
|
-
Troubleshooting (top of chapter)
![[NOTE: ]](images/note.gif)