Hi to all ,

Have problem updating fsm 1.3.1.2 to 1.3.2



ATKUPD576W The updates were successfully imported or acquired, but the compliance check failed for one or more of the updates or managed servers. See the related

update compliance job log for details about the failures and fix the problems. After all problems are fixed, collect inventory again on the affected servers so that

compliance can run successfully.

from log that has errors

(192.168.4.23 is ip to my imm on flex manager node)


September 9, 2014 12:01:13 PM CEST-Level:75-MEID:0--MSG: DNZUPX143W The compliance results for managed system "192.168.4.23" are potentially incomplete because some

neccessary updates were potentially not included. To update the compliance results, collect inventory for the system again.



DNZUPX124E An unknown error occurred while checking compliance for managed system "192.168.4.23". Look for related messages in the error log, follow any recommended

courses of action, and retry the operation.
September 9, 2014 12:09:19 PM CEST-Level:50-MEID:0--MSG: ATKUPD524E Compliance failed for provider "IBM System x servers and chassis UXSPi relationship extension".

Search above for previous related errors, fix each error, and then retry the operation.




September 9, 2014 12:09:19 PM CEST-Level:50-MEID:0--MSG: ATKUPD512E An update compliance relationship request has failed. Update relationship processing will continue.

Search above for previous related errors, fix each error, and then retry the operation.
September 9, 2014 12:09:19 PM CEST-Level:200-MEID:0--MSG: Subtask activation status changed to "Complete with errors".
September 9, 2014 12:09:19 PM CEST-Level:1-MEID:0--MSG: Job activation status changed to "Complete with errors".
September 9, 2014 12:09:19 PM CEST-Level:50-MEID:0--MSG: ATKUPD553E Task "Update Compliance" has failed. Read the following details on the error: ATKUPD551E Compliance

relationship pre-processing failed. Read the following details on the error: ATKUPD524E Compliance failed for provider "IBM System x servers and chassis UXSPi

relationship extension". Search above for previous related errors, fix each error, and then retry the operation.


found this too on recources explorer for fsm operating system , maybe something have whit above errors

        accsess     trust state   port
    CAS  OK    Not applicable  9510
   CAS  OK   Not applicable  9510


and for os 10.3.0.1 on 4.23 dont have trust state, there is revoke access here but
saw root user on ssh Access Type whit blank password but didn't have guts to do it.

whats the problem here whit updates and how to have all on trust state???

Hello and welcome to MyPureSupport!

I have not yet seen this issue but try the following and let us know if that does it.

1) REMOVE the FSM from Compliance Checking
       a) Go to 'Update Manager'
       b) Then 'Change Compliance Policies
       c) Browse for the FSM and Select it (MAKE SURE YOU DO THIS FOR BOTH OS OBJECT AND SERVER OBJECT)
       d) Click 'Show Compliance Policies' and remove each policy (MARK DOWN WHAT THESE ARE)
2) Now SSH in the FSM and run 'smcli cleanupd -mva'
3) Once ALL updates are cleared go back to Update Manager and add back the compliance policies you removed in Step #1 back to both FSM OS object and FSM Server object.
4) Now Inventory the FSM

Lastly retry the update from the CLI

Following the steps outlined in the Readme (attached) for downloading, importing the updates, and upgrading them VIA the CLI.

Let us know if this helps!!

this is only policy on picture  I have and its for chassis. it was auto assigned.
didn't try to remove it.  os and server have no policy. is it ok to remove chassis policy  and try

one more time error from log , tried lots of things today to fix this

MSG: ATKUPD553E Task "Update Compliance" has failed. Read the following details on the error: ATKUPD551E Compliance relationship pre-processing failed. Read the following details on the error: ATKUPD524E Compliance failed for provider "IBM System x servers and chassis UXSPi relationship extension". Search above for previous related errors, fix each error, and then retry the operation.

what would happened if I try to install manual update from Update Group - All appliance updates (View Members) pic upd3.png


   

Try to run through the steps I listed. I have had much more success upgrading the FSM from the CLI than the GUI.

You can also try to remove the chassis policy and then rerun the update using my steps. Just be sure to add all of your policies back so you can be sure you're making the most of compliance monitoring.

- removed policy from chassis
- did smcli cleanupd -mva
- did collect inventory from fsm for chassis and all members , interesting have runing whit errors

found this on log :
The CIMOM connection for managed resource "192.168.4.23" was not initialized. The reported inventory data might be incomplete. Verify the connection between the management server and the managed resource, and verify that CIMOM is running on the managed resource. Next, collect the inventory again.

on picture is my access for my flex manager node , have  no access to cim tryed to solved it whit no success

- did collect inventory from CLI didnt report errors
  -smcli collectinv -p "All Inventory" -i 10.3.0.1,10.3.0.2 -t OperatingSystem
  -smcli collectinv -p "All Inventory"
- wanted to update whitout returnig policy from CLI got the same problem as before
  - smcli importupd -v /home/USERID/FSMApplianceUpdate-1-3-2-ImportFirst.zip
 
 ATKUPD576W The updates were successfully imported or acquired, but the compliance check failed for one or more of the updates or managed servers. See the related update compliance job log for details about the failures and fix the problems. After all problems are fixed, collect inventory again on the affected servers so that compliance can run successfully.

What I have found interesting is that my imm firmware on flex is 4.21 and in FSMApplianceUpdate-1-3-2-ImportFirst.zip is 4.20
4.21 was updated from fix to 1.3.1 update to flex
have latest cmm firmware 2.00 2PET12O

seems update dont  pass because of   this CIM communication error whit flex node and access to it or 
will try to upgrade switches firmware too but cant stop communication to servers now.

anyone knows how to solve CIM problems or I have to wait for new firmware or other new updates  to flex . will see.

will return policy now and try collect inventory and update but think it has nothing to do whit error.

Is zevs sasija 1 the name of the FSM? I would highly recommend you remove the compliance policy from the FSM and try again. It sounds like there is an issue with compliance and the FSM.

zevs sasija 1 was my chassis , zevs.bmu.internal is my fsm and IBM 8731A1G 06ACTX8 70BA7736-05B0-4CC6-B7F1-EA2A204AFE13 is my fsm

still didnt manage to solve this, removed all policy-s, unmanaged chassis, left whit few resources on fsm.

if someone show up and knows what this error ATKUPD553E IBM System x servers and chassis UXSPi relationship extension is and how to fix or what is UXSPi relationship extension is pls write up.

every time i collect inventory I get this update compliance  errorr

Reboot the IMM of the FSM or reboot the CMM of the chassis that the FSM is in. See if this resets any communication.

For anybody else who finds this thread in the future....

I have had rotten luck upgrading things through the FSM GUI.  It works sometimes, and sometimes it doesn't.  In particular, I have catastrophically messed up one of my VIOs (Can't run CIM at all, so I can't do anything on that blade), and minorly  messed up two of my VIOs (Can't run inventory on the blades anymore.)

I have had two different IBMers tell me to NOT use the GUI but to do updates through the commandline, or through the web interface running directly on the hardware in question.  (For instance, go to the web interface on the V7000 and upgrade from there).

>>>>Ericw

Have you tried revoking access and then trying to gain access again?

If that does not work you could always try to remove the FSM object from the chassis and then inventory the chassis until the FSM appears. Then check your access again. It sounds like something is messed up in the FSM update database.

If all else fails a reboot of the FSM has cleared up alot of weird issues for me in the past and I have made it my first step when doing these upgrades.

pillow

have restarted imm on fsm, have shutdown fsm remove from chassis and put back in .
nothing works

weeda

what does storewize 7000 have to do whit it
how to remove v7000  storage connection  from fsm for good
it comes back automatic when i try for example to delete zevs.bmu.internal farm???

PureSystemsTech
I cant no option in menu to delete zevs.bmu.internal operating system    - my fsm
I cant no option in menu to delete 192.168.4.23  server  - my fsm imm
when I delete my zevs.bmu.internal farm  it auto comes back and brings v7000 resource that i deleted before
have revoked and deleted all access ,descover them back whit system discovey and restarts
nothing works

have updateed dsa , imm and uefi from imm on node.
now have question how to manual update rest of  fw on flex node from FSMApplianceUpdate-1-3-2-ImportFirst.zip

elx_fw_cna_ibm14a-oc11-10.2.261.36-1_linux_32-64
ibm_fw_hdd_sas-1.14.03-2_linux_32-64
ibm_fw_mpt2sas_x240-1.18.01_linux_32-64
brcm_fw_nic_2.2.1z1-fsm_rhev-h1_32-64

how to remove this zevs.bmu.internal farm that brings back v7000 form resources list for good

HOW TO RESET FLEX and do initial setup   will it destroy my liceance keys

have 1 more solution to try its to bring back old backup but think its fsm 1.2.x, and scared not to be able to update it to this level 1.3.1.2 if same problem accurs.

Well it makes sense that you can't remove the FSM from the FSM. 

At this point I can only suggest a manual recovery from the base media. Doing this would scrub your recovery partition to 1.3.2 so if you every recovered later you would already be at 1.3.2.

Check out this post http://mypuresupport.org/PureSystemsForum/index.php?topic=76.msg306#msg306

Make sure you have an externally powered USB DVD drive, that is crucial!

You should not lose any license keys and can add them back once the recovery is complete.

Let us know your thoughts!!

Blob,

I took a look at my FSM and checked its access and it shows the same exact CAS, CIM and SSH access as you do. Maybe its by design but I already am at version 1.3.2 with no issues on update. One thing I noticed is that you are getting errors for Compliance and I actually think its OK. But did you try to run the install command after you have imported the updates and got the compliance update error? Here are my steps when I have staged the the files on the FSM when I upgraded from 1.3.1 to 1.3.2. You can ignore the SMCLI IMPORTUPD command part, but the last command will begin the installation.

smcli cleanupd -amv
smcli cleanupd -mFv -P "Platform='Director' OR Platform='DirectorAppliance'"
smcli collectinv -p "All Inventory" -i 10.3.0.1,10.3.0.2 -t OperatingSystem
smcli importupd -v /home/userid/FSMApplianceUpdate-1-3-1-ImportFirst.zip
smcli importupd -v /home/userid/FSMApplianceUpdate-1-3-1-ImportSecond.zip
smcli importupd -v /home/userid/FSMApplianceUpdate-1-3-1-ImportThird.zip
smcli installneeded -v -F -I


Let us know what you think.

@pillow
did all those steps like 30 times, problem is I have 1.3.1.2 update whit all the fixes , would probobly had more luck upgrading from 1.3.1.
think problem acured because I have updated imm on flex throu one of the updates and something went wrong there I think. just look at my lsconfig -V.

USERID@zevs:~> lsconfig -V
"version= Version: 1
Release: 3
Service Pack: 1.2
FSM Build level 20140509-2227.Fri May  9 22:27:08 CDT 2014
","base_version=V1R3
"
fsmfix_com.ibm.itme.member_1.3.0.0201310121530:com.ibm.itme.member_1.3.0.0201310121530
fsmfix_com.ibm.itme.manager_1.3.0.0201310121530:com.ibm.itme.manager_1.3.0.0201310121530
fsmfix_ibm_fw_imm2_1aoo52y-3.78_anyos_noarch:ibm_fw_imm2_1aoo52y-3.78_anyos_noarch
fsmfix_ibm_fw_dsa_dsyte0u-9.60_anyos_32-64:ibm_fw_dsa_dsyte0u-9.60_anyos_32-64
fsmfix_ibm_utl_uxspi_9.50_rhel6_32-64:ibm_utl_uxspi_9.50_rhel6_32-64
fsmfix_ibm_fw_imm2_1aoo58u-4.21_anyos_noarch:ibm_fw_imm2_1aoo58u-4.21_anyos_noarch
fsmfix_com.ibm.director.storage.storagecontrol.member.Linux_4.2.5.0-build-00069-20140619-iFix:com.ibm.director.storage.storagecontrol.member.Linux_4.2.5.0-build-00069-20140619-iFix
fsmfix_com.ibm.director.storage.storagecontrol.mgr.Linux_4.2.5.0-build-00069-20140619-iFix:com.ibm.director.storage.storagecontrol.mgr.Linux_4.2.5.0-build-00069-20140619-iFix
fsmfix_fsm_native_update_1.3.1.0_csda_IT02336:fsm_native_update_1.3.1.0_csda_IT02336
fsmfix_fsm_native_update_1.3.1.0_pa_IT02336:fsm_native_update_1.3.1.0_pa_IT02336
fsmfix_fsm_native_update_1.3.1.0_IT00278:fsm_native_update_1.3.1.0_IT00278
fsmfix_ibm_fw_imm2_1aoo56g-3.79_anyos_noarch:ibm_fw_imm2_1aoo56g-3.79_anyos_noarch
fsmfix_com.ibm.director.storage.storagecontrol.mgr.Linux_4.2.5.0-build-00053-20140418-iFix:com.ibm.director.storage.storagecontrol.mgr.Linux_4.2.5.0-build-00053-20140418-iFix
fsmfix_com.ibm.director.storage.storagecontrol.member.Linux_4.2.5.0-build-00053-20140418-iFix:com.ibm.director.storage.storagecontrol.member.Linux_4.2.5.0-build-00053-20140418-iFix
fsmfix_com.ibm.director.mgr.automation.console.feature_6.3.4.0-20140110-IC98674:com.ibm.director.mgr.automation.console.feature_6.3.4.0-20140110-IC98674
fsmfix_com.ibm.vmcontrol.rf.vmware.feature_2.4.4.0-201405091905-it01647:com.ibm.vmcontrol.rf.vmware.feature_2.4.4.0-201405091905-it01647
fsmfix_com.ibm.dpsm.feature_1.0.0.7702201405045:com.ibm.dpsm.feature_1.0.0.7702201405045
fsmfix_com.ibm.director.core.console.ui.feature_6.3.4.0-20131213-IC98305:com.ibm.director.core.console.ui.feature_6.3.4.0-20131213-IC98305
fsmfix_com.ibm.director.storage.etpc.apijars_6.3.4.0-20140430-IT01370:com.ibm.director.storage.etpc.apijars_6.3.4.0-20140430-IT01370
fsmfix_com.ibm.director.core.kernel.feature_6.3.4.0-20140307-IC99904:com.ibm.director.core.kernel.feature_6.3.4.0-20140307-IC99904
fsmfix_com.ibm.vmcontrol.rf.power.feature_2.4.4.0-201405091905-it01647:com.ibm.vmcontrol.rf.power.feature_2.4.4.0-201405091905-it01647
fsmfix_com.ibm.itme.member_1.3.1.0201404081600:com.ibm.itme.member_1.3.1.0201404081600
fsmfix_com.ibm.itme.manager_1.3.1.0201404081600:com.ibm.itme.manager_1.3.1.0201404081600
fsmfix_com.ibm.director.mgr.status.server.feature_6.3.4.0-20140110-IC98669:com.ibm.director.mgr.status.server.feature_6.3.4.0-20140110-IC98669
fsmfix_fsm_native_update_1.3.1.0_IT00284:fsm_native_update_1.3.1.0_IT00284
fsmfix_fsm_native_update_1.3.1.0_PA_IT00284:fsm_native_update_1.3.1.0_PA_IT00284
fsmfix_DpsmNative_7.70.2.201405041521:DpsmNative_7.70.2.201405041521
fsmfix_fsm_native_update_1.3.1.0_IT00252:fsm_native_update_1.3.1.0_IT00252

@PureSystemsTech

downloaded recovery disk but don't have external dvd whit power only usb.
did smcli cleanupd -amv , and reconnected chassis will continue using 1.3.1.2 until  I find dvd or some new updates from ibm showup

will post here if manage to solve problem

All,

I recieved this from IBM after having a similar problem with my FSM upgrades. They look to be working now. Keep in mind you will need to open a ticket with IBM and gain ROOT access passwords

Technote:
============
Document Title:  Flex System Manager (FSM) 1.3.2 Upgrade Fails: ATKUPD524E - Compliance failed for UXSPi
Abstract    

Flex System Manager (FSM) upgrade from 1.3.1 to 1.3.2 fails with a compliance error related to the UXSPi update:
DNZUPX124E - An unknown error occurred while checking compliance for managed system "MS4-FSM". Look for related messages in the error log, follow any recommended courses of action, and retry the operation.
ATKUPD524E - Compliance failed for provider "IBM System x servers and chassis UXSPi relationship extension". Search above for previous related errors, fix each error, and then retry the operation.

Document Description:
 Description

Flex System Manager (FSM) upgrade from 1.3.1 to 1.3.2 fails.

Joblog shows a compliance failure:

September 10, 2014 9:00:20 AM MDT        DNZUPX140I Distribution of UXSPi "ibm_utl_uxspi_9.60_rhel6_32-64" to managed system "MS4-FSM" started.
September 10, 2014 9:00:23 AM MDT        DNZUPX133I UXSPi "ibm_utl_uxspi_9.60_rhel6_32-64" was successfully distributed to managed system "MS4-FSM".
September 10, 2014 9:00:25 AM MDT        DNZUPX121I Start compliance checking for managed system "MS4-FSM".
September 10, 2014 9:01:42 AM MDT        DNZUPX124E An unknown error occurred while checking compliance for managed system "MS4-FSM". Look for related messages in the error log, follow any                                                 recommended courses of action, and retry the operation.
September 10, 2014 9:01:50 AM MDT        ATKUPD524E Compliance failed for provider "IBM System x servers and chassis UXSPi relationship extension". Search above for previous related errors, fix                                                 each error, and then retry the operation.
September 10, 2014 9:01:50 AM MDT        ATKUPD512E An update compliance relationship request has failed. Update relationship processing will continue. Search above for previous related errors, fix                                                 each error, and then retry the operation.
September 10, 2014 9:01:51 AM MDT        MS4-FSM.WW005.SIEMENS.NET client job status changed to "Complete".


Error log will contain an error related to parsing the UXSPI xml file:

2014/09/10 09:04:06.425 INFO [Fatal Error] :127:3: XML document structures must start and end within the same entity.
 ::class.method=unknown ::thread=ManagedThreadPool-thread-10 ::loggername=SystemErr
2014/09/10 09:04:06.425 SEVERE parse UXSPI relationship result file failed ::class.method=com.ibm.director.updates.systemxandbc.relationship.uxspi.CompareResult.parseResultFromFile() ::thread=ManagedThreadPool-thread-10 ::loggername=com.ibm.director.updates.systemxandbc

        org.xml.sax.SAXParseException: XML document structures must start and end within the same entity.
        at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.CompareResult.parseResultFromFile(CompareResult.java:248)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.runComplianceBatch(UXSPiComplianceCallable.java:364)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.runCompliance(UXSPiComplianceCallable.java:296)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.complianceCheckOnEndpoint(UXSPiComplianceCallable.java:270)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.run(UXSPiComplianceCallable.java:203)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiCallable.call(UXSPiCallable.java:63)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiCallable.call(UXSPiCallable.java:44)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at com.ibm.sysmgmt.threadservices.ManagedExecutors$InstrumentedRunnable.run(ManagedExecutors.java:2403)
        at com.ibm.sysmgmt.utils.InnerManagedRunnable.run(InnerManagedRunnable.java:152)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:781)

or

Severity    : SEVERE
Class       : com.ibm.director.updates.systemxandbc.relationship.uxspi.CompareResult
Method      : parseResultFromFile()
Thread      : ManagedThreadPool-thread-29
Logger      : com.ibm.director.updates.systemxandbc

Message     : parse UXSPI relationship result file failed
Secondary   : org.xml.sax.SAXParseException: Premature end of file.
        at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
        at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
        at javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.CompareResult.parseResultFromFile(CompareResult.java:248)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.runComplianceBatch(UXSPiComplianceCallable.java:370)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.runCompliance(UXSPiComplianceCallable.java:302)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.complianceCheckOnEndpoint(UXSPiComplianceCallable.java:276)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiComplianceCallable.run(UXSPiComplianceCallable.java:209)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiCallable.call(UXSPiCallable.java:63)
        at com.ibm.director.updates.systemxandbc.relationship.uxspi.UXSPiCallable.call(UXSPiCallable.java:44)
        at java.util.concurrent.FutureTask.run(FutureTask.java:273)
        at com.ibm.sysmgmt.threadservices.ManagedExecutors$InstrumentedRunnable.run(ManagedExecutors.java:2403)
        at com.ibm.sysmgmt.utils.InnerManagedRunnable.run(InnerManagedRunnable.java:152)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:626)
        at java.lang.Thread.run(Thread.java:804)


Work-around
Free up any existing locks from previous update attempt with a full restart.
Notes:
1.          The first two steps clear any previous update which is hung.  Alternately, you could check for a running process in the rhevh partition and kill it:
2.           To get to the rhevh partition, you need to pesh to root first.

ssh 10.3.0.1         
ps aux | grep uxspi
You should look for something similar to the following:

 5738 32359   780   2208  0.0  0.0 /tmp/updatemanager/staging/systemxandbc/ibm_utl_uxspi_9.61_rhel6_32-64/ibm_utl_uxspi_9.61_rhel6_32-64.bin co -n -L -l updates --xml --ignore-req -m 8737
 5752  5738 68868 402512  100  0.2 ./uxspi961_cli.rhel6_64 co -n -L -l updates --xml --ignore-req -m 8737
If found, kill them or restart the system:
1.    Shut down the FSM.   
smshutdown -t now
2.    Start the FSM using the CMM.
Back up existing files
3.    Log into the cli of the FSM as pe and pesh to root.
4.    ssh 10.3.0.1
5.    ls -l /var/log/IBM_Support/* > /media/backuplist.list
6.    tar czvf /media/ibmsupport.tgz /var/log/IBM_Support/*
7.    Exit
8.    scp 10.3.0.1:/media/ibmsupport.tgz /home/pe/ibmsupport.tgz
9.    scp 10.3.0.1:/media/backuplist.list /home/pe/backuplist.list
Clean up disk space
10.     Remove the existing log files:       
11.    ssh 10.3.0.1       
12.      rm -rf /var/log/IBM_Support/*         
Caution:  Verify the path is correct!
13.    rm /media/ibmsupport.tgz     
14.    rm /media/backuplist.list
15.    ls /var/log/IBM_support

Confirm no files are left in /var/log/IBM_support
16.    Exit.
Repeat the upgrade
17.    Log out of the FSM and back in as USERID, and attempt the upgrade again.
18.    After the update completes successfully, remove the backup files.

rm /home/pe/ibmsupport.tgz
rm /home/pe/backuplist.list