Troubleshooting PPPoE Dial‑up Failure on Huawei AR2240 Gateway

The Huawei AR2240 is deployed as an enterprise edge gateway connecting to an ISP via PPPoE. After configuration, the device cannot negotiate an IP address, while a directly connected PC can dial successfully.

# dialer-rule
 dialer-rule 1 ip permit

interface Dialer1
 link-protocol ppp
 ip address ppp-negotiate
 dialer user user2
 ppp chap user user1
 ppp chap password cipher user1
 dialer bundle 1
 dialer queue-length 8
 dialer timer idle 300
 dialer-group 1

interface Ethernet2/0/0
 pppoe-client dial-bundle-number 1 on-demand

ip route-static 0.0.0.0 0 Dialer1

return

Investigation steps:

1. Checked PPPoE session status – no session was established. <Huawei> display pppoe-client session summary 2. Verified packet statistics – no PPPoE packets were observed. <Huawei> display pppoe-client session packet 3. Displayed the Ethernet2/0/0 configuration and confirmed the interface is set to on‑demand dialing.

[Huawei] interface Ethernet2/0/0
[Huawei-Ethernet2/0/0] display this
#
interface Ethernet2/0/0
 pppoe-client dial-bundle-number 1 on-demand
#
return

4. Checked the status of the internal Ethernet1/0/0 interface – it was down, meaning no traffic could trigger the PPPoE call.

<Huawei> display interface Ethernet 1/0/0
Ethernet1/0/0 current state : DOWN
Line protocol current state : DOWN

The root cause was that the on‑demand PPPoE client only initiates a call when there is outbound traffic. Because the internal Ethernet interface was down, no traffic was generated, so the PPPoE session never started.

5. Solution: change the PPPoE client mode from on‑demand to permanent (always‑online). After applying the change, the AR2240 successfully establishes a PPPoE session.

[Huawei] interface Ethernet2/0/0
[Huawei-Ethernet2/0/0] pppoe-client dial-bundle-number 1

After this modification, the gateway dials the ISP automatically once the external interface is up, and the IP address is obtained correctly.