The answer is that the FIP snooping policy is blocking the FLOGI. This is the most likely issue because the initiator appears in the show fcoe database on the Nexus switch but the session remains in a “FIP-VN_Port not logged in” state, which indicates the FLOGI request is being dropped before the session can become active. FIP snooping acts as a firewall for FCoE traffic, and if the initiator’s MAC address is not in the allowed FCoE MAC list or the policy is misconfigured, the switch will silently discard the FLOGI, preventing login even though the VSAN and zone configuration are correct. On the Cisco DCCOR 350-601 exam, this scenario tests your understanding of FIP snooping’s role in FCoE initialization and the distinction between a database entry and an active session. A common trap is assuming a zone or VSAN mismatch is the culprit when the real issue is a missing or misapplied FIP snooping policy. Memory tip: If the FCoE database shows the initiator but the session is not active, think “FIP snooping is the gatekeeper—check the MAC allow list first.”
350-601 Storage Network Practice Question
This 350-601 practice question tests your understanding of storage network. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A large enterprise uses Cisco Nexus 5548UP switches in FCoE mode. The storage array is connected via native FC to an MDS 9700. The FCoE switches are connected to the MDS via FC uplinks. Recently, the storage team deployed a new FCoE initiator that requires access to a specific LUN. After configuring the zone and VSAN, the initiator cannot discover the target. The zone includes the pWWN of the target and the FCoE initiator's pWWN (derived from its MAC address). The initiator is in VSAN 100, and the target is in the same VSAN. The MDS show flogi database shows the initiator. The show fcoe database on the Nexus shows the initiator but the session is not active (state: FIP-VN_Port not logged in). The engineer checks the FIP snooping policy and notices that the FCoE VLAN to VSAN mapping is correct. What is the most likely issue?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The FIP snooping policy is blocking the FLOGI
The FCoE initiator appears in the FCoE database but is not logged in, indicating the FLOGI is being dropped. The FIP snooping policy on the Nexus switch may be blocking the FLOGI traffic because the initiator's MAC address is not in the allowed FCoE MAC list or the policy is misconfigured. Incorrect VN_Port MAC would prevent FCoE database entry, NPV is not required for FCoE native mode, and routing is not an issue within the same VSAN.
Key principle: A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The MDS does not have a route to the FCoE initiator's VSAN
Why it's wrong here
The initiator and target are in the same VSAN, so routing is irrelevant.
✗
The FCoE initiator is not using the correct VN_Port MAC address
Why it's wrong here
If the MAC were incorrect, the initiator would not appear in the FCoE database.
✓
The FIP snooping policy is blocking the FLOGI
Why this is correct
FIP snooping uses ACLs to enforce zoning; if misconfigured, it can drop FLOGI frames.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Access ports place end devices into a single VLAN.
✗
The FCoE NPV is not enabled on the Nexus
Why it's wrong here
NPV is not required for this topology; the Nexus is in FCoE mode, not NPV.
Common exam traps
Common exam trap: an active trunk can still block the VLAN you need
A trunk being up does not prove every VLAN is crossing it. Check allowed VLAN lists, native VLAN mismatch, VLAN existence and access-port assignment.
Detailed technical explanation
How to think about this question
VLAN questions usually combine access-port and trunking clues. The key is to identify whether the issue is local to one switchport, caused by the trunk, or caused by the VLAN not existing where it needs to exist.
KKey Concepts to Remember
Access ports place end devices into a single VLAN.
Trunk ports carry multiple VLANs between switches.
Allowed VLAN lists decide which VLANs can cross a trunk.
Native VLAN mismatch can create confusing symptoms.
TExam Day Tips
→Use show vlan brief to verify access VLANs.
→Use show interfaces trunk to verify trunk state and allowed VLANs.
→Do not treat every same-VLAN issue as a routing problem.
Key takeaway
A trunk being up does not mean the VLAN is allowed across it. Always verify the allowed VLAN list and whether the VLAN exists on both switches.
Real-world example
How this comes up in practice
A help-desk technician troubleshoots why a newly connected PC cannot reach shared printers on the same floor. The cable is good, the switch port is active, but the PC is in VLAN 20 and the printers are in VLAN 10. The uplink trunk only allows VLAN 10. A trunk being up does not mean every VLAN crosses it.
What to study next
Got this wrong? Here's your next step.
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related 350-601 questions on switching, trunking, and access-port configuration.
Storage Network — This question tests Storage Network — Access ports place end devices into a single VLAN..
What is the correct answer to this question?
The correct answer is: The FIP snooping policy is blocking the FLOGI — The FCoE initiator appears in the FCoE database but is not logged in, indicating the FLOGI is being dropped. The FIP snooping policy on the Nexus switch may be blocking the FLOGI traffic because the initiator's MAC address is not in the allowed FCoE MAC list or the policy is misconfigured. Incorrect VN_Port MAC would prevent FCoE database entry, NPV is not required for FCoE native mode, and routing is not an issue within the same VSAN.
What should I do if I get this 350-601 question wrong?
Review VLAN allowed lists, native VLAN mismatch detection, and how to verify VLAN membership with show vlan brief and show interfaces trunk. Then practise related 350-601 questions on switching, trunking, and access-port configuration.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Access ports place end devices into a single VLAN.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An engineer is configuring FCoE on a Cisco Nexus 5000 switch. The switch connects to a Fibre Channel storage array. The FCoE Initialization Protocol (FIP) snooping must be enabled. What is the effect of enabling FIP snooping?
C.It enables the switch to act as an FCoE forwarder.
✓ D.It constructs a database of ENode MAC addresses and FC-MAPs.
E.It allows the switch to enforce zone-based policy for FCoE traffic.
Why D: FIP snooping on a Cisco Nexus 5000 switch constructs a database of ENode MAC addresses and FC-MAPs by inspecting FIP discovery, advertisement, and login frames. This database is used to enforce FCoE traffic only between authorized ENodes and FCFs, preventing rogue devices from injecting FCoE traffic. It does not terminate FCoE VLANs, act as an FCoE forwarder, or enforce zone-based policies directly.
Last reviewed: Jun 24, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This 350-601 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-601 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.