Troubleshooting Guide Alvarion BreezeMAX

BreezeMAX
Troubleshooting Guide
SW Version 2.5
June 2006
P/N 213940
Document History
Document History
No.
Topic
Description
Date Issued
General
This is the first release of this guide.
SW Version 2.0,
February 2006
Rates vs. SNR Table Section 8
Modulation and Coding column

updated
SW Version 2.0, Rev. B,

March 2006
General
Format Update
SW Version 2.5,
June 2006
ii
BreezeMAX Troubleshooting Guide
Legal Rights
Legal Rights
Copyright 2006 Alvarion Ltd. All rights reserved.
The material contained herein is proprietary, privileged, and confidential and
owned by Alvarion or its third party licensors. No disclosure thereof shall be made
to third parties without the express written permission of Alvarion Ltd.
Alvarion Ltd. reserves the right to alter the equipment specifications and
descriptions in this publication without prior notice. No part of this publication
shall be deemed to be part of any contract or warranty unless specifically
incorporated by reference into such contract or warranty.
Trade Names
Alvarion, BreezeCOM, WALKair, WALKnet, BreezeNET, BreezeACCESS,
BreezeMANAGE, BreezeLINK, BreezeConfig, BreezeMAX, AlvariSTAR,
BreezeLITE, MGW, eMGW, WAVEXpress, MicroXpress, WAVEXchange,
WAVEView, GSM Network in a Box and TurboWAVE and/or other products
and/or services referenced here in are either registered trademarks, trademarks
or service marks of Alvarion Ltd.
All other names are or may be the trademarks of their respective owners.
Statement of Conditions
The information contained in this manual is subject to change without notice.
Alvarion Ltd. shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance, or use of
this manual or equipment supplied with it.
Warranties and Disclaimers

All Alvarion Ltd. ("Alvarion") products purchased from Alvarion or through any of
Alvarion's authorized resellers are subject to the following warranty and product
liability terms and conditions.
Exclusive Warranty
(a) Alvarion warrants that the Product hardware it supplies and the tangible
media on which any software is installed, under normal use and conditions, will
be free from significant defects in materials and workmanship for a period of
fourteen (14) months from the date of shipment of a given Product to Purchaser
(the "Warranty Period"). Alvarion will, at its sole option and as Purchaser's sole
remedy, repair or replace any defective Product in accordance with Alvarion'
standard R&R procedure.
iii
Legal Rights
(b) With respect to the Firmware, Alvarion warrants the correct functionality
according to the attached documentation, for a period of fourteen (14) month from
invoice date (the "Warranty Period")". During the Warranty Period, Alvarion may
release to its Customers firmware updates, which include additional performance
improvements and/or bug fixes, upon availability (the "Warranty"). Bug fixes,
temporary patches and/or workarounds may be supplied as Firmware updates.
Additional hardware, if required, to install or use Firmware updates must be
purchased by the Customer. Alvarion will be obligated to support solely the two (2)
most recent Software major releases.
ALVARION SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING
AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT IN THE PRODUCT
DOES NOT EXIST OR WAS CAUSED BY PURCHASER'S OR ANY THIRD
PERSON'S MISUSE, NEGLIGENCE, IMPROPER INSTALLATION OR IMPROPER
TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR ANY OTHER CAUSE
BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE,
LIGHTNING OR OTHER HAZARD.
Disclaimer
(a) The Software is sold on an "AS IS" basis. Alvarion, its affiliates or its licensors
MAKE NO WARRANTIES, WHATSOEVER, WHETHER EXPRESS OR IMPLIED,
WITH RESPECT TO THE SOFTWARE AND THE ACCOMPANYING
DOCUMENTATION. ALVARION SPECIFICALLY DISCLAIMS ALL IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE AND NON-INFRINGEMENT WITH RESPECT TO THE SOFTWARE.
UNITS OF PRODUCT (INCLUDING ALL THE SOFTWARE) DELIVERED TO
PURCHASER HEREUNDER ARE NOT FAULT-TOLERANT AND ARE NOT
DESIGNED, MANUFACTURED OR INTENDED FOR USE OR RESALE IN
APPLICATIONS WHERE THE FAILURE, MALFUNCTION OR INACCURACY OF
PRODUCTS CARRIES A RISK OF DEATH OR BODILY INJURY OR SEVERE
PHYSICAL OR ENVIRONMENTAL DAMAGE ("HIGH RISK ACTIVITIES"). HIGH
RISK ACTIVITIES MAY INCLUDE, BUT ARE NOT LIMITED TO, USE AS PART OF
ON-LINE CONTROL SYSTEMS IN HAZARDOUS ENVIRONMENTS REQUIRING
FAIL-SAFE PERFORMANCE, SUCH AS IN THE OPERATION OF NUCLEAR
FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION SYSTEMS, AIR
TRAFFIC CONTROL, LIFE SUPPORT MACHINES, WEAPONS SYSTEMS OR
OTHER APPLICATIONS REPRESENTING A SIMILAR DEGREE OF POTENTIAL
HAZARD. ALVARION SPECIFICALLY DISCLAIMS ANY EXPRESS OR IMPLIED
WARRANTY OF FITNESS FOR HIGH RISK ACTIVITIES.
(b) PURCHASER'S SOLE REMEDY FOR BREACH OF THE EXPRESS
WARRANTIES ABOVE SHALL BE REPLACEMENT OR REFUND OF THE
PURCHASE PRICE AS SPECIFIED ABOVE, AT ALVARION'S OPTION. TO THE
iv
Legal Rights
FULLEST EXTENT ALLOWED BY LAW, THE WARRANTIES AND REMEDIES SET

FORTH IN THIS AGREEMENT ARE EXCLUSIVE AND IN LIEU OF ALL OTHER
WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY
OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING BUT NOT
LIMITED TO WARRANTIES, TERMS OR CONDITIONS OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE, SATISFACTORY QUALITY,
CORRESPONDENCE WITH DESCRIPTION, NON-INFRINGEMENT, AND
ACCURACY OF INFORMATION GENERATED. ALL OF WHICH ARE EXPRESSLY
DISCLAIMED. ALVARION' WARRANTIES HEREIN RUN ONLY TO PURCHASER,
AND ARE NOT EXTENDED TO ANY THIRD PARTIES. ALVARION NEITHER
ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY
OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION,
MAINTENANCE OR USE OF ITS PRODUCTS.
Limitation of Liability
(a) ALVARION SHALL NOT BE LIABLE TO THE PURCHASER OR TO ANY THIRD
PARTY, FOR ANY LOSS OF PROFITS, LOSS OF USE, INTERRUPTION OF
BUSINESS OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR
CONSEQUENTIAL DAMAGES OF ANY KIND, WHETHER ARISING UNDER
BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY
OR OTHERWISE AND WHETHER BASED ON THIS AGREEMENT OR
OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
(b) TO THE EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL
THE LIABILITY FOR DAMAGES HEREUNDER OF ALVARION OR ITS EMPLOYEES
OR AGENTS EXCEED THE PURCHASE PRICE PAID FOR THE PRODUCT BY
PURCHASER, NOR SHALL THE AGGREGATE LIABILITY FOR DAMAGES TO ALL
PARTIES REGARDING ANY PRODUCT EXCEED THE PURCHASE PRICE PAID
FOR THAT PRODUCT BY THAT PARTY (EXCEPT IN THE CASE OF A BREACH OF
A PARTY'S CONFIDENTIALITY OBLIGATIONS).
Legal Rights
Important Notice
This user manual is delivered subject to the following conditions and restrictions:
This manual contains proprietary information belonging to Alvarion Ltd. Such
information is supplied solely for the purpose of assisting properly authorized
users of the respective Alvarion products.
No part of its contents may be used for any other purpose, disclosed to any
person or firm or reproduced by any means, electronic and mechanical,
without the express prior written permission of Alvarion Ltd.
The text and graphics are for the purpose of illustration and reference only.
The specifications on which they are based are subject to change without
notice.
The software described in this document is furnished under a license. The
software may be used or copied only in accordance with the terms of that
license.
Information in this document is subject to change without notice. Corporate
and individual names and data used in examples herein are fictitious unless
otherwise noted.
Alvarion Ltd. reserves the right to alter the equipment specifications and
descriptions in this publication without prior notice. No part of this
publication shall be deemed to be part of any contract or warranty unless
specifically incorporated by reference into such contract or warranty.
The information contained herein is merely descriptive in nature, and does not
constitute an offer for the sale of the product described herein.
Any changes or modifications of equipment, including opening of the
equipment not expressly approved by Alvarion Ltd. will void equipment
warranty and any repair thereafter shall be charged for. It could also void the
user's authority to operate the equipment.
vi
Contents
1
SU Ethernet Port Connection Problem (No Telnet) ...................... 1
NPU Data Port Connection Problem (No Management)................ 2
TRAPs Sending Problem ................................................................ 3
SU Association Problem ................................................................ 3
SU Data Connectivity Problem ...................................................... 4
Downlink Traffic Problem .............................................................. 6
Uplink Traffic Problem................................................................... 8
Rate vs. SNR Table ...................................................................... 11
SU Ethernet Port Connection Problem (No Telnet)
SU Ethernet Port Connection

Problem (No Telnet)
Problem and Indication
Possible Cause
Corrective Action
The Ethernet Integrity

Indicator (the yellow LED
embedded in the Ethernet
connector) is off, and/or the
Ethernet Activity Indicator
(the green embedded LED)
does not blink when there
should be traffic on the
Ethernet port.
Wrong type of Ethernet

cable
If connected directly to PC-use a straight cable.

Otherwise-use a crossed cable.
Faulty Ethernet cable
Replace cable
IDU-ODU cable problem.
Verify that the IDU-ODU cable is in order and

connected properly. Using SAU, verify that PWR
LED is on and ALRM LED is off.
The Ethernet Activity and/or

Integrity LEDs are on, but
no Telnet access and the
unit does not respond to
ping.
Wrong IP configuration
Make sure that the PC is on the same subnet as the

unit. The unit's IP address for management
purposes is 192.168.254.251, and the subnet mask
is 255.255.255.0.
Wrong Ethernet port

operation mode
Make sure that the speed and duplex settings in the

PC match the configuration in the unit. The default
operation mode is Auto Negotiation, and supported
speeds are 10/100 Mbps, Full or Half Duplex.
ARP table in the PC

contains a wrong MAC
address for the
192.168.254.251 IP
address (due to a recent
connection to another SU).
Perform arpV-d at the DOS command prompt to

clear the ARP table, and retry the Telnet command
to the unit.
Bridging table in SU is full

(expected when Number of
Supported Devices,
configurable from the Base
station's side, is set to a
small number.
Reset the SU to clear the table and retry the Telnet

command to the unit.
Troubleshooting
NPU Data Port Connection Problem

(No Management)

No NPU Management
Connection
Troubleshoot via the
Monitor program, using the
MON Serial port)
Possible Cause
Corrective Action
1
Verify that the Management port is

disconnected. Verify that the IP address of the
Management port is other than 0.0.0.0.
Check the IP parameters of Data port and try to

ping it. The default IP address is 1.1.1.3 with
subnet mask 255.255.255.0.
Verify that the Data Port Management Traffic

parameter is Enabled.
Verify that the Data Port Status is Up. If not,

check that the Ethernet cable is straight/crossed,
according to the connected equipment: Crossed
when connected directly to a PC, straight
otherwise.
Verify that the Data Port Speed (100 Mbps or 1

Gbps) is compatible with the equipment
connected.
Verify that the Data Port Management VLAN ID

matches the Management VLAN ID of the
connected equipment. The default is None (No
VLAN).
When working in SNMP, verify that the IP

address of the device connecting to the
management system is configured as an
Authorized Manager, and that the Read/Write
communities configured in the Authorized
Manager entry complies with the community
strings used by the connected device.
If connecting from a different subnet, 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).
Assumptions:
Management should be
done via the Data port (In
Band) ONLY
TRAPs Sending Problem
TRAPs Sending Problem
Possible Cause
Corrective Action
No Traps (Management is
OK)
Configuration problem
Verify that the Send Traps parameter in the

Authorized Manager entry for the managing device
is set to Enable.
Verify that the Admin Status of relevant traps in the
Trap Configuration menu is set to Enable.
If connecting from a different subnet, 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).
SU Association Problem
Possible Cause
Corrective Action
No Association - No Link
(WLNK LED in SAU is off)
No power to the SU-IDU
Check that the power cable is connected.
Verify proper output power on the power cable

connector.
Replace power cable.
Verify that the IDU-ODU cable is connected.
Using SAU, check that the PWR LED is on and

that the ALRM LED is off.
Open a Telnet session to the SU. Verify that the

unit is connected.
Verify that the unit's configuration matches the

AU configuration: Frequency, Bandwidth, Base
Station ID parameters.
Assumptions:
The Base Station, including
the applicable AU, is up and
running properly.
SU-ODU is disconnected
At least 1 SU is associated
with the applicable AU.
The SU, AU and NPU use
the latest SW version.
Wrong configuration at SU
side
The antenna bearing is not

optimal.
Slowly align the antenna towards the Base Station

while checking the SAU's LINK Bar LEDs.
Severe NLOS conditions.
Check that the location of the SU is according to the

radio planning.
Troubleshooting
SU Data Connectivity Problem
Possible Cause
Corrective Action
No Data Connectivity
Bridging table in SU is full

(expected when Number of
Supported Devices,
configurable from the Base
station's side, is set to a
small number.
Reset the SU to clear the table and retry the Telnet

command to the unit.
SU Status Configuration
problem
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".
Check that the Service Fault Status of the SU is

OK. Otherwise, refer to SU Service Fault
reasons below.
Check the Status of the SU:
Assumptions:
Link with the Base Station
has been established.
User's data equipment
connectivity is OK.
Base Station is up and
running properly, at least
one SU receives data.
Filtering configuration
problem
SU is Temporary and the Base station

Service Mode is Advanced: the SU will not
receive services. Change the SU Status to
Permanent and configure services.
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).
Verify that the MAC Address of the data

equipment is not included in the MAC Address
Deny List.
Verify that traffic to/from the data equipment is

not rejected due to any of the active filtering
rules.
SU Data Connectivity Problem
Possible Cause
Corrective Action
Service Configuration
Problem
Check proper Service configuration:
Service Profile
configuration problem
Verify that the Admin Status of the Service is

Enabled.
Verify that the Admin Status of the Subscriber is

Enabled.
Verify that Operation Status is Up. If Down, the

SU may not be associated (refer to the "SU
Association Problem" above).
Make sure that the traffic you forward from the

equipment connected to the SU is with the
appropriate VLAN, matching the Service's
definitions for VLAN List and Hybrid VLAN
Mode.
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).
Check the Service Type - if configured as

PPPoE, make sure you are sending PPPoE
packets only.
Forwarding Rule
Check the "Unknown Forwarding Policy"

configuration; if configured to "Reject", 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).
Priority Classifier
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.1p (VLAN
Traffic only) or DSCP (packets containing DSCP).
If more than one Uplink/Downlink Upper Range is
defined, packets must carry either 802.1p or DSCP
marking. Verify that the equipment behind the SU
supports the correct marking.
Service Fault Status

indicates a Loop problem
QoS Starvation problem
Check the QoS configured for the Service. If a low

QoS (BE or NRT) is configured, the cell might be
overloaded with higher priority traffic. For testing
purposes, reconfigure a QoS with higher priority,
such as RT with CIR=12,000 Kbps, and repeat the
test.
A loop was detected on the

Ethernet side of the SU.
Correct the loop problem and reset the SU from the

Base Station's side.
Troubleshooting
Possible Cause
Corrective Action
Service Fault Status

indicates Duplicate SU
Name problem.
The Name configured in the

SU is already in use by
another SU.
Configure a new, unique name for the SU and reset

it.
Downlink Traffic Problem
Possible Cause
Corrective Action
High SNR, Low Rate in

Downlink (SU)
Multirate algorithm has not

stabilized yet
Run downlink traffic via the unit for approximately 5

minutes and recheck the rate.
Check the Downlink SNR

and Rate of the SU. The
Rate is lower than expected
according to the Rate
vs.SNR table (below)
Installation problem
Verify proper installation (including antenna

alignment and distance from objects that may affect
link quality) and when the installation is stable reset
the SU, run downlink traffic for 5 minutes and
recheck the rate.
In addition to the Rate

being lower than expected,
the Burst Error Rate at the
expected Rate is too high.
Interference
Due to interference the SU cannot reach the

expected rate. Try to identify source of interference.
If feasible, try a different frequency (AU).
Check for interferences using a spectrum analyzer.
Check the radio planning.
The Burst Error Rate at the

expected Rate is low.
SU-ODU problem
Replace the SU-ODU and recheck.
The problem exists also in

neighboring SUs, a single
ODU is connected to the
AU.
AU problem or high
interference
Check the LEDs of the AU-ODU and

AU-IDU/Micro Base Station.
Try to use the second Channel:If the problem

remains, replace the ODU. If the problem still
exists, replace the IDU.
If the problem disappeared after switching to the
second channel, the problem is in the channel. It
is recommended to replace the IDU.
If feasible, try a different frequency.
Check for interferences using a spectrum

analyzer.
Downlink Traffic Problem
Possible Cause
Corrective Action

neighboring SUs, two
ODUs are connected to the
AU/Micro Base Station and
the problem occurs only in
SUs served by one of the
ODUs.
IDU or ODU problem, or

high interference
Check the LEDs of the AU-ODU and AU-IDU/Micro

Base Station.
Try to switch between the two ODUs (to identify a
possible problem in one of the channels). If the
same ODU remains problematic, replace the ODU.
If the problem is identified in the channel (exists now
in the SUs served by the other ODU) - replace the
AU-IDU.

neighboring SUs, two
the problem occurs in SUs
served by both ODUs..
AU-IDU/Micro Base Station

problem or high
interference on both
channels.
Check the LEDs of the AU-ODUs and AU-IDU/Micro

Base Station.
Replace the AU-IDU/Micro Base Station.
Troubleshooting
Uplink Traffic Problem
Possible Cause
Corrective Action
AU/Micro Base Station (IDU

or ODU) malfunction or
strong interference
Reset the AU and check the rate.
Verify (via counters) that uplink traffic runs

through the AU.
If the Burst Error Rate at the expected rate is

low, try to use the other channel. If the problem
remains, replace the ODU and recheck. If the
problem does not exist any more, the problem is
in the Channel. It is recommended to replace the
AU-IDU/Micro Base Station.
If the Burst Error Rate at the expected Rate is

too high:
High SNR, Low Rate in

Uplink (SU)
Check the Uplink SNR and
Rate of the SU. The Rate is
lower than expected
according to the Rate
vs.SNR table (below).
Problem occurs in all SUs
served by the AU/Micro
Base station, the AU/Micro
Base station is connected
to a single ODU.
Perform Spectrum measurements with the

ODU disconnected and check for
interferences on the Channel's frequency.
Change the Channel's and SU frequencies

(this can be done for a number of SUs only)
and check the rate. Note: select an available
frequency as distant as possible from the
original frequency. If the rate has improved,
check the radio planning.
Synchronize the SU to the AU/Micro Base

station and recheck the rate.
Perform Spectrum measurements on the

Channel's new frequency. If no interferences
are exhibited, replace the ODU and recheck.
If the problem did not disappear, replace the
IDU and recheck.
Uplink Traffic Problem
Possible Cause
Corrective Action
Problem occurs in all SUs

served by the ODU. The
AU/Micro Base Station is
connected to two ODUs,
the problem occurs only in
SUs served by one of the
ODUs.
AU/Micro Base Station (IDU

or ODU) malfunction or
strong interference
Reset the AU/Micro Base Station and check the

rate.

through the AU/Micro Base Station.

low, try to switch between the channels. If the
problem remains in the SUs served by the same
ODU, replace the ODU and recheck. If the
problem exists now in SUs served by the other
ODU, the problem is in the Channel. Replace the
AU-IDU/Micro Base Station and recheck.

too high:

ODU disconnected and check for
interferences on the Channel's frequency.
Change the Channel and SU frequencies

(this can be done for a number of SUs only)
and check the rate. Note: select an available
frequency as distant as possible from the
original frequency. If the rate has improved,
check the radio planning.

Station and check the rate.

Channel's new frequency. If no interferences
are exhibited, replace the ODU and recheck.
If the problem did not disappear, replace the
IDU and recheck.
Troubleshooting
Possible Cause
Corrective Action
The problem exists in all

SUs served by the
AU/Micro Base Station, two
the problem occurs in SUs
served by both ODUs..
AU-IDU/Micro Base Station

problem or high
interference on both
channels.
Reset the AU/Micro Base Station and check the

rate.

through the AU/Micro Base Station.

low, replace the AU-IDU/Micro Base Station and
recheck.

too high:
Problem occurs in a single

SU
In addition to the Rate

being lower than expected,
the Burst Error Rate at the
expected Rate is too high.

ODUs disconnected and check for
interferences on the Channel's frequencies.
Change the Channels and SUs frequencies

(this can be done for a number of SUs only
for each sector) and check the rate. Note:
select aavailable frequencies as distant as
possible from the original frequencies. If the
rate has improved, check the radio planning.

Station and check the rate.

Channels' new frequencies. If no
interferences are exhibited, replace the IDU
and recheck.
Multirate algorithm has not

stabilized yet
Run downlink traffic via the unit for approximately 5

minutes and recheck the rate.
Installation problem
Verify proper installation (including antenna

alignment and distance from objects that may affect
link quality) and when the installation is stable reset
the SU, run downlink traffic for 5 minutes and
recheck the rate.
Interference
Due to interference the SU cannot reach the

expected rate. Try to identify source of interference.
The Burst Error Rate at the

expected Rate is low.
10
SU-ODU problem
Replace the SU-ODU and recheck.
Rate vs. SNR Table
Rate vs. SNR Table

Rate
Modulation & Coding
Minimum SNR (dB)
BPSK 1/2
3.3
BPSK 3/4
5.5
QPSK 1/2
6.5
QPSK 3/4
8.9
QAM16 1/2
12.2
QAM16 3/4
15
QAM64 2/3
19.8
QAM64 3/4
21
11

Troubleshooting Guide Alvarion BreezeMAX

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Troubleshooting Guide Alvarion BreezeMAX

Uploaded by

Copyright:

Available Formats

BreezeMAX

This is the first release of this guide.

Rates vs. SNR Table Section 8

Modulation and Coding column

SW Version 2.0, Rev. B,

BreezeMAX Troubleshooting Guide

Warranties and Disclaimers

BreezeMAX Troubleshooting Guide

BreezeMAX Troubleshooting Guide

FULLEST EXTENT ALLOWED BY LAW, THE WARRANTIES AND REMEDIES SET

BreezeMAX Troubleshooting Guide

BreezeMAX Troubleshooting Guide

SU Ethernet Port Connection Problem (No Telnet) ...................... 1

NPU Data Port Connection Problem (No Management)................ 2

TRAPs Sending Problem ................................................................ 3

SU Association Problem ................................................................ 3

SU Data Connectivity Problem ...................................................... 4

Downlink Traffic Problem .............................................................. 6

Uplink Traffic Problem................................................................... 8

Rate vs. SNR Table ...................................................................... 11

SU Ethernet Port Connection Problem (No Telnet)

SU Ethernet Port Connection

Problem and Indication

The Ethernet Integrity

Wrong type of Ethernet

If connected directly to PC-use a straight cable.

Faulty Ethernet cable

IDU-ODU cable problem.

Verify that the IDU-ODU cable is in order and

The Ethernet Activity and/or

Make sure that the PC is on the same subnet as the

Wrong Ethernet port

Make sure that the speed and duplex settings in the

ARP table in the PC

Perform arpV-d at the DOS command prompt to

Bridging table in SU is full

Reset the SU to clear the table and retry the Telnet

BreezeMAX Troubleshooting Guide

NPU Data Port Connection Problem

Problem and Indication

Verify that the Management port is

Check the IP parameters of Data port and try to

Verify that the Data Port Management Traffic

Verify that the Data Port Status is Up. If not,

Verify that the Data Port Speed (100 Mbps or 1

Verify that the Data Port Management VLAN ID

When working in SNMP, verify that the IP

If connecting from a different subnet, verify that

BreezeMAX Troubleshooting Guide

TRAPs Sending Problem

TRAPs Sending Problem

Problem and Indication

Verify that the Send Traps parameter in the

Problem and Indication

No power to the SU-IDU

Check that the power cable is connected.

Verify proper output power on the power cable

Replace power cable.

Verify that the IDU-ODU cable is connected.

Using SAU, check that the PWR LED is on and

Open a Telnet session to the SU. Verify that the

Verify that the unit's configuration matches the

The antenna bearing is not

Slowly align the antenna towards the Base Station