Working with Integrations in Your Nexus Dashboard, Release 4.3.1

Accessing IPAM Integrator

This procedure shows how to access IPAM integrator.

Viewing Network IP Scope

Network IP Scope is the landing page after you access the IPAM Integrator.

The following table describes the fields retrieved from the IPAM server.

The following table describes the fields retrieved from Nexus Dashboard.

Field	Description
Fabric Name	Specifies the name of the fabric.
Fabric Type	Specifies the type of the fabric. It can be Multi-Site Domain (MSD), or a standalone easy fabric or an eBGP VXLAN fabric.
Network Name	Specifies the name of the network.
VRF Name	Specifies the name of the VRF.
Network ID	Specifies the network ID.
VLAN ID	Specifies the VLAN ID.
Last Updated (by Infoblox)	Specifies the date and time when the data was last updated by Infoblox. The date and time of the last poll are displayed under the Network IP Scope title.

Click Export to export the data in a .csv file.

For each field, you can sort the values by clicking the arrow icons, and search by entering the search criterion in Filter by attributes box.

The polling of data is based on the following criteria:

Viewing Statistics and Summary Data for the Subnet Utilization

To view the summary data for the utilization of the IP Subnet over a time, navigate to the following path.

To view the statistics for the utilization of the IP Subnet over a time, navigate to the following paths.

Click the drop-down list and select the time for which you want to view the statistics. These statistics include utilization of subnet such as DHCP allocations, total allocations, dynamic allocations, and static allocations.

Viewing IP Allocation for Hosts

To view the IP allocation for each host, navigate to the following paths.

The following fields are displayed for each host in the IP Allocation page. The data for these fields is retrieved from the IPAM server.

The Switch:Port and Fabric Name are retrieved through Nexus Dashboard EPL (Endpoint Locator) integration. Their values are empty if EPL feature is not enabled.

For each field, you can sort the values by clicking the arrow icons, and search by entering the search criterion in Filter by attributes box.

By default, information about only active hosts are displayed. Click the All value to view information about all hosts retrieved from the IPAM server. Click Export to export the data in a .csv file.

Hosts that were recently freed show as "FREE" in the All tab. All the originally free hosts won’t be shown as FREE. Only the hosts that were recently freed appear in this tab.

Viewing Conflicting Networks

IPAM Integrator detects conflicting networks defined in IPAM server and Nexus Dashboard. You can view this info by clicking Conflicting in the Network IP Scope page.

For example, if one network is a subset of another, the conflicting IP addresses of the network are displayed under Conflicting.

The data is displayed similar to how the Matched data is displayed. You can click the IP range value under the IP Range column to view the IP allocation for each host.

Note that this table also lists the Nexus Dashboard Gateway for the conflicting IP scopes in addition to the subnet information from the IPAM server.

For each field, you can sort the values by clicking the arrow icons, and search by entering the search criterion in Filter by attributes box.

DNS file upload

This method is simple because mappings do not change often. In the GUI, you can upload a file containing mappings. Use one of the supported formats (.csv and .json). Nexus Dashboard verifies the integrity of the file. When required, you can also download or delete the file from the GUI.

If you do not specify a VRF instance, Fabric name, nor Tenant information, DNS will be applied to the fabrics for which the DNS server is configured based on the choices in Add Integrations and Associations section. If the DNS server is configured for a fabric, then DNS will be applied to all the fabrics in the group.

The DNS file upload size is limited to 1.8 MB.

recordType  fqdn            ips         siteName    tenant          vrf
dnsEntry    WebSrv1.foo.com 10.101.11.1 ACI-Fab1    prod            vrf_prod
dnsEntry    WebSrv2.foo.com 10.101.11.2 ACI-Fab1    prod            vrf_prod
dnsEntry    WebSrv3.foo.com 10.101.11.3 ACI-Fab1    prod            vrf_prod
dnsEntry    WebSrv4.foo.com 10.101.11.4 ACI-Fab1    prod            vrf_prod

[
    {
        "recordType": "dnsEntry",
        "fqdn": "WebSrv1.foo.com",
        "ips": [
            "10.101.11.1"
        ]
    },
    {
        "recordType": "dnsEntry",
        "fqdn": "WebSrv2.foo.com",
        "ips": [
            "10.101.11.2",
            "52::2"
        ]
    },
    {
        "recordType": "dnsEntry",
        "fqdn": "WebSrv3.foo.com",
        "ips": [
            "10.101.11.3",
            "52::3"
        ]
    },    {
        "recordType": "dnsEntry",
        "fqdn": "WebSrv4.foo.com",
        "ips": [
            "10.101.11.4",
            "10::101:0:4"
        ]
    }
]

DNS query

Use this method one query at a time to retrieve data from the DNS server using reverse lookup. Reverse lookup zone(s) must be configured on the DNS server.

Nexus Dashboard queries the DNS server at regular intervals and resolves IP addresses that are learned using endpoints.

Nexus Dashboard allows one primary and multiple secondary DNS servers, the primary DNS server will be polled first. If the resolution does not succeed, the secondary servers will be polled thereafter.

DNS zone transfer

DNS zone transfer is also known as AXFR downloads. Nexus Dashboard can retrieve zone data in bulk from the DNS server using AXFR downloads. This method is convenient for large quantities of data as you no longer have to work on one query at a time.

A zone transfer requires at least one DNS zone. If you configure a forward mapping zone, then all the A and AAAA records will be fetched from a DNS server, and if you configure a reverse mapping zone, then PTR records will be fetched. When onboarding the DNS server, you must provide a list of zones from which to fetch the data. Nexus Dashboard will fetch the data from each zone configured from the DNS server.

TSIG (transaction signature) is a computer-networking protocol defined in RFC 2845. Primarily it enables the DNS to authenticate updates to a DNS database. For a secure transfer, Nexus Dashboard allows you to configure the TSIG key for a zone to initiate the transaction. Configure the zone with the TSIG key, and an associated algorithm. In the Nexus Dashboard GUI, the supported algorithms are displayed in a drop-down list.

When you delete an onboarded DNS server, all the zones will be un-configured automatically. A zone can be a forward mapping or a reverse mapping zone.

Guidelines and limitations for DNS integration

These guidelines and limitations apply to DNS integration:

Configure DNS

Follow these steps to configure DNS.

The .json or .csv file used in this task must be uploaded in a specific schema. See the following section for the formats to use.

[
  {
        "recordType": "dnsEntry",
        "fqdn": "host1.cisco.com",
        "ips": ["1.1.0.0"],
        "vrf": "vrf-1",
        "siteName": "swmp3",
        "tenant": "tenant-1"
  },
  {
        "recordType": "dnsEntry",
        "fqdn": "host2.cisco.com",
        "ips": ["1.1.0.1"],
        "vrf": "vrf-1",
        "siteName": "swmp3",
        "tenant": "tenant-1"
 },
 {
         "recordType": "dnsEntry",
         "fqdn": "host3.cisco.com",
         "ips": ["1.1.0.2"],
 },
]

[
  {
        "recordType": "dnsEntry",
        "fqdn": "host1.cisco.com",
        "ips": ["1.1.0.0"],
        "vrf": "vrf-1",
        "siteName": "swmp3",
  },
  {
        "recordType": "dnsEntry",
        "fqdn": "host2.cisco.com",
        "ips": ["1.1.0.1"],
        "vrf": "vrf-1",
        "siteName": "swmp3",
 },
 {
         "recordType": "dnsEntry",
         "fqdn": "host3.cisco.com",
         "ips": ["1.1.0.2"],
 },
]

recordType,fqdn,ips,siteName,tenant,vrf
dnsEntry,swmp3-leaf1.cisco.com,"101.22.33.44",swmp3,tenant-1,vrf-1
dnsEntry,swmp5-leaf1.cisco.com,"10.2.3.4,10.4.5.6,1.2.3.4",fabric2,tenant-2,vrf-2
dnsEntry,swmp4-leaf1.cisco.com, "1.1.1.1",,,

Workflow for Hypershield integration

Follow this workflow to add your Hypershield integration.

Associate a fabric with Hypershield integration

You can associate a fabric with a Hypershield integration at different times during the Hypershield integration configuration. Here are different use-case scenarios for associating a fabric to a Hypershield integration.

Follow these steps to associate a Hypershield integration with an External and Inter-Fabric Connectivity fabric.

View Hypershield integration

Follow these steps to view your Hypershield integration and the fabrics associated with the Hypershield integration.

Navigate to Admin > Integrations.

Here you can view the the integration status.

These are the fields that display on the Integrations page.

Smart switch configuration behavior in brownfield deployments

Beginning with Nexus Dashboard 4.3.1, when you add one or more Smart switches that already contain Smart switch configuration to a supported fabric with the Preserve Config option enabled, Nexus Dashboard negates the existing Smart switch-related configuration, including the service system hypershield section. This behavior occurs even if Nexus Dashboard originally added the Smart switch configuration.

---

To continue managing the Smart switches from the Nexus Dashboard, you must recreate the required Smart switch intent in the Nexus Dashboard and deploy the configuration to the switches.

---

Onboard the Smart switch

Before you onboard a Smart switch, associate the fabric for that Smart switch with a Hypershield integration. The onboarding process uses the selected integration to retrieve the Smart switch token from the Hypershield controller.

Follow these steps to onboard the Smart switches.

Pair Smart switches for high availability

High availability (HA) pairing provides stateful redundancy for Layer 4 to Layer 7 (L4-L7) flows on Smart switches. You can pair Smart switches that are already virtual port channel (vPC) peers. You can also or pair standalone, non-vPC leaf Smart switches.

HA communication requires a dedicated physical link between the Smart switches.

---

For non-vPC HA pairing, size the HA link based on the amount of HA traffic that your deployment must support. In VXLAN EVPN fabrics, the HA link can require 800 Gbps of bandwidth. For example, use two 400 Gbps links on N9348Y2C6D-SE1U switch or eight 100 Gbps links on N9324C-SE1U switch. If the Smart switch is deployed as an ePBR destination or an ACI PBR destination, two 100 Gbps or 25 Gbps links are sufficient.

---

For standalone leaf Smart switches, Nexus Dashboard must discover the physical links between the switches before you can pair them.

Before you pair smart switches, enable the high availability configuration in the fabric settings. You can also enable automatic HA pairing when vPC pairing occurs on smart switches. Configure the following parameters:

• HA loopback interface

• HA source subnet

• HA VLAN

• HA peer link subnet

• HA peer link subnet granularity

---

• Ensure that the HA loopback interface that you select in fabric settings is not already in use on the Smart switches. If you use a loopback that is already in use, for instance Loopback1023 for HA pairing and Loopback1023 is preconfigured for another purpose, the HA pairing configuration can fail.

---

HA pair for vPC

For vPC-based high availability (HA) pairing, the Smart switches must have a direct physical vPC peer link. Nexus Dashboard uses the reserved HA VLAN, VLAN 3601 by default, on an SVI over this physical link for HA communication.

---

The vPC must be physical. Although vPCs created over a virtual link might appear in the selection list, they are not supported for HA pairing.

---

Follow these steps to perform HA pair for vPC.

1. Choose Manage > Fabrics.

2. Click the fabric name to view the fabric Overview page.

3. Click Inventory > vPC pairs > Discovered.

4. Click Actions drop-down list at the top right, Actions > Smart switches > HA pair.

5. Check the switches check box and click Next.

6. Click Pair.

7. Click Deploy now.

8. Click Done to complete.

HA pair for non-vPC

Follow these steps to perform HA pair for non-vPC.

1. Choose Manage > Fabrics.

2. Click the fabric name to view the fabric Overview page.

3. Click Inventory > Smart switches > HA pairs and ensure that switches are present in the fabric.

4. Click Actions drop-down list at the top right, Actions > Smart switches > HA pair.

5. Check the switch check box for the first switch and click Next.

6. Check the switch check box for the second switch and click Pair.

7. Click Deploy now.

8. Click Done to complete.

HA unpair for vPC

Follow these steps to perform HA unpair for vPC.

1. Choose Manage > Fabrics.

2. Click the fabric name to view the fabric Overview page.

3. Click Inventory > vPC pairs > Discovered.

4. Click Actions drop-down list at the top right, Actions > Smart switches > HA unpair.

5. Check the switches check box and click Next.

6. Click Unpair.

7. Click Deploy now.

8. Click Done to complete.

HA unpair for non-vPC

Follow these steps to perform HA unpair for non-vPC.

1. Choose Manage > Fabrics.

2. Click the fabric name to view the fabric Overview page.

3. Click Inventory > Smart switches > HA pairs and ensure that switches are present in the fabric.

4. Click Actions drop-down list at the top right, Actions > Smart switches > HA unpair.

5. Check the switches check box and click Next.

6. Click Unpair.

7. Click Deploy now.

8. Click Done to complete.

DPUs

Data Processing Units (DPUs) are integral to a Smart switch and help transform it into a multifunctional, service-hosting device. DPUs are specialized hardware components designed to offload and accelerate data processing tasks traditionally handled by CPUs or NPUs. DPUs are equipped with programmable data planes, memory, specialized acceleration engines, and embedded CPUs for control and management.

A Smart switch integrates with DPUs and networking Application-Specific Integrated Circuits (ASICs) to deliver these advanced services:

• Stateful firewall — Distributed stateful firewall capabilities for enhanced security.

• Encryption services — Support for IPsec encryption and other security protocols. Telemetry and analytics — Offloading telemetry and flow data collection for better network visibility.

• Segmentation and scalability — Enabling stateful segmentation and seamless scaling of services.

In Nexus Dashboard, you can view and download the Data Processing Unit (DPU) information from your Hypershield fabric’s Fabric > Inventory page. You can also view the DPU information in the Nexus Dashboard Manage > Inventory > Switch Overview > Hardware page.

---

Not all switch overview pages in Nexus Dashboard display the DPU information. You must have a Smart switch configured on your fabric to view information on the DPUs.

---

Add Slurm integration

Follow these steps to add the Slurm integration.

In the Integrations page, the status for the Slurm integration will display as Initialize for a short period of time, and will change to Active when the integration is successfully completed. In addition, Nexus Dashboard determines which servers are connected to the Slurm cluster, then locates the fabric that contains those servers and displays that fabric in the Derived fabrics column.

Using enhanced analytics for AI fabrics

After you have added the Slurm integration, you can now use enhanced analytics for AI fabrics using these procedures:

Prerequisites for VMware vCenter Server integration

Guidelines and limitations for VMware vCenter Server integration

Add VMware vCenter server integration

Follow these steps to add VMware vCenter Server integration.

vCenter VM adapter state overview

To display an Overview page for a vCenter integration:

Note that this table provides a complete inventory of the physical network path for network connections of a VM. The ToR name, ToR interface, and ToR PO columns display values only when a ToR switch is present in the network path.

View VM details

The VM details page displays specific operational, configuration, and inventory details for virtual machines that an integrated vCenter manages.

Follow these steps to view the VM details.

1. Navigate to the Integrations page.

   Go to Admin > Integrations.

2. Click the name of the vCenter server integration.

   The vCenter VM overview page displays.

3. In the VM inventory list, click the VM Name of the specific virtual machine you wish to inspect.

   The VM details page displays General details and Network adapter sections.

You can view the following information in General details section.

Field	Description
State	Specifies the power state of the VM (for example, connected or disconnected).
Status	Displays the health status of the VM as reported by vCenter.
Hostname	Displays the hostname assigned to the guest operating system.
Guest OS	Displays the operating system type and architecture running on the VM.
vCenter	Displays the IP address of the vCenter server managing the VM.
Datacenter	Displays the name of the vCenter datacenter where the VM resides.
Cluster	Displays the name of the vCenter cluster associated with the VM.
Compute host	Displays the IP address of the ESXi host where the VM is currently running.
CPU	Specifies current CPU usage of the VM.
Memory	Specifies the Active Guest Memory currently used by the VM. This value represents the memory the guest operating system currently uses. Nexus Dashboard normalizes this value across integrations.
Disk	Displays the total disk storage capacity allocated to the VM.

You can view the following information in Network adapter section.

Field	Description
IP Address	Displays the IP address assigned to the specific network adapter.
MAC address	Displays the hardware address of the network adapter.
Network	Displays the name of the network to which the adapter connects.
Switch	Displays the name of the fabric switch(es) connected to the host (for example, dev2-leaf1, dev2-leaf2).
Switch Interface	Displays the specific physical interface on the switch (for example, Ethernet 1/3).
PG/DVS PG	Displays the Port Group (PG) or Distributed Virtual Switch(DVS) PG name.

Configure routes

By default, Nexus Dashboard uses the data interface to connect to the Kubernetes API endpoint. To use the management interface instead, you need to configure an alternate route on Nexus Dashboard.

Follow these steps to configure routes on Nexus Dashboard.

Add a Kubernetes cluster

Follow these steps to add a Kubernetes cluster.

Ensure that the routes are configured to connect to the Kubernetes cluster through the appropriate network interface. For more information, see Configure routes.

Delete a Kubernetes cluster

Follow these steps to delete a Kubernetes cluster.

1. Choose the appropriate cluster.

2. From the Actions drop-down list, choose Delete Instance(s).

3. Click Confirm to delete the cluster.

---

All the data is deleted if you delete the cluster. The cluster is removed from the Topology view as well.

---

Guidelines and limitations

Ensure that you resync Kubernetes clusters after you use backup or restore operation. To synchronize individual Kubernetes cluster, click the ellipsis (…​) in the last column of the Integrations table to choose the Rediscover option.

Prerequisites for OpenShift integration

Add an OpenShift cluster

Follow these steps to add an OpenShift cluster.

View an OpenShift cluster

Follow these steps to view an OpenShift cluster.

You can also view the OpenShift cluster from the Topology page. Navigate to Home > Topology to view the OpenShift Nodes and VMs represented with OpenShift-specific icons. In the topology view, a specific VM is represented by both the pod that launches it and an icon for the VM itself. This occurs because OpenShift visualization, which is built on KubeVirt, treats VMs as pods.

Guidelines and limitations for OpenShift integration

Prerequisites for Panduit PDU integration

Guidelines and limitations for Panduit PDU integration

These guidelines and limitations apply for Panduit PDU integration:

Add PDU integration

Follow these steps to add PDU integration.

View PDU integration

Follow these steps to view PDU integration.

Onboarding for SaaS or cloud deployments

Starting from Nexus Dashboard release 6.0.2, you can connect to an AppDynamics controller using a proxy for SaaS or cloud deployments. For onboarding an AppDynamics Controller running on a cloud, Nexus Dashboard uses a proxy configured in Nexus Dashboard’s Admin Console to connect to the AppDynamics Controller.

Guidelines and limitations for AppDynamics integration

Installing AppDynamics

Before you begin using Nexus Dashboard integrations, you must install the AppDynamics Application Performance Management and Controller. See Getting Started for details.

Onboard an AppDynamics controller

For Nexus Dashboard and AppDynamics integration, Nexus Dashboard’s data network must provide IP reachability to the AppDynamics controller. For more information, see the Cisco Nexus Dashboard Deployment Guide.

Nexus Dashboard and AppDynamics integration dashboard

The AppDynamics Dashboard allows you to onboard controllers and presents a view of the Top 5 Applications by Anomaly Score along with various metrics. After a controller is onboarded, data related to applications monitored by that controller is pulled by Nexus Dashboard. It can take up to 5 minutes for the first set of data to appear on the GUI. The AppDynamics health state information provided for each entity is aggregated and reported by Nexus Dashboard on the dashboard.

The AppDynamics dashboard displays the overview of the applications monitored by the AppDynamics controller.

AppDynamics integration application for standalone NX-OS fabrics

Detailed information including operational, statistics, and metrics, for each tier or application is also presented.

Topology view

The topology view represents the stitching between nodes where these nodes are connected to the fabric.

The topology view includes application nodes and leaf nodes. Toggle between show or not show to view/hide the nodes with anomaly score. The anomaly score is represented by the dot in the topology.

The topology view represents a hierarchical view of Application > Node > Leaf and the links between them with a logical or network view of how various objects are related.

Overview

Slack integration with Nexus Dashboard allows you to query Nexus Dashboard directly from Slack messenger across various Slack channels, enabling seamless collaboration and real-time interaction.

Configure Slack app

To integrate your Slack app with Nexus Dashboard and enable real-time interactions, you need to perform the following steps.

display_information:
  name: Cisco_ND_Slack_App_Nov13
features:
  bot_user:
    display_name: Cisco_ND_Slack_App_Nov13
    always_online: false
  slash_commands:
    - command: /get_switch_health
      description: gets switch health from Nexus Dashboard
      usage_hint: fabricName* switchName* interfaceName severity startDate endDate maxResults
      should_escape: false
    - command: /get_endpoint_location
      description: gets endpoints data from Nexus Dashboard using ip or mac
      usage_hint: endPointIpOrMacAddress* maxResults
      should_escape: false
    - command: /get_link_util_alerts
      description: Retrieves real-time link utilization alerts to monitor network traffic load
      should_escape: false
    - command: /get_link_util_alert_details
      description: Provides detailed information about specific link utilization alerts
      should_escape: false
    - command: /get_switch_anomaly_details
      description: Retrieves detailed anomaly reports detected on network switches
      should_escape: false
oauth_config:
  scopes:
    bot:
      - commands
settings:
  interactivity:
    is_enabled: true
  org_deploy_enabled: true
  socket_mode_enabled: true
  token_rotation_enabled: false

Create slash commands

Slash commands allow you to interact with your app directly from Slack messages.

Follow these steps to create slash commands.

1. In the Slack app settings dashboard, go to Slash Commands.

2. Click Create New Command.

   The Create New Command page displays.

   

3. Fill in the command details for each of your required commands.

   • Command — Provide the keyword, starting with a slash (/).

   • Short Description — Provide brief description of the command.

   • Usage Hint — (Optional) Provide help text for users. For mandatory parameters, add an asterisk (*) beside the parameter name (For example, *Username).

     You can add one or more of the following commands as needed.

     Slack slash commands	Description	Command parameters
     /get_link_util_alerts	Retrieves real-time link utilization alerts to monitor network traffic load.	fabricName* switchName* interfaceName severity startDate endDate maxResults
     /get_link_util_alert_details	Provides detailed information about specific link utilization alerts.	fabricName* anomalyId* startDate* endDate*
     /get_switch_health	Performs an on-demand health check of network switches to assess device status.	fabricName* switchName* severity startDate endDate maxResults If a severity level is specified, the function returns anomalies with that severity. If there are no anomalies matching the specified severity, it returns "no data found". If no severity is specified, the function returns anomalies of all severity levels. If the maxResults parameter is not specified, the function returns all results.
     /get_switch_anomaly_details	Retrieves detailed anomaly reports detected on network switches.	fabricName* anomalyId* startDate* endDate*
     /get_endpoint_location	Searches for the location of an end host within the network.	endPointIpOrMacAddress* maxResults If maxResults is not specified, the function returns all results. The maxResults parameter limits the number of returned IP or MAC addresses associated with the input address.

     

     ---

     • The asterisk (*) indicates a mandatory (non-empty) input parameter.

     • Parameters without an asterisk (*) are optional. You can leave optional parameters empty by using empty single quotes (' ').

     • All command parameters are strings except for maxResults, which is an integer.

     • Provide the input dates in the following formats.

       • Dates are in ISO 8601 formats as follows.

         • YYYY-MM-DDTHH:MM:SSZ

         • YYYY-MM-DDTHH:MM:SS±hh:mm

       • You can also specify the start and end dates as now-7h/d/w or now.

         • now-7h indicates hours, d indicates days, and w indicates weeks. If you omit the unit (For example, now-7), the system interprets it as now minus 7 days.

       • If you do not provide input dates, the system sets the start date to now-2h and end date to now.

     ---

4. Click Save.

5. Repeat steps 2-4 for each command you want to configure.

---

You can configure as many slash commands as needed, with each command pointing to the appropriate endpoint.

---

After you complete the setup, install the app to your Slack workspace from the OAuth & Permissions section in the Slack app settings dashboard.

Set up Slack integration in Nexus Dashboard

Add Slack CA certificate

Before you integrate Slack with Nexus Dashboard, you must add the Slack CA certificate to ensure secure communication between Nexus Dashboard and Slack.

---

Configure the proxy settings before you add a Slack CA certificate. For more information on configuring proxy settings, see Proxy configuration. You need to configure an HTTPS proxy only on Nexus Dashboard setups that use a proxy for external connectivity.

---

Follow these steps to add Slack CA certificate.

1. Navigate to Admin > Integrations.

2. If there are no existing integrations, click Add integration.

   The Add integration page displays.

3. Under Integration type, go to Bot integration > Slack.

4. Click Before adding integration, add a Slack CA Certificate here.

   The Certificate Management page displays.

   

   ---

   You can also go to the Certificate Management page by navigating to Admin > Certificate Management.

   ---

5. Click the CA certificates tab.

6. From the Actions drop-down list, choose Add CA certificate.

   The Add CA certificate page displays.

   
   

   ---

   You can download the Slack CA certificate from Slack.com. The certificate is downloaded in Privacy Enhanced Mail (PEM) format from ISRG Root X1.

   ---

   

7. You can drag and drop your Slack CA certificate files or click Browse to locate and choose the Slack certificate files from your device.

8. Click Save.

   The CA certificate that you added appears in the certificates table on the Certificate Management page.

   

Query using Slack slash commands

Once the integration setup is complete, you can use the slash commands directly within Slack to query.

As a sample query to test your Slack integration, you can use the following command to query an endpoint.

/get_endpoint_location <identifier> [maxResults]

For example, to query for an endpoint with the IP address 9.1.201.158 and retrieve a result, provide the following command.

/get_endpoint_location 9.1.201.158 1

When you execute the command, you receive a comprehensive JSON-formatted response containing various details about the endpoint.

Troubleshoot Slack integration

This section provides guidance on resolving common anomalies that may arise with your Slack integration on Nexus Dashboard.

You can find the anomalies related to Slack integration in Nexus Dashboard under system anomalies. For more information, see View platform and system alerts in global anomalies table.