P
Placard
Fleet Naming Console
Sign in
Restricted to authorized Network / IT staff.
P
Placard
Fleet Naming Console
Monitor
Configure
OrgReal-Prod
Regionac2 · Global 03
Budget4,000/hr

Fleet overview

org_id · 8b072418…a459

— Live
Sites watched
—
across 4 shards
APs named
—
 
Renamed today
—
Errors —
—
last 24 hours

Shard map

Every site hashes to exactly one shard — no overlap, no gaps, stable across runs

Shard 0 Shard 1 Shard 2 Shard 3

Shard roster

Each shard runs independently on its own token and its own hourly budget

Shard Status Sites APs found Budget used (this hour) Last run

Recent activity

Renames, errors, and fixes across every shard

Code Site name APs named Status

Users

Admin accounts can do everything · read-only accounts can view the dashboard but can't change anything

Username Role Added Added by

Add a user

Placard — Fleet Naming Console
Fleet Summary
—
—
Loading…

Placard v1.4 · connected to api.ac2.mist.com · next sync in —

Add a shard

Step 1 of 3
Create the API token

Each shard needs its own Mist API token — rate limits are enforced per token, so adding a shard adds a fully independent budget rather than splitting the existing one.

✓
Access level: Network AdminWrite access to rename devices. Observer will pass a health check but fail every real rename.
✓
Site scope: All sitesNeeded so this shard can be correctly assigned any site in the hash split.
✓
Org-level read access: enabledRequired to list sites and sync the Esports tag.
Sent once over HTTPS to validate it against Mist directly — never written to disk or logged by this backend.
Step 2 of 3
Projected shard split

Computed live from your org's actual current site list, using the exact same hashing the naming script uses — not an estimate.

Step 3 of 3
Run this on the server

This backend does not execute deploy commands itself — copy this and run it over SSH with appropriate privileges.


        


        

          
          
        

      


    

  







  

    

      
Site

      
    

    

      

      

      
IDF is read from the connected switch's hostname (naming convention, not a native Mist field). Stack unit is parsed from the LLDP port ID — Juniper interface names follow type-fpc/pic/port, where fpc is the Virtual Chassis member ID.