HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- package querry
Operating System - HP-UX
1837932
Members
2803
Online
110124
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
08-29-2002 07:42 AM
08-29-2002 07:42 AM
package querry
Continuing on my previous querry.
Env : Two node Cluster.one Package runs on each box.
Package-Ip is on main subnet. Standby LAN is also on main subnet. Say subnet 2.
I configured a additional lan port(lan 2) on each node and connected them on a separate VLAN ( say 100.100)
Now cluster or package does not have any configuration about this new subnet or IP address. But in the /etc/hosts and on DNS I've redirected Package-name to this new private VLAN, package-IP have new IP-address only in hosts file but not in cluster configuration files.
Cluster and package are running fine with this new setup I also tried to run both package on one box without any problem. Lan3 is standby lan. lan0 is/was primary lan
*If suppose My VLAN fails, does service guard failover to laon0 or lan3 ??
*Does it fails over or not?
* Is this OK if I run my cluster with current setup. ( not making any changes in cluster configureation files but change ip address for package in hosts file)
Any answer would be a great help
Thx.
Env : Two node Cluster.one Package runs on each box.
Package-Ip is on main subnet. Standby LAN is also on main subnet. Say subnet 2.
I configured a additional lan port(lan 2) on each node and connected them on a separate VLAN ( say 100.100)
Now cluster or package does not have any configuration about this new subnet or IP address. But in the /etc/hosts and on DNS I've redirected Package-name to this new private VLAN, package-IP have new IP-address only in hosts file but not in cluster configuration files.
Cluster and package are running fine with this new setup I also tried to run both package on one box without any problem. Lan3 is standby lan. lan0 is/was primary lan
*If suppose My VLAN fails, does service guard failover to laon0 or lan3 ??
*Does it fails over or not?
* Is this OK if I run my cluster with current setup. ( not making any changes in cluster configureation files but change ip address for package in hosts file)
Any answer would be a great help
Thx.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2002 12:17 PM
08-29-2002 12:17 PM
Re: package querry
Hello Rushank,
ServiceGuard will NOT perform the standby LAN failure function for a lan that is not configured in the cluster binary file. This means that SG won't see lan2 failures until lan2 is configured in the cluster.
Once lan2 is added to the cluster ASCII configuration file properly, and cmapplyconf performed, lan3 can perform the standby LAN failure function for both lan0 and lan2 if they are of the same lan type and on the same physical network.
-s.
ServiceGuard will NOT perform the standby LAN failure function for a lan that is not configured in the cluster binary file. This means that SG won't see lan2 failures until lan2 is configured in the cluster.
Once lan2 is added to the cluster ASCII configuration file properly, and cmapplyconf performed, lan3 can perform the standby LAN failure function for both lan0 and lan2 if they are of the same lan type and on the same physical network.
-s.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2002 12:31 PM
08-29-2002 12:31 PM
Re: package querry
Thanks,
I tried physically disconnecting cable (private 100..) package was up and running on respective boxes.
then I disconnected the cable from lan 0 still every thing was OK!
I halted a node package failed over to next node.
And cluster configuration files still does not have any information about 100.100.100.0 network. only /etc/hosts file have this information
Only thing I could not findout is what network service guard use for package information.
I tried physically disconnecting cable (private 100..) package was up and running on respective boxes.
then I disconnected the cable from lan 0 still every thing was OK!
I halted a node package failed over to next node.
And cluster configuration files still does not have any information about 100.100.100.0 network. only /etc/hosts file have this information
Only thing I could not findout is what network service guard use for package information.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP