Update an IP interface
PATCH /network/ip/interfaces/{uuid}
Introduced In: 9.6
Updates an IP interface.
Related ONTAP commands
-
network interface migrate
-
network interface modify
-
network interface rename
-
network interface revert
Parameters
Name | Type | In | Required | Description |
---|---|---|---|---|
uuid |
string |
path |
True |
IP interface UUID |
Request Body
Name | Type | Description |
---|---|---|
_links |
||
ddns_enabled |
boolean |
Indicates whether or not dynamic DNS updates are enabled. Defaults to true if the interface supports "data_nfs" or "data_cifs" services, otherwise false. |
dns_zone |
string |
Fully qualified DNS zone name |
enabled |
boolean |
The administrative state of the interface. |
ip |
IP information |
|
ipspace |
Either the UUID or name must be supplied on POST for cluster-scoped objects. |
|
location |
Current or home location can be modified. Specifying a port implies a node. Specifying a node allows an appropriate port to be automatically selected. Ports are not valid and not shown for VIP interfaces. For POST, broadcast_domain can be specified alone or with home_node. For PATCH, set is_home to true to revert a LIF back to its home port. |
|
metric |
The most recent sample of I/O metrics for the interface. |
|
name |
string |
Interface name |
probe_port |
integer |
Probe port for Cloud load balancer |
rdma_protocols |
array[string] |
Supported RDMA offload protocols |
scope |
string |
Set to "svm" for interfaces owned by an SVM. Otherwise, set to "cluster". |
service_policy |
||
services |
array[string] |
The services associated with the interface. |
state |
string |
The operational state of the interface. |
statistics |
The real time I/O statistics for the interface. |
|
svm |
Applies only to SVM-scoped objects. Either the UUID or name must be supplied on POST. |
|
uuid |
string |
The UUID that uniquely identifies the interface. |
vip |
boolean |
True for a VIP interface, whose location is announced via BGP. |
Example request
{
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"dns_zone": "storage.company.com",
"ip": {
"address": "10.10.10.7",
"family": "string",
"netmask": "24"
},
"ipspace": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "exchange",
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
},
"location": {
"broadcast_domain": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "bd1",
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
},
"failover": "string",
"home_node": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "node1",
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
},
"home_port": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "e1b",
"node": {
"name": "node1"
},
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
},
"node": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "node1",
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
},
"port": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "e1b",
"node": {
"name": "node1"
},
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
}
},
"metric": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"duration": "PT15S",
"status": "ok",
"throughput": {
"read": 200,
"total": 1000,
"write": 100
},
"timestamp": "2017-01-25T11:20:13Z"
},
"name": "dataLif1",
"probe_port": 64001,
"rdma_protocols": [
"roce"
],
"scope": "string",
"service_policy": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "default-intercluster",
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
},
"services": [
"data_nfs"
],
"state": "string",
"statistics": {
"status": "ok",
"throughput_raw": {
"read": 200,
"total": 1000,
"write": 100
},
"timestamp": "2017-01-25T11:20:13Z"
},
"svm": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"name": "svm1",
"uuid": "02c9e252-41be-11e9-81d5-00a0986138f7"
},
"uuid": "1cd8a442-86d1-11e0-ae1c-123478563412"
}
Response
Status: 200, Ok
Error
Status: Default
ONTAP Error Response Codes
Error Code | Description |
---|---|
1376663 |
Cannot add interface to DNS zone because all interfaces from a single DNS zone must be in the same SVM. |
1376963 |
Duplicate IP address. |
1376997 |
Interface failed to migrate because the node hosting the port is not healthy. |
1376998 |
The specified location.node does not own any ports in the same broadcast domain as the home port of the interface. |
1376999 |
Interface failed to migrate because port is in the down admin state. |
1377607 |
The specified location.port is not in the same broadcast domain as the home port of the interface. |
1966138 |
The same IP address may not be used for both a mgmt interface and a gateway address. |
1966141 |
Invalid DNS zone name. |
1966142 |
Only data LIFs can be assigned a DNS zone. |
1966197 |
Migration of cluster interfaces must be done from the local node. |
1966267 |
IPv6 addresses must have a prefix length between 1 and 127. |
1966269 |
IPv4 addresses must have a prefix length between 1 and 32. |
1966476 |
DNS Update is supported only on data interfaces. |
1966477 |
DNS Update is supported only on interfaces configured with the NFS or CIFS protocol. |
1967106 |
The specified location.home_port.name does not match the specified port name of location.home_port.uuid. |
1967107 |
The specified location.home_port.uuid is not valid. |
1967111 |
A home node must be specified by at least one location.home_node, location.home_port, or location.broadcast_domain field. |
1967113 |
The specified location.port.name does not match the port name of location.port.uuid. |
1967114 |
The specified location.port.uuid is not valid. |
1967115 |
The specified location.node.name does not match the node name of location.node.uuid. |
1967116 |
The specified location.port.node.name does not match the node name of location.node.uuid. |
1967117 |
The specified location.port.node.name does not match location.node.name. |
1967118 |
A node must be specified by at least one location.node or location.port field. |
1967119 |
The specified location.node.name does not match the node name of location.port.uuid. |
1967120 |
The specified service_policy.name does not match the specified service policy name of service_policy.uuid. |
1967121 |
The specified service_policy.uuid is not valid. |
1967125 |
You cannot patch the "location.node" or "location.port" fields to migrate interfaces using the iSCSI data protocol. Instead perform the following PATCH operations on the interface: set the "enabled" field to "false"; change one or more "location.home_port" fields to migrate the interface; and then set the "enabled" field to "true". |
1967129 |
The specified location.home_port.uuid is not valid. |
1967130 |
The specified location.home_port.name is not valid. |
1967131 |
The specified location.home_port.uuid and location.home_port.name are not valid. |
1967132 |
The specified location.port.uuid is not valid. |
1967133 |
The specified location.port.name is not valid. |
1967134 |
The specified location.port.uuid and location.port.name are not valid. |
1967138 |
Cannot patch port for a VIP interface. The specified parameter location.port.uuid is not valid. |
1967139 |
Cannot patch port for a VIP interface. The specified parameter location.port.name is not valid. |
1967140 |
Cannot patch port for a VIP interface. The specified parameters location.port.uuid and location.port.name are not valid. |
1967141 |
Cannot patch home_port for a VIP interface. The specified parameter location.home_port.uuid is not valid. |
1967142 |
Cannot patch home_port for a VIP interface. The specified parameter location.home_port.name is not valid. |
1967143 |
Cannot patch home_port for a VIP interface. The specified parameters location.home_port.uuid and location.home_port.name are not valid. |
1967145 |
The specified location.failover is not valid. |
1967153 |
No suitable port exists on location.home_node to host the interface. |
1967380 |
Cannot patch home_port for a VIP interface. The specified parameter location.home_port.node.name is not valid. Consider using location.home_node.name instead. |
1967386 |
Cannot patch port for a VIP interface. The specified parameter location.port.node.name is not valid. Consider using location.node.name instead. |
1967387 |
The specified IP address is in use by a subnet in this IPspace. |
1967389 |
Patching location.is_home to the value "false" is not supported. The value "true" would revert a network interface to its home port if the current value is "false". |
1967390 |
Cannot patch a LIF revert as it requires an effective cluster version of 9.9.1 or later. |
1967391 |
Patching the DNS zone requires an effective cluster version of 9.9.1 or later. |
1967392 |
Patching the DDNS enable parameter requires an effective cluster version of 9.9.1 or later. |
53281065 |
The service_policy does not exist in the SVM. |
53281086 |
LIF would exceed the maximum number of supported intercluster LIFs in IPspace. |
53281089 |
LIF on SVM cannot be updated to use service policy because that service policy includes SAN services and the target LIF is not home. |
Definitions
See Definitions
href
Name | Type | Description |
---|---|---|
href |
string |
_links
Name | Type | Description |
---|---|---|
self |
ip_info
IP information
Name | Type | Description |
---|---|---|
address |
string |
IPv4 or IPv6 address |
family |
string |
IPv4 or IPv6 |
netmask |
string |
Input as netmask length (16) or IPv4 mask (255.255.0.0). For IPv6, the default value is 64 with a valid range of 1 to 127. Output is always netmask length. |
ipspace
Either the UUID or name must be supplied on POST for cluster-scoped objects.
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
IPspace name |
uuid |
string |
IPspace UUID |
broadcast_domain
Broadcast domain UUID along with a readable name.
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
Name of the broadcast domain, scoped to its IPspace |
uuid |
string |
Broadcast domain UUID |
home_node
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
|
uuid |
string |
node
Name | Type | Description |
---|---|---|
name |
string |
Name of node on which the port is located. |
home_port
Port UUID along with readable names. Either the UUID or both names may be supplied on input.
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
|
node |
||
uuid |
string |
node
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
|
uuid |
string |
port
Port UUID along with readable names. Either the UUID or both names may be supplied on input.
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
|
node |
||
uuid |
string |
location
Current or home location can be modified. Specifying a port implies a node. Specifying a node allows an appropriate port to be automatically selected. Ports are not valid and not shown for VIP interfaces. For POST, broadcast_domain can be specified alone or with home_node. For PATCH, set is_home to true to revert a LIF back to its home port.
Name | Type | Description |
---|---|---|
auto_revert |
boolean |
|
broadcast_domain |
Broadcast domain UUID along with a readable name. |
|
failover |
string |
Defines where an interface may failover. |
home_node |
||
home_port |
Port UUID along with readable names. Either the UUID or both names may be supplied on input. |
|
is_home |
boolean |
|
node |
||
port |
Port UUID along with readable names. Either the UUID or both names may be supplied on input. |
throughput
The rate of throughput bytes per second observed at the interface.
Name | Type | Description |
---|---|---|
read |
integer |
Performance metric for read I/O operations. |
total |
integer |
Performance metric aggregated over all types of I/O operations. |
write |
integer |
Peformance metric for write I/O operations. |
metric
The most recent sample of I/O metrics for the interface.
Name | Type | Description |
---|---|---|
_links |
||
duration |
string |
The duration over which this sample is calculated. The time durations are represented in the ISO-8601 standard format. Samples can be calculated over the following durations: |
status |
string |
Errors associated with the sample. For example, if the aggregation of data over multiple nodes fails, then any partial errors might return "ok" on success or "error" on an internal uncategorized failure. Whenever a sample collection is missed but done at a later time, it is back filled to the previous 15 second timestamp and tagged with "backfilled_data". "inconsistent_delta_time" is encountered when the time between two collections is not the same for all nodes. Therefore, the aggregated value might be over or under inflated. "Negative_delta" is returned when an expected monotonically increasing value has decreased in value. "inconsistent_old_data" is returned when one or more nodes do not have the latest data. |
throughput |
The rate of throughput bytes per second observed at the interface. |
|
timestamp |
string |
The timestamp of the performance data. |
service_policy
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
|
uuid |
string |
throughput_raw
Throughput bytes observed at the interface. This can be used along with delta time to calculate the rate of throughput bytes per unit of time.
Name | Type | Description |
---|---|---|
read |
integer |
Performance metric for read I/O operations. |
total |
integer |
Performance metric aggregated over all types of I/O operations. |
write |
integer |
Peformance metric for write I/O operations. |
statistics
The real time I/O statistics for the interface.
Name | Type | Description |
---|---|---|
status |
string |
Errors associated with the sample. For example, if the aggregation of data over multiple nodes fails, then any partial errors might return "ok" on success or "error" on an internal uncategorized failure. Whenever a sample collection is missed but done at a later time, it is back filled to the previous 15 second timestamp and tagged with "backfilled_data". "inconsistent_delta_time" is encountered when the time between two collections is not the same for all nodes. Therefore, the aggregated value might be over or under inflated. "Negative_delta" is returned when an expected monotonically increasing value has decreased in value. "inconsistent_old_data" is returned when one or more nodes do not have the latest data. |
throughput_raw |
Throughput bytes observed at the interface. This can be used along with delta time to calculate the rate of throughput bytes per unit of time. |
|
timestamp |
string |
The timestamp of the performance data. |
svm
Applies only to SVM-scoped objects. Either the UUID or name must be supplied on POST.
Name | Type | Description |
---|---|---|
_links |
||
name |
string |
The name of the SVM. |
uuid |
string |
The unique identifier of the SVM. |
ip_interface
Name | Type | Description |
---|---|---|
_links |
||
ddns_enabled |
boolean |
Indicates whether or not dynamic DNS updates are enabled. Defaults to true if the interface supports "data_nfs" or "data_cifs" services, otherwise false. |
dns_zone |
string |
Fully qualified DNS zone name |
enabled |
boolean |
The administrative state of the interface. |
ip |
IP information |
|
ipspace |
Either the UUID or name must be supplied on POST for cluster-scoped objects. |
|
location |
Current or home location can be modified. Specifying a port implies a node. Specifying a node allows an appropriate port to be automatically selected. Ports are not valid and not shown for VIP interfaces. For POST, broadcast_domain can be specified alone or with home_node. For PATCH, set is_home to true to revert a LIF back to its home port. |
|
metric |
The most recent sample of I/O metrics for the interface. |
|
name |
string |
Interface name |
probe_port |
integer |
Probe port for Cloud load balancer |
rdma_protocols |
array[string] |
Supported RDMA offload protocols |
scope |
string |
Set to "svm" for interfaces owned by an SVM. Otherwise, set to "cluster". |
service_policy |
||
services |
array[string] |
The services associated with the interface. |
state |
string |
The operational state of the interface. |
statistics |
The real time I/O statistics for the interface. |
|
svm |
Applies only to SVM-scoped objects. Either the UUID or name must be supplied on POST. |
|
uuid |
string |
The UUID that uniquely identifies the interface. |
vip |
boolean |
True for a VIP interface, whose location is announced via BGP. |