Accenture MDR Quick Start Guide for Cisco® Nexus™ and Cisco® APIC™
This quick start guide will help Accenture MDR customers configure Cisco® Nexus™ to send logs to the Log collection Platform (LCP).
The 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 |
Cisco Nexus | LCP | 514 (UDP) | Default port |
Cisco APIC | LCP | 6514 (TCP) or 514 (UDP) or 601 (TCP) | Default port |
Configuring Cisco Nexus
To configure Cisco Nexus to send syslog messages to the LCP, follow the steps below.
Note: You can configure up to three syslog servers to forward logs to remote systems.
Connect the Virtual Device Context (VDC).
Login to the CLI.
To view all the VDCs, enter the command: show vdc
To view the existing VDC, enter the command: show vdc current-vdc
To change the VDC, enter the command: switchto vdc
Configure Cisco Nexus in CLI.
Login to the CLI.
Enter the following commands in the same sequence:
switch# configure terminal
switch(config)# logging server <lcp_ip_address> <severity-level> use-vrf <vrf-name> facility <local7>
switch# copy running-config startup-config
Note:
Please refer the vendor documentation for more information on severity levels.
The use vrf vrf-name keyword argument identifies the default or management values for the VRF name. If a specific VRF is not identified, management is the default value. However, if management is configured, it will not be listed in the output of the show-running command because it is the default value. If a specific VRF is configured, the show-running command output will list the VRF for each server.
Note:
Cisco Nexus configuration does not provide any option to configure logging through TCP and/or a non-standard port even though collector support has been provided.
When Cisco Nexus is configured to forward logs to the LCP through ArcSight SmartConnector, the logging device IP is the IP of the ArcSight SmartConnector.
When multiple Cisco Nexus switches forward logs through the same ArcSight SmartConnector, the logs gathered from all the switches will have the IP of ArcSight SmartConnector as the logging device IP.
The Cisco Nexus collector supports log forwarding from ArcSight Smart connector. Please contact a Accenture MDR onboarding engineer if you need assistance with the configuration.
Device configuration for Cisco APIC
Creating a Syslog Destination and Destination Group:
In the menu bar, click Admin.
In the submenu bar, click External Data Collectors.
In the Navigation pane, expand Monitoring Destinations.
Right-click Syslog and choose Create Syslog Monitoring Destination Group.
In the Create Syslog Monitoring Destination Group dialog box, perform the following actions:
In the group and profile Name field, enter a name for the monitoring destination group and profile.
In the group and profile Format field, choose the format for Syslog messages. The default value is “aci”, you need to use the default value.
Enable "Show Milliseconds in Timestamp" and "Show time Zone in Timestamp".
In the group and profile Admin State drop-down list, choose enabled.
To enable sending of syslog messages to a local file, choose enabled from the Local File Destination Admin State drop-down list and choose a minimum severity from the Local File Destination Severity drop-down list. Choose severity as “Information”.
To enable sending of syslog messages to the console, choose enabled from the Console Destination Admin State drop-down list and choose a minimum severity from the Console Destination Severity drop-down list. Choose severity as “Alerts“.
Click Next.
In the Create Syslog Remote Destination dialog box, perform the following actions:
In the Host field, enter an “LCP IP” or a fully qualified domain name for the destination host.
(Optional) In the Name field, enter a name for the destination host.
In the Admin State field, click the enabled radio button.
Select severity as “warning”.
Select transport as ssl
Select port as 6514
Note - You can use transport as tcp, have to mention port as 601 and use transport as UDP, have to mention port as 514.
g. Select Forwarding Facility as local7.
h. Select Management EPG as default(out-of-band).
i. Click OK & Finish.
j. Path to upload certificate - Admin > AAA > Security > Public Key Management > Certificate Authorities, then Actions > Create Certificate Authority
Creating a Syslog Source:
Under Fabric > Fabric Policies > Monitoring Policies > Common Policy
Under the Common policy, click Callhome/Smart Callhome/SNMP/Syslog
In the Work pane, choose Syslog from the Source Type drop-down list.
From the Monitoring Object list, select “All”
In a tenant monitoring policy, select “All”
Click + to create a syslog source.
Enter a name for the syslog source.
Select the minimum severity as “Warning” from drop-down list.
Select all type of messages to sent to syslog server(Audit logs, Events, Faults, Session logs).
Select Dest Group which you have created in step 1 & 2.
Click Submit.
LCP Configuration Parameters
Table 1-2: The Cisco Nexus and Cisco APCI event collector (Syslog -3734) properties to be configured by MDR are shown in the table.
Property | Default Value | Description |
Protocol | UDP | The default protocol for syslog. Note: Cisco Nexus does not support TCP. Enable the TCP port only if CISCO APIC logs receiving in TCP port. |
IP Address | Cisco Nexus and Cisco APIC Interface IP Address | Logging device IP address mentioned in the Pre-Installation Questionnaire (PIQ).
|
Signatures | %LOG_LOCAL,%STM,%IGMP,%FWM,%VPC,%VTP,%VLAN_MGR,%PVLAN,%SVI,%FCS,%SFP,%GLBP,%HSRP,%VRRP_CFG,%VRRP- | MDR recommended signatures processed by the Cisco Nexus event collector. |
Port Number | 514 | The default port for UDP. Note:
|
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.