Known Issues
Table 3 lists known issues in NorthStar Controller Release 3.1.0. The identifier associated with each entry is the tracking number in the Juniper Networks Problem Report (PR) tracking system.
Table 3: Known Issues in NorthStar Controller 3.1.0
Identifier | Description |
|---|---|
1307031 | SNMP-based interface traffic collection does not work when a router is configured with multiple routing engines. In this case router hostname has suffix re0 and re1 (usually used in dual-RE configuration). |
1307032 | During initial loading of the web UI, the Server Status (Administration > Server Status in the More Options menu) is shown as down for PCE, Topology Acquisition, and PCS. The displayed error message is “Down...cannot retrieve PCE status.” |
1307033 | When the JUNOS statement dealing with node-segment is deactivated in a router, NorthStar may not automatically tear down the SPRING LSP originated, transiting, or terminated onto this router. |
1307034 | Minor display issue when using Chrome: On the Chrome browser, there are some UI issues while modifying the device profile – not all settings are displayed properly in the window. |
1307037 | PCS/ConfigServer rejects a user-specified P2MP group name that is the same as the LSP name: JUNOS does not allow commit if a P2MP name is also used by a current and existing LSP name. |
1307369 | When a PCEP session is down and LSP events are received, PCC-controlled LSPs might be temporarily deleted. |
