Network Ports - Revision history

Qadmin: Network Configuration now redirects here, so repoint the two links that pointed at it: describe Modify Grid Network Settings inline and point the per-system DNS/NTP settings at Storage System (QSTOR-12352)

2026-09-04T03:44:58Z

Network Configuration now redirects here, so repoint the two links that pointed at it: describe Modify Grid Network Settings inline and point the per-system DNS/NTP settings at Storage System (QSTOR-12352)

← Older revision		Revision as of 03:44, 4 September 2026
Line 79:		Line 79:
	Three operations are reachable only by right-clicking a port, not from the toolbar: '''Rename Network Port...''', '''Restart Network Port...''' and '''Create Static Route...''' / '''Delete Static Route...'''. Right-click a port either in the tree on the left or in the Network Ports tab.		Three operations are reachable only by right-clicking a port, not from the toolbar: '''Rename Network Port...''', '''Restart Network Port...''' and '''Create Static Route...''' / '''Delete Static Route...'''. Right-click a port either in the tree on the left or in the Network Ports tab.

	For grid-wide settings such as the DNS servers and search domain that apply to all ports, use ~~[[Network Configuration\|~~Modify Grid Network Settings]] ~~instead~~.		For grid-wide settings such as the DNS servers and search domain that apply to all ports, use '''Modify Grid Network Settings''' instead -- the '''Modify Grid''' button in the '''Storage System Grid''' toolbar group. It writes one DNS search suffix, DNS server list and NTP server list to every system you tick, overwriting whatever those systems had. The per-system equivalents are the [[Storage System#DNS Servers\|DNS Servers]] and [[Storage System#NTP Servers\|NTP Servers]] tabs of Storage System Modify.

	== Static vs DHCP assigned IP addresses ==		== Static vs DHCP assigned IP addresses ==
Line 417:		Line 417:
	== Related pages ==		== Related pages ==

	* [[~~Network Configuration~~]] -- ~~grid-wide~~ network settings ~~including DNS servers and search domain~~		* [[Storage System#DNS Servers\|Storage System]] -- the DNS, NTP and network settings on the Storage System Modify dialog
	* [[Network Port Usage]] -- every TCP and UDP port QuantaStor and its supporting services use		* [[Network Port Usage]] -- every TCP and UDP port QuantaStor and its supporting services use
	* [[Firewall Management]] -- system-level firewall settings, which the per-port settings inherit from		* [[Firewall Management]] -- system-level firewall settings, which the per-port settings inherit from

Qadmin: /* Static vs DHCP assigned IP addresses */

2026-09-03T23:54:22Z

Static vs DHCP assigned IP addresses

← Older revision		Revision as of 23:54, 3 September 2026
Line 89:		Line 89:
	There is a second, one-time reason to set a static management address first. A freshly installed system still has the installer's netplan configuration active. The first time you modify any network port, QuantaStor converts that configuration into {{Code\|1=/etc/network/interfaces}}, backs up the previous file as {{Code\|1=/etc/network/interfaces-netplan-convert-<timestamp>.backup}}, renames each {{Code\|1=/etc/netplan/*.yaml}} file to <code>.bak</code>, and disables the netplan renderer. All interfaces are torn down and brought back during that conversion, so a port still on DHCP can come back with a different address and the management session drops. QuantaStor guards against this: while any port is in that state it is flagged with a warning whose detail begins "Netplan", and the Modify Network Port dialog refuses any change other than to <code>static</code>, with the message ''"Be sure to configure a static management network port before modifying network ports."''		There is a second, one-time reason to set a static management address first. A freshly installed system still has the installer's netplan configuration active. The first time you modify any network port, QuantaStor converts that configuration into {{Code\|1=/etc/network/interfaces}}, backs up the previous file as {{Code\|1=/etc/network/interfaces-netplan-convert-<timestamp>.backup}}, renames each {{Code\|1=/etc/netplan/*.yaml}} file to <code>.bak</code>, and disables the netplan renderer. All interfaces are torn down and brought back during that conversion, so a port still on DHCP can come back with a different address and the management session drops. QuantaStor guards against this: while any port is in that state it is flagged with a warning whose detail begins "Netplan", and the Modify Network Port dialog refuses any change other than to <code>static</code>, with the message ''"Be sure to configure a static management network port before modifying network ports."''

	Set a static address on your management port first, then work through the remaining ports. '''Reboot afterwards and confirm the configuration, which is what the accompanying alert asks for.''' This is an important step after an initial QuantaStor OS installation as this allows the system to cleanup network configuration issues left behind by the text mode installer.		Set a static address on your management port first, then work through the remaining DHCP ports until they all have static IPs assigned. '''Reboot afterwards and confirm the configuration, which is what the accompanying alert asks for.''' This is an important step after an initial QuantaStor OS installation as this allows the system to cleanup network configuration issues left behind by the text mode installer.

	== Modifying network port settings ==		== Modifying network port settings ==

Qadmin: /* Static vs DHCP assigned IP addresses */

2026-09-03T23:53:29Z

Static vs DHCP assigned IP addresses

← Older revision		Revision as of 23:53, 3 September 2026
Line 89:		Line 89:
	There is a second, one-time reason to set a static management address first. A freshly installed system still has the installer's netplan configuration active. The first time you modify any network port, QuantaStor converts that configuration into {{Code\|1=/etc/network/interfaces}}, backs up the previous file as {{Code\|1=/etc/network/interfaces-netplan-convert-<timestamp>.backup}}, renames each {{Code\|1=/etc/netplan/*.yaml}} file to <code>.bak</code>, and disables the netplan renderer. All interfaces are torn down and brought back during that conversion, so a port still on DHCP can come back with a different address and the management session drops. QuantaStor guards against this: while any port is in that state it is flagged with a warning whose detail begins "Netplan", and the Modify Network Port dialog refuses any change other than to <code>static</code>, with the message ''"Be sure to configure a static management network port before modifying network ports."''		There is a second, one-time reason to set a static management address first. A freshly installed system still has the installer's netplan configuration active. The first time you modify any network port, QuantaStor converts that configuration into {{Code\|1=/etc/network/interfaces}}, backs up the previous file as {{Code\|1=/etc/network/interfaces-netplan-convert-<timestamp>.backup}}, renames each {{Code\|1=/etc/netplan/*.yaml}} file to <code>.bak</code>, and disables the netplan renderer. All interfaces are torn down and brought back during that conversion, so a port still on DHCP can come back with a different address and the management session drops. QuantaStor guards against this: while any port is in that state it is flagged with a warning whose detail begins "Netplan", and the Modify Network Port dialog refuses any change other than to <code>static</code>, with the message ''"Be sure to configure a static management network port before modifying network ports."''

	Set a static address on your management port first, then work through the remaining ports. Reboot afterwards and confirm the configuration, which is what the accompanying alert asks for.		Set a static address on your management port first, then work through the remaining ports. '''Reboot afterwards and confirm the configuration, which is what the accompanying alert asks for.''' This is an important step after an initial QuantaStor OS installation as this allows the system to cleanup network configuration issues left behind by the text mode installer.

	== Modifying network port settings ==		== Modifying network port settings ==

Qadmin: Deduplicate against the new High-availability VIF Management page (QSTOR-12352, guideline 14): remove the cluster-VIF use-case paragraph, which also listed an Object Storage Reverse Proxy use case the dialog does not offer (that radio is commented out; the live dialog's fourth option is Other), point the following paragraph at the new page, and repoint the site-VIF bullet from the fabricated AddSiteVirtualIP page. Keeps the port-level material - locked config type, refused IP/MTU/bond changes...

2026-09-03T11:33:16Z

Deduplicate against the new High-availability VIF Management page (QSTOR-12352, guideline 14): remove the cluster-VIF use-case paragraph, which also listed an Object Storage Reverse Proxy use case the dialog does not offer (that radio is commented out; the live dialog's fourth option is Other), point the following paragraph at the new page, and repoint the site-VIF bullet from the fabricated AddSiteVirtualIP page. Keeps the port-level material - locked config type, refused IP/MTU/bond changes...

← Older revision		Revision as of 11:33, 3 September 2026
Line 262:		Line 262:

	* '''HA pool virtual interfaces''' (<code>:ha</code>) are associated with a specific [[Storage Pools\|storage pool]] and move with the pool when it fails over to another system. A pool can have several; each additional one increments the last digit of the port name, so they run <code>:ha345680</code>, <code>:ha345681</code>, <code>:ha345682</code> and so on. Create them by right-clicking an HA failover group in the Storage Pools section and choosing '''Add Cluster VIF...''', or with <code>[[QuantaStor CLI Command Reference#ha-interface-create\|qs hai-create]] --ha-group=<group> --parent-port=<port> --ip-address=<ip></code>. A cluster heartbeat must be configured between the systems that manage the pool before an HA VIF can be created; see [[Setup Guide for Clustered HA Storage Pools]] and [[Storage Pool HA Failover Interface Create]].		* '''HA pool virtual interfaces''' (<code>:ha</code>) are associated with a specific [[Storage Pools\|storage pool]] and move with the pool when it fails over to another system. A pool can have several; each additional one increments the last digit of the port name, so they run <code>:ha345680</code>, <code>:ha345681</code>, <code>:ha345682</code> and so on. Create them by right-clicking an HA failover group in the Storage Pools section and choosing '''Add Cluster VIF...''', or with <code>[[QuantaStor CLI Command Reference#ha-interface-create\|qs hai-create]] --ha-group=<group> --parent-port=<port> --ip-address=<ip></code>. A cluster heartbeat must be configured between the systems that manage the pool before an HA VIF can be created; see [[Setup Guide for Clustered HA Storage Pools]] and [[Storage Pool HA Failover Interface Create]].
	* '''Site cluster virtual interfaces''' (<code>:sv</code>) float between the appliances of a site so that a service address stays available. See [[~~AddSiteVirtualIP~~]].		* '''Site cluster virtual interfaces''' (<code>:sv</code>) float between the appliances of a site so that a service address stays available. See [[High-availability VIF Management]].
	* The '''grid management virtual interface''' (<code>:gm</code>) is the single floating address a storage grid is managed through. There is exactly one per site cluster, and iSCSI and NVMe-oF are permanently disabled on it.		* The '''grid management virtual interface''' (<code>:gm</code>) is the single floating address a storage grid is managed through. There is exactly one per site cluster, and iSCSI and NVMe-oF are permanently disabled on it.

	When you add a cluster virtual interface you specify the '''use case''' it serves -- Grid Primary, Storage Pool (Scale-up HA), Storage Pool (Scale-out) or Object Storage Reverse Proxy -- and for the pool and proxy use cases you then select the object the address belongs to. The use case is what tells the cluster software which resource the address has to follow. A second tab sets the '''Site Cluster Member Location Constraints''', the per-node preference weights that decide where the address prefers to live; leave '''Automatic Location Constraints''' selected unless you have a reason to pin it. An existing local virtual interface can be turned into a cluster interface rather than recreated, using the '''Convert local virtual IP to cluster VIF resource''' option.		These are all managed from the '''[[High-availability VIF Management]]''' main tab, and by the cluster software rather than by the network port configuration -- that page covers use cases, failover, deliberate moves and location constraints. That is why the Modify Network Port dialog locks their Config Type to <code>static</code>, disables the addressing fields, and refuses IP, MTU and bond mode changes -- and why static routes cannot be created on them. Change a floating address through the HA or site VIF dialogs, not through Modify Network Port.

	These are all managed from the '''High-availability VIF Management''' main tab, and by the cluster software rather than by the network port configuration. That is why the Modify Network Port dialog locks their Config Type to <code>static</code>, disables the addressing fields, and refuses IP, MTU and bond mode changes -- and why static routes cannot be created on them. Change a floating address through the HA or site VIF dialogs, not through Modify Network Port.

	QuantaStor also enables ARP filtering automatically once a bonded or virtual port exists, because several addresses on the same network answering for each other's ARP requests otherwise sends traffic to the wrong interface.		QuantaStor also enables ARP filtering automatically once a bonded or virtual port exists, because several addresses on the same network answering for each other's ARP requests otherwise sends traffic to the wrong interface.

Qadmin: Tighten the CLI note: qs np-modify --port-type documents only static and dhcp (QSTOR-12352)

2026-09-03T03:03:18Z

Tighten the CLI note: qs np-modify --port-type documents only static and dhcp (QSTOR-12352)

← Older revision		Revision as of 03:03, 3 September 2026
Line 415:		Line 415:
	\|}		\|}

	Note that <code>~~qs np~~-~~modify~~ --port-~~type~~</code> ~~accepts~~ <code>static</code> and <code>dhcp</code>~~; to~~ remove a port's configuration entirely, use the '''Config Type''' setting of <code>disabled</code> in the web interface.		Note that the <code>--port-type</code> argument of <code>[[QuantaStor CLI Command Reference#network-port-modify\|qs np-modify]]</code> documents only <code>static</code> and <code>dhcp</code>. To remove a port's configuration entirely, use the '''Config Type''' setting of <code>disabled</code> in the web interface.

	== Related pages ==		== Related pages ==

Qadmin: Old-page diff pass: corrected static route worked example (gateway must be on the port's own network; previous revision's 10.0.8.1 restored), restored 56GbE in the NIC list, carried forward the HA VIF index numbering and the Add Cluster VIF use case / location constraint content that was previously only in an image caption (QSTOR-12352)

2026-09-03T03:01:43Z

Old-page diff pass: corrected static route worked example (gateway must be on the port's own network; previous revision's 10.0.8.1 restored), restored 56GbE in the NIC list, carried forward the HA VIF index numbering and the Add Cluster VIF use case / location constraint content that was previously only in an image caption (QSTOR-12352)

Qadmin: Rewrite to house doc standard: verified all dialogs/fields against 6.9.0 WUI, corrected default bond mode and netplan/interfaces behaviour, added Firewall tab, rename, online/offline/restart/rescan, port naming, CLI reference and new screenshots (QSTOR-12352)

2026-09-03T02:59:42Z

Rewrite to house doc standard: verified all dialogs/fields against 6.9.0 WUI, corrected default bond mode and netplan/interfaces behaviour, added Firewall tab, rename, online/offline/restart/rescan, port naming, CLI reference and new screenshots (QSTOR-12352)

Show changes

Qadmin: /* High-availability Virtual Ports/Interfaces */

2023-11-26T03:30:57Z

High-availability Virtual Ports/Interfaces

← Older revision		Revision as of 03:30, 26 November 2023
Line 36:		Line 36:

	=== High-availability Virtual Ports/Interfaces ===		=== High-availability Virtual Ports/Interfaces ===
			[[File:Add Site Clust VIF - Web.jpg\|712px\|thumb\|Specify the use case in which the new VIF shall be used. In some use cases, select an associated object for the VIF.]]

	QuantaStor also has some special virtual ports which are used in High-Availability configurations. You'll see these ports with :ha in the name such as eth0:ha345680. These HA virtual interfaces are associated with specific storage pools and move with the pool when the pool is failed-over to another system. Pools can have many VIPs (virtual ports) assigned to them and as more are assigned the last digit of the port name is incremented from 0, 1, 2, 3, 4 and so on.		QuantaStor also has some special virtual ports which are used in High-Availability configurations. You'll see these ports with :ha in the name such as eth0:ha345680. These HA virtual interfaces are associated with specific storage pools and move with the pool when the pool is failed-over to another system. Pools can have many VIPs (virtual ports) assigned to them and as more are assigned the last digit of the port name is incremented from 0, 1, 2, 3, 4 and so on.

Qadmin: /* Virtual Port Configuration */

2023-11-26T03:23:09Z

Virtual Port Configuration

← Older revision		Revision as of 03:23, 26 November 2023
Line 30:		Line 30:
	=== Virtual Port Configuration ===		=== Virtual Port Configuration ===
	Virtual interfaces (VIFs) allow one to use a given physical port on multiple networks with multiple IP addresses simultaneously. To create a VIF on a physical port simply right-click on it and choose '''Create Virtual Interface...''' from the menu. VIFs can be created and deleted at anytime, but cannot be attached to other VIFs.		Virtual interfaces (VIFs) allow one to use a given physical port on multiple networks with multiple IP addresses simultaneously. To create a VIF on a physical port simply right-click on it and choose '''Create Virtual Interface...''' from the menu. VIFs can be created and deleted at anytime, but cannot be attached to other VIFs.

			'''Navigation:''' Storage Management --> Storage Systems --> Network Port --> Create Virtual Port ''(toolbar)''

	[[File:Create Virtual Interface Web.jpg\|712px]]		[[File:Create Virtual Interface Web.jpg\|712px]]

Qadmin: /* VLAN Configuration */

2023-11-26T03:22:18Z

VLAN Configuration

← Older revision		Revision as of 03:22, 26 November 2023
Line 23:		Line 23:
	=== VLAN Configuration ===		=== VLAN Configuration ===
	QuantaStor supports the creation of '''VLAN''' ('''V'''irtual '''LAN''') ports which are simply virtual ports with VLAN tagging and QoS controls. To create a VLAN port simply right-click on a network port and choose the ''Create VLAN Interface...'' option as shown in the right-click menu shown at the top of this section. VLANs can be created and deleted at anytime and are easily identified as they are named with a period (.) as a delimiter between the parent port name and the VLAN tag number. For example, a VLAN with ID 56 associated with eth1 will have the name eth1.56. VLANs can also be created on bonded ports which yields ports with names like bond0.56.		QuantaStor supports the creation of '''VLAN''' ('''V'''irtual '''LAN''') ports which are simply virtual ports with VLAN tagging and QoS controls. To create a VLAN port simply right-click on a network port and choose the ''Create VLAN Interface...'' option as shown in the right-click menu shown at the top of this section. VLANs can be created and deleted at anytime and are easily identified as they are named with a period (.) as a delimiter between the parent port name and the VLAN tag number. For example, a VLAN with ID 56 associated with eth1 will have the name eth1.56. VLANs can also be created on bonded ports which yields ports with names like bond0.56.

			'''Navigation:''' Storage Management --> Storage Systems --> Network Port --> Create VLAN Port ''(toolbar)''

	[[File:Create VLAN Interface Web.jpg\|712px]]		[[File:Create VLAN Interface Web.jpg\|712px]]

← Older revision		Revision as of 03:01, 3 September 2026
Line 261:		Line 261:
	QuantaStor also has virtual interfaces that float between systems. You will see these with <code>:ha</code>, <code>:sv</code> or <code>:gm</code> in the name, such as <code>ens192:ha345680</code>.		QuantaStor also has virtual interfaces that float between systems. You will see these with <code>:ha</code>, <code>:sv</code> or <code>:gm</code> in the name, such as <code>ens192:ha345680</code>.

	* '''HA pool virtual interfaces''' (<code>:ha</code>) are associated with a specific [[Storage Pools\|storage pool]] and move with the pool when it fails over to another system. A pool can have several~~, and~~ each additional one increments the ~~trailing index~~. Create them by right-clicking an HA failover group in the Storage Pools section and choosing '''Add Cluster VIF...''', or with <code>[[QuantaStor CLI Command Reference#ha-interface-create\|qs hai-create]] --ha-group=<group> --parent-port=<port> --ip-address=<ip></code>. A cluster heartbeat must be configured between the systems that manage the pool before an HA VIF can be created; see [[Setup Guide for Clustered HA Storage Pools]] and [[Storage Pool HA Failover Interface Create]].		* '''HA pool virtual interfaces''' (<code>:ha</code>) are associated with a specific [[Storage Pools\|storage pool]] and move with the pool when it fails over to another system. A pool can have several; each additional one increments the last digit of the port name, so they run <code>:ha345680</code>, <code>:ha345681</code>, <code>:ha345682</code> and so on. Create them by right-clicking an HA failover group in the Storage Pools section and choosing '''Add Cluster VIF...''', or with <code>[[QuantaStor CLI Command Reference#ha-interface-create\|qs hai-create]] --ha-group=<group> --parent-port=<port> --ip-address=<ip></code>. A cluster heartbeat must be configured between the systems that manage the pool before an HA VIF can be created; see [[Setup Guide for Clustered HA Storage Pools]] and [[Storage Pool HA Failover Interface Create]].
	* '''Site cluster virtual interfaces''' (<code>:sv</code>) float between the appliances of a site so that a service address stays available. See [[AddSiteVirtualIP]].		* '''Site cluster virtual interfaces''' (<code>:sv</code>) float between the appliances of a site so that a service address stays available. See [[AddSiteVirtualIP]].
	* The '''grid management virtual interface''' (<code>:gm</code>) is the single floating address a storage grid is managed through. There is exactly one per site cluster, and iSCSI and NVMe-oF are permanently disabled on it.		* The '''grid management virtual interface''' (<code>:gm</code>) is the single floating address a storage grid is managed through. There is exactly one per site cluster, and iSCSI and NVMe-oF are permanently disabled on it.

			When you add a cluster virtual interface you specify the '''use case''' it serves -- Grid Primary, Storage Pool (Scale-up HA), Storage Pool (Scale-out) or Object Storage Reverse Proxy -- and for the pool and proxy use cases you then select the object the address belongs to. The use case is what tells the cluster software which resource the address has to follow. A second tab sets the '''Site Cluster Member Location Constraints''', the per-node preference weights that decide where the address prefers to live; leave '''Automatic Location Constraints''' selected unless you have a reason to pin it. An existing local virtual interface can be turned into a cluster interface rather than recreated, using the '''Convert local virtual IP to cluster VIF resource''' option.

	These are all managed from the '''High-availability VIF Management''' main tab, and by the cluster software rather than by the network port configuration. That is why the Modify Network Port dialog locks their Config Type to <code>static</code>, disables the addressing fields, and refuses IP, MTU and bond mode changes -- and why static routes cannot be created on them. Change a floating address through the HA or site VIF dialogs, not through Modify Network Port.		These are all managed from the '''High-availability VIF Management''' main tab, and by the cluster software rather than by the network port configuration. That is why the Modify Network Port dialog locks their Config Type to <code>static</code>, disables the addressing fields, and refuses IP, MTU and bond mode changes -- and why static routes cannot be created on them. Change a floating address through the HA or site VIF dialogs, not through Modify Network Port.
Line 335:		Line 337:
	\|}		\|}

	For example, on a system whose <code>ens192</code> port is <code>10.0.8.70/24</code> ~~with~~ a gateway at <code>10.0.0.1</code> that can reach the <code>192.168.0.0/16</code> network, enter a '''Gateway IP Address''' of <code>10.0.0.1</code>, a '''Destination IP Address''' of <code>192.168.0.0</code> and a '''Destination Subnet Mask''' of <code>255.255.0.0</code>. All traffic from that port destined for <code>192.168.0.0/16</code> is then sent via <code>10.0.0.1</code>.		For example, on a system whose <code>ens192</code> port is <code>10.0.8.70/24</code> and which has a gateway at <code>10.0.8.1</code> that can reach the <code>192.168.0.0/16</code> network, enter a '''Gateway IP Address''' of <code>10.0.8.1</code>, a '''Destination IP Address''' of <code>192.168.0.0</code> and a '''Destination Subnet Mask''' of <code>255.255.0.0</code>. All traffic from that port destined for <code>192.168.0.0/16</code> is then sent via <code>10.0.8.1</code>. Note that the gateway has to be on the port's own network -- QuantaStor applies the route immediately and refuses a gateway the port cannot reach.

	Routes are activated the moment they are created, and QuantaStor refuses a gateway it cannot reach rather than recording a route that will never work. A duplicate destination network and mask on the same system is also refused.		Routes are activated the moment they are created, and QuantaStor refuses a gateway it cannot reach rather than recording a route that will never work. A duplicate destination network and mask on the same system is also refused.
Line 347:		Line 349:
	<pre style="font-size: smaller">		<pre style="font-size: smaller">
	qs sr-create --port=ens192 --destination-ip-address=192.168.0.0 \		qs sr-create --port=ens192 --destination-ip-address=192.168.0.0 \
	--destination-netmask=255.255.0.0 --gateway-ip-address=10.0.0.1		--destination-netmask=255.255.0.0 --gateway-ip-address=10.0.8.1
	qs sr-list		qs sr-list
	</pre>		</pre>
Line 363:		Line 365:
	== Choosing which ports carry which traffic ==		== Choosing which ports carry which traffic ==

	QuantaStor works with all major 10/25/40/50/100GbE network interface cards (NICs) from Intel, Mellanox/NVIDIA, Broadcom, Cisco, Dell, HPE and Supermicro. Most systems have a mix of speeds, and the configuration that matters is which port carries which kind of traffic.		QuantaStor works with all major 10/25/40/56/100GbE network interface cards (NICs) from Intel, Mellanox/NVIDIA, Broadcom, Cisco, Dell, HPE and Supermicro. Most systems have a mix of speeds, and the configuration that matters is which port carries which kind of traffic.

	Clear '''iSCSI Portal''' and '''NVMeoF Portal''' on the slower 1GbE ports. That stops initiators from discovering and logging in through them, and reserves those ports for management traffic. A 1GbE port that answers an iSCSI discovery is a port some client will eventually run its I/O over.		Clear '''iSCSI Portal''' and '''NVMeoF Portal''' on the slower 1GbE ports. That stops initiators from discovering and logging in through them, and reserves those ports for management traffic. A 1GbE port that answers an iSCSI discovery is a port some client will eventually run its I/O over.