PowerFlex: MDM_CLUSTER_FAILED_EXPOSE_VIRT_IP ERROR

Summary: PowerFlex: MDM event: MDM_CLUSTER_FAILED_EXPOSE_VIRT_IP ERROR

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms



You may notice the MDM switching roles. The MDM service restarts when it is unable to reach its virtual IP.  This is expected if the virtual IP is not reachable by all subnets, and the working subnet has a problem.

Events log: 
182920 2019-10-16 00:19:09.726 MDM_CLUSTER_FAILED_EXPOSE_VIRT_IP ERROR         The Master MDM, MDM-N01 (ID xxxxxxxxxxxxxxxx), could not expose virtual IP addresses. 
182921 2019-10-16 00:19:09.899 REMOTE_SYSLOG_MODULE_INITIALIZED INFO          Initialized the remote syslog module 
182922 2019-10-16 00:19:09.899 MDM_MANAGER_START         INFO          MDM started with the role of Manager 
182923 2019-10-16 00:19:10.013 MDM_CLUSTER_CONNECTED     INFO          The MDM, MDM-N03 (ID xxxxxxxxxxxxxxxy), connected after 0ms 
182924 2019-10-16 00:19:10.013 MDM_CLUSTER_CONNECTED     INFO          The MDM, MDM-N02 (ID xxxxxxxxxxxxxxxz), connected after 0ms 
182925 2019-10-16 00:19:10.013 MDM_CLUSTER_CONNECTED     INFO          The MDM, TB-N05 (ID xxxxxxxxxxxxxxyy), connected after 0ms 
182926 2019-10-16 00:19:10.013 MDM_CLUSTER_CONNECTED     INFO          The MDM, TB-N04 (ID xxxxxxxxxxxxxxyz), connected after 0ms 
182927 2019-10-16 00:19:11.441 MDM_CLUSTER_LOST_CONNECTION WARNING       The MDM, MDM-N03 (ID xxxxxxxxxxxxxxxy), has lost connection to the cluster. 
182928 2019-10-16 00:19:11.727 MDM_CLUSTER_BECOMING_MASTER WARNING       This MDM, MDM-N01 (ID xxxxxxxxxxxxxxxx), took control of the cluster and is now the Master MDM. 
182929 2019-10-16 00:19:11.738 MDM_CLUSTER_CONNECTED     INFO          The MDM, MDM-N03 (ID xxxxxxxxxxxxxxxy), connected after 300ms 
182930 2019-10-16 00:19:11.929 MDM_CLUSTER_NODE_DEGRADED ERROR         MDM cluster node is now DEGRADED and is in offline node MDM-N03 (ID xxxxxxxxxxxxxxxy); IPs: [10.37.208.13,10.37.200.13,10.37.208.141], Port: 9011 . 
182931 2019-10-16 00:19:11.930 MDM_CLUSTER_NODE_NORMAL   INFO          MDM cluster node MDM-N02 (ID xxxxxxxxxxxxxxxz); IPs: [10.37.208.12,10.37.200.12,10.37.208.140], Port: 9011 is now in NORMAL state. 
182932 2019-10-16 00:19:11.930 MDM_BECOMING_MASTER       WARNING       This MDM is switching to Master mode. MDM will start running. 
182933 2019-10-16 00:19:12.145 MDM_CLUSTER_NODE_NORMAL   INFO          MDM cluster node MDM-N03 (ID xxxxxxxxxxxxxxxy); IPs: [10.37.208.13,10.37.200.13,10.37.208.141], Port: 9011 is now in NORMAL state. 
182934 2019-10-16 00:19:12.145 MDM_CLUSTER_NORMAL        INFO          MDM cluster is now in NORMAL mode.
We see that we are unable to reach IP 10.37.200.39


16/10 00:19:09.726004 0x7f40b2417db8:virtIP_IsInterfaceUp:01046: Interface bond1.4090:mdm is down - rc: 0, flags: 0x1003, errno: 11
16/10 00:19:09.726012 0x7f40b2417db8:actor_UmtRepublishVirtualIPs:19591: Virtual interface is down (interface: bond1.4090:mdm, IP: 10.37.200.39, RC: NOT_CONN)
16/10 00:19:09.726015 0x7f40b2417db8:actor_UmtRepublishVirtualIPs:19601: Up virtual IPs (0/1)
16/10 00:19:09.726051 0x7f40b2417db8:mosEventLog_PostInternal:00608: New event added. Message: "The Master MDM, MDM-N01 (ID xxxxxxxxxxxxxxxx), could not expose virtual IP addresses.". Additional info: "" Severity: Error
16/10 00:19:09.726081 0x7f40b2417db8:virtIP_RemoveIpv4:01114: Removed (bond1.4090:mdm)
16/10 00:19:09.726083 0x7f40b2417db8:actor_DoPlannedCrash:01461: --- Actor planned crash at: actor_UmtRepublishVirtualIPs, reason: Failed to republish virtual IPs ---

16/10 00:19:09.726100 0x7f40b2417db8:mosDbg_PlannedCrashModuleWithDesc:00599: ---Planned crash, reason: Failed to republish virtual IPs ---
16/10 00:19:09.836386 (nil):mosTrcLayer_Create:00235: ---------- Process started. Version private ScaleIO R3_0.200.104_Release Aug 13 2019. PID 181845 ----------
Frequent MDM restarts may affect availability and performance.

Cause

After configuring virtual IP addresses, if the Master MDM discovers that its virtual IP addresses are unreachable, it will try to perform a switch-over. Virtual IP addresses may be unreachable because the data network switch is down and the cluster is using a different network. If no MDM can obtain the virtual IP addresses, the MDM processes might shut down.

Resolution

Make sure the virtual IP is reachable.

Affected Products

PowerFlex appliance Intelligent Catalog Software

Products

PowerFlex rack, VxFlex Ready Nodes, PowerFlex Appliance, PowerFlex custom node, ScaleIO, PowerFlex appliance R650, PowerFlex appliance R6525, PowerFlex appliance R660, PowerFlex appliance R6625, Powerflex appliance R750, PowerFlex appliance R760 , PowerFlex appliance R7625, PowerFlex custom node, PowerFlex custom node R650, PowerFlex custom node R6525, PowerFlex custom node R660, PowerFlex custom node R6625, PowerFlex custom node R750, PowerFlex custom node R760, PowerFlex custom node R7625, PowerFlex rack connectivity, PowerFlex rack HW, PowerFlex rack RCM Software, VxFlex Ready Node, VxFlex Ready Node R640, VxFlex Ready Node R740xd, PowerFlex appliance R640, PowerFlex appliance R740XD, PowerFlex appliance R7525, PowerFlex appliance R840, VxFlex Ready Node R840 ...
Article Properties
Article Number: 000081366
Article Type: Solution
Last Modified: 24 Nov 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.