HP StorageWorks 2/8-EL quickloop fabric assist version 3.0.x user guide - Page 36

Preferred Phantom AL_PA Assignment, AL_PA Assignment Rules

Get HP StorageWorks 2/8-EL - SAN Switch PDF manuals and user guides View all HP StorageWorks 2/8-EL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 36 highlights

Using QuickLoop Fabric Assist Mode Preferred Phantom AL_PA Assignment When "cfg" is enabled, phantoms for all online zoned targets are created on the private host's loop and is re-LIPed so that it can see any newly added phantoms. As additional targets join the fabric, within the Fabric Assist zone (fazone), a phantom is created on the private host's loop, which is triggered off the Registered State Change Notification (RSCN). A target can be zoned with more than one private host, and may have a unique phantom created on each host's loop. Refer to Figure 1 for an example of the preferred AL_PA process. A preferred phantom AL_PA assignment can have the following characteristics: ■ A private Fabric Assist host 0x01 has two phantoms created on its loop. One for each target for which it is zoned. ■ A private format frame sent from 0x01 to 0x02 translates into a public format frame and then routed to the public device located at port 12. ■ Adding a new target that is already zoned with the private host causes a new phantom to be created, and the host's loop is reLIPed. The target on port 8 is be reLIPed. ■ A private host loop is not reLIPed when a phantom is removed. AL_PA Assignment Rules The following rules are applied when AL_PA assignments are made: ■ Loop targets that have an AL_PA value are assigned the same AL_PA as their phantom AL_PA. ■ N_Port targets are assigned the first available AL_PA on the host's loop. ■ Phantoms are kept persistent for a device as long as the switch where these phantoms are created is operational. ■ When a switch reboots, the phantom addresses for the targets may change, which means they are not persistent across reboots or fastboots. ■ When a new "cfg" is enabled, the phantom addresses for the targets may change. ■ Some private hosts have firmware that requires their targets to have specific AL_PA values. ■ Preferred AL_PA assignments (see Figure 1) may be identified at the time of zone creation. 36 Quickloop Fabric Assist User Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
Using QuickLoop Fabric Assist Mode
36
Quickloop Fabric Assist User Guide
Preferred Phantom AL_PA Assignment
When “cfg” is enabled, phantoms for all online zoned targets are created on the
private host’s loop and is re-LIPed so that it can see any newly added phantoms.
As additional targets join the fabric, within the Fabric Assist zone (fazone), a
phantom is created on the private host’s loop, which is triggered off the Registered
State Change Notification (RSCN). A target can be zoned with more than one
private host, and may have a unique phantom created on each host’s loop.
Refer to Figure 1 for an example of the preferred AL_PA process.
A preferred phantom AL_PA assignment can have the following characteristics:
■
A private Fabric Assist host 0x01 has two phantoms created on its loop. One
for each target for which it is zoned.
■
A private format frame sent from 0x01 to 0x02 translates into a public format
frame and then routed to the public device located at port 12.
■
Adding a new target that is already zoned with the private host causes a new
phantom to be created, and the host’s loop is reLIPed. The target on port 8 is
be reLIPed.
■
A private host loop is not reLIPed when a phantom is removed.
AL_PA Assignment Rules
The following rules are applied when AL_PA assignments are made:
■
Loop targets that have an AL_PA value are assigned the same AL_PA as their
phantom AL_PA.
■
N_Port targets are assigned the first available AL_PA on the host’s loop.
■
Phantoms are kept persistent for a device as long as the switch where these
phantoms are created is operational.
■
When a switch reboots, the phantom addresses for the targets may change,
which means they are not persistent across reboots or fastboots.
■
When a new “cfg” is enabled, the phantom addresses for the targets may
change.
■
Some private hosts have firmware that requires their targets to have specific
AL_PA values.
■
Preferred AL_PA assignments (see Figure 1) may be identified at the time of
zone creation.