Home > Tintri VMstore™ > Knowledge Base > Modifying the Data IP causes Replication to fail due to Invalid Source IP

Modifying the Data IP causes Replication to fail due to Invalid Source IP

Applies To

 

Product(s)

Version(s)

T540, T6xx, T8xx, T5xxx

TxOS 3.x, 4.0.x, 4.1.x, 4.2.x

Introduction

Modifying the Data IP causes Replication to fail due to Invalid Source IP

 

Symptoms

The VMstore is configured to use the data network for replication and the VMstore does not have a dedicated Replication NIC.

 

Alerts are received on the VMstore stating replication is delayed and an invalid IP address is specified:

LOG-REPL-0044 Replica VM 'VM12345678' and 12 others are from Fri Sep 30 10:00:04 CDT 2016 or older. They are more than 50 hours delayed. An invalid source IP address was specified. Ensure that the specified address is in standard dotted decimal format (A.B.C.D where A, B, C, and D are 0-255).

 

The ui-debug.log contains an entry showing the data IP was modified and replication was removed:

2016-09-30T10:15:20.545133-05:00 tintri#b tomcat: [http-443-12,com.tintri.log.LogBase] WARN : USER:AUDIT:LOG-AUDIT-0016: [714301] User 'accounts\a_user' changed configuration setting; added IP addresses '{{data service, 10.xx.xx.xx, 255.255.255.192, none, 3610}}' and removed '{{replication service, 10.yy.yy.yy, 255.255.255.192, none, 3603}}' on the data network.

 

 

Resolution

The workaround to resolve the situation is to reconfigure the Replication IP after any changes are made to the Data IP.

 

After this change, the following entry should be observed in the ui-debug.log:

ui-debug.log:2016-10-03T09:10:50.976670-05:00 tintri#b tomcat: [http-443-32,com.tintri.log.LogBase] WARN : USER:AUDIT:LOG-AUDIT-0016: [751301] User 'accounts\a_user' changed configuration setting; added IP addresses '{{replication service, 10.yy.yy.yy, 255.255.255.192, none, 3603}}' and removed 'none' on the data network

 

 

You must to post a comment.
Last modified

Tags

Classifications

This page has no classifications.