Solaris Troubleshooting – in.mpathd Error Messages and Corrective Actions

How to Analyse and Resolve various in.mpath Issues.

This article will give you quick overview of various in.mapthd error messages, the meaning and corrective action for each message. To understand more about in.mpathd troubleshooting you can refer the following articles  – Solaris IPMP Troubleshooting 

Solaris 10 : Test address is not unique; disabling probe-based failure detection on interface_name

For in.mpathd to perform probe-based failure detection, each test address in the group must be unique. Since the IPv6 test address is a link-local address derived from the MAC address, each IP interface in the group must have a unique MAC address

Action : ensure that the test address marked as “deprecated” and “non-failover” in the /etc/hostname. is unique. (see Step 1).

Solaris 8, 9, 10 : NIC interface_name of group group_name is not plumbed for IPv[4|6] and may affect failover capability

All NICs in a multipathing group must be homogeneously plumbed. For example, if a NIC is plumbed for IPv4, then all NICs in the group must be plumbed for IPv4. The streams modules pushed on all NICs must be identical.

Action : Ensure all interfaces in the group are plumbed for the same IP version. To identify, use “ifconfig -a4” to list only IPv4 interfaces; “ifconfig -a6” to list only IPv6 interfaces.

Solaris 10 : No test address configured on interface interface_name disabling probe-based failure detection on it

In order for in.mpathd to perform probe-based failure detection on a NIC, it must be configured with a test address: IPv4, IPv6, or both.

Action : Configure an additional test address marked as deprecated and non-failover in order to use probe-based IPMP (see Step 1)

Solaris 8, 9, 10 : The link has come up on interface_name more than 2 times in the last minute; disabling failback until it stabilizes.

In order to prevent interfaces with intermittent hardware, such as a bad cable, from causing repeated failovers and failbacks, in.mpathd does not failback to interfaces with frequently fluctuating link states.

Action : check for failing hardware

Solaris 8, 9, 10 : Invalid failure detection time assuming default 10000

An invalid value was encountered for FAILURE_DETECTION_TIME in the /etc/default/mpathd file.

Action : Adjust/correct FAILURE_DETECTION_TIME parameter if a failure detection time other than 10000 is desired (see Step 1)

Solaris 8, 9, 10 : Too small failure detection time of time assuming minimum 100

The minimum value that can be specified for FAILURE_DETECTION_TIME in the /etc/default/mpathd file is currently 100 milliseconds.

Action : Adjust/correct FAILURE_DETECTION_TIME parameter if a failure detection time to a value of 100 or higher (see Step 1)

Solaris 8, 9, 10 : Invalid value for FAILBACK value

Valid values for the boolean variable FAILBACK in the /etc/default/mpathd file are yes or no.

Action : Correct FAILBACK parameter

Solaris 8, 9, 10 : Invalid value for TRACK_INTERFACES_ONLY_WITH_GROUPS value

Valid values for the boolean variable TRACK_INTERFACES_ONLY_WITH_GROUPS in the /etc/default/mpathd file are yes or no.

Action : Correct TRACK_INTERFACES_ONLY_WITH_GROUPS parameter

Solaris 8, 9, 10 : Cannot meet requested failure detection time of time ms on (inet[6] interface_name) new failure detection time for group group_name is time ms

The round trip time for ICMP probes is higher than necessary to maintain the current failure detection time. The network is probably congested or the probe targets are loaded. in.mpathd automatically increases the failure detection time to whatever it can achieve under these conditions.

Action : Occasional adjustments of failure detection time based on network conditions are a normal part of mpathd’s monitoring of the interface. If excessive, see Step 3, Step 4, Step 6, Step 8 and Step 10

Solaris 8, 9, 10 : Improved failure detection time time ms on (inet[6] interface_name) for group group_name

The round trip time for ICMP probes has now decreased and in.mpathd has lowered the failure detection time correspondingly.

Action : Occasional adjustments of failure detection time based on network conditions are a normal part of mpathd’s monitoring of the interface.

Solaris 8, 9, 10 : NIC failure detected on interface_name

in.mpathd has detected NIC failure on interface_name, and has set the IFF_FAILED flag on NIC interface_name.

Action : informational; requires no action.
Solaris 8, 9, 10 : Successfully failed over from NIC interface_name1 to NIC interface_name2

in.mpathd has caused the network traffic to failover from NIC interface_name1 to NIC interface_name2, which is part of the multipathing group.

Action : informational; requires no action
Solaris 8, 9, 10 : NIC repair detected on interface_name

in.mpathd has detected that NIC interface_name is repaired and operational. If the IFF_FAILED flag on the NIC was previously set, it will be reset.

Action : informational; requires no action
Solaris 8, 9, 10 : Successfully failed back to NIC interface_name

in.mpathd has restored network traffic back to NIC interface_name, which is now repaired and operational.

Action : informational; requires no action

Solaris 8, 9, 10 : The link has gone down on interface_name

in.mpathd has detected that the IFF_RUNNING flag for NIC interface_name has been cleared, indicating the link has gone down.

Action : informational; requires no action
Solaris 8, 9, 10 : The link has come up on interface_name

in.mpathd has detected that the IFF_RUNNING flag for NIC interface_name has been set, indicating the link has come up.

Action : informational; requires no action.

Solaris 8, 9, 10 : probe status (count) Fake probe reply seq (number) on (interface_name) from (target address)

When checking the response packet, in.mpathd has detected that we don’t have any record of having sent a probe to this target.

Action : informational; requires no action. May check probe target (e.g. default router) for additional interfaces in subnet.
Solaris 8, 9, 10 : probe status (count) Duplicate probe reply seq (number) on (interface_name) from (target address)

When checking the response packet, in.mpathd tables indicate that this probe reply has been acknowledged already.

Action : informational; requires no action. May check probe target (e.g. default router) for additional interfaces in subnet.

Ramdev

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

1 Response

  1. September 16, 2015

    […] Read – in.mpathd Error Messages and Corrective Actions […]

What is in your mind, about this post ? Leave a Reply

Close
  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us