![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1016853.1 : VTL - When should "Everyone_FC" be used?
PreviouslyPublishedAs 227176
Applies to:Sun StorageTek VTL Storage ApplianceSun StorageTek VTL Plus Storage Appliance - Version: 1.0 - Build 1323 to 2.0 - Build 1656 [Release: 1.0 to 2.0] Sun StorageTek VTL Prime System - Version: 1.0 - Build 1813 to 1.1 - Build 2076 [Release: 1.0 to 1.0] Sun StorageTek VTL Value System - Version: 1.0 - Build 1323 to 1.0 - Build 1323 [Release: 1.0 to 1.0] All Platforms . ***Checked for relevance on 12-07-2011*** (dd-mm-yyyy) Goal
SolutionEveryone_FC is a convenient feature to get users started without knowing too much about the FC WWPN mappings, mainly for quick testing and demonstration purposes. The use of it is not recommended in a production environment. If a client initiator WWPN is not defined, then it's treated as a "Everyone_FC", and if there are more than one such client, then the device will be shared by all of them. Internally VTL map all such clients to one client "Everyone_FC" so the Reserve/Release would not work properly (causing possible data overwrite issues). However, if there are controls on the client host side to prevent multiple clients from accessing the same virtual device at the same time, Everyone_FC can be used safely. NOTE: If a client was accessing a virtual device via "Everyone_FC" and now is to be defined as a "SAN client", the previously used virtual device must first be removed on the client. Then the SAN client added and virtual devices reconfigured on the client. Attachments This solution has no attachment |
||||||||||||
|