Summary

  • Meraki’s historical Example C adds two one-year switch licences and moves the common expiry from 16 April to 14 March 2017, bringing it forward by 33 days.
  • Co-Term calculates a shared date from licensed quantities, terms and licence-type weights. Removing hardware, adding licences and renewing the organisation affect different parts of that arrangement.

Buy two more licences. Come back a month earlier. Meraki supplies this rather unhelpful pairing in its own explanation of Co-Term licensing. Extra coverage can bring the existing organisation’s next renewal closer, because the new licences join a shared expiry calculation.

The manufacturer’s Example C sets the transaction on 31 March 2015. The organisation has 747 days left. It adds two MS42P switches with one-year licences. The published result leaves 714 days, changing the expiry from 16 April 2017 to 14 March 2017.

This historical teaching example removes 33 days from the previous timetable. Its trick is quite ordinary averaging: the purchased term, 365 days, is shorter than the term remaining in the existing pool. Bring those periods under a common end date and the shorter addition can pull that date towards the present.

The purchase covers more equipment. It also changes when the whole pool returns to the renewal desk. A procurement system counting units and invoice value can easily record the first effect while leaving the second to surprise somebody else.

A new licence joins an old calendar

Meraki’s Co-Termination overview assigns one shared expiry to the licences in a Meraki organisation. Organisation here means the administrative grouping within the service. Existing and newly added licences enter its weighted calculation together.

Licence type supplies a weight as well as quantity and time. The detailed explanation uses the applicable licence’s one-year list price, called its Base Price. This is the weighting input in the time calculation. The amount a buyer negotiated on an invoice belongs to a different set of accounts.

For additional devices, the incremental time starts with the newly purchased term minus the organisation’s remaining term. A shorter new term gives a negative increment. Spreading that weighted contribution across the full licence pool can bring the common expiry forward. The historical example demonstrates the direction without turning its old teaching prices into a current quotation.

The mental picture that causes trouble is a separate little timer attached to each new box. Co-Term gives the organisation a common clock. A branch can buy exactly the coverage it wanted and still change the date faced by branches that ordered nothing.

Retiring a box does not refund its time

The distinction becomes just as important when a network shrinks. Meraki says the expiry calculation follows licence limits rather than the current device count. Removing devices from a network or organisation leaves the expiry unchanged.

Current Device Count measures devices added to the organisation’s networks. Devices held only in inventory are outside that count. Licence Limit reflects the relevant active licences and the capacity they provide. Taking devices out of networks can correct an excess over that capacity. The common date continues to follow the licensed pool.

Those records answer different operational questions. The retirement list says which hardware has left service. The licensing record says what capacity and time remain under the applied licences. Moving a switch into storage does not turn the unused portion of its former working life into extra days for everybody else.

Leaving a new key unclaimed offers no automatic pause either. The overview says licence time starts when the licence is processed; waiting to add it in Dashboard does not delay the start. The installation project can wait for an electrician. Its purchased time has its own appointment book.

Renewal can lengthen time and cut capacity

Adding devices and renewing the organisation are different operations. The detailed FAQ uses the full newly purchased term for a renewal alone, whereas an addition of devices accounts for the existing remaining term in its incremental contribution. The selected operation matters alongside the term printed on the order.

“Renew my Dashboard license” also sets the licensed device quantities to match the new key. Meraki illustrates the consequence with five access points and a three-year renewal covering two. The remaining time is retained. If all five access points stay in use, three exceed the new limit.

A buyer can therefore obtain a long renewal while buying less capacity than the network still uses. That can fit a planned reduction to two access points. It requires the other three to leave the networks on a schedule consistent with the smaller key. The word renewal does not carry the old quantity into the new entitlement by itself.

For Co-Term, the overview describes a 30-day grace period for exceeding licence limits or reaching expiry. An uncorrected licensing state then leads to organisation shutdown, with documented consequences including loss of management and traffic passage. Excess devices can be removed from networks or covered by additional licensing. Expired coverage needs fresh time for the active fleet.

The current general licensing FAQ offers Co-Term and Subscription, with legacy PDL restricted to existing users. One organisation uses one model. Establishing which model governs the organisation is the first step in reading its calendar correctly.

An exact forecast for a real organisation needs its remaining term, licence limits by type, applicable weights, proposed key quantities and terms, and intended operation. Those inputs would determine its actual new date. Meraki’s published example already establishes what an approval should ask to see: the additional coverage and the resulting common expiry, on the same page.