NS0-157 · Question #347
Which of the following statements are true about SAN LIFs? (choose all that apply)
The correct answer is A. SAN LIFs are either up or down E. NAS and SAN LIFs can share the same data port. SAN LIFs in NetApp ONTAP have a simple binary up/down state with no failover or migration, but multiple LIFs of different protocol types can share the same physical data port.
Question
Which of the following statements are true about SAN LIFs? (choose all that apply)
Options
- ASAN LIFs are either up or down
- BNAS and SAN protocols can share the same LIF
- CSAN LIFS can migrate or failover
- DSAN LIFs can be associated with more than one data vserver
- ENAS and SAN LIFs can share the same data port
How the community answered
(16 responses)- A88% (14)
- B6% (1)
- C6% (1)
Why each option
SAN LIFs in NetApp ONTAP have a simple binary up/down state with no failover or migration, but multiple LIFs of different protocol types can share the same physical data port.
SAN LIFs (FC and iSCSI) operate in only an up or down state - unlike NAS LIFs, they have no migration or partial-active state, and SAN redundancy is handled entirely by host-side multipath I/O (MPIO).
NAS and SAN protocols cannot share the same LIF - each LIF is configured for a specific protocol type (NFS/CIFS or FC/iSCSI) and cannot carry both simultaneously.
SAN LIFs do not support migration or failover - because SAN hosts use persistent WWPN/IQN bindings, moving a LIF would break those connections, so host-side MPIO handles redundancy instead.
Each SAN LIF belongs to exactly one data SVM (vserver) and cannot be associated with or shared across multiple data SVMs.
A single physical data port can host both NAS and SAN LIFs simultaneously, as ONTAP allows multiple LIFs of different protocol types to be bound to the same underlying port.
Concept tested: NetApp ONTAP SAN LIF state behavior and port sharing rules
Source: https://docs.netapp.com/us-en/ontap/san-admin/manage-lifs-all-san-protocols-concept.html
Topics
Community Discussion
No community discussion yet for this question.