Nokia vSIM not working in eve-ng community V5

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

rpnz
Posts: 9
Joined: Fri Nov 12, 2021 6:30 am

Nokia vSIM not working in eve-ng community V5

Post by rpnz » Tue May 31, 2022 8:08 am

Hi there,
I have been using the old of version eve-ng and now I have decided to build a new server with eve-ng community V5. I still have old server to compare if I run into issues on my new bare metal build.
Here is the issue:
When I try to boot up Nokia vSIM (I also have valid licenses) it boots up as VSR-I and not as vSIM. It also does not recognize the line card and chassis type I have configured for.
Here is an example:
My Timos line for CPM is:

Code: Select all

slot=A chassis=SR-12 sfm=m-sfm5-12 card=cpm5
and for the line card is:

Code: Select all

slot=1 chassis=SR-12 card=iom3-xp-c mda/1=m10-1gb-xp-sfp
I have the valid UUID etc.
When it boots up it validates the license file as I can see the following output from the console:

Code: Select all

Looking for cf3:/bof.cfg ... OK, reading

Contents of Boot Options File on cf3:
    primary-image    cf3:\timos\i386-both.tim
    primary-config   cf3:\config.cfg
    license-file     cf3:\lic.txt
    autonegotiate
    duplex           full
    speed            100
    wait             3
    persist          off
    no li-local-save
    no li-separate
    console-speed    115200

Hit a key within 1 second to change boot parameters...    

Primary image location: cf3:\timos\i386-both.tim
Loading image cf3:\timos\i386-both.tim
Version B-21.7.R2, Wed Sep 15 12:57:16 PDT 2021 by builder in /builds/c/217B/R2/panos/main/sros
text:(82549728-->281783008) + data:(45949056-->183560744)

Current Time: TUE MAY 31 07:51:06 UTC 2022
Loading license file for 'TiMOS-B-21.7.R2' from: cf3:\lic.txt ... OK
You can see it reads and loads the lic.txt file correctly.

Now here is the issue when I login this is what I see (at the command prompt it should say vSIM on the first boot and not VSR-I, my license is for vSIM and not VSR-I):

Code: Select all

ttempting to exec primary configuration file:
   'cf3:\config.cfg' ...
Executed 0 lines in 0.0 seconds from file cf3:\config.cfg

Login: admin
Password: 

<snip>

A:VSR-I#
As you can see below the chassis type shown is VSR-I which is not what I provided above.

Code: Select all

A:VSR-I# 
A:VSR-I# show chassis 
===============================================================================
System Information
===============================================================================
  Name                              : VSR-I
  Type                              : VSR-I
  Chassis Topology                  : Standalone
  Location                          : (Not Specified)
  Coordinates                       : (Not Specified)
  CLLI code                         :           
  Number of slots                   : 2
  Oper number of slots              : 2
  Num of faceplate ports/connectors : 0
  Num of physical ports             : 0
  Base MAC address                  : 00:00:ff:00:00:00
  FP Generations                    : None
  System Profile                    : none

===============================================================================
Chassis Summary
===============================================================================
Chassis   Role                Status
-------------------------------------------------------------------------------
1         Standalone          up      
===============================================================================
Here is the same node booting up on the older or previous version of eve-ng community edition:

Code: Select all

Attempting to exec primary configuration file:
   'cf3:\config.cfg' ...
Executed 0 lines in 0.1 seconds from file cf3:\config.cfg

Login: admin
Password: 

<snip>

A:vSIM# 

show commands:

Code: Select all

:vSIM# show chassis 
===============================================================================
System Information
===============================================================================
  Name                              : vSIM
  Type                              : 7750 SR-12
  Chassis Topology                  : Standalone
  Location                          : (Not Specified)
  Coordinates                       : (Not Specified)
  CLLI code                         :           
  Number of slots                   : 12
  Oper number of slots              : 12
  Num of faceplate ports/connectors : 0
  Num of physical ports             : 0
  Critical LED state                : Off
  Major LED state                   : Off
  Minor LED state                   : Off
  Over Temperature state            : OK
  Base MAC address                  : 02:01:ff:00:00:00
  Admin chassis mode                : d
  Oper chassis mode                 : d
  FP Generations                    : None
  System Profile                    : none
                                      
===============================================================================
Chassis Summary
===============================================================================
Chassis   Role                Status
-------------------------------------------------------------------------------
1         Standalone          up
===============================================================================

Code: Select all

A:vSIM# show card 

===============================================================================
Card Summary
===============================================================================
Slot      Provisioned Type                         Admin Operational   Comments
              Equipped Type (if different)         State State         
-------------------------------------------------------------------------------
1         (not provisioned)                        up    unprovisioned 
              iom3-xp-c                            
A         cpm5                                     up    up/active     
B         cpm5                                     up    down/standby  
              (not equipped)                       
===============================================================================
Any one please help me resolve this issue. I have looked everywhere and cannot see why this is not working on eve-ng community V5.
Any help will be really appreciated please.

abmedhat
Posts: 5
Joined: Tue Aug 06, 2019 4:33 pm

Re: Nokia vSIM not working in eve-ng community V5

Post by abmedhat » Tue May 31, 2022 1:04 pm

Hello,

I think I have the same issue with SROS 21.7 and 20.10, with small differences:
1. license file is not recognized
2. routers keep on crashing and rebooting

Tried to use different Qemu versions "2.2 and 6.0" but it didn't help.

Code: Select all


KVM based vcpu
Running in a KVM/QEMU virtual machine
ACPI: found 2 cores, 2 enabled

Total Memory: 4GB  Chassis Type: 0x1f  Core Freq: 2400.084 MHz
TiMOS-L-21.7.R2 boot/i386 Nokia 7750 SR Copyright (c) 2000-2021 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 15 12:57:16 PDT 2021 by builder in /builds/c/217B/R2/panos/main/sros

TiMOS BOOT LOADER
Time from clock is TUE MAY 31 12:23:44 2022 UTC
Switching serial output to sync mode...   done

Looking for cf3:/bof.cfg ... OK, reading

Contents of Boot Options File on cf3:
    primary-image    cf3:\timos\i386-both.tim
    primary-config   cf3:\config.cfg
    autonegotiate
    duplex           full
    speed            100
    wait             3
    persist          off
    no li-local-save
    no li-separate
    console-speed    115200

Hit a key within 1 second to change boot parameters...    

Primary image location: cf3:\timos\i386-both.tim
Loading image cf3:\timos\i386-both.tim
Version B-21.7.R2, Wed Sep 15 12:57:16 PDT 2021 by builder in /builds/c/217B/R2/panos/main/sros
text:(82549728-->281783008) + data:(45949056-->183560744)
No license file specified
Executing TiMOS image at 0x150000

KVM based vcpu
Running in a KVM/QEMU virtual machine
ACPI: found 2 cores, 2 enabled
2 paravirtualized E1000 devices are detected

Total Memory: 4GB  Chassis Type: 0x1f  Core Freq: 2400.084 MHz
TiMOS-B-21.7.R2 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2021 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 15 12:57:16 PDT 2021 by builder in /builds/c/217B/R2/panos/main/sros


   ___                    ___           ___           ___
  /\  \                  /\__\         /\  \         /\  \
  \:\  \        ___     /::|  |       /::\  \       /::\  \
   \:\  \      /\__\   /:|:|  |      /:/\:\  \     /:/\:\  \
   /::\  \    _\/__/  /:/|:|__|__   /:/  \:\  \   _\:\~\:\  \
  /:/\:\__\  /\__\   /:/ |::::\__\ /:/__/ \:\__\ /\ \:\ \:\__\
 /:/  \/__/ /:/  /   \/__/~~/:/  / \:\  \ /:/  / \:\ \:\ \/__/
/:/  /     /:/  /          /:/  /   \:\  /:/  /   \:\ \:\__\
\/__/      \/__/          /:/  /     \:\/:/  /     \:\/:/  /
                         /:/  /       \::/  /       \::/  /
                         \/__/         \/__/         \/__/

Running 64 bit architecture

Initializing VMM
  Virtual address sharing is disabled
Time from clock is TUE MAY 31 12:24:32 2022 UTC
Initial DNS resolving preference is ipv4-only
SMP: 2 cores available

Attempting to exec primary configuration file:
   'cf3:\config.cfg' ...
Executed 0 lines in 0.1 seconds from file cf3:\config.cfg

Login: 017 s 05/31/22 12:24:36.425: 
tRootTask: Assertion "boot_cpu_feature_is_supported(CPU_FEATURE_SSE42)" failed
   File: pchipsim/vfp_main.cpp  Line: 4159  Function: vfp_pchip_init
   Message: "VFP requires a CPU that supports the SSE 4.2 instruction set"
   Stack Trace:
   0x23136d0, i386StackBackTrace (0x023136d0) + 0x0
   0x235b719, stackBackTrace (0x0235b710) + 0x9
   0x24dff83, timosAssert (0x024dfd50) + 0x233
   0x77a59c7, vfp_pchip_init (0x077a5760) + 0x267
   0x7780bdd, VFP_PCHIP::VFP_PCHIP(unsigned char, bool, EITHER_CONFIG_PTR) [subobject] (0x07780bb0) + 0x2d
   0x778124c, hwSimNpchipDriverInitialize (0x077811d0) + 0x7c
   0x778132d, hwNpchipDriverInitialize (0x07781320) + 0xd
   0x9301fb1, pDriverInitialize (0x09301c60) + 0x351
   0x9302508, np3chipDriverInitialize (0x093024f0) + 0x18
   0x93469a8, hwRchipChipDriverInitialise (0x09346900) + 0xa8
   0x9347e9a, hwRchipGlobalChipInitialise (0x09347c50) + 0x24a
   0x92fe3dd, rchipGlobalChipInitialise (0x092fe3d0) + 0xd
   0x36c9fdf, iom_initialize_drivers(unsigned char) (0x036c9f50) + 0x8f
   0x36d1570, iom_start_tasks(bool) (0x036d1520) + 0x50
   0x36d3b4e, pnIomMain (0x036d38c0) + 0x28e
   0xb70bf1a, pnMainPrivate (0x0b70942a) + 0x2af0
   0xb709009, pnMain (0x0b708ffd) + 0xc
   0xb748568, usrRoot (0x0b748130) + 0x438
   0xb5c22cf, vxTaskEntry (0x0b5c22b0) + 0x1f

System Crash Dump Written - Please run the command
`admin tech-support` and contact your Nokia
support representative.

Rebooting...
Using preloaded VxWorks boot loader at 0x0000000000008000, size 0x0007D000, entrypoint 0x0000000000008010

KVM based vcpu
Running in a KVM/QEMU virtual machine
ACPI: found 2 cores, 2 enabled

rpnz
Posts: 9
Joined: Fri Nov 12, 2021 6:30 am

Re: Nokia vSIM not working in eve-ng community V5

Post by rpnz » Tue May 31, 2022 7:44 pm

@abmedhat
For crashing and rebooting issue I fixed it using following flag for qemu options:
-cpu host

As part of the error message it is looking for the following CPU feature:

Code: Select all

tRootTask: Assertion "boot_cpu_feature_is_supported(CPU_FEATURE_SSE42)" failed
So if you pass -cpu host, it should resolve the crashing issue, I had the same for some reason only in eve-ng community V5. In my older eve-ng community version this is not the case.
Not sure what has changed.

That should fix it.

I think this option may need to be part of the default template option.

See if that works.

I still have issue where it is only coming up as VSR-I. Not sure how to fix this issue.

abmedhat
Posts: 5
Joined: Tue Aug 06, 2019 4:33 pm

Re: Nokia vSIM not working in eve-ng community V5

Post by abmedhat » Wed Jun 01, 2022 7:14 pm

@rpnz

the -cpu host solved the reboot issue, however it still boots as VSR-I and also not being able to read the license file.

mamakos
Posts: 43
Joined: Thu Dec 19, 2019 4:49 pm

Re: Nokia vSIM not working in eve-ng community V5

Post by mamakos » Thu Jun 02, 2022 5:37 am

Hi,

Did you try increasing RAM to 8G for CPM and IOM ?
With the latest releases this is consuming a lot.

Did you only try qemu 2.2 and 6.0 ? On the Pro version 4 I had to stick to 5.2 (or 5.1.2 I do not recall)

I have not upgraded yet to pro V5 for I wanted to make sure things were still working for other users :)

rpnz
Posts: 9
Joined: Fri Nov 12, 2021 6:30 am

Re: Nokia vSIM not working in eve-ng community V5

Post by rpnz » Thu Jun 02, 2022 8:53 am

abmedhat wrote:
Wed Jun 01, 2022 7:14 pm
@rpnz

the -cpu host solved the reboot issue, however it still boots as VSR-I and also not being able to read the license file.
How are you configuring the license file for vSIM?
Are you adding the license to image using the following method:
https://www.eve-ng.net/index.php/docume ... nokia-vsr/

And also are configuring the matching UUID?

Thanks

rpnz
Posts: 9
Joined: Fri Nov 12, 2021 6:30 am

Re: Nokia vSIM not working in eve-ng community V5

Post by rpnz » Thu Jun 02, 2022 9:36 am

mamakos wrote:
Thu Jun 02, 2022 5:37 am
Hi,

Did you try increasing RAM to 8G for CPM and IOM ?
With the latest releases this is consuming a lot.

Did you only try qemu 2.2 and 6.0 ? On the Pro version 4 I had to stick to 5.2 (or 5.1.2 I do not recall)

I have not upgraded yet to pro V5 for I wanted to make sure things were still working for other users :)
In my case I have increased the memory and also tried all the different versions of Qemu.
Same result, it boots up as VSR-I and not vSIM, same issue as in my original post.
It will really good if some can comment on how we can fix this.

mamakos
Posts: 43
Joined: Thu Dec 19, 2019 4:49 pm

Re: Nokia vSIM not working in eve-ng community V5

Post by mamakos » Fri Jun 03, 2022 4:45 pm

rpnz wrote:
Thu Jun 02, 2022 8:53 am
How are you configuring the license file for vSIM?
Are you adding the license to image using the following method:
https://www.eve-ng.net/index.php/docume ... nokia-vsr/

And also are configuring the matching UUID?
For vSIM, I have the router download the license on boot thanks to the "Timos License Path" in the CPM-node properties (in the EVE GUI). I use an FTP server and I give the URL. The only thing is to make sure your FTP server is in the same LAN as your CPM management address :)

Code: Select all

ftp://anonymous:anonymous@<FTP_srv_IP>/licence_vSIM_R22.txt
Also, UUID for both CPM and Linecard VM must match and have to match the license's UUID.


Here is the Timos Line I use
  • on CPM

Code: Select all

slot=A chassis=SR-12 sfm=m-sfm5-12 card=cpm5
  • on the Linecard

Code: Select all

slot=1 chassis=SR-12 sfm=m-sfm5-12 card=iom4-e mda/1=me10-10gb-sfp+
Regarding Qemu (on Pro 4.0.1-86) I use the 5.2.0 one.

And for QEMU otpions
  • CPM :

Code: Select all

-machine type=pc,accel=kvm -serial mon:stdio -nographic -no-user-config -nodefaults -rtc base=utc
  • Line card :

Code: Select all

-machine type=pc,accel=kvm -serial mon:stdio -nographic -no-user-config -nodefaults -rtc base=utc

rpnz
Posts: 9
Joined: Fri Nov 12, 2021 6:30 am

Re: Nokia vSIM not working in eve-ng community V5

Post by rpnz » Sat Jun 04, 2022 5:35 am

Hi,
In my case I do not have any issues with license or booting up the node.
I have tried all the different versions of Qemu and the node boots up but it always boots up as VSR-I.

This is not correct. It should boot up as vSIM.

I have used another tool to boot same image on the same HW and it boots up fine as vSIM.

It only boots up as VSR-I on the new version of eve-ng, i.e. V5.

Can someone please help.

Thanks

mamakos
Posts: 43
Joined: Thu Dec 19, 2019 4:49 pm

Re: Nokia vSIM not working in eve-ng community V5

Post by mamakos » Sat Jun 04, 2022 9:27 am

I am afraid only Uldis can help. Maybe via the live chat-support.
If you happen to understand and get a solution/explanation please let us know

By the way I saw that a new release of V5 came out a couple of hours/days ago. Maybe this solves the issue (although this is not mentioned in the release notes)

Post Reply