Comment 6 for bug 1809249
Revision history for this message
| Walt Boring (walter-boring) wrote Re: OS-brick FC scan fails when 3Par is not exported to controllers/computes through all FC targets | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
It also looks like the FC fabric is manually zoned and isn't zoned to include the port picked by the 3PAR driver when running with multipath capability disabled in cinder.
The only way to fix this is to,
1) enabled multipath correctly in cinder.conf
2) since using manual zoning, add the 3par port in question to the FC zone on the switch
3) use the Cinder Fiber Channel Zone manager to manage the fabric zoning.
4) add a new feature to the 3PAR driver to allow the admin to specify which NSP on the 3PAR to use when attaching when multipath isn't enabled correctly. The 3PAR driver is currently automatically picking the first NSP it sees that's enabled on the 3PAR.