Ok, looking through the responses, I guess I'm stumped.
The SES processor isn't likely assigning the FC-AL ID's; it's usually not that smart. The SES processor will give status information (and possibly some limited control) about the drives, but there's usually a hard configuration option in the shelf to give a starting address. For example, I seem to recall the older NetApp FC shelves or maybe the Clariion ones (it's been a long time) had either a dial switch or up/down switches to select the starting address. Then each drive bay is incremented.
Knowing that they show up differently in the hinv every time, then it sounds like whichever drive is spinning up first is assigned an FC-AL address first. I think there may have been an "auto" mode in FC-AL where if there isn't a drive position specified, one is assigned automatically, but those details are a bit fuzzy.
Does the DS9 have any switches on it anywhere? If so, that might configure the "auto" mode. And also, has the DS9 always misbehave this way, or did it just recently start misbehaving?
Chris
The SES processor isn't likely assigning the FC-AL ID's; it's usually not that smart. The SES processor will give status information (and possibly some limited control) about the drives, but there's usually a hard configuration option in the shelf to give a starting address. For example, I seem to recall the older NetApp FC shelves or maybe the Clariion ones (it's been a long time) had either a dial switch or up/down switches to select the starting address. Then each drive bay is incremented.
Knowing that they show up differently in the hinv every time, then it sounds like whichever drive is spinning up first is assigned an FC-AL address first. I think there may have been an "auto" mode in FC-AL where if there isn't a drive position specified, one is assigned automatically, but those details are a bit fuzzy.
Does the DS9 have any switches on it anywhere? If so, that might configure the "auto" mode. And also, has the DS9 always misbehave this way, or did it just recently start misbehaving?
Chris
(<-EMXI/IO6G)
(<- quad R12k O200 w/GIGAchannel and ESI+Tex) plus a bunch of assorted standalone workstations...