Interconnect 6 Lost IPv4 Address after OneView 10.0 Update

[ndavis_cmm]

Hello,

I was curious if anyone else has seen a similar issue. After the OneView update completed one interconnect lost it's IPv4 address. OneView wants you to reapply the configuration to the LE, but that seems like it will cause major impact. We did open a case with HPE Support, but so far I have been underwhelmed with the support I am receiving from this particular technician. 

Thankfully everything is working using the IPv6 address, but I feel uneasy having a warning on my dashboard for a production system. 

Has anyone else seen this? Should I escalate the issue? 

[prajwal_ds]

Hi @ndavis_cmm,

Please take a look at this post, it might help you.

Thanks,
Prajwal D S

[Harshitha_K · Accepted solution]

Hi  @ndavis_cmm ,

Hope this helps!

Please try these steps:

-> Verify IPv4 Configuration:

• Ensure IPv4 address pool or manually assigned address is still intact.
• Sometimes, oneView resets or loses track of the static assignment post-upgrade.

-> Reapply Configuration to the Logical Interconnect (Link for procedure)

• Navigate to the Logical interconnect in oneView
• Uses "update from Group" or "Reapply configuration"
• This helps in syncing without need to modify the LE or reboot the interconnects.

-> Check firmware consistency:

• Ensure the firmware baseline for Interconnects and the enclosure group is still aligned with intended version.

If the issue still persists, please log a support case with HPE.

Thank you!

[ndavis_cmm]

I did see this article, I am going to ask about this in my open support case. 

[ndavis_cmm]

Hello,

The configuration for the IP address pool is there, OneView recognizes what the IP address should be, but it's blank on the actual interconnect. I was hesitiant to re-apply the Logical Interconnect configuration because it warns that it will be impactful. I don't see an update from group option only the "reapply configuration" option. The firmware is consistent. 

I did open a support case. 

[ndavis_cmm]

Working with support they had us do the reapply of the LE. The reapply was successful and it did not impact our production which was great. The next step if that had not worked was to perform and efuse of the interconnect, but we fortunately did not have to do that. 

[Rakesh0404]

Hello, Thank yoyu for sharing the update. 
We wanted to follow up and check if the links provided to you addressed the issue. Request you to please respond with a Yes/No. You may also click on "Accept as a solution" button if the issue is resolved.

[ndavis_cmm]

For reference this issue occurred again in our other datacenter when performing the update. This may be a larger issue related to the upgrade. 

It was a similar behavior that an interconnect on the second LE group lost its IPv4 address. 

We resolved it by the same steps posted above.