Relationships

Relationships enable Network Protocol Manager to associate the discovered logical routing topology objects with each other, and with the underlying physical network topology objects discovered by IP Availability Manager. Because the relationships establish dependencies between the routing topology objects and the network objects, Network Protocol Manager is able to correlate underlying network failures with routing-protocol service impairments.

BGP, EIGRP, IS-IS, and OSPF relationships describes some of the relationships that can appear in the class representation of BGP, EIGRP, IS-IS, and OSPF topology.

Table 1. BGP, EIGRP, IS-IS, and OSPF relationships

Relationship sets	Examples
1**Endpoint1 and Endpoint2 do not have inverse relationships.
AccessedVia/Accesses	BGPService AccessedVia BGPProtocolEndpointBGPProtocolEndpoint Accesses BGPService EIGRPService AccessedVia EIGRPProtocolEndpointEIGRPProtocolEndpoint Accesses EIGRPService ISISService AccessedVia ISISNeighborEndpointISISNeighborEndpoint Accesses ISISService OSPFService AccessedVia OSPFNeighborEndpointOSPFNeighborEndpoint Accesses OSPFService
ComposedOf/PartOf	Router ComposedOf InterfaceInterface PartOf Router
ConnectedTo/ConnectedVia	BGPSession ConnectedTo BGPServiceBGPService ConnectedVia BGPSession EIGRPSession ConnectedTo EIGRPServiceEIGRPService ConnectedVia EIGRPSession ISISNetwork ConnectedTo ISISInterfaceISISInterface ConnectedVia ISISNetwork OSPFNetwork ConnectedTo OSPFInterfaceOSPFInterface ConnectedVia OSPFNetwork
ConnectedSystems	BGPSession ConnectedSystems RouterRouter ConnectedVia BGPSession EIGRPSession ConnectedSystems RouterRouter ConnectedVia EIGRPSession ISISAdjacency ConnectedSystems RouterRouter ConnectedVia ISISAdjacency OSPFNeighborRelationship ConnectedSystems RouterRouter ConnectedVia OSPFNeighborRelationship
ConsistsOf/MemberOf	AutonomousSystem ConsistsOf BGPServiceBGPService MemberOf AutonomousSystem AutonomousSystem ConsistsOf RouterRouter MemberOf AutonomousSystem BGPSessionGroup ConsistsOf BGPSessionBGPSession MemberOf BGPSessionGroup EIGRPDomain ConsistsOf EIGRPNetworkEIGRPNetwork MemberOf EIGRPDomain EIGRPDomain ConsistsOf EIGRPServiceEIGRPService MemberOf EIGRPDomain ISISArea ConsistsOf ISISNetworkISISNetwork MemberOf ISISArea ISISArea ConsistsOf ISISServiceISISService MemberOf ISISArea OSPFArea ConsistsOf OSPFNetworkOSPFNetwork MemberOf OSPFArea OSPFArea ConsistsOf OSPFServiceOSPFService MemberOf OSPFArea
Endpoint1 or Endpoint2 1	BGPSession Endpoint1 or Endpoint2 BGPProtocolEndpoint EIGRPSession Endpoint1 or Endpoint2 EIGRPProtocolEndpoint ISISAdjacency Endpoint1 or Endpoint2 ISISNeighborEndpoint OSPFNeighborRelationship Endpoint1 or Endpoint2 OSPFNeighborEndpoint
HostedBy/HostsServices	BGPService HostedBy RouterRouter HostsServices BGPService EIGRPService HostedBy RouterRouter HostsServices EIGRPService ISISService HostedBy RouterRouter HostsServices ISISService OSPFService HostedBy RouterRouter HostsServices OSPFService
LayeredOver/Underlying	BGPProtocolEndpoint LayeredOver InterfaceInterface Underlying BGPProtocolEndpoint EIGRPProtocolEndpoint LayeredOver InterfaceInterface Underlying EIGRPProtocolEndpoint ISISNeighborEndpoint LayeredOver ISISInterfaceISISInterface Underlying ISISNeighborEndpoint OSPFNeighborEndpoint LayeredOver OSPFInterfaceOSPFInterface Underlying OSPFNeighborEndpoint

The examples given in BGP, EIGRP, IS-IS, and OSPF relationships are just a few of the many relationships that can appear in the class representation of routing-protocol topology. Generally, as demonstrated in the examples, for every relationship, there is an inverse relationship; for example, PartOf is the reverse relationship of ComposedOf.

The Common Information Model (ICIM) 1.11 Reference for Non-Service Assurance Manager Products provides detailed descriptions of classes and relationships.