SDN Starter Kit Quick Start Guide

SDN Starter Kit Quick Start Guide v2015.1

[email protected]

[email protected] 12/16/15

Introduction ................................................................................................................................................................. 3 Ordering ....................................................................................................................................................................... 3 Sample Topology .......................................................................................................................................................... 4 CloudVision Exchange (CVX) Setup ............................................................................................................................... 4

Deploying CloudVision Exchange on ESX ........................................................................................................................... 4 Configure the CVX CLI ........................................................................................................................................................ 9 Verify CVX Server connection to Clients ........................................................................................................................... 11

CloudVision Portal (CVP) Setup .................................................................................................................................. 12 Deploying the CVP OVA on ESX ....................................................................................................................................... 12 Configure the CVP Shell ................................................................................................................................................... 16

Additional Requirements ........................................................................................................................................... 17 Verify basic network connectivity .................................................................................................................................... 17 Attach Console & Obtain MACs ....................................................................................................................................... 17 Activate DHCP Server ...................................................................................................................................................... 18 Configure CVP to run in single node topology ................................................................................................................. 19 Upgrade EOS to Minimum Supported Version (if necessary) .......................................................................................... 19

Getting Started .......................................................................................................................................................... 21 Home Page ...................................................................................................................................................................... 22 Network Provisioning ...................................................................................................................................................... 23 Inventory ......................................................................................................................................................................... 26 Tasks ................................................................................................................................................................................ 27 Configlets ......................................................................................................................................................................... 27 Images ............................................................................................................................................................................. 29 Tap Aggregation .............................................................................................................................................................. 31

Appendix A: Configlets ............................................................................................................................................... 31


Introduction

The SDN Starter Kit includes two Arista 7050-‐series switches and CloudVision licenses. It is intended to provide an introduction to Arista Networks switches, Extensible Operating System (EOS) and recently released CloudVision management. Key CloudVision features include point and click interface to simplify bulk tasks, turnkey solutions for automating network operations, automated software upgrades across groups of devices and snapshot of pre-‐ and post-‐changes for improved change control among others. This Quick Start serves as an abridged version of the full CloudVision Configuration Guide with an additional sample topology and configurations to quickly and easily get a test lab environment operational.

Ordering Material Code

(Switch, Licenses) Product Description

BND-‐7050S-‐64-‐F Arista SDN Starter Kit: 2 x 7050S-‐64-‐F, 24 x 1M-‐NBD, 24 x CV-‐SWITCH-‐1M BND-‐7050S-‐64-‐R Arista SDN Starter Kit: 2 x 7050S-‐64-‐R, 24 x 1M-‐NBD, 24 x CV-‐SWITCH-‐1M BND-‐7050T-‐64-‐F Arista SDN Starter Kit: 2 x 7050T-‐64-‐F, 24 x 1M-‐NBD, 24 x CV-‐SWITCH-‐1M BND-‐7050T-‐64-‐R Arista SDN Starter Kit: 2 x 7050T-‐64-‐R, 24 x 1M-‐NBD, 24 x CV-‐SWITCH-‐1M BND-‐7050S-‐T-‐64-‐F Arista SDN Starter Kit: 1 x 7050S-‐64-‐F, 12 x 1M-‐NBD, 1 x 7050T-‐64-‐F, 12 x 1M-‐NBD, 24 x CV-‐SWITCH-‐1M BND-‐7050S-‐T-‐64-‐R Arista SDN Starter Kit: 1 x 7050S-‐64-‐R 12 x 1M-‐NBD, 1 x 7050T-‐64-‐R, 12 x 1M-‐NBD, 24 x CV-‐SWITCH-‐1M


Sample Topology

CloudVision Exchange (CVX) Setup Deploying CloudVision Exchange on ESX

1. Login to www.arista.com and navigate to Support > Software Download. Expand vEOS to download Aboot-‐veos-‐2.1.0.iso.

2. Expand Active Releases > 4.15 > EOS-‐4.15.2F to download EOS-‐4.15.2F.vmdk. 3. Load the Aboot-‐veos-‐2.1.0.iso and EOS-‐4.15.2F.vmdk files into a convenient filestore location within the

VMware vSphere environment.


4. Create a new virtual machine.

5. Select Create a new virtual machine and click Next”.


6. Assign a name and location for the new CVX Virtual Machine. Click Next.

7. Select a datastore for the Virtual Machine files. Click Next


8. Specify compatibility (e.g. VM Machine Version 10) and click “Next”.

9. Specify the Guest OS. Set Guest OS Family to Linux and Guest OS Family to Other Linux (64-‐bit). Click “Next”

when done.


10. Customize VM Hardware -‐ default values need to be modified to reflect the configuration below.

The following changes need be made the VM hardware setting:

• Modify CPU setting to “4” (Number of CPUs) • Modify Memory to “8 GB” • Delete current “New Hard Disk • Specify New Network connection to Network LAN segment with connectivity to CVX client devices (e.g

the Management LAN) -‐ this connection will be use for CVX client-‐server communications. • Modify the New CD/DVD Drive setting to “Datastore ISO File” and specify the Aboot-‐veos-‐2.1.0.iso from

Step 1. Ensure the Connect on boot box is ticked. • Create an “Existing Hard Disk” specifying EOS-‐4.15.2F.vmdk from Step 2. • Optionally, delete the floppy drive and SCSI controller.


Configure the CVX CLI 1. Open the Console session to the VM -‐ console will appear in new tab in web browser. Once the CVX VM has

booted successfully, login at the prompt (the same process as any Arista switch), enter configuration mode and cancel zerotouch provisioning. The switch will reboot.

2. Configure the system for basic connectivity. • Assign IP address to interface management. • Configure a default route if necessary. • Assign the hostname. • Create admin user and assign password etc.


3. Once complete, verify connectivity to other devices in the network by pinging to default gateway and any switches that will be connected to CVX. Note: Some or all CVX switches may be accessible until configured later in this guide.

4. The CVX server function is disabled by default. It is enabled with the following command:


5. Verify the CVX server is running.

6. Save the configuration to nvram using write memory.

Verify CVX Server connection to Clients Once both the CVX server and clients are configured you can verify that communications with all clients is operational using the following command. Note: Some or all CVX switches may be accessible until configured later in this guide.


CloudVision Portal (CVP) Setup Deploying the CVP OVA on ESX Deploying the CVP OVA file should be the first step in any setup. After the CVP OVA file is deployed, the user may chose between the two configuration methods for the CloudVision Portal (CVP).

1. Login to www.arista.com and navigate to Support > Software Download. Expand CloudVision Portal > 2015.1 to download cvp-‐2015.1.ova.

2. Optionally download and review Release Notes in CloudVisionPortal-‐2015.1-‐ReleaseNotes.pdf 3. The OVA file can be deployed as a VM in a VMware environment by using the drop menu under the Actions

heading and selecting Deploy OVF Template. * Note: The Deploy OVF Template requires VMWare Client Integration Plugin that is not supported in Chrome after versions 42.

4. Having selected the Deploy OVF Template option, VCenter will prompt for the location of the OVA file; this can be either on

a local hard disk, network share, or Internet URL. The location of the OVA file should be entered or selected.


Review OVA template details

Select name and folder location for OVA file


Select a resource

Select the destination storage


Setup the network

5. VCenter will then load the OVA and display the configuration settings as shown in the diagram below. These settings should be accepted by selecting the “Finish” button.

6. Having accepted the configuration options, VCenter will begin to deploy the virtual appliance. Once complete, proceed to configuration of the CVP application.


Configure the CVP Shell 1. Login to the virtual machine console as the cvpadmin user and configure ip parameters as prompted.

* Note: The cvpadmin user cannot ssh into a node and so the config shell is only available at the console. There is no password set by default. Also, the Linux cvpadmin user is independent from the CVP application’s cvpadmin user, each using independent credentials.

2. Verify and apply the CVP application configuration 3. Quit to exit the application configuration shell.


Additional Requirements Verify basic network connectivity

1. Login to the virtual machine console as the root user. * Note: The root password is not set as part of this example and is not set by default

2. Verify basic network connectivity by pinging the default gateway and a remote host. Confirm name resolution is

operational.

3. Troubleshoot as necessary to resolve basic server network connectivity.

Attach Console & Obtain MACs 1. Attach a console to each switch and obtain the MAC address of the Management1 interface. This will be the

source of the dhcp request during the zero touch provisioning (ZTP) process. To avoid confusion, manual bindings will be created to clearly identify and label LEAF1a and LEAF1b.

2. Leave the console attached as it may be required later to upgrade EOS to Minimum Supported Version


Activate DHCP Server Activation and configuration of the CVP dhcp server is only required if an alternate dhcp server doesn’t already exist. If there is an existing server, modify the network management scope to return Option 67 bootfile-‐name as “"http://10.255.249.15/ztp/bootstrap" where 10.255.249.15 is the address of the CVP server.

1. Edit the /etc/dhcp/dhcpd.conf file to include the desired IP address, MAC address obtained above and option bootfile-‐name, which starts the ZTP process between CVP and the device.

2. Restart the DHCP service after any config changes with the service dhcpd restart command. 3. Configure dhcpd to start on system boot with the chkconfig dhcpd on command.


Configure CVP to run in single node topology By default, CVP assumes it is multinode configuration. As a result, hadoop and/or hbase may fail to start using the service cvp start command. Edit the /etc/cvp.conf file and remove the hostname and IP address or under multinode configuration to resolve this issue.

1. Modify /etc/cvp.conf.

Upgrade EOS to Minimum Supported Version (if necessary) The Starter Kit 7050-‐series switches may ship with a stock EOS software version that is not recognized by CloudVision Portal. CVP requires EOS 4.14.8M or newer.

2. From the switch console, use show version to display the running EOS version.

3. If the switch is running an EOS software version prior to 4.14.8M, login to www.arista.com and navigate to

Support > Software Download. Expand Active Releases > 4.15 > EOS-‐4.15.2F to download EOS-‐4.15.2F.swi. 4. Optionally download and review Release Notes in RN-‐4.15.2F.pdf.


5. Assign a temporary password for the admin user and enable exec authorization to permit scp connectivity.

6. Copy EOS-‐4.15.2F.swi to the /mnt/flash directory via scp.


7. Configure the switch to boot the new EOS image and reload to restart the zero-‐touch provisioning process. DO NOT save the configuration to nvram prior to the reload.

Getting Started The CVP application is accessible after the CVP service has been started on the appliance, the login screen will be presented when you first attach to it with a web browser. * Note: Safari browser not supported as of CVP 2015.1.

1. To access the login page, point your browser to the CloudVision Portal (http://cvp.lab.local or https://cvp.lab.local).

2. For the purposes of this Quick Start, local authentication and authorization were defined in the CVP Shell configuration. Login initially using cvpadmin, password cvpadmin. Change the password as prompted after successful login.


Home Page

The home page provides the following selections: • Network Provisioning: Hierarchical Tree structure of the network is maintained here. All the configuration and

image assignment to the network switches are made via this module • Configlet Management: Configlet management consists of inventory of all the configlets in CloudVision. The

Configlets can be created, edited and deleted via this module. • Image Management: Image Management module holds inventory of all the images used in the CloudVision.

Images are uploaded via this module to CloudVision server. • Task Management: Tasks created in CloudVision are executed in Task Management module. • Inventory: All the devices managed by CloudVision are listed under the inventory module. The option to import

live devices to be controlled by CloudVision. • Tap Aggregation: All the TAP Aggregation enabled devices in CloudVision are listed in this module. Users can

access the TAP AGG -‐ GUI portal of the selected device via this module. • User Management: Network admin can create and manage network users with this module. • Label Management: All the labels created in the application (system and custom) are maintained in this module. • AAA Settings: Server details for Authentication and Authorization are defined in this module.


Network Provisioning The Network Provisioning Screen presents a hierarchical view of the network configuration. It is not a network topology; it is a configuration tree view. The switches at the bottom of the tree inherit the configuration specified in the containers above them as well as the configuration that is specific to them. The containers and switches all have sub menus that are accessed by right mouse clicking on them. The main features of the screen are described below. Note: Switches that have been added to the network from new will ZTP boot using generic details from CVP and appear in the "Undefined" container.

Network Provisioning Screen Options The following options are available from the Network Provisioning screen.

• Device Management -‐ Lists all the switches that reside below the selected container level, these could belong to the selected container or reside in sub-‐containers.

• Configlet Management -‐ Lists the configlets associated with the selected container or if a switch is selected all of the configlets applied to it both directly and inherited.

• Image Management -‐ Lists the EOS or vEOS software image associated with a container or switch. • Switches below the container selected will be loaded with this image. • Label Management -‐ Lists the system or custom labels associated with the selected container or switch. • Refresh and Listview -‐ Refresh the current screen to show any updates or changes to the switches or devices.

Listview changes the display from Topology View and displays the switches in a list. • Containers -‐ Provide the basis of the logical construct which is the topology view. They provide the structure to

group devices, apply configurations, and deploy images.


Container Right Click Options • Show From Here -‐ Changes the display to show only the containers and switches below the selected container. • Expand / Collapse -‐ toggles between shrinking or growing the tree topology below the selected container. • Show All Devices -‐ Lists the switches that are associated with that specific container. The container turns blue if

it contains more than five switches and will only display 5 of total number of switches in the topology structure. • Container: Add / Delete -‐ Create or remove a container that from the selected container. • Device: Add / Manage -‐ Add a device to the selected container or "manage" the switches already associated with

the container. The manage option displays a list of switches which can be selected by enabling the tick box on the lefthand side. The selected switches can then be moved to another container, reset (returned to a ZTP boot state and associated with the "undefined" container), or removed from CVP completely.

• Manage: Configlet / Image Bundle -‐ Allocate or remove a configlet or Image to or from a switch or container. • View Config -‐ View the configuration created from the combined configlets. At the container level this shows the

combined configlet configuration associated with that container Device Right Click Options

• Manage: Configlet / Image Bundle -‐ Allocate or remove a configlet or Image to or from a switch or container. • Labels -‐ Lists / assigns the user created labels associated with the selected switch. • View Config -‐ View the configuration created from the combined configlets. At the switch level the entire

configuration that will be applied to the switch is shown. • Move -‐ Allows a user to move a switch from one container to another. • Show Here -‐ Displays the topology with the selected container as the root. • Reset -‐ Erases the configuration on the switch then ZTP boots it. This will return it to the undefined container on

the provisioning screen. • Remove -‐ Removes the switch from CVP. This stops CVP making changes to it and tracking its configuration. The

switch is left running with its current configuration on it. • Check Compliance -‐ compares the current running configuration on the switch against the designed

configuration in CVP. If they are out of sync the device change to an orange color.

Container Actions

Creating a Container To create a container:

1. Select a parent container 2. Right click > Container > Add


3. Enter the name of the container and select to create a container. Create a LEAF container for this topology.

4. Click to apply the changes. Device Actions

Device Bootstrap Process Unprovisioned devices will boot up in ZeroTouch Provisioning mode, register themselves with the CloudVision Portal, and await configurations in the Undefined Container.

• Unprovisioned devices boot into ZeroTouch Provisioning mode and send out a DHCP request. • The DHCP server then assigns the device an IP Address and returns a URL pointing to the CloudVision portal in the

bootfile-‐name option. The URL to specify is http://10.255.249.15/ztp/bootstrap. • The device executes this bootstrap script and registers itself with the CloudVision Portal. At this point, the device is

available in the Undefined Container. • The user can now add the device to the appropriate container and apply the correct image and configuration, as

described in more detail below

Adding a Device from the Undefined Container

The device can be added to a given container from an undefined container.

1. Select a device from undefined container. Select and move LEAF1a to the LEAF container for this topology. 2. Right click > Move. This will show a popup listing all the containers in the topology.

3. Select the destination container, and click to propose the Add.

4. Repeat to move LEAF1b to the LEAF container.

5. the session. This will span Device Add task. 6. Execute the device add task in Task Management to add the device to destination container.


Managing Configurations Users can assign configuration to specific devices or containers. Configuration assigned to the container will be applied to all the devices under the container's hierarchy.

Applying Configuration to a Container

Configlets can be added to or removed from the container. 1. Select the LEAF container > Manage > Configlets.

2. This will open the window display the inventory of configlets. 3. Select or remove configlets. Apply all configlets except for interfaces-‐l3-‐

leaf1a and interfaces-‐l3-‐leaf1b to the LEAF container.

4. Select

Applying Configuration to a Device 1. Select the device > Manage> Configlets. This loads the configlet inventory page. 2. Select configlets to apply. For this topology, apply interfaces-‐l3-‐leaf1a to LEAF1a in addition to the configlets inherited

from the parent LEAF container. You will be required to validate the configuration.

3. Select . The validation page will be loaded.

4. Select to propose a “Config Assign” action. When saving the session, this will spawn a “Config Assign” task. 5. Repeat and apply interfaces-‐l3-‐leaf1b configlet to LEAF1b in addition to the configlets inherited from the parent LEAF

container. Inventory The Inventory page list all the devices managed by the CloudVision Portal. New devices can be imported and existing devices may be deleted from this page.


Tasks Task Management is an inventory of all the tasks spawned in CloudVision. Users can execute a task or cancel a task in task management.

Any action that affects the performance of the device is spawned as a task. Actions include: • Configuration Assigning • Image Push • Device addition from undefined to defined container

Configlets Configlets are portion of configuration that CLOUDVISION user codes and maintains independently under configlet management inventory. These configlets can be later applied to devices or containers in the topology.

Configlet Management Page


Configlet Creation

1. Select the + icon in the grid. 2. This will load the configlet creation page. 3. Enter the configlet codes. Create the aaa-‐local configlet referenced in Appendix A.

4. Optionally the configlet syntax against any device in the CloudVision inventory from the Validate Device dropdown on the right.

a. When an error occurs, a message will be displayed in the Validation Result below the dropdown. b. Troubleshoot configlet syntax as required.

5. the configlet. 6. Repeat for all configlets referenced in Appendix A.

Configlet Information

The configlet information page consists of: • Summary • Logs • Change History • Applied Containers • Applied Devices


Images The Extended Operating System used by the switches is uploaded into CloudVision and details about them are maintained in the Image management Inventory.

Image Management The module facilitates the user to upload images to CloudVision that will later be assigned to containers or devices.


Create an Image Bundle 1. Select the “+” icon present in the grid. 2. This will load the bundle creation page. 3. A desired image can be searched and selected. 4. Select the image and click 'Add/Open' to complete the action.

5. Select to create a new bundle.

Bundle Information The Bundle information page consists of:

• Summary tab -‐ quick information about the Image bundle • Logs -‐ complete information on the image assignment to devices and execution details. • Applied Containers -‐ displays the details on the containers to which the bundle is assigned to and the name of

the user who assigned it. • Applied Devices -‐ displays the details on the devices to which the bundle is assigned to and the name of the user

who assigned it.


Tap Aggregation Arista EOS provides unprecedented visibility for rapidly identifying and troubleshooting application and performance problems with tracers such as VM Tracer and MapReduce Tracer. EOS integrates with Apache Hadoop systems to track big data workloads, aggregates and monitors business critical applications across thousands of devices, and provides deep visibility and integration with virtualization platforms such as VMware vSphere.

Arista EOS also simplifies Tap Aggregation with the Arista Data Analyzer (DANZ) feature set. For organizations with compliance requirements to aggregate and capture traffic, Arista EOS enables traffic collection at high data volumes with minimal infrastructure investment and without impacting network performance.

The Arista EOS CloudVision platform further enhances network visibility through a network-‐wide database approach. By consolidating the network state to a central database, the network operator can visualize the environment.

Unfortunately, the SDN Starter kit does not support this feature. Platforms which support Tap Aggregation include 7150S, 7280SE and 7500E-‐series switches.

Appendix A: Configlets aaa-‐local:

username admin privilege 15 secret 0 admin username cvpadmin role network-‐admin privilege 15 secret 0 arista2015 aaa authentication login default local aaa authorization exec default local aaa authorization commands all default local aaa authorization console

alias:

alias cc clear counters alias senz show interface counter error | nz alias sbfd sh bfd neighbors | grep -‐i -‐c up alias snz show interface counter | nz alias sqnz show interface counter queue | nz alias srnz show interface counter rate | nz

banners:

banner login ===================================================================== UNAUTHORIZED ACCESS PROHIBITED. ===================================================================== EOF ! banner motd ===================================================================== Welcome to the Arista Networks SDN Lab. ===================================================================== EOF


interfaces-‐l2-‐leaf1: vlan 101 state active name LAB-‐VLAN101 ! vlan 102 state active name LAB-‐VLAN102

interfaces-‐l3-‐leaf1a:

hostname LEAF1a ! interface management1 ip address 10.255.249.241/24 ! interface vlan4094 ip address 10.255.255.0/31 ! mlag configuration peer-‐address 10.255.255.1

interfaces-‐l3-‐leaf1b: hostname LEAF1b ! interface management1 ip address 10.255.249.242/24 ! interface vlan4094 ip address 10.255.255.1/31 ! mlag configuration peer-‐address 10.255.255.0

mgmt-‐console

management console idle-‐timeout 10

mgmt.-‐cvx management cvx server host 10.255.249.240 no shutdown end

mgmt-‐eapi:

management api http-‐commands no shutdown

mgmt-‐ssh management ssh idle-‐timeout 10


mlag-‐enable: vlan 4094 name MLAG-‐LOCAL trunk group MLAG-‐PEER state active ! no spanning-‐tree vlan 4094 ! interface vlan4094 description MLAG-‐LOCAL no autostate ! interface ethernet 49/1, 50/1 channel-‐group 200 mode on speed forced 40gfull no shutdown ! interface Port-‐Channel200 description MLAG-‐PEER-‐LINK switchport mode trunk switchport trunk group MLAG-‐PEER ! mlag configuration domain-‐id LEAF1 peer-‐link Port-‐Channel200 local-‐interface vlan4094

mlag-‐interface: interface ethernet1 description LAB-‐ESX1 channel-‐group 201 mode active no shutdown ! interface ethernet51/1 description LAB-‐SPINE1 channel-‐group 101 mode active no shutdown ! interface ethernet52/1 description LAB-‐SPINE2 channel-‐group 102 mode active no shutdown ! interface Port-‐Channel101 description LAB-‐SPINE1-‐CHANNEL switchport mode trunk switchport trunk allowed vlan 101-‐102 mlag 101 ! interface Port-‐Channel102 description LAB-‐SPINE2-‐CHANNEL


switchport mode trunk switchport trunk allowed vlan 101-‐102 mlag 102 ! interface Port-‐Channel201 description LAB-‐ESX1-‐CHANNEL switchport mode trunk switchport trunk allowed vlan 101-‐102 mlag 201

monitoring

ip name-‐server 10.255.249.13 ip domain-‐name lab.local ! logging console notifications logging monitor informational ! logging level AAA errors logging level ACCOUNTING errors logging level ACL errors logging level AGENT errors logging level ALE errors logging level ARP errors logging level BFD errors logging level BGP errors logging level CAPACITY errors logging level CAPI errors logging level CLEAR errors logging level DATAPLANE errors logging level DOT1X errors logging level ENVMON errors logging level ETH errors logging level EVENTMON errors logging level EXTENSION errors logging level FHRP errors logging level FLOW errors logging level FORWARDING errors logging level FRU errors logging level FWK errors logging level GMP errors logging level HARDWARE errors logging level IGMP errors logging level IGMPSNOOPING errors logging level INTF errors logging level IP6ROUTING errors logging level IRA errors logging level ISIS errors logging level KERNELFIB errors logging level LACP errors logging level LAG errors logging level LAUNCHER errors


logging level LINEPROTO errors logging level LLDP errors logging level LOGMGR errors logging level LOOPBACK errors logging level LOOPPROTECT errors logging level MAPREDUCEMONITOR errors logging level MDIO errors logging level MIRRORING errors logging level MLAG errors logging level MMODE errors logging level MROUTE errors logging level MRP errors logging level MSDP errors logging level MSRP errors logging level MVRP errors logging level NAT errors logging level OPENFLOW errors logging level OSPF errors logging level OSPF3 errors logging level PFC errors logging level PIM errors logging level PIMBSR errors logging level PORTSECURITY errors logging level PTP errors logging level PWRMGMT errors logging level QOS errors logging level QUEUEMONITOR errors logging level REACHABILITYMONITOR errors logging level REDUNDANCY errors logging level RIB errors logging level ROUTING errors logging level SECURITY errors logging level SERVERMONITOR errors logging level SPANTREE errors logging level STAGEMGR errors logging level SYS errors logging level SYSDB errors logging level TAPAGG errors logging level TCP errors logging level TRANSCEIVER errors logging level TUNNEL errors logging level VM errors logging level VMTRACERSESS errors logging level VMWAREVI errors logging level VMWAREVS errors logging level VRF errors logging level VRRP errors logging level VXLAN errors logging level XMPP errors logging level ZTP informational !


ntp server 0.us.pool.ntp.org ntp server 1.us.pool.ntp.org ntp server 2.us.pool.ntp.org ntp server 3.us.pool.ntp.org clock timezone PST8PDT

mst-‐pvst-‐interop

spanning-‐tree mst pvst border

prompt: prompt %H.%D{%H:%M:%S}%P ! %s -‐-‐ space character ! %t -‐-‐ tab character ! %% -‐-‐ percent character ! %D -‐-‐ time and date ! %D{f_char} -‐-‐ time and date, format specified by the BSD strftime (f_char) time conversion function. ! %H -‐-‐ host name ! %h -‐-‐ host name up to the first ?.? ! %P -‐-‐ extended command mode ! %p -‐-‐ command mode ! %r -‐-‐ redundancy status on modular systems ! %R -‐-‐ extended redundancy status on modular systems (includes status and slot number)

unused

interface ethernet2-‐48 description UNUSED shutdown

vmtracer-‐enable:

vmtracer session vcenter url https://vcenter.lab.local username vcadmin password arista2015

vmtracer-‐interface: interface ethernet1 vmtracer vmware-‐esx

SDN Starter Kit Quick Start Guide

Documents

Transcript of SDN Starter Kit Quick Start Guide