APIC-EM Bot

This Webex Teams bot shows the power of cross-architectural demos that illustrate Cisco’s “Better Together” message of combining different product types of Cisco’s wide product portfolio to develop rich and tightly integrated experiences. The APIC-EM Bot leverages Webex Teams and APIC-EM APIs to enable NetOps teams and Network admins to gain information and query their network infrastructure via Webex Teams.


Demo Instructions

This Webex Teams bot showcases the capabilities of Webex Teams, as well as APIC-EM. We can write requests in human language, and then get responses based on data from APIC-EM. This means that the bot allows to demo both Webex Teams and APIC-EM at the same time. Best of all, you don’t have to learn exact phrases to demo the bot! We can process your requests to the bot, so the question can still work, even if you ask it differently. This guide will show you what capabilities are currently available in the bot, so you can create an effective demo. After the scenarios, this guide also explains how the bot works.

There are 3 distinct use cases that can be leveraged from this integration:

1. What is going on in my network?

  • The APIC-EM Bot allows Network Admins to get a quick overview of the health of the network they manage.
  • Add the bot to a space or start a 1:1 conversation with it, the address is: [email protected]
  • Get familiar with its capabilities by typing “@[email protected] help”(for spaces) or simply “help”(for direct messages to the bot).
  • Query the bot about the network status by typing “@[email protected] What is the status of my network?” (space) or “What is the status of my network?” (direct).
  • You can also use any natural language variant of that phrase as the bot is integrated with API.AI (Now Dialog Flow) and understands Natural Language.
  • This bot will display both the status of our APIC-EM controller, as well as the status of the network devices. The APIC-EM controller can either be reachable/online, or unreachable/offline, which is represented by a green or red symbol. For the network devices, it is a little bit more complex, as some might be reachable and some might be unreachable. If most devices are reachable, we will have a green symbol, but if many devices are unreachable, we will either see a yellow or red symbol.
  • Furthermore, you can get additional information at the device level by querying the bot “what is wrong with my network devices?”. This will list the affected devices and their issue.

2. Troubleshooting a Device’s Network Connectivity

  • The APIC-EM Bot allows Network Admins to get information about the equipment that a particular device is connected to via the device’s IP address.
  • Add the bot to a space or start a 1:1 conversation with it, the address is: [email protected]
  • Get familiar with its capabilities by typing “@[email protected] help”(for spaces) or simply “help”(for direct messages to the bot).
  • Query the bot about the network status by typing “@[email protected] Where is 10.1.15.117 connected?” (space) or “Where is 10.1.15.117 connected?” (direct).
  • You can also use any natural language variant of that phrase as the bot is integrated with API.AI (Now Dialog Flow) and understands Natural Language.
  • This bot will display a connectivity map of that connection of that device’s IP and the equipment (AP) it is connected to. Now the NetOps admin can troubleshoot that particular equipment.

3. Expanding a Network

  • The APIC-EM Bot allows Network Admins to query the network and see where there are ports available for them to expand their network and add more equipment where possible.
  • Add the bot to a space or start a 1:1 conversation with it, the address is: [email protected]
  • Get familiar with its capabilities by typing “@[email protected] help”(for spaces) or simply “help”(for direct messages to the bot).
  • Query the bot about the network status by typing “@[email protected] I want to expand my network” (space) or “I want to expand my network” (direct).
  • You can also use any natural language variant of that phrase as the bot is integrated with API.AI (Now Dialog Flow) and understands Natural Language.
  • This bot will ask you first, what location you are querying it for and second, what type of device you are looking for.
  • When the bot asks you for a location, please either specify a location that is known to APIC-EM (for example, “Pasadena”, or just write “Any”, in which case we do not filter by location. Then, for the device type, you want to specify the kind of device where you want to look for available ports, for example, a “Distribution Switch”.
  • Examples for options would be some of the following: Core Switch, Distribution Switch, Access switch, Router
  • Note: Do not forget to mention the bot when specifying the location and the devices you want to look at for available ports, eg. “@[email protected] Pasadena”
  • The bot will return a list of result devices and their available ports. Please note that these are ports that are not active, but the port might have a cable plugged in that is not sending anything.

 


Built by Michael Maurer

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.