swverify output in depth

[Gino Casella]

Hello,
i launched swverify \* on my system and found a lot of errors.
In particular swverify failed on some patch and product.
i would like to know how to manage those erros: that products are working and people says that swverify is not very reliable.
Thus how to know which test failed on swverify? How to know the meaning of hose errors?

thanks

Gino

[Michael Tully]

Could you post an example of these errors?
What is your current patch level?

Regards
Michael
"When I have trouble spelling, it's called fat finger syndrome"

[Gino Casella]

here is an example

ERROR: Verify failed Ignite-UX.MGMT-TOOLS,l=/,r=B.3.6.82

[Sridhar Bhaskarla]

Hi Gino,

Swverify looks at each product and compares the current checksum and permissions of each file against that stored in the IPD. It prints errors if it finds any differences.

For ex., if you have 100BASE-T product installed, look at the file

/var/adm/sw/products/100BASE-T/100BT-RUN/INFO

It registered file
path /usr/newconfig/etc/rc.config.d/hpbtlanconf
type f
size 1270
cksum 2567160831
mode 0555
uid 2
gid 2
owner bin
group bin
mtime 1012844632

So if you go ahead and edit that file or change the attributes, it will print out errors as you are not supposed to modify this file. For files that are modifiable like /etc/rc.config.d/hpbtlanconf, the entry will be like this

file
path /etc/rc.config.d/hpbtlanconf
type f
is_volatile true


This is how swverify works. Detailed warnings are printed in swagent.log. You will need to decide if you have to fix them or not.

-Sri