AMX Rack Rail Kit MMS Servers Specifications Page 135

  • Download
  • Add to my manuals
  • Print
  • Page
    / 142
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 134
Chapter 4. Continuous availability and manageability 121
Draft Document for Review September 2, 2008 5:05 pm4405ch04 Continuous availability and manageability.fm
򐂰 Accepted level – This is the backup level of server or power subsystem firmware. You can
return to this level of server or power subsystem firmware if you decide to remove the
installed level. It is installed on the
p side of system firmware.
IBM provide the Concurrent Firmware Maintenance (CFM) function on System p systems.
This function supports applying nondisruptive system firmware service packs to the system
concurrently (without requiring a reboot to activate changes). For systems that are not
managed by an HMC, the installation of system firmware is always disruptive.
The concurrent levels of system firmware can, on occasion, contain fixes that are known as
deferred. These deferred fixes can be installed concurrently but are not activated until the
next IPL. For deferred fixes within a service pack, only the fixes in the service pack, which
cannot be concurrently activated, are deferred. Figure 4-9 shows the system firmware file
naming convention.
Figure 4-9 firmware file naming convention
Here is one example.
Example 4-1
01EM310_026_026 = Managed System Firmware for 9117-MMA Release 310 Fixpack 026
An installation is disruptive if:
򐂰 The release levels (SSS) of currently installed and new firmware are different.
򐂰 The service pack level (FFF) and the last disruptive service pack level (DDD) are equal in
new firmware.
Otherwise, an installation is concurrent if:
򐂰 The service pack level (FFF) of the new firmware is higher than the service pack level
currently installed on the system and the above conditions for disruptive installation are
not met.
4.5.7 Management Edition for AIX
IBM Management Edition for AIX (ME for AIX) is designed to provide robust monitoring and
quick time to value by incorporating out-of-the box best practice solutions that were created
by AIX and PowerVM Virtual I/O Server developers. These best practice solutions include
predefined thresholds for alerting on key metrics, Expert Advice that provides an explanation
of the alert and recommends potential actions to take to resolve the issue, and the ability to
Page view 134
1 ... 134 135 136 137 138 139 140 141 142

Comments to this Manuals

No comments