Comware Based

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

 
pradeep7739
Occasional Contributor

How to configure and do cabling for BFD MAD on 4 IRF switches

Hi Team,

I am trying to build a irf stack with 4 switches, how to configure BFD MAD for this, i know for 2 switches, but i am confused for 4 switches.

should i do cabling from master to all 3 slave switches? or should they be daisy chained 

14 REPLIES 14
parnassus
Honored Contributor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

BFD MAD without an assist device (a fifth Switch) will require you to directly link any IRF Member with any other IRF member so...four IRF Members will require 6 links (three dedicated interfaces on each IRF Member)...to save interfaces you can deploy BFD MAD with an assist device (the fifth Switch) and so link, on each IRF Member, just one port to that assist device...using only  4 links (so four interfaces, one for each IRF Member).


I'm not an HPE Employee
Kudos and Accepted Solution banner
pradeep7739
Occasional Contributor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

BFD MAD cabling-2.png

if i understood your answer, i am looking at above cabling for BFD MAD.

How about configuration, will all the port be in same VLAN? 

parnassus
Honored Contributor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

Yes, BFD MAD dedicated ports must belong to the same VLAD dedicated to MAD.

Something like (four IRF Members directly connectet each others using three interfaces on each IRF Member, no BFD MAD intermediate device):

 

# IRF BFD MAD dedicated VLAN Id

vlan 200
description IRF-BFD-MAD

# IRF BFD MAD VLAN Id SVIs defined for each IRF Member (here we used a /28 Subnet for up to 14 hosts)

interface Vlan-interface 200
mad bfd enable
mad ip address 10.0.255.1 255.255.255.240 member 1
mad ip address 10.0.255.2 255.255.255.240 member 2
mad ip address 10.0.255.3 255.255.255.240 member 3
mad ip address 10.0.255.4 255.255.255.240 member 4

# IRF Member 1

interface GigabitEthernet 1/0/1
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 1/0/2
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 1/0/3
port link-mode bridge
port access vlan 200
stp disable

# IRF Member 2

interface GigabitEthernet 2/0/1
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 2/0/2
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 2/0/3
port link-mode bridge
port access vlan 200
stp disable

# IRF Member 3

interface GigabitEthernet 3/0/1
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 3/0/2
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 3/0/3
port link-mode bridge
port access vlan 200
stp disable

# IRF Member 4

interface GigabitEthernet 4/0/1
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 4/0/2
port link-mode bridge
port access vlan 200
stp disable

interface GigabitEthernet 4/0/3
port link-mode bridge
port access vlan 200
stp disable

 

A two IRF Members BFD MAD configuration can be found here (as example) BUT, for sure, the IRF Configuration Guide for your Comware based Switch Series (whatever it is) has some BDF MAD deployment examples too.


I'm not an HPE Employee
Kudos and Accepted Solution banner
Stefano Colombo
Regular Advisor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

Hello 

I'm setting up the same configuration, an IRF stack with 4 unit, but we have 2 unit in a data center and other 2 in another room.

Regarding the BFD connection using an assisting device, it would be possible to have 2 assisting devices , one per room, connected together, but not as a stack ?

thanks

 

parnassus
Honored Contributor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

Hi @Stefano Colombo  well let me say that if you already stretched a single IRF domain across two rooms (two IRF members on Room A and the other two IRF members on Room B), using a single BFD forwarding device (on any of the rooms) shouldn't be an issue in terms of cabling effort...documentation reports no particular restrictions in terms of number of BFD assisting switches (I mean there isn't anything in the form of "Two forwarding MAD devices can't be used" statement) but since BFD requires no STP on involved ports....how then you will deal with the fact that you want to use two (one per room) BFD forwarding switch just simply interlinked together (and so not part of an another dedicated IRF domain)? Indeed it is suggested the possibility to use another IRF (with a different Domain ID with respect the "main" IRF you want to protect against split brain scenarios) as the BFD forwarding entity so you can geographycally split it too (placing one fragment on Room A and the other in Room B) and continue to stay with STP not enabled on BFD involved ports. It looks like a sort of looping idea but...consider not implementing it that way will led you to two BFD Switches uplinked together and connected, each one, on each side of your stretched IRF...those two BFD Switches will form a network loop because the IRF acts - stretched or not it will be - as a single logical identity but the two BFD Switches instead act as two separate logical entities connected to your IRF and the loop will form. Am I wrong?

Not specifically related to BFD MAD scenarios...but this old blog post is really interesting about stretched IRF scenarios (Pro/Cons).


I'm not an HPE Employee
Kudos and Accepted Solution banner
Stefano Colombo
Regular Advisor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

HI @parnassus 

We're still in pre-deployment phase, so nothing configured yet.

The scenario is as such.

An IRF domain with 4 5710 devices, 2 per room,.

On each room there are Cisco 9200 swittch wich are connected with normal port channel.

Those 9200 switch, one per side, are the one we can use to configure MAD.
So excluding LACP mad I thougth ad BFD MAD, but your point about STP is correct.

I Thought that requirement for STP disabled on BFD MAD port was only referred on the physical port on the 5710 not on the link between two supporting devices.

Using L3 wouldn't be ok having a dedicated VLAN spanned across the Cisco 9200 switches used for BFD ?

If neither LACP nor BFD could be used in this scenario what can we use then ?

 

parnassus
Honored Contributor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

Ciao @Stefano Colombo 

I see the limitation comes from having the two Cisco switches working respectively as standalone units. Since you need STP enabled at some point (I believe you can't avoid that in the IRF 1 East side - 9200 East side - 9200 West side - IRF 1 West side loop), exactly the STP will kick in to cut the loop.

"I Thought that requirement for STP disabled on BFD MAD port was only referred on the physical port on the 5710 not on the link between two supporting devices."

But STP disabled on ports facing the sides of the HPE 5710 IRF (ports that are on each Cisco 9200) will not save you when both Cisco 9200 will be linked together to transport BFD VLAN messages (and Layer 3 is not an option since you need to transport the BFD VLAN at Layer 2 and, also, if going into Layer 3 between both Cisco 9200 would be an option, then you should create two separated Spanning Tree topologies - one per Cisco 9200 - to avoid STP to kick in among the two...something like using STP BPDU filtering on Cisco 9200 - Cisco 9200 inter-link(s)...I mean each Cisco 9200 should, in that case, have its own Spanning Tree...in any case Layer 3 is not an option with BFD MAD).

The only ways I can think of to overcome this cul-de-sac is:

  1. To use another dedicated IRF/Virtual Stack (ma temo la terapia sia peggiore della malattia che si intende tenere sotto controllo).
  2. To try to link directly IRF Members on both rooms to one single BFD assisting switch (not necessarily one of the two Cisco 9200) installed into Room A or into Room B (or, possibly, in another different room)
  3. Split the IRF stretched domain into two IRF Domains (2 x 5710 will form an IRF Domain on Room A and 2 x 5710 will form another IRF Domain on Room B), at that point implementing any MAD will not be an issue (within a Room). Both IRF Domains will be then interlinked by means of a proper LACP LAG.

With regard to scenario 3 there are for sure other requirements that should be considered too (where routing will take place if you're dealing with two IRFs and not with just one single stretched IRF, as example). There are also technologies as DCI/EVI/VXLAN that will help in interconnecting two Datacenters at Layer 2 level...but probably these weren't considered since you're just planning to "split" a single IRF into two separated DC Rooms...not interconnecting two geographically separated DCs.

Hope not to be wrong...


I'm not an HPE Employee
Kudos and Accepted Solution banner
Stefano Colombo
Regular Advisor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

Ciao @parnassus
I did not mention that there’s another expected connection between the 5710 IRF stack and a stack of 2 Cisco 4500
That connection will be a 4x 10Gb aggregated link, one for rack 5710, to the two Cisco 4500
In stack
Can we use that same link for MAD ? LACP MAD ?
Thanks
parnassus
Honored Contributor

Re: How to configure and do cabling for BFD MAD on 4 IRF switches

Ciao, if the Stack of Cisco 4500 - acting as the intermediate MAD assist "device"- supports extended LACP for MAD...it could work.

At that point on the Cisco 4500 Stack side you only need a "normal" BAGG (Bridge Aggregation) with LACP and on the HPE FlexNetwork 5710 IRF side you just need to setup a MAD LACP as per documentation.

Having a Cisco 4500 Stack available would probably solve your issue but it all boils down to be sure it supports extended LACP for MAD.

Out of curiosity: are the peer systems located in Room A consuming IRF services/features "dual homed" to both IRF Members on Room A and IRF Members on Room B (and vice-versa for peer systems on Room B)?


I'm not an HPE Employee
Kudos and Accepted Solution banner