Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

NorthStar Controller System Requirements

 

You can install the NorthStar Controller in the following ways:

  • Installation on a physical server

  • Two-VM installation in an OpenStack environment (JunosVM is not bundled with the NorthStar Controller software)

Before you install the NorthStar Controller software, ensure that your system meets the requirements described in Table 1.

Table 1: Hardware Requirements for NorthStar Servers

Server Type

RAM

HDD

Core Processor

Host must support hardware virtualization (VT-d)

NorthStar Application Only

48 GB

500 GB

Intel i5/i7

Yes

NorthStar Application with Analytics

64 GB

1.5 T

Intel i5/i7

Yes

Analytics Only

32 GB

1 T

Intel i5/i7

No

In addition to the hardware requirements, ensure that:

  • When upgrading NorthStar Controller, the /tmp directory has enough free space to save the contents of the /opt/pcs/data directory because the /opt/pcs/data directory contents are backed up to /tmp during the upgrade process.

  • You use a supported version of CentOS Linux or Red Hat Enterprise Linux. These are our Linux recommendations:

    • CentOS Linux 6.8, 6.9, or 7.2 image–earlier CentOS versions are not supported

    • Red Hat Enterprise Linux 6.8, 6.9, or 7.2

    • Install your choice of supported Linux version using the minimal ISO

    CentOS can be downloaded from https://www.centos.org/download/.

  • The ports listed in Table 2 are allowed by any external firewall being used. The ports with the word cluster in their purpose descriptions are associated with high availability (HA) functionality. If you are not planning to configure an HA environment, you can ignore those ports. The ports with the word Analytics in their purpose descriptions are associated with the Analytics feature. If you are not planning to use Analytics, you can ignore those ports. The remaining ports listed must be kept open in all configurations.

    Table 2: Ports That Must Be Allowed by External Firewalls

    Port

    Purpose

    22

    SSH daemon

    179

    JunosVM for router BGP-LS—not needed if IGP is used for topology acquisition

    4189

    PCC (router) to NorthStar PCE server

    7000

    Communications port to NorthStar Planner

    7003

    Communications port to NorthStar Operator

    7004

    Communications port to NorthStar Operator (view only)

    8091

    Web client/REST to webserver (http)

    8443

    Web client/REST to secure webserver (https)

    830

    Netconf communication between NorthStar Controller and routers

    7001

    Cassandra database cluster

    7199

    Cassandra database cluster

    9042

    Cassandra client port

    17000

    Cassandra database cluster

    5672

    Rabbitmq

    NorthStar application servers must allow incoming traffic to this port. Analytics nodes must allow outgoing traffic to this port.

    4369

    Rabbitmq cluster

    25672

    Rabbitmq cluster

    35197

    Rabbitmq cluster

    2888, 3888

    Zookeeper cluster

    1514

    Default Junos Telemetry Interface reports for RPM probe statistics (supports Analytics)

    2000

    Default Junos Telemetry Interface reports for IFD (supports Analytics)

    2001

    Default Junos Telemetry Interface reports for IFL (supports Analytics)

    2002

    Default Junos Telemetry Interface reports for LSP (supports Analytics)

    6379

    Redis

    9200

    Elasticsearch

Note

Sample iptable rules are available in /opt/northstar/utils/firewall.sh on the NorthStar application server.

Analytics Requirements

In addition to ensuring that ports 2000, 2001, 2002, and 1514 are kept open, using the NorthStar analytics features requires that you counter the effects of Reverse Path Filtering (RPF) if necessary. If your kernel does RPF by default, you must do one of the following to counter the effects:

  • Disable RPF.

  • Ensure there is a route to the source IP address of the probes pointing to the interface where those probes are received.

  • Specify loose mode reverse filtering (if the source address is routable with any of the routes on any of the interfaces).

Two-VM Installation Requirements

A two-VM installation is one in which the JunosVM is not bundled with the NorthStar Controller software.

Disk and Memory Requirements

The disk and memory requirements for installing NorthStar Controller in an OpenStack or other hypervisor environment are described in Table 3.

Table 3: Disk and Memory Requirements for NorthStar OpenStack Installation

VM

Virtual CPU

Virtual RAM

Disk Size

Virtual NIC

NorthStar Application VM

4

32 GB

100 GB

2 minimum

NorthStar-JunosVM

1

4 GB

20 GB

2 minimum

VM Image Requirements

  • The NorthStar Controller application VM is installed on top of a Linux VM, so Linux VM is required. You can obtain a Linux VM image in either of the following ways:

    • Use the generic version provided by most Linux distributors. Typically, these are cloud-based images for use in a cloud-init-enabled environment, and do not require a password. These images are fully compatible with OpenStack.

    • Create your own VM image. Some hypervisors, such as generic DVM, allow you to create your own VM image. We recommend this approach if you are not using OpenStack and your hypervisor does not natively support cloud-init.

  • The JunosVM is provided in Qcow2 format when inside the NorthStar Controller bundle. If you download the JunosVM separately (not bundled with NorthStar) from the NorthStar download site, it is provided in VMDK format.

  • The JunosVM image is only compatible with IDE disk controllers. You must configure the hypervisor to use IDE rather than SATA controller type for the JunosVM disk image.

    glance image-update --property
    hw_disk_bus=ide --property
    hw_cdrom_bus=ide

JunosVM Version Requirements

By default, the NorthStar Controller Release 3.0.0 and later requires that the external JunosVM be Release 17.2 or later. If you are using an older version of Junos OS, you can change the NorthStar configuration to support it, but segment routing support will not be available. See Installing the NorthStar Controller 3.1.0 for the configuration steps.

VM Networking Requirements

The following networking requirements must be met for the two-VM installation approach to be successful:

  • Each VM requires the following virtual NICs:

    • One connected to the external network

    • One for the internal connection between the NorthStar application and the JunosVM

    • One connected to the management network if a different interface is required between the router facing and client facing interfaces

  • We recommend a flat or routed network without any NAT for full compatibility.

  • A virtual network with one-to-one NAT (usually referenced as a floating IP) can be used as long as BGP-LS is used as the topology acquisition mechanism. If IS-IS or OSPF adjacency is required, it should be established over a GRE tunnel.

    Note

    A virtual network with n-to-one NAT is not supported.

Deployment Scenarios

Table 4 lists the supported deployment configurations by NorthStar release.

Table 4: Supported NorthStar Deployment Configurations by Release Number

Deployment

Configuration

Features Available

NorthStar Release 3.0.0

Features Available

NorthStar Release 3.1.0

Description:

  • NorthStar application (no Analytics, no HA)

Number of Servers:

  • NorthStar: 1

  • Total: 1

  • PCEP provisioning

  • NETCONF device collection

  • PCEP and NETCONF provisioning

  • NETCONF device collection

Description:

  • NorthStar application and Analytics, both installed in a single server

  • One or more optional slave collector servers

Number of Servers:

  • NorthStar + Analytics: 1

  • Total: 1

  • Total with optional slave collector servers: 2 or more

  • PCEP provisioning

  • NETCONF device collection

  • Telemetry

  • (Slave collectors not supported in this release)

  • PCEP and NETCONF provisioning

  • NETCONF device collection

  • Telemetry

  • Data Collection:

    • SNMP

    • Link latency

  • (Slave collectors not supported in this release)

Description:

  • NorthStar application and Analytics, each installed in a separate server

  • One or more optional slave collector servers

Number of servers:

  • NorthStar: 1

  • Analytics: 1

  • Total: 2

  • Total with optional slave collector servers: 3 or more

  • PCEP provisioning

  • NETCONF device collection

  • Telemetry

  • (Slave collectors not supported in this release)

  • PCEP and NETCONF provisioning

  • NETCONF device collection

  • Telemetry

  • Data Collection:

    • SNMP

    • Link latency

  • (Slave collectors not supported in this release)

Description:

  • NorthStar application HA

Number of servers:

  • NorthStar: minimum of 3 (odd numbers only)

  • Total: 3 or more

  • PCEP provisioning

  • NETCONF device collection

  • NorthStar HA

  • PCEP and NETCONF provisioning

  • NETCONF device collection

  • NorthStar HA

Description:

  • NorthStar application HA and separate, single Analytics server

  • One or more optional slave collector servers

Number of servers:

  • NorthStar: minimum of 3 (odd numbers only)

  • Analytics: 1

  • Total: 4 or more

  • Total with optional slave collector servers: 5 or more

  • PCEP provisioning

  • NETCONF device collection

  • NorthStar HA

  • Telemetry

  • (Slave collectors not supported in this release)

  • PCEP and NETCONF provisioning

  • NETCONF device collection

  • NorthStar HA

  • Telemetry

  • Data Collection:

    • SNMP

    • Link latency

  • (Slave collectors not supported in this release)

Description:

  • Single NorthStar application server and Analytics HA

  • One or more optional slave collector servers

Number of servers:

  • NorthStar: 1

  • Analytics: minimum of 3 (odd numbers only)

  • Total: 4 or more

  • Total with optional slave collector servers: 5 or more

  • PCEP provisioning

  • NETCONF device collection

  • Analytics HA

  • Telemetry

  • (Slave collectors not supported in this release)

  • PCEP and NETCONF provisioning

  • NETCONF device collection

  • Analytics HA

  • Telemetry

  • Data Collection:

    • SNMP

    • Link latency

  • (Slave collectors not supported in this release)

Description:

  • NorthStar application HA and separate Analytics HA

  • One or more optional slave collector servers

Number of servers:

  • NorthStar: minimum of 3 (odd numbers only)

  • Analytics: minimum of 3 (odd numbers only)

  • Total: 6 or more

  • Total with optional slave collector servers: 7 or more

  • PCEP provisioning

  • NETCONF device collection

  • NorthStar HA

  • Analytics HA

  • Telemetry

  • (Slave collectors not supported in this release)

  • PCEP and NETCONF provisioning

  • NETCONF device collection

  • NorthStar HA

  • Analytics HA

  • Telemetry

  • Data Collection:

    • SNMP

    • Link latency

  • (Slave collectors not supported in this release)

Description:

  • NorthStar application HA sharing servers with Analytics HA.

  • One or more optional slave collector servers

Number of servers:

  • NorthStar + Analytics: minimum of 3 (odd numbers only)

  • Total: 3 or more

  • Total with optional slave collector servers: 4 or more

Not supported

Not supported