Modifying a LIF
You can modify a LIF by changing the attributes, such as home node or current node, administrative status, IP address, netmask, failover policy, firewall policy, and service policy. You can also change the address family of a LIF from IPv4 to IPv6.
About this task
When modifying a LIF's administrative status to down , any outstanding NFSv4 locks are held until the LIF's administrative status is returned to up .
To avoid lock conflicts that can occur when other LIFs attempt to access the locked files, you must move the NFSv4 clients to a different LIF before setting the administrative status to down .
You cannot modify the data protocols used by a LIF.
To modify the data protocols used by a LIF, you must delete and re-create the LIF.
You cannot modify either the home node or the current node of a node management LIF.
You do not specify the home node when modifying the home port of a cluster LIF.
When using a subnet to change the IP address and network mask value for a LIF, an IP address is allocated from the specified subnet; if the LIF's previous IP address is from a different subnet, the IP address is returned to that subnet.
To modify the address family of a LIF from IPv4 to IPv6, you must use the colon notation for the IPv6 address and add a new value for the -netmask-length parameter.
You cannot modify the auto-configured link-local IPv6 addresses.
Modification of a LIF that results in the LIF having no valid failover target results in a warning message.
If a LIF that does not have a valid failover target attempts to fail over, an outage might occur.
Starting with ONTAP 9.5, you can modify the service policy associated with a LIF.
In ONTAP 9.5, service policies are supported only for intercluster and BGP peer services. In ONTAP 9.6 and later, you can create service policies for several data and management services.