HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Primary and alternate link ids
Operating System - HP-UX
1834017
Members
2544
Online
110063
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
06-03-2002 06:22 AM
06-03-2002 06:22 AM
Hello,
When we have a pvlink situation, if the primary link id is lower than the alternate link id, will there be any issues involved?
Also, if the primary link fails and it switches to the alternate link, when the primary link is available again, does it switch back to the original primary link? Or the once alternate link becomes primary and the once primary link becomes alternate?
Vince
When we have a pvlink situation, if the primary link id is lower than the alternate link id, will there be any issues involved?
Also, if the primary link fails and it switches to the alternate link, when the primary link is available again, does it switch back to the original primary link? Or the once alternate link becomes primary and the once primary link becomes alternate?
Vince
Tape Drives RULE!!!
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2002 06:36 AM
06-03-2002 06:36 AM
Solution
Hi Vincent:
It matters not which device represents the primary link.
On 11.x, the value of 'autoswitch' determines whether or not pvlinks will switch from the alternate (when used) back to the primary (when it becomes available again).
You can set or reset this behavior with:
# pvchange -S y|n
See the man pages for 'pvchange' for more information.
Regards!
...JRF...
It matters not which device represents the primary link.
On 11.x, the value of 'autoswitch' determines whether or not pvlinks will switch from the alternate (when used) back to the primary (when it becomes available again).
You can set or reset this behavior with:
# pvchange -S y|n
See the man pages for 'pvchange' for more information.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-06-2002 01:12 PM
06-06-2002 01:12 PM
Re: Primary and alternate link ids
While Alt-Pri links do not matter to LVM, they can matter to your performance and throughput.
If you have a VG vg01 with 4 PV's (EMC numbering shown);
c1t1d0,c1t1d2,c1t1d3,c1t1d4
and 4 Alt links;
c2t1d0,c2t1d1,c2t1d2,c2t1d3
If all the c1 PV's are the primaries then all your disk I/O traffic will flow through only one controller (c1). You can spread out controller I/O by setting half of the PV's to be primary on the other controller.
Short term solution is to use;
pvchange -s /dev/dsk/c2t1d1
pvchange -s /dev/dsk/c2t1d3
The small "s" will move I/O to the c2 controller until;
1. Controller 2 fails, and I/O is redirected to Controller 1
2. Next reboot
To keep I/O on the c2 controller after a reboot you need to take additional steps.
At boot Pri/Alt paths are determined by the order that they are found in /etc/lvmtab.
In order to change the order they are in you need to remove them and add them back in.
In this example above, once you have moved Primary I/O to the secondary controller for d1 & d3 you can safly remove and add the "c1" PV's like;
vgreduce /dev/v01 /dev/dsk/c1t1d1
vgextend /dev/vg01 /dev/dsk/c1t1d1
vgreduce /dev/vg01 /dev/dsk/c1t1d3
vgextend /dev/vg01 /dev/dsk/c1t1d3
Now if you do a strings on /etc/lvmtab you will see that c2t1d1 comes before c1t1d1 so at reboot c2t1d1 will be primary.
If you have a VG vg01 with 4 PV's (EMC numbering shown);
c1t1d0,c1t1d2,c1t1d3,c1t1d4
and 4 Alt links;
c2t1d0,c2t1d1,c2t1d2,c2t1d3
If all the c1 PV's are the primaries then all your disk I/O traffic will flow through only one controller (c1). You can spread out controller I/O by setting half of the PV's to be primary on the other controller.
Short term solution is to use;
pvchange -s /dev/dsk/c2t1d1
pvchange -s /dev/dsk/c2t1d3
The small "s" will move I/O to the c2 controller until;
1. Controller 2 fails, and I/O is redirected to Controller 1
2. Next reboot
To keep I/O on the c2 controller after a reboot you need to take additional steps.
At boot Pri/Alt paths are determined by the order that they are found in /etc/lvmtab.
In order to change the order they are in you need to remove them and add them back in.
In this example above, once you have moved Primary I/O to the secondary controller for d1 & d3 you can safly remove and add the "c1" PV's like;
vgreduce /dev/v01 /dev/dsk/c1t1d1
vgextend /dev/vg01 /dev/dsk/c1t1d1
vgreduce /dev/vg01 /dev/dsk/c1t1d3
vgextend /dev/vg01 /dev/dsk/c1t1d3
Now if you do a strings on /etc/lvmtab you will see that c2t1d1 comes before c1t1d1 so at reboot c2t1d1 will be primary.
If it ain't broke, let me have a look at it.
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