Installing IP/MPLSView in a Distributed Environment
This section describes how to install IP/MPLSView on your application servers and database servers.
Before you install IP/MPLSView, make sure your configuration meets all of the following prerequisites:
In a distributed environment where the database server and the application server are running on separate servers, follow the steps in Installing the Linux Operating System for IP/MPLSView High Availability and Configuring the Linux Operating System for IP/MPLSView High Availability for both the database server and the application server.
Apply all required patches for the network hardware (servers, HBAs, and storage) to the operating system.
Assign the same login ID and password for both the root user and the wandl user on all primary and backup servers.
Enable SSH login services on the servers.
Ensure that you can use SSH to log in to the application servers from the database servers without having to specify a password.
Use the yum –y update command to ensure that all servers have the same patch level installed.
Installing IP/MPLSView on Distributed Application and Database Servers
To install IP/MPLSView on the primary application and primary database servers:
- Make sure the cluster works with IP/GFS2 share. Do this by first failing back and forth to test the Linux high availability performance and reliability.
- Always install the application into a new application
directory such as
/home/wandl/ipmplsview_02_05_15/and place the data into the shared storage GFS2 disk. For example:/data/wandldata/. - Select Node 2 and click Leave Cluster.
Figure 1: Join and Leave Cluster Selections 
- On Node1, start Application-SG with disk and VIP resources enabled only.
- Install the application on the first node from the server directory in the installation package. Run the install script as you do for a standard IP/MPLSView installation without high availability support. Do not start IP/MPLSView.
- Select Node1 and click Leave Cluster.
- Select Node 2 and click Join Cluster.
- On Node2, start the Application-SG with the disk and VIP resources enabled only.
- Install the application on the second node from the server directory in the installation package. Run the install script as you do for a standard IP/MPLSView installation without high availability support. Do not start IP/MPLSView.
- Enable a script resource in the Application-SG Service Group.
- Start on either node (this can take a while once the application is added).
- To test the installation, use the following command on
both servers to verify how long the processes take to bring down and
then restore and compare the results:
#while true; do /u/wandl/bin/status_mplsview; sleep 5; done - Repeat the installation on the backup application server
and backup database server.
Keep the following guidelines in mind when installing IP/MPLSView on your application and database servers:
Store the data in the
/u/wandl/datadirectory in an external storage device that is accessible to both the primary and backup application and database servers.When you configure the IP address settings, change the following parameters to the shared IP address, also known as the virtual IP address (VIP), of the application server to ensure that switchovers on the server do not affect the client application.
Server IP—Change to the shared IP address.
Webserver IP—Change to the shared IP address if you are in a distributed environment and using separate application and database servers.
Mongo DB—Used for the application server only.
Remote Database—Change to the shared IP address if you are using a remote database not hosted by the application server.
The following is an example of the installation script for a typical IP/MPLSView installation.
[root@db1-lha server]# ./install.shPlease read the Getting Started document before installing this software. Note that you can stop the installation at any time using <Ctrl>-c. Preparing to install IP/MPLSView ... Setting soft limit of open files to 65535 for wandl user Setting hard limit of open files to 65535 for wandl user Setting soft limit of open processes to 10240 for wandl user Setting hard limit of open processes to 10240 for wandl user RHEL6 detected, disable huge page saving settings to /etc/rc.local... Changing ipv4/tcp_fin_timeout from 60 to recommanded value 30 Changing ipv4/tcp_keepalive_intvl from 75 to recommanded value 30 Changing ipv4/tcp_keepalive_probes from 9 to recommanded value 5 Changing core/netdev_max_backlog from 1000 to recommanded value 3000 Changing core/somaxconn from 128 to recommanded value 3000 This software requires a Linux ID as the owner. A Linux ID is the login name when you login to this Linux server Please input the IP/MPLSView user ID (wandl): Owner is set to: wandl You should have a group created for all the users who will use this program (a group may have only one member, if only one person uses this program) The installation script will assign the right permissions for the usersof this group to use, update and maintain the programs. Please input group ID (wandl): Group is set to: wandl Please enter the directory where this software will be installed. (default=/home/wandl/ipmplsview): Are you sure you want to install into /home/wandl/ipmplsview (default=yes)? [y/n ] y Checking available disk space ... Please enter the directory where the data will be stored. (default=/home/wandl/wandldata): Are you sure you want to install into /home/wandl/wandldata (default=yes)? [y/n] y Copying Java native library files... Switching user to "wandl" ... Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: a (A) Overall Settings General Administrative Settings for server db1-lha : 1.) Installation Directory.....: /home/wandl/ipmplsview 2.) Data Directory.............: /home/wandl/wandldata 3.) Admin User.................: wandl 4.) Admin Group................: wandl 5.) Email Server IP.......................: 172.25.152.112 6.) Email Server User.....................: wandl 7.) Email Server Password.................: 8.) Application Monitor Email Recipient...: 9.) Enable Server Monitoring..............: OFF 10.) Mapping for non-Unicode characters....: Please select a number to modify. [<CR>=return to main menu]: Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: b (B) IP Address IP/MPLSView Server IP Address Settings: 1.) Webserver IP.......................: 172.25.152.9 2.) LDAP Server IP.....................: 172.25.152.112 3.) External Webserver IP (for NAT)....: 4.) Mongo DB IP........................: 127.0.0.1 5.) Use Remote Database...............: NO Please select a number to modify. [<CR>=return to main menu]: Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: c (C) Memory Settings 1.) Task Manager Memory....................: 256 2.) Webserver Memory.......................: 1024 3.) Thrift Server Memory...................: 256 4.) HornetQ Memory.........................: 256 5.) DGS Memory.............................: 512 6.) Application Monitor Memory.............: 128 7.) Threshold Server Memory................: 256 8.) SNMP Trap Daemon Memory................: 128 9.) MongoDB Memory.........................: 512 10.) Event Server Memory....................: 256 11.) Aggregation Memory.....................: 1024 12.) Selective Interface Manager Memory.....: 256 13.) Maria Database Memory........................: 256 Total system physical memory: 32081 MB After starting IP/MPLSView, check "/u/wandl/bin/status_mplsview" to see the actual memory usage, which can be used to tune the memory settings. Please select a number to modify. [<CR>=return to main menu]: Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: d (D) Port Settings 1.) Server Port..........: 7000 2.) LDAP Server Port.....: 3389 3.) Webserver Port.......: 8091 4.) SSL Port........: 8443 SSL Domain......: Unknown SSL Department..: Unknown SSL Organization: Unknown SSL Loc./City...: Unknown SSL State/Prov..: Unknown SSL Country.....: United States,us 5.) Task Manager Primary Port...: 2099 6.) HornetQ Port................: 1856 7.) Thrift Server Port..........: 7911 Please select a number to modify. [<CR>=return to main menu]: Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: d (D) Port Settings (Advanced) 11.) SNMP Trap Daemon Port.............: 162 12.) Event Post Port...................: 7077 13.) MariaDB Database Port.............: 3333 10.) MongoDB Application Server Port...: 27017 Please select a number to modify. [<CR>=return to main menu]: Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: f (F) Online Fault Management Settings SNMP Trap Settings: 1.) SNMP Trap Daemon IP................: 172.25.152.112 2.) Enable Trap Forwarder..............: OFF 3.) Trap Forwarding Upstream Address...: 4.) Trap Forwarding Upstream Port......: Event Settings: 5.) Threshold Initial Notification...: OFF Main Menu Server Configuration Settings: (A) Overall Settings (B) IP Address (C) Memory Settings (D) Port Settings (E) Data Storage Capacity Settings (F) Online Fault Management Settings (G) Advanced Configuration (H) NorthStar AMQP Settings Please select a number to modify. [<CR>=accept, q=quit]: (A) Overall Settings General Administrative Settings for server db1-lha : 1.) Installation Directory.....: /home/wandl/ipmplsview 2.) Data Directory.............: /home/wandl/wandldata 3.) Admin User.................: wandl 4.) Admin Group................: wandl 5.) Email Server IP.......................: 172.25.152.17 6.) Email Server User.....................: wandl 7.) Email Server Password.................: 8.) Application Monitor Email Recipient...: 9.) Enable Server Monitoring..............: OFF 10.) Mapping for non-Unicode characters....: (B) IP Address IP/MPLSView Server IP Address Settings: 1.) Webserver IP.......................: 172.25.152.17 2.) LDAP Server IP.....................: 172.25.152.17 3.) External Webserver IP (for NAT)....: 4.) Mongo DB IP........................: 127.0.0.1 5.) Use Remote Database...............: NO Note the web server should be changed to the shared VIP address. (C) Memory Settings 1.) Task Manager Memory....................: 256 2.) Webserver Memory.......................: 1024 3.) Thrift Server Memory...................: 256 4.) HornetQ Memory.........................: 256 5.) DGS Memory.............................: 512 6.) Application Monitor Memory.............: 128 7.) Threshold Server Memory................: 256 8.) SNMP Trap Daemon Memory................: 128 9.) MongoDB Memory.........................: 512 10.) Event Server Memory....................: 256 11.) Aggregation Memory.....................: 1024 12.) Selective Interface Manager Memory.....: 256 13.) Maria Database Memory........................: 256 Total system physical memory: 32081 MB After starting IP/MPLSView, check "/u/wandl/bin/status_mplsview" to see the actual memory usage, which can be used to tune the memory settings. ((D) Port Settings 1.) Server Port..........: 7000 2.) LDAP Server Port.....: 3389 3.) Webserver Port.......: 8091 4.) SSL Port........: 8443 SSL Domain......: Unknown SSL Department..: Unknown SSL Organization: Unknown SSL Loc./City...: Unknown SSL State/Prov..: Unknown SSL Country.....: United States,us 5.) Task Manager Primary Port...: 2099 6.) HornetQ Port................: 1856 7.) Thrift Server Port..........: 7911 (D) Port Settings (Advanced) 11.) SNMP Trap Daemon Port.............: 162 12.) Event Post Port...................: 7077 13.) MariaDB Database Port.............: 3333 10.) MongoDB Application Server Port...: 27017 (F) Online Fault Management Settings SNMP Trap Settings: 1.) SNMP Trap Daemon IP................: 172.25.152.112 2.) Enable Trap Forwarder..............: OFF 3.) Trap Forwarding Upstream Address...: 4.) Trap Forwarding Upstream Port......: Event Settings: 6.) Threshold Initial Notification...: OFF (G) Advanced Configuration Advanced Configuration Settings: 1.) Distributed Collection Servers........: 2.) Database Temp Directory...............: /home/wandl/wandldata/mysql/tmp 3.) Email Sender Address..................: Accept these values (default=no)? [y/n] y Install Client (default=yes)? [y/n] y Install Data Collector (default=yes)? [y/n] y Install Rsync & Database Replication Package (default=no)? [y/n] n You may install the Rsync & Database Replication Package by running /u2/NPAT6.2.0/current.mpls/replication/instrepl.sh no crontab for wandl no crontab for wandl Extracting server files (this may take some time) ................... Done! Installing webserver ... Done! Creating database files for installation...Done. Analyzing database tables for upgrade...Done. Creating database tables ... Done. Upgrading database tables...Done. Creating symbolic links ... Done! Creating event repository ... Done! Relinking files ... Done! Installing client ... Done! Installing data collector... Configure Data Collectors for Selective Interface (default=no)?[y/n]: n no crontab for wandl Data collector crontab entries added successfully. Done! Configuration file:'/home/wandl/ipmplsview/bin/mplsenvsetup.sh' was created on Thu Jun 4 06:23:31 EDT 2015 Creating Webserver configuration files ... Done! Creating Diagnostics configuration files ... Done! Creating Event Model configuration files ... Done! Creating Traffic Summary configuration files ... Done! Creating DGS configuration files ... Done! Creating Event Server configuration files ... Done! Creating Monitor configuration files ... Done! Creating IP/MPLSView Application Monitor configuration files ... Done! Creating Task Manager Configuration files ... Done! Configuring Task Manager native library files... Done! Creating Selective Interface Manager configuration files ... Done! Creating database files ... Done! Creating MongoDB files ... Done! Creating LDAP files ... Done! Initializing LDAP directory ... Done! Creating Data Collector configuration files ... Done! You may start the client by running the following command: /home/wandl/ipmplsview/client/ipmplsview Remember to start the server before starting the client You may start the Data Collector by running the following commands: cd /home/wandl/ipmplsview/dcollect ./dc.sh start 0 Successfully created a symbolic link from /u/wandl to /home/wandl/ipmplsview. Please copy your license file to /home/wandl/ipmplsview/db/sys/npatpw. If you do not have a license file, please contact Juniper Technical Assistance Center (JTAC). After activating the software, you may start the IP/MPLSView server by running the following command: /home/wandl/ipmplsview/bin/startup_mplsview