Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


IBM SAN Volume Controller

The JSA DSM for IBM SAN Volume Controller collects events from IBM SAN Volume Controller.

The following table describes the specifications for the IBM SAN Volume Controller DSM:

Table 1: IBM SAN Volume Controller DSM Specifications





DSM name

IBM SAN Volume Controller

RPM file name

DSM-IBMSANVolumeController-JSA_version-build_number .noarch.rpm

Supported versions




Event format


Recorded event types

Activity, Control, and Monitor audit events

Automatically discovered?


Includes identity?


Includes custom properties?


More information

IBM SAN Volume Controller website (

To integrate IBM SAN Volume Controller with JSA, complete the following steps:

  1. If automatic updates are not enabled, download and install the most recent version of the following RPMs from the Juniper Downloads, in the order that they are listed, on your JSA console:

    • DSMCommon RPM

    • IBM SAN Volume Controller DSM RPM

  2. Configure your IBM SAN Volume Controller server to send syslog events to JSA.

  3. If JSA does not automatically detect the log source, add an IBM SAN Volume Controller log source on the JSA console. The following table describes the parameters that require specific values for IBM SAN Volume Controller event collection:

    Table 2: IBM SAN Volume Controller Log Source Parameters



    Log Source type

    IBM SAN Volume Controller

    Protocol Configuration


    Log Source Identifier

    The IP address or host name of the IBM SAN Volume Controller server.

  4. To verify that JSA is configured correctly, review the following table to see an example of a parsed event message.

    The following table shows a sample event message for IBM SAN Volume Controller:

    Table 3: IBM SAN Volume Controller Sample Message

    Event name

    Low level category

    Sample log message

    Backup Successful

    Backup Activity Succeeded

    Oct 12 20:02:33 Cluster_172.0.0.1 IBM2145: {"typeURI": "http://schemas." ,"eventTime": "2016-10-12T20:02 :30.000000+0000","target": {"typeURI": "service/storage/ object","id": "0","name": "username"},"observer": {"typeURI" : "service/network/cluster/logger", "id": "10032004394","name": "username"},"tags": ["Backup"], "eventType": "activity", "measurements": [{"metric": {"metricId": " /Backup_Time/1476302550/110/1", "name": "Time of backup being copied or restored","unit": "YYMMDDHHMMSS"},"result": "2016/ 10/12/20/02/30"},{"metric": {"metricId": " Cloud/Backup_Generation_Number/ 1476302550/110/2","name": "Volume backup generation number", "unit": "Natural Number"},"result" : "1"}],"initiator": {"typeURI": "service/network/node","host": {"address": ""}, "attachments": [{"content": "6005076400C8010E5000000000000 000","typeURI": "text/plain", "name": "volume_uuid"}],"name": "username","id": "1"},"reason": {"reasonCode": "200","reasonType" : " /http-status-codes/http-status -codes.xml"},"action": "backup" ,"outcome": "success","id": "10032004394-1476302550-110"}

Configuring IBM SAN Volume Controller to Communicate with JSA

To collect events from IBM SAN Volume Controller, you must configure IBM SAN Volume Controller (SVC) cluster to send events to JSA from a syslog server.

SVC cluster uses rsyslogd 5.8.10 on a Linux 6.4 based host.

  1. Use SSH to log in to the SVC cluster command-line interface (CLI).

  2. Type the following command to configure a remote syslog server to send CADF events to JSA:

    svctask mksyslogserver -ip <JSA_Event_Collector_IP_Address> error <on_or_off> -warning <on_or_off> -info <on_or_off> -cadf on

    The following example shows a command that is used to configure a remote syslog server to send CADF events:

    svctask mksyslogserver -ip -error on -warning on -info on -cadf o


    The error and warning flags are CADF event types that SVC sends to syslog servers.