Use the cfgportip command to assign an Internet Protocol (IP) address
to each node Ethernet port for Internet Small Computer System Interface (iSCSI) input/output
(I/O).
Syntax
For Internet Protocol Version 4 (IPv4) and Internet Protocol Version 6 (IPv6):
cfgportip -node { node_name | node_id } { -ip ipv4addr -mask subnet_mask -gw ipv4gw | -ip_6 ipv6addr prefix_6 prefix -gw_6 ipv6gw } [ -failover ] { [ -host { yes | no } ] | [ -host_6 { yes | no } ] } { [ -remotecopy remote_copy_port_group_id ] | [ -remotecopy_6 remote_copy_port_group_id ] } { [ -vlan vlan_id_ip4 ] | [ -novlan ] } { [ -vlan_6 vlanid_ip6 ] | [ -novlan_6 ] } { [ -storage { yes | no } ] | [ -storage_6 { yes | no } ] | } [ -force ] port_id
For maximum transmission unit (MTU):
cfgportip { -mtu { mtu } | -defaultmtu } [ -iogrp { io_grp_id | io_grp_name } ] port_id
Parameters
- -nodenode_name | node_id
- (Required) Specifies which node has the Ethernet port that the IP address is being assigned
to.
Note: This parameter is required for setting a port IP address. It cannot be used with the
-mtu parameter.
- -ipipv4addr
- (Required) Sets the Internet Protocol Version 4 (IPv4) address for the
Ethernet port. You cannot use this parameter with the ip_6
parameter.
- -ip_6ipv6addr
- (Required) Sets the Internet Protocol Version 6 (IPv6) address for the
Ethernet port. You cannot use this parameter with the ip parameter.
- -gwipv4addr
- (Required) Sets the IPv4 gateway IP address. You cannot use this parameter with
the gw_6 parameter.
- -gw_6ipv6gw
- (Required) Sets the IPv6 default gateway address for the port. You cannot use this
parameter with the gw parameter.
- -masksubnet_mask
- (Required) Sets the IPv4 subnet mask. You cannot use this parameter with the
prefix_6 parameter.
- -prefix_6prefix
- (Required) Sets the IPv6 prefix. You cannot use this parameter with the
mask parameter.
- -failover
- (Optional) Specifies that the IP address belongs to the partner node in the I/O group. If
the partner node is not configured or offline, the address is configured and presented by this
node. When another node comes online in the I/O group, the failover address is presented by
that node.
If the partner node is online, do not use this option.
- -mtu mtu |
-defaultmtu
- (Required) Specifies the maximum transmission unit (MTU). The default is 1500, with a
maximum of 9000. An MTU of 9000 allows you to save CPU utilization for packets of 4 KB and
over in size. The increased MTU provides you with improved Internet Small Computer System
Interface (iSCSI) performance. Specify -defaultmtu to use the default
value.
Notes: This parameter has the following restrictions:
- This parameter must be used when you are setting or changing the clustered system
(system) MTU value.
- This parameter cannot be used with the -node parameter.
- -iogrpiogrp
- (Optional) Specifies the I/O group that contains the nodes to
modify.
- -hostyes | no
- (Optional) Specifies the IPv4 address that is used for host attach (the existing system
settings are retained). Specifying:
- yes reports the IPv4 address to hosts during target discovery
(default)
- no turns off this report (IPv4 addresses are not reported during host
discovery).
- -remotecopyremote_copy_port_group_id
- (Optional) Specifies the IPv4
address that is used for the remote copy function. Remote copy includes HyperSwap, Metro
Mirror, and Global Mirror. It also specifies the ID for the associated port group. These
IDs are numerical values (0, 1, or 2) that
specify that IP addresses on a system can be part of a partnership for a login. To form a
login, IP addresses must be in the same port group. The default is 0, which
indicates that the port is not available for partnerships.
Important: To add or
delete ports to or from a replication group, make sure that the partnership that uses that
port group is in a stopped state.
- -host_6yes | no
- (Optional) Specifies the IPv6 address that is used for host attach (the existing system
settings are retained). Specifying:
- yes reports the IPv6 address to hosts during target discovery
(default).
- no turns off this report (IPv6 addresses are not reported during host
discovery).
Note: Turning off host attach settings for an IP address that is set to
yes is disruptive because all host iSCSI sessions to that IP address are
logged out.
- -remotecopy_6remote_copy_port_group_id
- (Optional) Specifies the IPv6
address that is used for the remote copy function. Remote copy includes HyperSwap, Metro
Mirror, and Global Mirror. It also specifies the ID for the associated port group. These
IDs are numerical values (0, 1, or 2) that
specify that IP addresses on a system can be part of a partnership for a login. To form a
login, IP addresses must be in the same port group. The default is 0, which
indicates that the port is not available for partnerships.
Important: To add or
delete ports to or from a replication group, make sure that the partnership that uses that
port group is in a stopped state.
- -vlanvlanid_ip4
- (Optional) Sets the virtual local area network (VLAN) ID for a IPv4 address that is
configured for iSCSI host attach or remote copy function. Remote copy includes HyperSwap, Metro Mirror, and Global Mirror. The VLAN ID for an IPv4 type address can be
specified only if the IP address for that port is set. VLAN tagging is disabled for any IP
address, so a VLAN ID must be specified by using -vlan to turn on VLAN
tagging.
Remember: Use
-vlan with caution. You can:
- Reset VLAN settings, which can disrupt port communication (connection) with hosts or
systems (including resetting the VLAN ID for an active iSCSI or IP partnership)
- Reset a VLAN value for a port that does not have VLAN tagging or does not have a
configured IP address
The VLAN ID can be set for the failover port that uses the
-failover attribute.
- -novlan
- (Optional) Disables VLAN tagging for an IPv4 address for an Ethernet port (which means no
VLAN tag is associated with that port).
- -vlan_6vlanid_ip6
- (Optional) Sets the virtual local area network (VLAN) ID for a IPv6 address that is
configured for iSCSI host attach or remote copy function. Remote copy includes HyperSwap, Metro Mirror, and Global Mirror. The VLAN ID for an IPv6 type address can be
specified only if the IP address for that port is set. VLAN tagging is disabled for any IP
address, so a VLAN ID must be specified by using -vlan to turn on VLAN
tagging.
Remember: Use
-vlan_6 with caution:
- Resetting VLAN settings can disrupt port communication (connection) with hosts or
systems, including resetting the VLAN ID for an active iSCSI or IP partnership.
- You can reset a VLAN tag for a port that does not have VLAN tagging or does not have a
configured IP address.
The VLAN ID can be set for the failover port by using the
-failover attribute.
- -novlan_6
- (Optional) Disables Virtual local area network (VLAN) tagging for an IPv6 address for an
Ethernet port (which means no VLAN tag is associated with that port).
Remember: Use
-novlan_6 with caution:
- Resetting VLAN settings can disrupt port communication (connection) with hosts or
systems, including resetting the VLAN ID for an active iSCSI or IP partnership.
- You can reset a VLAN tag for a port that does not have VLAN tagging or does not have a
configured IP address.
- -storageyes | no
- (Optional) Specifies whether an IPv4 address can be used for the backend storage attach
function. The value yes indicates that this IPv4 address can be used for
iSCSI target discovery and backend storage connectivity. You must specify
no (default) if you are not using the storage attach IP address. If the
IPv4 address associated with a specific port (on a node) is changed, the existing storage
attachment settings are retained. The values are yes and
no.
- -storage_6yes | no
- (Optional) Specifies whether an IPv6 address can be used for the backend storage attach
function. The value yes (the default) indicates that this IPv6 address can
be used for iSCSI target discovery and backend storage connectivity. You must specify
no if you are not using a storage attachment IP address. If the IPv6
address associated with a specific port (on a node) is changed, the existing storage
attachment settings are retained. The values are yes and
no.
- -force
- (Optional) Forces an IP address change for a node Ethernet port even if this causes iSCSI
backend controllers being removed or MDisks going into a degraded or offline state.
Important: Use
the force attribute rarely to prevent a loss of access to a node or a MDisk.
Changing IP
address attributes can cause MDisks to go into a degraded state for some time. If a source
IP address is in use for iSCSI backend controller connectivity, changing the IP address or
the subnet mask or the IP gateway removes existing sessions and establishes new sessions.
During this phase, the MDisks visible though the source port that is reconfigured go to
degraded state for a short while until new sessions are established.
You can use the
-force flag to go ahead with the reconfiguration if you understand all of the risks
involved. If you are unsure of what might happen, use the force attribute only under the
direction of your support personnel.
If you are adding a new I/O group in the system,
you might see message CMMVC8915E. When you configure iSCSI IP addresses on a new I/O group,
make sure that you assign the IP address to an unconfigured port and use the -force flag for
IP assignment.
- port_id
- (Required) Specifies which port (1, 2,
3, or 4) to apply changes to.
Description
The
cfgportip command either sets the IP address of an Ethernet port for iSCSI,
or configures the MTU of a group of ports. This command assigns either an IPv4 or IPv6 address
to a specified Ethernet port of a node. The IP address is used for iSCSI I/O. Use the
chsystemip command to assign clustered system IP addresses.
Remember: When IP addresses are configured with the
same remote replication port group ID (for redundancy) to each node of an I/O group, make sure
that the same Ethernet port for both nodes is used during configuration. MTU is set by using
symmetric Ethernet ports from the same I/O group. To make sure alternative remote replication
port groups work with the same MTU settings, symmetric Ethernet ports must be configured for
remote replication port groups.
For an IPv4 address, the ip,
mask, and gw parameters are required. All of the IPv4
IP parameters must be specified to assign an IPv4 address to an Ethernet port.
For an IPv6
address, the ip_6, prefix_6, and
gw_6 parameters are required. All of the IPv6 IP parameters must be
specified to assign an IPv6 address to an Ethernet port.
If an IP address is specified for a host, the specified port can be
discovered by hosts using the iSNS server (or other discovery mechanisms such as SendTargets).
These IP addresses are not reported to partner systems in order to create TCP sessions that are
used for remote copy. These ports also cannot be used for login to and SendTargets based
discovery of backend iSCSI Storage controllers.
IP addresses that are specified for remote copy cannot be discovered by
hosts, which means they cannot be used for host attachment. These ports are not reported to
partner systems in order to create TCP sessions for remote copy. These ports also cannot be used
to log in to and for SendTargets when considering discovery of backend iSCSI Storage
controllers.
After IP configuration,
host_port_group_id is
automatically assigned to the iSCSI ports. Host port grouping groups the ports that have the
same speed and ensures that no more than four ports are discovered by a host. Additional
host_port_group_id criteria include:
- A host_port_group_idis an automatic grouping of ports that is designated
by an integer. Host port group IDs are unique across I/O groups.
- Each host port group ID contains a maximum of four ports.
- All ports within a host port group ID have identical speeds.
- Identical host port group IDs are assigned to the failover port. If a
host_port_group_id is already assigned to a failover port, the same
host_port_group_id are assigned to a local port.
- Enabling -host flag to yes assigns the
host_port_group_id. If on a port with host flag no
, host flag is set to yes , resulting in assignment
of a host_port_group_id to a port.
- Disabling the flag to no removes the host port group id
associated with a iSCSI port.
IP addresses that are specified for storage cannot be discovered by
hosts, which means they cannot be used for host attachment. These IP addresses are not reported
to partner systems to create and set up TCP sessions for remote copy.
To use the same IP address for both host I/O and backend storage
attach functions (but not for remote copy):
- The -host parameter must be set to yes.
- The -storage parameter must be set to yes.
- The -remotecopy parameter must be set to no.
In these instances, these IP addresses can be discovered by hosts. These IP addresses can
also be used for backend storage controller discovery and login for iSCSI based migration and
virtualization.
To use the same IP address for both backend storage attach functions
and remote copy functions (but not for host I/O operations):
- The -storage parameter must be set to yes.
- The -remotecopy parameter must be specified with the required remote
copy port group ID.
- The -host parameter must be set to no.
In such cases, these IP addresses can be used to discover and connect to backend iSCSI
storage controllers. These IP addresses can also be used for IP-based remote copy.
To use the same IP address for both host I/O and remote copy functions
(but not for backend storage attach functions):
- The -host parameter must be set to yes.
- The -remotecopy parameter must be invoked with the required remote
copy port group ID.
- The -storage parameter must be set to no.
In such cases, these IP addresses can be discovered by hosts as well as used for IP-based
Remote Copy but not for backend storage attach.
Use the lsportip
command with the optional ethernet_port_id parameter to list the port IP
addresses for the specified port.
Remember: If cfgportip is used to modify the IP address that is associated with a
specific Ethernet port without specifying a new VLAN ID, the new (modified) IP address inherits
the existing VLAN ID setting of the earlier IP address (IPv4 or IPv6).
An invocation example for
IPv4
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 1
The
resulting output:
No feedback
An invocation example for
IPv6
cfgportip -node 1 -ip_6 3:3:0:4::0 -gw_6 ffe8::0 -prefix_6 64 2
The
resulting output:
No feedback
An invocation example to set an MTU of 1600 on port
1 in I/O group
0
cfgportip –mtu 1600 -iogrp 0 1
The resulting
output:
No feedback
An invocation example to set the MTU to its default
value
cfgportip –defaultmtu -iogrp 0 1
The resulting
output:
No feedback
An invocation example configuring a new IPv4
address for IP-based
replication
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –remotecopy 1 –host no -host_6 no 1
The
resulting output:
No feedback
An invocation example configuring a new IPv4
address for host
attach
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –host yes 1
The
resulting output:
No feedback
An invocation example configuring replication
for an existing IPv6
address
cfgportip -node 1 –remotecopy_6 2 1
The resulting
output:
No feedback
An invocation example configuring host attach
for a new IPv6
address
cfgportip -node 1 –ip_6 2001:db8::1:0:0:1 –host_6 yes 1
The
resulting output:
No feedback
An invocation example configuring a new IPv4 address with the VLAN ID
105
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –vlan 105 1
The
resulting output:
No feedback
An invocation example for configuring a new IPv6 address with the VLAN ID
1063
cfgportip -node 1 -ip_6 2001:db8::1:0:0:101 -prefix_6 64 -gw_6 2001:db8::1:0:0:1 -vlan_6 1063 1
The
resulting output:
No feedback
An invocation example for configuring a new IPv4 address for the backend storage attach
function using iSCSI
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –storage yes -remotecopy 0 –host no 1
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –storage yes –host no 1
The resulting output:
No feedback
An invocation example for configuring a new IPv4 address for host attach only
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –host yes -storage no 1
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 –host yes -storage no -remotecopy 0 1
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 1
The resulting output:
No feedback
An invocation example for configuring a new IPv4 address for IP-based replication
cfgportip -node 1 -ip 9.8.7.1 -gw 9.0.0.1 -mask 255.255.255.0 -storage no –remotecopy 1 –host no 1
The resulting output:
No feedback
An invocation example for configuring the storage attach function for a new IPv6
address
cfgportip -node 1 –ip_6 2001:db8::1:0:0:1 –storage_6 yes 1
cfgportip -node 1 –ip_6 2001:db8::1:0:0:1 1
The resulting output:
No feedback
An invocation example for changing the storage specification for an existing IPv6
address
cfgportip -node 1 –storage_6 no 1
cfgportip -node 1 –storage_6 yes 1
The resulting output:
No feedback