Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 

Known Behavior

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

  • Use of the supervisorctl restart all command to restart all services can cause a race condition. We recommend the use of the service northstar restart command instead.
  • If you are using a two-VM installation, in which the Junos VM is not bundled with the NorthStar Controller, and if your external Junos VM is older than Release 17.2, you must edit the northstar.cfg file to make the NorthStar Controller compatible with the external VM.

    Note: If you edit the northstar.cfg file to make the NorthStar Controller compatible with an older external VM, segment routing on the NorthStar Controller will no longer be supported.

    Follow the procedure in the NorthStar Controller Getting Started Guide.

  • After provisioning a P2MP LSP via Netconf, network utilization on the NorthStar Controller topology map might not be immediately refreshed. In this case, right-click on the topology map and select Reload Network.
  • PCEP sessions can flap when some Junos OS statements in the PCC router configuration file are changed. For example, changes in the Junos group stanza.
  • A P2MP group statement provisioned by the NorthStar Controller will not be deleted when the P2MP LSP is deleted. The usser must manually remove the group statements from the router configuration files.

Modified: 2017-09-13