- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Redundant Switches
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
09-13-2016 09:28 AM
09-13-2016 09:28 AM
Redundant Switches
Hi all,
I need to implement a couple of swithces 2530 in redundancy. I would like to assign to couple ports (23 and 24) for redundancy link. The servers and workstation implement the LACP on NIC ethernet ports. What is the suggested switch configuration for my scope?
Thanks in advance,
Alberto
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2016 01:49 PM
09-13-2016 01:49 PM
Re: Redundant Switches
Port Trunking is the magic word.
If you need to interconnect your two Aruba 2530 Switches Port Trunking on both ends is required: using two (or more) physical ports aggregated together in a single LAGG (Link AGGregation Group) set up to use LACP should suffice...doing things that way you will be able to enhance the interconnection's resiliency (and also obtain a throughput enhacement too for particular inter-Switch traffic conditions).
Refers to "Port Trunking" on Aruba 2530 documentation.
If your Hosts (Servers/Clients) are yet using Teaming (that's also port trunking with/without LACP) you should pay attention that doing Port Trunking between your two Aruba 2530 doesn't mean you can terminate each (Server/Client) Team's member link into different Switches (to do that you should do something called Distributed Trunking)...but you can connect them to just one of two Switches.
This limitation is due to the fact that Port Trunking doesn't create a Virtual Switch as VSF (Virtual Switching Framework) does so every (Server/Client) Team's member shall co-terminate on one Switch (co-terminus) or the other.
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2016 12:51 AM
09-14-2016 12:51 AM
Re: Redundant Switches
Hi,
first of all thank you for the answer.
Here I detail my request, the servers and worsktation has been configured with the HP Network Fault Tolerant only (NFT), and here attached the network scenario that I had implemented.
So considering this the Port Trunking should be the solution that you suggest?
Best Regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2016 02:25 AM - edited 09-14-2016 02:32 AM
09-14-2016 02:25 AM - edited 09-14-2016 02:32 AM
Re: Redundant Switches
If Servers/Workstations use [*] NFT (Network Fault Tolerance) it means that those hosts use just one Active port (called Primary) of the team to transmit/receive network traffic to/from the network, other remaining teamed ports (called Secondary/Non-Primary) are left in Standby mode, idle until the Primary port eventually fails.
Said so and considering that - probably - your Aruba 2530 Switches have (R)STP yet globally enabled (and so Fast Port Span is globally enabled too) the actual connections (Team's member ports that span to both Aruba 2530 Switches as per attached diagram) should work because each Secondary/Non-Primary link of every Team will be automatically and immediately [**] blocked (not causing a reconvergence calculation by the RSTP) by the RSTP until the Primary member ports eventually fail.
Port Trunking is the only option you have (apart the single link uplink) to interconnect/uplink your two Switches Aruba 2530 giving the interconnection link a basic resiliency (against port/cable failures) and enhanced throughput (in case of inter-Hosts traffic flows of type: many-to-many or many-to-one...from Hosts on Switch A to Hosts on Switch B).
[*] as per NFT related documentation:
I'm not an HPE Employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2016 01:49 AM
09-16-2016 01:49 AM
Re: Redundant Switches
Just to select better my situation, I confirm that all teamed NIC's serever has been connecteted in two separate switch and configured on server as NFT , the switched has been connected with a couple of link (23-24) and I had enable the "spanning-tree".
My question is I had to add some instruction on the configuration below? trunk? or something else?
Thanks so muche
Alb
hostname "SWITCH-A"
timesync sntp
sntp unicast
sntp 30
sntp server priority 1 ....
ip default-gateway ....
vlan 1
name "DEFAULT_VLAN"
untagged 1-28
ip address ....
exit
spanning-tree
hostname "SWITCH-A"
timesync sntp
sntp unicast
sntp 30
sntp server priority 1 ....
ip default-gateway ....
vlan 1
name "DEFAULT_VLAN"
untagged 1-28
ip address ....
exit
spanning-tree