SIM card related Projects » osmo-remsim

• assembled hardware
• configured host system for libvirt, remsim-server, sshd
• moved to osmocom-network segment (vlan25)
• added cardreader

• 2x kvm debian9 inside the debian9 on apu2 for remsimbank and remsimclient(s)
• added nightly feeds to all debian
• usb from acs reader routed into remsimbank vm
• autostart vms
• installed osmo-* daemons in respective vm
• network segment for vms: 10.9.99.0/24 - .1 server .10 client .30 simbank

• tc netem
• systemd servicefiles for all daemons
• qmod/modems
• simcards

• systemd servicefiles for -bankd and -server
• qmod/modems connected - may need to move to a different usb controller (issues pushing all parts of the device to vm)

• tested usb forwarding via complete seperate usb port - no go on apu due to hw limits.
• swapped the vm for -client and host for -server due to usb/pci forwarding limitations (qmod needs to be on host)
• systemd servicefile template (copy 4 times and configure for specific modems)

• systemd servicefile for osmo-remsim-client using proper templating (no copying servicefile around anymore), just add more configs.

• netem
• manual testing/verification

• updated all install/vm
• the clients now have proper ids (-n 0-3)
• basic netem setup (inmarsat-style 300ms / 150ms jitter / 50% corrlation / 512kBit)
  on network output of remsimserver-vm - do we need a more complicated setup here? it feels proper laggy to me.

• real tests/load/traffic on all components (do we have a list of things to probe already?)
• which testrunner to use?

• documentation of the setup https://osmocom.org/projects/osmo-remsim/wiki/Osmo-remsim

i think we need a bigger ssd for this machine. it ran out of disk twice now.

it has 2 images for the vm (4g each) and 4g swap, which results in about 500mb free when i delete all old logs.
i tried adding it to the monitoring but we have another blocking issue there. (#4664)

kevin got access a few days ago, so he can help get some traffic on those simcards.

how will this work exactly? jenkins will log in via ssh and key and trigger some script?

• swapped the simcards to sysmoUSIM.

done: * upgraded ssd to 240G, copied system, fixed uuid, resized / to 100Gb, grown swap to 16Gb, added remaining diskspace to /space

I cannot find any mention of the IP adresss of thee system. roh please add.

its on 10.9.25.90/24

i noted it in https://osmocom.org/projects/osmo-remsim/wiki/Osmo-remsim#Test-Suite (only on the graphic)

I'm currently upgrading the system and the VMs to buster. We shouldn't start to deploy new systems based on oldstable, it just means we need to migrate at some point sooner than neccessary.

sorry, yes.
i think this was due to buster being released in july and the install happening beforehand.

• CP2102 USB UART for ST12 of QMOD
• CP2102 USB UART for ST34 of QMOD

• added a usb-hub (apu only has 2 ports and both were used)
• added 2x cp2102
• soldered pinheader
• added 2.5mm to pinheader adapters.

it took me quite a while to get the osmo-remsim-client working again (the usb path changed obviously) and to figure out that the cp2102 i used were broken before or have problems with the high baudrate (looks like binary)

is there any (standard distro shipped) tool to display usb-paths besides lsusb.py?

packaging is now a cardboard box to contain the cp2102 and usbhub.

for some reason i cannot edit the checklist item (grayed out).

also somebody disabled the start of osmo-remsim-client@[0-3] for reasons i do not know.

roh, please upgrade the system to latest dfu bootloader + cardem, and install latest nightly packages of libosmo-simtrace2 + osmo-remsim-*. Might be a good idea to try the script tsaitgaist produced (where is it? in some ticket here?) for full upgrade with multiple steps, including DFU loader upgrade via DFU. mschramm might know more?

Note: The client side package name has changed from osmo-remsim-client to osmo-remsim-client-st2

minimum osmo-remsim software version:0.2.2.80.b797
minimum cardem/dfu firmware: 0.7.0.54-823f

done

the packages on the 3 debian machines were updated to -nightly

hardware was manually updated according to https://projects.sysmocom.de/projects/quad-modem-board/wiki/Board_Update

pushed https://gerrit.osmocom.org/c/osmo-remsim/+/17389 to fix the systemd startscripts - paramter for ip was -s and is -i now, and proper client ids

laforge wrote:

roh, please upgrade the system to latest dfu bootloader + cardem, and install latest nightly packages of libosmo-simtrace2 + osmo-remsim-*. Might be a good idea to try the script tsaitgaist produced (where is it? in some ticket here?) for full upgrade with multiple steps, including DFU loader upgrade via DFU. mschramm might know more?

Note: The client side package name has changed from osmo-remsim-client to osmo-remsim-client-st2

the script taking care/simplifying of updating can be found here: https://git.osmocom.org/simtrace2/tree/contrib/flash.py

i think this can be closed or have i missed a feature?