[VIDEO] - Step By Step Guide To Install NSM 2009 On RHEL 5

Posted by Ahsan Tasneem | 4:31 AM | , , , , , | 1 comments »

I have just completed the installation of nsm20091r1 on RHEL(Redhat) 5 with the help of this tutorial, but there were also some additional steps done by me that are not mentioned in this tutorial. All the additional steps are also added in the tutorial below
Within this tutorial we will be installing Juniper NSM 2009.1 onto a RHEL (Redhat) 5 server.
                           Click Here To Play The Installation Video
Below describes the steps within the above video :

Transfer FilesCopy the required files across to your server. These files are : nsm2009.1r1-systemupdate-linux.zip & nsm2009.1r1_servers_linux_x86.zip.
You will also need to ensure you have rsync and unzip installed.

Update your server
To ensure that the NSM has all the required dependencies installed you will need to update you server by running the update package. This is done by unzipping the zip, untar`ing the tarball and running the install script.

Change Kernel Settings
The following kernel setting will need to be set "kernel.shmmax = 402653184". This change can be done by running the following line :

sed -i 's/kernel\.shmmax.*$/kernel\.shmmax = 402653184/g' /etc/sysctl.conf
Once done you will need to reboot your system.

Install NSM Software

Unzip the install package and then run the install script. Once installed you can run log into the NSM GUI and import your firewall device. This is outside the scope of this article.

Please Note : Within the video tutorial the sections where no input appears to be entered the default setting (value with sqaure [#] brackets) is being used by just pressing the enter key.

Problem Faced While Installations & Their Solutions

Problem1:
Some users might face some problem while installation of nsm2009.1r1_servers_linux_x86.sh as shown in the example below, this issue can be resolved by changing the transfer mode from ASCII to binary (We also faced the same problem while using WinSCP, finally the issue was resolved when the file transfer was done after changing the mode from ASCII to binary in WinSCP)

# sh nsm2009.1r1_servers_linux_x86.sh
Extracting payload....
Decompressing payload....
/bin/tar: Skipping to next header
/bin/tar: Archive contains obsolescent base-64 headers
gzip: payload.tgz: invalid compressed data--format violated
/bin/tar: Error exit delayed from previous errors
FAILED

Resolution: This error usually occurs when a file is transferred over to the server in ASCII mode. To resolve the issue, transfer the file over to the server again; this time in the binary mode. The best practice is to uncompress the file on the server which also helps to verify file integrity.

Problem 2:
Once the file nsm2009.1r1_servers_linux_x86.sh is transfered to redhat server, some user might not be able to run the file

# sh nsm2009.1r1_servers_linux_x86.sh
error while executing ...

Resolutions: This can be resolve by just changing the mode of the file 

# chmod 777 nsm2009.1r1_servers_linux_x86.sh

Note:  If you are installing the UI on RHEL 5, first install the “libXp” package.
You can obtain libXp from RedHat.




Courtesy: Fir3net.com

1 comments

  1. Anonymous // June 12, 2012 at 4:23 PM  

    I am really thankful to the holder of this site
    who has shared this enormous paragraph at at this time.
    Look at my web-site ... KFZ Versicherung Rechner nutzen auf www.kfzversicherungsvergleich1.org

Related Posts Plugin for WordPress, Blogger...