Deal of The Day! 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 create a storage virtual machine (SVM) called SVM500 that is provisioned for iSCSI. After creating a LUN in the SVM and mapping it to an igroup, the attached VMware hosts are unable to mount the LUN.

Referring to the exhibit, what is the issue?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Jaleesa
1 years ago
I think migrating the LIF to its home port might actually be the most effective action to take.
upvoted 0 times
...
Aleisha
1 years 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
12 months ago
I agree. Let's give it a try and see if it resolves the problem.
upvoted 0 times
...
Antonette
12 months ago
Yeah, that could definitely solve the issue. Let's hope it's as simple as that.
upvoted 0 times
...
Dorsey
12 months ago
Option C seems like the best choice. Changing the MTU on the VM kernel ports should help.
upvoted 0 times
...
Rosalia
12 months ago
I agree. Let's give it a shot and see if that resolves the issue.
upvoted 0 times
...
Cristal
1 years ago
Yeah, that makes sense. It's worth a try before looking into other options.
upvoted 0 times
...
Reuben
1 years ago
Yeah, that's what I was thinking too. Hopefully that solves the issue.
upvoted 0 times
...
Glendora
1 years ago
Option C sounds like the best solution. Changing the MTU on the VM kernel ports should do the trick.
upvoted 0 times
...
Shaniqua
1 years ago
Option C seems like the best choice. Changing the MTU on the VM kernel ports should do the trick.
upvoted 0 times
...
...
Brandon
1 years 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
1 years ago
I disagree, I believe adding a default gateway to the SVM would solve the issue.
upvoted 0 times
...
Bobbye
1 years 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
1 years 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
12 months ago
D) Migrate the LIF to Its home port.
upvoted 0 times
...
Romana
12 months ago
C) Change the MTU of the VM kernel ports on the vSphere hosts to 9,000 bytes.
upvoted 0 times
...
Melodie
12 months ago
B) Add a default gateway to the SVM.
upvoted 0 times
...
Krystina
1 years ago
A) Enable jumbo frames on the network switches.
upvoted 0 times
...
...
Brandon
1 years ago
I think the correct action is to enable jumbo frames on the network switches.
upvoted 0 times
...
Pamella
1 years 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
1 years ago
I agree, that would help ensure the entire path can handle the larger packets.
upvoted 0 times
...
Wai
1 years ago
I think enabling jumbo frames on the network switches is the way to go.
upvoted 0 times
...
...
Vincenza
1 years 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
1 years 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
1 years ago
I agree, changing the MTU of the VM kernel ports to 9,000 bytes should solve the problem.
upvoted 0 times
...
...

Save Cancel