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
  1. AccessedVia

BGPProtocolEndpointBGPProtocolEndpoint
  1. Accesses

BGPService
EIGRPService
  1. AccessedVia

EIGRPProtocolEndpointEIGRPProtocolEndpoint
  1. Accesses

EIGRPService
ISISService
  1. AccessedVia

ISISNeighborEndpointISISNeighborEndpoint
  1. Accesses

ISISService
OSPFService
  1. AccessedVia

OSPFNeighborEndpointOSPFNeighborEndpoint
  1. Accesses

OSPFService

ComposedOf/PartOf

Router
  1. ComposedOf

InterfaceInterface
  1. PartOf

Router

ConnectedTo/ConnectedVia

BGPSession
  1. ConnectedTo

BGPServiceBGPService
  1. ConnectedVia

BGPSession
EIGRPSession
  1. ConnectedTo

EIGRPServiceEIGRPService
  1. ConnectedVia

EIGRPSession
ISISNetwork
  1. ConnectedTo

ISISInterfaceISISInterface
  1. ConnectedVia

ISISNetwork
OSPFNetwork
  1. ConnectedTo

OSPFInterfaceOSPFInterface
  1. ConnectedVia

OSPFNetwork

ConnectedSystems

BGPSession
  1. ConnectedSystems

RouterRouter
  1. ConnectedVia

BGPSession
EIGRPSession
  1. ConnectedSystems

RouterRouter
  1. ConnectedVia

EIGRPSession
ISISAdjacency
  1. ConnectedSystems

RouterRouter
  1. ConnectedVia

ISISAdjacency
OSPFNeighborRelationship
  1. ConnectedSystems

RouterRouter
  1. ConnectedVia

OSPFNeighborRelationship

ConsistsOf/MemberOf

AutonomousSystem
  1. ConsistsOf

BGPServiceBGPService
  1. MemberOf

AutonomousSystem
AutonomousSystem
  1. ConsistsOf

RouterRouter
  1. MemberOf

AutonomousSystem
BGPSessionGroup
  1. ConsistsOf

BGPSessionBGPSession
  1. MemberOf

BGPSessionGroup
EIGRPDomain
  1. ConsistsOf

EIGRPNetworkEIGRPNetwork
  1. MemberOf

EIGRPDomain
EIGRPDomain
  1. ConsistsOf

EIGRPServiceEIGRPService
  1. MemberOf

EIGRPDomain
ISISArea
  1. ConsistsOf

ISISNetworkISISNetwork
  1. MemberOf

ISISArea
ISISArea
  1. ConsistsOf

ISISServiceISISService
  1. MemberOf

ISISArea
OSPFArea
  1. ConsistsOf

OSPFNetworkOSPFNetwork
  1. MemberOf

OSPFArea
OSPFArea
  1. ConsistsOf

OSPFServiceOSPFService
  1. MemberOf

OSPFArea

Endpoint1 or Endpoint2 1

BGPSession
  1. Endpoint1 or Endpoint2

BGPProtocolEndpoint
EIGRPSession
  1. Endpoint1 or Endpoint2

EIGRPProtocolEndpoint
ISISAdjacency
  1. Endpoint1 or Endpoint2

ISISNeighborEndpoint
OSPFNeighborRelationship
  1. Endpoint1 or Endpoint2

OSPFNeighborEndpoint

HostedBy/HostsServices

BGPService
  1. HostedBy

RouterRouter
  1. HostsServices

BGPService
EIGRPService
  1. HostedBy

RouterRouter
  1. HostsServices

EIGRPService
ISISService
  1. HostedBy

RouterRouter
  1. HostsServices

ISISService
OSPFService
  1. HostedBy

RouterRouter
  1. HostsServices

OSPFService

LayeredOver/Underlying

BGPProtocolEndpoint
  1. LayeredOver

InterfaceInterface
  1. Underlying

BGPProtocolEndpoint
EIGRPProtocolEndpoint
  1. LayeredOver

InterfaceInterface
  1. Underlying

EIGRPProtocolEndpoint
ISISNeighborEndpoint
  1. LayeredOver

ISISInterfaceISISInterface
  1. Underlying

ISISNeighborEndpoint
OSPFNeighborEndpoint
  1. LayeredOver

OSPFInterfaceOSPFInterface
  1. 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.