Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Traffic Updates from IP/MPLSView to NorthStar Controller Overview

 

This section describes the following:

Traffic Updates from IP/MPLSView to NorthStar Controller

Juniper Networks IP/MPLSView and Juniper Networks NorthStar Controller are similar in modeling network topology and monitoring network updates. IP/MPLSView has a static topology view and receives network events passively. NorthStar Controller is an SDN controller that enables granular visibility and control of IP/MPLS tunnels in large service provider and enterprise networks. NorthStar can receive traffic statistic updates from IP/MPLSView.

You must have an IP/MPLSView Performance Management license to receive these updates. The Performance Management license allows the router interface data and LSP traffic statistics to be collected, and then sent over the interface to NorthStar Controller. These updates include node and link changes, as well as node and link status.

Figure 1 shows how the router interface data and LSP traffic statistics are exchanged between the IP/MPLSView system to the NorthStar Controller. Advanced Message Queuing Protocol (AMQP) is used for the system-to-system communication.

Figure 1: Traffic Update Architecture for IP/MPLSView to NorthStar
Traffic Update
Architecture for IP/MPLSView to NorthStar

The following list describes interactions among the components in Figure 1:

Base PortsA group of ports used for offline and online networks.
Traffic Data CollectionA performance management subsystem that collects traffic statistics on a periodic basis. The Data Gateway Server (DGS) and the Traffic Data Collectors (TDCs) are the primary application processes involved in collecting and storing the traffic statistics from all routers defined in a traffic collection set of devices. These routers are queried on a regular interval, typically a 5-minute interval. The results of these queries are stored in the traffic collection database by the DGS process. In addition, these traffic results are stored in readable text files in /u/wandl/data/.network.
Traffic Data FilesA data collection accessed and stored in /u/wandl/data/.network/interface.traffic and /u/wandl/data/.network/tunnel.traffic.
NorthStar AMQP Agent An agent that reads the traffic data files on a periodic basis, creates a data structure populated by this data, and sends these structures to the configured NorthStar Controller.
Frequency of Data Transmission to NorthStar ControllerA data transmission that does not require any special configuration of the agent to schedule the publishing of data. You can configure the IP/MPLSView system to collect traffic statistics at different intervals, such as every 5 minutes, 10 minutes, 15 minutes, or longer. The NorthStar AMQP Agent uses this same interval for publishing data to the remote NorthStar Controller.
Threshold ServerA server that creates and updates the interface and tunnel traffic files in /u/wandl/data/.network as part of the overall performance management subsystem.
Application Monitor ServerA server that is responsible for monitoring the various application processes in the IP/MPLSView system. The monitoring functions include a periodic check (once a minute) to ensure that a configured process is running. If the monitored process does not exist (assuming it was previously started), it will automatically restart that process.

System Requirements

For traffic updates from IP/MPLSView to NorthStar Controller, the following system requirements apply:

  • Both IP/MPLSView and NorthStar Controller must be installed.

  • An IP/MPLSView Performance Management license must be installed to receive updates.

NorthStar AMQP Agent

NorthStar AMQP Agent reads the traffic data files on a periodic basis, creates a data structure populated by this data, and sends these structures to the configured NorthStar system. The data is sent at a time interval defined in the Traffic Data Collector subsystem.

You start the NorthStar AMQP Agent by invoking the /u/wandl/bin/.nsamqpagent script when you run the /u/wandl/bin/startup_mplsview script. After the process starts, the following steps are performed:

  1. The agent reads the configuration information in the /u/wandl/db/config/nsamqpagent.config file. This file contains all the necessary access information including the login and password values used to access the remote NorthStar Controller.
  2. The agent connects to the NorthStar Controller using the access credentials described in Step 1.
  3. After successfully connecting, the agent monitors the update to the /u/wandl/data./network/interface.traffic and /u/wand/data/.network/tunnel.traffic files.
  4. When the threshold server posts an update to the interface or tunnel traffic files, the agent reads the contents of these files and formats a data structure that defines the contents.
  5. After constructing the message, the agent sends (publishes) the data to the remote NorthStar Controller.
  6. Step 3 through Step 5 are repeated indefinitely while the agent process is running.

Configuring NorthStar AMQP Agent

The NorthStar AMQP Agent is configured using the /u/wandl/bin/changeconfig.sh script. Changing the settings for the agent requires first stopping IP/MPLSView using the /u/wandl/bin/stop_mplsview command. After the settings have been changed, restart IP/MPLSView using the /u/wandl/bin/startup_mplsview command.

The variables used for configuring the NorthStar AMQP Agent are the values that the agent process uses to access the remote NorthStar Controller. In addition to setting the variables, the changeconfig.sh script also creates and updates the /u/wandl/db/config/nsamqpagent.config file.

Note

If needed, you can run the /u/wandl/bin/changeconfig.sh script to increase the allocated memory size used by the agent process.

Log files are created in the /u/wandl/log directory and the specific log file names are all prefixed with nsamqpagent. Log files can also be accessed from the user interface by selecting Admin > View > Logs.

To configure the NorthStar AMQP Agent:

  1. After the installation script finishes prompting for required settings, the Main Menu is displayed.
  2. Select (H) NorthStar AMQP Settings to display the following settings:
  3. Select 1.) IP Address of NorthStar System. Enter the IP address of the remote NorthStar Controller.
  4. Select 2.) NorthStar System Port. Enter the port number to access the remote NorthStar Controller. The default is 5672.
  5. Select 3.) NorthStar System Username. Enter the user account of the remote NorthStar Controller. The default is northstar.
  6. Select 4.) NorthStar System Password. Enter the encrypted user password of the remote NorthStar Controller.
  7. Select 5.) NorthStar System Exchange Name. Enter the exchange name of the remote NorthStar Controller. The default is controller.wan.stats.

Configuring Additional Attributes

The changes made by using the /u/wandl/bin/changeconfig.sh script provide the ability to change the settings necessary to configure different access credentials to a Northstar Controller. There are some additional attributes available that can only be manually changed in the /u/wandl/db/config/nsamqpagent.config file.

The following output shows an example of a nsamqpagent.config file, and Table 1 describes these attributes that can only be manually changed.

Table 1: Variables for NorthStar AMQP Agent

Config EntryName

Description

Default Value

mq_noconnect

When set to true, the agent process does not connect to the remote NorthStar Controller.

false

Allowed values: true, false

mq_trafficfileset

You can define the type of traffic statistics to send—interface, tunnel, or both.

interface.traffic,tunnel.traffic

Allowed values: One or both of the values.

mq_useipaddr

The agent can send either the name or IP address of the device.

Setting the value to false sends the device name rather than the IP address of the device.

true

Allowed values: true, false

Note

If needed, you can run the /u/wandl/bin/changeconfig.sh script to increase the allocated memory size used by the agent process.

Log files are created in the /u/wandl/log directory and the specific log file names are all prefixed with nsamqpagent. Log files can also be accessed from the user interface by selecting Admin > View > Logs.

Starting or Stopping the NorthStar AMQP Agent

The NorthStar AMQP Agent process is started by using the /u/wandl/bin/startup_mplsview command, which is used to start all of the IP/MPLSView application processes.

To start the NorthStar AMQP Agent:

  1. Run the /u/wandl/bin/startup_mplsview command. (By default, the NorthStar AMQP Agent is not running.)

    The system displays:

    Would you like to start the Northstar AMQP Agent (default=no)? [y/n]

  2. Press Enter or y to continue.

    The startup_mplsview command invokes the /u/wandl/bin/.nsamqpagent start script to start the agent process.

To stop NorthStar AMQP Agent:

  1. Stop NorthStar AMQP Agent using the /u/wandl/bin/.nsamqpagent stop command.Note

    The /u/wandl/bin/stop_mplsview command stops all application processes, including the NorthStar AMQP Agent.