A PEN convergence module's dual uplink only works as a clean master/backup pair when the two center-switch ports are configured exactly right — get the port numbering wrong and Eth-Trunk itself refuses the configuration with one of three specific error messages. This is what those errors actually mean, the interface-numbering rule behind them, and the pre-checks that avoid them before you even start typing.
By the AtlasCommTech engineering team — 13 years of carrier & enterprise network deployments · Updated July 2026
Two uplink fibers to the same PEN convergence module share an identical wavelength by design — plugging them in isn't enough, they have to be told to cooperate.
A PEN convergence module's dual-uplink design connects it to the center switch with two fibers instead of one, for redundancy. But because both fibers carry identical wavelength by design, they can't simply run in parallel as two independent links — without Eth-Trunk in manual backup mode explicitly grouping them, the identical wavelength interferes directly and produces a port that won't link up, or one that flaps. Eth-Trunk itself enforces this: try to configure the pair wrong and it refuses with one of three specific error messages, rather than silently accepting a broken configuration.
What follows is those three error messages exactly as they appear, the interface-numbering rule behind all of them, the strict 2-member limit for this specific backup mode, and the pre-checks that avoid all three before you type a single command.
One convergence module, two center-switch ports, one Eth-Trunk in manual backup mode — everything else follows from getting this one relationship right.
The master port carries traffic; the backup port stays Inactive and ready, and its TX power reading of -40dBm is the expected, healthy state for a standby member, not a fault.
Diagram labels are kept in English for engineering clarity.
Everything in the three error messages below comes back to that numbering-rule box in the diagram — Eth-Trunk is enforcing it at configuration time instead of letting a bad pairing reach production.
Each of these blocks the configuration outright rather than accepting it and failing later — read the error text itself before assuming it's a bug.
This fires when you try to set backup mode on an Eth-Trunk whose member ports don't share the required numbering relationship.
[HUAWEI]interface Eth-Trunk 100
[HUAWEI-Eth-Trunk100]mode manual backup
Error: The parameter of work mode command is invalid, because the remainders of the member interface numbers divided by 8 must the same.
[HUAWEI-Eth-Trunk100]Same underlying rule, caught at the point of adding the interface rather than at the point of setting the mode.
[HUAWEI]interface 10GE1/0/11
[HUAWEI-10GE1/0/11]eth-trunk 100
Error: Failed to add the interface to the Eth-Trunk interface in master/backup mode because the remainders of the member interface numbers divided by 8 must the same.
[HUAWEI-10GE1/0/11]This one is a hard count limit, unrelated to numbering — manual-backup Eth-Trunk on a PEN dual uplink supports exactly 1 master and 1 backup, never more.
[HUAWEI]interface 10GE1/0/34
[HUAWEI-10GE1/0/34]eth-trunk 100
Error: Failed to add the port into the trunk in manual backup mode because the number of Eth-Trunk members cannot exceed two.
[HUAWEI-10GE1/0/34]This isn't an arbitrary software limit — it's Eth-Trunk enforcing a physical requirement about wavelength before a bad pairing ever reaches production.
A PEN center module's 160G/40G CFP2 interface breaks down into 8 logical sub-ports per group, and each of the 8 positions within a group is tied to a fixed wavelength — position 1 in every group uses the same wavelength as position 1 in every other group, position 2 the same as every other position 2, and so on. For two ports to form a valid master/backup pair on the same wavelength, they have to occupy the same numbered position in their respective groups — which is exactly what "the same remainder when divided by 8" checks. Two ports at different positions would carry different wavelengths, which defeats the entire purpose of a same-wavelength backup pair, so Eth-Trunk refuses the configuration outright rather than accepting a pairing that can't actually work as backup.
#
interface 10GE1/0/40
eth-trunk 1
device transceiver 10GBASE-FIBER
#
interface 10GE2/0/40
eth-trunk 1
device transceiver 10GBASE-FIBER
#
interface Eth-Trunk1
port link-type trunk
mode manual backup
#
<HUAWEI> display eth-trunk 1
Eth-Trunk1's state information is:
WorkingMode: BACKUP
WorkingState: Master
--------------------------------------------------------------------------------
PortName Slave/Master Status WorkingState
10GE1/0/40 M Up Active
10GE2/0/40 S Up Inactive
// both port numbers give remainder 0 when divided by 8 -- a valid backup pairRead these before you pick which two ports to bundle — most rejected configurations trace back to one of these five.
SYMPTOMmode manual backup is rejected with the remainder-of-8 error, even though the two ports look like a sensible pair at a glance.
CAUSETwo ports only carry the identical wavelength required for a backup pair when they occupy the same numbered position within their respective 8-port groups — that's what the remainder-of-8 check verifies, and it has nothing to do with which physical slot or panel position looks convenient.
FIXDivide each candidate port's interface number by 8 and compare the remainders before choosing a pair — don't pick ports based on which two happen to be physically adjacent or convenient to cable.
SYMPTOMEth-Trunk mode was already set to manual backup successfully, but adding the second physical interface as a member fails.
CAUSEThe remainder-of-8 rule is enforced at two separate points — when the mode itself is set, and again independently when a physical interface is added as a member — so passing the first check doesn't guarantee the second will pass if the wrong port is chosen.
FIXVerify both candidate ports' remainders match before configuring either the Eth-Trunk mode or adding members — checking once up front avoids hitting this error at a second, separate configuration step.
SYMPTOMA third interface is refused when trying to join an Eth-Trunk that already has a master and a backup member, with no numbering issue involved at all.
CAUSEPEN's dual-uplink manual-backup scenario is specifically a 1-master, 1-backup design — this 2-member cap is a rule of this specific backup mode, not a general Eth-Trunk member limit that applies everywhere else in the system.
FIXKeep dual-uplink Eth-Trunk bundles to exactly 2 members; if more redundant paths are actually needed, that calls for a different design, not a larger backup-mode bundle.
SYMPTOMAfter a correct dual-uplink configuration, the backup member's TX power reads -40dBm permanently, and someone opens a ticket to investigate a failed module.
CAUSEThe Inactive member of a manual-backup Eth-Trunk does not transmit while in standby — it isn't sending light, so a -40dBm TX reading is exactly what a correctly working backup port should show, not a symptom of damage.
FIXCheck display eth-trunk before troubleshooting the module itself; a -40dBm TX reading on a port confirmed as the Inactive member needs no further action.
SYMPTOMA member port joins the Eth-Trunk without error, but the bundle still doesn't behave correctly, or the interface doesn't recognize the optic properly.
CAUSEThe device transceiver 10GBASE-FIBER line under each member interface is part of the working reference configuration alongside the Eth-Trunk membership itself — skipping it leaves the interface's transceiver type unset even though the Eth-Trunk configuration otherwise succeeded.
FIXConfigure device transceiver 10GBASE-FIBER under both member interfaces as part of the same change as the Eth-Trunk membership, not as an afterthought.
Pulled straight from the field — the ones worth having an answer ready for.
Both fibers to the same convergence module carry identical wavelength by design. Two independent links on the same wavelength arriving at the same receiver interfere with each other directly at the physical layer — that shows up as a port that won't link up, or one that flaps, not as a working pair of redundant links. Eth-Trunk in manual backup mode is what makes the pair safe.
A PEN center module's CFP2 interface breaks into 8 logical sub-ports per group, and each numbered position within a group carries a fixed wavelength shared with the same position in every other group. Two ports at the same position — same remainder when divided by 8 — carry identical wavelength, which is exactly what a backup pair needs. Different remainders mean different wavelengths, which can't function as a backup pair.
No — load-balancing modes send traffic over both members simultaneously, which puts identical-wavelength light on both fibers at once and produces exactly the interference this design exists to avoid. Manual backup mode, with one Active and one Inactive member, is what keeps only one fiber transmitting at a time.
No. The Inactive backup member of a manual-backup Eth-Trunk doesn't transmit while on standby, so its TX power reads -40dBm by design — that's the expected, healthy state, confirmed with display eth-trunk, not a module to replace.
Run display eth-trunk on the bundle. The WorkingMode field confirms it's actually running BACKUP mode, and the per-member table's WorkingState column shows Active for the port currently forwarding traffic and Inactive for the standby port — that table is the authoritative answer, not the optical power readings alone.
This note is built around the Huawei S-series PEN dual-uplink Eth-Trunk manual-backup mode and its display eth-trunk / display current-configuration interface commands, plus the exact error messages behind them. The remainder-of-8 numbering rule and the 2-member cap described here are specific to this PEN dual-uplink backup scenario; general-purpose Eth-Trunk load-balancing modes elsewhere in the same product line follow different rules and member limits. It doesn't cover LACP-negotiated Eth-Trunk configuration, since PEN dual uplink specifically uses manual backup mode, not LACP.
Send us the exact error message and the two interface numbers you're trying to bundle — we'll help you read it.