network port modify
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Modify network port attributes
Availability: This command is available to cluster administrators at the admin privilege level.
Description
The network port modify
command enables you to change the maximum transmission unit (MTU) setting, autonegotiation setting, administrative duplex mode, and administrative speed of a specified network port.
The MTU of ports that belong to broadcast-domains must be updated through the broadcast-domain modify
command.
Modification of a port's IPspace will only work before a node is added to a cluster, when the cluster version is below Data ONTAP 8.3, or when the node is offline. To change the IPspace of a port once the node is in a Data ONTAP 8.3 cluster, the port should be added to a broadcast-domain that belongs to that IPspace.
Parameters
-node {<nodename>|local}
- Node-
Use this parameter to specify the node on which the port is located.
-port {<netport>|<ifgrp>}
- Port-
Use this parameter to specify the port that you want to modify.
[-mtu <integer>]
- MTU-
The port's MTU setting. The default setting for ports in the "Cluster" IPspace is 9000 bytes. All other ports use a default value of 1500 bytes.
[-autonegotiate-admin {true|false}]
- Auto-Negotiation Administrative-
Whether the port uses Ethernet autonegotiation to determine the highest speed and duplex mode that the port and its endpoint can support. The default setting when you create a port is
true
. [-duplex-admin {auto|half|full}]
- Duplex Mode Administrative-
The administrative setting for the port's duplex mode. This is the duplex mode that you prefer the port to use. Depending on network limitations, the operational value can be different from the administrative setting. The default setting when you create a port is
full
. [-speed-admin {auto|10|100|1000|10000|25000|40000}]
- Speed Administrative-
The administrative speed setting, in megabits per second. This is the speed setting that you prefer the port to use. Depending on network limitations, the operational value can be lower than the administrative setting.
[-flowcontrol-admin {none|receive|send|full}]
- Flow Control Administrative-
The administrative flow control setting of the port. this is the flow control setting that you prefer the port to use. Depending on network and port limitations, the operational value can be different from the administrative setting.
[-up-admin {true|false}]
- Up Administrative (privilege: advanced)-
The administrative state of the port. If set to
true
, the port is used if it is operational. If set tofalse
, the port is configured down. [-ipspace <IPspace>]
- IPspace Name-
Use this parameter to specify the IPspace the network port is assigned to. Modification of a port's IPspace will only work before a node is added to a cluster, when the cluster version is below Data ONTAP 8.3, or when the node is offline. To change the IPspace of a port once the node is in a Data ONTAP 8.3 cluster, the port should be added to a broadcast-domain that belongs to that IPspace. If there is an inconsistency between the broadcast-domain and IPspace, this parameter can be set to bring the IPspace into alignment with the broadcast-domain.
[-ignore-health-status {true|false}]
- Ignore Port Health Status (privilege: advanced)-
Use this parameter to specify that the system ignore network port health status of the specified port for the purpose of hosting a logical interface.
Examples
The following example modifies port e0a on a node named node0 not to use auto-negotiation, to preferably use half duplex mode, and to preferably run at 100 Mbps.
cluster1::> network port modify -node node0 -port e0a -autonegotiate-admin false -duplex-admin half -speed-admin 100