Help Center User GuideGetting StartedFAQRelease Notes
 
X
User Guide
Getting Started
FAQs
Release Notes
Contents  

Installation and Upgrade Instructions


This section contains the procedures to upgrade Junos Space Security Director and Log Collector.

Installing Junos Space Network Management Platform

Junos Space Security Director Release 16.2R1 is supported only on Junos Space Network Management Platform Release 16.1R2. For more information on the Network Management Platform upgrade process, see Upgrading to Junos Space Network Management Platform Release 16.1R1.

At the end of the installation, you are prompted to choose the backup tgz location to restore the previous version of the Network Management Platform release. Click N to continue with the fresh installation of the Network Management Platform.

Installing Security Director Release 16.2R1

In Junos Space Security Director Release 16.2R1 a single image installs Security Director, Log Director, and the Security Director Logging and Reporting modules. Installing the Security Director Release 16.2R1, image installs all three applications. You must deploy the Log Collector and then add it to the Junos Space Network Management Platform fabric to view the log data on the Dashboard, Events and Logs, Reports, and Alerts pages.

For more information on adding Junos Space applications, see Adding a Junos Space Application.

Upgrading Security Director Prerequisites

Before you upgrade the Security Director, Log Director, and Security Director Logging and Reporting modules, you must upgrade to Junos Space Network Management Platform Release 16.1R2.

Table 1 shows the upgrade sequence if your current Security Director release is earlier than Security Director Release 15.2.

Table 1: Upgrade Sequence

Junos Space Network Management Platform Release

Security Director Release

15.2R1

15.2R1

15.2R2

15.2R2

16.1R1

16.1R1

16.1R2

16.2R1

Upgrading Security Director

Note: If you are upgrading from a previous version of Security Director, clear your browser cache before accessing the Security Director UI.

To upgrade from a previous version of Security Director to Security Director Release 16.2R1:

Note: In Junos Space Security Director Release 16.2R1, all IPS report definitions are consolidated into a single report definition called IPS Report. After upgrading Security Director to 16.2R1, IPS reports for already scheduled IPS report definitions will not be generated because, the individual IPS report definitions does not exist. You must use the consolidated IPS report.

Upgrading Log Collector VM and Integrated Log Collector

Note: Before creating a backup of Log Collector Release 15.2R2, you must delete all the Log Collector nodes from Security Director > Administration > Logging Management > Logging Nodes.

Table 2 shows the topology difference between Log Collector Releases 15.2R2, 16.1R1, and 16.2R1 before the upgrade.

Table 2: Understanding the Topology Difference Before Upgrading

Node Type

15.2R2

16.1R1

16.2R1

All-in-One

Yes

Yes

Yes

Log receiver

Yes

Yes

Yes

Log storage

Yes (Log Indexer node and Log Data node)

Yes

Yes

Query node

Client node

Yes (20K eps)

No

No

Master node

Cluster Manager node

Yes (20K eps)

No

No

Integrated

No

Yes

Yes

In Log Collector Release 16.2R1:

To upgrade from Log Collector Release 16.1R1 to Log Collector Release 16.2R1:

  1. If the log password was changed for the logging nodes in Log Collector Release 15.2R2, perform the following steps. Otherwise, continue to Step 2.
    • Use the ssh command to open a connection to Log Query node (Indexer node) or All-in-One node.
    • Edit the elasticsearch.yml file, located at vi/etc/elasticsearch/.
    • In the elasticsearch.yml file, search for http.basic.password and replace the changed password with 58dd311734e74638f99c93265713b03c391561c6ce626f8a745d1c7ece7675fa.
    • Save the changes.
  2. Download the Log Collector upgrade script from here.
  3. Copy the upgrade script to the /root path of all the applicable nodes that you want to upgrade.
  4. Run the sh Log-Collector-Upgrade-16.2R1.XXX script.

    The status of the upgrade is shown on the console.

    Note:

    • The Logstash process does not run on the log receiver node any longer. Instead the jingest process will run.
    • You must ensure that the jingest and elasticsearch processes are running.
  5. Add the logging nodes back to Security Director from Security Director > Administration > Logging Management > Logging Nodes.

Upgrading Integrated Log Collector

To upgrade from integrated Log Collector Release 16.1R1 to integrated Log Collector Release 16.2R1:

Procedure

  1. Download the integrated Log Collector image Integrated-Log-Collector-16.2.R1.xxx.sh from here.
  2. Copy the integrated Log Collector script to a JA2500 appliance or virtual appliance.
  3. Connect to the CLI of a JA2500 appliance or virtual appliance with admin privileges.
  4. Navigate to the location where you have copied the integrated Log Collector script.
  5. Install the integrated Log Collector script using the following command: sh Integrated-Log-Collector-16.2.R1.xxx.sh.

    The integrated Log Collector is successfully upgraded to Log Collector Release 16.2R1.

Deploying Log Collector

System Requirement

Table 3 and Table 4 provide the virtual machine (VM) configuration that is recommended for the log collection to work effectively.

Table 3: With SSD Drives

Setup

Number of Nodes

(Log Receiver Nodes)

CPU

(Log Receiver Nodes)

Memory

(Log Receiver Nodes)

Number of Nodes

(Log Storage Nodes)

CPU

(Log Storage Nodes)

Memory

(Log Storage Nodes)

Total Nodes

4K events per second (eps)

1

4

16 GB

-

-

-

1

10K eps

1

8

32 GB

1

8

64 GB

2

20K eps

1

8

32 GB

2

8

64 GB

3

Table 4: With Non-SSD Drives

Setup

Number of Nodes

(Log Receiver Nodes)

CPU

(Log Receiver Nodes)

Memory

(Log Receiver Nodes)

Number of Nodes

(Log Storage Nodes)

CPU

(Log Storage Nodes)

Memory

(Log Storage Nodes)

Total Nodes

3K eps

1

4

16 GB

-

-

-

1

10K eps

1

8

32 GB

2

8

64 GB

3

20K eps

1

8

32 GB

3

8

64 GB

4

Note: VMs with 64-GB memory provides better stability for the log collection.

Table 5 includes supported node types in which the Log Collector can be deployed.

Table 5: Log Collector Deployment Nodes

Node Type

Description

All-in-One node (combined deployment)

  • Both receiver and storage nodes run on the same VM or JA2500 appliance.
  • Supports up to 3000 eps with spinning disks and 4000 eps with SSD drives.
  • Suitable for demos and small-scale deployments.

Log Receiver node (Distributed deployment)

This node receives syslogs from SRX Series devices. SRX Series devices must be configured with the Log Receiver node IP address to send syslogs. Upon configuration, this node parses and forwards logs to the Log Storage Node. You must provide the IP address of the Log Storage node while configuring this node.

Log Storage node (Distributed deployment)

This node analyzes, indexes, and stores syslogs. It receives the syslogs from Log Receiver node.

Note: You cannot edit the settings of virtual machines using hardware version 10 or earlier, using vSphere Client version 5.5 or earlier. For more details, see VMware Knowledge Base.

Storage Requirements

The total storage required for retaining X number of days at a given eps rate is:

eps * 0.155 * X = (in GB)

For example, the storage requirement for 7 days at 500 eps is 500 * 0.155 * 7 = 542 GB, with a +20% margin. The storage space is allocated and equally distributed to the Log Indexer nodes.

Note: The logs are rolled over in the following scenarios:

  • Time-based rollover—Logs that are older than 45 days are automatically rolled over, even if the disk space is available.
  • Disk size-based rollover—Older logs are rolled over when the disk size reaches 400 GB.

Deploying Log Collector VM on a KVM Server

Procedure

Before You Begin

Before You Begin

The prerequisites to deploy a Log Collector on a KVM server are as follows:

  • Knowledge about configuring and installing a KVM server.
  • The KVM server and supported packages must be installed on a machine running CentOS with the required kernels and packages. See http://wiki.centos.org/HowTos/KVM.
  • The Virtual Machine Manager (VMM) client must be installed on your local system.
  • The bridge interface must be configured according to your environment and you must have at least two static IP addresses that are unused.

Note: You can deploy the Log Collector virtual appliance on a KVM server by using virtual machine clients other than VMM. However, Juniper Networks does not provide support for installing the Junos Space virtual appliance using clients other than VMM.

To deploy Log Collector virtual machine (VM) on a KVM server:

  1. Download the Log Collector KVM image from the Download Site on the KVM host and extract the tgz file, which contains the system.qcow2 and data.qcow2 files.
  2. Launch the VMM client by typing virt-manager from your terminal or you can search from the System Tools menu.
  3. Select File > New Virtual Machine to install a new virtual machine.

    The new VM dialog box appears and displays Steps 4 to 8.

  4. Select Import existing disk image and click Next.
  5. Click Browse and then select the system.qcow2 file.
  6. Select Linux as the operating system and the versions as Red Hat Enterprise Linux 6.6 or later.
  7. Click Forward.
  8. Set CPU settings as 4, and then select or enter the memory (RAM) value as 16,384 MB (minimum).
  9. Click Forward.
  10. Edit the Name field, select or set up the network for each bridge or interface configured, and select the Customize Configuration Before Install option.
  11. Click Finish.
  12. Select the Storage option from the left navigation on the Add New Virtual Hardware window, and then click Add Hardware.
  13. On the Storage window:
    • Select Select managed or other existing storage and choose the data.qcow2 file.
    • Select the storage format as qcow2 under Advanced Options.
    • Click Finish.
  14. Click Begin Installation to start the Log Collector VM.
  15. After the installation, you can configure the IP address, name server, and time zone.

Add Log Collector Node to Security Director

To add Log Collector to Security Director, see Adding Log Collector to Security Director.

Deploying Log Collector VM on an ESX Server

Procedure

To deploy the Log Collector on an ESX server:

  1. Download the latest Log Collector open virtual appliance (OVA) image.
  2. Using vSphere or vCenter, deploy the Log Collector OVA image Log-Collector-16.21R1.ova onto the ESX server.
  3. Edit the CPU and memory as per the system requirement for the required events per second (eps).

    Note: Log Collector virtual machine (VM) contains a Virtual Appliance Management Infrastructure (VAMI) agent. The agent enables the VM to use the required server configuration from the ESX server.

  4. Power on the Log Collector VM.

    A configuration script lets you choose the node type and configure the network settings.

  5. Use the default credentials to log in to Log Collector. The username is root and the password is juniper123
  6. Change the root password of the VM.
  7. Deploy Log Collector as the desired node.
  8. Configure your network settings.

Add Log Collector Node to Security Director

To add Log Collector to Security Director, see Adding Log Collector to Security Director.

Installing Log Collector on the JA2500 Appliance Using a USB Flash Drive

To install the Log Collector on the JA2500 appliance using a USB flash drive, you must create a bootable USB flash drive, install the Log Collector node using the USB flash drive, and add the Log Collector node to Security Director.

Create a Bootable USB Flash Drive

Procedure

Before creating a bootable USB flash drive, download and install the Rufus utility on your system.

  1. Plug the USB storage device into the USB port of a laptop or PC.
  2. Download the Log collector ISO image from here.

Procedure

If you are using a computer with Microsoft Windows as the operating system, follow these steps to create a bootable USB flash drive:

  1. Open the Rufus utility installed on your computer.

    The Rufus window opens.

  2. From the Device list, select the USB storage device.
  3. In the Format Options section, select the ISO image downloaded in Step 2. To select the ISO image, click the open or browse icon next to the Create a bootable disk using option.
  4. Click Start.

    A progress bar on the Rufus page indicates the status of the bootable USB flash drive. A success message is displayed once the process completes successfully.

  5. Click Exit to exit the window.
  6. Eject the USB storage device and unplug it from the computer.

Procedure

If you are using a computer with Linux as the operating system, follow these steps:

Note: While you can use any of the available tools, we recommend that you use the dd command in Linux to create a bootable USB drive.

  1. Open a shell prompt.
  2. Use the cd command to navigate to the directory containing the software image file.
  3. Type the [user@host ~]$ dd if=Log-collector-version.spinnumber.img of=/dev/usb-drive command to copy the image file to the USB drive and press Enter.

    Log-Collector-version.spin-number.img is the name of the downloaded Junos Space image file, and /dev/usb-drive is the name of the device drive to which your USB drive is mapped. The image file is copied to the USB drive and you are directed to the command prompt.

  4. Eject the USB drive and unplug it from the computer.

Install Log Collector Using USB Flash Drive

Procedure

  1. Plug the USB storage device into the USB port of the JA2500 appliance.
  2. Follow these steps to access the JA2500 appliance boot menu:

    Procedure

    1. Power on the JA2500 appliance.
    2. As the JA2500 appliance powers on, press the key mapped to send the DEL character in the terminal emulation utility.

      Note: Typically, the Backspace key is mapped to send the DEL character.

    3. The boot menu appears after a few minutes.
  3. Ensure that the USB boot is at the top of the appliance boot-priority order.

    If USB KEY: CBM USB 2.0 - (USB 2.0) is not at the top of the list, follow these steps:

    1. Use the Down Arrow key to select USB KEY:CBM USB 2.0- (USB 2.0), and use the + key to move the entry to the top of the list.
    2. Press the F4 key to save your changes and exit the BIOS setup.
  4. Verify the BIOS setting, and then power off the JA2500 appliance.
  5. Power on the appliance again. The boot menu displays the following options:
    1. Install Log Collector on Juniper JA2500 Hardware
    2. Boot from local drive
  6. Select Install Log Collector on Juniper JA2500 Hardware.
  7. Power off the appliance once the installation is completed.
  8. Restart the appliance and select Boot from local drive.
  9. Use the default credentials to log in to the JA2500 appliance; username is root and password is juniper123.
  10. Change the default root password when prompted.
  11. After logging in, select the desired node type.
  12. Configure the IP address and gateway.
  13. Configure settings for the DNS name server and the NTP server.

Add Log Collector Node to Security Director

To add Log Collector to Security Director, see Adding Log Collector to Security Director.

Installing Integrated Log Collector on a JA2500 Appliance or Junos Space Virtual Appliance

Before You Begin

The prerequisites to install the integrated Log Collector on a JA2500 appliance or virtual machine (VM) are as follows:

Note: Security Director Logging and Reporting is not supported on a JA1500 appliance.

Specifications

Table 6 shows the specifications for installing the integrated Log Collector on a JA2500 appliance.

Table 6: Specifications for Installing an Integrated Log Collector on a JA2500

Component

Specification

Memory

8 GB

Log Collector uses 8 GB of memory of the available 32-GB system RAM.

Disk space

500 GB

This is used from the existing JA2500 appliance disk space.

CPU

Single core

Note: These specifications are used internally by the integrated Log Collector on a JA2500 appliance.

Table 7 shows the specifications for installing the integrated Log Collector on Junos Space Virtual Appliance.

Table 7: Specifications for Installing an Integrated Log Collector on a VM

Component

Specification

Memory

8 GB

If the integrated Log Collector is running on the Junos Space VM, we recommend adding 8 GB of RAM to maintain the Junos Space performance. It uses 8 GB of system RAM from the total system RAM.

Disk space

500 GB

Minimum 500 GB is required. You can add any amount of disk space.

CPU

2 CPUs of 3.20 GHz

Note: These specifications are used internally by the integrated Log Collector running on the Junos Space Virtual Appliance.

Procedure

To install the integrated Log Collector on a JA2500 appliance or virtual appliance:

  1. Download the integrated Log Collector image Integrated-Log-Collector-16.2.R1.xxx.sh from here.
  2. Copy the integrated Log Collector script to a JA2500 appliance or virtual appliance.
  3. Connect to the CLI of a JA2500 appliance or virtual appliance with admin privileges.
  4. Navigate to the location where you have copied the integrated Log Collector script.
  5. Change the file permission using the following command: chmod +x Integrated-Log-Collector-16.2.R1.xxx.sh.
  6. Install the integrated Log Collector script using the following command: sh Integrated-Log-Collector-16.2.R1.xxx.sh.

When the integrated Log Collector is installed on the JA2500 appliance or VM, the following message is displayed:

Shutting down system logger: [ OK ]
Starting jingest ... jingest started.
{"log-collector-node": {"id":376,"ip-address":"x.x.x.x","priority":0,"node-type": "INTEGRATED","cpu-usage":0,"memory-usage":0, "fabric-id":0,"display-name": "Integrated","timestamp":0}}

Once the installation is complete, a logging node is automatically added in Administration > Logging Management > Logging Nodes.

Configuring Log Collector Using Scripts

If you have used the standard setup menu to configure Log Collector, then you can use the script described in Table 8 to reconfigure it.

“jnpr-” <TAB>
[root@NWAPPLIANCE25397 ~]# jnpr- jnpr-configure-node jnpr-configure-ntp
jnpr-configure-timezone jnpr-network-script healthcheckOSLC

Table 8: Description of the Log Collector Script

Script

Description

jnpr-configure-node

Master script for the node configuration and network settings.

jnpr-configure-ntp

Script for NTP configuration.

jnpr-configure-timezone

Script for time zone configuration.

jnpr-network-script

Script for interface configuration.

healthcheckOSLC

Script for checking the issues with logging infrastructure.

Adding Log Collector to Security Director

You must deploy either Security Director Log Collector or Juniper Secure Analytics (JSA) as a log collector and then add it to Security Director to view the log data in the Dashboard, Events and Logs, Reports, and Alerts pages.

Before You Begin

Procedure

To add Log Collector to Security Director:

  1. From the Security Director user interface, select Administration > Logging Management > Logging Nodes, and click the plus sign (+).

    The Add Logging Node page appears.

  2. Choose the Log Collector type as Security Director Log Collector or Juniper Secure Appliance.

    If you select the Log Collector type as Security Director Log Collector, then select the deployment.

  3. Click Next.
  4. Provide the root credentials of the Log Collector node.
  5. Verify the corresponding job status.

    The Log Collector node appears in the Logging Nodes page with the status UP.

  6. Complete the configuration for Add Collector/JSA Node.
  7. If the Log Collector type is Security Director Log Collector, then Add Another Node is displayed to add multiple nodes as needed.
  8. Click Next.

    The certificate details are displayed.

  9. Click Finish.
  10. Review the summary of configuration changes from the summary page and click Edit to modify the details, if required.
  11. Click OK to add the node.

    A new logging node with your configurations is added. To verify if the node is configured correctly, click Logging Management to check the status of the node.

Note: JSA node sends many maintenance logs from its own IP address to localhost (127.0.0.1). These system logs are displayed in the Event Viewer page. You can disable these maintenance logs.

To disable the maintenance logs:

  1. Log in to the JSA console.
  2. Select Admin > Routing Rules.
  3. Add a rule: Destination IP - Equals - 127.0.0.1
  4. Select the Drop routing option.
  5. Uncheck the Forward routing option.
  6. Click Save.
Help us to improve. Rate this article.
Feedback Received. Thank You!

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit