DEV Community: rhira777

How to use Enterprise SONiC on CML

rhira777 — Sun, 31 Dec 2023 14:37:31 +0000

Summary

In CML (Cisco Modeling Labs), the available platforms can be defined and used by yourself in addition to the standard ones.

This procedure is shown in the user guide.
https://developer.cisco.com/docs/modeling-labs/#!custom-vm-images

On SONiC, commercial distribution (Enterprise SONiC) is supplied from each vendor.

Enterprise SONiC Distribution by Edgecore
https://support.edge-core.com/hc/en-us/categories/360002134713-Enterprise-SONiC-Distribution-by-Edgecore

Enterprise SONiC Distribution by Dell Technologies
https://infohub.delltechnologies.com/p/enterprise-sonic-distribution-by-dell-technologies/

Enterprise SONiC has published images that can be used in virtualized environments, depending on the company that provides them.

This time, I tried to set up using SONiC image for virtual machines in CML 2.2.3 environment (installed on the previously built ESXi host), and was able to start using it.
The following is a record of that.

Detail of what I did

Get SONiC image

In this case, obtain from the following
- https://www.dell.com/support/home/en-us/product-support/product/enterprise-sonic-distribution/drivers
- Download gns3 file
  - Select Enterprise SONiC OS 4.2.0 gns3 this time
  - "Enterprise_SONiC_OS_4.2.0_gns3.zip"
  - Use "Enterprise_SONiC_OS_4.2.0.img" in the zip file

Define node

Select "Node and Image Definition" from "TOOLS"
Confirm that the "Node Definition" tab is selected and click the "ADD" button.
Select/enter the following information in the "General" field
- ID: "dellsonic"
- Nature: "switch"
Select/enter the following information in the "User Interface" field
- Prefix: "dellsonic-"
- Icon: "switch"
- Label: "Enterprise SONiC"

Select/enter the following information in the "Linux Native Simulation" field
- Domain Driver: "KVM"
- Simulation Driver: "server"
- Disk Driver: "VirtIO"
- Memory: "4096" in this case
- CPUs: "2" in this case
- CPU Limit: "100"
- Network Driver: "E1000"

Select/enter the following information in the "Interfaces" field
- Loopback name: "Loopback0"
- Number of serial ports: "1"
- Default number of physical interfaces: "10" in this case
- interface 0："eth0"
In the same field, press the "ADD INTERFACE" button until the number specified in the "Default number of physical interfaces" is displayed, and enter the following information
- interface 1: "Eth1/1"
- interface 2: "Eth1/2"
- interface 3: "Eth1/3"
- interface 4: "Eth1/4"
- interface 5: "Eth1/5"
- interface 6: "Eth1/6"
- interface 7: "Eth1/7"
- interface 8: "Eth1/8"
- interface 8: "Eth1/9"

Enter the following information in the "Boot" field
- Timeout: "480" in this case
In the same field, click the "ADD BOOT LINE button" and enter the following information
- "sonic login"
Click the CREATE button

Define image

Select "Node and Image Definition" from "TOOLS"
Select the "Image Definition" tab
Click the "MANAGE" button
Select "Choose a file" in the "Upload New Image File" field and specify the downloaded SONiC image
Click the "UPLOAD IMAGE" button

After confirming the display of the file specified in the "Uploaded Images" field(reloading the page may be required), press the "CREATE NEW IMAGE DEFINITION" button.

Select/enter the following information in the "General" field
- ID: "dellsonic-420"
- Label: "Enterprise SONiC 4.2.0"
- Disk Image: The uploaded SONiC image
- Node Definition: The defined node
Press "CREATE IMAGE DEFINITION" button

Confirmation of operation

I created a lab using the registered node and it was successfully started.
It was also confirmed that communication with neighboring nodes was possible.

Supplemental information and others

The default username/password is admin/YourPaSsWoRd.

Dell Networking SONiC: Secure Shell based login https://www.dell.com/support/kbdoc/en-us/000218783/dell-networking-sonic-ssh-based-login

startup log

  Booting `SONiC-OS-4.2.0-Enterprise_Base'


Loading SONiC-OS OS kernel ...

Loading SONiC-OS OS initial ramdisk ...

[   34.656910] in-memory.sh[344]: + [[ -e /dev/pmem0 ]]
[   34.673136] in-memory.sh[344]: ++ uname -r
[   34.738057] in-memory.sh[344]: + insmod /lib/modules/5.10.0-21-amd64/kernel/drivers/block/ramdisk.ko rd_address=0x40000000 rd_size=0x4000000
[   35.233113] in-memory.sh[344]: + '[' -e /dev/ramdisk ']'
[   35.248529] in-memory.sh[344]: + [[ ! -e /proc/vmcore ]]
[   35.264929] in-memory.sh[344]: + mkfs.ext4 /dev/ramdisk
[   35.782623] in-memory.sh[344]: mke2fs 1.44.5 (15-Dec-2018)
[   35.832664] in-memory.sh[344]: Creating filesystem with 65536 1k blocks and 16384 inodes
[   35.863029] in-memory.sh[344]: Filesystem UUID: 6843eecc-8058-4005-b57d-dab7f113505f
[   35.885951] in-memory.sh[344]: Superblock backups stored on blocks:
[   35.911651] in-memory.sh[344]:       8193, 24577, 40961, 57345
[   35.932443] in-memory.sh[344]: Allocating group tables: done
[   35.955397] in-memory.sh[344]: Writing inode tables: done
[   35.983239] in-memory.sh[344]: Creating journal (4096 blocks): done
[   36.009111] in-memory.sh[344]: Writing superblocks and filesystem accounting information: done
[   36.034260] in-memory.sh[344]: + e2fsck -fy /dev/ramdisk
[   36.215813] kdump-tools[343]: Starting kdump-tools: Creating symlink /var/lib/kdump/vmlinuz.
[   36.262157] kdump-tools[343]: Creating symlink /var/lib/kdump/initrd.img.
[   36.398311] in-memory.sh[344]: e2fsck 1.44.5 (15-Dec-2018)
[   36.446069] in-memory.sh[344]: Pass 1: Checking inodes, blocks, and sizes
[   36.514393] in-memory.sh[344]: Pass 2: Checking directory structure
[   36.571572] in-memory.sh[344]: Pass 3: Checking directory connectivity
[   36.590362] in-memory.sh[344]: Pass 4: Checking reference counts
[   36.610644] in-memory.sh[344]: Pass 5: Checking group summary information
[   36.636916] in-memory.sh[344]: /dev/ramdisk: 11/16384 files (0.0% non-contiguous), 7465/65536 blocks
[   36.729179] in-memory.sh[344]: + tune2fs -O '^metadata_csum' /dev/ramdisk
[   36.748593] in-memory.sh[344]: tune2fs 1.44.5 (15-Dec-2018)
[   36.767494] in-memory.sh[344]: + mount /dev/ramdisk /var/log/ramfs
[   36.792774] in-memory.sh[344]: ++ mountpoint -q /var/log/ramfs
[   36.814500] in-memory.sh[344]: + chmod 655 /var/log/ramfs
[   36.832928] in-memory.sh[344]: + set +x
[   38.196615] rc.local[578]: + cat /proc/cmdline
[   38.224026] rc.local[578]: + xargs -n1
[   38.238218] rc.local[578]: + grep loop=
[   38.264957] rc.local[578]: + cut -d= -f 2-
[   38.660962] rc.local[578]: + dirname image-4.2.0-Enterprise_Base/fs.squashfs
[   38.688844] rc.local[578]: + LOOP_IMAGE_DIR=image-4.2.0-Enterprise_Base
[   38.726252] rc.local[578]: + echo image-4.2.0-Enterprise_Base
[   38.758279] rc.local[578]: + cut -d- -f 2-
[   38.774483] rc.local[578]: + loop_version=4.2.0-Enterprise_Base
[   38.815105] rc.local[578]: + grep build_version
[   38.834005] rc.local[578]: + sed -e s/build_version: //g;s/'//g
[   38.905527] rc.local[578]: + cat /etc/sonic/sonic_version.yml
[   39.016109] rc.local[578]: + SONIC_VERSION=4.2.0-Enterprise_Base
[   39.146697] rc.local[578]: + [ 4.2.0-Enterprise_Base !=  ]
[   39.169304] rc.local[578]: + [ 4.2.0-Enterprise_Base != 4.2.0-Enterprise_Base ]
[   39.190152] rc.local[578]: + FIRST_BOOT_FILE=/host/image-4.2.0-Enterprise_Base/platform/firsttime
[   39.214308] rc.local[578]: + SONIC_FIRST_BOOT_SCRIPT=/host/image-4.2.0-Enterprise_Base/first_boot.sh
[   39.279311] rc.local[578]: + SONIC_BRANDING_OVERRIDE=/host/image-4.2.0-Enterprise_Base/sonic_branding.yml
[   39.314123] rc.local[578]: + SONIC_BRANDING_FILE=/etc/sonic/sonic_branding.yml
[   39.367061] rc.local[578]: + RUNTIME_JOURNALD_CONF=/etc/systemd/journald.conf.d/01-journald-storage.conf
[   39.448329] rc.local[578]: + RSYSLOG_FILE=/etc/logrotate.d/rsyslog
[   39.487485] rc.local[578]: + IMEM_INFO_FILE=/etc/logrotate.d/in-memory/00-in-memory-info
[   39.510376] rc.local[578]: + IMEM_DEBUG_FILE=/etc/logrotate.d/in-memory/00-in-memory-debug
[   39.539099] rc.local[578]: + IMEM_DISK_INFO_FILE=/etc/logrotate.d/in-memory/01-disk-info
[   39.561205] rc.local[578]: + IMEM_DISK_DEBUG_FILE=/etc/logrotate.d/in-memory/01-disk-debug
[   39.588452] rc.local[578]: + IMEM_CONF_FILE=/etc/rsyslog.d/in-memory/00-in-memory.conf
[   39.608050] rc.local[578]: + APPLOG_CONF_FILE=/etc/rsyslog.d/20-sonic.conf
[   39.628947] rc.local[578]: + HISTOGRAM_FILE=/etc/logrotate.d/histogram/mem-histogram-rule
[   39.657673] rc.local[578]: + LOGCLEANUP_FILE=/usr/bin/log-cleanup.sh
[   39.699884] rc.local[578]: + SONIC_CONFIG_DIR=/host/image-4.2.0-Enterprise_Base/sonic-config
[   39.745542] rc.local[578]: + SONIC_ENV_FILE=/host/image-4.2.0-Enterprise_Base/sonic-config/sonic-environment
[   39.799352] rc.local[578]: + [ -d /host/image-4.2.0-Enterprise_Base/sonic-config -a -f /host/image-4.2.0-Enterprise_Base/sonic-config/sonic-environment ]
[   39.896294] rc.local[578]: + logger SONiC version 4.2.0-Enterprise_Base starting up...
[   39.946870] rc.local[578]: + mount -t bpf none /sys/fs/bpf/
[   39.963135] rc.local[578]: + set +x
[   39.975345] rc.local[578]: + grub_installation_needed=
[   39.990196] rc.local[578]: + [ ! -e /host/machine.conf ]
[   40.010572] rc.local[578]: + migrate_nos_configuration
[   40.028620] rc.local[578]: + rm -rf /host/migration
[   40.046210] rc.local[578]: + mkdir -p /host/migration
[   40.078869] rc.local[578]: + cat /proc/cmdline
[   40.091773] rc.local[578]: + set -- BOOT_IMAGE=/image-4.2.0-Enterprise_Base/boot/vmlinuz-5.10.0-21-amd64 root=UUID=b13fefc3-4898-498e-bf1f-180508201499 rw console=tty0 console=ttyS0,115200n8 quiet net.ifnames=0 biosdevname=0 loop=image-4.2.0-Enterprise_Base/fs.squashfs loopfstype=squashfs crashkernel=0M-2G:256M,2G-4G:256M,4G-8G:384M,8G-:448M apparmor=1 security=apparmor varlog_size=4096 usbcore.autosuspend=-1 cgroup_enable=memory swapaccount=1 cma=0 memmap=64M$1G softlockup_all_cpu_backtrace=1
[   40.278371] rc.local[578]: + [ -n  ]
[   40.347631] rc.local[578]: + . /host/machine.conf
[   40.470225] rc.local[578]: + onie_arch=x86_64
[   40.482312] rc.local[578]: + onie_bin=
[   40.496259] rc.local[578]: + onie_boot_fs_type=ext4
[   40.510051] rc.local[578]: + onie_boot_gfdisk_type=0x3000
[   40.541161] rc.local[578]: + onie_boot_gpt_uuid=7412F7D5-A156-4B13-81DC-867174929325
[   40.610572] rc.local[578]: + onie_boot_label=ONIE-BOOT
[   40.680146] rc.local[578]: + onie_boot_mnt=/mnt/onie-boot
[   40.698145] rc.local[578]: + onie_boot_reason=install
[   40.756545] rc.local[578]: + onie_build_date=2018-11-17T04:18+00:00
[   40.814912] rc.local[578]: + onie_build_machine=kvm_x86_64
[   40.936072] rc.local[578]: + onie_build_platform=x86_64-kvm_x86_64-r0
[   40.958906] rc.local[578]: + onie_config_dir=/mnt/onie-boot/onie/config
[   40.986345] rc.local[578]: + onie_config_version=1
[   41.012968] rc.local[578]: + onie_default_filename=onie-installer-x86_64-kvm_x86_64-r0
[   41.054993] rc.local[578]: + onie_default_filenames=onie-installer-x86_64-kvm_x86_64-r0
[   41.084595] rc.local[578]: + onie_dev=/dev/vda2
[   41.100605] rc.local[578]: + onie_disco_boot_reason=install
[   41.131212] rc.local[578]: + onie_disco_dns=10.0.2.3
[   41.154133] rc.local[578]: + onie_disco_interface=eth0
[   41.187801] rc.local[578]: + onie_disco_ip=10.0.2.15
[   41.250023] rc.local[578]: + onie_disco_lease=86400
[   41.333788] rc.local[578]: + onie_disco_mask=24
[   41.377991] rc.local[578]: + onie_disco_opt53=05
[   41.419109] rc.local[578]: + onie_disco_router=10.0.2.2
[   41.446504] rc.local[578]: + onie_disco_serverid=10.0.2.2
[   41.492428] rc.local[578]: + onie_disco_siaddr=10.0.2.2
[   41.649018] rc.local[578]: + onie_disco_subnet=255.255.255.0
[   41.715032] rc.local[578]: + onie_exec_url=file://dev/vdb/onie-installer.bin
[   41.758713] rc.local[578]: + onie_firmware=auto
[   41.900357] rc.local[578]: + onie_grub_image_name=shimx64.efi
[   41.933383] rc.local[578]: + onie_iana_enterprise=42623
[   41.983371] rc.local[578]: + onie_image_suffixes=.bin
[   42.006215] rc.local[578]: + onie_image_type_nos=nos
[   42.023183] rc.local[578]: + onie_image_type_update=update
[   42.098738] rc.local[578]: + onie_initrd_tmp=/
[   42.203583] rc.local[578]: + onie_installer=/var/tmp/installer
[   42.232167] rc.local[578]: + onie_kernel_version=4.9.95
[   42.249325] rc.local[578]: + onie_local_parts=
[   42.264658] rc.local[578]: + onie_machine=kvm_x86_64
[   42.326350] rc.local[578]: + onie_machine_rev=0
[   42.413097] rc.local[578]: + onie_neighs=[fe80::2-eth0],
[   42.432558] rc.local[578]: + onie_operation=os-install
[   42.448676] rc.local[578]: + onie_partition_type=gpt
[   42.462873] rc.local[578]: + onie_platform=x86_64-kvm_x86_64-r0
[   42.513297] rc.local[578]: + onie_root_dir=/mnt/onie-boot/onie
[   42.634832] rc.local[578]: + onie_secure_boot=yes
[   42.715092] rc.local[578]: + onie_server_name=onie-server
[   42.744945] rc.local[578]: + onie_skip_ethmgmt_macs=yes
[   42.763887] rc.local[578]: + onie_switch_asic=qemu
[   42.781268] rc.local[578]: + onie_uefi_arch=x64
[   42.818990] rc.local[578]: + onie_uefi_boot_loader=shimx64.efi
[   42.918507] rc.local[578]: + onie_update_attempts_dir=/mnt/onie-boot/onie/update/attempts
[   42.996999] rc.local[578]: + onie_update_dir=/mnt/onie-boot/onie/update
[   43.016292] rc.local[578]: + onie_update_log=/mnt/onie-boot/onie/update/update.log
[   43.094914] rc.local[578]: + onie_update_pending_dir=/mnt/onie-boot/onie/update/pending
[   43.129414] rc.local[578]: + onie_update_results_dir=/mnt/onie-boot/onie/update/results
[   43.203477] rc.local[578]: + onie_updater_cookie=ONIE-UPDATER-COOKIE
[   43.230578] rc.local[578]: + onie_vendor_id=42623
[   43.246749] rc.local[578]: + onie_version=master-201811170418
[   43.267024] rc.local[578]: + program_console_speed
[   43.283649] kdump-tools[343]: loaded kdump kernel.
[   43.300353] rc.local[578]: + cat /proc/cmdline
[   43.325960] rc.local[578]: + grep -Eo console=ttyS[0-9]+,[0-9]+
[   43.347377] rc.local[578]: + cut -d , -f2
[   43.364099] rc.local[578]: + speed=115200
[   43.376920] rc.local[578]: + [ -z 115200 ]
[   43.404188] rc.local[578]: + CONSOLE_SPEED=115200
[   43.425112] rc.local[578]: + sed -i s|\-\-keep\-baud .* %I| 115200 %I|g /lib/systemd/system/serial-getty@.service
[   43.456972] rc.local[578]: + systemctl daemon-reload
[   43.472915] rc.local[578]: + [ -f /host/image-4.2.0-Enterprise_Base/platform/firsttime ]
[   43.498849] rc.local[578]: + [ -f /var/log/fsck.log.gz ]
[   43.516777] rc.local[578]: + gunzip -d -c /var/log/fsck.log.gz
[   43.535652] rc.local[578]: + logger -t FSCK
[   43.550609] rc.local[578]: + rm -f /var/log/fsck.log.gz
[   43.573821] rc.local[578]: + [ -n x86_64-kvm_x86_64-r0 ]
[   43.619912] rc.local[578]: + mkdir -p /mnt/onie-boot
[   43.637075] rc.local[578]: + mount LABEL=ONIE-BOOT /mnt/onie-boot
[   43.661882] rc.local[578]: + [ -f /mnt/onie-boot/onie/update/update.log ]
[   43.689742] rc.local[578]: + /usr/bin/python3 /usr/local/bin/fwpkg_tables_init.py
[   43.713299] rc.local[578]: + cp /mnt/onie-boot/onie/update/update.log /var/log/onie-update.log
[   43.739411] rc.local[578]: + set +x
[   43.753270] rc.local[578]: + /usr/bin/python3 /usr/local/bin/image_tables_init.py
[   43.802658] rc.local[578]: + exit 0


Debian GNU/Linux 10 sonic ttyS0

sonic login:

[SONiC Virtual Switch] EVPN-VXLANv4 / BGP unnumbered

rhira777 — Mon, 15 Aug 2022 20:25:00 +0000

Summary

I tried BGP unnumbered and the combination with EVPN-VXLAN in the SONiC on CML environment that we had previously built.

In this case, the virtual switch version of SONiC.202205 was configured with a minimum of communication checks in mind, and were able to achieve IPv4 forwarding using BGP unnumbered and L2 forwarding using EVPN-VXLAN.

The following is a record of that.

The main information that I was referring to is as follows:

[Edgecore SONiC] BGP Unnumbered
https://support.edge-core.com/hc/en-us/articles/900002377366--Edgecore-SONiC-BGP-Unnumbered

[Edgecore SONiC] EVPN L2 VxLAN
https://support.edge-core.com/hc/en-us/articles/900002720523--Edgecore-SONiC-EVPN-L2-VxLAN

[Edgecore SONiC] VLAN & Inter-VLAN Routing
https://support.edge-core.com/hc/en-us/articles/900000210426-VLAN-Inter-VLAN-Routing

SONiC USER MANUAL
https://github.com/sonic-net/SONiC/blob/master/doc/SONiC-User-Manual.md

SONiC Command Line Interface Guide
https://github.com/sonic-net/sonic-utilities/blob/master/doc/Command-Reference.md

Vxlan SONiC
https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/Vxlan_hld.md

Detail of what I did

Network diagram(Topology)

Network information

node	hostname	Loopback0	ASN
sonicvsvm-0	R001	10.0.0.1/32	65001
sonicvsvm-1	R002	10.0.0.2/32	65001
sonicvsvm-2	R011	10.0.0.11/32	65000
sonicvsvm-3	R012	10.0.0.12/32	65000
sonicvsvm-4	R013	10.0.0.13/32	65000
sonicvsvm-5	R014	10.0.0.14/32	65000
sonicvsvm-6	R101	10.0.0.101/32	65001
sonicvsvm-7	R102	10.0.0.102/32	65001

node	hostname	VLAN	VNI
sonicvsvm-6	R101	2	5002
sonicvsvm-7	R102	2	5002

node	interface	MAC address	VLAN	IP address	VRF
csr1000v-0	Gi2	0000.0000.0101	untag	192.168.2.101	101-2
	Gi3	0000.0000.0102	untag	192.168.2.102	102-2

SONiC OS configuration (Excerpts)

save and reload (execute as appropriate)

node	command
sonicvsvm-0~7	sudo config save -y
	sudo config reload -fy

transit link: IPv6 link-local

node	command
sonicvsvm-0~5	sudo config ipv6 enable link-local
sonicvsvm-6/7	sudo config interface ipv6 enable use-link-local-only Ethernet0
	sudo config interface ipv6 enable use-link-local-only Ethernet4

loopback: IPv4

node	command
sonicvsvm-0	sudo config interface ip add Loopback0 10.0.0.1/32
sonicvsvm-1	sudo config interface ip add Loopback0 10.0.0.2/32
sonicvsvm-2	sudo config interface ip add Loopback0 10.0.0.11/32
sonicvsvm-3	sudo config interface ip add Loopback0 10.0.0.12/32
sonicvsvm-4	sudo config interface ip add Loopback0 10.0.0.13/32
sonicvsvm-5	sudo config interface ip add Loopback0 10.0.0.14/32
sonicvsvm-6	sudo config interface ip add Loopback0 10.0.0.101/32
	sudo config interface ip add Loopback0 10.255.0.101/32 secondary
sonicvsvm-7	sudo config interface ip add Loopback0 10.0.0.102/32
	sudo config interface ip add Loopback0 10.255.0.102/32 secondary

VLAN

node	command
sonicvsvm-6/7	sudo config vlan add 2
	sudo config vlan member add -u 2 Ethernet8

VXLAN (EVPN compatible)

node	command
sonicvsvm-6	sudo config vxlan add VXLAN 10.255.0.101
sonicvsvm-7	sudo config vxlan add VXLAN 10.255.0.102
sonicvsvm-6/7	sudo config vxlan evpn_nvo add NVO VXLAN
	sudo config vxlan map add VXLAN 2 5002

FRRouting configuration (Excerpts)

sonicvsvm-0/1

no router bgp 65100
router bgp 65001
 no bgp ebgp-requires-policy
 no bgp default ipv4-unicast
 neighbor SERVICE peer-group
 neighbor SERVICE remote-as internal
 neighbor SERVICE update-source Loopback0
 neighbor TRANSPORT peer-group
 neighbor TRANSPORT remote-as external
 neighbor TRANSPORT capability extended-nexthop
 neighbor Ethernet0 interface peer-group TRANSPORT
 neighbor Ethernet4 interface peer-group TRANSPORT
 neighbor Ethernet8 interface peer-group TRANSPORT
 neighbor Ethernet12 interface peer-group TRANSPORT
 bgp listen range 10.0.0.0/8 peer-group SERVICE
 address-family ipv4 unicast
  redistribute connected
  neighbor TRANSPORT activate
  neighbor TRANSPORT allowas-in
 exit-address-family
 address-family l2vpn evpn
  neighbor SERVICE activate
  neighbor SERVICE route-reflector-client
 exit-address-family
exit

sonicvsvm-2/3/4/5

no router bgp 65100
router bgp 65000
 no bgp ebgp-requires-policy
 no bgp default ipv4-unicast
 neighbor TRANSPORT peer-group
 neighbor TRANSPORT remote-as external
 neighbor TRANSPORT capability extended-nexthop
 neighbor Ethernet0 interface peer-group TRANSPORT
 neighbor Ethernet4 interface peer-group TRANSPORT
 neighbor Ethernet8 interface peer-group TRANSPORT
 address-family ipv4 unicast
  redistribute connected
  neighbor TRANSPORT activate
  neighbor TRANSPORT allowas-in
 exit-address-family
exit

sonicvsvm-6/7

no router bgp 65100
router bgp 65001
 no bgp ebgp-requires-policy
 no bgp default ipv4-unicast
 neighbor SERVICE peer-group
 neighbor SERVICE remote-as internal
 neighbor SERVICE update-source Loopback0
 neighbor TRANSPORT peer-group
 neighbor TRANSPORT remote-as external
 neighbor TRANSPORT capability extended-nexthop
 neighbor 10.0.0.1 peer-group SERVICE
 neighbor 10.0.0.2 peer-group SERVICE
 neighbor Ethernet0 interface peer-group TRANSPORT
 neighbor Ethernet4 interface peer-group TRANSPORT
 address-family ipv4 unicast
  redistribute connected
  neighbor TRANSPORT activate
  neighbor TRANSPORT allowas-in
 exit-address-family
 address-family l2vpn evpn
  neighbor SERVICE activate
  advertise-all-vni
 exit-address-family
exit

Confirmation of operation

csr1000v-0

HOST#ping vrf 101-2 192.168.2.102 source 192.168.2.101 repeat 3
Type escape sequence to abort.
Sending 3, 100-byte ICMP Echos to 192.168.2.102, timeout is 2 seconds:
Packet sent with a source address of 192.168.2.101
.!!
Success rate is 66 percent (2/3), round-trip min/avg/max = 5/5/6 ms
HOST#
HOST#!#ping:ok

csr1000v-0 ~ sonicvsvm-7
sonicvsvm-5 ~ sonicvsvm-7

Supplemental information and others

Status of IPv4 FIB

In the preparation process, IPv4 routes exchanged by BGP were being imported, but IPv4 communication for those routes was failing. In this case, the entries displayed in "show ip route" were not displayed in "ip route show".
This problem was resolved by reloading once.

before reloading

admin@R101:~$ show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

B>r 10.0.0.1/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:04:19
  r                    via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:04:19
B>r 10.0.0.2/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:04:19
  r                    via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:04:19
B>r 10.0.0.11/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:05:53
B>r 10.0.0.12/32 [20/0] via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:05:53
B>r 10.0.0.13/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:04:19
  r                     via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:04:19
B>r 10.0.0.14/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:04:19
  r                     via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:04:19
C>* 10.0.0.101/32 is directly connected, Loopback0, 10:02:07
B>r 10.0.0.102/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:04:19
  r                      via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:04:19

admin@R101:~$
admin@R101:~$ ip route show
240.127.1.0/24 dev docker0 proto kernel scope link src 240.127.1.1 linkdown
admin@R101:~$
admin@R101:~$ ping 10.0.0.102 -I 10.0.0.101 -c 3
PING 10.0.0.102 (10.0.0.102) from 10.0.0.101 : 56(84) bytes of data.

--- 10.0.0.102 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2027ms

admin@R101:~$

after reloading

admin@R101:~$ show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       > - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

B>* 10.0.0.1/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:01:30
  *                    via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:01:30
B>* 10.0.0.2/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:01:30
  *                    via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:01:30
B>* 10.0.0.11/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:01:30
B>* 10.0.0.12/32 [20/0] via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:01:30
B>* 10.0.0.13/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:01:25
  *                     via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:01:25
B>* 10.0.0.14/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:01:17
  *                     via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:01:17
C>* 10.0.0.101/32 is directly connected, Loopback0, 00:06:34
B>* 10.0.0.102/32 [20/0] via fe80::5054:ff:fe1c:514a, Ethernet0, weight 1, 00:01:25
  *                      via fe80::5054:ff:fe1d:5a36, Ethernet4, weight 1, 00:01:25

admin@R101:~$
admin@R101:~$ ip route show
10.0.0.1 nhid 226 proto bgp src 10.0.0.101 metric 20
        nexthop via inet6 fe80::5054:ff:fe1c:514a dev Ethernet0 weight 1
        nexthop via inet6 fe80::5054:ff:fe1d:5a36 dev Ethernet4 weight 1
10.0.0.2 nhid 226 proto bgp src 10.0.0.101 metric 20
        nexthop via inet6 fe80::5054:ff:fe1c:514a dev Ethernet0 weight 1
        nexthop via inet6 fe80::5054:ff:fe1d:5a36 dev Ethernet4 weight 1
10.0.0.11 nhid 227 via inet6 fe80::5054:ff:fe1c:514a dev Ethernet0 proto bgp src 10.0.0.101 metric 20
10.0.0.12 nhid 228 via inet6 fe80::5054:ff:fe1d:5a36 dev Ethernet4 proto bgp src 10.0.0.101 metric 20
10.0.0.13 nhid 226 proto bgp src 10.0.0.101 metric 20
        nexthop via inet6 fe80::5054:ff:fe1c:514a dev Ethernet0 weight 1
        nexthop via inet6 fe80::5054:ff:fe1d:5a36 dev Ethernet4 weight 1
10.0.0.14 nhid 226 proto bgp src 10.0.0.101 metric 20
        nexthop via inet6 fe80::5054:ff:fe1c:514a dev Ethernet0 weight 1
        nexthop via inet6 fe80::5054:ff:fe1d:5a36 dev Ethernet4 weight 1
10.0.0.102 nhid 226 proto bgp src 10.0.0.101 metric 20
        nexthop via inet6 fe80::5054:ff:fe1c:514a dev Ethernet0 weight 1
        nexthop via inet6 fe80::5054:ff:fe1d:5a36 dev Ethernet4 weight 1
240.127.1.0/24 dev docker0 proto kernel scope link src 240.127.1.1 linkdown
admin@R101:~$
admin@R101:~$ ping 10.0.0.102 -I 10.0.0.101 -c 3
PING 10.0.0.102 (10.0.0.102) from 10.0.0.101 : 56(84) bytes of data.
64 bytes from 10.0.0.102: icmp_seq=1 ttl=61 time=3.81 ms
64 bytes from 10.0.0.102: icmp_seq=2 ttl=61 time=3.29 ms
64 bytes from 10.0.0.102: icmp_seq=3 ttl=61 time=3.05 ms

--- 10.0.0.102 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 3.045/3.381/3.806/0.316 ms
admin@R101:~$

Status of bridge table

After successful L2 communication, the EVPN Route Type 2 routes exchanged by BGP were imported, but their entries were not displayed in output such as "show mac".
In this environment, it is possible that this is a display problem or that unicast communication also success as BUM forwarding. It may be possible to proceed to isolate this point, for example, by adding NVEs.

sonicvsvm-6

admin@R101:~$ #ping:ok
admin@R101:~$
admin@R101:~$ show mac
  No.    Vlan  MacAddress         Port       Type
-----  ------  -----------------  ---------  -------
    1       2  00:00:00:00:01:01  Ethernet8  Dynamic
Total number of entries 1
admin@R101:~$
admin@R101:~$ vtysh

Hello, this is FRRouting (version 8.2.2).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

R101#
R101# show bgp l2vpn evpn
BGP table version is 9, local router ID is 10.0.0.101
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal
Origin codes: i - IGP, e - EGP, ? - incomplete
EVPN type-1 prefix: [1]:[EthTag]:[ESI]:[IPlen]:[VTEP-IP]
EVPN type-2 prefix: [2]:[EthTag]:[MAClen]:[MAC]:[IPlen]:[IP]
EVPN type-3 prefix: [3]:[EthTag]:[IPlen]:[OrigIP]
EVPN type-4 prefix: [4]:[ESI]:[IPlen]:[OrigIP]
EVPN type-5 prefix: [5]:[EthTag]:[IPlen]:[IP]

   Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 10.0.0.101:1
*> [2]:[0]:[48]:[00:00:00:00:01:01]
                    10.255.0.101                       32768 i
                    ET:8 RT:65001:5002
*> [3]:[0]:[32]:[10.255.0.101]
                    10.255.0.101                       32768 i
                    ET:8 RT:65001:5002
Route Distinguisher: 10.0.0.102:1
* i[2]:[0]:[48]:[00:00:00:00:01:02]
                    10.255.0.102             0    100      0 i
                    RT:65001:5002 ET:8
*>i                 10.255.0.102             0    100      0 i
                    RT:65001:5002 ET:8
* i[3]:[0]:[32]:[10.255.0.102]
                    10.255.0.102             0    100      0 i
                    RT:65001:5002 ET:8
*>i                 10.255.0.102             0    100      0 i
                    RT:65001:5002 ET:8

Displayed 4 out of 6 total prefixes
R101#

How to use SONiC on CML

rhira777 — Sat, 13 Aug 2022 17:58:12 +0000

Summary

In CML (Cisco Modeling Labs), the available platforms can be defined and used by yourself in addition to the standard ones.

This procedure is shown in the user guide.
https://developer.cisco.com/docs/modeling-labs/#!custom-vm-images

SONiC is also available for virtual machines and containers.

SONiC on virtual machine for Windows
https://github.com/sonic-net/SONiC/wiki/SONiC-on-virtual-machine-for-Windows

HOWTO Use Virtual Switch (VM)
https://github.com/sonic-net/sonic-buildimage/blob/master/platform/vs/README.vsvm.md

HOWTO Use Virtual Switch (Docker)
https://github.com/sonic-net/sonic-buildimage/blob/master/platform/vs/README.vsdocker.md

Detail of what I did

Get SONiC image

In this case, obtain from the following
- https://sonic.software/
- Download the virtual switch image file
  - Select the one from Branch 202205 this time
  - "sonic-vs.img.gz".

Define node

Select "Node and Image Definition" from "TOOLS"
Confirm that the "Node Definition" tab is selected and click the "ADD" button.
Select/enter the following information in the "General" field
- ID: "sonicvsvm"
- Nature: "switch"
Select/enter the following information in the "User Interface" field
- Prefix: "sonicvsvm-"
- Icon: "switch"
- Label: "SONiC Virtual Switch (VM)"

Select/enter the following information in the "Linux Native Simulation" field
- Domain Driver: "KVM"
- Simulation Driver: "server"
- Disk Driver: "VirtIO"
- Memory: "2048" in this case
- CPUs: "2" in this case
- CPU Limit: "100"
- Network Driver: "E1000" ---
Select/enter the following information in the "Interfaces" field
- Loopback name: "Loopback0"
- Number of serial ports: "1"
- Default number of physical interfaces: "9" in this case
- interface 0："eth0"
In the same field, press the "ADD INTERFACE" button until the number specified in the "Default number of physical interfaces" is displayed, and enter the following information
- interface 1: "Ethernet0"
- interface 2: "Ethernet4"
- interface 3: "Ethernet8"
- interface 4: "Ethernet12"
- interface 5: "Ethernet16"
- interface 6: "Ethernet20"
- interface 7: "Ethernet24"
- interface 8: "Ethernet28"

Enter the following information in the "Boot" field
- Timeout: "480" in this case
In the same field, click the "ADD BOOT LINE button" and enter the following information
- "sonic login"
Click the CREATE button

Define image

Select "Node and Image Definition" from "TOOLS"
Select the "Image Definition" tab
Click the "MANAGE" button
Select "Choose a file" in the "Upload New Image File" field and specify the downloaded SONiC image
Click the "UPLOAD IMAGE" button

After confirming the display of the file specified in the "Uploaded Images" field, press the "CREATE NEW IMAGE DEFINITION" button.

Select/enter the following information in the "General" field
- ID: "sonicvsvm-202205"
- Label: "SONiC Virtual Switch (VM) 202205"
- Disk Image: The uploaded SONiC image
- Node Definition: The defined node
Press "CREATE IMAGE DEFINITION" button

Confirmation of operation

I created a lab using the registered node and it was successfully started.
It was also confirmed that communication with neighboring nodes was possible.

Supplemental information and others

The default username/password is admin/YourPaSsWoRd.

SONiC USER MANUAL https://github.com/sonic-net/SONiC/blob/master/doc/SONiC-User-Manual.md

startup log

  Booting `SONiC-OS-202205.133812-e8fe21b3a'


Loading SONiC-OS OS kernel ...

Loading SONiC-OS OS initial ramdisk ...

tune2fs 1.46.2 (28-Feb-2021)
Setting reserved blocks percentage to 0% (0 blocks)
Setting reserved blocks count to 0
[    5.274055] rc.local[357]: + cat /etc/sonic/sonic_version.yml
[    5.286346] rc.local[358]: + grep build_version
[    5.308838] rc.local[372]: + sed -e s/build_version: //g;s/'//g
[    5.346575] rc.local[354]: + SONIC_VERSION=202205.133812-e8fe21b3a
[    5.374217] rc.local[354]: + FIRST_BOOT_FILE=/host/image-202205.133812-e8fe21b3a/platform/firsttime
[    5.406043] rc.local[354]: + SONIC_CONFIG_DIR=/host/image-202205.133812-e8fe21b3a/sonic-config
[    5.414535] rc.local[354]: + SONIC_ENV_FILE=/host/image-202205.133812-e8fe21b3a/sonic-config/sonic-environment
[    5.442671] rc.local[354]: + [ -d /host/image-202205.133812-e8fe21b3a/sonic-config -a -f /host/image-202205.133812-e8fe21b3a/sonic-config/sonic-environment ]
[    5.479881] rc.local[354]: + logger SONiC version 202205.133812-e8fe21b3a starting up...
[    5.551047] rc.local[354]: + grub_installation_needed=
[    5.579501] rc.local[354]: + [ ! -e /host/machine.conf ]
[    5.606349] rc.local[354]: + . /host/machine.conf
[    5.634855] rc.local[354]: + onie_arch=x86_64
[    5.641530] rc.local[354]: + onie_bin=
[    5.655218] rc.local[354]: + onie_boot_reason=install
[    5.664985] rc.local[354]: + onie_build_date=2018-11-17T04:18+00:00
[    5.672286] rc.local[354]: + onie_build_machine=kvm_x86_64
[    5.682261] rc.local[354]: + onie_build_platform=x86_64-kvm_x86_64-r0
[    5.699784] rc.local[354]: + onie_config_version=1
[    5.709808] rc.local[354]: + onie_dev=/dev/vda2
[    5.718218] rc.local[354]: + onie_disco_boot_reason=install
[    5.724046] rc.local[354]: + onie_disco_dns=10.0.2.3
[    5.739660] rc.local[354]: + onie_disco_interface=eth0
[    5.746767] rc.local[354]: + onie_disco_ip=10.0.2.15
[    5.752000] rc.local[354]: + onie_disco_lease=86400
[    5.762114] rc.local[354]: + onie_disco_mask=24
[    5.763791] rc.local[354]: + onie_disco_opt53=05
[    5.775585] rc.local[354]: + onie_disco_router=10.0.2.2
[    5.787520] rc.local[354]: + onie_disco_serverid=10.0.2.2
[    5.795402] rc.local[354]: + onie_disco_siaddr=10.0.2.2
[    5.797178] rc.local[354]: + onie_disco_subnet=255.255.255.0
[    5.803935] rc.local[354]: + onie_exec_url=file://dev/vdb/onie-installer.bin
[    5.817521] rc.local[354]: + onie_firmware=auto
[    5.823414] rc.local[354]: + onie_grub_image_name=shimx64.efi
[    5.827010] rc.local[354]: + onie_initrd_tmp=/
[    5.828773] rc.local[354]: + onie_installer=/var/tmp/installer
[    5.839240] rc.local[354]: + onie_kernel_version=4.9.95
[    5.842667] rc.local[354]: + onie_local_parts=
[    5.846107] rc.local[354]: + onie_machine=kvm_x86_64
[    5.851656] rc.local[354]: + onie_machine_rev=0
[    5.866354] rc.local[354]: + onie_neighs=[fe80::2-eth0],
[    5.870137] rc.local[354]: + onie_partition_type=gpt
[    5.873605] rc.local[354]: + onie_platform=x86_64-kvm_x86_64-r0
[    5.883782] rc.local[354]: + onie_root_dir=/mnt/onie-boot/onie
[    5.891640] rc.local[354]: + onie_secure_boot=yes
[    5.895686] rc.local[354]: + onie_skip_ethmgmt_macs=yes
[    5.900815] rc.local[354]: + onie_switch_asic=qemu
[    5.910116] rc.local[354]: + onie_uefi_arch=x64
[    5.914736] rc.local[354]: + onie_uefi_boot_loader=shimx64.efi
[    5.918640] rc.local[354]: + onie_vendor_id=42623
[    5.929991] rc.local[354]: + onie_version=master-201811170418
[    5.935779] rc.local[354]: + program_console_speed
[    5.961289] rc.local[381]: + cat /proc/cmdline
[    5.967825] rc.local[382]: + grep -Eo console=ttyS[0-9]+,[0-9]+
[    5.969963] kdump-tools[348]: Starting kdump-tools:
[    5.983970] rc.local[391]: + cut -d , -f2
[    5.989988] kdump-tools[385]: no crashkernel= parameter in the kernel cmdline ...
[    5.994164] kdump-tools[431]:  failed!
[    6.015307] rc.local[354]: + speed=115200
[    6.016722] rc.local[354]: + [ -z 115200 ]
[    6.022641] rc.local[354]: + CONSOLE_SPEED=115200
[    6.034225] rc.local[395]: + grep keep-baud
[    6.038480] rc.local[394]: + grep agetty /lib/systemd/system/serial-getty@.service
[    6.043188] rc.local[395]: ExecStart=-/sbin/agetty -o '-p -- \\u' --keep-baud 115200,57600,38400,9600 %I $TERM
[    6.052015] rc.local[354]: + [ 0 = 0 ]
[    6.053117] rc.local[354]: + sed -i s|\-\-keep\-baud .* %I| 115200 %I|g /lib/systemd/system/serial-getty@.service
[    6.059409] rc.local[354]: + systemctl daemon-reload
[    6.065592] rc.local[354]: + [ -f /host/image-202205.133812-e8fe21b3a/platform/firsttime ]
[    6.074332] rc.local[354]: + echo First boot detected. Performing first boot tasks...
[    6.078155] rc.local[354]: First boot detected. Performing first boot tasks...
[    6.081148] rc.local[354]: + [ -n  ]
[    6.086179] rc.local[354]: + [ -n x86_64-kvm_x86_64-r0 ]
[    6.088825] rc.local[354]: + platform=x86_64-kvm_x86_64-r0
[    6.090372] rc.local[354]: + [ -d /host/old_config ]
[    6.094434] rc.local[354]: + [ -f /host/minigraph.xml ]
[    6.096638] rc.local[354]: + [ -n  ]
[    6.101041] rc.local[354]: + touch /tmp/pending_config_initialization
[    6.102851] rc.local[354]: + touch /tmp/notify_firstboot_to_platform
[    6.108945] rc.local[354]: + [ ! -d /host/reboot-cause/platform ]
[    6.114369] rc.local[354]: + mkdir -p /host/reboot-cause/platform
[    6.116093] rc.local[354]: + [ -d /host/image-202205.133812-e8fe21b3a/platform/x86_64-kvm_x86_64-r0 ]
[    6.121007] rc.local[354]: + sync
[    6.126091] rc.local[354]: + [ -n x86_64-kvm_x86_64-r0 ]
[    6.135691] rc.local[354]: + [ -n  ]
[    6.138201] rc.local[354]: + mkdir -p /var/platform
[    6.143169] rc.local[354]: + [ -f /etc/default/kdump-tools ]
[    6.147718] rc.local[354]: + sed -i -e s/__PLATFORM__/x86_64-kvm_x86_64-r0/g /etc/default/kdump-tools
[    6.152807] rc.local[354]: + firsttime_exit
[    6.155310] rc.local[354]: + rm -rf /host/image-202205.133812-e8fe21b3a/platform/firsttime
[    6.165820] rc.local[354]: + exit 0


Debian GNU/Linux 11 sonic ttyS0

sonic login: admin

Password: 
Linux sonic 5.10.0-12-2-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64
You are on
  ____   ___  _   _ _  ____
 / ___| / _ \| \ | (_)/ ___|
 \___ \| | | |  \| | | |
  ___) | |_| | |\  | | |___
 |____/ \___/|_| \_|_|\____|

-- Software for Open Networking in the Cloud --

Unauthorized access and/or use are prohibited.
All access and/or use are subject to monitoring.

Help:    http://azure.github.io/SONiC/

admin@sonic:~$ 

admin@sonic:~$ show lldp table

Capability codes: (R) Router, (B) Bridge, (O) Other
LocalPort    RemoteDevice    RemotePortID    Capability    RemotePortDescr
-----------  --------------  --------------  ------------  -----------------
Ethernet0    sonic           fortyGigE0/0    BR            Ethernet0
--------------------------------------------------
Total entries displayed:  1
admin@sonic:~$

How to use Arista vEOS on CML

rhira777 — Sat, 13 Aug 2022 17:57:48 +0000

Summary

In CML (Cisco Modeling Labs), the available platforms can be defined and used by yourself in addition to the standard ones.

This procedure is shown in the user guide.
https://developer.cisco.com/docs/modeling-labs/#!custom-vm-images

Arista EOS also offers vEOS/cEOS available for virtual machines and containers.
At the time of this writing, the software is available for download by anyone with user registration, and examples of its use in various network simulators are introduced.

Setting up EVE-NG, CloudVision Portal and vEOS
https://aristanetworks.force.com/AristaCommunity/s/article/setting-up-eve-ng-cloudvision-portal-and-veos

vEOS/cEOS GNS3 Labs
https://aristanetworks.force.com/AristaCommunity/s/article/veos-ceos-gns3-labs

Running vEOS in GNS3 1.5
https://aristanetworks.force.com/AristaCommunity/s/article/running-veos-in-gns3-1-5

We can also see examples of attempts to use the system in CML.

Using Arista with CML
https://www.youtube.com/watch?v=Bg8aHL48n5g&t=2s

Importing Arista Devices into Cisco CML
https://www.youtube.com/watch?v=LfivGQa03sM&t=1166s

This time, I tried to set up EOS 4.28.1F in CML 2.2.3 environment (installed on the previously built ESXi host), and was able to start using it.
The following is a record of that.

Detail of what I did

Get vEOS

Obtain from Arista's website
- https://www.arista.com/en/support/software-download
- Download vmdk vEOS file
  - Select the non-64-bit one this time
  - "vEOS-lab-XXXX.vmdk"

Define node

Select "Node and Image Definition" from "TOOLS"
Confirm that the "Node Definition" tab is selected and click the "ADD" button.
Select/enter the following information in the "General" field
- ID: "veos"
- Nature: "switch"
Select/enter the following information in the "User Interface" field
- Prefix: "veos-"
- Icon: "switch"
- Label: "Arista vEOS"

Select/enter the following information in the "Linux Native Simulation" field
- Domain Driver: "KVM"
- Simulation Driver: "server"
- Disk Driver: "IDE"
- Memory: "2048" in this case
- CPUs: "2" in this case
- CPU Limit: "100"
- Network Driver: "E1000"

Select/enter the following information in the "Interfaces" field
- Loopback name: "Loopback0"
- Number of serial ports: "1"
- Default number of physical interfaces: "9" in this case
- interface 0："Management1"
In the same field, press the "ADD INTERFACE" button and enter the following information
- interface 1: "Ethernet1"
In the same field, press the "INCREMENT LAST INTERFACE" button until the number specified in the "Default number of physical interfaces" is displayed.

Enter the following information in the "Boot" field
- Timeout: "480" in this case
In the same field, click the "ADD BOOT LINE button" and enter the following information
- "localhost login"
Click the CREATE button

Define image

Select "Node and Image Definition" from "TOOLS"
Select the "Image Definition" tab
Click the "MANAGE" button
Select "Choose a file" in the "Upload New Image File" field and specify the downloaded vEOS file
Click the "UPLOAD IMAGE" button

After confirming the display of the file specified in the "Uploaded Images" field, press the "CREATE NEW IMAGE DEFINITION" button.

Select/enter the following information in the "General" field
- ID: "veos-4-28-1f"
- Label: "Arista vEOS 4.28.1F"
- Disk Image: The uploaded vEOS file
- Node Definition: The defined node
Press "CREATE IMAGE DEFINITION" button

Confirmation of operation

I created a lab using the registered node and it was successfully started.
It was also confirmed that communication with neighboring nodes was possible.

Supplemental information and others

The Aboot file was not used in this work.
Also, the conversion to qcow2 was not performed.

Getting external connectivity within CML on ESXi environment

rhira777 — Fri, 12 Aug 2022 15:01:32 +0000

Background and result

In CML (Cisco Modeling Labs), when accessing each node in the lab from the outside via SSH, etc., a node called the External Connector is deployed and connected to the management interface of each node.

This procedure is shown in the user guide.
https://developer.cisco.com/docs/modeling-labs/#!bridge-mode

In my ESXi environment, the following work was required as a preliminary step.

Accept promiscuous mode in ESXi https://developer.cisco.com/docs/modeling-labs/#deploying-the-ova-on-esxi-server

In addition, the following task was also required for CML 2.4.0.

Edit the bridge interface in CML https://developer.cisco.com/docs/modeling-labs/#!configuring-the-management-ip-address

What I did

Accept promiscuous mode

Check settings of port groups assigned to VMs in CML
If it is inherited from a vSwitch, check the related vSwitch settings
- Change promiscuous mode to accept and save

Edit the bridge interface

Login to CML's Web console
- https://{CML's IP address}:9090/
- username : "sysadmin"
- password : string specified during installation
Press bridge0 after selecting Networking from the menu
- At this time, check the interface on which the management IP address is set
Press "+" on the port and select the interface you just checked
- in this case "ens160"
Confirm that bridge0 is assigned an IP address for management

The required step was the above.

Supplemental information and others

If the hypervisor is nested, then promiscuous mode must be accepted for all vNICs/vSwitches that the communication passes through.

Getting 128GB ESXi host for my home lab [Year 2022]

rhira777 — Sun, 31 Jul 2022 04:50:21 +0000

Background

I want to deploy a large number of virtual routers.
-> I want to prepare 128GB ESXi host as inexpensive as possible.

Virtual appliances for commercial networking products tend to require a lot of memory. For this reason, memory size becomes a resource bottleneck when testing a network of many nodes in a virtualized environment.

This is a trend for commercial software; using FRRouting with Docker and other methods will result in resource consumption that will scale.

I thought there were numerous options for 64GB, but this time I wanted a 128GB machine. Search showed that barebone is a useful option...so I tried it with current hardware, while gratefully following the information of our predecessors who have put it into practice.

Using the new Shuttle SH370R8 as home lab server with VMware ESXi

The following is a record of that.

Preparing hardware

I prepared the following hardware:

Barebone：SH570R6
CPU：Corei7-11700
Memory：32GB * 4
SSD：512GB
USB memory：16GB

The power cable was the one included with the SH570R6.
The LAN cable was used from home.
During the ESXi installation process, I also used a display, an HDMI cable for its connection, and a USB-connected keyboard.

SSD of 1 or 2TB would also be a good option.

Preparing software and license

I prepared VMware vSphere and the license due to assuming to use and test it.

License：VMUG Advantage

The software could be downloaded along with the license.
At the time of this trial, VMUG Advantage Membership subscriptions to be available were the following:

Installing hardware

I could finish to install hardware according to SH570R6 Series Quick Guide.

No physical force was required for any of the tasks.
During the process, the work was stopped for a while in the following places.
- At "B. CPU and ICE Module Installation", "Unfasten the ICE fan thumbscrews on the back of the chassis" that was not included in the diagram.

Installing software

I created the USB installation media with using Rufus.

I confirmed to be selected USB memory as the device and specified an iso file starting with "VMware-VMvisor-Installer-".
I used ESXi 6.7 on this time.

After that, I connected "Installation media(to USB)" "Power cable(to AC power)" "UTP cable(to LAN)" "Display (to HDMI)" "Keyboard(to USB)" to the barebone, and powered it on.

After confirming BIOS booting, I entered BIOS setup view by entering F2 key. I specified USB as first order on Boot option in the "Boot" tab. After saving and exit from setup view, I could confirm ESXi booting.

When I proceeded to start ESXi as it was, the installation process stopped with "Initialiizing IOV" displayed.

When the following output in the lower right corner of the screen, I entered "o" key with pushing shift key.

Shift + O: Edit boot options

Then, following the output string, I typed "noIOMMU" after a single space and pressed Enter. ESXi booting proceeded and the installation wizard was displayed.

i7-4770K Haswell core - ESXi5.1 hang on "initializing IOV"

From then on, I confirmed the ESXi installation was complete by following the instructions to enter the information.

Result

It worked fine.

The license has been successfully installed ,too.

What I noticed

It seemed that only one LAN port was recognized by ESXi, whereas two existed. Regarding this, there was actually a phenomenon that ESXi could not connect to the network when the right LAN port was first connected, and this was resolved by replacing it with the left port.

Upon further investigation, it seems that the two LAN ports are of different types. If the second port is used in this environment, it is possible that an additional driver will be required.