Table of Contents Introduction ............................................................................................................................................. 2 How to book the LAB? ............................................................................................................................. 3 Using Remote Desktop ............................................................................................................................ 3 Using VIA ................................................................................................................................................. 6 LAB Infrastructure ................................................................................................................................... 8
Network diagram ................................................................................................................................. 9 Video Server and Client access ............................................................................................................ 9 Switch console access (Command Line Interface) ............................................................................ 10 Equipment IP addresses & Credentials ............................................................................................. 11
Preparing for the LAB ............................................................................................................................ 13 Verify that Switches are Powered ..................................................................................................... 13 Reloading from Pre-Configured Directory (Easy Way) ...................................................................... 15 Starting from Scratch (Hard Way) ..................................................................................................... 16
Usernames, Addresses and Passwords ................................................................................................. 21 Contacts ................................................................................................................................................. 22
This document contains the necessary information to connect, manage and deliver the demos contained in the SPB SE Remote Lab Environment. All information is subject to change as and when the demos are expanded and additional demos put in place. Please check with the content owners if in doubt and for the latest version. Please feel free to send any improvements of ideas to the central team (contact details at end of this document). Always make sure to download the most current version of this document. This LAB can be accessed through a Remote Desktop session or a VPN session, using the VIA client. VIA is recommended when connecting from a high latency location (i.e. outside of Europe).
Access is via the Microsoft Remote Desktop Connection application that will allow to have access to a rebound server equipped with all required tools (serial MobaXterm terminal, Chrome browser and VMware vSphere client). The process for access is as follows:
1. When on the eDemo Shortest Path Bridging dedicated web page (http://edemo.al-mydemo.com/?page_id=2426):
a. click on the “→ Register and book a demo” link b. fill in the required fields (marked with an *)
i. the calendar can help selecting the wished demo timeslot ii. a 5 working days delay shall be considered
iii. “Email” and “ALE email contact” information may be the same if the demo is requested by an ALE employee, or different if the demo is requested by a non ALE employee.
iv. The “Zone” in which the demo will be run (EMEA, APAC, NAR, CALA) is needed to allocate the relevant support for the demonstration
c. Click on the “Submit” button
Using Remote Desktop
When the demonstration request is approved, you receive a mail confirming the demonstration availability for the wished timeslot. The mail also includes a Microsoft Remote Desktop Connection “Shortest Path Bridging.RDP” file and an
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
WARNING: Ensure that the correct keyboard layout is selected by clicking on the language shortcut at the bottom right of the screen! Today, the options are French and US EN.
If using this demo from a location with high latency (i.e. outside Europe), Remote Desktop may not be very responsive. For this reason, we provide an option to access this demo using the VIA client.
1. Download the VIA client here: http://edemo.al-mydemo.com/bin/ansetup64.msi
2. Make sure your device is connected to the Internet trough DSL, LTE, etc. TCP Port 443 and UDP Port 4500 must be allowed through the Firewall for VIA to work.
3. Install the VIA client. 4. Once installed, launch the VIA client and configure as follows.
a. Remote Server: gatewlan.al-mydemo.com b. Username: <your username from Step 1> c. Password: <your password from Step 1>
5. Press the “Login” button.
6. A Security Alert message may be displayed, click “Yes” to accept.
9. You will be prompted to enter your credentials once again, please provide the information and click “Ok”.
10. VIA will automatically connect and minimize to the status bar. You can look for the icon and double click to check the status of your connection. A successful connection will be displayed as “Established” as in the example below and here you can check the IP address of your client.
When connecting through VIA, you will need to install the following components on your own PC. It is recommended that you download these tools before connecting through VIA:
o You will need to set up the connections to the switch consoles as explained in Table 1.
o You can use the “Split” button to arrange all 4 consoles in a tiled pattern.
VmWare Vsphere Client: https://kb.vmware.com/s/article/2089791 o Version 6 is recommended o When launching the connection for the first time, it will complain
about the certificate. Tick to accept saving and click “Ignore”
The following diagram shows the layout of the LAB:
The infrastructure is built around a Windows “rebound server” equipped with a VMware ESXi hypervisor hosting two (2) virtual machines: Video server Video client
The Video server and Video client are respectively connected to the TOR1, and TOR2 switches.
Video Server and Client access
Access to the Video server and the Video client is done from the rebound server through a VMware vSphere client that allows connecting to the ESXi hypervisor:
Once connected, vSphere displays both the video client and server virtual machines, and a right-click allows opening a console:
Switch console access (Command Line Interface)
The serial console port of each switch is connected to a console server that allows access to the CLI of each switch, during the reboot process of the switches and after the reboot in order to issue key commands.
Note 1: It may happen sometimes that the previous user has removed the terminal configuration from Moba Xterm (please don’t be that kind of user ). In such case, the configuration can be added with the information below.
Table 1 - Switch Console Connection Data
CORE1 CORE2 TOR1 TOR2
IP 10.243.1.1 10.243.1.1 10.243.1.1 10.243.1.1
PORT 10001 10002 10003 10004
Note 2: It may also happen sometimes that another user has hijacked the remote console sessions. A “line busy” message will be displayed. If so, you will need to reset the sessions as explained below.
1. From Moba Xterm, telnet to 10.243.1.1 on standard port (23) 2. Login using admin/raritan credentials 3. Kill each session with commands below:
kill line 1
kill line 2
kill line 3
kill line 4 After completing this step, you can connect to the switch consoles per Table 1.
The easy way: reloading from a pre-configured directory
The hard way: starting from scratch Instructions are given below for both of these options. When finished, verify that pings between client and server are successful and that video streaming is operational.
Verify that Switches are Powered
Since this Lab shares infrastructure with the iFab demo, there is a chance that the previous user may have cut power to some switches. So we will connect to the Power Control Unit make sure that all 4 switches are powered on. Access to the PDU GUI has been pre-configured with a shortcut on the rebound server desktop. Double click on the “PDU Access” shortcut to open the PDU GUI on screen
#1. Or, if connected through VIA, launch your local browser:
Click on “Advanced” to bypass the security certificate warning
Verify that outlets for all 4 switches (CORE-1, CORE-2, TOR/Distrib-1, TOR/Distrib-2 are in the “On” state and if not, power them on by clicking on their checkbox and then on the “On” button at the bottom of the page.
Wait for the switch(es) to bootup before proceeding.
Reloading from Pre-Configured Directory (Easy Way)
Here we take advantage of the AOS multiple directories. Configuration files have already been created under the “spblab” directory in all 4 switches. It is assumed that the previous demo user booked the Intelligent Fabric demo and you will find that Core 1 and Core 2 switches have formed a Virtual Chassis. Core 1 is the Master and Core 2 is the Slave. Logon to Core 1 with credentials below and execute the commands in the snippet. It is important that you execute the command below on Core 1, not Core 2, because Core 1 is the VC Master. User: admin Password: switch
-> reload from spblab no rollback-timeout Confirm Activate (Y/N) : y
Repeat above commands on TOR1 and TOR2. Do not enter the above commands on CORE2 because it is the VC Slave. Once the bootup sequence is complete, logon to CORE2 and execute the commands below to change its system name to reflect the standalone configuration.
If you find that the switches were already running from the spblab directory, it is still recommended that you follow the above procedure in case the previous user made some (unsaved) configuration changes. If that’s the case, you can also individually reload CORE2 because it won’t be part of a VC. If you find that the demo/lab is in none of these two states, you can follow the instructions in the next section to start from scratch.
Starting from Scratch (Hard Way)
Alternatively, you can follow instructions below to restore factory default configuration. But you will need to abort the iFab auto-configuration during the bootup sequence in order to have a blank configuration and manually configure all 4 switches as shown in the snippets below. So pay attention to the bootup sequence and you may want to reload one switch at a time and not all 4 at once.
! Chassis: system name "CORE1" ! Interface: interfaces port 1/1/32A admin-state disable ! VLAN: spb bvlan 4001-4002 admin-state enable ! Ethernet-OAM: ethoam domain ALE format string level 3 ethoam domain ALE mhf default ethoam domain ALE id-permission chassisid ethoam association BVLAN4001 format string domain ALE ethoam association BVLAN4001 domain ALE primary-vlan 4001 ethoam association BVLAN4001 domain ALE mhf default ethoam association BVLAN4001 domain ALE id-permission chassisid ethoam association BVLAN4001 domain ALE ccm-interval interval1s ethoam association BVLAN4001 domain ALE endpoint-list 21-24 ethoam association BVLAN4002 format string domain ALE ethoam association BVLAN4002 domain ALE primary-vlan 4002 ethoam association BVLAN4002 domain ALE mhf default ethoam association BVLAN4002 domain ALE endpoint-list 31-34 ethoam endpoint 21 domain ALE association BVLAN4001 direction up port virtual primary-vlan 4001 ethoam endpoint 21 domain ALE association BVLAN4001 admin-state enable ethoam endpoint 21 domain ALE association BVLAN4001 priority 5 ethoam endpoint 21 domain ALE association BVLAN4001 lowest-defect-priority all-defect ethoam endpoint 31 domain ALE association BVLAN4002 direction up port virtual primary-vlan 4002 ethoam endpoint 31 domain ALE association BVLAN4002 admin-state enable ethoam endpoint 31 domain ALE association BVLAN4002 priority 5 ethoam endpoint 31 domain ALE association BVLAN4002 lowest-defect-priority all-defect ! SAA: saa spb auto-create auto-start ! SPB-ISIS: spb isis bvlan 4001 ect-id 1 spb isis bvlan 4002 ect-id 2 spb isis control-bvlan 4001 spb isis interface port 1/1/1A-1B spb isis interface port 1/1/31A spb isis admin-state enable
! Chassis: system name "CORE2" ! Interface: interfaces port 1/1/32A admin-state disable ! VLAN: spb bvlan 4001-4002 admin-state enable ! Ethernet-OAM: ethoam domain ALE format string level 3 ethoam domain ALE mhf default ethoam domain ALE id-permission chassisid ethoam association BVLAN4001 format string domain ALE ethoam association BVLAN4001 domain ALE primary-vlan 4001 ethoam association BVLAN4001 domain ALE mhf default ethoam association BVLAN4001 domain ALE id-permission chassisid ethoam association BVLAN4001 domain ALE ccm-interval interval1s ethoam association BVLAN4001 domain ALE endpoint-list 21-24 ethoam association BVLAN4002 format string domain ALE ethoam association BVLAN4002 domain ALE primary-vlan 4002 ethoam association BVLAN4002 domain ALE mhf default ethoam association BVLAN4002 domain ALE endpoint-list 31-34 ethoam endpoint 21 domain ALE association BVLAN4001 direction up port virtual primary-vlan 4001 ethoam endpoint 21 domain ALE association BVLAN4001 admin-state enable ethoam endpoint 21 domain ALE association BVLAN4001 priority 5 ethoam endpoint 21 domain ALE association BVLAN4001 lowest-defect-priority all-defect ethoam endpoint 31 domain ALE association BVLAN4002 direction up port virtual primary-vlan 4002 ethoam endpoint 31 domain ALE association BVLAN4002 admin-state enable ethoam endpoint 31 domain ALE association BVLAN4002 priority 5 ethoam endpoint 31 domain ALE association BVLAN4002 lowest-defect-priority all-defect ! SAA: saa spb auto-create auto-start ! SPB-ISIS: spb isis bvlan 4001 ect-id 1 spb isis bvlan 4002 ect-id 2 spb isis control-bvlan 4001 spb isis interface port 1/1/1A-1B spb isis interface port 1/1/31A spb isis admin-state enable
! Chassis: system name "TOR1" ! VLAN: spb bvlan 4001-4002 admin-state enable ! Ethernet-OAM: ethoam domain ALE format string level 3 ethoam domain ALE mhf default ethoam domain ALE id-permission chassisid ethoam association BVLAN4001 format string domain ALE ethoam association BVLAN4001 domain ALE primary-vlan 4001 ethoam association BVLAN4001 domain ALE mhf default ethoam association BVLAN4001 domain ALE id-permission chassisid ethoam association BVLAN4001 domain ALE ccm-interval interval1s ethoam association BVLAN4001 domain ALE endpoint-list 21-24 ethoam association BVLAN4002 format string domain ALE ethoam association BVLAN4002 domain ALE primary-vlan 4002 ethoam association BVLAN4002 domain ALE mhf default ethoam association BVLAN4002 domain ALE endpoint-list 31-34 ethoam endpoint 21 domain ALE association BVLAN4001 direction up port virtual primary-vlan 4001 ethoam endpoint 21 domain ALE association BVLAN4001 admin-state enable ethoam endpoint 21 domain ALE association BVLAN4001 priority 5 ethoam endpoint 21 domain ALE association BVLAN4001 lowest-defect-priority all-defect ethoam endpoint 31 domain ALE association BVLAN4002 direction up port virtual primary-vlan 4002 ethoam endpoint 31 domain ALE association BVLAN4002 admin-state enable ethoam endpoint 31 domain ALE association BVLAN4002 priority 5 ethoam endpoint 31 domain ALE association BVLAN4002 lowest-defect-priority all-defect ! SAA: saa spb auto-create auto-start ! SPB-ISIS: spb isis bvlan 4001 ect-id 1 spb isis bvlan 4002 ect-id 2 spb isis control-bvlan 4001 spb isis interface port 1/1/47-48 spb isis admin-state enable ! SVCMGR: service access port 1/1/1 service access port 1/1/2 service 1 spb isid 1001 bvlan 4001 stats enable service 2 spb isid 1002 bvlan 4002 stats enable service 1 sap port 1/1/1:1001 service 2 sap port 1/1/2:1002
! Chassis: system name "TOR2" ! VLAN: spb bvlan 4001-4002 admin-state enable ! Ethernet-OAM: ethoam domain ALE format string level 3 ethoam domain ALE mhf default ethoam domain ALE id-permission chassisid ethoam association BVLAN4001 format string domain ALE ethoam association BVLAN4001 domain ALE primary-vlan 4001 ethoam association BVLAN4001 domain ALE mhf default ethoam association BVLAN4001 domain ALE id-permission chassisid ethoam association BVLAN4001 domain ALE ccm-interval interval1s ethoam association BVLAN4001 domain ALE endpoint-list 21-24 ethoam association BVLAN4002 format string domain ALE ethoam association BVLAN4002 domain ALE primary-vlan 4002 ethoam association BVLAN4002 domain ALE mhf default ethoam association BVLAN4002 domain ALE endpoint-list 31-34 ethoam endpoint 21 domain ALE association BVLAN4001 direction up port virtual primary-vlan 4001 ethoam endpoint 21 domain ALE association BVLAN4001 admin-state enable ethoam endpoint 21 domain ALE association BVLAN4001 priority 5 ethoam endpoint 21 domain ALE association BVLAN4001 lowest-defect-priority all-defect ethoam endpoint 31 domain ALE association BVLAN4002 direction up port virtual primary-vlan 4002 ethoam endpoint 31 domain ALE association BVLAN4002 admin-state enable ethoam endpoint 31 domain ALE association BVLAN4002 priority 5 ethoam endpoint 31 domain ALE association BVLAN4002 lowest-defect-priority all-defect ! SAA: saa spb auto-create auto-start ! SPB-ISIS: spb isis bvlan 4001 ect-id 1 spb isis bvlan 4002 ect-id 2 spb isis control-bvlan 4001 spb isis interface port 1/1/47-48 spb isis admin-state enable ! SVCMGR: service access port 1/1/1 service access port 1/1/2 service 1 spb isid 1001 bvlan 4001 stats enable service 2 spb isid 1002 bvlan 4002 stats enable service 1 sap port 1/1/1:1001 service 2 sap port 1/1/2:1002
