Leaf issue

[nomair_83]

Hi, Is it possible that one leaf reboot could affect other leaf switches ?

Regards,

[Robert Burns]

That depends how you define "affect".  IF the switches are border leafs, rebooting another border leaf would have some layer 3 routing changes, but shouldn't necessarily be a negative impact.  Additionally if the switches are VPC Peers, there's going to be some change in forward behavior, but also not necessarily a bad thing.   Typically rebooting a single leaf will not directly impact another leaf outside of the usual forwarding updates & changes.

Robert

[nomair_83]

Thanks for clarification :).

One of our leaf switch restarted and during the same time APIC shows tunnel down on other leaf switches and protocol-bgp-adjacent errors. We did not face any errors on spine and no impact was observed by end users.

I found protocol-bgp-adjacent details but not able to understand what caused this sudden tunnel disconnections to other switches and one leaf switch restart.

APIC software version is 1.32f

Any help or hint is appreciated :)

F0299 - fltBgpPeerEntryFailed

Syslog Message

%LOG_LOCAL0-4-SYSTEM_MSG [F0299][protocol-bgp-adjacency-down][warning][DN of affected MO] BGP peer is not established, current state [operSt]

Explanation

This fault occurs when the peer state is not established

Recommended Action

To recover from this fault, try the following actions

---

Step 1 Look at any configuration issues

Step 2 Verify the configuration is correct/complete

Step 3 Check network connectivity to the peer

Step 4 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

[sateeshk10]

Hi,

I never experienced such kind of issues, could be configuration issue?

Regards

Sateesh K

[micgarc2]

From the leaf that is affected try what is the output of show bgp sessions vrf overlay-1

Compare this command with a working leaf.

Were any of the spines every decommissioned?

You may have a stale entry for a spine that was configured as a route reflector. The peer may not be in an established state ("E") causing you to get this fault (F02999).