How to emulate Nokia Service Router (TiMOS SROS)

How to emulate Nokia Service Router (TiMOS SROS)

When studying for NSR1, NSR2 or SRA choosing the right network simulator can be a tough decision. And there’s no best way to go about making your selection. After all, you’ve got an exam coming up. Our opinion and advice is to use eve-ng for all Nokia labs because of its simplicity and powerful. This article How to emulate Nokia Service RouterSROS will discuss about this.

What is EVE-NG?

EVE-NG (Emulated Virtual Environment Next Generation) is a multi-vendor virtual network simulator that, similar to VIRL Personal Edition, was developed for individuals and smaller businesses. They offer a free Community Edition as well as a Professional Edition for $110.75 per year.

You can download Eve-ng Free Community Editon on this link: https://www.eve-ng.net/index.php/download/. Choose OVF version for the next-step.

What is VMware Workstation

VMware Workstation is a line of Desktop Hypervisor products which lets users run virtual machines. For our lab, we use VMware to build Eve-ng for simulation. We recommend to download and use VMware Workstation Pro version. There are many user guide and how to download, setup VMware in the internet so we don’t focus in here.

How to emuxlate Nokia Service Router (TiMOS SROS) with Eve-ng

Setup Eve-ng

You can refer to how to install eve-ng on vmware on the official page of eve-ng.

Download SROS timos-13.0.R4 or timos-15.0.R3. Link update in the comment page.

Let’s start setup:

Step 1: Start up the Eve in the VMWare and get ip to FTP:

Step 2: Use FileZilla upload the SROS to the EVE, default username/password is root/eve

Upload timos-13.0R4 folder (include hda.qcow2 inside) to /opt/unetlab/addons/qemu

Setup Node

Step 1: Login to the eve by browser and create a new lab

You can login to the guide with username/password default is admin/eve. For this exam is http://10.1.1.130

Choose icon Add new lab, write down the Name and Save.

Step 2: Create nodes and optimize

Add an object -> Node and choose some option bellow:

  • Template: Nokia 7750 VSR
  • Number of nodes to add: For example is 2
  • Name/prefix: you can write R. After finish it will appear R1 and R2 for this example.
  • Icon: What eve you want, but Nokia should use SROS.png

After all, you scroll down and click Save

Right click to each node choose Edit and change QEMU custom options as follows and Save:

R13:

-nographic -enable-kvm -uuid 00000000-0000-0000-0000-000000000000 -rtc base=2015-03-10

R15:

-nographic -enable-kvm -uuid 15b03403-d9a5-463b-9816-0884b004a972 -rtc base=2017-07-20

Change Timos Line

slot=A chassis=SR-c12 slot=1 card=iom-xp mcm/1=mcm-xp mda/1=m10-1gb-xp-sfp

R21:

Change Qemu option:

-smbios type=1 -machine type=pc-1.0,accel=kvm -serial mon:stdio -nographic -no-user-config -nodefaults -rtc base=2021-05-01 -cpu host -uuid 00000000-0000-0000-0000-210000000070

Change Timos Line:

chassis=SR-1 slot=A card=iom-1 mda/1=me6-100gb-qsfp28

In this example, you can connect 2 routers together with Port 1/1/1 in router R1 and Port 1/1/1 in router R2

Turn it on, telnet by SecureCRT or PuTTY and login with user/pass is admin/admin.

How to emulate Nokia Service Router (TiMOS SROS)
How to emulate Nokia Service Router (TiMOS SROS)

Let’s try ping test!!!

How to emulate Nokia Service Router (TiMOS SROS)
How to emulate Nokia Service Router (TiMOS SROS)

This is just the base of setup node for learning only. If you have any questions, you can ask for help in here.

Hope you enjoy it and Good luck!

40 thoughts on “How to emulate Nokia Service Router (TiMOS SROS)

    • Bruh says:

      Add the following to the Qemu options:
      -cpu qemu64,+x2apic

      Like this
      -smbios type=1 -machine type=pc-1.0,accel=kvm -cpu qemu64,+x2apic -serial mon:stdio -nographic -no-user-config -nodefaults -rtc base=2021-05-01 -cpu host -uuid 00000000-0000-0000-0000-210000000070

      Reading around different forums R20 and after for Timos seems to be really picky for hardware, also it’s a big resource hog now it instantly eats 2.4G of memory for R21. Old R12 uses 500MB on boot, if it weren’t for lack of supported protocols I wouldn’t use R21 even with EVENG UKSM I think. Ty very much to adminreboot for lic, though. Incredibly helpful to not reboot mid lab.

  1. repotsirc says:

    what if I change the time in the node? (Today’s date is 29 Feb 2024)

    *A:R1# show system license

    ===============================================================================
    System License
    ===============================================================================
    License status : monitoring, valid license record
    Time remaining : 121 days 16 hours
    ——————————————————————————-
    License name : ALCATEL-LUCENT CANADA
    License uuid : 00000000-0000-0000-0000-210000000070
    Machine uuid : 00000000-0000-0000-0000-210000000070
    License desc : NokiaEDU Ottawa VSR-SIM 02 (SROS 20)
    License prod : Virtual-SIM
    License sros : TiMOS-[BC]-21.*
    Current date : SAT MAY 01 08:34:08 UTC 2021
    Issue date : WED MAR 03 13:15:07 UTC 2021
    Start date : n/a
    End date : MON AUG 30 23:59:59 UTC 2021
    ===============================================================================
    *A:R1# show time
    Sat May 1 08:35:18 UTC 2021
    *A:R1#

  2. anas abdullkarim says:

    Hello
    i try to add new MDA for esa/isa
    chassis=SR-1 slot=A card=iom-1 mda/1=me6-100gb-qsfp28 mda/3=isa-tunnel
    but igot error on booting

    sysVmBootStringGenerateInner: ERROR: failed parsing key->’mda’ instance->’3=isa-tunnel’ value->’isa-tunnel’

  3. John says:

    Hello everyone, can you please tell me what the following prompt means:
    A:vSIM#
    there is no configure command available, only:
    A:vSIM#
    admin + Administrative commands for the system
    bof + Configure the Boot Options File
    [no] enable-dynamic* – Enable manual modification of dynamic services in this
    CLI session
    [no] enable-vsd-con* – Enable manual modification of VSD configuration in this
    CLI session
    environment + Environment preference setup commands
    file + File system commands
    help – Display help
    password – Change a local user password
    show + Display configuration and operation information

    Global Commands :

    back – Go back a level in the command tree
    candidate + Commands used for editing candidate configurations
    echo – Echo the text that is typed in
    enable-admin – Enable the user to become a system administrator
    exec – Execute a file – use -echo to show the commands and
    prompts on the screen
    exit – Exit to intermediate mode – use option all to exit to
    root prompt
    help – Display help
    history – Show command history
    logout – Log off this system
    mrinfo – Request multicast router information
    mstat – Trace multicast path from a source to a receiver and
    display multicast packet rate and loss information
    (IGMP based)
    mstat2 – Trace multicast path from a source to a receiver and
    display multicast packet rate and loss information (UDP
    based)
    mtrace – Trace multicast path from a source to a receiver (IGMP
    based)
    mtrace2 – Trace multicast path from a source to a receiver (UDP
    based)
    ping – Verify the reachability of a remote host
    pwc – Show the present working context
    sleep – Sleep for specified number of seconds
    ssh – SSH to a host
    telnet – Telnet to a host
    traceroute – Determine the route to a destination address
    tree – Display command tree structure from the context of
    execution
    write – Write text to another user

    A:vSIM#

    Thanks!

  4. bruh says:

    I am having issues with R15

    Attempting to exec primary configuration file:
    ‘cf3:\config.cfg’ …
    MINOR: CLI Unknown card type “iom-xp”.

    MAJOR: CLI #1009 An error occurred while processing a CLI command –
    File cf3:\config.cfg, Line 1: Command “/configure card 1 card-type “iom-xp”” failed.

    CRITICAL: CLI #1002 The system configuration is missing or incomplete because an error occurred while processing the configuration file.

    Because of this there is no lic and the node boots with nothing configured. Normally this would not be an issue but if there is a fix to

    *A:VSR# show system license

    ===============================================================================
    Current License
    ===============================================================================
    License status : chassis reboot pending, configuration does not match license
    record
    Time remaining : CPM A will reboot the chassis in 60 minutes
    ——————————————————————————-
    License name : […]
    License uuid : […]
    Machine uuid :[…]
    License desc : […]
    License prod : […]
    License sros : TiMOS-[BC]-15.0.*
    Current date : […]
    Issue date : […]
    Start date :[…]
    End date : […]
    ===============================================================================

  5. repotsirc says:

    I’d like to use different card type and mda type such that I can have port operating on 1Gbps instead of anything higher, reason being is that I can only emulate cisco devices using 1Gbps interfaces (enterprise grade routers). For the Timos Line mentioned in the blog only supports the following mda types:

    “me16-25gb-sfp28+2-100gb-qsfp28”
    “me6-100gb-qsfp28”
    “me3-200gb-cfp2-dco”
    “me12-100gb-qsfp28”
    “me3-400gb-qsfpdd”
    “me6-400gb-qsfpdd”
    And none of them are 1Gbps.

    Anyone knows the correct options?

Để lại một bình luận