R&S v5 Adv TS lab 3 ticket 4
Just wondering if anyone knew a troublshooting cmd/logic to determine that the loopback interface of R2 was a /24 rather than the required /32?
When running through the tickets I try to assertain the necessary cmds I could use to diagnose this issue, rather than manually checking using 'show run' if at all possible. e.g. debug ppp negotiation etc or show bgp vpnv4 unicast all summary
With this ticket I managed to reach a point where the BGP VPNV4 adjacencies had established and exchanged routes which had been installed in the various VRF RTs. Each loopback was pingable across the network & correct /32 routes were seen at each peer (due to the LOs being treated by default as stub networks by OSPF). Even the show mpls forwarding-table seemed to look OK on a subset of routers I checked.
Is there any obvious show/debug cmd I could/should have used to determine this fault, or, in similar instances is it just best to check manually?