- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- reboot vs. uname -S / hostname <hostname> and more
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО02-22-2005 09:15 PM
тАО02-22-2005 09:15 PM
reboot vs. uname -S / hostname <hostname> and more
I'm having an issue here that I'll try to explain briefly.
We have 2 nodes, 1 is production, 1 is test.
The systems are exactly similar (HW and SW).
OS is exactly similar (patches etc)
the customer didn't want to use serviceguard but wants a disaster recovery option. So they thought of the following:
use scripts to gather specific system info, user info (home dirs) etc. and ftp these every evening to the test system. Build scripts to install these files and attach the PROD storage to the test system.
When disaster strikes, prod is down, test will be altered to function as the prod system. hostname and ip address will be changed so that it looks like the prod system is up and running.
OK, you see what I'm facing here? Terrible solution but I'm stuck with it..
This all is working already (in test phase) but what i would like to know is.
Should I expect any problems when I don't reboot the test system and let it boot with a new hostname/ip-adres but use # uname -S
Any idea's if this will create a problem?
Thanks in advance
Emiel
- Tags:
- uname
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 09:24 PM
тАО02-22-2005 09:24 PM
Re: reboot vs. uname -S / hostname <hostname> and more
You can't change the hostname just
by typing #hostname. The #uname -s hostname
will always give you the HPUX the ver of OS you are running.
If your system i,e production and
test servers are working fine as the fault
redundance without any problem using your
customised script, you can check the same
at the test phase by removing network connection to the production server.
In this case your test server should get
alert to get activate with the new ip and
hostname. If this is not working everything
you have struggled or enjoyed to prepare
script will be waste and it will not be the
redundance server.
Thanks and regards
Techtricks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 09:46 PM
тАО02-22-2005 09:46 PM
Re: reboot vs. uname -S / hostname <hostname> and more
Actually, I tested with a system and after i changed the hostname and the uname the system replied in every case the new given name..
Sure that the unique ID will not be the same but I don't think this will be a problem.
What i'm wondering about mostly if something will stay in memory that refers to the old nodename and will give me a problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 09:50 PM
тАО02-22-2005 09:50 PM
Re: reboot vs. uname -S / hostname <hostname> and more
If disaster striks on your PROD storage, you'll be left with two nice servers but without operational data.
Well, on the other hand this solution gives an extra benefit to the test server.
regards,
Thierry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 09:52 PM
тАО02-22-2005 09:52 PM
Re: reboot vs. uname -S / hostname <hostname> and more
Check for the /etc/rc.config.d/netconf file
after changing the HOSTNAME, check for the
HOSTNAME entry.
If it is reflecting the hostname in the conf
file, there is no such things to keep it in the memory for the hostname change.
Regards
Techtricks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 10:02 PM
тАО02-22-2005 10:02 PM
Re: reboot vs. uname -S / hostname <hostname> and more
This is all on EMC symmetrics devided over 2 sites.
the 2 systems are about 10KM apart and on the site where the test system is, prod storage is available with a srdf mirror (read only)
When disaster strikes, the mirror will be altered so that the test site storage will become leading. I'm not that worried about the storage actually..
netconf is not altered with uname or hostname, this is a manual action that we will perform when the hostname will be changed.
Please understand that if it was my decision we would not use such a procedure that is waiting for something to go wrong but would use serviceguard.. but.. it's not my decision
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 10:23 PM
тАО02-22-2005 10:23 PM
Re: reboot vs. uname -S / hostname <hostname> and more
The nodename is generally not so important. Users (applications) generally connect via the IP address.
If the application does not check on the nodename, I would only change the IP address.
regards,
Thierry.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 10:30 PM
тАО02-22-2005 10:30 PM
Re: reboot vs. uname -S / hostname <hostname> and more
we were just wondering if a reboot is needed or not to 'clean the system'.
If not, it will save us some time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 10:34 PM
тАО02-22-2005 10:34 PM
Re: reboot vs. uname -S / hostname <hostname> and more
a) you forked out for a Symmetrix, dust off your wallet!
b) compare the cost of Serviceguard to the cost of man-hours & downtime that this so-called "solution" will involve when (not if!) you have a disaster.
Stepping down from my soapbox, I'll now say that although changing the hostname & IP address of a system can certainly be done, there is often some niggly little thing that is overlooked and bites you in the bum. So I suggest one of the following 2 alternatives, in order of preference:
1) keep your hostname & primary IP address for each server , but have a spare LAN card, and a name & IP address for the service that you're running. In case of disaster, configure the spare lan card with the address of the service, mount the EMC disks and away you go. This is basically what serviceguard does, without the bells & whistles.
2) In the event of disaster, take an Ignite tape from your production server and boot your test server from it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-22-2005 10:43 PM
тАО02-22-2005 10:43 PM
Re: reboot vs. uname -S / hostname <hostname> and more
Yeah, you're completely right that they're to cheap but there's nothing I can do about it more..
In the end it will cost more and it's much less fault tolerance.
we need the hostname for the ftp users who connect on hostname.
Ignite is an option but because of the HW it takes a long time to finish..
My biggest problem is that I was never consulted, it was simply put on my desk with the notification: "make it happen".
Yep, they want it all. But enough about politics :)
Are there any problems that cannot be overcome without a reboot?
Now I can still claim that a reboot is needed, if later after i claimed otherwise it shows that i was incorrect I'll have a problem.
In such situations it's important to make sure you can't be the one to blame... sad but true