Accenture MDR Quick Start Guide for Nokia SR
- Dinesh Murugaiyan
This quick start guide will help Accenture MDR customers configure Nokia SR 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 |
Nokia SR | LCP | 514 (UDP) or 601 (TCP) | Default port
|
Configuring Nokia SR
How To Configure Syslog on Router Instances :
config# logconfig>log# syslog <syslog-id>config>log>syslog$ description "<description>"config>log>syslog# address <LCP IP>config>log>syslog# port 514config>log>syslog# log-prefix "Nokia-SR"config>log>syslog# facility local0config>log>syslog# level info
NOTE : Log-prefix command is very important here and should always be configured as Nokia-SR.
Syslog Fields | Values | Description |
|---|---|---|
syslog syslog-id | 1 - 10 | This command creates the context to configure a syslog target host that is capable of receiving selected syslog messages from this network element. A valid syslog-id must have the target syslog host address configured. |
address ip-address | LCP IP as Syslog Destination | This command adds the syslog target host IP address to/from a syslog ID. This parameter is mandatory. If no address is configured, syslog data cannot be forwarded to the syslog target host. |
facility syslog-facility | 0 - 23 Default : local0 | This command configures the facility code for messages sent to the syslog target host |
log-prefix log-prefix-string | Nokia-SR | This command adds the string prepended to every syslog message sent to the syslog host. RFC3164, allows a alphanumeric string (tag) to be prepended to the content of every log message sent to the syslog host. |
level syslog-level | emergency, alert, critical, error, warning, notice, info, debug Default : info | This command configures the syslog message severity level threshold. All messages with severity level equal to or higher than the threshold are sent to the syslog target host. |
port port | 514 | This command configures the UDP port that will be used to send syslog messages to the syslog target host |
IMPORTANT NOTE :
MxDR does not support any modification or Tampering in syslog format for Nokia SR . Below is the default log format provided and any modification or configuration in this format will not be supported.
Default Log Format : <timestamp> <hostname> <log-prefix>: <sequence> <router-name> <appname>-<severity>-<eventname>-<eventid> [<subject>]: <logmessage>
Time Stamp should be in UTC format Always . Log Prefix should be Nokia-SR always .
LCP Configuration Parameters
Table 1-2: The Nokia SR OS event collector (Syslog -3993) properties to be configured by Accenture are given in the table.
Property | Default Value | Description |
Protocol | UDP | The default protocol for syslog. The collector can also accept logs in TCP. Note: While TCP offers guaranteed delivery of log packets, it places a larger overhead on the LCP. To balance TCP for reliability over UDP for speed/simplicity, contact the Accenture Security Onboarding team. |
Host Names / IP Addresses | * | Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ). Note: If the device sends logs using multiple interfaces, contact the Accenture Security Onboarding team. |
Signatures | Nokia-SR: | Accenture Security recommended signatures processed by the Nokia SR event collector. |
Port Number | 514 | The default port for UDP. For TCP, the default port is 601. Note: The LCP can be configured to listen on a non-standard port, please advise the Accenture Security Onboarding team if this is a requirement. |
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.