U means unmanaged. Did something change on the network ? Are the Storage Processors pingable from the host ? If somehow a firewall is inbetween or the subnets are not connected at all, the U appears.
If you find a particular answer helpful, please mark them as such to point out these answers as valuable for future generations
Has the Navisphere agent been installed on the server or, on the contrary, has it been manually registered in Clariion Connectivity status?
If the host has manually been registered, it is normaly to get the U (Unmanaged) since no TCP/IP communication exists between host and clariion. On the other hand, it the agent is configured and there are no connectivity issues, or FWs, in between, try to restart the Navisphere agent in the host to see if the communication is restored between the host and clariion agents. In any case, this U status is harmless since once the host has been regsitered it is not very useful anymore...
I ve seen these cases wherin a simple restart of NaviAgent fix the trouble.
Make sure that these ports are open *Ports 6389, 6390, 6391,and 6392. Make sure that the firewall is not blocking the ports. Opening the port in firewall several times resolves the issue.
Restart Navisphere Host Agent Service from services.msc.
sasamir1
234 Posts
0
July 16th, 2011 22:00
Hi,
Did you try to right click the host in Storage group and click on Reconnect. Also try Update now with Update host information ticked.
hope this helps.
regards,
Samir
RRR
1 Rookie
1 Rookie
•
5.7K Posts
0
August 11th, 2011 00:00
U means unmanaged. Did something change on the network ? Are the Storage Processors pingable from the host ? If somehow a firewall is inbetween or the subnets are not connected at all, the U appears.
If you find a particular answer helpful, please mark them as such to point out these answers as valuable for future generations
tdubb123
470 Posts
0
August 28th, 2011 11:00
all sps are pingable. sps and hosts are on different vlans but no fw inbetween blocking access
felipon1
96 Posts
0
August 29th, 2011 01:00
Hi,
Has the Navisphere agent been installed on the server or, on the contrary, has it been manually registered in Clariion Connectivity status?
If the host has manually been registered, it is normaly to get the U (Unmanaged) since no TCP/IP communication exists between host and clariion. On the other hand, it the agent is configured and there are no connectivity issues, or FWs, in between, try to restart the Navisphere agent in the host to see if the communication is restored between the host and clariion agents. In any case, this U status is harmless since once the host has been regsitered it is not very useful anymore...
Sheron1
224 Posts
0
September 20th, 2012 05:00
How are these host registered?
I ve seen these cases wherin a simple restart of NaviAgent fix the trouble.
Make sure that these ports are open *Ports 6389, 6390, 6391,and 6392. Make sure that the firewall is not blocking the ports. Opening the port in firewall several times resolves the issue.
Restart Navisphere Host Agent Service from services.msc.
Regards,
Sheron Godfred.