Adding a flowSensor to an existing CSNA

[nastiakhon]

Hello!

We already have a working CSNA with three nodes: Manager, DataNode, and Flowcollector. They've been running for almost a year. Now we've decided to add a FlowSensor, but adding it throws an error.

All our nodes are in the same subnet, including the new one. The versions match: VE version 7.5.3 build 20250624.2140. I'm also entering the correct "admin" password.

I should add that the current nodes have a certificate from our corporate CA, and the new FlowSensor has a self-signed one.

Please help me solve this problem.

[kegunner]

Hi, I realise that you mentioned this in your message but when you reach this screen during the FTS process you are certain that you are using the correct manager details (IP and password) and not the password that was set earlier in the FTS process for the FS (which may be different to manager).  You can check by logging into the manager with the admin password. 

[nastiakhon]

Yes, I'm entering the admin password specifically from Manager. I thought maybe I was typing it incorrectly, but then I checked and manually entered the password through the Manager GUI. And now I'm sure it's the right password.
I've tried it many times today. I even tried resetting the FS, but that didn't help either. After resetting the FS and going through all the steps again, after entering the data from Manager, I see a prompt:

I agree, and then I get message saying it can't register.

[nastiakhon]

I tried downloading the certificate from flowSensor and importing it into Manager's TraustCert section. But that didn't help. Could the problem be something else? Is there a place I can check for the error preventing registration? Please help.

[kegunner]

Hi, assuming there are no issues with basic connectivity to the manager or interface configuration on the new FS, I would recommend a TAC case in this instance. 

[nastiakhon]

Yes, I understand, but unfortunately, we don’t have the opportunity to contact TAC now.

[nastiakhon]

Please tell me if it is possible to see the exact reason for the refusal somewhere.

[nastiakhon]

I found the exact cause. I dumped the traffic from the Manager during the flow sensor registration, and it's clear that the flow sensor is sending messages to the manager that it doesn't recognize the certificate authority.

However, during registration, a question about trusting the Manager certificate still appears. It turns out we need to somehow upload our corporate root certificate to the flow sensor. Can anyone please tell me if this is possible? Or at least a rough plan?

[nastiakhon · Accepted solution]

I managed to solve the problem as follows. I deployed separate test virtual machines for Manager and FlowCollector. I attached FlowCollector to Manager. I attached my FlowSensor to Manager. I added corporate certificates through the Inventory menu. I detached my FlowSensor from the test Manager and attached it to the corporate Manager I have in Production. The addition was successful.