iSCSI adapter IQN may change during the upgrade of ESXi 7.0 U1

3 years ago
January 12, 2022
11 comments
1113 views

victorwu
Veeam Vanguard
375 comments

According to VMware KB 84339, if the iSCSI adapter IQN is not the user setting then it is auto-generated by ESXi, and the IQN may change post upgrade. If access control is configured on the target side, based on the IQN, then the ESXi host may not be able to discover the LUN or datastore.

Today we will simulate this upgrade issue, we upgrade vSphere 7.0 U1c to 7.0U2a (build-17867351). This ESXi host is connected to an iSCSI datastore.

Demo Environment

vSphere 7.0 U1c build-17325551
iSCSI Software Adapter enabled
iSCSI Adapter IQN: iqn.1998-01.com.vmware:61dd29c9-bfb7-5707-6f97-000c29f2fde1-68ae16f6
Open Platform Software Defined Storage

Now we will upgrade vSphere 7.0 U1c to 7.0U2a. We can see the iSCSI adapter IQN is changed to "iqn.1998-01.com.vmware:localhost.localdomain:1988924762:65" after upgrading to vSphere 7.0 U2a. If the iSCSI LUN access control is configured on the target side based on the generated IQN, the ESXi host may not be able to discover the LUN or datastore.

To prevent this issue. Before upgrading to vSphere 7.0 U2, we need to use the esxcli get and set commands to set the generated iSCSI adapter IQN.

esxcli iscsi adapter get -A vmhba65

esxcli iscsi adapter set -A vmhba65 -n iqn.1998-01.com.vmware:61dd29c9-bfb7-5707-6f97-000c29f2fde1-68ae16f6

Now the iSCSI adapter IQN is a user setting, it won't change after the upgrade.

We can see the iSCSI adapter IQN won't change after the upgrade.

For details, please refer to this VMware KB https://kb.vmware.com/s/article/84339

+14

regnor
Veeam MVP
1352 comments
3 years ago
January 12, 2022

Thanks for posting about that issue @victorwu. I think I've ran into this some time ago and lost all iSCSI volumes after the upgrade; now I know the reason 😅

Max M. | Systems Engineer @Veeam | VMCE/VMCA | VeeaMVP 2023 | former Legend & Vanguard

victorwu
Author
Veeam Vanguard
375 comments
3 years ago
January 12, 2022

regnor wrote:

Thanks for posting about that issue @victorwu. I think I've ran into this some time ago and lost all iSCSI volumes after the upgrade; now I know the reason 😅

Great! I can let you know the reason. :grin:

Victor Wu

+17

JMeixner
On the path to Greatness
2650 comments
3 years ago
January 12, 2022

Thank you @victorwu , we have run into to this issue, too. I will forward this to our VMware admins.

+13

vNote42
On the path to Greatness
1246 comments
3 years ago
January 12, 2022

Thanks for sharing! I also know this issue from an upgrade of an customer environment.

BTW: in 6.7 releases it can happen that NICs get a new numbering after an update. This also leads to no access to iSCSI storage.

Wolfgang | vnote42.net | @vNote42

victorwu
Author
Veeam Vanguard
375 comments
3 years ago
January 12, 2022

vNote42 wrote:

Thanks for sharing! I also know this issue from an upgrade of an customer environment.

BTW: in 6.7 releases it can happen that NICs get a new numbering after an update. This also leads to no access to iSCSI storage.

Based on this VMware KB, this issue only exists in vSphere 7.0 U1. vSphere 6.7 and 7.0 are not affected during upgrade to 7.0 U2.

Victor Wu

+17

JMeixner
On the path to Greatness
2650 comments
3 years ago
January 12, 2022

We had this issue at update from 7.0 U2 to 7.0 U3, too….

victorwu
Author
Veeam Vanguard
375 comments
3 years ago
January 12, 2022

JMeixner wrote:

We had this issue at update from 7.0 U2 to 7.0 U3, too….

vSphere 7.0 U3 is not stable due to critical issues. This version is not suggested for production environment.

https://kb.vmware.com/s/article/86398

Victor Wu

+17

JMeixner
On the path to Greatness
2650 comments
3 years ago
January 12, 2022

victorwu wrote:

JMeixner wrote:

We had this issue at update from 7.0 U2 to 7.0 U3, too….

vSphere 7.0 U3 is not stable due to critical issues. This version is not suggested for production environment.

https://kb.vmware.com/s/article/86398

Yes, I know. The update was tested in a non-productive environment.

But this specific problem seems to exist with this version, too.

victorwu
Author
Veeam Vanguard
375 comments
3 years ago
January 12, 2022

JMeixner wrote:

victorwu wrote:

JMeixner wrote:

We had this issue at update from 7.0 U2 to 7.0 U3, too….

vSphere 7.0 U3 is not stable due to critical issues. This version is not suggested for production environment.

https://kb.vmware.com/s/article/86398

Yes, I know. The update was tested in a non-productive environment.

But this specific problem seems to exist with this version, too.

@JMeixner Thanks for your info. I will tell my team.

Victor Wu

+13

vNote42
On the path to Greatness
1246 comments
3 years ago
January 12, 2022

victorwu wrote:

vNote42 wrote:

Thanks for sharing! I also know this issue from an upgrade of an customer environment.

BTW: in 6.7 releases it can happen that NICs get a new numbering after an update. This also leads to no access to iSCSI storage.

Based on this VMware KB, this issue only exists in vSphere 7.0 U1. vSphere 6.7 and 7.0 are not affected during upgrade to 7.0 U2.

Yes, its another issue.

Wolfgang | vnote42.net | @vNote42

+21

Chris.Childerhose
Veeam Legend, Veeam Vanguard
8482 comments
3 years ago
January 12, 2022

Yeah had this issue in my homelab when upgrading. Nice to see it shared here.

Comment

Related topics

How to tuning my theater # SONOS ARC + Sub(Gen3) + ERA300icon

Trueplay in Home Theatericon

Era 300 right on the edge of which way to mounticon

Arc Ultra + Sub Gen 3 : Sub less powerful than before !?icon

Arc ULTRA - lack of bass with sub gen 3icon

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded