GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problem with lanqueryconf to extract Failover Grou...
Operating System - HP-UX
1844097
Members
2036
Online
110227
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
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
10-24-2008 12:47 AM
10-24-2008 12:47 AM
Hi.
I have a working Failover Group named lan900. When that FG was created, the sysadmin followed all the steps in the APA Manual and all was OK except that now I'm unable to use "lanqueryconf" to extract the current config in ascii format.
The error I get is:
# lanqueryconf -s -c lanconfig.txt
WARNING: Port 1 is probably a part of a Fail-Over Group
WARNING: Port 3 is probably a part of a Fail-Over Group
No Fail-Over Groups found. ASCII file not created
But I found no errors when I applyed my "custom" lanconfig.ascii file:
# (Extract of lanconfig.ascii):
FAILOVER_GROUP lan900
STATIONARY_IP XX.XX.XX.XX
PRIMARY lan1 5
STANDBY lan5 3
# lanapplyconf -v -c /etc/lanmon/lanconfig.ascii
Reading ASCII file /etc/lanmon/lanconfig.ascii
Verifying ASCII file /etc/lanmon/lanconfig.ascii
Configuring Fail-Over Group(s)
Creating Fail-Over Group lan900
Updated binary file /etc/lanmon/lanconfig
# lanscan | grep LinkAgg0
LinkAgg0 0x0012239ACAA1 900 UP lan900 snap900 12 ETHER Yes 119
# lanscan -q
0
6
8
2
4
900 1 5
901
902
903
904
# lanadmin -x -v 900
Link Aggregate PPA # : 900
Number of Ports : 2
Ports PPA : 1 5
Link Aggregation State : LINKAGG MANUAL
Load Balance Mode : Hot Standby (LB_HOT_STANDBY)
# lanadmin -x -i 900
Link Aggregate PPA # : 900
Link Aggregation Mode : LAN_MONITOR
Load Balance Mode : Hot Standby (LB_HOT_STANDBY)
Active Port PPA # : 1
Port(s) ready : 5
Port(s) not ready : NONE
Port(s) connected to active port : 5
The Failover group is working as expected and the configuration keeps working after reboots. I tried also to remove the /etc/lanmon/lanconfig binary and /sbin/init.d/hplm recreated it correctly at boot time.
But I'm unable to save the current configuration in a text file. That's not a great problem, because I keep a copy of the file I used with lanapplyconf and I can modify it directly, but I would like to know why lanqueryconf gives that error.
Any idea? Maybe lanqueryconf must be called BEFORE hplm is started so that it can find "available" apa ports? :?
Thanks.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2008 06:03 AM
10-27-2008 06:03 AM
Solution
You are right. Lanqueryconf does not read the binary file and send it to the output file. Instead, it inspects the system's lan interfaces in their current state and creates an ascii file based on what it finds.
The odd thing is that it reports the "already part of a failover group" message for port 3 instead of port 5.
The odd thing is that it reports the "already part of a failover group" message for port 3 instead of port 5.
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