02-20-2019 07:18 AM
Hello,
I'm attempting to follow the first NSO tutorials from the Dev download, however each time I try to run the network for example 1 I get an error as per the below and the devices do not start
I have installed java and ant and via homebrew and Xcode too. not having much luck searching online. does anyone know what th issues may be?
Thanks
AW-MacBook-Pro:ncs-test alex$ ncs-netsim list
ncs-netsim list for /Users/alex/ncs-test/netsim
name=c0 netconf=12022 snmp=11022 ipc=5010 cli=10022 dir=/Users/alex/ncs-test/netsim/c/c0
name=c1 netconf=12023 snmp=11023 ipc=5011 cli=10023 dir=/Users/alex/ncs-test/netsim/c/c1
name=c2 netconf=12024 snmp=11024 ipc=5012 cli=10024 dir=/Users/alex/ncs-test/netsim/c/c2
AW-MacBook-Pro:ncs-test alex$ ncs-netsim start
./env.sh: line 12: export: `Fusion.app/Contents/Public:/Applications/Wireshark.app/Contents/MacOS': not a valid identifier
DEVICE c0 OK STARTED
./env.sh: line 12: export: `Fusion.app/Contents/Public:/Applications/Wireshark.app/Contents/MacOS': not a valid identifier
DEVICE c1 OK STARTED
./env.sh: line 12: export: `Fusion.app/Contents/Public:/Applications/Wireshark.app/Contents/MacOS': not a valid identifier
DEVICE c2 OK STARTED
AW-MacBook-Pro:ncs-test alex$ ncs_cli -C -u admin
admin connected from 127.0.0.1 using console on AW-MacBook-Pro
admin@ncs# show devices list
NAME ADDRESS DESCRIPTION NED ID ADMIN STATE
-----------------------------------------------
admin@ncs#
Solved! Go to Solution.
02-20-2019 02:31 PM
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:
02-20-2019 08:27 AM
It doesn't look like it is causing any real problems in this case.
However, it seems to be something that misbehaves in the interaction between your environment and env.sh in the netsim directory. You can try doing env | grep Wireshark to figure out which environment variable it is and what is wrong with it.
02-20-2019 09:03 AM
Hi,
For more context, you can google "export + not a valid identifier" for more context. There are similar errors, but not exact to the one you have.
It seems you may modify the export variable to an acceptable format.
https://unix.stackexchange.com/questions/79658/not-a-valid-identifier-when-i-do-export-path
02-20-2019 02:31 PM
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:
05-02-2019 07:52 AM - edited 05-02-2019 07:56 AM
I've seen this error off an on in my NSO travels as well, and have generally ignored it - although it finally reached "annoying enough" stage that I took a deeper look. The issue here is that VMWare Fusion (with space) is trying to be added to a path statement.
The following link helped me rid myself of this error.
TL;DR
Create a link without spaces to the path VMWare Fusion App
ln -sf /Applications/VmwareFusion.app "/Applications/Vmware Fusion.app"
Then modify /etc/paths.d/com.vmware.fusion.public pointing to the linked version of the app. (remove the space)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide