Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[NorthStar] How to determine what is fixed in a NorthStar Service Pack



Article ID: KB35822 KB Last Updated: 19 May 2020Version: 1.0

NorthStar Service Packs have been released, but we don't know what is included in each service pack.

This article explains how you can get a list of what bugs are fixed in the NorthStar service pack.



Beginning with NorthStar version 4.2.3 SP3 and version 5.1.0 SP2, you can get a list of what bugs are fixed in the Service Pack.  

First, go to the path where your patch directory has been extracted to. Then, apply the rpm with the following syntax:

rpm -qp --changelog <enter the northstar patch name>

Example: Assume that you have installed the NorthStar 5.1.0 SP2 Service Pack.

[root@localhost Patches]# cd NorthStar_5.1.0-Patch-All-20200422
[root@localhost NorthStar_5.1.0-Patch-All-20200422]# ls
[root@localhost NorthStar_5.1.0-Patch-All-20200422]# rpm -qp --changelog NorthStar_5.1.0-Patch-SP2-20200422_112357-767683b_107.x86_64.rpm
* Wed Apr 22 2020 Juniper Networks <> - NorthStar_5.1.0-Patch-SP2
- POC-3927: PR 1485994 - CollectionCleanup Task reporting unable to connect to collector at
- POC-4240: Traffic charts not representing correct start time
- POC-3862: NS Planner is not displaying link traffic statistics per CoS
- POC-4338: zombie rabbits upset web, cant list tasks
- POC-4311: GUI issue for parallel links
- POC-3682: Map Layout snaps to 0,0 - Asia network keeps snapping off to the edges
- POC-4731: Link utilization demand reports cause an exception in elasticsearch
- POC-4543: CPU info for data collector display issue under System Health
- POC-4596: SSE Stream notifcation is causing memory buildup and eventually crash nodejs
- POC-4569: uncaught exception when exiting java client
- POC-3163: Restricted Admin View: Stale admin user that has been running for 7 days
- POC-4027: Netflowd does not use sampling_interval in some cases
- POC-4788: Netflow Decoder to handle FLOW_SAMPLER_RANDOM_INTERVAL
- POC-4444: Resolving a node could cause TopoServer stack to overflow
- POC-4593: Issue with node deletion (with force_delete)
- POC-4347: adjust PCS delay unit to micro seconds
- POC-4446: PCS not removing demand permanently on delete order
- POC-4303: reset Topology not reseting PCS node-to-node link table completely
- POC-4213: bug fix on PC interface update
- POC-4212: avoid access LSP signaling address when deleting demand that's not routed
- POC-3900: move path computation request from PCViewer to PCServer
- POC-3968: Path Optimization erases LSP tracking on links if the LSPs maintain the same path update LSPs on link when using the same path on rerouting bug fix on removing lsps on link tracking
- POC-3931: add path name to p2mp branch which inherit template attributes
- POC-4525: PCServer crashed on netflow demands
- POC-4702: Device collection wipes out interface to link mapping in PCS
- POC-4789: PCS linkstat queue corrupted due to thread race condition

[root@localhost NorthStar_5.1.0-Patch-All-20200422]#


Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search