Wow, been at this job for years now and this is the first time I've really looked at this command.
In OSPFv2 and v3 it shows a lot of useful information that I have at times struggled to work out for myself.
Firstly, when recursing the OSPF database to work out routes, costs and so forth I have to do a RIB walk in my head and then look at the respective LSAs. This is time consuming and often not efficient or easy. Now I'll go straight to this command (and the detailed option) to get these things sorted.
Before I move on I recommend you just put a very simple OSPF lab together and run OSPFv2 and one for OSPFv3 in Area 0 on all interfaces. Use the base of any of INE's Lab WBs as they are familiar and easy to follow.
Both OSPFv2 and v3 support the command. It is a way to look at the OSPF-specific RIB and that basic fact is covered in many-a-blog and even documented to some extent by Cisco. What is lacking is the meaning of the output and for me the meaning of the LSAs identified per prefix.
In OSPFv2 and v3 it shows a lot of useful information that I have at times struggled to work out for myself.
Firstly, when recursing the OSPF database to work out routes, costs and so forth I have to do a RIB walk in my head and then look at the respective LSAs. This is time consuming and often not efficient or easy. Now I'll go straight to this command (and the detailed option) to get these things sorted.
Before I move on I recommend you just put a very simple OSPF lab together and run OSPFv2 and one for OSPFv3 in Area 0 on all interfaces. Use the base of any of INE's Lab WBs as they are familiar and easy to follow.
Both OSPFv2 and v3 support the command. It is a way to look at the OSPF-specific RIB and that basic fact is covered in many-a-blog and even documented to some extent by Cisco. What is lacking is the meaning of the output and for me the meaning of the LSAs identified per prefix.
No comments:
Post a Comment