Additional considerations when troubleshooting MSTP/SMLT co-existence
1. Verify that both boxes are operating in the same mode (4 or 2byte). If 4Byte, the 4-
2. Attempt to ping the destination network to ensure it is reachable.
3. If unable to extablish an IGP connection, check for IGP neighbors and check
4. Check whether the path learned is the best path from an IBGP or EBGP peer.
5. Check the topology for an STP blocking state on the ports or non-routable
6. Check for ARP entries of the next-hop (if next-hop is specified). If there is no ARP
7. If neighbor discovery for a particular IPv6 route fails then the IPv6 route will not be
Routes are not advertised to a BGP peer
If routes are not advertised to a BGP peer, use the following procedure to troubleshoot the
issue.
1. If you use the network command, then check for the route information.
2. If you use a redistribute command to advertise a static or IGP route, check whether
3. If the problem still persists then check whether any route policy is configured on the
4. Check all redistributed routes:
Troubleshooting
byte-as flag needs to be enabled globally.
whether or not IGP is enabled.
interfaces.
entry, the route will not be added to the route table.
installed in the RTM.
show ip route info (CLI)
show ip route (ACLI)
auto-summary is enabled.
show ip bgp conf (CLI or ACLI)
redistribute command denying the peer:
show ip bgp redistribution (CLI)
show ip bgp redistributed-routes (ACLI)
show ip bgp imported-routes (CLI or ACLI)
BGP+ troubleshooting
July 2013
365