Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Does someone have a basic process/procedure to go through where a client from a Window/Linux machine cannot contact the nfs/CFS shares due to a probably network issue? I tend to get confused with all the different IP in play across this scenario.
many thanks
Larry
5 REPLIES 5
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Depends on the error that the client is getting. if it's something like "cannot connect" or just spins, I will do pings between the client to the Netapp's NAS Data lif and from the Netapp's data lif to the client
If it's like "you do not have permissions". you'll need to check the share permission on the Netapp
Few other helpful links for you -
https://docs.netapp.com/us-en/ontap-cli-9141//network-ping.html
you'll want to ping in the context of the vserver (SVM) and lif
https://docs.netapp.com/us-en/ontap/networking/commands_for_diagnosing_network_problems.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I thought these links might be helpful
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi larry
I hope my reply is helpful to you
1. Identify the Environment
Determine the Client OS:
Windows or Linux.
Identify the NFS/CFS IP Address:
Ensure that the correct IP address is configured
2. Verify Network Connectivity
Ping the NFS/CFS IP:
Run the Ping command to ensure reachability
network ping
Check Routing:
Check that the route configuration is correct
network route show
3. Check Firewall Settings
Ensure that the firewall allows the traffic required by NFS/CFS
4. Network Configuration Issues
Ensure there are no IP address conflicts on the network.
Check that the subnet mask and gateway Settings are correct
5. Testing with Other Clients
If possible, test connectivity from another client machine to determine if the issue is isolated to one client or more widespread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, thank you very much.
________________________________
This email, including any attachments, is confidential. If you have received this email in error, please let me know and then delete it - do not read, use, or distribute it or its contents. This email does not designate an information system for the purposes of the Contract and Commercial Law Act 2017.
________________________________
This email, including any attachments, is confidential. If you have received this email in error, please let me know and then delete it - do not read, use, or distribute it or its contents. This email does not designate an information system for the purposes of the Contract and Commercial Law Act 2017.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your best bet is wireshark on client and tcpdump on NetApp side.
