Your question is a little bit unclear.
What do you mean with the word redundancy once it is applied to a single Switch/Chassis?
Do you mean adding redundancy at Management Module level (called Nonstop Switching) within each HPE 5406R zl2 chassis you have or what else (Power Supply redundancy, always within the same chassis)?
If you mean adding redundancy at Management Module level within the same chassis you need to add an additional Management Module per chassis (so you end with an Active Management Module and a Standby Management Module): redundant Management Modules offer Nonstop switching and Hitless failover within the same Chassis.
This, it's clear, is valid only per-chassis not between them.
Start by reading the Chassis Redundancy (8200zl and 5400R Switches) page here and then follow next related pages.
AFAIK there is no other redundancy concept between these Switches (between Fabrics = between Chassis).
Eventually, there is a new technology called VSF (Virtual Switching Framework), very recently introduced, but that technology adds definitely other features (Two Physical Switches become a single Logical Switch) and it has little to do with Management Module redundancy. The VSF, if implemented, disables the Nonstop switching (if enabled).
Probably there are other (more or less complex) configurations with which you can try to avoid SPoF...like using proprietary IRF (Intelligent Resilient Framework) but, AFAIK, IRF is supported only by HPE FlexNetwork Switches family and not by the HPE/Aruba ProCurve one.
I'm not an HPE Employee
VRRP has nothing to do with the broader "core redundancy" concept...so saying that VRRP provides a "redundant core setup" is simply misleading.
Why it is?
Because VRRP is a protocol that provides redundancy to Default Gateway(s) within a LAN; VRRP allows you to provide alternate Default Gateway's paths for LAN's Hosts without changing the IP/MAC addresses by which those Hosts know their next-hop gateway.
So...considering the PO request in the light of what he posted (he didn't mention about any peer/edge Switch connected with Distributed Trunks) if:
- He configures VRRP as you told him,
- He simulates that a Switch of the pair (as example: the VRRP member 1, actually the VRRP Master) goes definitely down (K.O.),
- He has an Host (as example a Workstation) that is directly connected only to that Switch (no DT),
What is going to happen to that Host? ...there is no VRRP that can help it.
That Host on that Switch will be left out...despite the VRRP, despite both HPE 5400R zl2 Chassis are trunked togheter, despite the single HPE 5400R zl2 Chassis has Nonstop switching feature enabled (if equipped with the second Management Module).
If you want redudancy you need Hosts:
- connected to another layer of peer Switch (or Switches), that additional layer is then connected with DT links to the ISC-Enabled core (in this way you are just moving down your SPoF at peer level):
or
- directly connected to the ISC-Enabled core with direct DT links (so you need Host/Servers equipped with dual port NIC with ports capable of Distributed Trunking):
or a mix of both.
In both cases you need ISC. Then you need DTs and, eventually, then you can add VRRP.
For Distributed Trunking (dt-lacp or dt-trunk) to work you must use ISC (InterSwitch Connection) between the two 5400R zl2 cores. It's a pre-requisite.
For Distributed Trunking and ISC there are a lot of others restrictions and requirements.
I'm not an HPE Employee
Sorry! was an hot day yesterday. I didn't mean to offend you.
The point is that a Core that has no other connections to any other device (so there is only just Switch 1 <--> Switch 2 and exactly nothing else) is a practical non sense, no matter if VRRP, ISC or DT were used or not (probably theoretically it could have a meaning but I ignored it)...so I supposed that if the OP asked (He asked two times, didn't him?) for an Active/Standby clustering-like Core with two 5400R zl2 then maybe he is going to use that clustered-Core to provide some sort of continuity to any Servers/Hosts and/or to any Edge/Access Switches (not indicate, you're right) connected to it.
It's like the OP is asking for a "load balancing"/"redudancy" to nowhere...
Yes, I just supposed that and I build up a picture a little bit more complex than required but I did that to show the OP that things (if he really need to implement that) aren't simple as his request.
Sorry again.
I'm not an HPE Employee
Hello Biju,
I think we understood pretty well what you have.
IMHO, the point here is that you need to explore/read/understand by yourself any pertinent documentation about the features provided by Aruba 5400R zl2 so you can compare them with your specific requirements and decide what to do next.
Start by reading The Joy of Stacking here.
The Aruba VSF Configuration Guide is published here.
Also the ArubaOS-Switch Management and Configuration guide for K/KA/KB.16.01 has a good section (Chapter 19) about VSF. Read it.
Just study all the material you're able to find.
There is also a nice Video about VSF in which Justin Nooan (Technical Marketing Engineer at HPE) explains quite well what VSF is and how to configure it; that video is called "Improve network resiliency with VSF simplicity" and can be found here.
It's really up to you to understand if what you want is achievable (or not) with the systems and the knowledge you have now.
It's really up to you to understand if VSF is good enough (it has clear requirements and restrictions, pay attention) or if you need something different to setup, as written.
Good work and good luck Biju.
P.S.
It's not clear from the picture...but I think you're using the HP 12-port 10/100/1000BASE-T PoE+ / 12-port 1GbE SFP MACsec v3 zl2 Module (J9989A) for your uplinks between your 5406R zl2 Switches...if so...even if you just want to give VSF a try...you will not be able to...because VSF cannot be enabled on port(s) operating at other than 10G or 40G (you have SFP so limited to 1G ports) and, in any case, you can't mix different port speeds in the same VSF link: all ports of the VSF link must be either 10G or 40G (no 1G).
I'm not an HPE Employee