IPMP Troubleshooting Reference

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

Error Explanation :

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

Troubleshooting Action:

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


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

Error Explanation:

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.

Troubleshooting 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.


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

Error Explanation :

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.

Troubleshooting Action :

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


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

Error Explanation :

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.

Troubleshooting Action :

Check for failing hardware


Error Message : Invalid failure detection time assuming default 10000 ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :

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


Error Message : Too small failure detection time of time assuming minimum 100 ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :

Adjust/correct FAILURE_DETECTION_TIME parameter if a failure detection time to a value of 100 or higher


Error Message : Invalid value for FAILBACK value ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :
Correct FAILBACK parameter


Error Message : Invalid value for TRACK_INTERFACES_ONLY_WITH_GROUPS value ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :

Correct TRACK_INTERFACES_ONLY_WITH_GROUPS parameter


Error Message : 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 ( Solaris 8, 9, 10 )

Error Explanation :

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.

Troubleshooting 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


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

Error Explanation :

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

Troubleshooting Action :

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


Error Message : NIC failure detected on interface_name ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :

informational; requires no action.

Note: see Step 3 below for additional info pertaining to /dev/ip settings and excessive, otherwise unexplained failover/failback events.)


Error Message : Successfully failed over from NIC interface_name1 to NIC interface_name2 ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :

informational; requires no action

(Note: see Step 3 below for additional info pertaining to /dev/ip settings and excessive, otherwise unexplained failover/failback events.)


Error Message : NIC repair detected on interface_name ( Solaris 8, 9, 10 )

Error Explanation :

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.

Troubleshooting Action :

informational; requires no action


Message : Successfully failed back to NIC interface_name ( Solaris 8, 9, 10 )

Error Explanation :

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

Troubleshooting Action :

informational; requires no action


Error Message : The link has gone down on interface_name ( Solaris 8, 9, 10 )

Message Explanation :

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

Troubleshooting Action :

informational; requires no action


Error Message : The link has come up on interface_name ( Solaris 8, 9, 10 )

Message Explanation :

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

Troubleshooting Action :

informational; requires no action.


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

Message Explanation :

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

Troubleshooting Action:

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


Error Message : Probe status (count) Duplicate probe reply seq (number) on (interface_name) from (target address) ( Solaris 8, 9, 10 )

Message Explanation :

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

Troubleshootin 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/

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