UNSOLVED
Wonky Unisphere issue
Hello,
We have a situation where we are working with some VM that have varied unisphere agent versions. The vms that have version 1.3 have an issue where they inherit a different host name and IP, yet they work. The host connected shows all initiators green, yet I do not see that host name in the connect hosts panel for both non connected and connected. The upgrade of unisphere on those hosts was done after I initially presented the storage and by the Windows team. The hosts are running windows 2012.
So the storage group points to another host name and IP. We get these capital letter names from the windows hosts when Unisphere is installed. The thing is the IP/host that is referred to incorrectly in the storage groups is no longer up and ruuning on the array.
So the issue(best described in pictures).
co-ds-sql-d18 is the decommissioned host and storage group that is incorrectly referred to in the storage group.
co-ds-sql-d17 is one of four hosts having the issue. co-ds-sql-d17 is used for this discussion. All four hosts having the issue have 1.3.X(early version of unisphere 3, from 2013) installed.
I have to migrate these VMs to another cluster on the VNX and I am leery to do anything with the hosts since the storage group is not correct.
653
0
Posted July 22nd, 2016 09:00
Thank you! I will look at the KBs now. The thing is it doesn't happen for VMs using unisphere 1.2
653
0
Posted July 22nd, 2016 10:00
Hi Glen,
I am not able to view the documents.
Admingirl
653
1
Posted July 22nd, 2016 12:00
Sorry - the links are not working - copy/paste the link into a new browser window and see if that works
glen
653
0
Posted July 22nd, 2016 13:00
Thank you Glen, I can access the docs now. Is this still true about the agent for 2012 R2 and VMs This is from KB Article Number 000444341The issue on Windows 2012 is as expected. Since Release 32 Host Agent
doesn't know the existence of Windows 2012, this issue will be resolved
by Release 33 Host Agent.The first release of the Host Agent for
Release 33 only supports Windows 2012 R1, it does not yet support R2.Windows Server 2012 has a new feature for Hyper-V which can create a
virtual FC port for Hyper-V VM. Release32 Host Agent doesn't support the
virtual FC port registration for Windows 2012 Hyper-V VM.
653
0
Posted July 22nd, 2016 13:00
Thanks Glen, I will work with our windows to check this.
Is 2012 R2 for VMs using virtual fiber channel only supported fully under OE 5.33?
653
1
Posted July 22nd, 2016 13:00
The latest Host Agent supports 2012 R2.
What I think the issue may be the VM's are clone images - that would mean that the hostID.txt file contains the same information each time you start a new VM.
glen
653
0
Posted July 22nd, 2016 13:00
Yes
kelleg
6 Operator
•
4537 Posts
653
1
Posted July 22nd, 2016 09:00
It sounds like you may have a closed host issue. See the below KBs - the first one talks about what happens when you used closed hosts for VM's
https://support.emc.com/kb/323174
https://support.emc.com/kb/428717
https://support.emc.com/kb/444341
Master KB for Host Agent issues:
https://support.emc.com/kb/468319
glen