This post is more than 5 years old
2 Posts
0
2412
October 3rd, 2016 08:00
Can't ping veth2 anymore
Hello there
The replication between our two datadomains suddenly stopped last weekend.
The webinterface says "Communication failed".
Replication status in console says "connection disconnected".
I can still ping veth1 but not veth2 from the switch.
I can still ping veth2 from a server on the same switch/subnet but not from another site.
Can anyone make sense out of this? is this a Datadomain issue?
Regards,
Alarm
No Events found!
alarm1
2 Posts
0
October 3rd, 2016 23:00
Thank you both for your answer.
I was troubleshooting the whole day yesterday and then half an hour after i left the office it suddenly started working again. Also it stopped working on the weekend in the middle of the night.
Therefore i wouldn't suspect network changes to be the cause.
there were no system upgrades or anything for a year. There are no routes configured.
the pings now work in every case.
I guess there was some issue with the NIC or something.
-solved.
umichklewis
3 Apprentice
•
1.2K Posts
1
October 3rd, 2016 12:00
You might want your network team to investigate any changes they might have made recently. If you can ping the interface from a host on the same subnet, not from another, it sounds like a change in the gateway or netmask has occurred.
jbrooksuk
208 Posts
1
October 3rd, 2016 23:00
I think Karl is right.
But is Veth1/Veth2 failover or LACP?
Are all configured physical NICs in each virtual port up (net show hardware)?
Did you update DDOS or change any network config or routes at the DD (system upgrade history)?
Do you have any routes on the DD (route show config)?
If veth1 and veth2 are in different subnets, is the default gateway aligned to veth1 or veth2 (route show gateway)?
Regards,
Jonathan