Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resolved Issues

This section lists the resolved issues in NorthStar Controller Release 6.2.4.

  • While saving network archive in NorthStar Planner with a new runcode or directory, traffic files might not be saved in the new location.

  • If you upgrade from NorthStar Release 6.1.0 or earlier, by default, only the networks archived during the past fourteen days are retained.

  • In NorthStar Planner, the network archives shows the affinity attribute value as 0 for some links. [PR 1659045]

  • In NorthStar Planner, OSPF metric of demands may be incorrect when path includes parallel links with differing metrics and one of the links is failed interactively.

  • Delegated LSPs may have some include-all values off by 2 bits which could keep the LSPs from finding the correct path.

  • Logstash may stop processing telemetry while processing unexpected data in an event.

  • An LSP might not take a shortest path when the link threshold re-route interval is configured.

  • Pings from a high-availability (HA) agent to the virtual IP adddress (VIP) of a NorthStar installation fail if the NorthStar application is hosted on a device running CentOS 7.6 and later.

  • The active NorthStar server goes down when the standby server goes down.

  • The default network archives retention period should be set to 60 days (which was 14 days in the previous 6.2.0 releases). The network archives retention period should be modified by editing the value for networkArchiveCapacity in the /opt/northstar/web/config.json file and then running supervisorctl restart infra:prunedb.

  • An RSVP tunnel may attempt to utilize an SR-TE link which does not have RSVP bandwidth configured on it.