First would be to make sure you have the right scope selected when looking at the flow search. If you don’t have the right scope, the expected data will not show up.
Next, check the Inventory page. There, filter out for the IP address of the sensor host (again, check the scope you are in) and see when the last check-in is for the sensor. You should see something the last check-in time within the last hour. If it has not checked in, then you will need to check from the server where the server is installed.
From the sensor, if this is linux server, check that the directory /usr/local/tet/ exists. If the directory is not there, make sure that the sensor was installed and that there was no issue when installing the rpm. rpm -qa | grep tet should show you what is installed if it is.
If the directory is there, check the sensor_id file in that location. If you see some content that begins with “uuid”, this means that after the rpm was deployed, it was not able to communicate back to the cluster. Run the fetch_sensor_id.sh file and then check the fetch_sensor_id.log file in /usr/local/tet/log and see what issues occurred in getting the sensor ID. This should help narrow down what is going on.
Here are some commonly asked questions and answers to help with your adoption of Cisco ACI solution. Subscribe to this post to stay up-to-date with the latest Q&A and recommended Ask the Experts (ATXs) sessions to attend.