WMAX

Troubleshooting Guide

SW Version 2.5 September 2007 P/N 214693

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

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

.

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

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

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

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

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

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

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

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

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

5 6.5 8.3 5. 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.8 21 WMAX Troubleshooting Guide 11 .9 12. SNR Table 8 Rate vs.Rate vs.2 15 19.