The other posters have addressed V2 and V3 OSPF, but do realize, implementations, including Cisco's, do sometimes vary if there are "optional" parts of the specification (or other RFC suggestions), vendor "enhancements", and in the "gray" areas of the specification, i.e. how the protocol is actually implemented. These sometimes lead to (hopefully) rare, but "interesting" issues when mixing vendors or even major software levels within a vendor's product line even though the "whatever the product" meets standards.
Reason I mention the above, just wondering why you wanted to know the OSPF version.
A simple example of differences within the same OSPF standard, is anything automatically done for link costing?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...