The three figures, OSPF Connectivity map launched for an OSPFArea object through OSPF Connectivity map launched for an OSPFNeighborRelationship object, show the initial layout of an OSPF Connectivity map launched for an OSPFArea object, an OSPFService object, and an OSPFNeighborRelationship object, respectively.
OSPF Connectivity map launched for an OSPFArea object is an example of an OSPF Connectivity map that has an OSPFArea focal object. The map shows the selected OSPF area, along with the two devices that are members of the OSPF area. The directed dotted lines indicate that the two devices are members of the OSPF area. Each device in Figure 11 is running an OSPF service.
The two member devices that belong to OSPF-AREA-0.0.0.0/OSPF1 also belong to at least one other OSPF area. This fact explains why OSPF-AREA-0.0.0.0/OSPF1 is represented as a standard OSPF area icon rather than as a container. If the two member devices belonged only to OSPF-AREA-0.0.0.0/OSPF1, the OSPF area would be shown as a container with the two devices inside the container.
The inclusion of “/OSPF1” in the OSPF area’s name signifies that Network Protocol Manager for OSPF:
-
Has imported tagged IP objects from the source IP Availability Manager.
-
Has detected tagged IP objects in OSPF area 0.
-
Has created subareas for OSPF area 0 in accordance to the tag values (OSPF1, for example) that are assigned to the tagged IP objects.
As shown in Figure 11, Network Protocol Manager for OSPF has created five subareas for OSPF area 0. In a managed network that contains overlapping IP addresses on the same routing device, the creation of subareas ensures that Network Protocol Manager for OSPF creates the correct OSPF neighbor relationships in its modeled topology. The VMware Smart Assurance Network Protocol Manager Discovery Guide Supplement provides more details about the creation of OSPF subareas and OSPF neighbor relationships in an overlapping IP environment.
OSPF Connectivity map launched for an OSPFService object is an example of an OSPF Connectivity map that has an OSPFService focal object. The map shows the selected OSPF service and its hosting device, along with its neighboring OSPF services and their hosting devices. Because the selected OSPF service is displayed in a container, it is not surrounded by a box.
Figure 2. OSPF Connectivity map launched for an OSPFService object 
The fact that the hosting device of the selected OSPF service is displayed inside the container indicates that the device belongs only to OSPF-AREA-0.0.0.0.
The fact that the hosting devices of the neighboring OSPF services are displayed outside the container indicates that both devices belong to at least one other domain besides OSPF-AREA-0.0.0.0. The directed dotted lines indicate that the devices are members of OSPF-AREA-0.0.0.0.
OSPF Connectivity map launched for an OSPFNeighborRelationship object is an example of an OSPF Connectivity map that has an OSPFNeighborRelationship focal object. The map shows within the container the selected OSPF neighbor relationship, which is represented as a solid green line, between the two devices that are running neighboring OSPF services. Green indicates that the OSPF neighbor relationship is healthy.
Figure 3. OSPF Connectivity map launched for an OSPFNeighborRelationship object 
An OSPF Connectivity map that has an OSPFVirtualLink focal object is similar to an OSPF Connectivity map that has an OSPF NeighborRelationship focal object, except that the peering OSPF devices that are connected by the virtual link are always ABRs.
