Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Help with hardware documentation
- Thread starter jcp001
- Start date
You are going to want to start with an ioscan, but you probably will also need to know the layout of the disks, which changes more than the hardware that an ioscan will show you. You will need to do a pvdisplay, vgdisplay, and lvdisplay and then connect all the information together (which lvs and filesystems belong to which vgs, which disks belong to which vgs, etc.), including the info you get from an ioscan.
Check the man page for ioscan for an explanation of what the output of an ioscan means.
If you have a lot of hardware on your system, it may take a while, but it will be worth it in the long run. I do this on all my systems and create very simple PowerPoint drawings of the systems. Info I include are hardware addresses, volume groups disks belong to, sometimes even down to filesystems on the disks. It helps to have these drawings when something goes wrong.
There are some scripts out on the internet that may help gather the information for you. Check stokely.com for some. You might also try the Unix scripting forum on Tek-tips. If you get a good script, I recommend running it periodically and storing the text output (along with other system information) on the system itself and another system.
And, if you find a good script, post it here if you can.
Good luck.
Check the man page for ioscan for an explanation of what the output of an ioscan means.
If you have a lot of hardware on your system, it may take a while, but it will be worth it in the long run. I do this on all my systems and create very simple PowerPoint drawings of the systems. Info I include are hardware addresses, volume groups disks belong to, sometimes even down to filesystems on the disks. It helps to have these drawings when something goes wrong.
There are some scripts out on the internet that may help gather the information for you. Check stokely.com for some. You might also try the Unix scripting forum on Tek-tips. If you get a good script, I recommend running it periodically and storing the text output (along with other system information) on the system itself and another system.
And, if you find a good script, post it here if you can.
Good luck.
- Status
Similar threads
- Locked
- Question
- Locked
- Question