Nokia-VSR-VM-15.0.R5 crashes on loginprompt

[joverdijk]

Hi

I'm running Nokia-VSR-VM-15.0.R5 (downloaded from AlcatelLucent site with my account) in GNS3, but it crashes.
Info:

I use original qcow2 image from the zip-file.
Settings in GNS3:
2048 MB
vCPUs
Qemu binary: /usr/bin/qemu-system-x86_64 (v2.5.0)
6 network adapters (e1000)
Advanced settings: -smp 2

When booting, TiMOS boots until login-prompt, and then crashes with Fatal Error: CORE0 dead. Rebooting!



Total Memory: 3071MB Chassis Type: 0x1f Core Freq: 3695.816 MHz
TiMOS-B-15.0.R5 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2017 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 27 14:53:19 PDT 2017 by builder in /builds/150B/R5/panos/main


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

Running 64 bit architecture

Initializing VMM
Virtual address sharing is disabled
Time from clock is MON JUL 09 20:35:12 2018 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.0 seconds from file cf3:\config.cfg

TiMOS-B-15.0.R5 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2017 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Wed Sep 27 14:53:19 PDT 2017 by builder in /builds/150B/R5/panos/main


Login:
Fatal Error: CORE0 dead. Rebooting!

Watchdog: Task 0x235b6260 (sysMonitor) blocked for 113 ticks.
90a934d vxTaskEntry +1d : sysMonitorTask (0, 0, 0, 0)
67d66a7 sysMonitorTask +257: wdCheckForFailedCores (0, 0, 0, 0)
67d39c5 wdCheckForFailedCores+125: timosCrashDumpGeneral (1000000008, 0, 6564203045524f43, 6461)
1bf23b5 timosCrashDumpGeneral+25 : timosCrashDumpSystemState (0, 1, 253a3310, 67d39ca)
1bf2208 timosCrashDumpSystemState+a8 : debugDisplayBootLog (5b43c707253a32b0, 1a, 204c554a204e4f4d, 35333a3032203930)
1c0e811 debugDisplayBootLog+11 : debugCloseBootLog (1, 1, 253a3270, 1bf220d)
1c0e7ee debugCloseBootLog+9e : debugSaveBootLog (253a31f0, 1bf0fe5, 12a410, 1)
1c0e6e7 debugSaveBootLog+77 : debugWriteBootLog (0, 235b6260, 253a3040, 9140aab)
1c0e619 debugWriteBootLog+29 : openURL (ffffffffffffffff, 0, 1, 0)
1b106e2 openURL +12 : openURLWithError (253a2e90, 12a410, 253a3010, 1c0e61e)
1b106c0 openURLWithError+10 : openURLWithTimeoutWithError (0, 235bc440, 253a2e30, 1b106e7)
1b10674 openURLWithTimeoutWithError+54 : openParsedUrl (253a2de0, 6010914eff0, a49b2a6e, 253a2e40)
1b104f5 openParsedUrl +195: urlOpenFile (253a2e6c, 253a2eb0, 500000000, 253a2e40)
1b0e267 urlOpenFile +17 : open (253a2d40, 253a2e40, 253a2da0, 1b104fa)
911509d open +8d : iosOpen (6b00000050, 4000000000000a, 24198410, 1fffff001fffff)
9116821 iosOpen +21 : dosFsOpen (253a2d20, 91150a2, 6b00000050, 4000000000000a)
90b81c6 dosFsOpen +e6 : cbioIoctl (0, 6800000000, 0, 253a2bf0)
916e183 cbioIoctl +33 : dpartIoctl (0, ffffffffffffffff, 24198410, 253a2bf0)
90bf62b dpartIoctl +11b: dcacheIoctl (68, 241993a8, cb100001, 0)
90b32a2 dcacheIoctl +2c2: dcacheChangeDetect (253a2b00, 241993a8, 0, cb100001)
90b1e5e dcacheChangeDetect+2e : dcacheBlockGet (241a1be0, 0, 1dfa1560, ffff1eef)
90b28a1 dcacheBlockGet +71 : dcacheBlockFill (253a2a80, 241a1be0, 1dfa1560, 1)
90b2570 dcacheBlockFill+a0 : blkWrapBlkRW (253a2a60, 241a1e10, 253a2e40, 241a1e10)
916ebc8 blkWrapBlkRW +198: ataBlkRd (40, 2428d7d0, 4000000000, 4000000000)
916a3f7 ataBlkRd +7 : ataBlkRW (253a2a00, 916ebca, 40, 2428d7d0)
916a658 ataBlkRW +138: ataRW (40, 0, 16e33578, 0)
916b122 ataRW +1e2: semTake (253a3100, ffffffa0253a2aa0, 0, 2428d7d0)
914717a semTake +7a : semBTake (253a2930, 40, 40, 16e330c0)
91464d8 semBTake +a8 : windKernelExit (16e33500, 1f4, 253a2840, 2460914640b)
*** Blocked task info during crash dump - ending ***

[Stoffen]

Hi.
I get the same error when I try SROS-15.0.R1 in my GNS3 setup.
I do suspect this might be related to spesific CPU features in SROS15 that GNS3 / GNS3-VM cannot provide.

When I try with only one CPU allocated, I don't get the erorr, but it does a hardboot

Code: Select all

TiMOS-B-15.0.R1 both/x86_64 Nokia 7750 SR Copyright (c) 2000-2017 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Tue Mar 7 09:53:27 PST 2017 by builder in /builds/rel15.0/150B/R1/panos/main


Login:
       Rebooting...

[joverdijk]

Hi

Yeah we'll I'm not sure it's a GNS3 thing, because, in meanwhile I did some further testing and If I start the OVA-image straight in VMWare Fusion (Mac) I get the exact same thing. So that has nothing to do with GNS3.

I'd like to run version 15 because I'm running that on our XRS7950s and I want to do some lab-work together with GNS3.
Does anybody know which (recent) version is stable with GNS3? So not the 12's and 13's .....

[Stoffen]

Doing some testing with 14.0.R10 in GNS3 now.
It seems like two SROS14 devices can communicate with each other, but one SROS13 and one SROS14 device have some issues.
Not sure why this happens.

I have licensed vSIM's (v13 & v14), but when I apply the license to the correct UUID in GNS3, it accepts it but still its a mismatch.
However, I do get full functionality but with reboot every 60 minutes on SROS14.

Will continue to test this out, but as far as I can tell, SROS13 is the most stable, most reliable SROS system in GNS3.

[Stoffen]

Tests so far:

SROS13 = 13.0.R4, vCPU = 1, Mem = 2048, NIC = 6
SROS14 = 14.0.R11 vCPU = 2, Mem = 4096, NIC = 6
IOS-XR = 5.1.3 vCPU = 2, Mem = 4096, NIC = 5

SROS13 default interface MTU: 8922
SROS14 default interface MTU: 9198

SROS13 <-> SROS13: OK
SROS13 <-> SROS14: Lot of packetloss / high latency
SROS13 <-> Cisco IOS-XR: OK
SROS14 <-> Cisco IOS-XR: Packetloss / high latency.
SROS14 <-> SROS 14: Packetloss / high latency

For now, I'll keep my previous statement, that SROS13 is more compatible with GNS3 than SROS14.

[Stoffen]

Just came across this article:

https://community.gns3.com/discussions/ ... s-15-x-ima

Playing around with some SMBIOS settings now.
Still havent connected the SROS14 devices, but for now the license is valid !

Code: Select all

===============================================================================
System Information
===============================================================================
System Name            : SR04
System Type            : 7750 SR-c4
Chassis Topology       : Standalone
System Version         : B-14.0.R11


===============================================================================
Current License
===============================================================================
License status : monitoring, valid license record
Time remaining : n/a
-------------------------------------------------------------------------------
...
License prod   : Virtual-SIM
License sros   : TiMOS-[BC]-14.0.*
Current date   : THU JUL 12 10:40:52 UTC 2018
Issue   date   : FRI JUN 10 11:01:29 UTC 2016
Start   date   : MON JUN 15 00:00:01 UTC 2015
End     date   : n/a
===============================================================================

[Stoffen]

So, I've created a distributed SROS14 environment in GNS3, so to do this, you need two VM's

Code: Select all

VM CPM/SFM: 
vCPU 2, MEM: 4096, NIC: 2 (First port A/1, name format: 1/1/{port0}), 
Advanced options: -nographic  -enable-kvm -uuid <my uuid> -smbios type=1,product="TIMOS:slot=A chassis=SR-7 card=sfm4-7"

VM IOM1:
vCPU 2, MEM: 4096, NIC: 6 (First port A/1, name format: 1/1/{port0})
Advanced options: -nographic  -enable-kvm -smbios type=1,product="TIMOS:slot=1 chassis=SR-7 card=iom3-xp-c mda/1=m5-1gb-sfp-b"

Load license on CPM/SFM VM.
Connect SFM/CPM port 1/1/0 to IOM port 0/0/0 either directly or via ethernet switch.
This will be the virtual switch-fabric between the linecards.
Provision the IOM and MDA.

I do believe this will work in SROS 15 as well, but I havent tested it yet.

Edit:
IP connectivity between SROS 13 and 14 is now good!

[Stoffen]

Update with SROS15:

Code: Select all

*A:SROS# show system information

===============================================================================
System Information
===============================================================================
System Name            : SROS
System Type            : 7750 SR-7
Chassis Topology       : Standalone
System Version         : C-15.0.R1

A:SROS# show card state

===============================================================================
Card State
===============================================================================
Slot/  Provisioned Type                  Admin Operational   Num   Num Comments
Id         Equipped Type (if different)  State State         Ports MDA
-------------------------------------------------------------------------------
1      iom3-xp-c                         up    up                  2
1/1    m10-1gb-hs-sfp-b                  up    up            10
A      sfm4-7                            up    up                      Active
B      sfm4-7                            up    down                    Standby
           (not equipped)
===============================================================================

*A:SROS# show system license

===============================================================================
Current License
===============================================================================
License status : monitoring, valid license record
Time remaining : n/a
-------------------------------------------------------------------------------

GNS3 Advanced options:

Code: Select all

SFM/CPM: -nographic  -enable-kvm -uuid <uuid> -smbios type=1,product="TIMOS:slot=A chassis=SR-7 card=sfm4-7"
IOM1: -nographic  -enable-kvm -smbios type=1,product="TIMOS:slot=1 chassis=SR-7 card=iom3-xp-c mda/1=m10-1gb-hs-sfp-b"

[Stoffen]

Now with redundant CPM/SFM SROS 15.0.R1:

Code: Select all

*A:SROS# show  card state

===============================================================================
Card State
===============================================================================
Slot/  Provisioned Type                  Admin Operational   Num   Num Comments
Id         Equipped Type (if different)  State State         Ports MDA
-------------------------------------------------------------------------------
1      iom3-xp-c                         up    up                  2
1/1    m10-1gb-hs-sfp-b                  up    up            10
A      sfm4-7                            up    up                      Active
B      sfm4-7                            up    up                      Standby
===============================================================================

GNS3 advanced options for slot B:

Code: Select all

-nographic  -enable-kvm -uuid <uuid> -smbios type=1,product="TIMOS:slot=B chassis=SR-7 card=sfm4-7"

Now, port 1/1/0 Slot A, B and IOM1 is connected to an ethernet switch.

[Stoffen]

Some issues with services.
Have created a basic rvpls between SROS13, 14 and 15.
IES bound to RVPLS.
All SDP's are LDP based, and only use spoke.
All services are up.

Ping IES via RVPLS from SROS 14 to SROS 15: Fail.
VPLS FDB: empty except from own

Ping IES via RVPLS from SROS15 to SROS 14: Fail.
VPLS FDB: empty except from own

I can see in wireshark ARP request, and ARP reply with the correct MPLS labels attached according to LDP bindings table, but somehow it does not enter the actual service.

Ping IES via RVPLS from SROS13 to SROS14: OK
VPLS FDB: Populated with MAC from spoke SDP

Ping IES via RVPLS from SROS13 to SROS15: OK
VPLS FDB: Populated with MAC from spoke SDP

Not done too much debugging yet, but this seems a bit weird to me..

Config:
IGP: ISIS, area 49.0000

Code: Select all

        sdp 102 mpls create
            description "to SROS 15"
            far-end 2.2.2.2
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit

        sdp 106 mpls create
            description "to SROS 13"
            far-end 6.6.6.6
            ldp
            keep-alive
                shutdown
            exit
            no shutdown
        exit

        vpls 2 customer 1 create
            allow-ip-int-bind
            exit
            stp
                shutdown
            exit
            service-name "vpls"
            spoke-sdp 102:2 create
                no shutdown
            exit
            spoke-sdp 106:2 create
                no shutdown
            exit
            no shutdown
        exit
        ies 22 customer 1 create
            interface "ies22" create
                address 192.168.22.1/24
                ip-mtu 1500
                vpls "vpls"
                exit
            exit
            no shutdown
        exit

The same configuration is used on the other devices adjusted with correct IP's of course.
MTU on network port between SROS 14 and 13 is adjusted to 8000 bytes.