Every license activate failure on a Huawei S-series campus switch resolves to one of six exact error messages. What each one actually means, how the license file itself is structured internally, and a real case where a stacking ESN mismatch quietly ran out a 60-day trial and dropped a VXLAN tunnel network-wide.
By the AtlasCommTech engineering team — 13 years of carrier & enterprise network deployments · Updated July 2026
A failed license activate isn't a mystery — the device tells you, verbatim, which of six exact things went wrong.
license activate on a Huawei S-series campus switch (S1720, S5700, S6700, S6730, S7700 and the rest of the family) only ever fails one of a small number of ways, and the CLI prints the exact reason rather than a generic error. Learn the six messages once and you stop guessing at what to check next.
What follows: the six messages classified by what's actually broken, the internal structure of the license file itself — which explains why a “format invalid” error happens even when the ESN looks right — and a real case where a license silently sat in Trial state for 60 days before a VXLAN tunnel dropped across the whole business.
Sorting the six messages by what's actually wrong tells you where to look first — the wrong file, a rejected file, or a file that doesn't match this device or this moment in time.
Diagram labels are kept in English for engineering clarity.
All six messages, word for word, come from the same license-activation fault table in Huawei's S-series campus switch maintenance manual.
Same six errors as the diagram above — here's the exact CLI text, what's really going on, and the fix for each.
| Error Message | Group | What It Means |
|---|---|---|
| The filename is invalid, and the postfix of the file name must be 'dat'. | Group A | The file activate was pointed at isn't a .dat license file. |
| The specified file does not exist or is illegal. | Group A | No file by that exact name exists on the device's storage. |
| License file validation failed. | Group B | The file's digital signature doesn't check out — often a corrupted transfer. |
| No product features present in LK. | Group B | The license's controlled items don't match this product at all. |
| License File expired. | Group C | The license's own validity window has already passed. |
| License File with ESN or Version mismatch cannot be activated repetitively. | Group C | An ESN/version-mismatched license was already activated once and is being retried. |
SYMPTOMlicense activate <filename> returns Error: The filename is invalid, and the postfix of the file name must be 'dat'.
CAUSEThe file being pointed at doesn't carry a .dat extension — either the wrong file was selected, or the extension was changed or stripped somewhere during transfer.
FIXRun dir on the device first to confirm the exact filename and extension, then activate that file — don't retype a filename from memory.
<Quidway> license active lics7700v200r0XX_XXX.dat
Error: Verify license failed.
Error: License file format invalidSYMPTOMError: The specified file does not exist or is illegal.
CAUSEThe filename typed at activation doesn't match anything actually stored on the device, or it contains characters the CLI treats as illegal.
FIXRun dir to list what's actually on the storage device, then copy the filename character for character — case included — rather than retyping it.
SYMPTOMInfo: License file validation failed — and separately, an ESN that visibly matches the device still gets rejected as a mismatch.
CAUSEThe source documentation traces this exact symptom to packet loss during upload — a partial or corrupted transfer leaves a license file on the device that's incomplete, so its signature no longer validates even though the visible ESN field still reads correctly.
FIXCompare the uploaded file's size against the size of the file you were issued using dir; if they differ, switch the FTP client to binary transfer mode before re-uploading, then reactivate.
ftp client> binary
ftp client> put lics7700v200r0XX_XXX.dat
<SW> dir
// compare file size against the originally issued license fileSYMPTOMNo product features present in LK (the same underlying mismatch also surfaces as “No product features present in license file” in related FAQ entries).
CAUSEThe license's controlled items were generated against a different device model or product family than the one it's being activated on — the ESN can be entirely correct and the license still won't apply.
FIXReapply for a new license quoting the exact device model, not just the ESN, and confirm the product field in the reissued file before uploading it again.
SYMPTOMInfo: License File expired, on a file that's never been activated before.
CAUSEThe license's own validity window has already closed by the time someone gets around to activating it — common when a license sits in an inbox for a while after being issued, or a demo license's fixed window runs out before deployment.
FIXReapply for, or repurchase, a fresh commercial license against the device's current ESN and activate it right away rather than stockpiling issued-but-unused license files.
SYMPTOMInfo: License File with ESN or Version mismatch cannot be activated repetitively.
CAUSEA license whose ESN or software version already didn't match this device was activated once before — which drops it into Trial state — and the same file is now being activated again. The device refuses the repeat rather than silently resetting the trial clock.
FIXDon't re-run the same activation expecting a different result — reapply for a license that genuinely matches the current ESN and software version, then activate that file instead.
All six error messages and their causes are cross-checked directly against Huawei's S-series campus switch license fault-handling table.
A license file isn't just an ESN and an expiry date — it's a signed header plus one signed block per feature, and the signature covers the whole thing.
The most basic of the six failures doesn't even make it into the classification above, because it happens before the device gets a chance to check ESN, expiry or product match: the file itself is malformed. license activate rejects it immediately with a two-line error, and the cause is almost always one of three things — a mistake made when the license was originally applied for, corruption during transfer, or someone manually editing a file that was never meant to be touched.
<Quidway> license active lics7700v200r0XX_XXX.dat
Error: Verify license failed.
Error: License file format invalidA genuine license file is plain text, structured as a signed header followed by one signed block per controlled feature. The fields that matter for troubleshooting:
| Field | What It Holds |
|---|---|
| LicenseSerialNo / Sign | The file's serial number and the digital signature computed over the surrounding content — this is what “format invalid” or “validation failed” is actually checking. |
| Product / Feature | The device model this block applies to, and which controlled feature or resource it grants — this is what a “No product features present” mismatch is checking. |
| Esn | The device serial number this block is tied to — compared directly against display esn on activation. |
| Attrib | Three values: commercial vs. demo, the expiry date (or PERMANENT), and — fixed at 60 — the number of trial days a mismatched or demo license runs before its controlled features fail. |
| Function / Comment | The specific controlled items granted (and any resource counts, such as AP capacity) plus an internal order-reference comment. |
Because Sign is computed over the surrounding visible fields, any manual edit to a license file — even one that looks harmless, like tidying whitespace — breaks the signature and produces exactly the format-invalid error above. The source guidance is blunt about this: never modify a license file's visible content, and before activating, confirm the uploaded file's size matches the size of the file you were originally issued.
The license output looked fine for two months — until the trial clock it had quietly been running on ran out, and a VXLAN tunnel across the whole business went down with it.
A customer reported that a VXLAN tunnel had suddenly gone down. Checking the switch showed its license had failed — and the customer confirmed the license had been installed on that device for exactly 60 days.
Board fails. (Index=67108873, EntityPhysicalIndex=67108873,
PhysicalName="MPU Board 0", EntityTrapEntType=1, EntityTrapFaultID=132322,
EntityTrapReasonDescr="the ESN of card does not match the license file")
<SW> display license
Info: No license is activated.
<SW> display esn
ESN of slot 0: 1022B5088417
ESN of slot 1: 1022B5088418
<SW> more licensexxx.dat
ESN:1022B5088418
// the license's ESN matches slot 1 (standby) -- not slot 0 (the master this switch is checking against)Day zero: the stacking system was installed with a license that only carried the standby unit's (slot 1) ESN. Because slot 0 (the master) never matched, the license dropped into Trial status immediately — and per the source guidance, once a license is in Trial, its 60-day countdown starts right then, not at some later warning point. Day sixty: the trial window closed, the license-controlled features failed immediately, exactly as the FAQ describes it — and because VXLAN was one of the features under that license, the tunnel dropped with no further warning.
Huawei's stacking license mechanism has an extra failure mode on top of a plain single-device ESN mismatch. On versions before V200R009, a single license has to carry both stack members' ESNs — a license with only one ESN goes Trial the moment there's a failover, even if it looked fine before. From V200R009 onward, each member can carry its own separate license file instead, but only if both files' controlled items are identical: if the master and standby licenses grant different feature sets, the standby silently starts syncing the master's license file, and if that synced file doesn't include the standby's own ESN, the standby's license state flips to Trial too — carrying the same 60-day clock into the next failover.
Pulled straight from the field — the ones worth having an answer ready for.
Per the source documentation, this is usually a transfer problem, not a real mismatch: packet loss during upload can leave an incomplete license file on the device. Compare the uploaded file's size against the originally issued file's size with dir; if they differ, switch the FTP client to binary mode before re-uploading and reactivate.
Almost never. The large majority of license activations take effect immediately with no reboot required. A small number need a follow-up command and a reboot before they apply — a 40GE-to-100GE port-speed license is the documented example, which needs assign port-speed 100GE run and the device rebooted afterward. If a license's own documentation doesn't mention a reboot requirement, it doesn't need one.
Per the source guidance, the license-controlled features fail immediately the moment the trial window closes — there's no grace period and no separate warning event beyond whatever alarms the underlying feature itself generates. The fix is to reapply and reactivate before the Expired date shown in display license, not after.
A device's ESN is tied to its main control board. Swapping the board changes the device's effective ESN, and if that no longer matches the installed license's ESN, the license drops to Trial automatically — the same mechanism that shows up in a stacking failover, just triggered by a hardware swap instead.
No — for better compatibility, a license file continues working across a software upgrade or downgrade without any action needed. Aligning the license's recorded product version with the new software version is optional, and only useful if you're planning future capacity changes or service requests against that license.
This note is built around the license-activation fault table and field cases in Huawei's S-series campus switch maintenance manual — S1720, S5700, S6700, S6730, S7700 and related models. It doesn't cover AR router or firewall licensing, which use a different activation tool and portal, and it doesn't go deep on the license-mode differences under cloud-managed NCE-Campus deployment, which follows its own separate table.
Send us the exact error text, the device model and ESN, and how the license file was transferred — we'll help you work out which of the six causes it actually is.