Quick IRF Query - hopefully

[stuart_d1]

Hi all,

We have a stack of 5 x 5130-48G's that is showing one of the IRF links as down - see below - my question is, would reseating or inserting a cable (if missing) cause any issues to the stack?

dis irf link

Member 1
IRF Port  Interface                             Status
1         Ten-GigabitEthernet1/0/51             DOWN
2         Ten-GigabitEthernet1/0/52             UP

Member 2
IRF Port  Interface                             Status
1         Ten-GigabitEthernet2/0/51             UP
2         Ten-GigabitEthernet2/0/52             UP

Member 3
IRF Port  Interface                             Status
1         Ten-GigabitEthernet3/0/51             UP
2         Ten-GigabitEthernet3/0/52             UP

Member 4
IRF Port  Interface                             Status
1         Ten-GigabitEthernet4/0/51             UP
2         Ten-GigabitEthernet4/0/52             UP

Member 5
IRF Port  Interface                             Status
1         Ten-GigabitEthernet5/0/27             UP
2         Ten-GigabitEthernet5/0/28             DOWN

[parnassus]

What are (sanitized) outputs of:

• display irf
• display irf configuration
• display irf topology
• display irf link (already provided)
• display mad verbose

commands

[stuart_d1]

>dis irf
MemberID    Role    Priority  CPU-Mac         Description
 *+1        Master  32        00e0-fc0f-8c02  ---
   2        Standby 20        00e0-fc0f-8c03  ---
   3        Standby 15        00e0-fc0f-8c04  ---
   4        Standby 14        00e0-fc0f-8c05  ---
   5        Standby 13        00e0-fc0f-8c06  ---
--------------------------------------------------
 * indicates the device is the master.
 + indicates the device through which the user logs in.

 The bridge MAC of the IRF is: 2c23-3abe-ff65
 Auto upgrade                : yes
 Mac persistent              : 6 min
 Domain ID                   : 11

dis irf conf
 MemberID NewID    IRF-Port1                     IRF-Port2
 1        1        Ten-GigabitEthernet1/0/51     Ten-GigabitEthernet1/0/52
 2        2        Ten-GigabitEthernet2/0/51     Ten-GigabitEthernet2/0/52
 3        3        Ten-GigabitEthernet3/0/51     Ten-GigabitEthernet3/0/52
 4        4        Ten-GigabitEthernet4/0/51     Ten-GigabitEthernet4/0/52
 5        5        Ten-GigabitEthernet5/0/27     Ten-GigabitEthernet5/0/28

dis irf top
                              Topology Info
 -------------------------------------------------------------------------
               IRF-Port1                IRF-Port2
 MemberID    Link       neighbor      Link       neighbor    Belong To
 1           DOWN       ---           UP         2           00e0-fc0f-8c02
 2           UP         1             UP         3           00e0-fc0f-8c02
 3           UP         2             UP         4           00e0-fc0f-8c02
 4           UP         3             UP         5           00e0-fc0f-8c02
 5           UP         4             DOWN       ---         00e0-fc0f-8c02

dis mad v
Multi-active recovery state: No
Excluded ports (user-configured):
Excluded ports (system-configured):
  Ten-GigabitEthernet1/0/51
  Ten-GigabitEthernet1/0/52
  Ten-GigabitEthernet2/0/51
  Ten-GigabitEthernet2/0/52
  Ten-GigabitEthernet3/0/51
  Ten-GigabitEthernet3/0/52
  Ten-GigabitEthernet4/0/51
  Ten-GigabitEthernet4/0/52
  Ten-GigabitEthernet5/0/27
  Ten-GigabitEthernet5/0/28
MAD ARP disabled.
MAD ND disabled.
MAD LACP enabled interface: Bridge-Aggregation1
  MAD status                : Faulty
  Member ID    Port                                    MAD status
  1            Ten-GigabitEthernet1/0/49               Normal
  5            Ten-GigabitEthernet5/0/25               Normal

[pattap · Accepted solution]

Your link between master and switch 5 is down anyway as long as you're not introducing a new master switch or reintroducing existing master, switches within the stack should not reboot also you would't split the stack

[stuart_d1]

Thank you - that was just the quick answer I was looking for. Apprecaite it.

[parnassus]

As @pattap pointed out, your broken IRF Ring topology (the "1-2-3-4-5-1" loop is broken between 1st and 5th IRF Member) is not going to experience an IRF Master re-election because the Master is, actually, Member 1 (the one with highest priority).