The following new features are introduced in NorthStar Release 4.2.1:
Automation of GeoDiverse HA Cluster Installation
NorthStar 4.2.1 installation has been improved to facilitate the roll-out of GeoDiverse clusters. The installation script offers a new option to automate the deployment of NorthStar servers in remote data centers such as those located in different countries. A new field in the HA Setup menu is now available for entering a site location:
You access the HA Setup menu from the NorthStar Main Menu, option E (HA Setting).
The default site name for all nodes is “site1”. Modify the name for each node as appropriate for your data center setup.
If you configure nodes to have multiple site names, the multi-data center automatic configuration setup for Cassandra is activated when you select option H on the HA Setup menu (Prepare and Deploy HA configs).
If you configure all nodes to have the same site name, the multi-data center automatic configuration setup for Cassandra is not activated.
IMPORTANT: The total number of nodes across all sites must still conform to HA requirements: an odd number of nodes with a minimum of three. We recommend three sites with either one node per site or 3 nodes per site. We do not recommend an even number of nodes nor an even number of sites.
This feature currently does not support adding a new node into a cluster after HA deployment.
This feature currently does not support Analytics.
PCEP Mapping File to Improve PCEP Interoperation with Non-Juniper Equipment
The PCEP protocol used by the Junos OS and NorthStar Controller supports PCEP Extensions for establishing relationships between sets of LSPs (draft-minei-pce-association-group-00) which defines the format and usage of AssociationObject, the optional object that makes association between LSP groups possible. There are later versions of this draft that might be supported by other equipment vendors, which introduces the possibility of mismatch between AssociationObject formats. Such a mismatch could cause non-Juniper PCCs to discard LSP provisioning requests from NorthStar. To prevent this, we recommend that you configure all non-Juniper PCCs to omit AssociationObject altogether.
The result of omitting AssociationObject in non-Juniper PCC configuration is that NorthStar cannot associate groups of LSPs on those devices. For example, you would not be able to associate a primary LSP with secondary LSPs or a primary LSP with standby LSPs. This does not affect NorthStar’s ability to create associations between LSP groups on Juniper PCCs.
Omitting AssociationObject on non-Juniper PCCs involves creating or updating the pcc_version.config (mapping) file on the NorthStar server and restarting the associated PCEP sessions:
- Create/edit the pcc_version.config file on the NorthStar server to include the IP addresses of all
non-Juniper PCCs. For each IP address, specify 3 as the PCC version. PCC version 3 omits AssociationObject.
The IP address should be the PCC IP used to establish the PCEP session. This is the IP address the PCC uses as the local IP address and is the same as appears in the PCC_IP field in the web UI device profile for the device.
The pcc_version.config file is located in
/opt/pcs/db/config/. The syntax of the configuration is ver=ip_address:pcc_version.
[root@northstar]# cat /opt/pcs/db/config/pcc_version.config ver=192.0.2.100:3 ver=192.0.2.200:3
- At the PCEP CLI (pcep_cli command
at the NorthStar Linux shell), execute the set pcc-version command to activate the change in PCC version.
Executing this command restarts the PCEP sessions to the non-Juniper PCCs, applying the new PCC version 3. You can then provision LSPs from the NorthStar UI.