Loading...
Loading...
When a direct-attached Fabric port is disabled and re-enabled for any reason, either from Virtual Connect side or Storage side, the healthy non-impacted paths disappear and do not re-appear under the specific connection when the connection is re-established. Meanwhile the Operating System (OS) loses the disabled path and regains the path when the connection is re-established. There is no impact to the other paths that are active and healthy at this point.On the OneView Profile –> Volume Attachments –> Storage, target paths will continue to show an incorrect status, the disabled path will be left in the server profile, and the active/good path will disappear. At this point this does not impact OS connectivity.This issue is only applicable to profiles with direct-attached storage and can only be seen when direct-attach paths are disabled.Below is an example of a good state and the example path "23:33:00:02:AC:07:EB:01"Example of the path on Storage being disabled below:As shown in the example below, even when the disabled path is active, the unhealthy/inactive path remains on the impacted side and the active/healthy paths are incorrectly removed:As a consequence of OneView logic, the "OneView - Volumes" section will now recommend removing extra presentations. This recommendation is incorrect and should be ignored. If this flawed recommendation is followed, the valid paths can be removed resulting in loss of redundancy or an outage in the OS:Never remove "Extra Presentations;" just clear the alert pointing to volume XXXXX with presentations to WWPNs that are not configured by HPE OneView.
Any HPE OneView with directly-attached storage.
This issue is fixed by upgrading toHPE OneView 10.10or later.The issue will not impact the actual OS storage connections and will remain a cosmetic issue, as long as the incorrect recommendation that displays in HPE OneView is ignored. It is only be seen when direct-attach paths are disabled.As a workaround, schedule a server downtime. Then un-assign and re-assign the server profile. This should be done after all the required/expected paths are back online.It is not necessary remediate all the server profiles at once; instead, downtime can be scheduled in stages.Document VersionRelease DateDetails2Sept 03, 2025Updated the advisory with the permanent fix.1July 09, 2025Original Document Release.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.