Claim a Meraki Device by Serial or Order

Claiming new Cisco Meraki devices is a fundamental first step in their deployment and management. This process registers hardware with your Meraki…

Claiming new Cisco Meraki devices is a fundamental first step in their deployment and management. This process registers hardware with your Meraki organization, making it available for assignment to a specific network. Understanding the different methods of claiming and their implications is crucial for efficient Meraki infrastructure scaling, from single-site deployments to large, multi-site enterprise environments.

Understanding the Meraki Inventory

The Meraki Dashboard maintains a central inventory for each organization. All devices, regardless of type (MR access points, MS switches, MX security appliances, MV cameras, MG gateways), must be present in this inventory before they can be assigned to a network and begin configuration synchronization. Devices typically ship with a unique serial number and often come associated with a Meraki order number. Both can be used for claiming.

To access your organization's inventory, navigate in the Meraki Dashboard to Organization > Inventory. Here, you'll see a list of all claimed devices, their types, serial numbers, MAC addresses, and their current network assignment status.

Claiming Devices by Serial Number

The most common method for adding individual devices or small batches is by their serial number. Each Meraki device has a unique serial number, typically found on a label on the device itself (e.g., underside of an access point, rear of a switch or firewall) and on its packaging. Serial numbers usually follow a 12-character alphanumeric format (e.g., Qxxx-xxxx-xxxx).

Steps:

  1. Log into the Meraki Dashboard.
  2. Navigate to Organization > Inventory.
  3. Click the Claim button (often located at the top right of the inventory table).
  4. Select the "Claim devices by serial number or order number" option.
  5. In the text box, enter each serial number on a new line. For example: 
    Q2XX-ABCD-EFGH
Q2XX-IJKL-MNOP
Q2XX-QRST-UVWX
  6. Click Claim.

Upon successful claiming, the devices will appear in your organization's inventory as "Unassigned." If a serial number is invalid or already claimed in another organization, the Dashboard will provide an error message.

Best Practice: For larger deployments, or when unboxing devices, it's advisable to scan or manually record serial numbers into a spreadsheet. This allows for bulk claiming and easier tracking against physical assets.

Claiming Devices by Order Number

For larger deployments, especially when ordering many devices directly from Meraki or a distributor, claiming by order number is significantly more efficient. A single Meraki order number can encompass dozens or hundreds of devices across various product lines.

Steps:

  1. Log into the Meraki Dashboard.
  2. Navigate to Organization > Inventory.
  3. Click the Claim button.
  4. Select the "Claim devices by serial number or order number" option.
  5. In the text box, enter the Meraki order number. This is typically a numeric string, e.g., 12345678.
  6. Click Claim.

The Dashboard will then process the order number and add all associated devices to your inventory. This can take a few moments for very large orders. Once complete, all devices from that order will appear as "Unassigned" in your inventory.

Verification: After claiming by order number, it's good practice to cross-reference the number of claimed devices in the Dashboard against your purchase order or packing slip to ensure all expected hardware has been added.

Assigning Devices to Networks

Once devices are claimed into the organization's inventory, they are ready to be assigned to a specific network. A Meraki network defines the configuration, policies, and management scope for a group of devices, typically corresponding to a physical site or a logical service boundary.

Steps:

  1. From Organization > Inventory, locate the "Unassigned" devices you wish to configure.
  2. Select the checkboxes next to the devices.
  3. Click the Add to network button (often at the top of the table).
  4. Choose an existing network from the dropdown list, or create a new one if necessary.
  5. Click Add to network again to confirm.

After assignment, the devices will show their assigned network in the inventory. When these devices are powered on and connect to the internet, they will automatically contact the Meraki cloud and download their network-specific configuration and firmware.

Firmware Updates

Upon initial contact with the Meraki cloud, devices automatically check for and apply any necessary firmware updates to match the version specified by their assigned network. This ensures consistent operation across all devices within a network and often involves a reboot. Plan for this initial update window when deploying devices.

Note: Firmware versions are managed per network under Network-wide > General > Firmware upgrades. You can set a specific firmware version or allow automatic updates to the latest stable release.

Leveraging Configuration Templates for Scalability

For organizations managing multiple sites with similar configurations (e.g., branch offices, retail stores), Meraki configuration templates are invaluable. Templates allow you to define a baseline configuration once and then apply it to multiple networks, streamlining deployment and ensuring consistency.

How Templates Work:

  1. Create a "template network" with your desired base configuration (SSIDs, VLANs, firewall rules, port settings, etc.).
  2. Convert this network into a template via Organization > Configuration templates > Create new template.
  3. When creating new networks or editing existing ones, you can bind them to this template.

When you assign devices to a network that is bound to a template, they inherit the configuration from that template. Any changes made to the template propagate automatically to all bound networks. This significantly reduces manual configuration effort for large-scale deployments.

Trade-offs: While powerful, templates can complicate site-specific customizations. Meraki offers "network-specific overrides" for certain settings, but extensive deviations might warrant separate networks not bound to a template or the use of multiple templates for different site profiles.

Common Pitfalls and Troubleshooting

  • Device Already Claimed: If you try to claim a serial number that's already in another organization's inventory, you'll receive an error. You'll need to contact Meraki Support to transfer the device to your organization, providing proof of ownership (e.g., purchase order).
  • Invalid Serial/Order Number: Double-check for typos. Meraki serial numbers are case-sensitive and adhere to a specific format.
  • Delayed Appearance: After claiming a large order number, it can take a few minutes for all devices to populate the inventory. Refresh the page or wait patiently.
  • Firmware Update Loop: If a device fails to update firmware and keeps rebooting, ensure it has stable internet connectivity and can reach Meraki's cloud servers (dashboard.meraki.com and associated IP ranges/ports like TCP 7335, 7735, 9920, 9922, 9993, 10000, 10001, 10002, 10003, 10004 for device communication, depending on device type and firmware version). Firewall rules or proxy settings might be blocking necessary traffic.
  • Incorrect Network Assignment: Always verify that devices are assigned to the correct network after claiming. An MR AP assigned to an MX network will not function correctly, for example.
  • Licensing Issues: Ensure your organization has sufficient active licenses for the newly claimed devices. Meraki devices require active licenses to operate. If licenses are expired or insufficient, devices will not be able to connect to the Dashboard and download configurations. Check Organization > License info.

Back to the knowledge base · Ask the AI assistant