ONTAP Discussions
ONTAP Discussions
I have been struggling with establishing a transition SM between a 7-mode system and a cDOT system.
I have configured many others in my environment that have worked successfully and have followed the same procedures on this particular one with no success.
Any help/suggestions would be appreciated. Here's the scenario:
Source 7-Mode system: FAS3240, OnTAP 8.2.1 7-mode, 64bit aggregates
Destination cDOT system: FAS3250, OnTap 8.2.1 Cluster-mode
7-Mode /etc/messages after Snapmirror initialize:
[<hostname>:snapmirror.src.sockErr:error]: Cannot accept SnapMirror destination requests: destination connection dropped.
After MANY attempts, I decided to install the 7MTT to see what it would do:
With the 7MTT tool, I am unable to add the 7-mode system. I get "System is unreachable" on the 7MTT side. Nothing in /etc/messages of the 7-mode system.
The "ransition-gui.log" on the 7MTT system reports the following:
I have followed the 7MTT workflow troubleshooting from the knowledgebase with no success.
Any suggestions? What am I missing?
Solved! See The Solution
After pulling out most of my remaining hair, I found the problem. It turned out to be an MTU setting on the 7-mode system.
I have a VIF (ifgrp) on this 7-mode system that consists of a 2GB LACP and a 20GB LACP combined into a single-mode VIF, favoring the 20GB.
MTU was set to 9000 on the single-mode VIF, but even though I am favoring the 20GB connection I was unable to pass packet sizes over 1500.
I set the MTU to 1500 on the main VIF and initialized the snapmirror and it worked as expected.
I would start with ping tests from 7-Mode to ALL cDOT intercluster lifs.. then net ping back from ALL cDOT intercluster lifs to 7-Mode. 7MTT is alerting about not being able to reach 7-Mode...but could be routing from cDOT to 7-Mode...
Usually it is either options snapmirror.access but you already checked that, or routing... in cDOT when you create a LIF manually, it creates the routing entry but without routes. For example, if you run "net routing-group show" you will see the "ix.x.x.x" network, but when you type "net routing-group route show" do you see a default route for that routing group. Often that can be the issue. Also run "event log show" and see if anything on that end.
Do you have routes on cDOT or errors in cDOT logs?
Thank you for the suggestions. Here's what I've uncovered so far.
I performed some testing and was able to setup 7-mode to cDOT SM relationships from other 7-mode systems to this particular cDOT system and they worked as expected, without problem.
The same entries were placed in the "options snapmirror.access" on the working, 7mode systems as the non-working system.
I confirmed that pings work in both directions, routing-groups and routes exist with default routes.
It is only this one 7-mode system that is not working.
Confirmed successful pings:
From cDOT: network ping -lif intcl_lif -lif-owner xxxxxxx -destination "7-mode system ip" -disallow-fragmentation false -show-detail
From 7mode: ping <cDot intcl lif>
cDOT: event log show
7mode: /etc/messages
After pulling out most of my remaining hair, I found the problem. It turned out to be an MTU setting on the 7-mode system.
I have a VIF (ifgrp) on this 7-mode system that consists of a 2GB LACP and a 20GB LACP combined into a single-mode VIF, favoring the 20GB.
MTU was set to 9000 on the single-mode VIF, but even though I am favoring the 20GB connection I was unable to pass packet sizes over 1500.
I set the MTU to 1500 on the main VIF and initialized the snapmirror and it worked as expected.
@tlkendall thanks a lot for your comment! I spent a few hours fighting this problem.