Best Practice Guide for clients to follow deploying DNA Spaces

Owned by Constandino Stylianou
Last updated: 06 Dec, 2022 by Roselle B Dela Fuente (Unlicensed)
1 min read

Before a partner Tenant id is even sent to MazeMap, we need to be clear to our clients that they have configured DNAS in accordance with Cisco’s best practice guidance listed below in order to reduce any issues with wayfinding or other features such as FMF.


For All Mazemap Use Cases

  • DNA Spaces deployed with DNA Spaces connector architecture

    • Deploy latest connector version

  • Accurate and up to date maps with APs placed

    • Check Prime or DNAC Compatibility with DNAS

      Follow AP deployment for location best practises

      Follow Map deployment guide to ensure Inclusion/exclusion zones marked correctly

      GPS Markers placed accurately; This can be verified in DNA Spaces dashboard with green markers

  • Blue dot Navigation and Find-My-Friends work with Cisco Spaces Extend and Act licenses

  • Asset Locator (Asset Tracking) works only on Cisco Spaces Act license.

  • Refresh rates recommend fast locate

 

For MazeMap's wayfinding use case:

  • Customers can use username hashing if they like. But they need to make sure they do not check 'hide the IP' in the connector. Mazemap requires the IP address to go to the cloud.

  • Customers need to make sure they are not re-using the same IPs for devices.

    • For example, they may try to test in labs in multiple places where different device may get same IP. Generally, this is not a concern in production deployments, but should be made clear that they understand it.

 

For MazeMap's other features like find my friend,

  • they need to make sure to not hash the data on the connector since MazeMap also uses the username field for that.