Accenture MDR Quick Start Guide for NetApp ONTAP

This quick start guide will help Accenture MDR customers configure NetApp ONTAP to send logs to the Log collection Platform (LCP).

This document includes the following topics:

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

Source

Destination

Port

Description

ONTAP

LCP

514 (UDP) or

601 (TCP)

Default port

 

Configuring NetApp ONTAP

There are two configurations need to be done for log forwarding:

  1. Configuration for Audit logs.

  2. Configuration for EMS logs.

Configuration for Audit logs:

To configure forwarding, you must provide the IP address of the syslog host, its port number, a transmission protocol, and the syslog facility to use for the forwarded logs.

Note: You can select one of the following transmission values:

UDP Unencrypted (default), TCP Unencrypted, TCP Encrypted

Configuration Steps:

  1. Login to the cluster via ONTAP command line with admin privilege level.

  2. For each destination that you want to forward the audit log to, specify the destination IP address or host name and any security options.

  3. cluster1::> cluster log-forwarding create -destination 192.168.123.96 -port 514 -facility user.

  4. Verify that the destination records are correct by using the cluster log-forwarding show command.

Configuration for EMS logs:

To log notifications of the most severe events on a syslog server, you must configure the EMS to forward notifications for events that signal important activity.

You can perform this task any time the cluster is running by entering the commands on the ONTAP command line.

Note: DNS must be configured on the cluster to resolve the syslog server name.

Configuration Steps:

  1. Login to the cluster via ONTAP command line with admin privilege level.

  2. Create a syslog server destination:

event notification destination create -name <Name of the destination> -syslog <LCP Address>

3. Create an event filter named filter1 or any name you want:

event filter create -filter-name <Filter name>

4. Configure all events to forward notifications to the syslog server:

event notification -filter-name <Name of the filter you created> -destinations <Name of the syslog destination created>

Note: EMS has some system defined filters. Like: “default-trap-events, “important-events“ and “no-info-debug-events

  • default-trap-events - This filter matches all ALERT and EMERGENCY events. It also matches all Standard, Built-in SNMP trap type events.

  • important-events - This filter matches all ALERT and EMERGENCY events.

  • no-info-debug-events - This filter matches all non-INFO and non-DEBUG messages (EMERGENCY, ALERT, ERROR and NOTICE).

The system-defined event filters cannot be modified or deleted.

LCP Configuration Parameters

Table 1-2: The NetApp ONTAP event collector (Syslog -3980) properties to be configured by Accenture are given in the table.

Property

Default Value

Description

Property

Default Value

Description

Protocol

UDP

UDP/TCP

Host Names/IP Addresses 

*

 

Signatures

:info]:,:INFO]:,:Info]:,:DEBUG]:,:debug]:,:Debug]:,:notice]:,:NOTICE]:,:Notice]:,:error]:,:ERROR]:,:Error]:,:ALERT]:,:alert]:,:Alert]:,:Emergency]:,:EMERGENCY]:,:emergency]: 

 

Enable Signatures

TRUE

Let you enable or disable the signature filtering.

Port Number

514

Default port number for UDP is 514. For TCP preferred port is 601

Time Offset

+00:00

Specify a time offset to convert timestamps of all logged events to the time zone of the collector computer

 

Legal Notice

Copyright © 2021 Accenture. All rights reserved.

Accenture, the Accenture Logo, and DeepSight Intelligence are trademarks or registered trademarks of Accenture in the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Accenture and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. ACCENTURE SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Accenture as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.