Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

IBM Cloud Platform (formerly known as IBM Bluemix Platform)

IBM Cloud Platform is formerly known as IBM Bluemix Platform. The name remains the same in JSA.

The JSA DSM for the IBM Cloud Platform collects events logs from your IBM Cloud Platform.

The following table identifies the specifications for the IBM Cloud Platform DSM:

Table 1: Bluemix Platform DSM Specifications

Specification

Value

Manufacturer

IBM

DSM name

Bluemix Platform

RPM file name

DSM-IBMBluemixPlatform-7.x-xxxxxxx.noarch.rpm

Supported versions

N/A

Protocol

Syslog, TLS Syslog

Recorded event types

All System (Cloud Foundry) events, some application events

Automatically discovered?

Yes

Includes identity?

No

Includes custom properties?

No

More information

IBM Cloud website

To integrate IBM Cloud Platform with JSA, complete the following steps:

You must complete the installation, third-party configuration, and JSA configuration procedures in the order. Installation must always be first, but you can invert the order of the other two procedures, In some cases, no action is required for the third-party configuration and you can omit the procedure.

  1. If automatic updates are not enabled, download and install the most recent version of the Bluemix Platform DSM RPM from the Juniper Downloads onto your JSA console:

  2. Configure your IBM Cloud Platform device to send syslog events to JSA.

  3. If JSA does not automatically detect the log source, add a IBM Cloud Platform log source on the JSA Console.

Configuring IBM Cloud Platform to Communicate with JSA

To collect IBM Cloud Platform events, you must configure your third-party instance to send events to JSA.

You must have an app running in IBM Cloud so that you can create log drains.

  1. From the Cloud Foundry command-line interface, type the following command to create a drain:

    Alternatively, use the following command:

    1513 is the port that is used to communicate with JSA.

  2. Bind the service instance with the following command:

Integrating IBM Cloud Platform with JSA

In most installations, there is only the RPM. For installations where there are multiple RPMs required, (for example a PROTOCOL RPM and a DSMCommon RPM), ensure that the installation sequence reflects RPM dependency.

  1. If required, download and install the latest TLS Syslog RPM from the Juniper Downloads onto your JSA console. You can install a protocol by using the procedure to manually install a DSM. If automatic updates are configured to install protocol updates, this procedure is not necessary.

  2. Download and install the latest DSMCommon RPM from the Juniper Downloads onto your JSA console. If automatic updates are configured to install DSM updates, this procedure is not necessary.

  3. Download and install the latest Bluemix Platform RPM from the Juniper Downloads onto your JSA console. If automatic updates are configured to install DSM updates, this procedure is not necessary.

Configure a log source in JSA by using Syslog or TLS Syslog.

Syslog Log Source Parameters for IBM Cloud Platform

If JSA does not automatically detect the log source, add an IBM Cloud Platform log source on the JSA Console by using the Syslog protocol.

When using the syslog protocol, there are specific parameters that you must use.

The following table describes the parameters that require specific values to collect syslog events from IBM Cloud Platform:

Table 2: Syslog Log Source Parameters for the IBM Cloud Platform DSM

Parameter

Value

Log Source type

Bluemix Platform

Protocol Configuration

Syslog

Log Source Identifier

The IP address of the Cloud Loggregator.

Note:

It might be necessary to include the IP address and the port, as the Log Source Identifier. For example, 192.0.2.1:1513.

TLS Syslog Log Source Parameters for IBM Cloud Platform

If JSA does not automatically detect the log source, add an IBM Cloud Platform log source on the JSA Console by using the TLS syslog protocol.

When using the TLS syslog protocol, there are specific parameters that you must use.

The following table describes the parameters that require specific values to collect TLS syslog events from IBM Cloud Platform:

Table 3: TLS Syslog Log Source Parameters for the IBM Cloud Platform DSM

Parameter

Value

Log Source type

Bluemix Platform

Protocol Configuration

TLS Syslog

Log Source Identifier

Type the IP address of the IBM Cloud Loggregator.

Note:

It might be necessary to include the IP address and the port, as the Log Source Identifier. For example, 192.0.2.1:1513.

For more information about TLS syslog log source parameters, see TLS Syslog Protocol Configuration Options.

IBM Cloud Platform Sample Event Messages

Use this sample event message to verify a successful integration with JSA.

Note:

Due to formatting issues, paste the message format into a text editor and then remove any carriage return or line feed characters.

IBM Cloud Sample Message when you use the Syslog Protocol

The following sample event message shows that a route is unregistered.

Table 4: JSA Field Names for the IBM Cloud Platform Sample Event

JSA field name

Highlighted values in the payload

Event ID

unregister-route

Category

This DSM doesn't have a category field to key from for the device in the payloads. JSA provides the value Cloud Foundry as a static category.

Log Source Time

1519329639.0902693

Source IP

10.68.232.5

Source Port

8081