Straight from Huawei's official AR Router Acceptance Test Guide — the six-stage path every delivered network takes from the loading dock to a signed completion certificate, what gets tested at each stage, how a pass is judged, and the paperwork that proves it happened.
By the AtlasCommTech engineering team — 13 years of carrier & enterprise network deployments · Updated July 2026
A delivered network doesn't pass one inspection — it moves through four to six separate acceptance checkpoints, each with its own pass criteria and its own signature, before the contract can close.
Huawei's AR Router Acceptance Test Guide defines acceptance as the contractual milestone that confirms a customer received equipment meeting the specifications they were promised — a joint activity between the customer and the installation and commissioning team, run against ITU-T recommendations, IETF standards, national standards and the equipment vendor's own criteria. Acceptance runs through the whole delivery lifecycle, from the customer's original requirement at bid stage through contract negotiation and project delivery to contract closure, and it is one of the key milestones that triggers payment.
The guide breaks that single word — “acceptance” — into four checkpoints: factory acceptance, delivery check, installation acceptance and preliminary acceptance — followed by a trial run and a separate final acceptance once that trial period closes. Running every project through the same sequence, end to end, is also how we deliver at AtlasCommTech — see the full production-to-handover process on our Factory page — and here is each checkpoint in order: what actually gets tested, how a pass is judged, and the document each stage leaves behind.
Each stage has its own pass criteria and its own paper trail — skipping the sign-off is what turns a routine stage into a dispute six months later.
Diagram labels are kept in English for engineering clarity.
The guide is explicit that these four checkpoints happen before a device is judged commercially usable, with the trial run and final acceptance closing out the contract afterward.
Before any functional test runs, the installed hardware itself has to pass six checks — this is the sign-off table the guide ties to a completed installation.
| Item | Standard & Requirements |
|---|---|
| Cabinet / enclosure | Installed in the correct position, mounted securely, arranged neatly, labeling complete, fastenings tight, exterior finish intact. |
| Peripheral terminals | Network management terminal installed in the correct position and fully configured; equipment cabinets arranged neatly. |
| Cable routing | Internal fiber and communication cable routing and lacing meet workmanship requirements; power cables and cables are arranged neatly. |
| Grounding | Grounding connection method meets the standard, routing and lacing meet requirements, protective-earth resistance below 1 ohm. |
| Power | No grounding faults in internal power wiring, power cable routing is neat, DC power connectors meet requirements, DC feed cable insulation resistance meets requirements. |
| Hardware check | Boards can be inserted or removed without obstruction, board retainers are secure, alarm devices meet requirements, loaded programs confirm the hardware is fault-free. |
Both parties sign this table on the spot, with the inspection date recorded — the guide refers to it as the installation acceptance sign-off table, and it is the precondition before commissioning and functional testing begin.
Preliminary acceptance is where the network's actual functions get exercised — the guide organizes these into a Basic Package, plus two optional Extended Packages for anything needing a site visit or specialized instruments.
| Test ID | What It Verifies | How a Pass Is Judged |
|---|---|---|
| T01-0101 | System hardware status | display device shows Power = PowerOn and Register = Registered for every board in position |
| T01-0201 | System clock | clock datetime sets the time, and display clock confirms it took effect |
| T02-0101 | Telnet login | An AAA-authenticated Telnet session reaches the device's user view successfully |
| T02-0102 | FTP file transfer | ftp get downloads the target file from the FTP server to the device without error |
| T02-0201 | Configuration save | save persists configuration changes through a full device restart |
| T03-0101 | Layer-2 basic service | The interface joins the configured VLAN and the router learns the peer's MAC address in the correct VLAN |
| T04-0101 | Layer-3 basic service | End-to-end routed connectivity between test PCs across the router |
<Huawei> system-view
[Huawei] sysname RouterA
[RouterA] aaa
[RouterA-aaa] local-user test password simple test@123
[RouterA-aaa] local-user test privilege level 3
[RouterA-aaa] quit
[RouterA] user-interface vty 0 4
[RouterA-ui-vty0-4] authentication-mode aaa
[RouterA-ui-vty0-4] quit
<Huawei> display device
AR2220's Device status:
Slot Sub Type Online Power Register Alarm Primary
0 - AR2220 Present PowerOn Registered Normal Master
<RouterA> clock datetime 15:00:00 2026-07-19
<RouterA> display clock
<RouterA> ftp
[ftp] open 1.1.0.1
[ftp] get sup.bin flash:/sup.bin
[ftp] bye
[RouterA] vlan 2
[RouterA] interface ethernet2/0/0
[RouterA-Ethernet2/0/0] port link-type access
[RouterA-Ethernet2/0/0] port default vlan 2
[RouterA] display vlan 2
[RouterA] display mac-address
<RouterA> saveBasic Package items are chosen so a remote acceptance — over the network, no site visit — is enough. Extended Packages A and B exist for anything that needs a site visit or an expensive instrument, and per the guide they are a separately priced service, not a default line item.
None of these are exotic edge cases — they are the same handful of mistakes the source guide explicitly calls out.
RISKThe guide splits delivery check into two stages: a case-count check against the shipping manifest, which triggers the Delivery Note, and a packing-list check that only finishes once the very last site is unboxed and signed — potentially much later. Tying full payment to the Delivery Note risks paying before delivery is actually complete.
SAFER PRACTICETreat the Delivery Note as proof the shipment count matched the manifest — nothing more. Only treat the last site's signed packing list as proof the delivery itself is closed.
RISKThe installation acceptance table isn't a formality item — it's where the guide requires protective-earth resistance under 1 ohm before commissioning even starts. A device with a marginal ground can pass every functional test at preliminary acceptance and still fail unpredictably in production.
SAFER PRACTICESign the installation table before scheduling preliminary acceptance testing, not after — the guide places it explicitly as the prerequisite stage before commissioning and functional testing begin.
RISKExtended Packages A and B target hardware indicators and instrument-heavy tests that the guide says are better controlled through the factory quality system than through a field retest — and both require paid site time and instruments.
SAFER PRACTICEFollow the guide's own selection principle: choose Basic Package items first, keep the item count as small as possible, and only add Extended Package items when the customer insists — with time and instrument cost negotiated separately.
RISKThe guide requires a preliminary acceptance application report to be submitted before testing starts, on top of installation workmanship and appearance already passing inspection — skipping straight to running test items without that precondition isn't a shortcut, it's out of sequence.
SAFER PRACTICEConfirm the application report is filed and installation acceptance is signed before booking any Basic or Extended Package test session.
RISKThe guide is explicit that a 24-hour bit-error test must run undisturbed by outside interference, human or power-related; any anomaly needs its exact time logged, or the test has to be redone from the start.
SAFER PRACTICESchedule 24-hour test items for a window with no planned maintenance elsewhere in the room, and treat any interruption as a redo, not a resume.
The guide treats the three months after preliminary acceptance as evidence, not a formality — final acceptance is where that evidence gets judged.
The most direct test of real operating quality, per the guide, is how the network actually behaves once it is carrying traffic: every hardware and software fault during the roughly three-month trial run gets logged, so the network's stability can be evaluated on real operating history rather than a point-in-time test.
Pulled straight from the field — the ones worth having an answer ready for.
No — delivery check, in two stages of case-count check and packing-list check, confirms the equipment that arrived matches what was shipped and ordered. Installation acceptance is a separate, later stage that inspects the physically installed hardware — cabinets, cabling, grounding, power, boards — before commissioning even starts.
The guide's own principle is to keep the item count as small as possible while still guaranteeing the network and business are usable — Basic Package items are the priority, chosen because they can be verified remotely with simple, inexpensive instruments.
The guide's suggested path is to first walk the customer through the vendor's quality-assurance system and existing factory test reports; if they still insist, keep the item count as small as possible and have the customer cover the added time and instrument cost.
About three months, per the guide. Every hardware and software fault during that window gets logged — that log is exactly what final acceptance reviews to judge whether the network is stable enough to close the contract.
At minimum: the Delivery Note and signed packing list from delivery check, the installation acceptance sign-off table, the preliminary acceptance item sign-off sheet, the trial-run fault log, and the final acceptance report with its completion certificate — the guide ties payment and contract-closure milestones to exactly these documents.
This checklist is built from Huawei's AR Router Acceptance Test Guide — its acceptance-flow definitions, its Basic Package test items across device management, basic configuration, and Layer-2 and Layer-3 basic service, and its installation sign-off table. It covers the acceptance sequence for AR-series router deployments specifically. Extended Package A and B item-by-item procedures, other product lines' acceptance manuals, and customer-specific contractual acceptance clauses are a different set of documents and aren't covered here.
Send us the equipment list, the site count and what the customer is asking to test — we'll help you scope a Basic Package that closes the contract without turning acceptance into a second project.