Huawei HG8245T Router Manual PDF (Setup & Configuration Guide)

Home

Manuals

Huawei

HG8245T

Page 391 / 429 Scroll up to view Page 386 - 390

Check whether the number of PPPoE sessions reaches the upper limit in the case that the

MAC address allocation mode is single-mac.

CAUTION

To facilitate fault report, save the results of the following steps.

Procedure

Step 1

Run the

display alarm history

command to check whether alarms (such as alarms indicating

ONU power-off, loss of optical signals, and Ethernet port down) are generated. If such alarms

are generated, clear them by referring to alarm processing guide.

If the fault persists even after alarms are cleared, proceed to

Step 2

If the fault is rectified after alarms are cleared, go to

Step 19

Step 2

Check the upper-layer device and perform PPPoE dialup simulation on the OLT.

If the simulation result is "timeout", "parameter negotiation failure", "user authentication

failure", "offline requested by the peer side", or "other errors", it indicates that the upper-

layer device connected to the OLT is faulty. Then, mainly check whether the VLAN

configuration of the upper-layer device is correct, whether the OLT can ping the BRAS,

whether the user name/account is configured correctly on the BRAS, and whether the BRAS

limits the number of users accessing the Internet. Ensure that all the preceding information

is correct. Then, proceed to

Step 3

If the simulation result is "success", go to

Step 4

Step 3

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 4

Replace the user's PC with another one to perform PPPoE dialup again.

If PPPoE dialup is successful, it indicates that the user's PC is faulty. Mainly check whether

the PPPoE software is installed correctly and whether the PC NIC is faulty or disabled.

Ensure that there are no abnormalities. Then, proceed to

Step 5

If PPPoE dialup still fails, go to

Step 6

Step 5

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 6

Check whether the ONU encounters faults such as ONU registration failure, failure to auto

discover an ONU, and ONU frequent offline.

If the ONU encounters any of the preceding faults, solve it by referring to relevant

troubleshooting guide. Then, proceed to

Step 7

If the ONU works in the normal state, go to

Step 8

Step 7

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 8

EchoLife HG8010/HG8240B/HG8245T/HG8247T GPON

Terminal

Service Manual

5 Maintenance and Troubleshooting

Issue 01 (2011-10-18)

Huawei Proprietary and Confidential

383

Page 392 / 429

Step 8

Check the line between the ONU and the PC. Connect the PC to the ONU direct.

If the network cable is broken or not connected firmly, replace or reconnect the network

cable. Then, go to

Step 9

If PPPoE dialup still fails when the PC connect to the ONU direct. Then, go to

Step 10

Step 9

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 10

Check the data configuration. Specifically, check whether the data configurations of the OLT

and the ONU are correct. If services are in the normal state before the fault occurs, it is

recommended that you run the

display log

command to check the system logs and then check

whether the fault is caused by modifications of data configuration.

NOTE

Incorrect data configuration is a common cause of a fault. The following is likely to configure incorrectly:

Service stream: You can run the

display service-port

command to check whether the service stream

configuration is correct. Specifically, mainly check whether the user VLAN, GEM port, ONU ID, port ID,

and upstream port comply with actual conditions.

VLAN tag switching: You can analyze the VLAN tag switching process according to the service port

configuration on the OLT and the ONU. Specifically, mainly check whether the VLAN tag switching on

the ONU and the OLT and the native VLAN configuration on the upstream port of the OLT are correct.

If there are data configuration errors, correct them by referring to configuration guide

documents. Then proceed to

Step 11

If the data configuration is correct, go to

Step 12

Step 11

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 12

Check the PITP configuration. That is, run the

display pitp config

command to check the status

of the global PITP function, run the

display pitp port

command to check the status of the PITP

port, and then run the

display pitp service-port

command to check the status of the PITP

function of the service port to check whether the PITP function is enabled.

NOTE

PITP is supported at three levels, namely, system level, port level, and service port level. By default,

the system-level PITP is disabled, while the port-level PITP and the service-port-level PITP are enabled.

The PITP function takes effect only when the three levels of PITP are enabled concurrently.

After the PITP function is enabled, the device information is carried in a PPPoE packet and the PPPoE

packet is then authenticated on the BRAS. The authentication is successful only when the device

information (added by OLT or by a user-side device) is the same as that configured on the BRAS.

If PITP is in the enable state, check whether the device information carried in a PPPoE

packet is added by the OLT or by a user-side device during the authentication on the BRAS.

–

If the device information is added by a user-side device, run the

pitp permit-

forwarding service-port

command to configure the OLT to allow the PPPoE packet

with the device information (vendor tag) added by the user-side device to pass a user

port. Then, proceed to

Step 13

–

If the device information is added by the OLT (this is the default mode), there is no need

to proceed. Then, go to

Step 14

If PITP is in the disable state, go to

Step 14

EchoLife HG8010/HG8240B/HG8245T/HG8247T GPON

Terminal

Service Manual

5 Maintenance and Troubleshooting

Issue 01 (2011-10-18)

Huawei Proprietary and Confidential

384

Page 393 / 429

Step 13

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 14

Check whether the number of MAC addresses learned reaches the upper limit. Run the

display

mac-address port

command and the

display mac-address max-mac-count

command to

respectively query the actual number of MAC addresses learned by a user port and the maximum

number of MAC addresses learned dynamically by the user port.

If the actual number of MAC addresses learned by the user port reaches the upper limit

(that is, the maximum number of MAC addresses learned dynamically by the user port),

run the

mac-address max-mac-count

command to increase the upper limit. Then, proceed

Step 15

If the actual number of MAC addresses learned by the user port is lower than the upper

limit, go to

Step 16

Step 15

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 16

Check whether the number of PPPoE sessions reaches the upper limit in the case that the MAC

address allocation mode is single-mac. Run the

display pppoe mac-mode

command to query

the MAC address allocation mode for the PPPoE user.

If the MAC address allocation mode is single-mac, run the

pppoe max-session-count

command to configure the maximum number of PPPoE sessions of a user port to 8 (the

largest value). Then, proceed to

Step 17

NOTE

If the number of online PPPoE sessions is greater than the preset upper limit, the system does

not allow to set up a new PPPoE session.

When the MAC address allocation mode is single-mac, a user port allows a maximum of eight

PPPoE sessions. Thus, make a proper plan before network deployment to prevent that the number

of online PPPoE sessions exceeds eight.

If the MAC address allocation mode is multi-mac (the default mode), go to

Step 18

Step 17

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 19

If the service does not recover to normal, proceed to

Step 18

Record the results of the preceding steps in the form for reporting a fault, fill in the form

completely, and then submit the form to Huawei for technical support.

Step 19

The fault is rectified.

----End

?.5. Failure to Obtain an IP Address in the DHCP Mode

This topic describes how to troubleshoot the fault when a user fails to obtain an IP address in

the DHCP mode during accessing the Internet.

Location Method

When the IP address cannot be obtained in the DHCP mode, locate the fault according to the

following procedure:

EchoLife HG8010/HG8240B/HG8245T/HG8247T GPON

Terminal

Service Manual

5 Maintenance and Troubleshooting

Issue 01 (2011-10-18)

Huawei Proprietary and Confidential

385

Page 394 / 429

Check major alarms.

Check the upper-layer device.

Check the user's PC.

Check the ONU.

Check the line between the ONU and the PC.

Check the data configuration.

Check the DHCP option82 configuration.

CAUTION

To facilitate fault report, save the results of the following steps.

Procedure

Step 1

Run the

display alarm history

command to check whether alarms (such as alarms indicating

ONU power-off, loss of optical signals, and Ethernet port down) are generated. If such alarms

are generated, clear them by referring to alarm processing guide.

If the fault persists even after alarms are cleared, proceed to

Step 2

If the fault is rectified after alarms are cleared, go to

Step 15

Step 2

Check the upper-layer device, and check whether all the users of the upper-layer device fail to

obtain the IP address.

If all the users fail to obtain the IP address, it indicates that the upper-layer device is faulty.

In this case, check whether the DHCP server works normally. Then, proceed to

Step 3

If only certain users cannot obtain the IP address, go to

Step 4

Step 3

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 15

If the service does no recover to normal, proceed to

Step 4

Replace the user's PC with another one to perform a test again.

If an IP address can be obtained, it indicates that the PC is faulty. Then, mainly check

whether the network position of the PC is correct and whether the PC NIC is faulty or

disabled. Ensure that there are no abnormalities. Then, proceed to

Step 5

If the IP address cannot be obtained, go to

Step 6

Step 5

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 15

If the service does no recover to normal, proceed to

Step 6

Check whether the ONU encounters faults such as ONU registration failure, failure to auto

discover an ONU, and ONU frequent offline.

If the ONU encounters any of the preceding faults, rectify it by referring to relevant

troubleshooting guide. Then, proceed to

Step 7

If the ONU works in the normal state, go to

Step 8

EchoLife HG8010/HG8240B/HG8245T/HG8247T GPON

Terminal

Service Manual

5 Maintenance and Troubleshooting

Issue 01 (2011-10-18)

Huawei Proprietary and Confidential

386

Page 395 / 429

Step 7

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 15

If the service does no recover to normal, proceed to

Step 8

Check the line between the ONU and the PC. Connect the PC to the ONU direct.

If the network cable is broken or not connected firmly, replace or reconnect the network

cable. Then, go to

Step 9

If PPPoE dialup still fails when the PC connect to the ONU direct. Then, go to

Step 10

Step 9

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 15

If the service does no recover to normal, proceed to

Step 10

Check the data configuration. Specifically, see configuration guide documents to check whether

the data configurations of the OLT and the ONU are correct. If services are in the normal state

before the fault occurs, it is recommended that you run the

display log

command to check the

system logs and then check whether the fault is caused by modifications of data configuration.

NOTE

Incorrect data configuration is a common cause of a fault. It is likely to configure the following incorrectly:

Service port: You can run the

display service-port

command to check whether the service port configuration

is correct. Specifically, mainly check whether the user VLAN, GEM port, ONU ID, port ID, and upstream

port comply with actual conditions.

VLAN tag switching: You can analyze the VLAN tag switching process of data packets according to the

service port configuration on the OLT and the ONU. Specifically, mainly check whether the VLAN tag

switching on the ONU and the OLT, and the native VLAN configuration on the upstream port of the OLT

are correct.

DHCP configuration: By default, DHCP works in the Layer 2 mode and there is no need to configure it. If

DHCP is required to work in the Layer 3 mode, configure it by referring to the configuration guide

documents.

If there are data configuration errors, correct them by referring to configuration guide

documents. Then proceed to

Step 11

If the data configuration is correct, go to

Step 12

Step 11

Check whether the service recovers to normal.

If the service recovers to normal, go to

Step 15

If the service does no recover to normal, proceed to

Step 12

When the OLT works in the Layer 2 mode, check the DHCP option82 configuration. That is,

run the

display dhcp option82 config

command to check whether the status of the global DHCP

option82 function and then run the

display dhcp option82 service-port

command to check

whether the status of the DHCP option82 function of the service port to check whether the DHCP

option82 function takes effect.

NOTE

The DHCP option82 function works globally or works only for service ports. By default, this function

works only for service ports. Only when this function works globally and works for service ports, can

this function take effect.

After the DHCP option82 function is enabled, the device information is carried in a DHCP packet and

the DHCP packet is then authenticated on the BRAS. The authentication is successful only when the

device information (added by OLT or by a user-side device) is the same as that configured on the

BRAS.

EchoLife HG8010/HG8240B/HG8245T/HG8247T GPON

Terminal

Service Manual

5 Maintenance and Troubleshooting

Issue 01 (2011-10-18)

Huawei Proprietary and Confidential

387

Rate

Popular Huawei Models

Famous Router IPs

Famous Router Companies

Bookmark Our Site

Share