You are on page 1of 16

WMAX

Troubleshooting Guide

SW Version 2.5 September 2007 P/N 214693

B. Rev.5. March 2006 SW Version 2. Date Issued SW Version 2.0. June 2006 2 Modulation and Coding column updated Format Update 3 General ii WMAX Troubleshooting Guide . 1 Topic General Rates vs.Document History Document History No. SNR Table Section 8 Description This is the first release of this guide.0. February 2006 SW Version 2.

............................ 4 Downlink Traffic Problem .......Contents 1 2 3 4 5 6 7 8 SU Ethernet Port Connection Problem (No Telnet) .......... 3 SU Association Problem ........................................... 1 NPU Data Port Connection Problem (No Management)............................................................... 11 ......................................................................................................................... 2 TRAPs Sending Problem ....... 8 Rate vs...................... SNR Table .................................................................................................. 3 SU Data Connectivity Problem .................. 6 Uplink Traffic Problem....

.

Using SAU. and retry the Telnet command to the unit.251 IP address (due to a recent connection to another SU). Perform arpV-d at the DOS command prompt to clear the ARP table. is set to a small number. Replace cable Verify that the IDU-ODU cable is in order and connected properly. Wrong IP configuration Make sure that the PC is on the same subnet as the unit.0. and supported speeds are 10/100 Mbps. configurable from the Base station's side. verify that PWR LED is on and ALRM LED is off.254.SU Ethernet Port Connection Problem (No Telnet) 1 SU Ethernet Port Connection Problem (No Telnet) Possible Cause Wrong type of Ethernet cable Faulty Ethernet cable IDU-ODU cable problem. and the subnet mask is 255. Make sure that the speed and duplex settings in the PC match the configuration in the unit. Reset the SU to clear the table and retry the Telnet command to the unit. Wrong Ethernet port operation mode ARP table in the PC contains a wrong MAC address for the 192.168.168. Full or Half Duplex. but no Telnet access and the unit does not respond to ping. Otherwise-use a crossed cable.254. and/or the Ethernet Activity Indicator (the green embedded LED) does not blink when there should be traffic on the Ethernet port. The default operation mode is Auto Negotiation.251. Bridging table in SU is full (expected when Number of Supported Devices. The unit's IP address for management purposes is 192. Problem and Indication The Ethernet Integrity Indicator (the yellow LED embedded in the Ethernet connector) is off. The Ethernet Activity and/or Integrity LEDs are on. WMAX Troubleshooting Guide 1 . Corrective Action If connected directly to PC-use a straight cable.255.255.

verify that the Management Port Dest Subnet and Management Port Dest Subnet Mask are defined correctly (to ensure that the reply is routed through the Data port and does not go out through the Management port). straight otherwise. Verify that the Data Port Speed (100 Mbps or 1 Gbps) is compatible with the equipment connected. The default is None (No VLAN). check that the Ethernet cable is straight/crossed.255.0. The default IP address is 1.1.255. Verify that the Data Port Management VLAN ID matches the Management VLAN ID of the connected equipment.1. verify that the IP address of the device connecting to the management system is configured as an Authorized Manager.0. Problem and Indication No NPU Management Connection Troubleshoot via the Monitor program. Verify that the IP address of the Management port is other than 0. Check the IP parameters of Data port and try to ping it.0.Troubleshooting 2 NPU Data Port Connection Problem (No Management) Possible Cause Corrective Action 1 Verify that the Management port is disconnected. If connecting from a different subnet. If not. Verify that the Data Port Status is Up. according to the connected equipment: Crossed when connected directly to a PC.3 with subnet mask 255. Verify that the Data Port Management Traffic parameter is Enabled. and that the Read/Write communities configured in the Authorized Manager entry complies with the community strings used by the connected device.0. When working in SNMP. using the MON Serial port) Assumptions: 2 3 Management should be done via the Data port (In Band) ONLY 4 5 6 7 8 2 WMAX Troubleshooting Guide .

Corrective Action 1 2 Check that the power cable is connected.TRAPs Sending Problem 3 TRAPs Sending Problem Possible Cause Configuration problem Problem and Indication No Traps (Management is OK) Corrective Action Verify that the Send Traps parameter in the Authorized Manager entry for the managing device is set to Enable. check that the PWR LED is on and that the ALRM LED is off. Bandwidth. AU and NPU use the latest SW version. including the applicable AU. Verify that the Admin Status of relevant traps in the Trap Configuration menu is set to Enable. Verify that the IDU-ODU cable is connected. 3 SU-ODU is disconnected 1 2 Wrong configuration at SU side 1 2 The antenna bearing is not optimal. Using SAU.No Link (WLNK LED in SAU is off) Assumptions: The Base Station. Base Station ID parameters. Open a Telnet session to the SU. WMAX Troubleshooting Guide 3 . If connecting from a different subnet. At least 1 SU is associated with the applicable AU. Verify proper output power on the power cable connector. 4 SU Association Problem Possible Cause No power to the SU-IDU Problem and Indication No Association . Replace power cable. Verify that the unit's configuration matches the AU configuration: Frequency. Check that the location of the SU is according to the radio planning. Slowly align the antenna towards the Base Station while checking the SAU's LINK Bar LEDs. verify that the Management Port Dest Subnet and Management Port Dest Subnet Mask are defined correctly (to ensure that the reply is routed through the Data port and does not go out through the Management port). The SU. is up and running properly. Severe NLOS conditions. Verify that the unit is connected.

Troubleshooting 5 SU Data Connectivity Problem Possible Cause Bridging table in SU is full (expected when Number of Supported Devices. Check the Status of the SU: a SU is Temporary and the Base station Service Mode is Advanced: the SU will not receive services. at least one SU receives data. refer to SU Service Fault reasons below. Corrective Action Reset the SU to clear the table and retry the Telnet command to the unit. Otherwise. Check that the Service Fault Status of the SU is OK. Change the SU Status to Permanent and configure services. Base Station is up and running properly. SU is Temporary and the Base station Service Mode is Quick: Check that the applicable Default L2/PPPoE Service is configured (in the Services menu). SU is Permanent: check that a service is configured for the SU's MAC address (in the Services menu). find the SU according to its MAC address and check that the Registration Status of the SU is "In Service". SU Status Configuration problem 1 2 Ping the ISP's Local IP/Default Gateway. 2 4 WMAX Troubleshooting Guide . In the Base Station. Verify that traffic to/from the data equipment is not rejected due to any of the active filtering rules. Problem and Indication No Data Connectivity Assumptions: Link with the Base Station has been established. configurable from the Base station's side. User's data equipment connectivity is OK. is set to a small number. 3 4 b c Filtering configuration problem 1 Verify that the MAC Address of the data equipment is not included in the MAC Address Deny List.

and repeat the test. For testing purposes. if configured to "Reject". packets must carry either 802. If Down. Verify that Operation Status is Up. run Uplink traffic (SU to Base Station) before running Downlink Traffic (in order to update the Base station's bridging table (addresses behind the SU). If a low QoS (BE or NRT) is configured. Correct the loop problem and reset the SU from the Base Station's side. Verify that the Admin Status of the Subscriber is Enabled. matching the Service's definitions for VLAN List and Hybrid VLAN Mode.if configured as PPPoE. Make sure that the traffic you forward from the equipment connected to the SU is with the appropriate VLAN. Service Fault Status indicates a Loop problem A loop was detected on the Ethernet side of the SU. Verify that the traffic from the user's data equipment to the SU is with the correct priority marking as defined in the Priority Classifier: 802. If more than one Uplink/Downlink Upper Range is defined. make sure you are sending PPPoE packets only. the cell might be overloaded with higher priority traffic. reconfigure a QoS with higher priority. the SU may not be associated (refer to the "SU Association Problem" above).000 Kbps.1p or DSCP marking. Priority Classifier configuration problem QoS Starvation problem Check the QoS configured for the Service.SU Data Connectivity Problem Problem and Indication Possible Cause Service Configuration Problem Corrective Action Check proper Service configuration: 1 Verify that the Admin Status of the Service is Enabled. such as RT with CIR=12. Verify that the equipment behind the SU supports the correct marking.1p (VLAN Traffic only) or DSCP (packets containing DSCP). Check the Service Type . WMAX Troubleshooting Guide 5 . Verify that the equipment connected to the Data port of the Base Station supports the configured VPL ID (if VLAN Transparency Mode is Off) or the VLAN ID used by the equipment connected to the SU (if VLAN Transparency Mode is On). 2 3 4 Service Profile configuration problem 1 2 Forwarding Rule configuration problem Check the "Unknown Forwarding Policy" configuration.

replace the IDU. AU problem or high interference 1 Check the LEDs of the AU-ODU and AU-IDU/Micro Base Station. Check the radio planning. unique name for the SU and reset it. a single ODU is connected to the AU. run downlink traffic for 5 minutes and recheck the rate. the Burst Error Rate at the expected Rate is too high. If feasible. Corrective Action Configure a new. It is recommended to replace the IDU. Check for interferences using a spectrum analyzer.Troubleshooting Problem and Indication Service Fault Status indicates Duplicate SU Name problem. the problem is in the channel. Check for interferences using a spectrum analyzer. Try to identify source of interference.SNR table (below) In addition to the Rate being lower than expected. Try to use the second Channel: If the problem remains. Corrective Action Run downlink traffic via the unit for approximately 5 minutes and recheck the rate. try a different frequency (AU). Interference The Burst Error Rate at the expected Rate is low. SU-ODU problem Replace the SU-ODU and recheck. Possible Cause The Name configured in the SU is already in use by another SU. If the problem disappeared after switching to the second channel. 6 Downlink Traffic Problem Possible Cause Multirate algorithm has not stabilized yet Installation problem Problem and Indication High SNR. Due to interference the SU cannot reach the expected rate. Verify proper installation (including antenna alignment and distance from objects that may affect link quality) and when the installation is stable reset the SU. Low Rate in Downlink (SU) Check the Downlink SNR and Rate of the SU. The Rate is lower than expected according to the Rate vs. try a different frequency. replace the ODU. Check the radio planning. If the problem still exists. 2 3 4 5 6 WMAX Troubleshooting Guide . The problem exists also in neighboring SUs. If feasible.

two ODUs are connected to the AU/Micro Base Station and the problem occurs in SUs served by both ODUs. Check for interferences using a spectrum analyzer.Downlink Traffic Problem Problem and Indication The problem exists also in neighboring SUs. or high interference Corrective Action Check the LEDs of the AU-ODU and AU-IDU/Micro Base Station.replace the AU-IDU. If feasible. Check for interferences using a spectrum analyzer. If the problem is identified in the channel (exists now in the SUs served by the other ODU) . AU-IDU/Micro Base Station problem or high interference on both channels. Try to switch between the two ODUs (to identify a possible problem in one of the channels).. Check the LEDs of the AU-ODUs and AU-IDU/Micro Base Station. Possible Cause IDU or ODU problem. two ODUs are connected to the AU/Micro Base Station and the problem occurs only in SUs served by one of the ODUs. Replace the AU-IDU/Micro Base Station. WMAX Troubleshooting Guide 7 . Check the radio planning. Check the radio planning. replace the ODU. If the same ODU remains problematic. The problem exists also in neighboring SUs. try a different frequency.

If the rate has improved. It is recommended to replace the AU-IDU/Micro Base Station. Synchronize the SU to the AU/Micro Base station and recheck the rate. replace the ODU and recheck.SNR table (below). If the problem remains. the AU/Micro Base station is connected to a single ODU. The Rate is lower than expected according to the Rate vs. Note: select an available frequency as distant as possible from the original frequency. 3 4 b c d 8 WMAX Troubleshooting Guide . Low Rate in Uplink (SU) Check the Uplink SNR and Rate of the SU. replace the ODU and recheck. If the Burst Error Rate at the expected rate is low. If no interferences are exhibited. AU/Micro Base Station (IDU or ODU) malfunction or strong interference 1 2 Reset the AU and check the rate. Change the Channel's and SU frequencies (this can be done for a number of SUs only) and check the rate. Verify (via counters) that uplink traffic runs through the AU. Perform Spectrum measurements on the Channel's new frequency. the problem is in the Channel. Problem occurs in all SUs served by the AU/Micro Base station.Troubleshooting 7 Uplink Traffic Problem Possible Cause Corrective Action Problem and Indication High SNR. If the Burst Error Rate at the expected Rate is too high: a Perform Spectrum measurements with the ODU disconnected and check for interferences on the Channel's frequency. check the radio planning. replace the IDU and recheck. try to use the other channel. If the problem does not exist any more. If the problem did not disappear.

If the Burst Error Rate at the expected Rate is too high: a Perform Spectrum measurements with the ODU disconnected and check for interferences on the Channel's frequency. the problem is in the Channel. Perform Spectrum measurements on the Channel's new frequency. Possible Cause AU/Micro Base Station (IDU or ODU) malfunction or strong interference Corrective Action 1 Reset the AU/Micro Base Station and check the rate. replace the IDU and recheck. Replace the AU-IDU/Micro Base Station and recheck. check the radio planning.Uplink Traffic Problem Problem and Indication Problem occurs in all SUs served by the ODU. try to switch between the channels. Change the Channel and SU frequencies (this can be done for a number of SUs only) and check the rate. replace the ODU and recheck. If the Burst Error Rate at the expected rate is low. If no interferences are exhibited. replace the ODU and recheck. If the problem remains in the SUs served by the same ODU. Verify (via counters) that uplink traffic runs through the AU/Micro Base Station. the problem occurs only in SUs served by one of the ODUs. If the rate has improved. If the problem did not disappear. If the problem exists now in SUs served by the other ODU. Note: select an available frequency as distant as possible from the original frequency. Synchronize the SU to the AU/Micro Base Station and check the rate. 2 3 4 b c d WMAX Troubleshooting Guide 9 . The AU/Micro Base Station is connected to two ODUs.

Try to identify source of interference. 10 WMAX Troubleshooting Guide . Verify (via counters) that uplink traffic runs through the AU/Micro Base Station. Check the radio planning. check the radio planning. Interference The Burst Error Rate at the expected Rate is low. Note: select aavailable frequencies as distant as possible from the original frequencies.Troubleshooting Problem and Indication The problem exists in all SUs served by the AU/Micro Base Station. two ODUs are connected to the AU/Micro Base Station and the problem occurs in SUs served by both ODUs. Corrective Action 1 Reset the AU/Micro Base Station and check the rate. Verify proper installation (including antenna alignment and distance from objects that may affect link quality) and when the installation is stable reset the SU. Perform Spectrum measurements on the Channels' new frequencies. SU-ODU problem Replace the SU-ODU and recheck. replace the AU-IDU/Micro Base Station and recheck. the Burst Error Rate at the expected Rate is too high. If the Burst Error Rate at the expected Rate is too high: a Perform Spectrum measurements with the ODUs disconnected and check for interferences on the Channel's frequencies. If feasible. In addition to the Rate being lower than expected. run downlink traffic for 5 minutes and recheck the rate. try a different frequency. Check for interferences using a spectrum analyzer. If the Burst Error Rate at the expected rate is low. Synchronize the SU to the AU/Micro Base Station and check the rate. Due to interference the SU cannot reach the expected rate. Possible Cause AU-IDU/Micro Base Station problem or high interference on both channels. replace the IDU and recheck.. 2 3 4 b c d Problem occurs in a single SU Multirate algorithm has not stabilized yet Installation problem Run downlink traffic via the unit for approximately 5 minutes and recheck the rate. Change the Channels and SUs frequencies (this can be done for a number of SUs only for each sector) and check the rate. If the rate has improved. If no interferences are exhibited.

SNR Table 8 Rate vs.5 8.5 6.3 5.8 21 WMAX Troubleshooting Guide 11 .2 15 19. SNR Table Rate 1 2 3 4 5 6 7 8 Modulation & Coding BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 QAM16 1/2 QAM16 3/4 QAM64 2/3 QAM64 3/4 Minimum SNR (dB) 3.9 12.Rate vs.