Keywords: MA5616, Access network product line Summary In MA5616 V800R312 equipped with an H831CCUB or H831CCUC control board, if data is frequently saved into the database, the database malfunctions after the MA5616 runs for a period of time. As a result, the MA5616 resets and starts from an empty database. Problem Description Trigger Conditions This… Read More »
Keywords: MA5616, Access network product line Summary The MxU products use the IPOS protocol stack. After the MxU devices run for a long time (for example, longer than 497 days), the Address Resolution Protocol (ARP) entry learned by some MxU devices from the upper-layer device, such as a gateway, cannot automatically age. In this case,… Read More »
Keywords: MA5616, H831CCUC, JDSU (optical module vendor), GE optical module, GE optical port cascading, cascading failure Summary: An MA5616 equipped with the H831CCUC control board uses the JDSU-provided GE optical module with BOM number 34060286 for upstream cascading. The cascading fails and the LINK indicator on the control board is not on. Product Line: Access Network… Read More »
Abstract: In MxU V800R306C01, V800R307C00, and V800R307C01, the MxU control board fails after the following operations are performed: Product Line: Access network product line Product Model: MA5616 l Create a rate unlimited traffic profile (traffic table ip) through the U2000 or N2000. l Bind the traffic profile to a service port on the MxU. Restart the MxU. [Problem Description]… Read More »
During a lab test for the SmartAX MA5616 V800R307C02, a service interruption has occurred due to an exception of the logic. The root cause, however, is not yet identified after more than three months of efforts to reproduce the issue in the lab. This prewarning notice describes how to identify this issue and restore the service. Product Line: Access network Product Model: MA5616 Problem Description Trigger conditions Use a SmartAX MA5616 V800R307C02 that is in full configuration of service boards in the test. Create a service port on each VDSL port, set up a point-to-point over Ethernet (PPPoE) connection on each service port, and send the packets. Import the configuration file to the device and activate the file multiple times, and then reset the system. Enable and disable the security function multiple times and then perform dynamic host configuration protocol (DHCP) dialup and PPPoE dialup multiple times. Symptom 1. The dialup on all service ports fails. 2. The uplink and user ports collect statistics of the received ports but the logic does not collect packet statistics. Identification method 1 The system cannot forward services and all the services are interrupted. 2 Query the statistics of the received and transmitted packets on the uplink and user ports to determine whether the packets are transmitted to the FPGA logic. 2.1 The following screen shows the command and command output for querying the statistics of the received and transmitted packets on the user port. 2.2 The following screen shows the command and command output for querying the statistics of the received and transmitted packets on the uplink port. 3 If the received packets on the uplink and user ports increase, the packets are transmitted to the FPGA logic. Then, query the statistics of the packets processed by the logic. 3.1 The following screen shows the command and command output for querying the statistics of the packets processed by the logic. 4 If the values of all statistical items do not increase, an exception occurs on the logic. Note: All the preceding four conditions must be met. Root Cause The inner status mechanism of the logic becomes abnormal, resulting in the system failure to transmit packets to the FPGA logic. As a result, the packets are discarded on the ingress port. The root cause for the abnormality of the status mechanism has not yet been identified. Impact and Risk All the services on the system are interrupted. Measures and Solutions Solution There is little probability of this issue, which has not recurred during more than three months of issue… Read More »
Summary: In MA5616 V800R310C00SPC100 through V800R310C00SPH109, if the MA5616 uses an H.248 interface registered using a domain name, the MA5616 resource overload occurs after the MA5616 runs for a long period of time. Product Line: Access network Product Family: MxU Product Model: MA5616 Keywords: MA5616 resource overload Problem Description Trigger Conditions This issue occurs if the following conditions are met: The H.248 service has been configured on the MA5616. A softswitch domain name has been configured on an H.248 interface. The softswitch domain name is only used for checking an H.248 message head. The following figure shows an example.
Summary: When replacing the AC power board PAIA/PAIB on the MA5610/MA5616, if the operator removes the power board without powering off it beforehand (removing the 220 V AC power connector on the panel), there are potential safety hazards. Product Line: Access Network Product Model: MA5616 Keywords: MA5610/MA5616 PAIA PAIB AC power board security specifications Problem Description Trigger conditions When replacing of the AC power board PAIA/PAIB on the MA5610/MA5616, the operator removes the AC power board without powering off the board beforehand (disconnecting the 220 V AC power plug from the panel). Symptom Removing the power board before disconnecting the 220 V power plug from the board panel causes potential safety hazards. Identification method The MA5610s/MA5616s installed with the PAIA or PAIB power boards that are delivered to sites before September 1, 2009 are affected. Root Cause The safety specifications of the H831PAIA/H831PAIB AC power boards used on the MxUs cannot fully meet the requirements, which may produce potential safety hazards to operators who remove the power boards without complying with safety rules. Impact and Risk There are potential safety hazards. Measures and Solutions Preventive measures The safety specifications of the AC power boards delivered after September 2009 have been strengthened. Recovery measures Use the inspection tool to check the boards on the live network. Rectify the board with potential safety hazards. For the inspection tool script, detailed delivery data, rectification method, contact CS coordinator Xue Guoqiang (Employee ID: 98735) for China market and Nie Bo (Employee ID: 92548) for markets outside of China. Prewarning Expiration Condition This prewarning will expire after the board check is complete.