AIX Firmware Capture

Content Authoring
1

(imported topic written by ajandi91)

First I’d like to say this forum rocks, a lot of great people and advice. I have a question and hope this is correct place to post it. THANKS FOR ALL YOUR TIME IN ADVANCE.

I have a task running to capture the AIX system firmware versions from our 400+ LPARS (210 Frames) which ran fine and produced results that I can have my management, SA’s etc… run reports on to determine how we’re progressing on our infrastructure wide initiative to get all frames upgraded to SF240_403.

The ISSUE: The capture is no longer working, we have upgraded over 75 frames and confirmed this at the CLI/Via the HMC. The data in BF is not changing and we have changed the scheduling to run the task 1 a day from bi weekly and before that weekly.

What the task is running is a simple shell out running the lsmcode command:

not sure if the task action is wrong or the analyses parsing data into BF is issue or neither. Need help as I’m new to BF.

Sorry forgot to mention we’re on 8.1

  1. THIS IS THE ORGINAL ACTION THAT WORKED TO PRODUCE DATA ###########

(version of client >= “6.0.0.0”) AND (exists true whose (if true then (exists (operating system) whose (it as string as lowercase contains “aix” as lowercase)) else false))

Action:

delete __appendfile

delete /tmp/task_lsmcode.sh

appendfile #!/bin/sh

appendfile lsmcode > {pathname of parent folder of client}/task_lsmcode.log

move __appendfile /tmp/task_lsmcode.sh

wait /bin/sh -C /tmp/task_lsmcode.sh

  1. THEN WE ADDED THIS TO IT ############

we added: delete /tmp/task_lsmcode.log

our thinking was the log file was being appened to and new data via lsmcode was not being parsed. so to create a new file each time.

  1. THIS IS THE NEW COMMAND WE’RE THINKING OF USING ##########

delete __appendfile

delete /tmp/task_lsmcode.sh

appendfile #!/bin/sh

appendfile lsmcode > {pathname of parent folder of client}/task_lsmcode.log

move __appendfile /tmp/task_lsmcode.sh

run chmod 755 /tmp/task_lsmcode.sh

wait /bin/sh -C /tmp/task_lsmcode.sh

Thanks

Andre

2

(imported comment written by SystemAdmin)

ajandi,

That should work fine, but I have also used createfile.

createfile until __EOF

#!/bin/sh

lsmcode >/tmp/task_lsmcode.log

__EOF

move __createfile /tmp/task_lsmcode.sh

wait sh -c “chmod +x /tmp/task_lsmcode.sh”

wait sh -c “/tmp/task_lsmcode.sh”

Remember to place " " around any commands you run with wait sh -c “your script”

Jeff

3

(imported comment written by ajandi91)

Awesome Jeff, thanks so much for the advice. I think I will do a test run with your script as well, i will keep you posted on the results.

4

(imported comment written by SystemAdmin)

Are you just using TEM for reporting purposes? I don’t know of any way TEM can perform firmware updates on your pSeries frames via your HMC???

5

(imported comment written by ajandi91)

yes this is for reporting and validation purposes, to confirm across the infrastructure where we stand.

6

(imported comment written by ajandi91)

All/Jeff,

For whatever reason the firmware levels are not updating in BigFix, I have checked the action and the task is running succesfully.

What else can I be missing or whatelse in big fix should I look at? I believe the action script is sound with the verification from you guys it should work and has worked in the past.

Thanks for your input