Flexattach Virtual Pwwn Cfs Distribution; Difference Between San Device Virtualization And Flexattach Port Virtualization - Cisco MDS 9000 Series Configuration Manual

Difference Between San Device Virtualization and FlexAttach Port Virtualization

S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
For more details on enabling port security, refer to the Cisco MDS 9000 Family NX-OS Security
Configuration Guide.

FlexAttach Virtual pWWN CFS Distribution

The FlexAttach virtual pWWN configuration is distributed for CFS through IPv4, and is enabled by
default. The FlexAttach virtual pWWN distribution, by default, is on CFS region 201. The CFS region
201 links only to the NPV-enabled switches. Other CFS features such as syslog is on region 0. Region 0
will be linked through IPv4 for all NPV switches on the same physical fabric. If CFS has an option to
link through IPv4 or ISL, then CFS will select the ISL path.
NPV switches do not have ISL (E or TE ports) and are linked through IPv4.
Note
Difference Between San Device Virtualization and FlexAttach
Port Virtualization
Table 8-2
virtualization.
Table 8-2 Difference Between SDV and FlexAttach Virtualization
SAN Device Virtualization (SDV)
Facilitates target and disk management, and only
facilitates disk and data migration.
WWN NAT and Fibre Channel ID (FC-ID) are
allocated on the virtual device, both primary and
secondary.
FC-ID rewrite on the switch indicates a
rewrite-capable switch on the path.
Configuration is distributed. This allows
programming rewrites and connectivity
anywhere.
Configuration is secured to device alias.
Does not allow automapping to the secondary
device.
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
8-6
describes the difference between SAN device virtualization (SDV) and FlexAttach port
Chapter 8 Configuring FlexAttach Virtual pWWN
FlexAttach Virtualization
Facilitates server management and has no
restriction on the end devices used.
WWN and Network Address Transport (NAT) is
allocated to host bus adapter (HBA).
No rewrite requirements.
Configuration distribution is not required for any
of the interface-based configurations.
Does not require device alias for virtual pWWN.
Allows automapping to the new HBA. Mapping
process is manual for NPIV.
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)