Table 4 lists resolved issues in NorthStar Controller Release 6.0.0. If an identifier is reported, it is the assigned identifier in the GNATS problem report tracking system.
Table 4: Resolved Issues in NorthStar Controller Release 6.0.0.
NorthStar was not displaying correct bandwidth utilization figures in NorthStar 3.0.0.
NorthStar was not displaying link and LSP delay information.
NorthStar upgrade was not working properly.
Sort option in the web UI was sorting the entries only on the first page.
NorthStar NETCONF collection was running forever on NorthStar 3.2.1.
Link diversity was failing after bringing link down on one of the two preferred paths.
Default map views were not getting loaded for another user.
Stale PCOperator processes consumed memory and caused frequent restart of Cassandra database process.
Database initialization failed during upgrade.
Junos OS: A user can configure a template in the router and map that template to an external controller. The router inherits the required configuration from the template and then provisions the external controller-initiated LSP. Unbinding the template from the external controller or changing template configuration can trigger deletion of the PCE-initiated LSPs (only LSPs which are using that particular template). Later, the LSPs are re-provisioned by the external controller.
PCS was not setting overload to false for a node in the model when updated by TopoServer.
Aggregated Ethernet interface traffic statistics were computed incorrectly when telemetry was used.
LDAP authentication with SSL was not working properly.
"Active" node unreachable message in UI.
"Host default gateway" could not be set via net_setup.py after changing the default gateway IP address.
Reduced default verbosity of logs written into bandwidth_sizing.log.
NorthStar LSP was staying stuck after NorthStar tried to modify a device controlled LSP.
LSP rerouting was not triggered by threshold crossing.
Active NorthStar VM shutdown was not causing HA failover.
NorthStar analytics cluster HA failover root cause.
POC-3191 Tony, Sid
P2MP: During transient make-before-break, the PCE server could erroneously send a delete event message to the PCS, potentially causing a branch to go from “live” to “unknown” state. The PCS then detected the unknown state and tried to reprovision. The PCE server accepted the order and forwarded it to the PCC, but the PCC returned an error saying the LSP already existed. The only workaround was to deactivate and activate the PCEP protocol.
Netconf status stayed down after change of password on the router and device profile.
High memory usage and swap usage was causing high load on two analytics nodes.
There was an incorrect warning about node count being exceeded in the UI.
Netconf issues reported while running test connectivity as well as netconf testing.
NorthStar provisioned SRLG diverse LSPs were using links from the same SRLG.
Web UI page stayed in loading state on navigating to System Health.
Dashboard network model audit was showing "Unavailable".
NorthStar UI was not allowing LSP/task creation and did not display running tasks.
P2MP: LSPs are being deleted when they should be modified.
NorthStar analytics was not working with Junos telemetry.
Controller status was showing “No Path Found” post reboot of MX router, even after confirming that LSP showed OP Status as 'Active' and up.
NorthStar 5.0.0 topology map was not putting nodes with [0, 0] lat/long coordinates in the correct location.
Duplicate links returned via API query - link latency task was measuring latency for certain links twice.
NORTHSTAR:Link - one end interface not identified.
Network Archive and Network Cleanup tasks Summary window was always showing "Collecting information from 1 devices..."
NorthStar Controller task collection was showing data returned from previous task.
Master server UI has restricted Admin view.
NorthStar UI was not showing Add/Modify/Delete buttons for LDAP users.
Telemetry data not appearing in NorthStar 4.0.
NorthStar UI was unable to display interface utilization AZ or ZA for some routers.
SSH process failure post upgrade to 5.1.0.
CollectionCleanup task was reporting unable to connect to collector at 127.0.0.1:9200.
NorthStar topology node did not inherit group assignment from device profile.
There were overlapping links after migrating IP addresses between links.
Zombie Rabbitmq upset web application when reanimated, showing an empty task list.
There was a configServer crash.
There was a PCServer crash.
CPU information for data collector display issue under System Health.
NorthStar Planner BGP report was incorrectly showing certain routers to be peered with only one route reflector, when in fact it was peered with two. The underlying issue was with the configuration parsing of IOS-XR devices and how to assess whether a node is a route reflector or not. The issue was resolved by enhancing the configuration parsing code where route reflector determination could be based on presence of a ‘cluster-id’ statement in the neighbor-group block referenced by the neighbor block under the router bgp section for IOS-XR devices.
node.js created many connections to Rabbitmq after a reconnect attempt.
SSE Stream notification was causing memory buildup and eventually crashed node.js.
There was an uncaught exception when exiting Java client.
Default latency graph Y axis minimum is 0-100ms; changed default to 10ms.
Gateway timeout noticed when accessing NorthStar Planner.
Problem with the NorthStar Planner statistics box.
Problem with the NorthStar Planner statistics box.
NorthStar Planner traffic aggregation window disappeared after task completion.
NorthStar Planner traffic file header was missing important information.
The privateForwardingAdjacency (a pair of binding SID SR LSPs from A->Z and Z->A) logical link could be marked as down after the TopoServer process was restarted.
NETCONF-Provisioned SR Tunnels: NETCONF-provisioned SR tunnels can only depend on static (as opposed to dynamic) SIDs. Dynamic SIDs can change at any time due to various network events such as interface flaps. If SIDs change, NorthStar detects the tunnels affected and marks their paths as “down”, but still shows their tunnels as “up”. The paths for these tunnels are no longer highlighted in the topology.
EPE Planner application could fail to start after a fresh install of NorthStar Controller. Sample log messages when this happened:
Diversity group was not working as expected for individually-created LSPs assigned to the same diversity group.
PCViewer was not updating PCE-controlled LSP paths, resulting in LSP delay not being calculated and updated in the NorthStar web UI.
IP address link changes were not being gracefully handled on the link.
Path preview was not consistent with provisioned path.
Same LSP source and destination caused the entire P2MP group to go into "Unknown state".
Path diversity with symmetric LSPs is not working properly.