The command fails if the specified host is contained in a cluster. In this case, the
unmapping of the host must be performed through the cluster.
The command does not fail when the volume is not mapped to the host/cluster.
Access Control:
User Category Permission Condition
Storage administrator Allowed N/A
Storage integration administrator Allowed N/A
Application administrator Conditionally Allowed The volume is a snapshot, where
its master volume is mapped to
a host or cluster associated with
the user and the snapshot was
created by an application
administrator.
Security administrator Disallowed N/A
Read-only users Disallowed N/A
Technicians Disallowed N/A
Completion Codes:
v HOST_BAD_NAME
Host name does not exist
v HOST_BELONGS_TO_CLUSTER
Host is part of a cluster
v CLUSTER_BAD_NAME
Cluster name does not exist
v VOLUME_BAD_NAME
Volume name does not exist
v SNAPSHOT_IS_INTERNAL
Internal snapshots cannot be mapped, modified or deleted.
v VOLUME_IS_NON_PROXY_OLVM_DESTINATION
The volume is in an IBM Hyper-Scale Mobility migration state.
v OLVM_LINK_IS_NOT_UP
IBM Hyper-Scale Mobility link is not up. The mapping list cannot be updated.
v ISCSI_HOST_ILLEGAL_PORT_NAME
Port name for iSCSI Host is illegal
Troubleshooting: Port names for iSCSI Hosts must contain only printable
characters.
v MAX_PORTS_REACHED
Maximum number of ports already defined in the system
v HOST_PORT_EXISTS
Host with this port ID already defined
v MAPPING_IS_NOT_DEFINED
The requested mapping is not defined
v REMOTE_MAX_VIRTUAL_HOSTS_REACHED
Maximum number of remote virtual hosts already defined
Chapter 2. Host and Cluster Management 25
To Next Page
Loading...
