Demonstration Guide
Cisco dCloud
Intro to Multicast Sandbox Demo
Last Updated: 22-March-2021
About This Demo
This guide for the preconfigured demonstration includes:
About This Demo 1
Getting Started 4
Scenario 1. Starting the Multicast Demo Topology 5
Troubleshooting 8
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 8
Demonstration Guide
Cisco dCloud
Limitations
This demo is virtual and uses VIRL with IOSv. There are no Nexus devices and so Anycast with PIM is not
supported.
Topology
This content includes preconfigured users and components to illustrate the features of the solution. Most
components are fully configurable with predefined user accounts. You can see the IP address and user account
credentials to use to access a component by clicking the component icon in the Topology menu of your active
session. Only wkst1 is accessible via Remote Desktop.
dCloud Topology
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 2 of 8
Demonstration Guide
Cisco dCloud
Physical Topology
Equipment Details
Name Description Host Name (FQDN) IP Address Username Password
Wkst1 Admin Workstation Wkst1.dcloud.cisco.com 198.18.133.36 demo C1sco12345
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 3 of 8
Demonstration Guide
Cisco dCloud
Getting Started
Follow the steps to schedule a session of the content.
1. Initiate your dCloud session. [Show Me How]
NOTE: It may take up to 15 minutes for your session to become active.
2. For best performance, connect to the workstation with Cisco AnyConnect VPN [Show Me How] and the
local RDP client on your laptop [Show Me How]
• Workstation 1: 198.18.133.36, Username: demo, Password: C1sco12345
3. If AnyConnect is not an option, use the Web RDP session by doing the following:
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 4 of 8
Demonstration Guide
Cisco dCloud
Scenario 1. Starting the Multicast Demo Topology
1. Log into Wkst1 machine via Remote Desktop with AnyConnect or Web RDP
2. After logging in, please wait up to 5 minutes for the following:
• Putty Connection Manager to load
• Flask App to start (Please do not cancel/quit this window, keep it minimized)
• Google Chrome to open
3. Select which multicast solution you wish to be loaded as seen below:
4. Be patient after selecting! This process will take about 3 minutes and will show the following when
successful:
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 5 of 8
Demonstration Guide
Cisco dCloud
5. The devices are loading at this point. After about 3-5 minutes, you can open Putty CM and should have
access to each device.
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 6 of 8
Demonstration Guide
Cisco dCloud
Note: You might have to hit Enter a few times after connecting to get the console.
6. That’s it! You can now investigate configurations and start your own traffic generation. To start a multicast
source sending:
a. Log into Server-1 or Server-2.
b. Ping [Multicast group IP] (239.1.2.3 as an example) repeat 10000 – this will ensure that multicast
traffic is being sent to the group for a good long while.
7. To start a receiver’s IGMP Any-Source Multicast Report:
a. Log into Receiver-1 or Receiver-2.
b. Enter configuration mode with config t
• interface Gig0/0
• ip igmp join-group (multicast group IP)
8. To do SSM, use the SSM topology for reference. It has IGMPv3 configured on the receivers already.
9. The Sandbox Topology has multicast enabled, but is what you should use if you want to configure specific
solutions on your own such as SSM, Anycast, etc.
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 7 of 8
Demonstration Guide
Cisco dCloud
Troubleshooting
• If Google Chrome does not immediately show the Multicast Toplogy menu, be patient! It takes about two
minute for the menu to load after you first log in. In fact, Chrome should start on its own when the menu is
ready.
• If the Flask app command window is accidentally cancelled/closed, the folder on the desktop BRKIPM-1261
contains a batch file to restart it, as well as the VIRL topology files used in this demo.
• There is no external access to the VIRL appliance or automation which bootstraps the VIRL topologies.
Please feel free to use the topologies as created to learn and practice multicast!
• If you have any feedback, please open a ticket with the dCloud support team.
© 2019 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 8 of 8
