HP0-J73 · Question #182
A system administrator is updating the firmware on an FCoE converged network (CN) switch. How should the FCoE CN switch be configured to minimize disruption of port connectivity during the update proc
The correct answer is B. Implement a dual path configuration with redundant FCoE CN switches.. A dual-path configuration with redundant FCoE CN switches ensures that connected ports can fail over to the secondary switch during a firmware update, eliminating disruption to connectivity.
Question
A system administrator is updating the firmware on an FCoE converged network (CN) switch. How should the FCoE CN switch be configured to minimize disruption of port connectivity during the update process?
Options
- AUpdate the driver for the CNA before beginning the firmware update.
- BImplement a dual path configuration with redundant FCoE CN switches.
- CCreate logical switches within the physical switch by dividing the switch ports and assigning them to
- DAssign a unique virtual port name to each virtual machine that shares the switch port.
How the community answered
(23 responses)- A4% (1)
- B74% (17)
- C9% (2)
- D13% (3)
Why each option
A dual-path configuration with redundant FCoE CN switches ensures that connected ports can fail over to the secondary switch during a firmware update, eliminating disruption to connectivity.
Updating the CNA driver addresses host-side firmware or software compatibility but does not prevent connectivity disruption caused by the CN switch itself going through a firmware update.
When redundant FCoE CN switches are deployed in a dual-path topology, hosts and storage targets maintain active paths through both switches simultaneously. Taking one switch through a firmware update does not interrupt port connectivity because all traffic continues to flow through the alternate switch, eliminating the single point of failure that would otherwise cause disruption.
Creating logical switches partitions a physical switch into isolated segments for traffic separation, but all logical switch instances share the same physical firmware and would all be disrupted simultaneously during the update.
Assigning unique virtual port names to virtual machines is a naming or zoning practice for identification purposes and has no effect on maintaining port connectivity during a physical switch firmware update.
Concept tested: FCoE dual-path redundancy for non-disruptive switch firmware updates
Source: https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/fcoe/b_5k_FCoE_Config_Guide.html
Topics
Community Discussion
No community discussion yet for this question.