- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: Distributed Trunking Configuration - KeepAlive
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
12-24-2013 04:37 AM - edited 12-24-2013 04:45 AM
12-24-2013 04:37 AM - edited 12-24-2013 04:45 AM
Distributed Trunking Configuration - KeepAlive
Hi all,
I'm trying to configure Distributed Trunking with 5400zl and although I've been reading Management and Configuration guide, some articles about it and all the messages related, I'm still having some doubts about it, especially with keepalive
If I understand this document (http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay?javax.portlet.begCacheTok=com.vignette.cachetoken&javax.portlet.endCacheTok=com.vignette.cachetoken&javax.portlet.prp_ba847bafb2a2d782fcbb0710b053ce01=wsrp-navigationalState%3DdocId%253Demr_na-c03361117-1%257CdocLocale%253D%257CcalledBy%253D&javax.portlet.tpst=ba847bafb2a2d782fcbb0710b053ce01&sp4ts.oid=1827663&ac.admitte... well, seems you have to use one VLAN exclusively for Peer-Keepalive (the vlan should not be configured in any othe ports, except the one used for keepalive). But the it suggest you have to configure an IP keepalive with a subnet froma a different VLAN. And that's my problem. Is that correct?
Or Can I, for example, use vlan 100 for keepalive, configure 192.168.100.1 and 192.168.100.2 as IP interfaces for vlan 100 and the use these IPs as destination in keepalive command?
distributed-trunking peer-keepalive destination 192.168.100.1/192.168.100.2
Thanks for your help! And have a nice Christmas!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2014 04:27 AM
02-18-2014 04:27 AM
Re: Distributed Trunking Configuration - KeepAlive
Here you have an example of DT-lacp config:
SWITCH-A:
trunk E4 trk99 lacp
trunk E1 trk100 dt-lacp
switch-interconnect trk99
vlan 4092
name "LACP-heartbeat"
untagged A20
ip address 192.168.92.5 255.255.255.252
exit
distributed-trunking peer-keepalive vlan 4092
distributed-trunking peer-keepalive destination 192.168.92.6
SWITCH-B:
trunk E4 trk99 lacp
trunk E1 trk100 dt-lacp
switch-interconnect trk99
vlan 4092
name "LACP-heartbeat"
untagged A20
ip address 192.168.92.6 255.255.255.252
exit
distributed-trunking peer-keepalive vlan 4092
distributed-trunking peer-keepalive destination 192.168.92.5
After that you connect a cable from SWITCH-A interface E4 to SWITCH-B interface E4. This is the switch interconnect, in a stacked scenario this would be the stacking cable.
You also connect SWITCH-A interface A20 to SWITCH-B interface A20. This is the heartbeat connection so that if the interconnect goes down the swithces can still talk to eachother and decide who is "in charge".
Creating a lacp trunk for interface E4 is not neccesary, but if you do this you can easily add more interfaces to this connection making it redundant in itself and giving you more throughput.
Best Regards // Kristian Modess