Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Dual Routing Engine Support

 

Some routers have more than one routing engine. In this case, only one routing engine is operational at any given point in time. Depending upon which routing engine is active, the hostname and management IP address can be different. In this case, for the traffic collection to recognize that two hostnames belong to the same device, this information may need to be provided as an additional input to IP/MPLSView.

In the case of Juniper master and backup engines, if the default routing engine naming conventions are used, beginning or ending with “re0” or “re1”, then no special configuration is needed. For such a device, IP/MPLSView will store the hostname as the part in common between the two routing engines, that is, with the re0 and re1 removed, along with any separating characters adjacent to re0 and re1 (for example, “.”, “_”, or “-”).

For other naming conventions for dual router engines, it is necessary to create a special alias file to indicate which routing engine hostnames belong to the same router. The format of this file is as follows:

<AliasName> <RoutingEngine0’s Hostname> <Routing Engine1’s Hostname>

Explanation: If this alias file is specified in the Conversion Options of the Scheduling Live Network Collection Task, then the routers in the topology display would be displayed with the name <AliasName> if the host name of the collected router matches with either <RoutingEngine0’s Hostname> or <Routing Engine1’s Hostname>. The original hostname can still be seen in the hostname field of the Network > Elements > Nodes view, which can be added as a column to the table via the right-click menu.

In this case, the Router Profile for the device with the dual router engines should contain the AliasName in the Router Name field. The primary IP address can be set to the loopback IP address of the device, assuming that it is the same for both router engines. Alternatively, if there is no common loopback IP address, then the primary and secondary addresses can be set to the master and backup engines’ management IP addresses. In case the primary address fails, then the secondary address will be used.