Intelligent Fabric SE Remote Demo Script

Table of Contents Introduction ............................................................................................................................................. 2 Equipment Requirements ....................................................................................................................... 2 Overview of the Demo ............................................................................................................................ 3

Step 1: Connect to the eDemo Environment ..................................................................................... 4 Step 2: Connect to the Video Server and Client ................................................................................ 6 Step 3: Connect to switches, and put them in an “out-of-the-box” state ........................................ 8 Step 4: Connect to the Power Distribution Unit and reboot the switches ..................................... 10 Step 5: Observe iFab process and issue key CLI commands ............................................................ 12

Contacts ................................................................................................................................................. 16

Introduction

This is a step-by-step guide on how to perform the Intelligent Fabric (iFab) Remote Demo, what to show the customer and what to say while doing it. It is strongly recommended that the reader is already familiar with the demo set-up (please refer to “SE iFab Remote Demo – Platform Information” document for further details).

CAUTION DO NOT MAKE ANY CONFIGURATION CHANGES TO THE REBOUND SERVER CONFIGURATION OR THE VIRTUAL MACHINES IT HOSTS (VIDEO SERVER AND VIDEO CLIENT). DOING SO WILL CHANGE THE BEHAVIOUR OF THE DEMO SETUP RENDERING IT USELESS FOR OTHERS.

Equipment Requirements

- One (1) PC It is recommended to have two (2) screens and extend the PC display to the additional screen. Having to switch between the Video Server and Client and tools involved in the demo scenario using one screen d (the PDU GUI for the remote power control, the switches console CLI via MobaXterm terminal...) will break up the demo flow’s flow and will not improve the audience’s demonstration experience. This demo script was written using ‘Windows 7’ as the Client PC OS. Warnings and options may differ if using another version of windows.

Overview of the Demo The demo flow is summarised as follows:

1. Connect to the central eDemo environment, and more specifically to the iFab dedicated rebound server

2. From the rebound server, connect with VMware vSphere client to the ESXi hypervisor hosting the Video Server and client virtual machines

3. Connect to the console port of the switches to put them in an “out-of-the-box” state (delete any configuration file) and to monitor the state of the switches during the demonstration

4. Connect to the Power Distribution Unit and switch on/off the switches (to initiate a rebooot)

5. Observe the effects of iFab and issue key CLI commands to high-light key points of the iFab demonstration

Step 1: Connect to the eDemo Environment

For additional information, refer to the “SE iFab Remote Demo – Platform Information” document. On screen #1, you should now be connected to the rebound server and see its Microsoft desktop with shortcuts to all elements needed to run and control the demonstration: Power Distribution Unit for the power control of the switches Video server streaming a video and Video client receiving the video CLI (Command Line Interface) of all switches

On screen #2, display the demo network diagram for illustration purposes:

What to say to the audience: “The objective of the demonstration is to show that the topology described here can be cabled up as shown, then powered up and pass customer traffic between two Virtual Machines (the Video Server and the Video Client) without a single CLI entry. Without any human intervention, just by connecting and powering on out-of-the-box switches, the Intelligent Fabric feature will allow you to automatically build a state-of-the-art network for a large campus or Data Center:

- CORE-1 and CORE-2 switches will establish a VFL (Virtual Fabric Link) and build a Virtual Chassis with the election of a master switch and a slave switch. A Virtual Chassis is a logical switch made up of several physical switches. The resulting logical equipment behaves as a single switch at the management, control and forwarding planes.

- The switches are smart enough to detect that they are doubly connected to each other. This triggers the building of LACP logical aggregated links between the CORE-1 and 2 on the one hand and TOR or distribution switches on the other. The logical links include several physical links with the benefits of additional bandwidth, more resiliency, and no physical loops to manage.

- A modern and advanced SPB-based core network is then established between the switches.

- The TOR or distribution switches will read the VLAN id of the data flow entering the network and configure an end-to-end SPB-based L2 VPN service by mapping this VLAN id to the SPB core service.”

Step 2: Connect to the Video Server and Client

Double click on the “VMware vSphere” client shortcut:

Connect to the ESXi Hypervisor hosting the Video Server/Client Virtual Machines:

IP 10.243.1.200

User name ifab

Password iF4b@Ale!

Ignore the Security Warning:

On the left hand side, expand the server to reveal the 2 VMs. Right-click

on each Virtual Machine and click on the “Open Console” contextual menu:

Organize both consoles on screen #1 for a comfortable display:

What to say to the audience: “You can see a live video displayed on the Video client and broadcasted from the Video server. You can also see successful pings between each machine.” If the pings and video are not “launched”, scripts have been configured and are available on the desktop of the server and the client:

On the server On the client

Step 3: Connect to switches, and put them in an “out-of-the-box” state

Double click on the “Console sessions to switches” shortcut (the console window may take 3 minutes to display):

Arrange the four console windows in a “mosaic” layout on screen #2 for a comfortable display:

On each switch, authenticate and delete any configuration file: Login admin

Password switch

What to say to the audience: “All switches are now in an out of the box state”.

Step 4: Connect to the Power Distribution Unit and reboot the switches

Double click on the “PDU Access” shortcut to open the PDU GUI on screen #1:

Click on “Advanced” to bypass the security certificate warning

Click on “Proceed to ...” to ignore the security certificate warning

Enter the login/password and click on “login” to connect:

User Name ifab

Password iF4b@Ale!

When connected, select the “Outlet” menu (1), tick CORE-1, CORE-2,

TOR/Distrib-1 and TOR/Distrib-2 switches (2), click on “Cycle” (3) and click on “Yes” (4) to confirm you want to reboot the switches and then close the PDU GUI:

What to say to the audience: “At Alcatel-Lucent Enterprise, we believe we have the right technology to reduce your network complexity, so you can introduce applications faster. This is called “Intelligent Fabric Technology”. iFab is supported on our OmniSwitch™ 10K and 6900 models. It enables streamlined operations and better application integration in both converged campus and data center networks. It provides IT with simpler design, easier deployment and simple moves, adds and changes.”

Step 5: Observe iFab process and issue key CLI commands

Switch back to the Video Server and Client consoles and validate that the Client has stopped receiving traffic and pings are down:

At the end of the reboot cycle (when the pings are successful again, and when the video is received on the client), or, better, during the reboot and at the end of the reboot, issue key commands to demonstrate the iFab process:

o on CORE-1 and CORE-2 switches:

show interfaces status: before completion of the Auto-Virtual-Chassis feature, the command can be issued on both switches. At the end of the Auto-Virtual-Chassis feature, the command is no longer possible on the slave switch. Moreover, slave switch interfaces are seen as additional interfaces (index 2) by the master switch.

Show virtual-chassis topology: shows the roles assigned to both core switches after election.

o On any switch: show linkagg (port) or show conf snapashot linkagg: even if

all configuration files have been previously deleted, LACP aggregated links are automatically created, and the associated configuration inserted

show spb isis interface, show conf snapshot spb-isis: the SPB protocol has been automatically configured and interfaces between switches now bind to the SPB protocol

show spb isis services: end-to-end SPB based L2 VPNs have been automatically built

o on TOR/DISTRIB-1 or TOR/DISTRIB-2 switches: show unp user: validate that TOR/Distribution switches have

read the IP/Mac addresses, the VLAN ID and have associated all information

What to say to the audience: “during the reboot process, the Video Client does not receive traffic and pings between both Virtual Machines fail. Then, with no human intervention, the iFab process is triggered, it re-builds the network as expected, by adding the relevant and needed configuration elements (Auto Virtual Chassis, LACP, SPB...). We hope you are now convinced by the value iFab can bring to our customers. iFab:

• Simplifies network operations • Improves agility of operations • Reduces IT expense, support costs and OPEX • Improves productivity and efficiency

How?

• network architects no longer need to be experts on every protocol thanks to auto-configuration

• deployment time and manual errors greatly reduced by automating network protocol configuration

• plug-n-play deployment and automation of moves/adds/changes

IDC Frontier, a cloud computing provider company was faced with the challenge of improving their operational efficiency, so they could grow the business. IDCF chose the Intelligent Fabric technology. The auto-provisioning capabilities helped provide a 44% improvement in the time it took to provision a new service across the network, resulting in significant OPEX savings. In addition, with the cost-effective capacity of the OmniSwitch 6900, they saw a greater than 50% CAPEX cost saving deploying 10GbE services. The flexible design of the OmniSwitch 6900 lets them scale up/down simply and easily, enabling them to redeploy systems to meet changing demands of their data centre customers with minimal overhead.”

When you have finished the demo, please close all windows to leave a clean environment for the next user.

Contacts

eDemo support team: edemo-support@al-enterprise.com