Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Netconf Persistence

 

Netconf Persistence allows you to create collection tasks to discover information from device configurations (such as hostname and interface name), and from operational commands (such as LSP on non-PCEP enabled devices). The Analytics features rely on the results of Netconf collection to associate statistics with the correct network elements. As an alternative to provisioning LSPs (P2P or P2MP) using PCEP (the default), you can also provision LSPs using Netconf.

Enabling Netconf Connections

Before using Netconf features, you must enable your system to allow NorthStar Controller to modify the router configuration files via Netconf. Perform the following steps:

  1. Ensure that port 830 is allowed by any external firewall being used. Port 830 enables Netconf communication between the NorthStar Controller and other devices.
  2. Populate the Device Profile (only the Admin user can perform this step). From the More Options menu in the upper right corner of the NorthStar Controller web UI, navigate to Administration > Device Profile. Figure 1 shows the More Options menu.
    Figure 1: More Options Menu
    More Options Menu
  3. Highlight a device in the Device List and click Modify. The Modify Device(s) window is displayed.
  4. On the General tab, the following fields are required:Note

    If these fields are not populated, the Netconf connection will fail.

    • Management IP: The IP address NorthStar Controller can use to establish Netconf sessions.

    • Vendor: Use the drop-down menu to select the vendor for the device (Juniper, Cisco, and so on).

    • Login and Password: Enter the credentials that allow the NorthStar Controller to authenticate with the router.

  5. Enable NorthStar Controller to use Netconf by clicking the check box beside Enable Netconf in the Netconf section of the Access tab.
  6. Click Modify at the bottom of the Modify Device(s) window.
  7. Click Save Changes (which should be red to signal there are unsaved changes) which should turn black once the save operation is complete.
  8. In the Topology view, verify that the NorthStar Controller can establish a Netconf session. On the Node tab in the network information table, look for the NETCONF Status column. You can select that column for display if it is not already selected by clicking the down arrow next to any column heading, and selecting Columns. The Netconf status should be reported as Up.Note

    In Junos OS Release 15.1F6 and later, you can enable the router to send P2MP LSP information to a controller (like the NorthStar Controller) in real time, automatically. Without that configuration, you must run live network collection tasks for NorthStar to learn about newly provisioned P2MP LSPs.

    In the Junos OS, the configuration is done in the [set protocols pcep] hierarchy for PCEs and for PCE groups:

    set protocols pcep pce pce-id p2mp-lsp-report-capability
    set protocols pcep pce pce-group p2mp-lsp-report-capability