- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- LAN Routing
- >
- Procurve 3500 backup route
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
Forums
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
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
06-08-2011 05:51 AM
06-08-2011 05:51 AM
Procurve 3500 backup route
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2011 06:59 AM
08-01-2011 06:59 AM
Re: Procurve 3500 backup route
Hi,
No problem about your english... probably my english level is worse :)
I'm take 2 years working with HP Procurve, essentially with 5406zl, and the problem that you raise in my work it was solved by the VRRP Protocol an doing a LACP trunk between both switches.
For example, this is my conf:
Switch (1) LEAD
vlan 176
name "Vlan Servers"
untagged A1-A7,A12-A13,A18-A22,A24,D6,D8,D14-D15,D19-D20,Trk9
ip address 10.128.176.8 255.255.255.0
tagged B16,Trk1-Trk5
exit
vlan 180
name "PCs"
untagged B1-B24,C1-C12,D1,D3-D5,D7,D12-D13,D17
ip address 10.128.180.8 255.255.252.0
tagged A18,D15,Trk1-Trk5
trunk C18-C19 Trk1 LACP
interface Trk1
unknown-vlans Block
exit
router vrrp
vlan 176
vrrp vrid 176
owner
virtual-ip-address 10.128.176.8 255.255.255.0
priority 255
enable
exit
exit
vlan 180
vrrp vrid 180
owner
virtual-ip-address 10.128.180.8 255.255.252.0
priority 255
enable
exit
exit
Switch (2) BACKUP
vlan 176
name "Vlan Servers"
untagged A1-A7,A11-A13,A18-A22,A24,C10,C14,D8,D14,D17,D19-D20,E2,E20
ip address 10.128.176.9 255.255.255.0
tagged C21-C24,D1-D4,Trk1
exit
vlan 180
name "PCs"
untagged B1-B24,C1-C3,C5-C8,C11-C13,C15,C17,D6-D7,D9-D13,E24
ip address 10.128.180.9 255.255.252.0
tagged A11,A20,C14,C21-C24,D1-D4,D14-D16,E20,Trk1
exit
trunk C18-C19 Trk1 LACP
router vrrp
vlan 176
vrrp vrid 176
backup
virtual-ip-address 10.128.176.8 255.255.255.0
enable
exit
exit
vlan 180
vrrp vrid 180
backup
virtual-ip-address 10.128.180.8 255.255.252.0
enable
exit
exit
I don't know if your model (Hp Procurve 3500) support this configuration (VRRP).
Anyway check this document about VRRP's Configuration on HP Procurve Switches
Above all... GOOD LUCK!!
Greets from Spain!