beef410's version from 2018-04-11 14:31


Question Answer
Instancesv2 and v3 can be run on the same router and will act as v2 with different processes numbers would.
Enablingv3 uses OSPF on a per interface basis, no network command
RIDSames a v2, even uses ipv4 still. If none present an ipv4 RID must be created
Single Link, Multiple InstancesUnlike v2, v3 allows a single link to participate in multiple OSPF instances routers FF02::5 DR/BDR's FF02::6
(config)# ipv6 unicast-routingEnables IPv6 routing, off by default
(config-rtr)#IPv6 prompt. IPv4 is (config-router)#
sh ipv6 ospfRequired for IPv6 implementations
Point to PointDoesn't elect DR/BDR can be seen from sh ipv6 ospf int.
IPv6IPv6 EVERYTHING, router will let you use the ip command in most cases without warning.
(config-if)$ipv6 ospf neighbor <ipv6>Manually set neighbor, uses link local FE80 address. Required on hub of NBMA network
NBMAHub, enable OSPF on int and use neighbor command; spoke, enable on int and use priority 0 command
(config-rtr)# area # stubList area as a stub, resets adjacencies
Total stub(config-rtr)# area # stub no-summary, if existing stub will not reset adj. Only needed on border router.
Virtual LinkStatement is on the transit router, whereas v2 has it on the end-routers with statements 'facing' each other
NeighborBeing a neighbor does not indicate adjacency. 2way/drother state in a broadcast network with 4+ routers indicates neighbor with non-DR/BDR router but not an adjacency
(config-if)#ipv6 ospf # area #Enable OSPF on the interface using process #, area #.