Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Known Behavior

 

The following behaviors are known to occur in NorthStar Controller Release 5.1.0:

  • Important: It is currently necessary to remove any lingering NorthStar RPM packages before performing a fresh installation of NorthStar Release 5.1.0. This will be unnecessary in future releases.

  • EPE Planner: Testing shows that Junos PRPD/SR/Steering functionality is very sensitive to load and routing can be adversely affected if the functionality is driven too hard by NorthStar. As a result, when executing a plan change, the EPE Planner must pace the rate of operations that change the network to a configured rate.

    A configuration setting is available in both northstar.cfg and in the settings that can be managed by the REST API to help manage this.

    This parameter is the maximum rate at which the EPE Planner executes NorthStar REST API calls that change the network in units of calls per second. The NorthStar REST API calls that the EPE Planner executes in the process of executing a plan change are:

    • Posts, Patches, Puts, and Deletes of demands to change the LSP bindings and steer traffic

    • Patches of LSPs to change the tunnel bandwidth

    See Understanding the EPE Planner Application for information about setting this parameter and the effect it has.

  • PCEP P2MP: NorthStar automatically reroutes PCEP P2MP groups around a network element failure. After the failed element comes back up, the group might not be automatically restored to the original path, even if the user chooses to optimize LSP paths. In a future NorthStar release, the concept of what constitutes an optimal P2MP group will be addressed.

  • Behaviors and limitations related to PCEP-provisioned P2MP Groups:

    • This feature requires that you use Junos OS Release 18.3R2 or later, in which the following Junos OS PRs have been fixed:

      • Junos OS PR 1412649

        The fix for this PR enables you to define a separate template for P2MP (separate from the one used for P2P), one that does not allow “adaptive” to be configured. To define the new template, configure the following statements on the head end PE of the PCE-initiated P2MP LSP:

      • Junos OS PR 1412490

        The fix for this PR ensures that deletion of P2MP PCEP branches is properly reported.

      • Junos OS PR 1358245 (not specific to P2MP).

        The fix for this PR ensures that segment routing (SR) path names are properly reported in Junos OS Release 18.3R2.

    • When viewing P2MP groups in the network information table, be aware that the refresh button at the bottom of the table periodically turns orange to prompt you for a refresh. When you click the refresh button, the web UI client retrieves the latest P2MP sub-LSP status from the NorthStar server.

  • NETCONF P2MP (Re-provisioning LSPs):

    • For a NETCONF-provisioned P2MP tree, reprovisioning individual sub-LSPs to go around a failed link can fail under the following conditions:

      • The user reprovisions sub-LSPs separately.

      • The user has a mixture of sub-LSPs with a user-specified strict path and paths computed by NorthStar.

    • The workflow is to reprovision all sub-LSPs of a tree together; NorthStar computes sub-LSPs of a tree as a whole, not individually.

  • Automatic rerouting: Automatic rerouting of NETCONF-provisioned LSPs (including NETCONF-provisioned SR LSPs) due to a failure in the network is not supported.

  • PCE-initiated LSP: During PCE-initiated LSP, some Cisco routers configured with IOS-XR version can return an error code for an unknown reason. Currently NorthStar Application only reports “NS_ERR_GENERIC” when this issue happens. It is planned to improve this behavior and report the exact error code (e.g. PCEP Error Type = 24 error value = 2 ) in future releases.

  • Empty Results in Service Tab: In rare case, you might get an empty result in the network information table, Service tab for both summary and detailed information, for example, after a system upgrade. If this happens, you can resolve it by restarting the web process:

  • Netflow Collector: It can happen that during a NorthStar upgrade, netflowd cannot be started. If netflowd fails to start, run the following command on the system hosting the netflowd collector:

    After running the command, restart the Netflow process: