White Papers

296
Table 2 - FC HBA FQDD examples
FQDD
Friendly Name
FC.Slot.3-2
FC HBA in Slot 3 Port 2
FC.Mezzanine.1B-1
FC HBA in Mezzanine 1 Port 1
297
298 6.2 Virtual Address attributes
299 Virtual address attributes include the following attributes:
300  Virtual World Wide Node Name (VirtualWWN)
301  Virtual World Wide Port Name (VirtualWWPN)
302 The default values of these virtual attributes is equal to the permanent addresses programmed onto the
303 controller.
304 To set these attributes, see Section 8.1 and 8.2 for more details. Virtual address attributes behave
305 differently from the other attributes in the following way:
306 6.2.1 Read Write behavior
307 Generally, the virtual address attributes, as listed above, are read-write attributes through the Lifecycle
308 Controller Remote Services WSMAN interface. This feature allows a remote application to change the
309 virtual identities of FC HBA. However, on number of FC HBA cards these attributes may not be settable,
310 such as the later revisions of QLogic
TM
8Gb Fibre Channel Adapter. For those FC HBA adapters, the
311 IsReadonly property on the virtual attribute instances will have value TRUE.
312 6.2.2 Reset behavior
313 Setting a particular virtual address attribute to zeros causes that particular address to be erased and reset
314 to the default permanent address. The attributes can be set to default permanent values: as equivalent to
315 resetting to factory default and removing a virtual address attribute from a system.
316 When there is AC Power loss to the system, all the virtual address attributes are erased and reset to
317 default addresses when AC Power is restored to the system. AC Power loss includes power loss to both
318 MAIN and AUX power bus.
319 7 Implementation Description
320 Requirements and guidelines for propagating and formulating certain properties of the classes are
321 discussed in this section. Methods are listed in section 8.
322 Table 3 shows the instances of CIM Elements for this profile. Instances of the CIM Elements shall be
323 implemented as described in Table 3. Sections 7 (“Implementation Requirements” and “Methods”) may
324 impose additional requirements on these elements.