Host Console Access via IPMI

If you have a problem accessing the host externally, SSH into IPMI and access the host console.

The console redirect to serial over SSH, use an SSH client and complete the following steps.

  1. SSH into the IPMI and login with the root user and IPMI password. You will get a login similar to admin->
    This indicates you are in the IPMI SSH console.
  2. Execute the following commands: 
    racadm set BIOS.SerialCommSettings.SerialComm OnConRedirAuto
racadm set BIOS.SerialCommSettings.SerialPortAddress Serial1Com2Serial2Com1
racadm jobqueue create BIOS.Setup.1-1
racadm serveraction powercycle
    The IPMI should now be configured to access serial console.
  3. From the IPMI SSH interface run the command below to access the serial console: 
    console com2
  4. To return to the IPMI interface and disconnect from the console the default escape sequence is ^\ (CTRL+\) , or simply close the SSH window.

SNMP Monitoring Support

To locate the SNMP support page, go to iDRAC Settings > Network > Services.
Figure 1. SNMP page

Rack Installation

Use the following steps to assemble the racking rails and attaching the components to the system.

  1. Routing the Cables
    1. Locate the outer brackets on the interior sides of both rack flanges (1).

    2. Bundle the cables gently, pulling them clear of the system connectors to the left and right sides (2).

    3. Thread the hook and loop straps through the tooled slots on the outer brackets on each side of the system to secure the cable bundles (3).


  2. Removing the System From the Rack
    1. Locate the lock levers on the sides of the inner rails (1).

    2. Unlock each lever by rotating it up to its release position (2).

    3. Grasp the sides of the system fi rmly and pull it forward until the rail standoffs are at the front of the J-slots. Lift the system up and away from the rack and place it on a level surface (3).


  3. Installing the System in a Rack
    1. Pull the inner slide rails out of the rack until they lock into place (1).

    2. Locate the rear rail standoff on each side of the system and lower them into the rear J-slots on the slide assemblies (2).

    3. Rotate the system downward until all the rail standoffs are seated in the J-slots (3).

    4. Push the system inward until the lock levers click into place. Press the slide-release lock buttons on both rails and slide the system into the rack (4).


  4. Installing and Removing Tooled Rails (Threaded Hole Racks)
    1. Remove the pins from the front and rear mounting brackets using a fl at-tipped screwdriver (1).

    2. Pull and rotate the rail latch sub-assemblies to remove them from the mounting brackets (2).

    3. Attach the left and right mounting rails to the front vertical rack flanges using two pairs of screws (3).

    4. Slide the left and right back brackets forward against the rear vertical rack flanges and attach them using two pairs of screws (4).


  5. Installing and Removing Tool-less Rails (Square Hole or Round Hole Racks)

    1. Position the left and right rail end pieces labeled FRONT facing inward and orient each end piece to seat in the holes on the front side of the vertical rack flanges (1).

    2. Align each end piece in the bottom and top holes of the desired U spaces (2).

    3. Engage the back end of the rail until it fully seats on the vertical rack flange and the latch clicks into place. Repeat these steps to position and seat the front end piece on the vertical rack flange (3).

    4. To remove the rails, pull the latch release button on the end piece midpoint and unseat each rail (4).


  6. Identifying the Rail Kit Contents
    Locate the components for installing the rail kit assembly:

    • Two sliding rail assemblies (1)

    • Two hook and loop straps (2)


  7. Engaging and Releasing the Slam Latch
    Note:

    For systems not equipped with slam latches, secure the system using screws, as described in step C of this procedure.

    1. Facing the front, locate the slam latch on either side of the system (1).

    2. Th e latches engage automatically as the system is pushed into the rack and are released by pulling up on the latches (2).

    3. To secure the system for shipment in the rack or for other unstable environments, locate the hard-mount screw under each latch and tighten each screw with a #2 Phillips screwdriver (3).


Front Panel Features and Indicators

This appendix displays the front panel of the CloudVision appliance.

Figure 1. CloudVision appliance (front view)

  Indicator, Button, or Connector Description
1 Power-on indicator, power button

The power-on indicator lights when the system power is on. The power button controls the power supply output to the system.

Note: On ACPI-compliant operating systems, turning off the system using the power button causes the system to perform a graceful shutdown before power to the system is turned off.
2 NMI button

Used to troubleshoot software and device driver errors when running certain operating systems. This button can be pressed using the end of a paper clip.

Note: Use this button only if directed to do so by qualified support personnel.
3 System identification button

The identification buttons on the front and back panels can be used to locate a particular system within a rack. When one of these buttons is pressed, the system status indicator on the back flashes until one of the buttons is pressed again.

Press to toggle the system ID on and off. If the system stops responding during POST, press and hold the system ID button for more than five seconds to enter BIOS progress mode.

To reset the iDRAC (if not disabled in F2 iDRAC setup) press and hold the button for more than 15 seconds.
4 Video connector Allows you to connect a display to the system.
5 Diagnostic indicators The diagnostic indicator lights up to display error status.
6 LCD panel Displays system ID, status information, and system error messages.
7

USB management port/iDRAC managed USB port

The USB management port can function as a regular USB port or provide access to the iDRAC features.
8 USB connector

Allows you to connect USB devices to the system. The port is USB 2.0-compliant.
9 Information tag

A slide-out label panel which contains system information such as Service Tag, NIC, MAC address, and so on for your reference.
10 Hard drives Up to four 3.5 inch hot-swappable hard drives/SSDs.
11 Optical drive (optional) One optional slim SATA DVD-ROM drive or DVD+/-RW drive.

Left Control Panel View

Figure 2. Left Control Panel with Optional IPMI Quick Sync 2.0 Indicator

Item Indicator, button, or connector Icon Description
1 Status LED indicators N/A Indicate the status of the system.
2 System health and system ID indicator
Indicates the system health.
3 IPMI Quick Sync 2 wireless indicator (optional)
Note: IPMI Quick Sync 2 wireless indicator is available only on certain configurations.
Indicates if the IPMI Quick Sync 2 wireless option is activated. The Quick Sync 2 feature allows management of the system using mobile devices. This feature aggregates hardware/firmware inventory and various system level diagnostic/error information that can be used in troubleshooting the system. You can access system inventory, Lifecycle Controller logs or system logs, system health status, and also configure IPMI, BIOS, and networking parameters. You can also launch the virtual Keyboard, Video, and Mouse (KVM) viewer and virtual Kernel-based Virtual Machine (KVM), on a supported mobile device.

Right Control Panel View

Figure 3. Right Control Panel

 

Item 1 is the power button, indicates if the system is turned on or off.

Item 2 is the USB port, enables you to connect USB devices to the system.

Item 3 is the iDRAC Direct LED, indicates that the IPMI Direct port is connected.

Item 4 is the iDRAC Direct port, enables you to access the IPMI direct features.

Item Indicator or button Icon Description
1 Power button
Power ON, power OFF.
2 USB port
The USB ports are 4-pin, 2.0-compliant. This port enables you to connect USB devices to the system.
3 IPMI Direct LED N/A The IPMI Direct LED indicator lights up to indicate that the IPMI Direct port is actively connected to a device.
4 IPMI Direct port (Micro-AB USB)
The IPMI Direct (Micro-AB USB) port enables you to access the IPMI Direct (Micro-AB) features.

Back Panel Features and Indicators

This appendix displays the back panel of the Arista CloudEOS and vEOS Router Appliance.

Figure 1. Arista CloudEOS and vEOS Router Appliance (back view)
Table 1. Back-panel Features and Indicators
Number Indicator, Button, or Connector Description
1 Serial connector Allows you to connect a serial device to the system.
2 IPMI port (optional) Dedicated management port on the IPMI ports card.
3 Ethernet connector 1 Integrated 10/100/1000 Mbps NIC connector.
4 10G Port 1 Data Port 1
5 10G Port 2 Data Port 2
6 10G Port 3 Data Port 3
7 10G Port 4 Data Port 4
8 System identification button The identification buttons on the front and back panels can be used to locate a particular system within a rack. When one of these buttons is pressed, the system status indicator on the back flashes until one of the buttons is pressed again.

Press to toggle the system ID on and off. If the system stops responding during POST, press and hold the system ID button for more than five seconds to enter BIOS progress mode.

To reset the IPMI (if not disabled in F2 IPMI setup) press and hold the button for more than 15 seconds.
9 System identification connector Connects the optional system status indicator assembly through the optional cable management arm.
10 Video connector Allows you to connect a VGA display to the system.
11 USB connector Allow you to connect USB devices to the system. The port is USB 2.0-compliant.
12 USB connector Allow you to connect USB devices to the system. The port is USB 3.0-compliant.
13 Ethernet connector 2 Integrated 10/100/1000 Mbps NIC connector.
14 Ethernet connector 3 Port not used by CloudEOS and vEOS launcher scripts.
15 Ethernet connector 4 Port not used by CloudEOS and vEOS launcher scripts.
16 Power supply (PSU1 and PSU2) Up to two 550 W redundant AC power supplies.

Tools to Manage and Update Images

A number of tools are available to help manage and update images and insert ISO to the Virtual Machine (VM).

Upgrade the Host Image

Arista provides an ISO with all updated packages and a tool to mount the images ISO and upgrade the system.

Note: This process may reboot the CVA.

To upgrade the Host image, complete the following steps.

  1. Go to http://www.arista.com.
  2. Download the mfg tgz tools (arista-cv-<version>-mfg.tgz).
  3. Extract tar -xvf arista-cv-<version>-mfg.tgz. This ensures you have the new version of upgradeCva.py.
  4. Download the update ISO.
  5. Run the upgrade CV appliance tool. 
    ./upgradeCva.py -i <Arista Cva Update Iso>
$ ./upgradeCva.py -h 
usage: upgradeCva.py [-h] [-i ISO] [--fixNw] [-vm] [-f FORCE]

Upgrade CVA

optional arguments:
-h, --helpshow this help message and exit
-i ISO, --iso ISO Path to ISO
--fixNw Fixes CVA network config to what is expected Does not touch devicebr config.
-vm, --vm Used for CVA VM emulation - NOT for H/W CVA
-f FORCE, --force Forces the command. Skips user interaction

Single Node CloudEOS and vEOS Router Appliance

To upgrade a single node CVA, perform all the steps listed in Steps to Upgrade the CVA. After the CVA host comes up, and after rebooting the system from the last step of upgrade, allow 20 minutes for the CVP application to be accessible again.

Multi-Node CloudEOS and vEOS Router Appliance

Perform a rolling upgrade to update the CVA systems in multi-node configuration. Perform all the steps listed in section Steps to Upgrade the CVA from the start to finish on only one of the CVAs at a time. After the upgrade, wait for all the VMs, (CVP and CVX) to be fully up and running (CVP takes 20 minutes to be up from reboot). Verify that the CVP is accessible. After the verification, proceed to upgrade the second CVA host in a similar fashion and then the third CVA.

Note:Process only one CVA upgrade at a time in a multi-node system.

Steps to Upgrade the CVA

  1. Download the tools mfg tgz (arista-cv-<version>) from https://www.arista.com/en/. Locate the upgradeCva.py inside the tgz 
    tar -zxvf cvp-<version>-kvm.tgz
  2. Run the upgrade executable. 
    ./upgradeCva-<version> --force
    Note:The version can be verified after upgrade using the "version" command. 
    # version
CVA Version: 2.1.3.1

Status Indicators

LCD Panel Features

The system's LCD panel provides system information and status and error messages to indicate if the system is operating correctly or if the system needs attention.

The LCD back-light lights blue during normal operating conditions.

When the system needs attention, the LCD lights amber and displays an error code followed by descriptive text.

Note: If the system is connected to a power source and an error is detected, the LCD lights amber regardless of whether the system is turned on or off.

The LCD back-light turns OFF when the system is in standby mode and can be turned on by pressing either the Select, Left, or Right button on the LCD panel.

The LCD back-light remains OFF if LCD messaging is turned off through the IPMI utility, the LCD panel, or other tools.
Figure 1. LCD Panel Features

 

Table 1. LCD Panel Features Description
Item Button Description
1 Left Moves the cursor back in one-step increments.
2 Select Selects the menu item highlighted by the cursor.
3 Right Moves the cursor forward in one-step increments.
During message scrolling:
  • Press once to increase scrolling speed
  • Press again to return to the default scrolling speed
  • Press again to repeat the cycle
  • Press again to stop

Status LED indicators

Note: The indicators display solid amber if any error occurs.
Table 2. Status LED indicators and descriptionsItem 1 is the health indicator that indicates the health status of the system. The indicator turns solid blue if the system is turned on and in good health. The indicator flashes amber if the system is turned on or in standby, and if any issue occurs (for example, a failed fan or drive). Item 2 is the drive indicator that flashes amber if an error occurs related to drive. Item 3 is the electrical indicator that flashes amber if an electrical error occurs (for example, voltage out of range, or a failed power supply unit or voltage regulator). Item 4 is the temperature indicator that flashes amber if a thermal error occurs (for example, temperature out of range or fan failure). Item 5 is the memory indicator that flashes amber if a memory error occurs. Item 6 is the PCIe indicator that flashes amber if an error occurs related to PCIe card.
Icon Description Condition Corrective action

Drive indicator The indicator turns solid amber if there is a drive error.
  • Check the System Event Log to determine if the drive has an error.
  • Run the appropriate Online Diagnostics test. Restart the system and run embedded diagnostics (ePSA).
  • If the drives are configured in a RAID array, restart the system, and enter the host adapter configuration utility program.

Temperature indicator The indicator turns solid amber if the system experiences a thermal error (for example, the ambient temperature is out of range, or there is a fan failure). Ensure that none of the following conditions exist:
  • A cooling fan has been removed or has failed.
  • System cover, air shroud, memory module blank, or back filler bracket is removed.
  • Ambient temperature is too high.
  • External airflow is obstructed.

Electrical indicator The indicator turns solid amber if the system experiences an electrical error (for example, voltage out of range, or a failed power supply unit (PSU) or voltage regulator). Check the System Event Log or system messages for the specific issue. If it is due to a problem with the PSU, check the LED on the PSU. Reseat the PSU.

Memory indicator The indicator turns solid amber if a memory error occurs. Check the System Event Log or system messages for the location of the failed memory. Reseat the memory module.

PCIe indicator The indicator turns solid amber if a PCIe card experiences an error. Restart the system. Update any required drivers for the PCIe card. Reinstall the card.

IPMI Direct LED Indicator Codes

The IPMI Direct LED indicator lights up to indicate that the port is connected and is being used as a part of the IPMI system.

You can configure IPMI Direct by using a USB to micro USB (type AB) cable, which you can connect to your laptop or tablet. The following table describes IPMI Direct activity when the IPMI Direct port is active:

Table 3. IPMI Direct LED Indicator CodesThe IPMI Direct LED indicator codes table describes the IPMI status when it is solid green, flashing green, and when it is turned off.
IPMI Direct LED Indicator Code Condition
Solid green for two seconds Indicates that the laptop or tablet is connected.
Flashing green (on for two seconds and off for two seconds) Indicates that the laptop or tablet connected is recognized.
Turns off Indicates that the laptop or tablet is unplugged.

IPMI Quick Sync 2 Indicator Codes

The IPMI Quick Sync 2 module (optional) is located on the left control panel of your system.

Figure 2. IPMI Quick Sync 2 Indicators

Table 4. IPMI Quick Sync 2 Indicators and DescriptionsThis table describes the Quick Sync status indicators. The indicator statuses are Off, which is the default state. Solid white, blinks white rapidly, blinks white slowly, blinks white five times rapidly and then turns off, solid amber, and blinking amber.
IPMI Quick Sync 2 indicator code Condition Corrective action
Off (default state) Indicates that the IPMI Quick Sync 2 feature is turned off. Press the IPMI Quick Sync 2 button to turn on the IPMI Quick Sync 2 feature. If the LED fails to turn on, reseat the left control panel flex cable and check.
Solid white Indicates that IPMI Quick Sync 2 is ready to communicate. Press the IPMI Quick Sync 2 button to turn off. If the LED fails to turn off, restart the system.
Blinks white rapidly Indicates data transfer activity.  
Blinks white slowly Indicates that firmware update is in progress.  
Blinks white five times rapidly and then turns off Indicates that the IPMI Quick Sync 2 feature is disabled. Check if IPMI Quick Sync 2 feature is configured to be disabled by IPMI.
Solid amber Indicates that the system is in fail-safe mode. Restart the system.
Blinking amber Indicates that the IPMI Quick Sync 2 hardware is not responding properly. Restart the system.

NIC Indicator Codes

Each NIC on the back of the system has indicators that provide information about the activity and link status. The activity LED indicator indicates if data is flowing through the NIC, and the link LED indicator indicates the speed of the connected network.

Figure 3. NIC Indicators

  1. Link LED indicator.
  2. Activity LED indicator.
Table 5. NIC Indicator CodesThe NIC indicator codes table describes different NIC indicator codes and condition of the connectivity.
Status Condition
Link and activity indicators are off The NIC is not connected to the network.
Link indicator is green, and activity indicator is blinking green The NIC is connected to a valid network at its maximum port speed and data is being sent or received.
Link indicator is amber and activity indicator is blinking green The NIC is connected to a valid network at less than its maximum port speed and data is being sent or received.
Link indicator is green, and activity indicator is off The NIC is connected to a valid network at its maximum port speed and data is not being sent or received.
Link indicator is amber and activity indicator is off The NIC is connected to a valid network at less than its maximum port speed and data is not being sent or received.
Link indicator is blinking green and activity is off NIC identify is enabled through the NIC configuration utility.

Power Supply Unit Indicator Codes

AC power supply units (PSUs) have an illuminated translucent handle that serves as an indicator. The indicator shows whether power is present or if a power fault has occurred.
Figure 4. AC PSU status indicator


  1. AC PSU status indicator/handle
Table 6. AC PSU status indicator codesThis table describes the AC PSU status indicators and what condition is the PSU when the power indicator light is green, blinking green, blinking amber, and when it is not lit.
Power indicator codes Condition
Green A valid power source is connected to the PSU, and the PSU is operational.
Blinking amber Indicates a problem with the PSU.
Not illuminated Power is not connected to the PSU.
Blinking green When the firmware of the PSU is being updated, the PSU handle blinks green.
CAUTION: Do not disconnect the power cord or unplug the PSU when updating the firmware. If the firmware update is interrupted; the PSUs do not function.
Blinking green and turns off When hot-plugging a PSU, the PSU handle blinks green five times at a rate of 4 Hz and turns off. This indicates a PSU mismatch concerning efficiency, feature set, health status, or supported voltage.
CAUTION: If two PSUs are installed, both the PSUs must have the same type of label; for example, Extended Power Performance (EPP) label. Mixing PSUs from previous generations of PowerEdge servers is not supported, even if the PSUs have the same power rating. This results in a PSU mismatch condition or failure to turn the system on.
CAUTION: When correcting a PSU mismatch, replace only the PSU with the blinking indicator. Swapping the PSU to make a matched pair can result in an error condition and unexpected system shutdown. To change from a high output configuration to a low output configuration or vice versa, you must turn off the system.
CAUTION: AC PSUs support both 240 V and 120 V input voltages except for Titanium PSUs, which support only 240 V. When two identical PSUs receive different input voltages, they can output different wattage, and trigger a mismatch.
CAUTION: If two PSUs are used, they must be of the same type and have the same maximum output power.

OS Installation and Application Setup

 

In order to use the CloudEOS and vEOS router, use the following link to access the vEOS Router Configuration Guide to create vEOS routers. https://www.arista.com/en/support/product-documentation.

Installing the Base CVA OS

Note: Complete the following steps to re-image the appliance to the factory reset. This will remove and you will lose all existing configurations and CloudEOS and vEOS routers.

To install the base CVA OS image, complete the following steps.

  1. Create the boot image.
    Note: Contact Arista TAC team to get the bootable self installing ISO image.
  2. Create a bootable flash drive.
    • Insert a flash drive and locate it: 
      [root@cv ~]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 205G 0 disk
__sda1 8:1 0 500M 0 part /boot
__sda2 8:2 0 204.5G 0 part
__centos_cv­root 253:0 0 50G 0 lvm /
__centos_cv­swap 253:1 0 20.5G 0 lvm [SWAP]
__centos_cv­home 253:2 0 134G 0 lvm /home
sdb 8:16 0 3.4T 0 disk /data
sdc 8:32 1 14.6G 0 disk
__sdc1 8:33 1 7.5G 0 part
    • Format the flash drive. 
      sudo mkfs.vfat /dev/sdc ­I
    • Copy the downloaded ISO image to the flash drive: 
      dd if=<path_to_iso> of=<flash_drive> status=progress
  3. Insert the flash drive and power on the server.
  4. Remove the flash drive after completing the installation.

Installing the CloudEOS and vEOS Router Appliance

Once the base CVA OS image is installed, complete the following steps to build the CloudEOS and vEOS Router Appliance.

  1. Acquire the artifacts to build the vEOS appliance.
  2. Inflate the CloudEOS and vEOS Router Appliance manufacturing tools under /data/tools/. 
    %mkdir /data/imaging; mkdir /data/tools; cd /data/imaging
%tar -zxf arista-dca-200­veos-2.1.0-mfg.tgz
%mv dca-200-veos-setup-vm.py /data/tools/
%mv <Downloaded_EOS.qcow2_image_from_above> /data/tools/
  3. Run the installer: 
    %/data/imaging/dca-200-veos-setup.sh

    This re-boots the box at the end.

  4. Run the post-install test: 
    %/data/imaging/dca-200-veos-test.sh
  5. Test the NICs cards:
    • Connect the 4x10Gb data ports using the supported Arista copper or fiber transceivers. Make sure to connect Port 1 to Port 3 and Port 2 to Port 4. Port 1 is first port towards the 1G management port side.
    • Run the NIC test script: 
      %/data/imaging/dca-200-veos-test-nics.py -a -i /data/tools/EOS.qcow2
    • Remove the transceivers before shipping the box.
    Note: Make sure to leave VM launcher script dca-200-veos-setup-vpm.py under /data/tools/ as it will be used by customers to dynamically create CloudEOS and vEOS VMs on-site.

Setting Up CVP

Note: Single-Node is not recommended for production deployments.

Pre-installation Checklist

  • Ensure that you have console access to the CVP virtual machine on each appliance, via WOK web access. See Web Access into CVX and CVP consoles via WOK.
  • Enter the CVP Console.
  • Ensure all configurations are done via console and not via SSH.
Note: This configuration will change the IPs and will drop connectivity if done over SSH.

Using the CloudEOS and vEOS Router Appliance on Microsoft Azure

The CloudEOS and vEOS Router Appliance, which is based on the Arista EOS, runs as a virtual machine instance on Azure. Use the CloudEOS and vEOS Router Appliance to create the various types of virtual machine router instances you need for your Azure deployment. For example, gateway routers and transit routers.

CloudEOS and vEOS Router Appliance Image Updates

The process you use to update CloudEOS and vEOS Router Appliance images is the standard update process used for EOS images.

For details on the steps to use, refer to the Arista EOS User Manual, see https://www.arista.com/en/support/product-documentation.

System Requirements

Describes the CloudEOS and vEOS Router Appliance Azure minimum support requirements.

The CloudEOS and vEOS Router Appliance Azure instance supports the following instance types:

  • D2_v3 with 2 cores, 8.0GiB RAM, 2 NICs (1,000 Mbps), and a 4GB OS disk.
  • D4_v3 with 4 cores, 16.0GiB RAM, 2 NICs (2,000 Mbps), and a 4GB OS disk.
  • D8_v3 with 8 cores, 32.0GiB RAM, 4 NICs (4,000 Mbps), and a 4GB OS disk.
  • D16_v3 with 16 cores, 64.0GiB RAM, 8 NICs (8,000 Mbps), and a 4GB OS disk.

Launching the CloudEOS and vEOS Router Appliance Azure Instance

There are two methods which can be used to launch a CloudEOS and vEOS Router Appliance instance.

Below is a summary of each method.

  • Portal Marketplace: This method launches an instance using the Azure Portal Marketplace UI.
  • Azure CLI 2.0: This method launches an instance using a custom template through the Azure CLI 2.0. The primary advantage of a CLI deployment is the ability to include custom-data and customize your deployment.

Do not deploy the same template twice into a single resource group, because this creates name conflicts. To deploy multiple instances into the same resource group, modify the template, so all resources are renamed, and all IP addresses are unique.

Creating an Instance using the Portal Marketplace

To create an instance using the Portal Marketplace, complete the following steps.

  1. In the Azure portal, select the green '+' button in the top left of the screen.
  2. In the search bar, type "Arista" and press enter.
    Figure 1. Type '"Arista"

  3. Select the Arista offer you are interested in.
    Figure 2. Arista Selection

  4. Select "Create".
    Figure 3. Select "Create"

  5. Fill out the required information and press "OK".
    Figure 4. Required Information

  6. Configure the VNet and press "OK".
    Figure 5. Configuring the VNet

  7. Configure the subnets and press "OK".
    Figure 6. Verification

  8. Read the Terms and Conditions, then press "Purchase".
    Figure 7. Terms and Conditions

Creating an Instance under Azure CLI 2.0

To create an instance under Azure CLI 2.0, complete the following steps.

  1. Install Azure CLI 2.0 (https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest).
  2. Run az login and follow the prompts to authorize the machine.
  3. Download the template and parameters files from the GitHub repository. https://github.com/Azure/azure-quickstart-templates.
  4. Open <prefix>-parameters.json:. Locate the ./single_line_json.sh user_data.txt script.
  5. Copy and paste the generated output into the customData value field of the JSON parameters file.
  6. Use the script as in the following example: 
    #!/usr/bin/bash
cat $1 | python -c 'import json, sys; print( json.dumps( sys.stdin.read() ) )'
  7. Use the template and parameters JSON files to launch a vEOS Router instance in Azure using the Azure CLI 2.0. 
    $ az group create --name ExampleGroup --location "Central US"
    Note: You must use the same location as the storage account where the VHD image is uploaded.
    $ az group deployment create \
--name ExampleDeployment \
--resource-group ExampleGroup \
--template-file <prefix>-template.json \
--parameters @<prefix>-parameters.json
    Note: If you are using a newer version of the Azure CLI 2.0, you may encounter a parameter file parsing bug. To fix this, remove the @ symbol before the parameters filename.

Logging into an Instance

To log into an instance, complete the following steps.

  1. Select the resource group containing your vEOS Router deployment from the Resource Groups list.
  2. Select the item publicIP.
    Figure 8. Selecting the PublicIP

  3. Locate the IP address and DNS name found on the Overview page.
    Figure 9. Locating the IP address and DNS

     

    Note: If either of these fields is not populated, your instance still deploys. Refresh the page after a couple of minutes.
  4. Secure Shell (SSH) to your Virtual Machine (VM) using the IP address or Domain Name Server (DNS) name found in the previous step, using the credentials you gave when you initially setup the VM. 
    bash# ssh This email address is being protected from spambots. You need JavaScript enabled to view it..1 
Password: *********
    Note: It may take between 5-10 minutes for the instance to become reachable after the deployment starts.

CloudEOS and vEOS Router Startup-Configuration using Instance Custom-Data

Describes launch employing custom-data information.

During the initial launching of the CloudEOS and vEOS Router Instance, Azure provides a feature to upload custom-data. The administrator can upload the CloudEOS and vEOS Router configuration using custom-data at the time of the launching of the CloudEOS and vEOS Router Instance.

Custom-data can be used to pass in configuration for multiple entities. This configuration must be separated by start and end markers.

Entity Markers File Path
CloudEOS and vEOS CLI configuration file 
%EOS-STARTUP-CONFIG-START% 
%EOS-STARTUP-CONFIG-END%
 N/A
Cloud HA configuration file 
%CLOUDHA-CONFIG-START% 
%CLOUDHA-CONFIG-END%
 /mnt/flash/cloud_ha_config.json

Note, the following regarding the custom-data.

  • Markers must be at the beginning of the line.
  • The user is expected to have tested the configurations on a live system before using the configurations to deploy the new CloudEOS and vEOS Router. Mis-configuration may result in an unrecoverable instance.
  • The CloudEOS and vEOS Router configuration for all interfaces can be passed in during deployment. The configuration takes effect as the new instances attach to the CloudEOS and vEOS Router.

Sample Instance Custom-Data

Illustrates a sample Instance with custom-data.

%EOS-STARTUP-CONFIG-START% 
! EOS startup config 
username admin nopassword 
username admin sshkey file flash:key.pub
%EOS-STARTUP-CONFIG-END%

 

Providing Startup-Configuration using Azure Custom-Data

Adding custom-data to an instance.

Currently, custom-data can only be used on instances deployed using the Azure CLI 2.0.

In order to add custom-data to an instance, the custom-data must be provided as a single-line value with '\n' delimiting newlines.

Use the single_line_json.sh script to convert your custom-data into this format.

#!/usr/bin/bash
cat $1 | python -c 'import json, sys; print( json.dumps( sys.stdin.read() ) )'

Usage of the script is as follows:

./single_line_json.sh user_data.txt

Copy and paste the generated output into the customData value field of the JSON parameters file.

Troubleshooting Instance

To troubleshoot the instance, complete the following steps.

  1. Select the resource group containing your vEOS Router deployment from the Resource groups list.
  2. Select the item CloudEOS and vEOS Router.
    Figure 10. Select the CloudEOS and vEOS Router

  3. Note the status of the VM. It should either be "Creating", "Starting", or "Running".
    Figure 11. Status of the VM

  4. Check the boot diagnostics for any error messages or warnings.
    Figure 12. Error Messages and Warnings