Cisco DS-C9216I-K9, Руководство по настройке

Страница: 361 / 436

26-11
Cisco MDS 9000 Fabric Manager Switch Configuration Guide
OL-7753-01
Chapter 26 Configuring Domain Parameters
Purging Persistent FC IDs
•
A N or NL port logs into a Cisco MDS 9000 Family switch, the WWN of the requesting N or NL
port and the assigned FC ID, are retained and stored in a volatile cache. The contents of this volatile
cache are not saved across reboots.
• The switch is designed to preserve the binding FC ID to the WWN, on a best-effort basis. For
example, if one N port disconnects from the switch and its FC ID is requested by another device,
this request is granted, and the WWN with the initial FC ID association is released.
•
The volatile cache stores up to 4000 entries of WWN to FC ID binding. If this cache is full, a new
(more recent) entry overwrites the oldest entry in the cache. In this case, the corresponding WWN
to FC ID association for the oldest entry is lost.
• The switch connection behavior differs between N ports and NL ports:
–
N ports receive the same FC IDs if disconnected and reconnected to any port within the same
switch (as long as it belongs to the same VSAN).
– NL ports receive the same FC IDs only if connected back to the same port on the switch to which
it was originally connected.
The assigned FC IDs in a fcdomain can be enabled to remain persistent even after a reboot. This ensures
that an attached N port receives the same FC IDs after a reboot. If you enable this feature, the following
consequences apply:
• 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.
Note
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.
Note
Persistent FC IDs with loop-attached devices (FL ports) need to remain connected to the same port in
which they were configured.
A persistent FC ID assigned to an F port can be moved across interfaces and can continue to maintain
the same persistent FC ID.
Purging Persistent FC IDs
Persistent FC IDs can be purged selectively. Static entries and FC IDs currently in use cannot be deleted.
Table 26-1 identifies the FC ID entries that can be deleted.
Table 26-1 Purged FC IDs
Persistent FC ID state Persistent Usage State Action
static in use Not deleted
static not in use Not deleted
dynamic in use Not deleted
dynamic not in use deleted