How To Add Cisco Nexus 9k Switch in Eve-ng

Cisco Nexus Switched requires no introduction in networking world. Today, I will help you to add nexus switches in eve-ng. Nexus Switches uses little bit more resources as compared to other nodes.

Nexus switch is so rich in features that it covers almost 80% data center in world. Now you can create topology and practice as much as you can in Eve-ng.

If you want to download Eve-ng with multiple pre loaded images then just click here.
If you want to install Cisco Nexus 9k switch on VMware then check our another post- How to install Cisco Nexus switch on Vmware.

I will help you step by step to add nexus 9k switch in eve-ng. For more help you can watch video shared in the last, Video- how to add Cisco Nexus Switch in Eve-ng.

Content
1 How to install Eve-ng on vmware in windows
2 Download Cisco Nexus 9k Images.
3 Preparing Eve-ng for Cisco Nexus 9k.
4 Getting ready Cisco Nexus 9k for first use.
5 NX9K first boot setup steps.

There is separate post in detail of how to install Eve-ng on vmware, so we will continue with the second step directly.

1. Cisco Nexus 9k Images in eve-ng.

EVE Image NameDownloaded FilenameVersionvCPUsvRAM
nxosv9k-7.0.3.I7.4nxosv9k-7.0.3.I7.4.qcow2nxosv9k-7.0.3.I7.428192

Other versions should also be supported following bellow’s procedure

2. Download Cisco Nexus 9k Images for Eve-ng

if you have access to Cisco software portal, so you can directly download the image from Cisco website from below URL.

https://software.cisco.com/download/home/286312239/type/282088129/release/7.0%25283%2529I7%25284%2529

No worries, if you do not have access to Cisco Website you can download the image from below alternate link.
Download Cisco Nexus 9k Image

Images provided above are strictly for education purpose and are not hosted on www.networkhunt.com server. We are just indexing the links fond on internet for education purpose only. Once you download the image then we are go to go for next step.

3. Preparing Eve-ng Cisco Nexus 9k switch.

Steps below are based on nxosv-final.7.0.3.I7.4.qcow2 creation, for other image deployment, use proper names respectively.

SSH to EVE-ng and login as root, from cli and create temporary working directory on the EVE’s root:

mkdir /opt/unetlab/addons/qemu/nxosv9k-7.0.3.I7.4/


Upload the downloaded nxosv-final.7.0.3.I7.4.qcow2 image to the EVE /opt/unetlab/addons/qemu/nxosv9k-7.0.3.I7.4/ using for example FileZilla or WinSCP.

From cli go to created directory and rename image to Sataa.qcow2.

cd /opt/unetlab/addons/qemu/nxosv9k-7.0.3.I7.4/
mv nxosv-final.7.0.3.I7.4.qcow2 sataa.qcow2

Now we need to Fix permissions in eve-ng, once done we are good to start the node

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

5. NX9K first boot setup steps.

Now you must be seeing node in Eve-ng. when you start the node it will take some time to start depending on your cpu and memory.
you may be getting loader on the screen once Nexus completed its booting.

Insert below command to check all the available file

dir
you will see output mentioning the boot file as like below image.

how to add nexus switch in eve-ng

after running dir command you will be able to see NXOS image then just use below command and press enter
loader > boot nxos.7.0.3.I7.4.bin

it will take some time to load depending on cpu and memory once done it will ask for prompt answer

1. Start node and on prompt answer:

Abort Auto Provisioning and continue with normal setup ?(yes/no)[n]: yes
Do you want to enforce secure password standard (yes/no) no

Enter passwords for admin:
admin
admin


Would you like to enter the basic configuration dialog (yes/no): no

2. Login in your switch first time:

User Access Verification
 login: admin
Password: admin

3. dir flash: To get proper image name to set  boot nxos from it

switch# dir bootflash:
       4096    Apr 18 00:53:27 2017  .rpmstore/
       4096    Apr 18 00:53:47 2017  .swtam/
      14160    Apr 18 00:58:45 2017  20170418_005603_poap_26331_init.log
  757307904    Feb 16 17:17:14 2017  nxos.7.0.3.I7.4.bin
          0    Apr 18 01:00:14 2017  platform-sdk.cmd
       4096    Apr 18 00:55:47 2017  scripts/
       4096    Apr 18 00:55:57 2017  virt_strg_pool_bf_vdc_1/
       4096    Apr 18 00:54:00 2017  virtual-instance/
         59    Apr 18 00:53:52 2017  virtual-instance.conf

4. Enter into global configuration mode:

switch# conf t
Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# boot nxos bootflash:nxos.7.0.3.I7.4.bin
end
copy run start

Now your NX9K after reboot or stop node will start normally. Steps 1-3 need to to do one time on every first added NX9K node on the topology !

Now your switch is ready !!!

For any Queries or help Comment below, and help us by sharing on Facebook, LinkedIn or twitter.

23 thoughts on “How To Add Cisco Nexus 9k Switch in Eve-ng”

    • bash-4.2#
      bash-4.2#
      bash-4.2# dir
      bin isan_lib.img mod-1 usr_ro
      boot isan_lib_eth.img modflash usr_rw
      boot_dev isan_lib_eth_ro n3k_tor_delete.list var
      boot_eth isan_lib_n9k_ro nativeboot vdc_10
      bootflash isan_lib_n9k_rw nfsroot vdc_11
      cgroup isan_lib_ro nginx vdc_12
      cmn isan_lib_rw nxos vdc_13
      data isan_n9k_bin.img opt vdc_14
      debug isan_n9k_lib.img proc vdc_15
      debugfs isanboot proc_isan vdc_16
      dev lc rd vdc_17
      dklm_lc.tar lc_n9k_ro root vdc_2
      etc lc_ro rpms vdc_3
      home lc_rw sbin vdc_4
      init lcimages slot0 vdc_5
      isan lib smack vdc_6
      isan_bin.img lib64 sys vdc_7
      isan_bin_eth.img linuxrc sys_block_bootdev vdc_8
      isan_bin_eth_ro log tmp vdc_9
      isan_bin_n9k_ro logflash usbslot1 vmachine
      isan_bin_n9k_rw media usbslot2 volatile
      isan_bin_ro mgmt usr
      isan_bin_rw mnt usr.img
      bash-4.2#
      bash-4.2#

      Reply
  1. I did every step but when Nexus boot, it stuck in loader and I saw this log:

    2019 Apr 4 08:08:26 %$ VDC-1 %$ Apr 4 08:08:25 %KERN-0-SYSTEM_MSG: [ 10.144781] [1554365075] Error: Could not find mtd devices – kernel
    ..System is coming up … Please wait …
    2019 Apr 4 08:08:51 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: before access to bkout_cfg – clis
    ..2019 Apr 4 08:09:25 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: <> logflash: online – usbhsd
    .2019 Apr 4 08:09:46 %$ VDC-1 %$ %SYSMGR-2-SIGKILL_FAILURE: Service “pixm_vl” failure to respond to SIGKILL causing supervisor to reset. Last heartbeat 63.27 secs ago.

    I try everything but still not work. Can you help me?

    Reply
    • Wait for 10 min it will come up
      It happened to me as well reason it requires huge cpu and memory to work faster

      Reply
  2. Hi,
    When I try to turn on BGP feature, it complains about license. And BGP just doesn’t work. Any idea how to get around this?

    r1(config)# 2019 Apr 18 21:45:20 r1 %$ VDC-1 %$ clis[27331]: !!!!!! WARNING: ‘LAN_ENTERPRISE_SERVICES_PKG’ LICENSE NOT FOUND ON THE SYSTEM !!
    !!!!. You have tried to enable a licensed feature [bgp] without installing the ‘LAN_ENTERPRISE_SERVICES_PKG’ license, which has not been found
    on the system.
    2019 Apr 18 21:45:20 r1 %$ VDC-1 %$ clis[27331]: System supports honor based license.Feature will be enabled and fully functional.License usage
    for feature will appear after license install and a reload.
    2019 Apr 18 21:45:20 r1 %$ VDC-1 %$ clis[27331]: If you have enabled this feature in error, please disable the feature. If you have not purchas
    ed the license, please contact your Cisco account team to order the license. It is in violation of Cisco’s Terms of Use to use this feature wit
    hout purchasing the license.

    Reply
  3. Hi,

    This is what I get when I start my nx os. Can you please help ?

    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
    Total memory is 0x9f000
    Total memory is 0x800000
    Sysconf checksum failed. Using default values
    WARNING: No BIOS Info found
    Sysconf checksum failed. Using default values
    serial –speed=115200 –word=8 –stop=1 –parity=no

    success
    Sysconf checksum failed. Using default values
    Strlen bootflash: is 10
    Device bootflash: is Drive 0x80 Partition 3
    ATE0Q1&D2&C1S0=1
    Trying to read config file /boot/grub/menu.lst.local from (hd0,4)
    Filesystem type is ext2fs, partition type 0x83
    Number of devices detected by BIOS is 1
    Failed. Trying to read config file from (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    Number of devices detected by BIOS is 1

    Reply
    • It depends on Cpu and memory assigned to eve, for first time it took 10-15 min for me… wait for some time and then check.

      Reply
  4. I am getting error as mentioned below in the last, however I followed each every step as it is, kindly help me out.

    loader > dir
    Setting listing for bootflash:
    Number of devices detected by BIOS is 1
    Number of devices detected by BIOS is 1
    Number of devices detected by BIOS is 1
    Going to print files for device bootflash: 1
    .rpmstore
    nxos.7.0.3.I7.4.bin
    bootflash_sync_list
    .swtam
    Number of devices detected by BIOS is 1
    Number of devices detected by BIOS is 1
    Number of devices detected by BIOS is 1
    Clearing listing for bootflash:

    loader > boot nxos.7.0.3.17.4.bin
    Booting nxos.7.0.3.17.4.bin
    Trying diskboot
    dev_str: bootflash: partition_str: 3 filename_str /nxos.7.0.3.17.4.bin
    command = root (hd0,3)
    Filesystem type is ext2fs, partition type 0x83
    Formed cmdline console=ttyS0,115200n8nn loader_ver=”5.01.0″ quiet debug
    Formed cmdline console=ttyS0,115200n8nn loader_ver=”5.01.0″ quiet debug ksimg=nxos.7.0.3.17.4.bin card_index=21099 dummy_sprom swiotlb=48000
    Booting kickstart image: bootflash::3:/nxos.7.0.3.17.4.bin….
    Number of devices detected by BIOS is 1
    ERROR

    image length read 0

    image hash: c941e6b0 ae3ecc98 72f8a26f ddcd986d
    Boot failed

    Error 9: Unknown boot failure

    please please please help me out!

    Reply
  5. 3h
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,6f771edf-c83a-436d-b8b7-17c23a9d59e0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,a3332,136c9c75-7a50-48c4-14b3-13c1cb3c6bea)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,ac000,146666,85b96414-6e94-4247-0da6-51c8adbc7073)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,1f2800,6b199c,894191e4-652d-40e6-5c83-e25699d1a666)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,8a4800,146666,a215830b-694d-42ac-369c-27779994b529)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,9eb000,146666,283e2bb9-9e0b-4e86-33ac-52dff90441d0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,b31800,4c8000,a4217258-e536-4282-6cb8-aaf9db72d657)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,6f771edf-c83a-436d-b8b7-17c23a9d59e0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,a3332,136c9c75-7a50-48c4-14b3-13c1cb3c6bea)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,ac000,146666,85b96414-6e94-4247-0da6-51c8adbc7073)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,1f2800,6b199c,894191e4-652d-40e6-5c83-e25699d1a666)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,8a4800,146666,a215830b-694d-42ac-369c-27779994b529)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,9eb000,146666,283e2bb9-9e0b-4e86-33ac-52dff90441d0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,b31800,4c8000,a4217258-e536-4282-6cb8-aaf9db72d657)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
    Total memory is 0x9f000
    Total memory is 0x800000
    Sysconf checksum failed -1, Using default values
    WARNING: No BIOS Info found
    Sysconf checksum failed -1, Using default values
    serial –speed=115200 –word=8 –stop=1 –parity=no

    success
    Sysconf checksum failed -1, Using default values
    Strlen bootflash: is 10
    Device bootflash: is Drive 0x80 Partition 3
    ATE0Q1&D2&C1S0=1
    Trying to read config file /boot/grub/menu.lst.local from (hd0,4)
    Filesystem type is ext2fs, partition type 0x83
    Number of devices detected by BIOS is 1
    Failed. Trying to read config file from (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    Number of devices detected by BIOS is 1
    3h
    3h
    ==========================================================================
    mkdir /opt/unetlab/addons/qemu/nxosv9k-7.0.3.I7.4/
    file: sataa.qcow2

    Hello dear friend. I installed Nexus Image, just it did not start. could u help me pls?

    Reply
  6. 3h
    3h
    3h
    3h
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,6f771edf-c83a-436d-b8b7-17c23a9d59e0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,a3332,136c9c75-7a50-48c4-14b3-13c1cb3c6bea)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,ac000,146666,85b96414-6e94-4247-0da6-51c8adbc7073)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,1f2800,6b199c,894191e4-652d-40e6-5c83-e25699d1a666)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,8a4800,146666,a215830b-694d-42ac-369c-27779994b529)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,9eb000,146666,283e2bb9-9e0b-4e86-33ac-52dff90441d0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,b31800,4c8000,a4217258-e536-4282-6cb8-aaf9db72d657)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,6f771edf-c83a-436d-b8b7-17c23a9d59e0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,a3332,136c9c75-7a50-48c4-14b3-13c1cb3c6bea)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,ac000,146666,85b96414-6e94-4247-0da6-51c8adbc7073)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,1f2800,6b199c,894191e4-652d-40e6-5c83-e25699d1a666)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,8a4800,146666,a215830b-694d-42ac-369c-27779994b529)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,9eb000,146666,283e2bb9-9e0b-4e86-33ac-52dff90441d0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,b31800,4c8000,a4217258-e536-4282-6cb8-aaf9db72d657)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
    /ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
    Total memory is 0x9f000
    Total memory is 0x800000
    Sysconf checksum failed -1, Using default values
    WARNING: No BIOS Info found
    Sysconf checksum failed -1, Using default values
    serial –speed=115200 –word=8 –stop=1 –parity=no

    success
    Sysconf checksum failed -1, Using default values
    Strlen bootflash: is 10
    Device bootflash: is Drive 0x80 Partition 3
    ATE0Q1&D2&C1S0=1
    Trying to read config file /boot/grub/menu.lst.local from (hd0,4)
    Filesystem type is ext2fs, partition type 0x83
    Number of devices detected by BIOS is 1
    Failed. Trying to read config file from (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    Number of devices detected by BIOS is 1
    3h
    3h
    ===========================================
    directory: /opt/unetlab/addons/qemu/nxosv9k-7.0.3.I7.4/
    file: sataa.qcow2

    I am getting error. what is that?

    Reply
    • Even I faced similar case..repeated the below command multiple times at loader prompt..and resolved..

      boot nxos.7.0.3.I7.4.bin

      Reply
  7. I setup as described on this page, when nxos boot, I get loader prompt and i run command boot nxos.7.0.3.I7.4.bin.
    But every time I press enter, it adds an extra carriage return and this is messing up initial config as yes to abort auto provisioning also feeds carriage return to setup secure paasword and then when setting initial password and enter, will also feed a carriage return to confirmation password making confirmation password blank and it wont let me abort.
    How do I get rid/fix extra carriage return?
    Any help is appreciated.
    Charles .

    Reply
  8. I’ve followed the steps exactly but I have my own image – nxosv.9.2.3.qcow2. When I go to open up program, it just hangs. I waited overnight. It is set to defaults – 2 cpu, 8192 memory, etc… I even changed the name as the instructions state from nxosv,9.2.3.qcow2 to sataa.qcow2 but the switch won’t stay on unless I either capitalize the S in sataa.qcow2 or add nxosv9k-sataa.qcow2 to the Linux name. I’ve fixed permissions a dozen times. I even tried VNC instead of putty or secureCRT. VNC just states not boot. Both putty and secureCRT just hangs there when I have the Sataa.qcow2 or nxosv9k-sataa.qcow2 applied. Can someone please help me out? I’ve tried on two different laptops. One laptop I have the vL2/L3 configure. This one I don’t have configured but same thing happens. I need to create a lab for VPC configuration between several pairs of L3 switches.

    Reply
  9. help me..

    If you proceed the same as above, the following log pops up and you cannot boot normally

    image hash: 6d201ff6 47c0a72e fd4ccef8 3d0c979d
    [ 6.431671] [1574832083] Error: Could not find mtd devices

    Reply
  10. The switch is powering on and then automatically stops following the above steps.
    assigned CPU – 3 and Memory – 1888 MB in Eve-ng

    Reply

Leave a Reply

%d bloggers like this: