With NetworkBrain topology framework, more topology types can be supported without modifying any codes, and existing built-in topology links can be stitched easily and efficiently.
The extensible topology framework consists of the following parts:
Tip: All topology types, interface types, and media types are extensible through scripts and Qapps, without the needs to modify any codes. The customization of extensible topology framework is processed by NetBrain team upon your requests.
The following built-in topology types are provided in the system:
The following modules are offered in the system to help domain administrators manage network topology:
▪Topology Link Manager — used to centralize and manage all topology links generated through building topology. It also supports to add, edit, disable, and lock a topology link, and rebuild any existing topology types.
▪Duplicated IP and Subnet Manager — used to resolve duplicated IPs in IPv4 L3 topology, by moving the interfaces with duplicated IPs and the interfaces of their neighbor devices into different zones. As a result, the topology link of each duplicated IP pair can be maintained separately during the process of building topology, and will not be lost.
The following technologies are also supported when you build topology in the system.
▪MPLS Cloud
An MPLS Cloud is treated as a device. It has its own interfaces and IP interfaces, starting with e0 by default. If two interfaces of an MPLS cloud are configured with the same IP address, but without configured VRF, you can resolve the duplicated IPs by moving them into different zones as you deal with a device. See Resolving Duplicated IP and Subnet for more details.
▪Secondary IP
When building IPv4 or IPv6 L3 topology for the interfaces configured with secondary IPs, a phantom interface will be created for each IP address and all of them will be used in topology calculation to generate links.
▪IP Unnumbered Interface
IP Unnumbered Interfaces are supported in IPv4 L3 topology calculation, but not involved in the calculation of duplicated IPs. The logic to build topology with IP unnumbered interfaces is different from other interfaces. This topology is not simply built based on the same subnet. Instead, if two interfaces have NDP neighbor relationships and are configured with unnumbered IP addresses, then an IPv4 L3 topology link will be created between them.
See also: