Question:
I have devices inventoried and licensed but many of the servers are showing in the Isolated Stack? Why don’t we see any connections?
Answer:
There are 2 common reasons devices can be categorized as ‘Isolated Devices:’
- Once licensed, the platform will begin to monitor netstat connections on devices. The data is then uploaded to our NOC servers (or the FDP server for Flex Deploy Engagements.) The uploads occur on demand periodically throughout the day depending on the amount of data recorded. It can take up to 24 hours in some cases for the data to be aggregated in the portal. Users will license the devices and immediately select ‘Build Application Stacks’ in the portal. As the platform has not uploaded and aggregated the data the devices are placed in ‘Isolated’ because no traffic records are seen. User is recommended to wait 2-3 days prior to running Build App Stacks. User can rerun build app stacks at a later time to verify if the platform has TCP connections.
- Devices in this group have had connectivity collected (there is an existing connectivity record where the specific device is either the source or destination of the connection), but none of the collected connections or processes would cause the specific server to join into an AutoApp or RSG Group. When a device with connectivity is being placed in the Isolated Devices stack, there are three reasons why this might happen without it being indicative of a problem:
A.) The device's connectivity is only non-critical.
B.) The device has critical connectivity only to other devices that are already in saved/confirmed stacks (we do not automatically add devices to already confirmed/saved stacks, so you can have a situation where a device gets locked out)
C.) The device has critical connectivity only to devices which are being placed into RSGs.
