Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Installing the IP/MPLSView Server, Client, Traffic Data Collector, and Rsync Package

 

This procedure describes how to install the default IP/MPLSView servers and clients. The procedure installs the following:

  • The Application Server is the main data processing and simulation server. The default installation settings install the Database, LDAP, and Traffic Data Collector packages on the application server.

  • The Client is the client running on the local server.

  • The Traffic Data Collector is used to distribute the traffic collection.

  • The replication and rsync package is used to keep the files and database on the primary server and a secondary server in sync.

To install the IP/MPLSView servers and clients, follow the steps in the following procedures:

Downloading and Extracting the IP/MPLSView Software

To download and extract the IP/MPLSView software:

  1. Access the Juniper WANDL IP/MPLSView - Download Software page at https://www.juniper.net/support/downloads/?p=wandl#sw. Select the install package. The package name is similar to WANDL IP/MPLS View, version X.X.X, Linux!.
  2. Download the software bundle. The filename is similar to MPLSView_621_Linux_0128_17.tar.gz.
  3. Copy the file to a directory on the server where you want to install IP/MPLSView.
  4. Extract all the files using the following command:

    The extracted files are used by the install script. You are now ready to install the application server using the instructions in this topic.

  5. Some compressed files are also extracted. The compressed files are used to install individual packages such as the client, dcollect, and optionally the replication package on separate servers.

    To extract the compressed files that end in .tar.gz on the target server:

    To extract the compressed files that end in .tar on the target server:

    Exact filenames might vary.

Preparing for Installation

IP/MPLSView Release 6.2.1 and later releases are only supported on 64-bit processors. To verify that your server has a 64-bit processor, use the following command:

Before upgrading IP/MPLSView from a previous installation, ensure that your customer maintenance license has not expired. To verify your license:

$cat /u/wanddb/sys/npatpw

The contents of the npatpw license file varies depending on the type of server you are using. Verify that the date in the maintenance line has not passed, as shown in the sample output.

If you upgrade IP/MPLSView after the customer maintenance license has expired, the upgrade succeeds but you are not be able to access the GUI interface.

If there is a previous IP/MPLSView installation on the machine, switch to the IP/MPLSView admin user (usually this user is wandl) and shut down the existing services before starting a new installation. For example:

If the previous IP/MPLSView installation includes traffic collection, we recommend that you back up the data. Check for sufficient disk space using the following command:

Compress and zip the files using the following command:

The tar h flag is necessary to archive the data pointing to the logical link /u/wandl/data.

Log in as the root user. If you do not have direct access, you can telnet or ssh from a different machine using a non-root user login and then switch to root user using the su command.

If you intend to change the IP address or hostname of the server, you should do this before running the server installation.

  • In some cases, the server has more than one interface: one with an IP address configured for the internal network and another with an IP address configured for the external network. For the server IP address, choose the IP address that can be reached by the client machine(s) from which you plan to access the server, which is usually the external IP address.

  • In other cases, the server IP address is a private NAT IP address, and the client needs to reach it over the public NAT IP address. For more information about setting up the installation to support NAT environments, see Additional Steps for Installing IP/MPLSView in a NAT Environment.

Make sure the hostname points to the IP address that you want to use for the installation so that the installation picks up the correct default IP address. To check this, run a traceroute to the hostname on the server using the following command and verify that the results include the desired IP address:

Before the installation, you should create a user ID and group ID to use for the IP/MPLSView admin. To create a new group ID for the IP/MPLSView admin, use the following command as the root user and substitute the groupname with a name of your choosing:

To create a new user ID named wandl, in the group named staff, with the administrative home directory, or $HOME, set to /home/wandl, for the IP/MPLSView admin, use the following command as the root user:

Create your administrative home directory with the correct ownership and privileges for the administrative user. For example, if the administrative home directory is /home/wandl, use the following two commands to give wandl ownership of the directory, give wandl full privileges, and give other users read and execute privileges:

After adding a new user, create a password (for example, wandl) for the new user using the following command:

Note

If your machine is under your company NIS or NIS+ system, the local root access might not be able to create a new group, or the creation might cause conflicts with the NIS/NIS+ system. In this case, ask the NIS system administrator to create the proper group and add all the users to the group before installing IP/MPLSView.

Starting the Server Installation

The following are general instructions for the installation:

  • File paths are assumed to be under the server directory where you extracted the files.

  • During the installation, press Enter without entering any text to select the default settings.

  • At any time during the installation, you can press Ctrl-c to abort the installation.

To install IP/MPLSView:

  1. Run the installation script as root.

    The system prompts you to continue.

  2. The first required general setting is the Admin User, which defaults to the wandl user. Enter a valid system user ID other than root.

  3. The second required general setting is the Admin Group, which defaults to the group ID of the user ID. If you want to use a different group ID, then enter the new group ID. If this group does not exist, the installation program creates one and asks you to add its members. Please be aware that if a user is currently logged on to the system, the installation program cannot add the user to the group. In this case, you need to contact your system administrator to add all the users into the group.
  4. The third required general setting is the installation directory. Make sure there is sufficient disk space to install the program (approximately 1 GB). The directory is created by the installation program if it does not already exist. At the end of the installation, the /u/wandl/ directory is automatically linked to this directory.Note

    Do not use the operating system partition “/” for the installation directory as this might lead to errors if the partition becomes full. If you are upgrading from an existing installation and are planning to use online features such as traffic data collection, we recommend installing IP/MPLSView in a new installation directory.

  5. The last required general setting is the Data Directory, which is where most of the user data, including the MariaDB database, is stored. Make sure there is sufficient disk space, especially if you plan to run data collection on your network. At the end of the installation, the /u/wandl/ directory is automatically linked to this directory.Note

    If you are upgrading from a previous installation and have previously collected data that you still want to load from IP/MPLSView, enter the complete path for that data directory. To determine that path, use the ls -l /u/wandl/data command. Due to database structural changes, we recommend that you back up the previous data directory. If you do not have any previously collected data, we recommend that you perform a fresh install with a new data directory.

Installation Main Menu Advanced Options

This procedure describes setting advanced installation options. Some of these options can be changed after installation using the /u/wandl/bin/changeconfig.sh script. Changing these settings 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.

  1. After the installation script finishes prompting for required settings, the Main Menu is displayed.
  2. Select (A) Overall Settings to display the following General Administrative Settings:
  3. Select 5.) Email Server IP. The e-mail server IP address is used by certain online functions to send e-mail, such as the Aggregated Traffic Report task, Event Subscription, and the Application Monitor, which provides status notifications regarding IP/MPLSView processes. This IP address can be the IP address of your company’s e-mail server. Your application server should be able to reach this IP address, and your company’s e-mail server might need to be configured accordingly.
  4. To set up your server to send e-mail, edit the /etc/hosts file as follows, and then run the svcadm restart sendmail command or the /etc/init.d/sendmail stop; /etc/init.d/sendmail start command, depending on your environment.

    In this example, it is assumed that the e-mail server is on the same subnet or that there is a route to reach it.

  5. To have the application monitor notify you via e-mail of IP/MPLSView application process status information, such as when processes go down, select 9.) Enable Server Monitoring. This setting allows you to view the application processes monitored by Application Monitor from the Web by selecting Admin > View > System Monitor.
  6. To change the character encoding used by IP/MPLSView in both the Java and Web interface, select 10.) Mapping for non-Unicode characters. This feature might be needed if your data files, for example, configuration files, contain special characters. By default the character encoding is ASCII. To see a list of supported code set names, use the /usr/bin/iconv -l command. When prompted for a new coding, enter the code set name. Note that the code set name is case sensitive.
  7. From the Main Menu, select (B) IP Address. The IP Address menu is displayed.
  8. Select 1.) Webserver IP. Enter the webserver IP address. The webserver IP address is used to access the Web interface. It is usually the same as the server IP address. If the server has more than one interface with different IP addresses, verify that the server IP address used is accessible by the client. For more information, see Preparing for Installation.
  9. Select 2.) LDAP Server IP. The LDAP server IP address is required for IP/MPLSView user administration. Set it to the same address as the server IP address.
  10. Select 3.) External Webserver IP (for NAT). The external webserver IP address is used for special NAT and port forwarding situations. If you have a firewall forwarding internalIP:port to externalIP:port, set the external webserver IP address to the public NAT IP address and enable the option for NAT. For more information, see Additional Steps for Installing IP/MPLSView in a NAT Environment.
  11. Select 4.) Mongo DB IP. Set the address to be the MongoDB local host or remote server IP address.
  12. Select 5.) Use Remote Maria Database. If you want to set up the server environment as a distributed database, set this option to YES. Setting the option to YES installs the MariaDB database on a server other than the IP/MPLSView application server. (see Preparing for Installation.) A menu is displayed with options to set the remote Maria database IP address and port.
  13. Select Remote Maria Database IP. Set this to the IP address of the remote database server.
  14. Select Remote Maria Database Port. Set this to the protocol port of the remote database server.
  15. From the Main Menu, select (C) Memory Settings. The Memory Settings menu is displayed.
  16. Set the memory settings for your server environment.

    You can display how much physical memory (RAM) is available on your server using the more /proc/meminfo command. Some servers might not support more than 2048 MB per process even if the total RAM resources are larger than 2 GB.

    You can display memory usage during operation using the /u/wandl/bin/status_mplsview command.

  17. From the Main Menu, select (D) Port Settings. The Port Settings Server to Client Settings and Port Settings (Advanced) menus are displayed.

    The Port Settings Server to Client Settings menu items 1 through 7 are the required ports to open between the server and client. Generally, you do not need to modify these ports unless they are in conflict with other applications which need to use them or due to special firewall requirements. If the Server, LDAP, or webserver port settings are modified on the server, they also need to be modified on the client. See Required Ports to Open in Firewalls.

    The Port Settings (Advanced) menu items 11 through 14 are the required ports to open when advanced settings are used. Generally, these ports do not need to be modified.

  18. From the Main Menu, select (E) Data Storage Capacity Settings. The Data Storage Capacity Settings menu is displayed.

    The following list describes the data storage capacity settings. Make the appropriate changes for your environment:

    Traffic – LiveSet this to the number of days you want the 5-minute traffic data stored in the MariaDB.
    Traffic – AggregatedSet this to the number of days you want the hourly traffic data, aggregated on a daily basis, stored in the /u/wandl/data/traffic_history directory.
    Traffic – ArchivedSet this to the number of days you want the aggregated traffic stored in the database for daily, weekly, monthly, and yearly reports.
    LDP TrafficSet this to the number of days you want the LDP traffic collected using TaskManager to be stored in the file system.
    LSP TrafficSet this to the number of days you want the LSP traffic collected using TaskManager to be stored in the file system.
    Device and Network – LiveSet this to the number of days you want the device and network performance data to be stored in the file system.
    Device and Network – ArchivedSet this to the number of days you want the device and network performance data aggregated and stored in the database for daily, weekly, monthly, and yearly reports.

    The following list describes the Fault Management Data Max Storage Days settings. Make the appropriate changes for your environment:

    SNMP TrapSet this to the number of days you want the raw SNMP trap to be stored in the /u/wandl/data/trap file.
    Network EventSet this to the number of days you want the network event data to be stored in the database.

  19. From the Data Storage Capacity Settings menu, select 10.) Hardware Inventory. Set this to the number of days you want network event data to be stored in the database.
  20. From the Data Storage Capacity Settings menu, select 11.) User Activity. Set this to the number of days you want the user activity logs to be stored in the database.
  21. From the Main Menu, select (F) Online Fault Management Settings. The Online Fault Management Settings menu is displayed.
  22. Select 1.) SNMP Trap Daemon IP. Set this to the IP address of the IP/MPLSView server which receives traps from network devices. Make sure it is reachable by network devices, and is configured on the network devices as the SNMP target address.
  23. Select 2.) Enable Trap Forwarder. As necessary, enable or disable trap forwarding to a third-party server.
  24. Select 3.) Trap Forwarding Upstream Address. If necessary, set this to the IP address of a third-party NMS supporting JMS to forward traps from IP/MPLSView. Make sure that the IP address is reachable from the IP/MPLSView application server, and that the third party device is listening on port 162 (the default). Additional configuration is also required by selecting Application > Event Subscription Editor. For more information, see the IP/MPLSView Java-Based Management and Monitoring Guide.
  25. Select 4.) Trap Forwarding Upstream Port. If necessary, set this to the protocol port of a third-party server.
  26. Select 5.) Threshold Initial Notification. Enable or disable initial threshold notification.
  27. Select 6.) Background Ping. The background ping allows you to ping all devices in the live network and sends an event to the Event Browser if a device becomes unreachable.

    There is a setting (not part of this installation procedure) that allows you to multi-thread the ping process for faster performance and add additional device profiles not collected in the network. The additional devices appear as an event in the Event Browser when it becomes unreachable. Edit the /u/wandl/db/config/diag.xml file. Within the <DevicePing> tag, you can add <threadcount>integer</threadcount> for multi-thread, and <addprofile>filename</addprofile> for additional device profiles. You can add multiple <addprofile> tags using one tag per profile. The addprofile file format is the same as the Router Profile and must be in the same directory under the /u/wandl/data/.TaskManager/profile/ directory. Changes to the diag.xml file take effect when the network is loaded. For more information, see the IP/MPLSView Java-Based Management and Monitoring Guide.

  28. To enable the distributed remote collection servers, select (G) Advanced Configuration from the Main Menu. The Advanced Configuration menu is displayed.
  29. From the Advanced Configuration menu, select 1.) Distributed Collection Servers. You must also create a file containing a list of IP addresses and ports (IP_address:port) of the remote collection servers. The port is normally 2099.
  30. From the Advanced Configuration menu, select 2.) Database Temp Directory and enter a temporary directory used by the MariaDB server for daily traffic aggregation.
  31. From the Advanced Configuration menu, select 3.) Email Sender Address and enter the e-mail address for task server notifications.

Installing the IP/MPLSView Client on the Local Server

After installing the server, the script prompts you to install the client on the machine.

You can install the client at a later time by running the following script as a non-root user:

To install the client on the local server:

  1. Press Enter or y to continue.
  2. When prompted by the installation script, enter the server name or IP address, port number for communication, the name or IP address of the application server, and the server protocol port number.

Installing the Traffic Data Collector on the Local Server

After installing the client, the script prompts you to install the Traffic Data Collector on the machine.

To install the Traffic Data Collector on the local server:

  1. Press Enter or type y to continue.
  2. When prompted by the installation script, enter the appropriate information.

    If you want to install the Traffic Data Collector on a different system, you can enter N, and then run the /install_dir/dcollect/unix/install.dcollect installation script from the other system. We recommend that you set up one Traffic Data Collector per 100 to 150 devices. When installing the Traffic Data Collector on another system, enter the IP address of the main IP/MPLSView server when prompted for the JMS server.

Installing the Replication and Rsync Package on the Local Server

After installing the Traffic Data Collector, you might be asked if you want to install the replication and Rsync package. The replication and rsync package is used for the IP/MPLSView online functions (data and traffic collection) to keep the files and database on the primary server and a secondary server in sync. The purpose of the package is to have a backup copy in case the primary server fails. The rsync package backs up files from the primary application server to the backup application server, and the replication package updates the secondary database to be in sync with the primary database.

Note

The Replication and Rsync package requires the backup IP/MPLSView server to have a separate license. Additionally, the actual rsync program should be separately installed using the /install_dir/replication/inst_rsync.sh script if it is not already available on the server,

Note

If you want to install the Replication and Rsync package later, then enter N at the prompt. The installation script is also available from the /install_dir/replication/instrepl.sh script. Some prerequisites are required before running the script. The prerequisite steps can be performed from another open telnet or SSH session.