Summary
Question
Why do added OT scan ranges not appear in the cloud tenant after a massive import?
Answer OT subnets that are imported via massive import on the local web console, are NOT synced as Discovery Actions in LS Sites.
Here is a valid work-around:
- open the CSV file
- filter on the OT sensor
- logon to LS Sites
- choose Scanning/Discovery Actions > create Discovery Action > Network Target: Create target
- copy the IP subnets (you selected in csv)
- Save the target
Repeat these steps for each OT Sensor
For further details, refer to the relevant knowledge base article: Configure Network Discovery
