There are several possible drawbacks caused by insufficient read permissions on device and config files.
So only root can usually execute the diskinfo command because the disks' char devs cannot be read by others.
The same is the case for files like /etc/lvmtab .
If you don't want to relinquish permissions on these files your script must be run as root.
On the other hand permitting root logins (even via SSH) isn't a good habit for several reasons.
Usually one would login under a low priviledged maintenance account and then su to root.
Anyway, you could stuff something like this (of course better formatted) in a script on the clients, and make it root owned with setting the suid bit (another of the big Don'ts).
/usr/sbin/vgdisplay -v vg00|awk '/PV Name/{print$NF}'|sed s/dsk/rdsk/|xargs -n1 diskinfo|awk '/desc|rev/{print$NF}'
(n.b. at least one sed and awk call can be avoided by an appropiate awk block if you use awk functions like sub(), match() etc.)
E.g. executed on one of our boxes produces this:
/dev/rdsk/c2t2d0:
HPC2
/dev/rdsk/c1t2d0:
HPC2
As for the pinging, that doesn't necessarily proof if the to be contacted remote host is up or down.
We for instance, have most of our servers behind firewalls that only allow SSH connections (from our central managing host where one would run the SSH for loop) but silently drop all ICMP echo requests.
If this is not an issue for you,
then you could do as already shown by the others with some construct like
for $h in hostA hostB hostC; do
ping $h -n 1 -m 5 >/dev/null 2>&1 || continue
# do ssh stuff here
done
Btw, I cannot beleive that the FW revision of your Root VG disks change that often to not have this information stored in some more tangible table or file.
Madness, thy name is system administration
