Were you able to start replication afterward?
P.S. Make sure to use redundant Network cards.
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software
Replication network unavailable
Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)
I was able to get the nodes back online and syncing again. I had run the Powershell script in the instructions to change all sync/iSCSI network cards to 9014 MTU already... but I also had to go to the underlying physical NIC properties and change the MTU to match there as well.
I've been able to do several reboots of both nodes and the VM live migrates with the storage back and forth without issue now. I picked up a couple more dual port Connectx-5 25Gb cards I plan to install and reconfigure with some more high bandwidth redundancy.
I've been able to do several reboots of both nodes and the VM live migrates with the storage back and forth without issue now. I picked up a couple more dual port Connectx-5 25Gb cards I plan to install and reconfigure with some more high bandwidth redundancy.
Just for fun, I turned on the linux CVM's again after setting the jumbo frame to 9014 on the physical NIC's and it got past that ping error message without a problem!
See below for the settings I changed. The hyper-v adapter created by the hyper-V switch was set correctly, but the underlying physical NIC was not.
See below for the settings I changed. The hyper-v adapter created by the hyper-V switch was set correctly, but the underlying physical NIC was not.
- Attachments
-
- JumboFrame1.png (123.49 KiB) Viewed 295 times
-
- JumboFrame2.png (121.67 KiB) Viewed 295 times
-
yaroslav (staff)
- Staff
- Posts: 2361
- Joined: Mon Nov 18, 2019 11:11 am
I see. Thanks for your reply!
Yes, MTU can be a problem. SR-IOV can be too, sadly.
Good to know you solved it!
Yes, MTU can be a problem. SR-IOV can be too, sadly.
Good to know you solved it!