Loading...
Loading...
HPE Synergy Image Streamer – In Synergy multi-frame configurations that host Image Streamer appliances, ESXi hosts deployed using Image Streamer may lose connectivity to their boot volumes when the Master Interconnect module is unavailable. To resolve this issue, ESXi multipathing (MPIO) configuration is needed for the Image Streamer deployment iSCSI connections that are configured during Server Profile creation.In a typical Synergy Setup with Image Streamer, where ESXi hosts are deployed with Interconnect Modules configured in HA mode, the unavailability of a Master Interconnect module may result in iSCSI path failures on the hosts.In this scenario, the hypervisor continues to run the workload; however, any host configuration changes will not be saved to persistent storage until the path becomes Active. When this occurs, the following message can be seen on the vCenter Host summary page:
Any HPE Image Streamer firmware versions 4.00.xx and 4.10.xx and all HPE IHPE Image Streamer supported ESXi versions.
HPE highly recommends using the latest ESXi Artifact bundle for all ESXi deployments to avoid encountering this issueNote: The latest ESXi artifact bundle for 4.0 is HPE-ESXi-2018-07-31-v4.0.zip and the latest ESXi artifact bundle for 4.1 is HPE-ESXi-2018-07-31-v4.1.zipFor existing ESXi deployments, perform one of the options below to configure multipathing (MPIO) on the ESXi Host:Reapply the server profile (redeploy the ESXi host) using the MPIO enabled Image Streamer Deployment Plan and Scripts.MPIO using CLI.MPIO using vCenter.Note: A vCenter alert, "Lost connectivity to the device naa.6001f93107808000ad0002000 backing the boot filesystem /vmfs/devices/disks/naa.naa.6001f93107808000ad0002000. As a result, host configuration changes will not be saved to persistent" is expected. This alert will clear only after host reboot attempted to or restarted the ESXi host management agent.Option 1:Reapply the server profile (redeploy the ESXi host) using the MPIO enabled Image Streamer Deployment Plan and Scripts.Redeploy ESXi hosts using HPE provided latest ESXi artifact bundle uploaded at below location.4.0 Buildhttps://github.com/HewlettPackard/image-streamer-esxi/blob/v4.0/artifact-bundles/HPE-ESXi-2018-07-31-v4.0.zip4.1 Buildhttps://github.com/HewlettPackard/image-streamer-esxi/blob/v4.1/artifact-bundles/HPE-ESXi-2018-07-31-v4.1.zipORCreate new plan script with iSCSI configuration -> add to existing Build Plan and redeploy the ESXi host.Sample plan script with iSCSI configuration:#HPE - ESXi - mpio - configure iSCI boot HAesxcli network vswitch standard uplink add --uplink-name=vmnic0 --vswitch-name=vSwitch0esxcli network vswitch standard uplink add --uplink-name=vmnic1 --vswitch-name=vSwitch0esxcfg-vmknic -d "Management Network" # Removes vmk0 and converts Management Network as Port Groupesxcfg-vswitch -D "Management Network" vSwitch0 # deletes the Port Group Management Networkesxcfg-vswitch -A iSCSI-PG1 vSwitch0esxcfg-vswitch -A iSCSI-PG2 vSwitch0esxcfg-vswitch -N vmnic0 -p iSCSI-PG1 vSwitch0 # Moves vmnic0 to unused Adapter for Port Group iSCSI-PG1esxcfg-vswitch -N vmnic1 -p iSCSI-PG1 vSwitch0esxcfg-vswitch -N vmnic0 -p iSCSI-PG2 vSwitch0esxcfg-vswitch -N vmnic1 -p iSCSI-PG2 vSwitch0esxcfg-vswitch -M vmnic0 -p iSCSI-PG1 vSwitch0 # Makes vmnic0 as active adapter for Port Group iSCSI-PG1esxcfg-vswitch -M vmnic1 -p iSCSI-PG2 vSwitch0 # Makes vmnic1 as active adapter for Port Group iSCSI-PG2# Assign an IP address to the port groupsesxcfg-vmknic -a -i @_Initiator1.ip@ -n @_Initiator1.netmask@ iSCSI-PG1esxcfg-vmknic -a -i @_Initiator2.ip@ -n @_Initiator2.netmask@ iSCSI-PG2esxcli iscsi software set -e trueiscsi_adapter=`esxcfg-scsidevs -a | grep "iSCSI Software Adapter" | awk '{ print $1 }'`esxcli iscsi networkportal add --nic vmk0 --adapter "${iscsi_adapter}"esxcli iscsi networkportal add --nic vmk1 --adapter "${iscsi_adapter}"esxcli iscsi session remove --adapter "${iscsi_adapter}"esxcli iscsi session add --adapter "${iscsi_adapter}"esxcfg-rescan -Aesxcfg-rescan –A#EndOption 2: MPIO Using the CLI:1. Log into OneView, Navigate to Server Profile -> Connections page -> Expand Deployment Network A and Deployment Network B.2. Record the Initiator IP address and Initiator subnet mask from Deployment Network A and Deployment Network B from connections section on the server profile page and replace recorded values with the below example:In the example, replace the above recorded values with Initiator IP address and subnet mask:Deployment Network A(vmkernel portgroup “iSCSI-PG1”)Initiator IP address: 10.10.7.40Initiator Subnet mask: 255.255.255.0Deployment Network B(vmkernel portgroup “iSCSI-PG2”)Initiator IP address: 10.10.7.41Initiator Subnet mask: 255.255.255.03. Login SSH session to ESXi host >> Execute below commands.Execute below commands to add vmnic0 and vmnic1 to vSwitch0 (Active / Active).esxcli network vswitch standard uplink add --uplink-name=vmnic0 --vswitch-name=vSwitch0esxcli network vswitch standard uplink add --uplink-name=vmnic1 --vswitch-name=vSwitch0esxcli network vswitch standard policy failover set -a vmnic0,vmnic1 -v vSwitch0Execute below commands to create vmkernel portgroup name “iSCSI-PG2”.esxcfg-vswitch -A iSCSI-PG2 vSwitch0Execute below commands to assign ip address to vmkernel portgroup “iSCSI-PG2”. (Refer to Step No: 2 for Initiator IP address and Subnet mask).esxcfg-vmknic -a -i <Deployment Network B initiator IP> -n <Deployment Network B initiator subenetmask> iSCSI-PG2Execute below commands to assign vmnic1 as active and vmnic0 as unused for vmkernel portgroup “iSCSI-PG2” on vSwitch0.esxcfg-vswitch -M vmnic1 -p iSCSI-PG2 vSwitch0esxcfg-vswitch -N vmnic0 -p iSCSI-PG2 vSwitch0Execute below commands to delete and recreate vmkernel portgroup name“iSCSI-PG1”. (Refer Step No: 2 for Initiator IP address and Subnet mask).esxcfg-vmknic -d "Management Network"esxcfg-vswitch -D "Management Network" vSwitch0esxcfg-vswitch -A iSCSI-PG1 vSwitch0esxcfg-vmknic -a -i <Deployment Network A initiator IP-n <Deployment Network A initiator subenetmask> iSCSI-PG1esxcfg-vswitch -N vmnic1 -p iSCSI-PG1 vSwitch0Execute below commands to Storage adapters network port binding.esxcli iscsi adapter list (RecordiSCSI Software adapter name, UID“oneview” as highlighted as below)esxcli iscsi software set -e trueesxcli iscsi networkportal add --nic vmk0 --adapter <Name of the iscsi software adapter>esxcli iscsi networkportal add --nic vmk1 --adapter <Name of the iscsi software adapter>Execute below commands to rescan storage adapter:esxcfg-rescan –AExecute the following command to verify MPIO configuration: esxcli iscsi networkportal listExample Result: (You will notice twoActivepaths have been added)[root@esxi-mpio:~] esxcli iscsi networkportal listvmhbaXXAdapter: vmhbaXXVmknic:vmk0IPv4: 10.10.7.30IPv4 Subnet Mask: 255.255.255.0Compliant Status:compliantNonCompliant Message:NonCompliant Remedy:Vswitch:vSwitch0PortGroup:iSCSI-PG1Path Status:activevmhbaXXAdapter: vmhbaXXVmknic:vmk1IPv4: 10.10.7.31IPv4 Subnet Mask: 255.255.255.0Compliant Status:compliantNonCompliant Message:NonCompliant Remedy:Vswitch:vSwitch0PortGroup:iSCSI-PG2Path Status:activeOption 3: MPIO Using vCenter1. Log into vCenter Server using Web Client:https://<vcenterIP address>/vsphere-client/?csp2. Navigate to Host and Cluster view. Assuming that ESXi host has been added to vCenter server.3. Select Host from the Inventory page and Navigate to Configure tab >> Virtual switches >>vSwitch0and select Manage Physical Network Adapters for vSwitch0 as highlighted below.4. Click on Add button to addvmnic1and make sure “Failover order group” isActive adapters.Make sure Network adaptersvmnic0andvmnic1assigned asActive adapter. If not, Select appropriate Move UP Move Down button to make adapters Active.Login to OneView, Navigate to Server Profile >> Connections page >> Expand Deployment Network A and Deployment Network B.Record the Initiator IP address and Initiator subnet mask from Deployment Network A and Deployment Network B from connections section on the server profile page and replace recorded values with below Example.Example: (Replace above recorded values with Initiator IP address and Subnet mask)Example: (Replace above recorded values with Initiator IP address and Subnet mask)Deployment Network Avmkernel portgroup “iSCSI-PG1”)Initiator IP address: 10.10.7.40Initiator Subnet mask: 255.255.255.0Deployment Network B(vmkernel portgroup “iSCSI-PG2”)Initiator IP address: 10.10.7.41Initiator Subnet mask: 255.255.255.08. Login to vCenter and Select Host from Inventory page and Navigate to Configure tab >> Virtual switches >>vSwitch0>> clickManagement Network>> Edit as highlighted below.9. Properties tab >> Edit Network Label asiSCSI-PG1and Navigate to Teaming and failover tab.10. Select “Teaming and failover” tab and move downvmnic1toUnused adaptersas below and click OK.11. Select Host from Inventory page and Navigate to Configure tab >> Virtual switches >> selectvSwitch0>> Click Add Host networking to create VMkernel portgroup.11. Select VMkernel Network Adapter >> Click Next.12. Browse and select vSwitch0 >> Click Next.13. Type Network label asiSCSI-PG2>> Click Next.14. Select “Use static IPV4 settings” and enter IP address and Subnet mask of Deployment Network B initiator which was mentioned inStep No: 7Example >> Click Next >> Click Finish.15. Select Host from Inventory page and Navigate to Configure tab >> Virtual switches >> vSwitch0 >> clickiSCSI-PG2>> Edit as highlighted below.16. Select “Teaming and failover” tab >> select all Override check Box >> move downvmnic0toUnused adaptersas below and click OK.17. Select Host from Inventory page and Navigate to Configure tab >> Storage Adapters >> selectvmhbaXXunder iSCSI Software Adapter (Select the adapter which shows identifier “oneview”) >> Click “Network Port Binding” tab.18. Click Add button to Bind VMkernel Adapter >> SelectiSCSI-PG1(vSwitch0)andiSCSI-PG2(vSwitch0)>> Click OK.19. Warning message pops up “Due to recent configuration changes, a rescan of this storage adapter is recommended” >> Click “Rescan storage adapter”. After rescan both adapter Path Status will be shown as “Active”.20. Storage Adapters page >>Select iSCSCI software adaptervmhbaXX>> Select “Paths” tab. You will notice two Active paths have been added for lefthand networks.
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
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.