Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

NetApp Exam NS0-162 Topic 3 Question 62 Discussion

Actual exam question for NetApp's NS0-162 exam
Question #: 62
Topic #: 3
[All NS0-162 Questions]

Exhibit

You need to provision a new NFS datastore for a vSphere cluster. You configure a new SVM and a new volume on your ONTAP cluster. You successfully mount the datastore to your vSphere cluster. You are able to upload and download a test 1 KB file to and from the datastore. You can also successfully ping the NFS LIF (192.168.106.11) from the vSphere hosts without any packet loss. However, you are unable to upload ISO Images or migrate VMs to the new datastore.

Referring to the exhibit, which action would correct the problem?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Jaleesa
5 months ago
I think migrating the LIF to its home port might actually be the most effective action to take.
upvoted 0 times
...
Aleisha
5 months ago
I'm going with option C. Change the MTU on the VM kernel ports. Seems the most straightforward way to fix this. Though I do wonder if the network team has been eating too much fiber optic cable again.
upvoted 0 times
Hillary
4 months ago
I agree. Let's give it a try and see if it resolves the problem.
upvoted 0 times
...
Antonette
4 months ago
Yeah, that could definitely solve the issue. Let's hope it's as simple as that.
upvoted 0 times
...
Dorsey
4 months ago
Option C seems like the best choice. Changing the MTU on the VM kernel ports should help.
upvoted 0 times
...
Rosalia
4 months ago
I agree. Let's give it a shot and see if that resolves the issue.
upvoted 0 times
...
Cristal
4 months ago
Yeah, that makes sense. It's worth a try before looking into other options.
upvoted 0 times
...
Reuben
4 months ago
Yeah, that's what I was thinking too. Hopefully that solves the issue.
upvoted 0 times
...
Glendora
4 months ago
Option C sounds like the best solution. Changing the MTU on the VM kernel ports should do the trick.
upvoted 0 times
...
Shaniqua
5 months ago
Option C seems like the best choice. Changing the MTU on the VM kernel ports should do the trick.
upvoted 0 times
...
...
Brandon
5 months ago
But wouldn't changing the MTU of the VM kernel ports on the vSphere hosts to 9,000 bytes be a better solution?
upvoted 0 times
...
Jonell
5 months ago
I disagree, I believe adding a default gateway to the SVM would solve the issue.
upvoted 0 times
...
Bobbye
5 months ago
Migrating the LIF to its home port? That's just moving the problem around. It's like trying to hide your socks when your mom is looking for them.
upvoted 0 times
...
Bong
5 months ago
Ah, but what if the default gateway is the issue? Adding one to the SVM could solve the connectivity problem. You never know what weird network configurations are in place.
upvoted 0 times
Belen
4 months ago
D) Migrate the LIF to Its home port.
upvoted 0 times
...
Romana
4 months ago
C) Change the MTU of the VM kernel ports on the vSphere hosts to 9,000 bytes.
upvoted 0 times
...
Melodie
4 months ago
B) Add a default gateway to the SVM.
upvoted 0 times
...
Krystina
5 months ago
A) Enable jumbo frames on the network switches.
upvoted 0 times
...
...
Brandon
5 months ago
I think the correct action is to enable jumbo frames on the network switches.
upvoted 0 times
...
Pamella
5 months ago
Hmm, I'm not so sure. Enabling jumbo frames on the network switches might be a better solution. That would ensure the entire path can handle the larger packets.
upvoted 0 times
Mica
4 months ago
I agree, that would help ensure the entire path can handle the larger packets.
upvoted 0 times
...
Wai
4 months ago
I think enabling jumbo frames on the network switches is the way to go.
upvoted 0 times
...
...
Vincenza
6 months ago
The issue is definitely with the MTU settings. Changing the VM kernel ports to 9,000 bytes should fix the problem. I've seen this before and it's a common problem.
upvoted 0 times
Judy
5 months ago
Let's go ahead and make that change, it should allow us to upload ISO Images and migrate VMs to the new datastore.
upvoted 0 times
...
Sunshine
5 months ago
I agree, changing the MTU of the VM kernel ports to 9,000 bytes should solve the problem.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77