|Article Number: 482960||Article Version: 3||Article Type: Break Fix|
Unisphere Service Manager,VNX1 Series,VNX2 Series
User was not aware that someone had changed the SP name awhen he noticed that the SP rebooted.
By checking the log, it looks like SP reboot was requested from itself. The IP address is SPA/SPB itself.
A 04/07/16 18:13:39 NaviAgent 1 RebootSP requested from IP 1X2.2X.X.X4.
A 04/07/16 18:14:26 NaviAgent 1 WARNING: Reboot requested. SP(s) going down. SP type=4 (this)
B 04/07/16 18:14:33 NaviAgent 1 RebootSP requested from IP 1X2.2X.X.X5.
A 04/07/16 18:14:39 NaviCimom 79XXX000 Reboot: 50XXX160-bea069fa; 0
B 04/07/16 18:15:01 NaviAgent 1 WARNING: Reboot requested. SP(s) going down. SP type=4 (this)
Similar to Windows, changing a SP name requires a reboot.
A 04/07/16 18:16:45 EventLog 177b The NetBIOS name and DNS host name of this machine have been changed from RXXX to OXXXNX400–SPA.
B 04/07/16 18:17:52 EventLog 177b The NetBIOS name and DNS host name of this machine have been changed from BXXXAGE to OXXXNX400-SPB.
SP name is changed.
SP reboot after changing SP name works as designed.
In this case, have the user confer with his team members and confirm if someone else changed the SP name.