Physical Server Discovery

CloudBolt has the ability to scan networks to find physical servers and create server records for them so they can be managed and reported on from CloudBolt. These servers would not be detected via CloudBolt’s traditional mechanism of querying virtualization systems and public cloud providers for VM inventories, so scanning the network is necessary to find these servers.

To begin a scan, go to Admin > Rules and look for the rule called “Scan Network for Physical Servers”. This rule can be run from the UI even though automatic, recurring execution is disabled . Executing this rule will identify any IPs within the specified range that have a device listening, but are not already tracked in CloudBolt, and create server records for them. After that, they can be seen and managed in CloudBolt, and will be included in reports.

Optional Extended Discovery

If provided with a potential password for discovered servers, CloudBolt will attempt to authenticate using that password (and either a default username of Administrator/root or the specified username). If the credentials work, CloudBolt will store them on the new server record, then run any CB Plugins whose name starts with “Discover <OS Family>” for the OS Family of the server, and each ancestor of that OS Family. Thus, if this feature discovers an ESXi server, it will run any plugins whose name starts with “Discover ESXi”, then any plugins that start with “Discover Linux”. For an example, go to All Actions and look for an action called “Discover Windows Info”.