Storage Network practice questions

FIP operates only over lossless Ethernet.

Why wrong: FIP operates over any Ethernet, but FCoE requires lossless.

FIP is used only for FCoE initialization, not for maintenance.

Why wrong: FIP handles keep-alives and link maintenance.

FIP requires IP addresses to establish FCoE sessions.

Why wrong: FIP is Layer 2, not Layer 3.

Delete the active zone set and create a new one.

Why wrong: Disrupts existing traffic.

Edit the active zone set directly.

Why wrong: May cause inconsistency.

Use the 'commit' command to update the zone set.

Why wrong: Not a standard command.

Fibre Channel ports are in trunk mode.

Why wrong: Trunking is allowed.

The core switch has NPV mode enabled.

Why wrong: Core should not be NPV.

The NPV switch has an incorrect domain ID.

Why wrong: NPV does not use domain IDs.

Disabling flow control.

Why wrong: Flow control is essential.

Enabling broadcast zoning.

Why wrong: Broadcast increases overhead.

Setting fabric login timeout to the maximum.

Why wrong: Does not improve performance.

FCoE Forwarder (FCF)

Why wrong: FCF forwards FCoE frames, but encapsulation is done by the endpoint.

Virtual Fibre Channel interface (VFC)

Why wrong: VFC is a logical interface, not the encapsulator.

VN interface

Why wrong: VN interface is a virtual N-port.

Incorrect domain ID.

Why wrong: Domain ID issues cause fabric login problems.

Buffer credit starvation.

Why wrong: Buffer credit issues cause frame drops, not CRC.

Incorrect zone configuration.

Why wrong: Zoning issues cause login failures, not CRC.

IOM (I/O Module)

Why wrong: IOM is for chassis connectivity, not direct SAN.

Cisco VIC adapter

Why wrong: VIC presents virtual interfaces, not direct SAN connectivity.

UCS Manager

Why wrong: Management plane only.

Jumbo frames must be enabled.

Why wrong: Not strictly required, though recommended.

Spanning Tree Protocol must be disabled.

Why wrong: STP can be used but is often disabled for FCoE VLANs.

Link aggregation (LACP) is required.

Why wrong: Not required.

Use multiple initiators in a single zone.

Why wrong: Increases risk of misconfiguration.

Use soft zoning exclusively.

Why wrong: Soft zoning is less secure.

Disable zoning for performance.

Why wrong: Zoning is required for security.

Reduce the buffer credit count.

Why wrong: Reducing buffer credits increases latency.

Enable trunking on the ISL.

Why wrong: Trunking allows multiple VSANs, but doesn't reduce latency.

Disable flow control on the ISL.

Why wrong: Flow control helps prevent drops, not reduce latency.

Provide encryption on Fibre Channel links.

Why wrong: Not related.

Enable multiple paths between initiator and target.

Why wrong: That's multipathing.

Allow a switch to act as an NPV device.

Why wrong: NPV is different.

Use the same VLAN for FCoE and LAN.

Why wrong: Causes interference.

Disable flow control on FCoE VLAN.

Why wrong: FCoE needs flow control.

Use jumbo frames for LAN traffic only.

Why wrong: Not a separation mechanism.

It increases the maximum distance of Fibre Channel links.

Why wrong: Distance is limited by Ethernet.

It provides native Fibre Channel security.

Why wrong: FCoE uses FC security but not natively.

It eliminates the need for zoning.

Why wrong: Zoning is still required.

Port channels

Why wrong: Port channels aggregate bandwidth.

NPV

Why wrong: NPV is for edge switches.

IVR (Inter-VSAN Routing)

Why wrong: IVR routes between VSANs, not isolate.

It enables NPV mode on VSAN 100.

Why wrong: Not related.

It clears the zone configuration for VSAN 100.

Why wrong: Does not affect zones.

It reboots the switch.

Why wrong: Only restarts FC domain.

Reconfigure the vHBAs on the UCS Manager with new WWPNs.

Why wrong: WWPNs are persistent; reconfiguration is unnecessary.

Check the storage array LUN masking and re-apply LUN access.

Why wrong: LUNs are accessible from MDS, so storage is fine.

Downgrade the MDS firmware to the previous version.

Why wrong: Not necessary; configuration issue is more likely.

Reduce the buffer credit count on the backup VSAN ISLs to reduce latency.

Why wrong: Latency is not the issue.

Enable QoS to prioritize backup traffic over other traffic.

Why wrong: QoS does not increase bandwidth.

Implement IVR to route backup traffic through the other fabric.

Why wrong: IVR adds complexity and does not add bandwidth to the backup VSAN.

show zone

Why wrong: Shows all configured zones but not necessarily the active set.

show flogi database

Why wrong: Shows fabric login information, not the name server or active zoneset.

show fcns details

Why wrong: 'show fcns details' is not a valid Cisco NX-OS command.

FSPF is not enabled on the NPV switch.

Why wrong: NPV switches do not run FSPF; they rely on the core switch's FSPF.

The NPV switch does not have the proper license for NPV mode.

Why wrong: NPV mode is included in the base NX-OS license and does not require an additional license.

NPV

Why wrong: NPV reduces domain IDs but does not provide redundancy.

VSAN trunking

Why wrong: VSAN trunking allows multiple VSANs over a single link, not switch redundancy.

IVR

Why wrong: IVR is for inter-VSAN routing, not redundancy within a single VSAN.