#Additional network troubleshooting tools
1 messages · Page 1 of 1 (latest)
If you need that, there are options in systemshell. https://community.netapp.com/t5/ONTAP-Discussions/Troubleshooting-with-tcp-client/m-p/144980
So, I have a node from one of our CDOT 9.1 clusters that all of a sudden can no longer reach the mail relay to send autosupport emails. I've checked DNS, IP routes, traceroute etc - all good - nothing has been changed on the filer, the partner node still sends emails fine. "you'll need to try a tel...
@digital yarrow Can you provide some specific examples of when this is needed? Systemshell has some options as noted, but it would be ideal to understand the use-case(s)
There's a lot of use cases - common one I run into is checking if SnapMirror ports are open across a network or not, especially from a specific LIF if there are multiple networks/VLANs in play.
I haven't used the systemshell telnet client in a bit but I don't recall being able to select what LIF to initiate the connection from.
I was wrong on this - see below
Can you please share how you check the snapmirror availability with this?
--edited - removed this to clear up the conversation
So it looks like I was wrong.
Here's the source IC LIFs on my primary cluster:
`
mn1-ontap1::*> net int show -role intercluster
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
mn1-ontap1
iclif1 up/up 10.0.4.58/24 mn1-ontap1-01 a0a-4 true
iclif2 up/up 10.0.4.59/24 mn1-ontap1-02 a0a-4 true
2 entries were displayed.
mn1-ontap1::*> `
Here's the IC LIFs on my secondary cluster:
`mn101-ontap101a::> net int show -role intercluster
(network interface show)
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
mn101-ontap101a
ontap101a-iclif1 up/up 10.0.4.68/24 mn101-ontap101a-01 e0b true
ontap101a-iclif2 up/up 10.0.4.69/24 mn101-ontap101a-01 e0c true
2 entries were displayed.
mn101-ontap101a::>`
You can specify a source address in the telnet systemshell command:
mn1-ontap1-01% telnet -h telnet: illegal option -- h usage: telnet [-4] [-6] [-8] [-B baudrate] [-E] [-K] [-L] [-N] [-S tos] [-X atype] [-c] [-d] [-e char] [-k realm] [-l user] [-f/-F] [-n tracefile] [-r] [-s src_addr] [-u] [-P policy] [-y] [host-name [port]] mn1-ontap1-01%
and testing a telnet to one of the snapmirror ports works, the -s being my source IP address:
mn1-ontap1-01% telnet -s 10.0.4.58 10.0.4.68 11104 Trying 10.0.4.68... Connected to 10.0.4.68. ^C ^CConnection closed by foreign host. mn1-ontap1-01%
In the above output, the LIF needed to be owned or at least currently present on the node that you picked for systemshell. You can use 'ifconfig' in systemshell to get a list of inet addresses you can use as the source.
I maintain It would still be helpful to have this built into the ONTAP command line instead of dropping into systemshell, but at least there's some potential workarounds in the meantime
@plucky pagoda this might be helpful?
Very nice! Thank you so much!
Just tried this and it doesn't seem to be possible using SVM LIF's.
bind: Can't assign requested address
snapmirror occurs over the cluster peering link on intercluster LIFs
I intepreted Joels post as an example of what could be done with telnet from systemshell, but I understand now that it only applies to this particular use case and not in the general idea that this Feature request was created with.
Interesting, I'd thought this would work for LIFs owned by data SVMs but yeah it seems to fail to assume any address not owned by the cluster-named SVM