Skip to main content
A newer release of this product is available.

san.noconnectediscsiport events

Contributors
Suggest changes
PDFs

san.NoConnectediSCSIPort

Severity

ERROR

Description

This message occurs in MetroCluster(tm) configurations on clustered Data ONTAP® systems, when Data ONTAP cannot replicate an iSCSI logical interface (LIF) to a candidate port in the destination cluster. A candidate port is one that both resides on the disaster recovery (DR) partner node and is connected to the same subnet as the home port of the primary Vserver iSCSI LIF.

Corrective Action

Check the wiring of the network ports and ensure that there are ports on the destination cluster node (DR partner) that are connected to the same subnet as the source cluster port hosting the primary Vserver iSCSI LIF. If the wiring is correct but this failure is still reported when you run the "metrocluster check lif show" command, ensure that the source LIF is operationally up. If the admin-status of the source LIF is down, bring it up using the "network interface modify" command. When the source LIF is up, run the "metrocluster check lif repair-placement" command from the source cluster, with the Vserver name and the LIF name as inputs. Enter the "metrocluster check lif show" command again to check whether LIF placement succeeded or not.

Syslog Message

Subnet discovery failed during LIF replication. There might not be any ports on the destination cluster node %s that are connected to subnet %s in IP space %s to place the iSCSI LIF %s for Vserver %s.

Parameters

node (STRING): Name of the destination cluster node (DR partner) that does not have a port connected to the subnet.
subnet (STRING): The subnet that the primary cluster port hosting the primary Vserver iSCSI LIF is connected to.
ipspace_name (STRING): Name of the IP space that the primary cluster port hosting the primary Vserver iSCSI LIF is connected to.
lif (STRING): Name of the iSCSI LIF.
vserver (STRING): Name of the secondary Vserver in the MetroCluster relationship.