Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

Where to configure IRF?

 
emsc
Advisor

Where to configure IRF?

Hi,

 

I'm planning a 3 rack solution, with 2 ToR switches per rack (5700). These ToR will be uplink to a 5406r.

The idea is to connect servers with LACP to each ToR. 

I also want to configure IRF, one domain per rack.

Question:

  • Should I configure IRF on the 5406r, where the uplink are (using a second transciever) or interconnect both ToR directly and do it from there?

 

Thanks! 

3 REPLIES 3
parnassus
Honored Contributor

Re: Where to configure IRF?

Aruba 5400R zl2 Switch series doesn't support IRF Stacking within its features (eventually there is VSF) because IRF stacking is implemented on (some) Comware 5/7 based switches. Aruba 5400R zl2 is ArubaOS-Switch (legacy ProVision) based.
IRF has nothing to do with Aruba 5400R zl2: various (LACP) BAGGs between your central Aruba 5406R zl2 chassis and each IRF Stack (ToR) of each Rack should suffice.
The point is to plan and distribute three BAGGs from 5406R zl2 and (possibly) each IRF Stack's member...for resiliency...on each Rack.
emsc
Advisor

Re: Where to configure IRF?

Thanks for the answer.

 

So, I'll connect both 5700 directly with SFP+ and form one domain per rack.

Question:

  • Does it make sense to have redundant cross connect between both switches?
  • If I do redundant, should I configure it as LACP?

thanks!

parnassus
Honored Contributor

Re: Where to configure IRF?

Yep, it's reasonable (each IRF Member of the IRF Stack - so each 5700 - has a single SFP+ link to a port of SFP+ module installed into the 5400R zl2 chassis...so you can start with at least 2 SFP+ links - and go up to 8 if you have budget for transceivers and FO cables - between the ToR and the 5400R zl2): a ports trunk made through a BAGG (Yes, configured to use LACP on its member ports) between the IRF Stack and the 5400R zl2 chassis.

That way you will achieve (a) resiliency against cable/physical port failures and (b) enhanced throughput between the Rack's ToR level and the access level...especially considering that your Servers are connected to ToR and your clients are connected to the 5400R zl2 chassis.

Pay attention to distribute as much as possible each of your BAGG's member ports on the 5400R zl2's SFP+ module (a) to avoid SFP+ ports oversubrscription [*] and (b) to provide resiliency against the single SFP+ Module failure (if you are forced to use just a single SFP+ Module on 5400R zl2 chassis and to collect there all your SFP+ ports of the BAGG...then there is nothing you can really do against this SFP+ Module failure)...same on the IRF Stack side...probably distributing your BAGG's member ports into both IRF Members would be a good idea (provided that logical IRF ports 1 and 2 between them are respectively binded to aggregated 10G member ports, see - just an example - this discussion about IRF Stacking topology with only two IRF Stack members).

[*] It's about correctly planning SFP+ (or 10GbE) interfaces channels (to Switch's fabric) grouping/usage (also valid when you are going to use those interfaces as BAGG's members) to avoid oversubrscriptions on the SFP+ Module when single interfaces are forced to sustain wire-speed throughput.