Unfortunately what you're experiencing is how it works. While XenServer does support different CHAP credentials by SR, it only supports a single CHAP credential for discovery. It can be made to work, but you'd need to either modify how the storage manager works to pull it off, or rewrite some of the init scripts to cache the discovery data.
On Wed, Dec 18, 2013 at 3:55 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > Hi, > > I just noticed a problem today while creating SRs in XenServer. Perhaps > someone with related experience could point me in the right direction. > > Let's say my SAN's management IP address is X. > > I can have XenServer create a shared SR using IP address X with CHAP > credentials Y. > > If I try to have XenServer create another shared SR using IP address X that > uses different CHAP credentials (ex. CHAP credentials Z), XenServer returns > a discovery failure. > > It's like XenServer is expecting all iSCSI targets at the same IP address > to have the same CHAP credentials. > > Does anyone know if I am mistaken here? This seems like a critical defect > if this is true. > > Thanks! > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *™* >
