IBM Flex System(TM) Manager, Version 1.3.

2 fix pack Readme

Readme file for: IBM Flex System Manager Update Package
Product/Component Release: 1.3.2
Fix ID: fsm_appliance_update_1.3.2
Publication Date: Aug 25, 2014
PREREQUISITES AND CO-REQUISITES
The minimum release of IBM Flex System Manager that this
package can be installed on is '1.3.0'.
The Flex Update Best Practice guide should be read prior to updating the
FSM. All the updates for the Flex System Chassis have been tested and releas
ed
together and the Chassis components must be updated as a unit.
"http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5091991"
Attention: Prior to updating IBM Flex System Manager, it is recommended to st
op
IBM Network Advisor SMIA Configuration Tool and reboot your FSM. For more
information, refer to the IBM Flex Update Best Practice guide.

FIRMWARE FOR FLEX SYSTEM MANAGER INCLUDED IN THIS PACKAGE:

Description
===========

Fix ID
=========================

Preboot Dynamic System Analysis (DSA)

32-64

ibm_fw_dsa_dsyte0r-9.60_anyos_

Integrated Management Module II (IMM2) Firmware ibm_fw_imm2_1aoo58r-4.20_anyos

_noarch
uEFI Firmware Update
_32-64
IBM UpdateXpress System Pack Installer (UXSPI)

ibm_fw_uefi_bde142a-1.50_anyos
ibm_utl_uxspi_9.60_rhel6_32-64

Emulex Firmware
1.36-1_linux_32-64

elx_fw_cna_ibm14a-oc11-10.2.26

IBM Online SAS/SATA Hard Disk Drive Update

_32-64

ibm_fw_hdd_sas-1.14.03-2_linux

LSI 2004 SAS Controller BIOS and Firmware Update ibm_fw_mpt2sas_x240-1.18.01_li

nux_32-64
Broadcom Firmware Update
1_32-64

brcm_fw_nic_2.2.1z1-fsm_rhev-h

ADDITIONAL SOFTWARE INCLUDED IN THIS PACKAGE:

Description
===========

Fix ID
=========================

IBM Flex System Manager 1.3.2

fsm_appliance_update_1.3.2

INSTALLATION INFORMATION
INSTALLING THE IBM FLEX SYSTEM MANAGER UPDATE
Note: A Flex System Manager update installation requires that the
Flex System Manager be shutdown and restarted afterwards.
Installation instructions are provided below, but additional detail can be
found in the IBM Flex System Manager Information Center. A link to the
Information Center is provided on the "Home" tab of the Flex System Manager
user interface in the upper right-hand corner of the panel.
The Information Center is also available on the Web at this address:
http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp
There are two methods for loading a fix pack on the Flex System Manager.
Choose one of these two options to acquire the fix pack.
I. Use the "Flex System Manager - Check and Update" function on the
FSM user interface.
II. Download the fix pack files from Fix Central to a workstation or
server and then move the files to the Flex System Manager. This option
is required if your FSM does not have access to the Internet.
================================================================
I. Flex System Manager - Check and Update function
Note: This option requires that the Flex System Manager is on a
network that that is connected to the Internet.
1) Select the "Flex System Manager - Check and Update" link on the
"Initial Setup" tab.
The Flex System Manager will connect to IBM's Fix Central site
and look for the latest fix pack update version.
The version of the latest available fix pack is displayed, if
an FSM update package is found with a higher version than what
is currently installed.
2) Click the "Download and Install" button to initiate the download
and installation of the fix package.
3) A dialog will be shown that asks if you want to display the job
properties of the update task while it runs. If you select
"Display Properties", you can track the status of the job as the
operation progresses. The "Log" tab will show the "Update Log"
messages and detailed status of activities as the update is processed.
4) If the update task completed with errors, do not continue.
Instead, contact IBM Support and do not restart the Flex System
Manager.

5) If the update task completed successfully, restart the Flex System

Manager to complete the installation.
You can use the link provided under the
"Flex System Manager - Check and Update"
link to restart the Flex System Manager.
Alternatively, you can use the command line interface to
restart the Flex System Manager with this command:
smshutdown -r -t now
(-r means to restart, '-t now' means to shutdown now.)
============================================================
II. Manually download the fix pack update files from PureSystems Centre
or IBM Fix Central to a workstation and copy the update files to the FSM.
This method downloads a fix package that consists of multiple
zip files and this readme file.
1) Download FSM update zip file package
a) Pure Systems Centre web site
Retrieve the FSM update package from the PureSystems Centre web site:
- Point your browser to the following website:
http://www.ibm.com/software/brandcatalog/puresystems/centre/
-

Click the System updates tab.

Click the Flex System 1.3.2 tab.
Select 'Flex System Manager image' link
Select 'FSMApplianceUpdate-1-3-2' link

b) Fix-Central
Go to "http://www.ibm.com/eserver/support/fixes/"
You can navigate the Fix Central interface as follows or use
the link below to find Flex System Manager update packages.
To obtain the files from Fix Central using the 'Find Product'
tab search:
- Click 'Find product' tab
- Product Selector -> Enter '8731' or '7955'
- Operating system -> Select 'All'
- Click 'Continue'
- Select 'FSM' to jump to the FSM section of the page
- Select 'FSMApplianceUpdate-1-3-2' check box
- Click 'Continue'
- Follow prompts to enter IBM ID and related machine information
- If you agree with the terms and conditions on the
'View terms and conditions' panel, click 'I agree'
- Download files using Download Director, ftp, or http.

2) After obtaining the files, use one of the following methods to

copy the update files to the /home/USERID directory on the Flex
System Manager:
a) Use the scp command (Secure Copy) to send the update package
files from a workstation on the management or data network to the
Flex System Manager.
For example, from a remote workstation:
scp FSMApplianceUpdate-1-3-2-ImportFirst.zip USERID@<FSM_host_name>:/
home/USERID
scp FSMApplianceUpdate-1-3-2-ImportSecond.zip USERID@<FSM_host_name>:/
home/USERID
scp FSMApplianceUpdate-1-3-2-ImportThird.zip USERID@<FSM_host_name>:/
home/USERID
b) Copy the update files from a USB storage device that is formatted
for FAT32, ext2, or ext3 file systems.
Note: Format your USB storage device for the FAT32, ext2, or ext3
file system so that they can handle these large zip files.
i) Insert a USB storage device into the USB port on the front of the
management node.
ii) Access the management node using SSH and log in with the default
USERID and password.
iii)Use the lsmediadev command to list the storage media devices that
are available for use on the system and identify the USB storage
device. The resulting output will be similar to the following,
where vdi1 is the USB storage device:
device=/dev/cdrom,mount_point=/media/cdrom,type=1,description=CD/DVD
device=/dev/vdi1,mount_point=/media/vdi1,type=3,description=USB flash
memory device
iv) Type "mount /media/vdi1" and press Enter.
(Note: Replace vdi1 with the output from your command above.)
v) Use the command cp to copy the files. For example:
cp /media/vdi1/* /home/USERID
vi) Type "umount /media/vdi1" and press Enter to unmount the USB
storage device.
3) Import and install the updates
After the files are copied to the Flex System Manager in the
/home/USERID directory, you must use the command line (through an SSH
connection) to import and install the updates. You cannot use the
Flex System Manager user interface.
From a command line, run the following commands to collect inventory,
and import the updates:

smcli cleanupd -mFv -P "Platform='Director' OR Platform='DirectorAppli

ance'"
smcli collectinv -p "All Inventory" -i 10.3.0.1,10.3.0.2 -t OperatingS
ystem
smcli importupd -v /home/USERID/FSMApplianceUpdate-1-3-2-ImportFirst.z
ip
smcli importupd -v /home/USERID/FSMApplianceUpdate-1-3-2-ImportSecond.
zip
smcli importupd -v /home/USERID/FSMApplianceUpdate-1-3-2-ImportThird.z
ip
smcli installneeded -v -F -I
As the install task is running, messages are displayed in the console.
Wait for them to "Complete" successfully.
If the installation task completed with errors, do not continue.
Instead, contact IBM Support and do not restart the Flex System
Manager.
4) If the installation task completed successfully, restart the
Flex System Manager to complete the installation processing.
You can use the command line interface to restart:
smshutdown -r -t now
(-r means to restart, '-t now' means to shutdown now.)
Alternatively, you can use the link provided under the "Flex System
Manager - Check and Update" link to restart the Flex System Manager.
VERIFICATION AFTER FIX PACK INSTALLATION
Verify the update has installed properly and the version is changed. You can
use either the Web user interface or the command line interface:
A) From the Flex System Manager Web interface:
After the Flex System Manager has started, check to see that the new
version level is active.
1) Go to Home->Plugins tab
2) Select "IBM Flex System Manager"
3) Approximately half way down the page, the current version is displayed.
* For this update, the version will be 1.3.2.
B) From the Flex System Manager command line (through an SSH connection):
1) Sign in with any user ID that has administrator privileges
(default is USERID)
2) Run the command "lsconfig -V"
3) The output will be:
# lsconfig -V
"version= Version: 1
Release: 3
Service Pack: 2
You must also update the firmware for the Chassis Management Module

(CMM). The files for the CMM update are included in this package,
but it requires a separate installation process. Refer to the
section at the end of this document for instructions on how to
complete the installation of this required firmware.
Chassis Management Module (CMM) -----------s_noarch

ibm_fw_cmm_2pet12k-2.0.0h_anyo

For additional information on updating the CMM and the rest of the Flex Chas
sis components,
refer to the Flex Update Best Practice guide. The guide can be found at:
"http://www-947.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-509199
1"

==================================================================
INSTALLING THE CHASSIS MANAGEMENT MODULE (CMM) FIRMWARE UPDATE
The Chassis
included in
not applied
fix package

Management Module (CMM) firmware update files are

the Flex System Manager fix package, but they are
to the CMM automatically when the Flex System Manager
is installed. You must install the CMM firmware separately.

There are two options for loading a CMM firmware update on the
Flex System Manager. Choose one of these options to acquire
the CMM firmware.
I) Use the "CMMs - Check and Update Firmware" function if the
Flex System Manager is connected to the Internet.
Note: If you installed the updates for Flex System Manager already,
you do not need to check for CMM updates. Instead, click the link to
install the CMM firmware, which is available on the
"CMMs - Check and Update Firmware" page.
II) Manually import and install the zip file that you downloaded
along with the Flex System Manager fix pack update.
I. CMMs - Check and Update Firmware
Note: This option requires that the Flex System Manager is on
a network that that is connected to the Internet.
1) On the FSM Web interface, select the "Update chassis components"
link on the "Initial Setup" tab. Then select
"CMMs - Check and Update Firmware".
2) Select "Check for updates" and click "OK".
Note: If you installed the updates for Flex System Manager already,
you do not need to check for CMM updates. Instead, click the link to
install the CMM firmware, which is available on the
"CMMs Check and Update Firmware" page.

3) If a new CMM update is found, follow the dialog screens to

download and install the update.
II. Manually import and install the zip file.
1) Follow procedure described in II. section 2 "Download the fix pack
from IBM Fix Central to a workstation" to copy files to the FSM.
2) On the FSM Web interface select the "CMMs - Check and Update Firmware"
link on the "Initial Setup" tab.
3) Select "Import updates from file system" and enter the full
target directory path in the "Path:" field. Click "OK".
For example, if you previously copied the files to /home/USERID,
you should specify /home/USERID in the Path field.
4) Follow the directions in the wizard to install the update.
TROUBLESHOOTING:
I. During the installation process, you might see the following message
in the update log. It indicates that the Flex System Manager Update
Manager library (which is used to cache update files) is full. The
update files stay in this library until they are removed using the
"smcli cleanupd" command. This command will only delete update files
in the Update Manager library. It will not uninstall updates that
have been previously installed on the Flex System Manager.
Message "ATKUPD247E":
"An error occurred while writing to the file <file name> on system <system>,
there is not enough space in the target file system. Ensure the target file
system has sufficient space and then retry the operation.
The command to remove previously cached update files from the
Update Manager cache is:
"smcli cleanupd -mva"
II. During the installation process you may see the message below
in the update task log. It indicates that there was an error
while running fsm_appliance_update_preparation_1.3.2. For more
information on the error(s) you can do a cat /var/log/fsmprep.log
from an ssh console.
ATKUPD767W The installation of update "fsm_appliance_update_preparation_1.3.2"
was not successful for system "<management server name>".
DNZDVM122E An error occurred while installing "fsm_appliance_update_preparatio
n_1.3.2"
on system "<management server name>" : Failure to install rpm
fsm_appliance_update_preparation-1.3.2-0.x86_64.rpm,. Check the rpm file .Then
,
retry update operation.

Execute 'cat /var/log/fsmprep.log', to see more details on the error.

Examples of errors you may see include:
A) Cleaning up <number> KB in /tmp, After cleanup, <number> KB free in /tmp."
Cleanup failed.
Contact IBM Support for further assistance. Refer to http://www.ibm.com/suppor
t if
you need help determining how to contact IBM Support.
The /tmp file system contains additional files that must be deleted before the
update
package can be installed. If you are applying this update on FSM version 1.2.
0 or
later, you can shutdown and start the FSM to delete all files in /tmp. Otherw
ise you
will need to contact IBM support for assistance.
More information on cleaning up /tmp on older versions of FSM (before 1.2.0) i
s
available in Technote '662049691' at IBM's Support Portal at the following URL
:
"http://www.ibm.com/support/docview.wss?rs=0&uid=nas754388dacd47ad5ad86257b190
06fd33a"
B) Examples of messages that can occur if local resources on the Flex System M
anager
are not in the proper state to install the update package:
Error: *** The local Server Managed End-point (MEP) is in 'No access' state.
Establish access with Server MEP by using Resource Explorer and locating the loc
al
server MEP with IP address '10.3.0.1' in 'IP Address' column. Select the 'No acc
ess'
link in the 'Access' column. On the next screen enter the User ID and Password
of the
local Server MEP (IMM) and click 'Request Access'.
Error: *** The local Operating System Managed End-point (MEP) is in 'No access'
state.
Establish access with Operating System MEP by using Resource Explorer and locati
ng the
local Operating System MEP with IP address of FSM assigned during Setup Wizard i
n
'IP Address' column. Select the 'No access' link in the 'Access' column. On the
next
screen enter the User ID and Password if the Operating System set during the FSM
Setup
Wizard and click 'Request Access'.
Error: *** The local Server Managed End-point (MEP) is in 'Not trusted' state.
stablish
Trust with Server MEP by using Resource Explorer and locating the local server
EP with
IP address '10.3.0.1' in 'IP Address' column. Select the 'Not trusted' link in
he
'Access' column to open the 'View Certificates' panel. Select the certificate
nd click
'Accept' to accept the certificate and change the status to 'Trusted'.

E
M
t
a

Status: The local Server Managed End-point (MEP) is online. This is not an erro
r.
Status: LAN-over-USB is enabled. This is not an error.
Status: The local Server Managed End-point (MEP) is unlocked. This is not an er
ror.
FIX INFORMATION:
IT03491 FSM 1.3.2 UPGRADE FAILURE DUE TO NETWORK ADVISOR INSTALL FAILURE
IT00284 Flex System Manager (FSM) is affected by vulnerabilities in OpenSSL (CVE
-2014-0160 and CVE-2014-0076)
IT00252 Flex System Manager (FSM) security vulnerability found - security exposu
re CVE-2013-5211
IT00531 Flex System Manager (FSM) security vulnerability - CVE-2013-5780, CVE-20
13-5372, CVE-2013-5803, CVE-2013-5772
IT00936 IT00936 Flex System Manager (FSM) chnetcfg command fails when managemen
t software is shutdown
IT01336 FSM MANAGING 16 CHASSIS UNABLE TO ACCESS SOME CHASSIS VIA REMOTE CONTROL
IT01370 VIRTUAL IMAGE LOST AFTER UPGRADE FSM TO GA4.1
IT00594 BACKPORTING OF DEFECT FIXES FROM VMC 2.4.5.0 TO 2.4.4.0 FIXPACK
IC99928 IFIX FOR DPSM 770.2 20140217 - FSM 1.3.1.1
IT00873 IFIX FOR DPSM 770.2 20140401 - FSM 1.3.1
IC99855 IFIX FOR DPSM 1.3.1
IC91935 RMDATASOURCE should not remove a datasource with another IP
IC89907 IBM Systems Director Server manipulates MANPATH on Linux
IC92772 In PA 6.3.3 cimsub on kvm PA 64 bit works only post removing LSI indicat
ion filters
IC90613 During IBM Systems Director install on AIX, disagreeing with license agr
eement does not stop the install process
IC90625 Failed to install update "ibm_fw_imm2_1aoo40a-1.88_anyos_noarch"on syste
m. The UXSPi return code is "59" and error message is "?
IC90764 No such file or directory error messages at end of IBM Systems Director
6.3.2 DVD install
IC91060 Flex System Manager unable to detect Common Information Model(CIM) proto
col
IC91010 The script "reset_diragent_keys" does not create any log
IC92767 mofcompremove errors are seen in the uninstall log on WIN2008 R2 in PA 6

.3.3
IC94693 Cannot unlock storage array manageable endpoint for Flex v7000
IC95025 Install updates jobs may be delayed if long inventories are already runn
ing
IC91925 The HA farm is choosing the IP address that does not match the current d
b2
IC92416 Incorrect VMControl version is displayed while using REST API
IC93178 [Kestrel]Sensor Event Severity Not Match with IMM
IC92771 VIOS install updates task hangs when VIOS endpoint has ifix in locked st
ate 6.3.3
IC92456 IBM Systems Director Common Agent (CAS) stop event is not caught by Oper
ationalCondition Event Filter
IC92460 Insufficient error message running Systems management command- line inte
rface (smcli) backupcfg command without parameters
IC92585 Flex System FC5022 Switch SNMPV3 Auto-Trap Configuration failure
IC92588 Changing IMM password from User Management template deletes user
IC94080 Event severity not match with IMM when fan sensor assertion
IC92906 IBM System Director Common Agent calculates the size of data received in
correctly
IC93220 Unnecessary message "java.io.SyncFailedException: sync failed" is posted
when importing an image using VMControl
IC93268 On FSM, do not use the cfgldap command
IC93187 cfguserreg.sh -ldap -f gets ALR1257E or other error when com.ibm.lwi.ld
ap.ssl.enable=false
IC93812 Information of Ethernet port are different between each OS( IB)
IC94910 ISD Server local agents should not be updated to version higher than ser
ver version itself
IC95889 Upgrading IBM Systems Director server results in duplicate CIM subscript
ions
IC95737 IBM Systems Director shows duplicate events or historical events as new
IC94996 Uuinstall of PA on KVM fails but message says success
IC96188 Flex System manager SSH login and web console login may not work with th
e same username configured to use an external LDAP server
IC95644 The behavior of Ambient2 Temp is not right(IB)
IC96860 FSM user not notified of error message return code
IC96173 Inventory fails on HMC managed IBM i lpar with physical tagged adapters

with a slot number larger than 9

IC94657 SSM for ESXi fails check eligibility and call home for send test problem
IC95843 Local console and putty behavior diff when logon use a user name but in
wrong case
IC95964 Windows specific events might cause an out of memory error in IBM System
s Director
IC97433 Able to break out of restricted browser without logging in
IC98365 Inventory on VIOS failed
IC98449 Director server could not receive all power supply events that are gener
ated
IC96439 Platform Agent Watchdog service crashes because of some unhandled except
ion
IC96071 The "Slots Occupied" property name is misleading
IC97088 Java exception keeps IBM Systems Director server from starting
IC97301 After a successful firmware update, ESXi 5.0 System fails to restart
IC97364 Incorrect timestamp is displayed in Last Run field for a scheduled job i
nstance
IC97432 No Text' Event Text for mapped SNMP trap
IC98669 For FSP blades, recovery of a software sensor event clears the hardware
sensor events on the FSM chassis map.
IC97647 Osp-par-940xinp sysdirremoval.exe removes software objects other than IB
M Systems Director 6.3.x in add/remove programs
IC98305 Error 500: javax.faces.el.evaluationexception displayed on all active vi
ews during long running operations
IC98674 The create automation plan action on monitor task and threshold task rep
orts error
IC97975 Farm inventory failed with SQL exception in log
IC98158 Add thin provisioned storage pool support for storage control
IC98546 ibmpawatchdog process crashes when WMI query returns result with only CR
and LF
IC98452 CIM protocol cannot be unlocked with domain account
IC97364 Incorrect timestamp is displayed in Last Run field for a scheduled job i
nstance
IC98906 Director SSP subagent fails to install on VIOS 2.2.3.x
IC99019 Misleading error message causes confusion over how to clean up
IC99123 Importupd command creates two additional files that cannot be deleted

IC99002 FSM upgrade fails due to lack of disk space caused by /mirror0 being fil
led with DB2 logs
IC99092 FSM MIB files are unloaded during the discovery of a BNT ethernrt switch
I/O Module
IC99177 SLP Registration fails resulting in restart of Platform agent by watchdo
g service
IC98158 Add thin provisioned storage pool support for storage control
IC98388 Problem summary: bug in svs causes npiv capable storage
IC94384 Error code dnzlop004e capturing aix partition using vmcontrol
IC98079 VMC deploy of a remote restartable vs will fail on a system with ams mem
ory pools defined
IC98059 VMControl fails when adding a second vnic to a virtual server using rest
IC98846 Virtual server delete fails with SVSException: DNZVMP050E
IC98887 An HMC fail to respond to IBM System Director, when all SSH connections
resources are exhausted
IC97321 When deploying a virtual server to an IBM Power 5 system using IBM Syste
m Director VMControl the deploy fails with DNZVMP054