Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Resolved Issues

 

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.

Identifier

Description

1315434

NorthStar was not displaying correct bandwidth utilization figures in NorthStar 3.0.0.

1319301

NorthStar was not displaying link and LSP delay information.

1337655

NorthStar upgrade was not working properly.

1370026

Sort option in the web UI was sorting the entries only on the first page.

1380934

NorthStar NETCONF collection was running forever on NorthStar 3.2.1.

1382268

Link diversity was failing after bringing link down on one of the two preferred paths.

1387466

Default map views were not getting loaded for another user.

1396680

Stale PCOperator processes consumed memory and caused frequent restart of Cassandra database process.

1414695

Database initialization failed during upgrade.

1421093

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.

1432369

PCS was not setting overload to false for a node in the model when updated by TopoServer.

1434449

Aggregated Ethernet interface traffic statistics were computed incorrectly when telemetry was used.

1450327

LDAP authentication with SSL was not working properly.

1457141

"Active" node unreachable message in UI.

1457425

"Host default gateway" could not be set via net_setup.py after changing the default gateway IP address.

1461140

Reduced default verbosity of logs written into bandwidth_sizing.log.

1461185

NorthStar LSP was staying stuck after NorthStar tried to modify a device controlled LSP.

1461612

LSP rerouting was not triggered by threshold crossing.

1462497

Active NorthStar VM shutdown was not causing HA failover.

1462819

NorthStar analytics cluster HA failover root cause.

1464201

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.

1466962

Netconf status stayed down after change of password on the router and device profile.

1467512

High memory usage and swap usage was causing high load on two analytics nodes.

1468633

There was an incorrect warning about node count being exceeded in the UI.

1469455

Netconf issues reported while running test connectivity as well as netconf testing.

1470045

NorthStar provisioned SRLG diverse LSPs were using links from the same SRLG.

1470616

Web UI page stayed in loading state on navigating to System Health.

1470893

Dashboard network model audit was showing "Unavailable".

1471316

NorthStar UI was not allowing LSP/task creation and did not display running tasks.

1473136

P2MP: LSPs are being deleted when they should be modified.

1475180

NorthStar analytics was not working with Junos telemetry.

1478008

Controller status was showing “No Path Found” post reboot of MX router, even after confirming that LSP showed OP Status as 'Active' and up.

1478237

NorthStar 5.0.0 topology map was not putting nodes with [0, 0] lat/long coordinates in the correct location.

1478317

Duplicate links returned via API query - link latency task was measuring latency for certain links twice.

1478916

NORTHSTAR:Link - one end interface not identified.

1479535

Network Archive and Network Cleanup tasks Summary window was always showing "Collecting information from 1 devices..."

1479554

NorthStar Controller task collection was showing data returned from previous task.

1480325

Main server UI has restricted Admin view.

1480335

NorthStar UI was not showing Add/Modify/Delete buttons for LDAP users.

1482127

Telemetry data not appearing in NorthStar 4.0.

1483229

NorthStar UI was unable to display interface utilization AZ or ZA for some routers.

1484582

SSH process failure post upgrade to 5.1.0.

1485994

CollectionCleanup task was reporting unable to connect to collector at 127.0.0.1:9200.

1494820

NorthStar topology node did not inherit group assignment from device profile.

1497853

There were overlapping links after migrating IP addresses between links.

1497873

Zombie Rabbitmq upset web application when reanimated, showing an empty task list.

1498021

There was a configServer crash.

1498533

There was a PCServer crash.

1498874

CPU information for data collector display issue under System Health.

1499865

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.

1499940

node.js created many connections to Rabbitmq after a reconnect attempt.

1499942

SSE Stream notification was causing memory buildup and eventually crashed node.js.

1499944

There was an uncaught exception when exiting Java client.

1499946

Default latency graph Y axis minimum is 0-100ms; changed default to 10ms.

1499957

Gateway timeout noticed when accessing NorthStar Planner.

1502265

Problem with the NorthStar Planner statistics box.

1502266

Problem with the NorthStar Planner statistics box.

1502267

NorthStar Planner traffic aggregation window disappeared after task completion.

1502268

NorthStar Planner traffic file header was missing important information.

NA

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.

NA

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.

NA

EPE Planner application could fail to start after a fresh install of NorthStar Controller. Sample log messages when this happened:

  • 2019/11/26 18:38:11.711786 INFO:ConfigReader Configurations initialized are: map[…q_password_enc:<nil> admin_password_enc:,nil>...]

  • 2019/11/26 18:38:11.711828 CRIT:logger Password to connect to the Northstar REST server:127.0.0.1, with the username: admin, not provide

  • 2019/11/26 18:38:11 Password to connect to the Northstar REST server:127.0.0.1, with the username: admin, not provide

NA

Diversity group was not working as expected for individually-created LSPs assigned to the same diversity group.

NA

PCViewer was not updating PCE-controlled LSP paths, resulting in LSP delay not being calculated and updated in the NorthStar web UI.

NA

IP address link changes were not being gracefully handled on the link.

NA

Path preview was not consistent with provisioned path.

NA

Same LSP source and destination caused the entire P2MP group to go into "Unknown state".

NA

Path diversity with symmetric LSPs is not working properly.