Home > Tintri VMstore™ > Knowledge Base > LOG-HVPATHCHECK-0001 Secondary Controller Cannot Reach the Hypervisor

LOG-HVPATHCHECK-0001 Secondary Controller Cannot Reach the Hypervisor

Applies To

Product(s): T540,T620,T850,T880, VMstore

Product Version(s): 3.1.1.4 and later

Details

Alert Message ID LOG-HVPATHCHECK-0001
Alert Message Text The secondary controller cannot reach the hypervisor at {Hypervisor IP} via {Network Bond}.
Alert Trigger An Arping executed on the Secondary Controller with the Hypervisor Manager IP, or Gateway IP, as an argument, fails.
Common Causes Misconfigured switch port.
Misconfigured VLAN.

Description

In furtherance of service continuity in the event of controller or network failure, the Tintri VMstore employs two controllers, each with redundant network interfaces.
 
In order to make sure functionality will not be degraded in the event of a controller failover, the Tintri VMStore verifies network connectivity with the configured Hypervisor Manager by invoking an Arping command on the secondary controller. 
 
If the Hypervisor Manager IP address is in the same subnet as the VMstore data IP address, the Hypervisor Manager IP address is used as the argument to Arping.
If the Hypervisor Manager IP address is not in the same subnet as the VMstore data IP address, the gateway IP address is used as the argument to Arping.
 
If the Arping command fails, the alert LOG-HVPATHCHECK-0001 is sent. 

 

You must to post a comment.
Last modified
10:54, 22 Apr 2017

Tags

Classifications

This page has no classifications.