How do I manage or unmanage cloud controllers?

Once you’ve entered the credentials for your cloud controller, you can configure which sites and networks you want to manage with Auvik. This will provide Auvik with extra information about devices discovered by the collector. Currently, Auvik only supports the Juniper Mist, Meraki and Datto cloud controllers.

Depending on where you added the cloud controller (your MSP dashboard, or your client dashboard), you’ll need to specify which cloud network is to be managed.

• From your MSP dashboard, specify which of your clients have which cloud network.
• From your client dashboard, decide which cloud network you want managed.

If you need to, you can first filter your network list to show only certain networks. For more information on filtering, see How to filter data in Auvik.

Once the networks have been mapped, you can move onto viewing controller details.

• Manage clients
• Unmanage clients
• MSP KPIs
• Manage networks
• Unmanage networks
• Client KPIs

How to manage a network client

1. From your MSP dashboard, click Discovery in the side navigation bar.
2. Click the Manage Credentials tab.
3. Click the API Credentials tab.
4. In the displayed list of credentials, click the row for the credential.
5. In the displayed list of cloud networks, find the network device that corresponds to the client in Auvik. Check the box at the beginning of its row.
6. Click the Edit button.
7. Select the Auvik client(s) that maps to the network.
8. Click Save.

How to unmanage a network client

1. From your MSP dashboard, click Discovery in the side navigation bar.
2. Click the Manage Credentials tab.
3. Click the API Credentials tab.
4. In the displayed list of credentials, click the row for the credential.
5. In the displayed list of cloud networks, find the cloud network(s) you want to unmanage. Check the box at the beginning of each row.
6. Click the Unmanage button.
7. Confirm the networks should no longer be managed by clicking Unmanage.

Once you’ve marked a network as unmanaged, you’ll no longer be able to view details for that networked device.

MSP KPIs (key performance identifiers)

• Mapped Networks indicates how many cloud networks are being managed by Auvik.
• Unmapped Networks indicates how many cloud networks are not being managed by Auvik.
• Unmapped Auvik clients indicates how many Auvik clients are not mapped to a cloud network. To see all Auvik clients that haven’t been mapped, click the KPI.

Hovering over a color in the bar above the KPIs shows the number of clients per managed state.

How to manage a network

1. From your clients dashboard, click Discovery in the side navigation bar.
2. Click the Manage Credentials tab.
3. Click the API Credentials tab.
4. In the displayed list of credentials, click the row for the credential.
5. In the displayed list of cloud networks, find the cloud network(s) you want to manage. Check the box at the beginning of each row.
6. Click the Manage button.

How to unmanage a network client

1. From your clients dashboard, click Discovery in the side navigation bar.
2. Click the Manage Credentials tab.
3. Click the API Credentials tab.
4. In the displayed list of credentials, click the row for the credential.
5. In the displayed list of cloud networks, find the cloud network(s) you want to unmanage. Check the box at the beginning of each row.
6. Click the Unmanage button.
7. Confirm the networks should no longer be managed by clicking Unmanage.

Once you’ve marked a network as unmanaged, you’ll no longer be able to view details for that networked device.

Client KPIs (key performance identifiers)

• Mapped Networks indicates how many cloud networks are being managed by Auvik.
• Unmapped Networks indicates how many cloud networks are not being managed by Auvik.

Hovering over a color in the bar above the KPIs shows the number of clients per managed state.

A newly added cloud network is not appearing in Auvik

When a new network is added to the vendor’s cloud controller, it may not appear immediately in Auvik. Allow a few minutes for the vendor API and Auvik to update.

Confirm the network in the vendor portal

Confirm that:

• The network exists in the vendor’s cloud controller.
• The network is active and not archived, disabled, or pending.
• The API credentials configured in Auvik have permission to read the organization and network.
• The network belongs to an organization included in the Auvik cloud controller integration.

If the network does not appear in the vendor portal or is not available to the API credentials, update the network or permissions in the vendor system before troubleshooting Auvik.

Refresh the cloud controller information

1. Go to Discovery > Manage Credentials.
2. Open the API Credentials tab.
3. Select the applicable cloud controller credential.
4. Review the available network list.
5. If the new network is displayed, select it and map it to the appropriate Auvik client or site.
6. Save the changes.

If the network list does not update, reopen the cloud controller credential and use Save, Validate, or Refresh, if that option is available in your environment.

Allow several minutes after saving for the network and associated devices to appear in Auvik.

If the network still does not appear

Check the following:

• The API credential has read access to the correct organization.
• The correct organization or tenant is selected in the cloud controller configuration.
• The API credential has not expired, been revoked, or exceeded its permissions.
• The vendor API is not returning an authorization or rate-limit error.
• The collector or integration has the required outbound HTTPS access.

If the vendor API returns the network successfully but Auvik still does not display it, contact Auvik Support and provide:

• The Auvik site or tenant name.
• The cloud controller or integration name.
• The vendor organization and network name.
• The time the network was added.
• Any integration error or status message.
• Confirmation that the network is visible in the vendor portal.

Related articles

• How do I approve, add, edit, or delete networks to be scanned?