- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Bourne Shell Script to print Critical System ...
Operating System - HP-UX
1753565
Members
6245
Online
108796
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2001 01:44 PM
тАО05-18-2001 01:44 PM
Hi All,
After my disk crash with no backup (good
thing it was development and the EMC test
data was recovered due to some old papers I luckily hadn't throw away...that had the lvmtab info, ioscan info and directory/vol group and logical volume names... I was able from that to recover the EMC data.
My goal now is to install a script that runs
weekly on cron that sents all this info to
an output file. I manager over 13 HP-UX 11.0
so my memory is not good here.
I want the following commands output (and
I wasn't sure how to output SAM) from
a script:
1. bdf
2. cat /etc/lvmtab
3. cat /etc/fstab
4. ioscan
5. a listing of all volume groups with
their logical volumes and physical disk
and mount points...
6. Any SWAP/ Boot Disk Info/ Disk Mirroring
7. Kernel Configurable Parameters
8. Any important SAM stuff, I missed here ???
9. A listing of all the software I need to
reinstall (swlist -l bundle output)
=============================
I am assuming I'm not the only person out their
with this desire for a script...I want a nice
audit trail..a paper trail in case I have to
re-build from scratch (like I did today and
some of that was quess work without all the
paper).
Are there any folks out there that have a script similiar to this?
Have A Great Weekend...
Laurie
After my disk crash with no backup (good
thing it was development and the EMC test
data was recovered due to some old papers I luckily hadn't throw away...that had the lvmtab info, ioscan info and directory/vol group and logical volume names... I was able from that to recover the EMC data.
My goal now is to install a script that runs
weekly on cron that sents all this info to
an output file. I manager over 13 HP-UX 11.0
so my memory is not good here.
I want the following commands output (and
I wasn't sure how to output SAM) from
a script:
1. bdf
2. cat /etc/lvmtab
3. cat /etc/fstab
4. ioscan
5. a listing of all volume groups with
their logical volumes and physical disk
and mount points...
6. Any SWAP/ Boot Disk Info/ Disk Mirroring
7. Kernel Configurable Parameters
8. Any important SAM stuff, I missed here ???
9. A listing of all the software I need to
reinstall (swlist -l bundle output)
=============================
I am assuming I'm not the only person out their
with this desire for a script...I want a nice
audit trail..a paper trail in case I have to
re-build from scratch (like I did today and
some of that was quess work without all the
paper).
Are there any folks out there that have a script similiar to this?
Have A Great Weekend...
Laurie
Happiness is a choice
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2001 02:05 PM
тАО05-18-2001 02:05 PM
Solution
Laurie,
there are a number of scripts that gather system information for documentation purposes. The print_manifest command (part of Ignite) does a nice job. If you want something more customizeable, there are a few out there. I personally took one from Ralph Roth and modified it to the specific needs of my environment. You might want to track down his version, since he has likely made improvements since I, um, appropriated it.
My modified version is:
there are a number of scripts that gather system information for documentation purposes. The print_manifest command (part of Ignite) does a nice job. If you want something more customizeable, there are a few out there. I personally took one from Ralph Roth and modified it to the specific needs of my environment. You might want to track down his version, since he has likely made improvements since I, um, appropriated it.
My modified version is:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2001 02:13 PM
тАО05-18-2001 02:13 PM
Re: Bourne Shell Script to print Critical System Info/ SAM Info
Hi Laurie,
There are several scripts that do a very good job. One is called 'nickel'. If you search for it, you will find it with no trouble. Another is LVMcollect (an unsupported HP utility) that
I've attached.
Clay
There are several scripts that do a very good job. One is called 'nickel'. If you search for it, you will find it with no trouble. Another is LVMcollect (an unsupported HP utility) that
I've attached.
Clay
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-18-2001 03:11 PM
тАО05-18-2001 03:11 PM
Re: Bourne Shell Script to print Critical System Info/ SAM Info
Hi Laurie:
I too have similar scripts as Alan & Clay have offered. You can certainly add anything else to them that helps you.
The most recent versions of Ignite automatically produce a 'manifest' document whenever you do a 'make_tape_recovery'. That is, there is no need to independently execute a 'print_manifest'. You will find the current manifest(after every 'make_tape_recovery') is:
/var/opt/ignite/recovery/latest/manifest
You can add ('cat') this file to the output of other collection scripts or use it as a standalone reference.
Another useful feature of the manifest is that it will include a file called:
/var/opt/ignite/local/manifest/manifest.seed.
You can create or modify this optional file. Put records into it that look like this:
DOM "March 17, 2001, 02:25:47 EST"
IGNITE_REVISION B.2.2.161
SERIAL "1234A56789"
The SERIAL in this case is the hardware serial number -- the first thing the response center asks for when you place a hardware support call.
This information will be included into each manifest file generated and add to its usefulness.
Regards!
...JRF...
I too have similar scripts as Alan & Clay have offered. You can certainly add anything else to them that helps you.
The most recent versions of Ignite automatically produce a 'manifest' document whenever you do a 'make_tape_recovery'. That is, there is no need to independently execute a 'print_manifest'. You will find the current manifest(after every 'make_tape_recovery') is:
/var/opt/ignite/recovery/latest/manifest
You can add ('cat') this file to the output of other collection scripts or use it as a standalone reference.
Another useful feature of the manifest is that it will include a file called:
/var/opt/ignite/local/manifest/manifest.seed.
You can create or modify this optional file. Put records into it that look like this:
DOM "March 17, 2001, 02:25:47 EST"
IGNITE_REVISION B.2.2.161
SERIAL "1234A56789"
The SERIAL in this case is the hardware serial number -- the first thing the response center asks for when you place a hardware support call.
This information will be included into each manifest file generated and add to its usefulness.
Regards!
...JRF...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP