IBGP can cycle between established and available

IF you have a configuration where you have 2 routers to 2 separate ISPs if you run IBGP on the loopback interface and you do not cover that with an IBGP network statement, BUT put a BGP network statement this bouncing can happen. Router B does not have its loopback statement covered by OSPF, router A learns the loopback via eBGP. An IBGP session comes up going through the providers. Since most IBGP sessions have next hop self you get a recursive route situation. Adding router Bs loopback into the IGP fixes this. The first part of IBGP debugging is making sure that the peers match (if router A peers to router Bs loopback, then router B needs update source loop 0), after that you check that you have a route to the loopback address. You have to check were that route came from (make sure not eBGP).