FLRT & psearch to the rescue for AIX clients - Security, HIPERs and Siblings
Storage 060000D5Y9 Visits (2885)
The FLRT and psearch teams have released new versions and we think you are going to appreciate the features that have been added.
For the most part, the main FLRT function has not changed. The FLRT usage was updated with more information on how recommendations are maintained and where they come from and we have added more details on the EoSPS dates and interim fixes.
See new FLRT usage
The really interesting things added are in the ‘Other resources’ section in the right hand navigation section.
- AIX/VIOS Security Tables
These tables list all of the security issues that have come out in the last year by AIX TL/SP. They should help our clients keep informed about interim fixes that have come out since a service pack was released. We encourage you to use these tables when reviewing AIX and VIOS recommendations to be sure you have the latest information on what is available.
Links are provided to the security advisory to get full details, as well as information on when the fix was or will be introduced into an AIX or VIOS level.
These tables will be updated as new security issues are released. A new security advisory was released yesterday (7/16/13) and the tables will be updated ASAP.
- AIX HIPER (HIghly PERvasive) Tables
Similar to the security table, these tables also show all the HIPER APARs that have been reported in the last year by AIX TL/SP. There is also a link to the APARs.
- VIOS Service Life Information
This graphic is similar to what is displayed for AIX in Fix Central. It shows the new VIOS service strategy support of multiple levels and the life cycle of those levels.
If you’re not familiar with ‘psearch’ it’s the ‘Fix Search’ function you see in the drop down menu in Fix Central.
The psearch function was created to allow AIX customers to search on APARs, something that was not available in Fix Central. We have enhanced this function to now provide direct links to the Sibling documents (if available) and fileset documents (if available).
If you click on the ‘Fix pack information…’ link, you’ll see a list of all the levels where the issue was fixed, along with the associated APARs.
There does seem to be a problem with the ‘Fileset levels’ in production that did not show up on our test systems, and we are investigating.
But, we didn’t want to pull this new release because we believe the sibling information will be very helpful as you are working on maintenance plans.
Note that this information is not always available for an APAR, even if it has shipped in a TL/SP. Sometimes APAR require more than one PTF to fix an issue and in those cases, our code is not able to determine the SP/TL, but we are working on fixing this issue such that every APAR creates a sibling document.
Please let us know what you think about the new function in FLRT and psearch with the ‘Feedback’ button.
Follow us on Twitter @IBM_FLRT
Follow her on Twitter @juliel_craft.