Configure Cisco Nexus Dashboard alerts for ITSI 4.20.x and higher
Learn how to configure alerts for Cisco Nexus Dashboard in ITSI 4.20.x and higher, including data integration and normalization steps.
-
The generic data integration described on this page is only required if you want to ingest alerts to ITSI 4.20.x.
-
If you want to ingest alerts to ITSI 4.21.x and higher, you can use the generic data integration described on this page or the specific data integration for Cisco Nexus Dashboard described on Configure Cisco Nexus Dashboard alerts for ITSI 4.21.x and higher. The best practice is to use the specific data integration, which contains default connections and templates to map data fields to normalize alerts for new connections.
-
If you were using ITSI 4.20.x and configured the generic data integration, upgrading to ITSI 4.21.x and higher will not automatically migrate you to the specific data integration. The generic data integration will still be functional. To optionally switch to the specific data integration, deactivate your connection(s) in the generic data integration and follow the steps in Configure Cisco Nexus Dashboard alerts for ITSI 4.20.x and higher.
The Cisco DC Networking App for Splunk does not normalize alerts data. To ingest and normalize alerts from Cisco Nexus Dashboard to ITSI 4.20.x and higher, you can set up a generic data integration.
The generic data integration requires manually mapping data fields to normalize alerts.
For more information about data normalization, see Overview of the Splunk Common Information Model.
Configure a generic data integration for Cisco Nexus Dashboard alerts
Complete the following steps to configure a generic data integration for Cisco Nexus Dashboard alerts.
-
From the ITSI main menu, select .
-
The Integrations library tab is selected by default. Under Alerts, select Generic.
-
Enter a Title for the data connection, such as Cisco Nexus Dashboard.
-
Under Select data ingest method, enter and validate the index:
-
For * Search, enter:CODE
`cisco_dc_nd_index` sourcetype IN ("cisco:dc:nd:anomalies", "cisco:dc:nd:advisories") | mvexpand node_names | rename node_names as node_name | eval itsi_entity_id = fabricName.":".node_nameNote: If you are ingesting Cisco Nexus Dashboard alerts from a different index, changecisco_dc_nd_indexto the correct index. - Select a Lookback period.
-
Select Validate.
-
-
Under Map data fields for ingest and configuration, configure the following field mappings:
Field name Field type Field value Source = Composition Field: node_nameSignature = Composition Field: signatureVendor Severity = Composition Field: vendor_severitySeverity ID = Mapping rule - Value case mapping If vendor_severity is equal to (not case sensitive) criticalthen useCriticalIf Field:vendor_severity is equal to (not case sensitive)
majorthen useHighIf Field:vendor_severity is equal to (not case sensitive)
minorthen useMediumIf Field:vendor_severity is equal to (not case sensitive)
warningthen useLowIf Field:vendor_severity is equal to (not case sensitive)
normalthen useNormalIf Field:vendor_severity is equal to (not case sensitive)
infothen useInfoElse use this default value
LowTitle = Mapping rule - Value case mapping If Field:alertType is equal to (not case sensitive) advisorythen useField:titleElse use default values:-
Field: fabricName -
- -
Field: signature -
- -
Field: src
Note: You must enter 4 text values in this order, including the "-" symbols. Do not add spaces between the values.Owner = Composition unassignedStatus = Composition NewSubcomponent = Composition Field: entityNameAlert Identifier Fields = Composition Field: idDescription = Composition Field: descriptionApp = Composition Field: appITSI Drilldown Search Name = Composition Field: itsiDrilldownSearchNameITSI Drilldown Search = Composition Field:itsiDrilldownSearchITSI Drilldown earliest offset = Mapping rule - Coalesce Field: itsiDrilldownEarliestOffsetElse use default value-900ITSI Drilldown latest offset = Mapping rule - Coalesce Field: itsiDrilldownLatestOffsetElse use default value900 -
-
Under Association, enter itsi_entity_id as the value for the Entity Lookup Field.
-
Select Save and activate.