This video is a walkthrough of using the Cisco CNC tools to create a TSN flow for deterministic communication between two devices.
Before watching this video, please complete the following steps to set up the CNC Virtual Machine, and the Cisco IE 400 Switch:
*If you can't view the video in a browser, you can download a standalone mp4 here.
I'm having an issue where the CNC will get stuck on the "Discovering Network" phase. I believe it discovers the IE4000, but is not seeing the cRIO 9035's. All devices are on the same subnet, and I can ping to the IE4000, and both cRIOs from the CNC. Are there any troubleshooting tips anyone could suggest that I try?
It could be that the CNC Web UI has the problem and your system is ok. I believe the CNC Web UI will put down 'icon' of the switch even if was not discovered.
Little technical background that might help you with debugging.
The discovery part of devices happens over an LLDP (link layer discovery protocol). If you running the latest IE4000 tsn firmware then LLDP is already present on your switch. When you install the 'TSN Features' package, it will also install LLDP on a cRIO. You dont need to do anything else after that just, connect cRIOs to the switch.
First I would advise to console into your switch and see if the switch sees cRIOs. use commaind: 'show lldp neighbors' or neighbor I dont remember exactly. That should display list of cRIOs connected to the switch. If you dont see the list then:
1. you either dont have lldp installed on cRIOs
2. Make sure you are using port1(eth0) of the cRIO to connect the switch
If you see the list over console but not in Cisco WebUI then UI is not able to talk to switch properly (I believe Cisco uses telnet to do that)
Let us know what you find out
I checked and it appears like both the CNC, IE4000, and both cRIOs are visible via LDDP from both the CLI and web gui (see photos). Also, I updated the license on the CNC to 2018 version, as well as changing the port the CNC is connected to the IE4000 via to an access/management port (on the same subnet).
The CNC is still stuck on "discovering network", although if I cancel it prematurely, it has found the "volt1" switch (under devices), and is connected/pingable.
Thanks for the screen shots. It looks like there is an issue between Cisco CNC Web UI and the switch. I'm not an expert on Cisco tools but from my experience using the tools I would start with following:
It is important that the the name and address matches your IE4000 switch. Name is case sensitive! In my case switch is called volt1 and its static IP is 10.1.1.2, my VM is set to static IP 10.1.1.1.
As the Cisco's WebGui is not mature enough at the moment. I would suggest the following go throughs:
All the best
Did Miro_T's latest suggestions help, or are you still seeing troubles with the "discovering network" portion?
Also, as an additional question, is this switch connected to a larger, corporate network, or is it just an isolated network of the switch, cRIOs, and your CNC computer/VM?
No, I haven't managed to get it to work yet. My next course of action is probably to factory reset the switch and re-follow the setup instructions step by step. One other thing I might try is changing my subnet from what I have been using (10.0.50.x/24) to the default CNC subnet. I don't imagine this is the issue though as everything is ping-able.
Currently my setup is on isolated local network. It included the CNC VM running on Virtualbox on my workstation, connected to the switch via a USB to Ethernet adapter, which is connected to the two 9035(sync) cRIOs. Also there is no router on this network, everything is on the same subnet. Everything seems to be able to see each other, but the CNC discovery doesn't work. It does pick of the switch if I end the discovery manually, and is connected, but does not find the cRIOs.
From your post above:
" Virtualbox on my workstation, connected to the switch via a USB to Ethernet adapter," .
I believe the CNC install script sets your Ubuntu eth0 to a static IP and then the CNC expects eth0 of your VM/CNC to be connected to the switch.
If you plug in a usb ethenet adapter, Ubuntu OS will most likely enumerate that to eth1 or some other port.
Can you double-check that ?