title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | ||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Change IP Address of a Failover Cluster Instance |
Learn how to change the IP address of a SQL Server failover cluster instance using the Failover Cluster Manager. |
MashaMSFT |
mathoma |
03/14/2017 |
sql |
failover-cluster-instance |
how-to |
|
[!INCLUDE SQL Server] This topic describes how to change the IP address resource in an Always On Failover Cluster Instance (FCI) by using the Failover Cluster Manager snap-in. The Failover Cluster Manager snap-in is the cluster management application for the Windows Server Failover Clustering (WSFC) service.
- Before you begin: Security
Before you begin, review the following [!INCLUDEssNoVersion] Books Online topic: Before Installing Failover Clustering.
To maintain or update an FCI, you must be a local administrator with permission to logon as a service on all nodes of the FCI.
To change the IP address resource for an FCI
-
Open the Failover Cluster Manager snap-in.
-
Expand the Services and applications node, in the left pane and click on the FCI.
-
On the right pane, under the Server Name category, right-click the SQL Server Instance, and select Properties option to open the Properties dialog box.
-
On the General tab, change the IP address resource.
-
Click OK to close the dialog box.
-
In the right-hand pane, right-click the SQL IP Address1(failover cluster instance name) and select Take Offline. You will see the SQL IP Address1(failover cluster instance name), SQL Network Name(failover cluster instance name), and [!INCLUDEssNoVersion] status change from Online to Offline Pending, and then to Offline.
-
In the right-hand pane, right-click [!INCLUDEssNoVersion], and then select Bring Online. You will see the SQL IP Address1(failover cluster instance name), SQL Network Name(failover cluster instance name), and [!INCLUDEssNoVersion] status change from Offline to Online Pending, and then to Online.
-
Close the Failover Cluster Manager snap-in.