- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Reg package IP
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
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
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
10-15-2011 07:08 PM
10-15-2011 07:08 PM
Hi ,
I had an package for which there was an 10.1.4.1 IP , i changed the IP package.cntl IP when the package was up and tried to halt the IP it gave me an error saying that it failed , i checked the logs and found that IP was different so i reverted and then again fired cmhaltpkg but it says that the package is already halted.
I checked it with bdf it was halted but now my concern is that the old IP is still pingable , i do not want it to be pingable as i have switched over to new IP ( 10.1.4.2 ).
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2011 03:24 AM
10-16-2011 03:24 AM
Solution"Package halt failed", or more accurately, "something caused an error in the package halt procedure". Serviceguard requires the package halt procedure to be error-free, or else it won't restart the package automatically. Serviceguard lacks the intelligence required to determine if a particular error is harmful to package failover or not, so it will assume that all errors are harmful, to be safe.
The cause of the error is obvious: since you changed the package IP in the control file while the package was running, the package halt procedure attempted to shutdown the new package IP (which was not active yet) instead of the old one (which was still active). A failure to shutdown the configured package IP is an error.
As a result, the old package IP was left active while the rest of the package was halted.
To clean up this mess, you need to manually shutdown the old package IP. It is configured as an IP alias (also known as a "secondary interface" in "man ifconfig"). By your other thread I see the package IP interface was designated as lan0:2, so run "ifconfig lan0:2 0.0.0.0" to shut it down. This should also automatically remove the route entry associated with it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2011 03:32 AM
10-16-2011 03:32 AM