After importing the initial routing topology and CLI device-access objects from IP Availability Manager, Network Protocol Manager uses SNMP or CLI discovery to query the devices for routing-topology information. Specifically:
-
Network Protocol Manager for BGP uses SNMP discovery to access the BGP-enabled devices through the SNMP protocol and to poll certain BGP4 MIB objects to discover the BGP objects.
-
Network Protocol Manager for EIGRP uses CLI discovery to access the EIGRP-enabled Cisco devices through the Telnet, SSH1, or SSH2 (recommended) protocol and to execute CLI commands to discover the EIGRP objects.
-
IS-IS-enabled Cisco devices only: Network Protocol Manager for IS-IS uses CLI discovery to access the IS-IS-enabled Cisco devices through the Telnet, SSH1, or SSH2 protocol and to execute CLI commands to discover the IS-IS objects.
-
IS-IS-enabled Juniper devices only: Network Protocol Manager for IS-IS uses SNMP discovery to access the IS-IS-enabled Juniper devices through the SNMP protocol and to poll certain IS-IS MIB objects to discover the IS-IS objects.
-
Network Protocol Manager for OSPF uses SNMP discovery to access the OSPF-enabled devices through the SNMP protocol and to poll certain OSPF MIB objects to discover the OSPF objects.
Network Protocol Manager discovers the logical routing topology and creates a data model representation of the routing topology in its repository. It links the logical routing topology objects with the physical topology objects discovered by IP Availability Manager to build a complete model of the managed routing-protocol network.
