Here the issue is your Windows host is registered twice - one was earlier with the Old IP address and then the second one is with the new IP Address.
Since the IP Address got changed, Navisphere considered it as a seperate host.
To fix this issue - as Glen suggested, please go ahead and deregister the old initiator records which are grayed out now because that Host is no longer available on the network to be managed using the old IP Address.
The deregistration of these initiator records will not cause any issue at all - but will clean the records. It does not matter whether they were auto-registered or manually registered earlier.
On the storage group - ensure that the new host is connected to the storage group and all the paths are selected. You may have to check this out manually.
You may have to restart the management server on both SPs one more time after doing all these.
Please feel free to open a service request, if you are not feeling comfortable doing so on your own.
Sorry to participate in this discussion so late - but hopefully your issue will be resolved soon. Thanks, Sandip
Are you sure ? He's talking about a service on the Clariion itself, not the management pc next to the Clariion. Restarting an agent on the CX should be the trick here.
So go to http:// /setup and restart the management agent. Do this for both SP's.
Try stopping the host (power off). Remove the host from the Storage Group, then in Connectivity Status de-register all the entries for the host. Then power on host.
On the host, have you added the "agentID.txt" file at any time in the past? What type of host - Windows/Unix? If Windows check in the c:\emc\Navisphere Agent directory for this file - if Unix, see if the file is in root.
this is windows box. If I de register all the entries for this host. when the host boots up will it have a new entry and if I add this new host will there be any data loss or data corruption can happen? this is a Prod Frame.
There shouldn't be any data loss, since this is merely a host registration issue. Once the host is connected over FC, the data is available, whether or not the ip connectivity is ok isn't that important. Ip connectivity is only to make the registration process less painfull. I must say I almost never use the Navi agent. I register the hosts manually in 99% of the cases, since my customers are rather small and at all of their sites we hardly change hosts, so the work involved is limited to a minimum anyway.
I am okay with deregistering the old(grayed out) initiator. but the problem is in the storage group under host region its showing the old host(unmanaged) not the new(managed) one.
so if I remove the unmanaged host from the storage group, de-registered the initiors and added the host(new) again to the storage group. is this what you are saying?
when we add the host(managed) to the storage group will it be see the same disk with out any issues. since we are de-registering the host(unmanaged) and adding it again.
I wanted to try it out and learn before open an SR....
nandas
4 Operator
•
1.5K Posts
0
July 31st, 2009 08:00
Here the issue is your Windows host is registered twice - one was earlier with the Old IP address and then the second one is with the new IP Address.
Since the IP Address got changed, Navisphere considered it as a seperate host.
To fix this issue - as Glen suggested, please go ahead and deregister the old initiator records which are grayed out now because that Host is no longer available on the network to be managed using the old IP Address.
The deregistration of these initiator records will not cause any issue at all - but will clean the records. It does not matter whether they were auto-registered or manually registered earlier.
On the storage group - ensure that the new host is connected to the storage group and all the paths are selected. You may have to check this out manually.
You may have to restart the management server on both SPs one more time after doing all these.
Please feel free to open a service request, if you are not feeling comfortable doing so on your own.
Sorry to participate in this discussion so late - but hopefully your issue will be resolved soon.
Thanks,
Sandip
dynamox
9 Legend
•
20.4K Posts
0
July 24th, 2009 03:00
dynamox
9 Legend
•
20.4K Posts
0
July 24th, 2009 03:00
modaslam
2 Intern
•
217 Posts
0
July 24th, 2009 03:00
modaslam
2 Intern
•
217 Posts
0
July 24th, 2009 04:00
RRR
4 Operator
•
5.7K Posts
0
July 24th, 2009 04:00
So go to http:// /setup and restart the management agent. Do this for both SP's.
modaslam
2 Intern
•
217 Posts
0
July 24th, 2009 08:00
Yes I had restared the management agent(both SPA and B). that was a my mistake mentioning about station instead of service.
After pulling all the logs its found that the ip was changed
now how do we go about this...
the host under the storage group is un managed. but in the host I have double entries one is unmanaged other one is fine..
is there any way to swap this?
kelleg
4 Operator
•
4.5K Posts
1
July 24th, 2009 09:00
On the host, have you added the "agentID.txt" file at any time in the past? What type of host - Windows/Unix? If Windows check in the c:\emc\Navisphere Agent directory for this file - if Unix, see if the file is in root.
glen
modaslam
2 Intern
•
217 Posts
0
July 25th, 2009 11:00
RRR
4 Operator
•
5.7K Posts
0
July 27th, 2009 02:00
ALU4
10 Posts
0
July 29th, 2009 05:00
Did you try the button reconnect in Connectivity Status window?
Regards,
Chris
modaslam
2 Intern
•
217 Posts
0
July 30th, 2009 14:00
as in the previous post, he said me to de-register the hba. thats what I am afraid of.
Our policy states no manual registration. its allowed only if the navi agent is not present in case like celerra and all.
modaslam
2 Intern
•
217 Posts
0
July 30th, 2009 14:00
RRR
4 Operator
•
5.7K Posts
0
July 30th, 2009 14:00
modaslam
2 Intern
•
217 Posts
0
August 2nd, 2009 23:00
I am okay with deregistering the old(grayed out) initiator. but the problem is in the storage group under host region its showing the old host(unmanaged) not the new(managed) one.
so if I remove the unmanaged host from the storage group, de-registered the initiors and added the host(new) again to the storage group. is this what you are saying?
when we add the host(managed) to the storage group will it be see the same disk with out any issues. since we are de-registering the host(unmanaged) and adding it again.
I wanted to try it out and learn before open an SR....