A state university runs an edge MDS in NPV mode so the edge does not take a domain ID, but the servers still cannot complete fabric login toward the core. NPIV is disabled on the core switch. What must change on the core?
Select an answer to reveal the explanation.
Short Explanation
The branch office is not allowed to be its own city, so the main post office has to accept mail for every resident. You enable NPIV on the core so those server logins are legal on the uplink from the NPV edge. Handing the edge a domain ID throws away the NPV design instead of fixing the core.
Full Explanation
An NPV edge switch does not join the fabric as a domain. Its uplink is an NP port, and the servers behind it log in through the core. The core can accept multiple fabric logins on that link only when NPIV is enabled. With NPIV left off, the university servers cannot complete login even though the edge was correctly kept out of the domain-ID space. Enabling NPIV on the core is the change that matches the design. Assigning a static domain ID on the edge means leaving NPV and becoming a fabric switch, which is the opposite of the reason NPV was turned on. An empty zoneset does not convert an NP uplink into an E port, and zoning is not a substitute for NPIV. CFS distributes selected databases such as device aliases. Turning it off does not lend a domain ID to an NPV switch, and an NPV switch is not supposed to receive one. Caveat: the uplink still has to land on an F port on the core, and the servers still need to be zoned and masked after NPIV lets them log in. Operational check: enable NPIV on the core, confirm the edge uplink comes up as an NP port, and confirm the server FLOGIs appear on the core rather than on a new edge domain.