Alex,
Although you are seeing env.sh errors while starting your netsims, from the existence of 'DEVICE <devname> OK STARTED' it seems you netsims may have started.
You can check the status of the netsism:
$ ncs-netsim status
Have you gone thru the required steps to add you netsim devices to the NSO CDB Device tree?
The devices will not automatically get added to the device tree.
You can add them manually by setting devices/device/<devnam>/* parameters (address, port, authgroup, device-type, state)
OR
You can use the ncs-setup tool to create the device on-boarding configuration automatically to a file which can be loaded by NSO on its initial startup or 'load merged' into the CDB at a later time.
Example:
$ ncs-netsim create-network ./packages/cisco-iosxr 2 asr
DEVICE asr0 CREATED
DEVICE asr1 CREATED
$ ncs-netsim add-to-network ./packages/juniper-junos 2 mx
DEVICE mx0 CREATED
DEVICE mx1 CREATED
$ ncs-netsim start
DEVICE asr0 OK STARTED
DEVICE asr1 OK STARTED
DEVICE mx0 OK STARTED
DEVICE mx1 OK STARTED
## Add netsim devices to NCS startup config in ncs-cdb/netsim_devices_init.xml
$ ncs-setup --netsim-dir ./netsim --dest .
$ ls ncs-cdb
netsim_devices_init.xml
This xml file will be read at NSO initialization when it is started for the first time to provide the initial on-boarding config for the netsim devices.
Or, if NSO had previously been run prior to netsim network creation, simply 'load merge' the netsim_devices_init.xml file from NSO cli config mode to pull in the initial netsim device initial configurations:
% load merge ncs-cdb/netsim_devices_init.xml
-Larry
