Configuring Domain Parameters
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
About Persistent FC IDs
When persistent FC IDs are enabled, the following consequences apply:
If you connect to the switch from an AIX or HP-UX host, be sure to enable the persistent FC ID feature
in the VSAN that connects these hosts.
FC IDs are enabled by default. This change of default behavior from releases prior to Cisco MDS
SAN-OS Release 2.0(1b) prevents FC IDs from being changed after a reboot. You can disable this option
for each VSAN.
A persistent FC ID assigned to an F port can be moved across interfaces and can continue to maintain
the same persistent FC ID.
Persistent FC IDs with loop-attached devices (FL ports) need to remain connected to the same port in
which they were configured.
Due to differences in Arbitrated Loop Physical Address (ALPA) support on devices, FC ID persistency
for loop-attached devices is not guaranteed.
Enabling the Persistent FC ID Feature
To enable the persistent FC ID feature, follow these steps:
switch# config t
OL-16184-01, Cisco MDS SAN-OS Release 3.x
About Persistent FC IDs, page 17-15
Enabling the Persistent FC ID Feature, page 17-15
About Persistent FC ID Configuration, page 17-16
Configuring Persistent FC IDs, page 17-17
About Unique Area FC IDs for HBAs, page 17-17
Configuring Unique Area FC IDs for an HBA, page 17-17
About Persistent FC ID Selective Purging, page 17-19
Purging Persistent FC IDs, page 17-19
The currently in use FC IDs in the fcdomain are saved across reboots.
The fcdomain automatically populates the database with dynamic entries that the switch has learned
about after a device (host or disk) is plugged into a port interface.
Enters configuration mode.
Cisco MDS 9000 Family CLI Configuration Guide