Modify network port attributes
Contributors Download PDF of this page
You can modify the autonegotiation, duplex, flow control, speed, and health settings of a physical network port.
Before you begin
The port that you want to modify must not be hosting any LIFs.
About this task
You should not modify the administrative settings of the 100 GbE, 40 GbE, 10 GbE or 1 GbE network interfaces.
The values that you can set for duplex mode and port speed are referred to as administrative settings. Depending on network limitations, the administrative settings can differ from the operational settings (that is, the duplex mode and speed that the port actually uses).
You should not modify the administrative settings of the underlying physical ports in an interface group.
-up-adminparameter (available at the advanced privilege level) modifies the administrative settings of the port.
-up-adminadministrative setting should not be set to false for all ports on a node, or for the port that hosts the last operational cluster LIF on a node.
You should not modify the MTU size of the management port, e0M.
The MTU size of a port in a broadcast domain cannot be changed from the MTU value that is set for the broadcast domain.
The MTU size of a VLAN cannot exceed the value of the MTU size of its base port.
Modify the attributes of a network port:
network port modify
You can set the -ignore-health-status field to true for specifying that the system can ignore the network port health status of a specified port. The network port health status is automatically changed from degraded to healthy, and this port can now be used for hosting LIFs. You should set the flow control of cluster ports to none. By default, the flow control is set to full.
The following command disables the flow control on port e0b by setting the flow control to none:
network port modify -node cluster-1-01 -port e0b -flowcontrol-admin none