Figure 25 Consistency of I/O addressing

Device Addressing Identification

System Event

L

 

L

 

 

 

 

 

 

un

 

egac

 

 

 

 

UNpath

 

 

L

 

 

 

 

 

L

 

 

 

 

 

 

 

 

 

Per

 

 

 

 

y

 

 

 

 

 

 

 

 

 

yH/W evi

 

 

 

 

egac

 

 

 

 

 

H/W

 

 

 

 

 

 

tentH/W

 

 

 

 

 

 

 

sis

 

 

 

 

 

 

D

ce

 

 

 

P

P

 

D

P

 

 

 

 

 

 

SF ath

ath

SFath

 

D

 

 

 

 

 

 

 

 

WWI D D

Reboot

C

C

C

C

C

C

C

Reinstallation on same system and devices.

N

N

C

N

C

C

C

Installation with replacement of system and/or HBAs

N N C N C C C

with same model and config using the same devices

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Installation with same system and config using

N N *

N * N N

replacement devices

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Installation with other hardware changes

N

N

N

N

N

N

N

 

 

 

 

 

 

 

 

Recovery with same system and devices

R

N

C

R

C

C

C

 

 

 

 

 

 

 

 

Recovery with replacement of system and/or HBAs

R

N C

R

C

C C

with same model and config using the same devices

 

 

 

 

 

 

 

Recovery with same system and config using

replacement devices

R N * R * N N

Recovery with other hardware changes

N N N N N N N

Use the following key for the “Consistency of I/O Addressing” figure above.

C = Consistent — Device addressing id value is saved in HP-UX config content and the correlation between these values and devices does not change as a result of the event.

N = New Value — Device addressing id value is newly created as a result of the event. The device addressing id value for a device might or might not change as a result of the event.

R = Recovered — Ignite-UX will restore the association between device addressing id values and devices when possible. The process used to match previous and current devices is handled by Ignite-UX recovery matching methods. Matching might not be possible if the system configs differ.

*— Might be a consistent value for some I/O protocols such as parallel SCSI, and might be a new value for some I/O protocols such as fibre channel.

Practical considerations

79