WMAX

Troubleshooting Guide

SW Version 2.5 September 2007 P/N 214693

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

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

.

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

255. Verify that the Data Port Management Traffic parameter is Enabled.1. Check the IP parameters of Data port and try to ping it. When working in SNMP. Verify that the Data Port Status is Up.255. Verify that the Data Port Speed (100 Mbps or 1 Gbps) is compatible with the equipment connected. Verify that the IP address of the Management port is other than 0. Verify that the Data Port Management VLAN ID matches the Management VLAN ID of the connected equipment.0.0.0.Troubleshooting 2 NPU Data Port Connection Problem (No Management) Possible Cause Corrective Action 1 Verify that the Management port is disconnected. according to the connected equipment: Crossed when connected directly to a PC. verify that the IP address of the device connecting to the management system is configured as an Authorized Manager.3 with subnet mask 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).0. straight otherwise.1. 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 . If not. If connecting from a different subnet. The default is None (No VLAN). Problem and Indication No NPU Management Connection Troubleshoot via the Monitor program. and that the Read/Write communities configured in the Authorized Manager entry complies with the community strings used by the connected device. The default IP address is 1. check that the Ethernet cable is straight/crossed.

check that the PWR LED is on and that the ALRM LED is off.No Link (WLNK LED in SAU is off) Assumptions: The Base Station. The SU. Open a Telnet session to the SU. is up and running properly. At least 1 SU is associated with the applicable AU. 3 SU-ODU is disconnected 1 2 Wrong configuration at SU side 1 2 The antenna bearing is not optimal. Verify that the unit's configuration matches the AU configuration: Frequency. Bandwidth. WMAX Troubleshooting Guide 3 . Base Station ID parameters. Using SAU. AU and NPU use the latest SW version. Verify that the IDU-ODU cable is connected. including the applicable AU. 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). If connecting from a different subnet. Slowly align the antenna towards the Base Station while checking the SAU's LINK Bar LEDs. 4 SU Association Problem Possible Cause No power to the SU-IDU Problem and Indication No Association .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 location of the SU is according to the radio planning. Verify proper output power on the power cable connector. Verify that the unit is connected. Replace power cable. Verify that the Admin Status of relevant traps in the Trap Configuration menu is set to Enable. Severe NLOS conditions. Corrective Action 1 2 Check that the power cable is connected.

find the SU according to its MAC address and check that the Registration Status of the SU is "In Service". Change the SU Status to Permanent and configure services. at least one SU receives data. SU is Permanent: check that a service is configured for the SU's MAC address (in the Services menu). 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. Corrective Action Reset the SU to clear the table and retry the Telnet command to the unit. is set to a small number. Problem and Indication No Data Connectivity Assumptions: Link with the Base Station has been established. 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). refer to SU Service Fault reasons below. Check that the Service Fault Status of the SU is OK. SU Status Configuration problem 1 2 Ping the ISP's Local IP/Default Gateway. Base Station is up and running properly. configurable from the Base station's side. Otherwise. Verify that traffic to/from the data equipment is not rejected due to any of the active filtering rules.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. User's data equipment connectivity is OK. In the Base Station. 2 4 WMAX Troubleshooting Guide .

such as RT with CIR=12. packets must carry either 802. if configured to "Reject".if configured as PPPoE. If more than one Uplink/Downlink Upper Range is defined. 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. reconfigure a QoS with higher priority. Check the Service Type . If a low QoS (BE or NRT) is configured.000 Kbps. the cell might be overloaded with higher priority traffic. WMAX Troubleshooting Guide 5 . make sure you are sending PPPoE packets only.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. For testing purposes. 2 3 4 Service Profile configuration problem 1 2 Forwarding Rule configuration problem Check the "Unknown Forwarding Policy" configuration. Verify that the equipment behind the SU supports the correct marking. Priority Classifier configuration problem QoS Starvation problem Check the QoS configured for the Service.1p or DSCP marking. 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). Service Fault Status indicates a Loop problem A loop was detected on the Ethernet side of the SU. If Down. Verify that Operation Status is Up.1p (VLAN Traffic only) or DSCP (packets containing DSCP). 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). Verify that the Admin Status of the Subscriber is Enabled. the SU may not be associated (refer to the "SU Association Problem" above). matching the Service's definitions for VLAN List and Hybrid VLAN Mode. Make sure that the traffic you forward from the equipment connected to the SU is with the appropriate VLAN. Correct the loop problem and reset the SU from the Base Station's side. and repeat the test.

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

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

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

replace the ODU and recheck. Perform Spectrum measurements on the Channel's new frequency. If the problem did not disappear. If the problem exists now in SUs served by the other ODU. 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. try to switch between the channels. replace the IDU and recheck. Change the Channel and SU frequencies (this can be done for a number of SUs only) and check the rate. The AU/Micro Base Station is connected to two ODUs. If no interferences are exhibited. If the rate has improved. Synchronize the SU to the AU/Micro Base Station and check the rate.Uplink Traffic Problem Problem and Indication Problem occurs in all SUs served by the ODU. Note: select an available frequency as distant as possible from the original frequency. Replace the AU-IDU/Micro Base Station and recheck. 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. the problem occurs only in SUs served by one of the ODUs. replace the ODU and recheck. 2 3 4 b c d WMAX Troubleshooting Guide 9 . check the radio planning. the problem is in the Channel. If the Burst Error Rate at the expected rate is low. 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.

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

3 5.2 15 19.9 12. 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.5 8. SNR Table 8 Rate vs.5 6.Rate vs.8 21 WMAX Troubleshooting Guide 11 .