Showing posts with label Huawei MA5606T. Show all posts
Showing posts with label Huawei MA5606T. Show all posts

Thursday, November 30, 2017

What Is the Relationship Between the LOF and LOS Alarms?


How to detect LOF and LOS alarms and what is the relationship between these two alarms? What alarm is generated if optical fibers are removed when the Huawei MA5606T or MA5652G serves as an Huawei ONU?



LOF indicates loss of frame. When such an alarm is generated, the ONU can receive optical signals. LOS indicates loss of signal. When such an alarm is generated, the ONU fails to receive optical signals. The mechanisms of detecting LOFi and LOSi alarms are as follows:
  • LOFi: If four consecutive frames of an OLT fail to locate an upstream frame of an ONU, the LOFi alarm is generated and the ONU goes offline.
  • LOSi: If four consecutive frames of an OLT MA5600T fail to receive an upstream optical signal of an ONU, the LOFi alarm is generated and the ONU goes offline.
The relationship between the LOF and LOS alarms is as follows:
  • Use an optical attenuator to test the ATM 155/622 Mbit/s optical port and increase the attenuation gradually. It is found that the alarm status changes as follows: normal -> SD -> LOF -> LOS. This indicates that after LOF is generated, if the attenuation is increased further, no optical signal is received and LOS is generated. If an optical fiber is removed, LOF may be generated first and then LOS, which is related to the alarm detection mechanism. The LOSi, LOFi, and LCDGi alarms are detected in the time window mode. In the first several detections, if the time window detects the threshold for frame losing, the LOFi alarm will be generated.
  • If the PON line generates an LOF alarm, LOS will not be generated. This is because the PON port uses the time division system. If an LOF alarm is generated, the ONT goes offline and then the OLT does not assign the timeslot (bandwidth) to the ONU. Therefore, the OLT does not detect whether the ONT transmits upstream optical signals and an LOS alarm is not generated.
  • If LOS is generated, LOF/SD will be suppressed. This is because LOS is the alarm of the highest severity.
When the MA5606T and MA5652G serve as an ONU MA5628 and the optical patch is normal, LOS is generated when an optical fiber is removed.
Posted by at No comments:
Labels: , , , , , ,

Monday, August 14, 2017

What Is the Relationship Between the LOF and LOS Alarms?

How to detect LOF and LOS alarms and what is the relationship between these two alarms? What alarm is generated if optical fibers are removed when Huawei MA5606T or MA5652G serves as an Huawei ONU?
LOF indicates loss of frame. When such an alarm is generated, the ONU can receive optical signals. LOS indicates loss of signal. When such an alarm is generated, the ONU fails to receive optical signals. The mechanisms of detecting LOFi and LOSi alarms are as follows:
  • LOFi: If four consecutive frames of an OLT fail to locate an upstream frame of an ONU, the LOFi alarm is generated and the ONU goes offline.
  • LOSi: If four consecutive frames of Huawei OLT fail to receive an upstream optical signal of an ONU, the LOFi alarm is generated and the ONU goes offline.
The relationship between the LOF and LOS alarms is as follows:
  • Use an optical attenuator to test the ATM 155/622 Mbit/s optical port and increase the attenuation gradually. It is found that the alarm status changes as follows: normal -> SD -> LOF -> LOS. This indicates that after LOF is generated, if the attenuation is increased further, no optical signal is received and LOS is generated. If an optical fiber is removed, LOF may be generated first and then LOS, which is related to the alarm detection mechanism. The LOSi, LOFi, and LCDGi alarms are detected in the time window mode. In the first several detections, if the time window detects the threshold for frame losing, the LOFi alarm will be generated.
  • If the PON line generates an LOF alarm, LOS will not be generated. This is because the PON port uses the time division system. If an LOF alarm is generated, the ONT goes offline and then the OLT like MA5603T does not assign the timeslot (bandwidth) to the ONU. Therefore, the OLT does not detect whether the ONT transmits upstream optical signals and an LOS alarm is not generated.
  • If LOS is generated, LOF/SD will be suppressed. This is because LOS is the alarm of the highest severity.

When the MA5606T and MA5652G serve as an ONU and the optical patch is normal, LOS is generated when an optical fiber is removed.
Posted by at No comments:
Labels: , , , , , , ,

Monday, March 6, 2017

Where to Find the Corresponding for the Error Codes Carried by Response in the Package Capturing

Issue Description
Q:
Where to find the corresponding Chinese description for the error codes carried by response in the package capturing?
Alarm Information
Null
Handling Process
A:
As for the V200R008 network management version, the mapping of most error codes can be found in the table of bms_NMSErrCode in BMSDB database. For those error codes that cannot be found in this table, confirm with the R&D of the host.
The following commands can be run:
1>select * from bms_NMSErrCode                                                    
2> go    
iDevType    iModuleID   iDeviceErrCode  iNMSErrCode        strErrDesc
-2           0            -18          1610612809.000000            
Illegal address
In this table, two fields of iDeviceErrCode and strErrDesc exist: The former one is the error code returned by the equipment and the latter one is the corresponding interpretation.
Root Cause
Null
Suggestions
Null
 The most popular Huawei S2700EI switch as below:

LS-S2700-9TP-SI-AC

Posted by at No comments:
Labels: , , , , ,

Tuesday, March 8, 2016

How to Configure the Auto-save Function for Huawei OLT

This topic describes how to configure the auto-save function so that the system configuration data or database files can be saved automatically. You can also make an reference for the Huawei MA5612,MA5608T, MA5606T, MA5600T.
Background Information
The MA5600 supports two auto-save modes:
• Auto-save at preset interval.
• Auto-save at preset time.
Pay attention to the following points:
• Auto-save at preset time conflicts with auto-save at preset interval. You can enable only one of them.
• Saving data frequently affects the system. Therefore, an auto-save interval shorter than one hour is not recommended, and it is recommended that you set the interval equal to or longer than one day.
• Before the system upgrade operation, run the autosave interval off or autosave time off command to disable the auto-save function to prevent upgrade failure due to the conflict between upgrade and auto-save operations.

NOTICE:
After the system upgrade is completed, you must re-enable the auto-save function if the auto-save function is required

Procedure
• Configure auto-save at preset interval.
1. In the global config mode, run the autosave interval on command to enable auto-save at preset interval.
Auto-save at preset interval conflicts with auto-save at preset time. You can enable only one of them.
2. (Optional) In the global config mode, run the autosave interval configuration command to set the auto-save interval for modified system data.
Auto-save is performed according to the interval set by the user. The system checks whether the system data is modified at each interval. If the system data is modified, the system saves the data. Otherwise, the system does not save the data. By default, the interval is 30 minutes.
3. (Optional) In the global config mode, run the autosave interval command to set the auto-save interval.
After the setting, the system data is automatically saved at the set interval regardless of whether the system data is modified. By default, the interval is 24 hours.
4. (Optional) Set the auto-save file type.
In the global config mode, run the autosave type command to set the auto-save file type.
• Configure auto-save at preset time.
1. In the global mode, run the autosave time on command to enable auto-save at preset time.
Auto-save at preset time conflicts with auto-save at preset interval. You can enable only one of them.
2. (Optional) In the global config mode, run the autosave time command to set the auto-save time.
After the setting, the system data is automatically saved at the set time regardless of whether the system data is modified. By default, the time is 00:00:00.
3. (Optional) Set the auto-save file type.
In the global config mode, run the autosave type command to set the auto-save file type.

Example
To enable auto-save at preset interval on the MA5600 series, set the auto-save interval to two days (2880 minutes), and save both the database file and the configuration file, do as follows:
huawei(config)#autosave interval on
huawei(config)#autosave interval 2880
huawei(config)#autosave type all
huawei(config)#save

Telephone: 852-30623083
           Supports@Thunder-link.com            
Posted by at No comments:
Labels: , , , , , , , , , , ,

Thursday, March 3, 2016

Troubleshooting the FTTB and FTTC Service (OLT +MDU)

This chapter describes how to troubleshoot common faults in Internet access, multicast (IPTV), and voice (VoIP) services in the GPON access mode in FTTB and FTTC scenarios. MDU refers to MA561x, MA562x, MA5612 and MA5606T. Command lines executed by MDU are examples of MA5616.

Troubleshooting the Internet Access Service (When the MDU Provides xDSL Access)

This chapter describes how to troubleshoot common faults users encounter when accessing the Internet using MDU in xDSL mode on FTTB and FTTC network. Common faults include Internet access failure, frequent service disconnection, low access rate, and failure to obtain an IP address by Point-to-Point Protocol over Ethernet (PPPoE) dialup or Dynamic Host Configuration Protocol (DHCP) mode.

Prerequisites
The ONU and the OLT must communicate with each other normally. If a fault occurs in
communication between the ONU and the OLT, all the services of the ONU are interrupted.

NOTE
The following lists common faults in communication between the ONU and the OLT.
A 2.1.1 GPON ONU Registration Failure
B 2.1.2 Failure to Auto Discover a GPON ONU
C 2.1.3 GPON ONU Frequently Goes Online and Offline

Troubleshooting the Failure to Access the Internet
This section describes how to troubleshoot failures when users access the Internet on fiber to the building (FTTB) and fiber to the curb (FTTC) networks in xDSL mode, for example, users fail to open Web pages.

Fault Location
Use the following guidelines to locate the fault.

ma5603t 4-2 1
Procedure
Step 1 Check the user terminal.
1. Check whether the user’s PC can obtain an IP address

NOTE
To view the IP address of the PC, do as follows:
a. Choose Start > Run from the Windows main menu. In the Run dialog box displayed, enter cmd and press Enter.
b. In the CLI window displayed, run the ipconfig command to view the IP address obtained by the PC.
1 If the PC can obtain an IP address, go to Step 1.3.
If the PC cannot obtain an IP address, do as follows:
– For PPPoE users, see 2.3.1.4 Troubleshooting the Failure to Obtain an IP
Address by PPPoE Dialup. Then, go to Step 1.2.
– For DHCP users, see 2.3.1.5 Troubleshooting the Failure to Obtain an IP
Address in DHCP Mode. Then, go to Step 1.2.

2. Check whether the user can access the Internet.
l If the user can access the Internet successfully, go to Step 5.
l If the user cannot access the Internet, go to Step 1.3.

3. Replace the user’s PC with a test PC that can access the Internet in the same mode as the user’s PC. Then, check whether the user can access the Internet.
l If the user can access the Internet, the fault is on the user’s PC. Check whether the user’s PC is infected with viruses, the NIC or IE of the user’s PC is faulty, or the PC is slow
to respond after running for a long period. Then, go to Step 5.
l If the user cannot access the Internet, go to Step 2.
Step 2 Check whether the user can access the Internet by going to various Web sites through the Web server.
l If the user can access certain Web sites, the fault is on the Web site itself. Go to Step 5.
l If the user cannot access any Web sites, go to Step 3.

Step 3 Check the DNS.
1. Enter the IP address of an existing Web site in the address bar of IE (format: http://
192.168.0.2) and check whether the Web site opens.
l If the Web site opens, the fault is on the DNS and the DNS cannot resolve the domain
name. Go to Step 3.2.
l If the Web site does not open, go to Step 4.

2. Check whether the PC can ping the IP address of the DNS.
NOTE
To view the DNS IP address of the PC, do as follows:
a. Choose Start > Run from the Windows main menu. In the Run dialog box displayed, enter cmd and press Enter.
b. In the command line interface (CLI) window displayed, run the ipconfig/all command to view the DNS IP addresses obtained by the PC, namely, the values of the DNS Servers parameter.
l If the PC can ping the IP address of the DNS, the link between the PC and the DNS is
normal and the DNS is faulty. Go to Step 3.3.
l If the PC cannot ping the IP address of the DNS, go to Step 4.

3. Rectify the fault on the DNS. Then, check whether the user can access the Internet.
l If the user can access the Internet successfully, go to Step 5.
l If the user cannot access the Internet, go to Step 4.
                                       
Step 4 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 5 The fault is rectified.
—-End

More related:

Optical attenuation is too large lead to ONU recovery failure

Posted by at No comments:
Labels: , , , , , , , ,
Subscribe to: Posts (Atom)