Path Analysis

To see how Routing Instances affect the routing in a network, assign a Routing Instance to the Demand Type of demands (Network > Elements > Demands) or path traces (Network > Path & Capacity > Path) as shown in Figure 1. This window is accessed by clicking on the Type button of the Modify Demand or Demand Path window. Demands with a Routing Instance assignment can only be routed over links with the same Routing Instance setting.

Figure 1: Demand Type Window Software interface window titled Demand Type Parameter Generation with tabs General, Design, and Advanced. General tab includes settings for LDP Packet, Fixed T-Solve BW, Multicast, ECMP, Policy Class, and Routing Instance. Buttons for OK, Cancel, and Help are at the bottom.

Software interface window titled Demand Type Parameter Generation with tabs General, Design, and Advanced. General tab includes settings for LDP Packet, Fixed T-Solve BW, Multicast, ECMP, Policy Class, and Routing Instance. Buttons for OK, Cancel, and Help are at the bottom.

Reports

Navigate to Report > Report Manager from the main menu. Select the Route Instance report from Network Reports > Protocols. This report (RTINSTRPT) displays several integrity checks:

Asymmetric Route Instance Definition: Indicates links whose interfaces are associated with different Routing Instances
Unexpected OSPF process number: Indicates if an unexpected OSPF process number is defined
Site Diverse Statistics: An Isolated Site is defined as a site which has the given routing instance configured on at least one of its routers, but that site is not accessible via this routing instance from outside the site. A Single Link Site is defined as a site which only has one link of the given routing instance that can be used to reach the site from outside the site. If that link goes down, there is no other way to access that site for this routing instance.
BGP community definition errors: Indicates if the next-hop for any given community is in a different Routing Instance
Isolated colored PoP: Indicates if a Routing Instance has no outgoing link
Note that routing instance definitions via the routeinstance file or the Network > Protocols > OSPF/ISIS Routing Instance are prerequisites to generating the report.

Figure 2: Routing Instance Integrity Check Report

Alt text: Screenshot of Report Manager software showing the Route Instance Integrity Check Report. The left pane lists report categories with Route Instance selected under Protocols. The right pane displays report details including software release, customer, platform, report date, user, and sections on ProcessID to RouteInstance Mapping, Asymmetric Route Instance definition, and Site Diverse Statistics. No asymmetric route instance violations are present; site diversity statistics show none for listed instances.

File Format

ROUTEINSTANCE File

This file should be referenced in the specification file as “routeinst= filename”.

Note:

Because OSPF process names do not need to be specified for Juniper routers, a special keyword “NOID” is used, as seen in the third entry. The keyword “NOID” indicates that the interface is OSPF-enabled but is not listed in the [edit routing-instances] section for a Juniper router