FCC ID: HZB-MB83HP5 Access Point

 

 

 

 

 

802.11 a/b/g/n Mini-PCI module MB82HP RF Module Users Guide NOTICE:

The information in this document has been carefully reviewed and is believed to be accurate. Nonetheless, this document is subject to change without notice, and Proxim Wireless Corporation (Proxim) assumes no responsibility for any inaccuracies that may be contained in this document and makes no commitment to update or to keep current the contained information, or to notify a person or organization of any updates. Proxim reserves the right to attempt to supply the best product possible. Proxim dos not represent the products described herein are free from patent infringement or from any other third party right. Subject to change without notice. PROXIM MAKES NO WARRANTIES OF ANY KIND WITH REGARD TO THE CONTENT OF THIS DOCUMENT, IN NO EVENT SHALL PROXIM BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL SPECULATORY OR CONCEQUENTIAL DAMAGES ARISING FROM THE USE OR INABILITY TO USE THIS PRODUCT OR DOCUMENTATION, EVEN IF ADVISED OF THE POSIBILITY OF SUCH DAMAGES. IN PARTICULAR PROXIM SHALL NOT HAVE LIABILITY FOR ANY HARDWARE, SOFTWARE, OR DATA TRANSMITTED OR OTHERVWISE USED WITH THE PRODUCT, INCLUDING THE COST OF REPARING, REPLACING, INTERGATING, INSTALLING OR RECOVERING SUCH HARDWARE, SOFTWARE OR DATA. This document use information provided by Atheros Communications Inc. (Atheros), Atheros radio and chipsets user manuals, technical specifications, and Atheros regulatory manual. INTRODUCTION The Proxim MB82HP miniPCI module implements an IEEE 802.11a/b/g/n wireless LAN (WLAN) with Master function. MIMO operation is implemented using three transmit and three receive chains per the 802.11n standard. The device will be marketed under brand name: Proxim and model: MB82HP. This module may be installed in PC and host processor systems using approved external antennas. The module may be configured for 5GHz and 4.9GHz operation USING THE Web Server function provided by Atheros Communications Inc. Please, refer to Atheros driver User Manual instructions for details. The 2.4GHz radio frequency band will be turn off by firmware on this module. CONFIGURATION This section provide procedures for connecting and configuring the AP. Configuration can be performed either from a web browser accessing the build-in web server, or by entering commands using the command line interface (CLI). For detailed information on using the server refer to AP Web Server and for using CLI, refer to detailed operational guide provided by Atheros for the chipset. AP Initial Configuration Configure the AP for its Service Set Identifier (SSID) unique to the application. This configuration can be done either through a web browser with access to the build-in AP web server, or by commands using the command line interface (CLI). WEB Browser 3. Select the Access Point Web Server hotlink. 4. A dialog box appears requesting login authorization. When prompted, enter the following information to log in:

Login: Admin (case-sensitive) Password: 5up 5. Click OK to complete the login process. The 5GHz Statistics window will appear. 6. Select the Configuration hotlink from the navigation menu. The system Configuration window will appear. 7. Enter the SSID (name or address) for the AP in the SSID field. The SSID must be 132 characters in length. To configure a single SSID to have more then one AP in a single SSID, specify a unique System Name for each AP within that single SSID. Note that range of available channels will be automatically determined by factory settings. Note that the radio channel is specified using the IEEE 802.11a standard. For example, channel 48 is the equivalent of 5.240 GHz. The channel number is derived as:

1 2 Channel Frequency (in MHz) 5000MHz Channel Number =

Click Update to commit the changes. 5MHz After all configuration changes are complete, reboot the AP to enable them. To reboot AP, click on the REBOOT AP button that appears. For detailed information on using the server refer to AP Web Server and for using CLI refer to AP Command-Line Interface provided in Appendixes A and B of Atheros MPCI Module Users Guide. FCC Requirements for Operation in the United States This device is restricted to indoor use only due to its operation in 5150 to 5250 MHz frequency ranges in accordance with latest FCC regulations. Host systems using Porxim Firmware with this 802.11a/b/g/n 3x3 MIMO nimiPCI module to be sold in the United States do not have country code settings and are factory configured to only operate on the channels allowed by the FCC. Master devices with a US SKU that contain the 802.11a/b/g/n Radio module are limited to the following operating channels:

36 64 (5180 to 5320 MHz) in the 5150 to 5250 MHz band 149 165 (5745 to 5825 MHz) in the 5725 to 5825 MHz band 4940 to 4990MHz band.

FCC Statement:

Federal Communication Commission Interference Statement This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures:

Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the users authority to operate this equipment. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This device and its antenna(s) must not be co-located or operation in conjunction with any other antenna or transmitter. This device is going to be operated in 5.15~5.25GHz frequency range, it is restricted in indoor environment only. FCC NOTICE: To comply with FCC part 15 rules in the United States, the system must be professionally installed to ensure compliance with the Part 15 certification. It is the responsibility of the operator and professional installer to ensure that only certified systems are deployed in the United States. The use of the system in any other combination (such as co-located antennas transmitting the same information) is expressly forbidden. The module (Model number: MB82HP) is Limited Module Approval and only limited to install to the AP (Proxim / MP 8200). IMPORTANT NOTE:

FCC Radiation Exposure Statement:

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 50cm between the radiator & your body. IMPORTANT NOTE:

This module is intended for OEM integrator. The OEM integrator is still responsible for the FCC compliance requirement of the end product, which integrates this module. 50cm minimum distance has to be able to be maintained between the antenna and the users for the host this module is integrated into. Under such configuration, the FCC radiation exposure limits set forth for an population/uncontrolled environment can be satisfied. Any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. USERS MANUAL OF THE END PRODUCT:

In the users manual of the end product, the end user has to be informed to keep at least 50cm separation with the antenna while this end product is installed and operated. The end user has to be informed that the FCC radio-frequency exposure guidelines for an uncontrolled environment can be satisfied. The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. LABEL OF THE END PRODUCT:

The final end product must be labeled in a visible area with the following " Contains TX FCC ID:

HZB-MB83HP5 ". The FCC part 15.19 statement below has to also be available on the label:

This device complies with Part 15 of FCC rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference and (2) this device must accept any interference received, including interference that may cause undesired operation. IC Statement This Class B digital apparatus complies with Canadian ICES-003. Cet appareil numrique de la classe B conforme la norme NMB-003 du Canada. This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. This device and its antenna(s) must not be co-located or operation in conjunction with any other antenna or transmitter. Cet appareil et son antenne (s) ne doit pas tre co-localiss ou fonctionnement en association avec une autre antenne ou transmetteur. Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication. Conformment la rglementation d'Industrie Canada, le prsent metteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou infrieur) approuv pour l'metteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas l'intensit ncessaire l'tablissement d'une communication satisfaisante. This radio transmitter (identify the device by certification number, or model number if Category II) has been approved by Industry Canada to operate with the antenna types listed below with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Le prsent metteur radio (identifier le dispositif par son numro de certification ou son numro de modle s'il fait partie du matriel de catgorie I) a t approuv par Industrie Canada pour fonctionner avec les types d'antenne numrs ci-dessous et ayant un gain admissible maximal et l'impdance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour l'exploitation de l'metteur. The device could automatically discontinue transmission in case of absence of information to transmit, or operational failure. Note that this is not intended to prohibit transmission of control or signaling information or the use of repetitive codes where required by the technology. Le dispositif pourrait automatiquement cesser d'mettre en cas d'absence d'informations transmettre, ou une dfaillance oprationnelle. Notez que ce n'est pas l'intention d'interdire la transmission des informations de contrle ou de signalisation ou l'utilisation de codes rptitifs lorsque requis par la technologie. This device is going to be operated in 5.15~5.25GHz frequency range, it is restricted in indoor environment only. The module (Model number: MB82HP) is Limited Module Approval and only limited to install to the AP (Proxim / MP 8200). IMPORTANT NOTE:

IC Radiation Exposure Statement:

This equipment complies with IC RSS-102 radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 50cm between the radiator & your body. Declaracin de exposicin a la radiacin de Canada: Este equipo cumple con los lmites de exposicin a la radiacin de la IC establecidos para un ambiente no controlado. Este equipo se debe instalar y operar con una distancia mnima de 50 cm entre el radiador y su cuerpo. IMPORTANT NOTE:

This module is intended for OEM integrator. The OEM integrator is still responsible for the IC compliance requirement of the end product, which integrates this module. 50cm minimum distance has to be able to be maintained between the antenna and the users for the host this module is integrated into. Under such configuration, the IC RSS-102 radiation exposure limits set forth for an population/uncontrolled environment can be satisfied. Any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. USERS MANUAL OF THE END PRODUCT:

In the users manual of the end product, the end user has to be informed to keep at least 50cm separation with the antenna while this end product is installed and operated. The end user has to be informed that the IC radio-frequency exposure guidelines for an uncontrolled environment can be satisfied. The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. IC statement is required to be available in the users manual: This Class B digital apparatus complies with Canadian ICES-003. Operation is subject to the following two conditions: (1) this device may not cause harmful interference and (2) this device must accept any interference received, including interference that may cause undesired operation. LABEL OF THE END PRODUCT:

The final end product must be labeled in a visible area with the following " Contains TX IC:

1856A-MB83HP5 ". Antenna information:

Brand MARS MARS ModelName MAWA5530 MAWB5520 Antenna Type Panel Sector SmartAnt USI05220170 Dipole Chain 1/2/3 1/2/3 1/2/3 MARS MAWO5510NH Ommi 1/2/3 CommScope PX3F52N7A MARS MARS MAWA56DP25N MAWD56DP16 Sector Dish Panel 1/3 1/3 1/3 Attenuator

(dBi) 20 10

20 20 10 Connector NType,Female NType,Female RPSMAPlug NType,Female/

NType,Male

(optional) NFemale NType,Female NType,Female Antenna Gain 30 20 Cable loss 2 2 5 10 34 23.5 16 1 2 2 2 2 TestAnt Gain(dBi) 8 8 4 8 12 1.5 4 Ant. 1 2 3 4 5 6 7

 

 

Advanced Configuration Given below is the table which explains Protocol Filter parameters and the method to configure the configurable parameter(s):

Parameter Filtering Control This parameter is used to apply filters on the devices interface. The filtering can be applied on any of the following interfaces:

Description Filtering Type enabled to apply filters. Ethernet: Packets are examined at the Ethernet interface.

: In addition to enabling Filtering Control, the Global Filter Flag should also be By default, the Filtering Control is set to Disable, meaning which Protocol Filters are disabled on all the interfaces. This parameter specifies the action to be performed on the data packets whose protocol type is not defined in the protocol filter table (this table contains a list of default protocols supported by the device and the protocols defined by the user), or whose Entry Status is in Disable state. The available filtering types are:

Wireless: Packets are examined at the Wireless interface. All Interfaces: Packets are examined at both Ethernet and Wireless interface. Passthru: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are allowed through the configured interface. Block: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are blocked. After configuring the required parameters, click OK and then COMMIT. 5.10.1.1 Protocol Filter Table The Protocol Filter table displays a list of default protocols supported by the device and the protocols created by the user. By default, the system generates 19 protocols entries. Each of the Protocol contains the following information:

Parameter Protocol Name Protocol Number Description Represents the Protocol name. The system throws an error when you try to edit the name of a default protocol. Represents the Protocol number. The value is of 4 digit hexadecimal format. The system throws an error when you try to edit the Protocol number of a default protocol. Filter Status The supported filter status are, Passthru: When the filter status is set to Passthru and entry status is Enable, all packets whose protocol matches with the given protocol number are forwarded on the configured interface. Block: When the filter status is set to Block and entry status is Enable, all packets whose protocol matches with the given protocol number are dropped on the configured interface. By default, the status is set to Block. Tsunami 800 & 8000 Series - Software Management Guide 171 Entry Status Set the entry status as either Enable, Disable or Delete. Advanced Configuration

: System-defined default protocols cannot be deleted. Enable: Enables filter status on a protocol. Disable: Disables filter status on a protocol. Delete: Deletes a protocol entry from the Protocol Filter Table. 5.10.1.2 Add User-defined Protocols to the Filter Table To add user-defined protocols to the Protocol Filter Table, click Add in the Protocol Filter screen. The Protocol Filter Add Row screen appears. Enter details for all the required parameters and click Add. Figure 5-95 Add User-defined Protocols

: The maximum number of Protocol Filters that can be added to the table are 64, out of which 19 are default entries. 5.10.2 Static MAC Address Filter The Static MAC Address filter optimizes the performance of a wireless (and wired) network. With this feature configured, the device can block traffic between wired devices and wireless devices based on the MAC address. Each MAC Address or Mask is comprised of 12 hexadecimal digits (0-9, A-F) that correspond to a 48-bit identifier. (Each hexadecimal digit represents 4 bits (0 or 1)). Taken together, a MAC Address/Mask pair specifies an address or a range of MAC addresses that the device will look for when examining packets. The device uses Boolean logic to perform an AND operation between the MAC Address and the Mask at the bit level. A Mask of 00:00:00:00:00:00 corresponds to all MAC addresses, and a Mask of FF:FF:FF:FF:FF:FF applies only to the specified MAC Address. For example, if the MAC Address is 00:20:A6:12:54:C3 and the Mask is FF:FF:FF:00:00:00, the device will examine the source and destination addresses of each packet looking for any MAC address starting with 00:20:A6. If the Mask is FF:FF:FF:FF:FF:FF, the device will only look for the specific MAC address (in this case, 00:20:A6:12:54:C3). You can configure the Static MAC Address Filter parameters depending on the following scenarios:

To prevent all traffic from a specific wired MAC address from being forwarded to the wireless network, configure only the Wired MAC Address and Wired Mask (leave the Wireless MAC Address and Wireless Mask set to all zeros). Tsunami 800 & 8000 Series - Software Management Guide 172 Advanced Configuration To prevent all traffic from a specific wireless MAC address from being forwarded to the wired network, configure only the Wireless MAC address and Wireless Mask (leave the Wired MAC Address and Wired Mask set to all zeros). To prevent traffic between a specific wired MAC address and a specific wireless MAC address, configure all four parameters. Configure the wired and wireless MAC address and set the wired and wireless mask to all Fs. To prevent all traffic from a specific wired Group MAC address from being forwarded to the wireless network, configure only the Wired MAC Address and Wired Mask (leave the Wireless MAC Address and Wireless Mask set to all zeros). To prevent all traffic from a specific wireless Group MAC address from being forwarded to the wired network, configure only the Wireless MAC address and Wireless Mask (leave the Wired MAC Address and Wired Mask set to all zeros). To prevent traffic between a specific wired Group MAC address and a specific wireless Group MAC address, configure all four parameters. Configure the wired and wireless MAC address and set the wired and wireless mask to all Fs. Static MAC Filter Examples Consider a network that contains a wired PC and three wireless PCs. The MAC addresses for each PCs are as follows:

MAC Address of the wired PC: 00:40:F4:1C:DB:6A MAC Address of the wireless PC1: 00:02:2D:51:94:E4 MAC Address of the wireless PC2: 00:02:2D:51:32:12 MAC Address of the wireless PC3: 00:20:A6:12:4E:38 Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:02:2D:51:94:E4 Wireless Mask: FF:FF:FF:FF:FF:FF Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:02:2D:51:94:E4 Wireless Mask: FF:FF:FF:00:00:00 Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:00:00:00:00:00 Wireless Mask: 00:00:00:00:00:00 5.10.2.0.1 Prevent two specific PCs from communicating Configure the following settings to prevent the wired PC and wireless PC1 from communicating:

Result: Traffic between the wired PC and wireless PC1 is blocked. wireless PC2 and PC3 can still communicate with the wired PC. 5.10.2.0.2 Prevent multiple Wireless PCs from communicating with a single wired PC Configure the following settings to prevent wireless PC1 and PC2 from communicating with the wired PC:

Result: When a logical AND is performed on the Wireless MAC Address and Wireless Mask, the result corresponds to any MAC address beginning with the 00:20:2D prefix. Since wireless PC1 and wireless PC2 share the same prefix (00:02:2D), traffic between the wired Server and wireless PC1 and PC2 is blocked. Wireless PC3 can still communicate with the wired PC since it has a different prefix (00:20:A6). 5.10.2.0.3 Prevent all wireless PCs from communicating with a single wired PC Configure the following settings to prevent wired PC from communicating with all three wireless PCs:

Tsunami 800 & 8000 Series - Software Management Guide 173 Result: The device blocks all traffic between the wired PC and all wireless PCs. 5.10.2.0.4 Prevent a wireless PC from communicating with the wired network Configure the following settings to prevent wireless PC3 from communicating with any device on the Ethernet:

Advanced Configuration Result: The device blocks all traffic between wireless PC3 and the Ethernet network. Wired MAC Address: 00:00:00:00:00:00 Wired Mask: 00:00:00:00:00:00 Wireless MAC Address: 00:20:A6:12:4E:38 Wireless Mask: FF:FF:FF:FF:FF:FF 5.10.2.1 Static MAC Address Filter Configuration To configure Static MAC Filter parameters, navigate to ADVANCED CONFIGURATION > Filtering > Static MAC Address Filter. The Static MAC Address Filter screen appears:

Click Add in the Static MAC Address Filter screen. The Static MAC Address Filter Add Row screen appears. Figure 5-96 Static MAC Address Filter Figure 5-97 Static MAC Address Filter Add Entry Tsunami 800 & 8000 Series - Software Management Guide 174 Given below is the table which explains Static MAC Address Filter parameters and the method to configure the configurable parameter(s):

Advanced Configuration Parameter Wired MAC Address Specifies the MAC address of the device on the wired network that is restricted from communicating with a device on the wireless network. Description Wired MAC Mask Specifies the range of MAC address to which this filter is to be applied. Wireless MAC address Specifies the MAC address of the device on the wireless network that is restricted from communicating with a device on the wired network. Wireless MAC Mask Specifies the range of MAC address to which this filter is to be applied. Comment Status Specifies the comment associated with Static MAC Filter table entry. Specifies the status of the newly created filter. Click Add and then COMMIT.

You can configure a maximum of 200 MAC address filters. The Wired MAC address and the Wireless MAC address should be a unicast MAC address. The MAC Address or Mask includes 12 hexadecimal digits (each hexadecimal equals to 4 bits containing 0 or 1) which is equivalent to 48 bit identifier. 5.10.3 Advanced Filtering With Advanced Filtering, you can filter pre-defined IP Protocol traffic on the network. By default, 5 IP protocols are pre-defined and based on the configuration they can be blocked or allowed to enter the network. To apply filters on the IP protocols, navigate to ADVANCED CONFIGURATION > Filtering > Advanced Filtering. The Advanced Filtering screen appears:

Figure 5-98 Advanced Filtering Tsunami 800 & 8000 Series - Software Management Guide 175 Advanced Configuration The Advanced Filtering table contains a list of 5 pre-defined protocols on which Advanced Filtering is applied. The following table explains the Filtering table parameters:

Parameter Protocol Name Represents the protocol name. By default, Advanced Filtering is supported on the following 5 default protocols:

Description Deny IPX RIP Deny IPX LSP Deny IPX SAP Deny IP Multicasts Deny IP Broadcasts Ethernet to wireless Wireless to ethernet Both Represents the direction of an IP Protocol traffic that needs to be filtered. The directions that can be filtered are, The filters are applied on the IP protocol only when Entry Status is enabled. Direction Entry Status

5.10.3.1 Edit Advanced Filtering Table Entries The Advanced Filtering table contains a maximum of 5 pre-defined IP protocols. User-defined IP protocols cannot be added to the Advanced Filtering table. To edit Advanced Filtering table protocols, click Edit in the Advanced Filtering screen. The Advanced Filtering - Edit Entries screen appears. Tsunami 800 & 8000 Series - Software Management Guide 176 Advanced Configuration Modify the IP protocol traffic direction that needs to be filtered, and the filtering status for the desired IP Protocol. Figure 5-99 Advance Filtering- Edit Entries Next click OK and then COMMIT. 5.10.4 TCP/UDP Port Filter TCP/UDP Port Filtering allows you to enable or disable Transmission Control Protocol (TCP) ports and User Datagram Port

(UDP) ports on network devices. A user specifies a Protocol Name, Port Number, Port Type (TCP, UDP, or TCP/UDP), and filtering interfaces (Only Wireless, Only Ethernet or Both) in order to block access to services such as Telnet and FTP, and traffic such as NETBIOS and HTTP. To apply filters on TCP/UDP Port, navigate to ADVANCED CONFIGURATION > Filtering > TCP/UDP Port Filter. The TCP/UDP Port Filter screen appears. Tsunami 800 & 8000 Series - Software Management Guide 177 Advanced Configuration The Filter Control parameters determines if filter has to be applied or not on a TCP/UDP Port. By default, it is disabled. To apply filters, select Enable and click OK. Figure 5-100 TCP/UDP Port Filter 5.10.4.1 TCP/UDP Port Filter Table The TCP/UDP Port Filter table displays a list of default TCP/UDP ports and user-defined ports which can be enabled or disabled as desired. By default, the device support 7 default TCP/UDP port filter entries. Parameter Protocol Name Port Number Description Represents the name of the service/protocol. Please note that the system throws an error when an attempt is made to edit the default service/protocol name. Represents the destination port number. Please note that the system throws an error when an attempt is made to edit the port number. Port Type Represents the port type (TCP, UDP, Both). Filter Interface Represents the interface on which the filter is applied. The supported interfaces are, All Interfaces Only Ethernet Only Wireless Tsunami 800 & 8000 Series - Software Management Guide 178 Parameter Description Entry Status Set the entry status as either Enable, Disable or Delete. Advanced Configuration attempt to delete default entries, the device throws an error. Enable: Filter is applied and filters the packet based on the Port number and port type. Disable: No filter is applied. Delete: Allows to delete only user-defined TCP/UDP port filter entry. When you Entry Status (Enable/Disable) Port Number Port Type Filter Interface Ethernet Enable UDP If you have configured any user-defined protocols then click OK and then COMMIT. For example, a device with the following configuration would discard frames received on its Ethernet interface with a UDP destination port number of 137, effectively blocking NETBIOS Name Service packets. Please note that even the Filtering Control should be enabled to apply the filter. Protocol Name NETBIOS Name Service 137 5.10.4.2 Adding User-defined TCP/UDP Port Filter Entries To add user-defined TCP/UDP port filter entries to the table, click Add in the TCP / UDP Port Filter screen. The TCP/UDP Port Filter Add Row screen appears:

Figure 5-101 Add User-defined TCP/UDP Protocols Provide details for all the parameters and click Add. To apply the configured parameters, click COMMIT.

5.10.5 Storm Threshold Filter The TCP/UDP filtering operation is allowed only when the Global Flag and Filter Control options are enabled. You can add a maximum of 64 TCP/UDP Port Filter entries to the table, out of which 7 are default entries. The Storm Threshold Filter restricts the excessive inbound multicast or broadcast traffic on layer two interfaces. This protects against broadcast storms resulting from spanning tree misconfiguration. A broadcast or multicast filtering mechanism needs to be enabled so that a large percentage of the wireless link remains available to the connected mobile terminals. Tsunami 800 & 8000 Series - Software Management Guide 179 To configure Storm Threshold Filter, navigate to ADVANCED CONFIGURATION > Filtering > Storm Threshold Filter. The Storm Threshold Filter screen appears. This screen contains information about the threshold values per second of the multicast and broadcast packets that can be processed for the interface(s) present in the device. Advanced Configuration Given below is the table which explains Storm Threshold Filter parameters and the method to configure the configurable parameter(s):

Figure 5-102 Storm Threshold Filter Parameter Interface Multicast Threshold Broadcast Threshold Description Allows to configure the type of interface on which filtering has to be applied. The Storm Threshold filter can be used to filter the traffic on two types of interfaces: Ethernet or Wireless. By default, Storm Threshold filtering is disabled on both Ethernet and Wireless interfaces. Allows to configure the threshold value of the multicast packets to be processed for the Ethernet or Wireless interface. Packets more than threshold value are dropped. If threshold value for multicast packets is set to '0', filtering is disabled. The default Multicast Threshold value is 0 per second. Allows to configure the threshold value of the broadcast packets to be processed for the Ethernet or Wireless interface. Packets more than threshold value are dropped. If threshold value for broadcast packets is set to '0', filtering is disabled. The default Broadcast Threshold value is 0 per second. After configuring the required parameters, click OK and then COMMIT. 5.10.6 WORP Intra Cell Blocking

: Intra Cell Blocking is applicable only to a BSU in Bridge Mode only. The WORP Intra Cell Blocking feature restricts traffic between SUs which are registered to the same BSU. The two potential reasons to isolate traffic among the SUs are:

To provide better security by isolating the traffic from one SU to another in a public space. To block unwanted traffic between SUs to prevent this traffic from using bandwidth. Tsunami 800 & 8000 Series - Software Management Guide 180 Advanced Configuration The user can form groups of SUs at the BSU which define the filtering criteria. All data to/from SUs belonging to the same group are bridged. If an SU does not belong to any group, the BSU discards the data. The user can also configure a Security Gateway to block traffic between SUs connected to different BSUs. All packets destined for SUs not connected to the same BSU are forwarded to the Security Gateway MAC address (configured under Security Gateway). The following rules apply to Intra Cell Blocking Groups:

an SU can be assigned to more than one group. an SU that has not been assigned to any group cannot communicate to any other SU connected to the same or different BSU. 5.10.6.0.1 Example of Intra-Cell Blocking Groups Assume that four Intra Cell Blocking Groups have been configured on a BSU. SUs 1 through 10 are registered to the BSU. Group1 Group2 Group3 Group4 SU1 SU4 SU5 SU2 SU3 SU8 SU6 SU1 SU7 SU8 SU9 SU10 In this example, SU1 belongs to two groups, Group 1 and Group 3. Therefore, packets from SU1 destined to SU4, SU5, SU6 and SU7 are not blocked. However, SU9 belongs to group 4 only and packets from SU9 are blocked unless sent to SU8 or SU 10. To configuring Intra-Cell Blocking parameters, navigate to ADVANCED CONFIGURATION > Filtering> WORP Intra Cell Blocking. The following screen appears:

Figure 5-103 Intra Cell Blocking Tsunami 800 & 8000 Series - Software Management Guide 181 This screen is classified into two categories: Intra Cell Blocking and Security Gateway. Given below are the configuration details. Advanced Configuration Parameter Description Intra Cell Blocking Status By default, Intra Cell Blocking is disabled on a BSU. Select Enable to enable the feature and then Click OK and then COMMIT. Security Gateway Status By default, Security Gateway is disabled on a BSU. Select Enable to enable the feature. MAC Address Represents the MAC address of the security gateway. This gateway routes the packets transmitted by the SU to the different BSUs to which it belongs. After configuring the required parameters, click OK and then COMMIT.

: Intra Cell Blocking is configurable only in Bridge mode. When you change the device from Bridge to Routing mode or vice-versa, Intra-Cell Blocking stops or starts working only after device reboot. 5.10.6.1 WORP Intra Cell Blocking Group Table The user can form groups of SUs at the BSU which define the filtering criteria. All data to/from SUs belonging to the same group are bridged. If an SU does not belong to any group, the BSU discards the data. By default, a BSU supports 16 groups and each group can contain a maximum of 240 SUs. Please note that a single SU can be a member of all the existing groups. To view and configure the Intra Cell Blocking Group table, navigate to ADVANCED CONFIGURATION > Filtering> WORP Intra Cell Blocking > Group Table. The WORP Intra Cell Blocking Group Table screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 182 Advanced Configuration Figure 5-104 WORP Intra Cell Blocking Group Table This table displays the list of groups. If the Entry Status for a group is set to Enable then BSU discards all the packets coming from SUs which are not members of that group. If set to Disable, then allows all the packets coming from SUs which are not the members of that group. If you have changed the Entry Status of a group, then click OK and then COMMIT. 5.10.6.2 WORP Intra Cell Blocking MAC Table The WORP Intra Cell Blocking MAC table allows to add SUs MAC address and assign them to the groups. You can add a maximum of 250 SUs to the table. To add SU to the table, navigate to ADVANCED CONFIGURATION > Filtering > WORP Intra Cell Blocking > MAC Table. The WORP Intra Cell Blocking MAC Table screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 183 Advanced Configuration 5.10.6.2.1 To add MAC addresses, click Add. The following screen appears. Figure 5-105 WORP Intra Cell Blocking MAC Table Figure 5-106 WORP Intra Cell Blocking MAC Table Add Entry Given below is the table which explains the WORP Intra Cell Blocking MAC Table entries and the method to configure the configurable parameter(s):

Parameter Description MAC Address Represents the MAC address of the SU. Group IDs 1 to 16 By default, a Group ID is disabled meaning which the SU is not a part of that group. To make it a part of that group, select Enable. Entry Status If SU is part of a group and its Entry Status is enabled then it can communicate with all the SUs belonging to that group. If Entry Status is disabled, then the communication is blocked. After adding the MAC address, click Add. Tsunami 800 & 8000 Series - Software Management Guide 184 Advanced Configuration To edit the existing MAC addresses, click Edit icon in the WORP Intra Cell Blocking MAC Table screen. Modify the parameters as desired in the WORP Intra Cell Blocking MAC Table Add Row screen and click OK and then COMMIT. In the WORP Intra Cell Blocking MAC Table, you can change the Entry Status as either Enable/Disable/Delete. Once the status is changed, click OK and then COMMIT. 5.11 DHCP Dynamic Host Configuration Protocol (DHCP) is a network protocol that enables a server to assign an IP address to the DHCP client from a defined range of IP addresses configured for a given network. Allocating IP addresses from a central location simplifies the process of configuring IP addresses to individual DHCP clients, and also avoids IP conflicts. 5.11.1 DHCP Pool DHCP Pool is a pool of defined IP addresses which enables a DHCP Server to dynamically pick IP address from the pool and assign it to the DHCP client. To configure a range of IP addresses in the DHCP Pool, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Server

> Pool. The DHCP Pool screen appears:

Each pool entry comprises the following tabulated information:

Figure 5-107 DHCP Pool Parameter Description Interface Specifies the interface type, that is, Bridge or Routing (Ethernet and Wireless). Start IP Address and End IP Address Specifies the start and end IP address of the addresses to be added to the pool. Delete Allows you to delete a pool entry.

: You can add a maximum of five pool entries to the table. A pool entry can be deleted but cannot be edited. 5.11.1.1 Adding a New Pool Entry To add a new entry to the DHCP Pool, click Add on the DHCP Pool screen. The following DHCP Pool Table Add Row screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 185 Advanced Configuration Figure 5-108 DHCP Pool Table Add Entry Enter the pool details and click Add. The entry will be updated in the DHCP pool table. To apply the configured changes, click COMMIT. 5.11.2 DHCP Server If DHCP Server is enabled, it picks automatically the IP addresses from the specific interface address pool and assigns them to the respective DHCP clients. DHCP Server feature is applicable to both Bridge and Routing Mode. In Routing mode, DHCP Server can be configured for each interface (Ethernet and Wireless) separately. Unless the DHCP Server functionality is enabled for an interface, the DHCP Server does not respond to the DHCP requests received on that interface. To configure the DHCP server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Server > Interface. The DHCP Server screen appears:

Figure 5-109 DHCP Server (Bridge Mode) Tsunami 800 & 8000 Series - Software Management Guide 186 Advanced Configuration Given below is the table which explains DHCP Server parameters and the method to configure the configurable parameter(s):

Figure 5-110 DHCP Server (Routing Mode) Parameter Description DHCP Server Status By default, DHCP Server is disabled on a device. To enable DHCP Server, select Enable. A DHCP Server can be enabled only when the following two conditions are satisfied:

1. Before enabling, atleast one interface should be enabled on which the DHCP Server has to run. 2. The DHCP pool table should have atleast one pool configured for that interface. Max Lease Time Specifies the maximum lease time for which the DHCP client can use the IP address provided by the DHCP Server. The value ranges from 3600 - 172800 seconds. DHCP Interface Table Interface Type Net Mask Specifies the interface for which the DHCP Server functionality shall be configured. That is Bridge or Ethernet/Wireless in case of Routing mode. Specifies the subnet mask to be sent to the DHCP client along with the assigned IP address. The netmask configured here should be greater than or equal to the netmask configured on the interface. Default Gateway Specifies the default gateway to be sent to the DHCP client along with the assigned IP Address. Default Gateway is a node that serves as an accessing point to another network. Primary DNS Specifies the primary DNS (Domain Name Server) IP address to be sent to the DHCP client. Secondary DNS Specifies the secondary DNS IP address to be sent to the DHCP client. Tsunami 800 & 8000 Series - Software Management Guide 187 Advanced Configuration Parameter Default Lease Time Description DHCP Server uses this option to specify the lease time it is willing to offer to the DHCP client over that interface. Once the lease time expires, the DHCP Server allocates a new IP address to the device. The Default Lease Time should be less than or equal to the configured Max Lease Time. Comment Specifies a note for the device administrator. Entry Status Used to Enable or Disable the DHCP Server functionality over the interface. After configuring the required parameters, click OK and then COMMIT. 5.11.3 DHCP Relay (Routing Mode only) The DHCP relay agent relays DHCP messages between the DHCP Clients and the configured DHCP Servers on different IP networks. You can configure a maximum of five DHCP Servers. There must be at least one DHCP Server configured in order to relay DHCP request.

: DHCP Relay Agent is configurable only in Routing mode. It cannot be enabled when NAT or DHCP Server is enabled. To view and configure DHCP Relay Server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Relay >

Relay Server. The DHCP Relay screen appears:

Figure 5-111 DHCP Relay By default, DHCP Relay is disabled on the device. To enable it, atleast one DHCP Server IP address should be configured. To add a DHCP Server to the Relay Server Table, click Add in the DHCP Relay screen. The DHCP Relay Server Add Row screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 188 Advanced Configuration Figure 5-112 DHCP Relay Server Add Entry Enter the DHCP Server IP Address and then click Add. After configuring the required parameters, click OK and then COMMIT.

: DHCP server is disabled automatically if DHCP Relay agent is enabled and vice-verse. Tsunami 800 & 8000 Series - Software Management Guide 189 5.12 IGMP Snooping Advanced Configuration

: IGMP Snooping is applicable only in Bridge Mode. Proxims Tsunami devices support Internet Group Management Protocol (IGMP) Snooping feature. With IGMP Snooping enabled on the device, multicast traffic is only forwarded to ports that are members of the specific multicast group. By forwarding the traffic only to the destined ports, reduces unnecessary load on devices to process packets. Explained below is the IGMP Snooping process with the help of a diagram:

The router forwards the IP multicast data to the BSU/End Point A. Figure 5-113 IGMP Snooping Process Lets say, with IGMP Snooping not enabled on the BSU/End Point A, the multicast data is transmitted over the wireless medium irrespective of whether the multicast group address is a member of the multicast group table maintained in each BSU/End Point A. With IGMP Snooping enabled, the BSU/End Point A transmits the data only when the multicast group address is a member of the multicast group table, else drops the packet. The SU/End Point B will receive the multicast data. Tsunami 800 & 8000 Series - Software Management Guide 190 Similarly, with IGMP Snooping not enabled on the SU/End Point B, the multicast data is transmitted irrespective of whether the multicast group address is a member of the multicast group table maintained in each SU/End Point B. With IGMP Snooping enabled, the SU/End Point B transmits the data to the host only when the multicast group address is a member of the multicast group table, else drops the packet. IGMP Snooping is of 2 kinds:

Advanced Configuration Active: Active IGMP Snooping listens to IGMP traffic and filters IGMP packets to reduce load on the multicast router. Passive: Passive IGMP Snooping simply listens to IGMP traffic and does not filter or interfere with IGMP.

To configure IGMP Snooping parameters, navigate to ADVANCED CONFIGURATION > IGMP Snooping. The following IGMP Snooping screen appears:

IGMP versions v1,v2 and v3 are supported. Tsunami devices supports only passive IGMP Snooping. The device can add a maximum of 64 Multicast groups in the Snooping table. Given below is the table which explains IGMP Snooping parameters and the method to configure the configurable parameter(s):

Figure 5-114 IGMP Snooping Parameter IGMP Snooping Status IGMP Membership Aging Timer IGMP Router Port Aging Timer IGMP Forced Flood Description By default, IGMP Snooping Status is disabled on the device, meaning which, the device transmits IP multicast traffic to all the ports. To forward the traffic only to the members of the specific multicast group, enable IGMP Snooping Status. Represents the time after which the IGMP multicast group age-outs or elapses. It ranges from 135 to 635 seconds. The default Aging Timer is 260 seconds. Represents the time after which the IGMP Router port age-outs or elapses. It ranges from 260 to 635 seconds. The default Aging Timer is 300 seconds. If you select Yes, all the unregistered IPv4 multicast traffic (with destination address which does not match any of the groups announced in earlier IGMP Membership reports) and IGMP Membership Reports will be flooded to all the ports. By default, IGMP Forced Flood is set to No. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 191 Management This chapter provides information on how to manage the device by using Web interface. It contains information on the following:

6.1 System

: Recommended characters for the name field are A-Z a-z 0-9 - _ = : . @ $ & and space. 6.1.1 System Information The System Information tab enables you to view and configure system specific information such as System Name, System Description, Contact Details of the person managing the device, and so on. To view and configure system specific Information, navigate to MANAGEMENT > System > Information. The System Information screen appears:

Figure 6-1 System Information Tsunami 800 & 8000 Series - Software Management Guide 192 Management Given below is the table which explains System parameters and the method to configure the configurable parameter(s):

Parameter System Up-Time This is a read-only parameter. It represents the operational time of the device since its last reboot. Description System Description This is a read-only parameter. It provides system description such as system name, firmware version and the latest firmware build supported. System Name Email Phone Number Location GPS Longitude GPS Latitude GPS Altitude For example: MP-8100-BSU-WD-v2.X.Y(Build No.) Represents the name assigned to the device. You can enter a system name of maximum 64 characters and should be unique across all devices in WORP network. Represents the email address of the person administering the device. You can enter an email address of minimum 6 and maximum 32 characters. Represents the phone number of the person administering the device. You can enter a phone number of minimum 6 and maximum 32 characters. Represents the location where the device is installed. You can enter the location name of minimum 0 and maximum 255 characters. Represents the longitude at which the device is installed. You can enter a longitude value of minimum 0 and maximum 255 characters. Represents the latitude at which the device is installed. You can enter a latitude value of minimum 0 and maximum 255 characters. Represents the altitude at which the device is installed. You can enter a altitude value of minimum 0 and maximum 255 characters. After configuring the required parameters, click OK and then COMMIT. 6.1.2 Inventory Management The Inventory Management tab provides inventory information about the device. To view inventory information, navigate to MANAGEMENT > System > Inventory Management. The System Inventory Management Table appears. Tsunami 800 & 8000 Series - Software Management Guide 193 Management Figure 6-2 An Example - Inventory Management By default, the components information is auto-generated by the device and is used only for reference purpose. Click Refresh, to view the updated system inventory management information. 6.1.3 Licensed Features Licensing is considered to be the most important component of an enterprise-class device which typically has a feature-based pricing model. It is also required to prevent the misuse and tampering of the device by a wide-variety of audience whose motives may be intentional or accidental. Licensed Features are, by default, set by the company. To view the licensed features set on the device, click MANAGEMENT > System > Licensed Features. The Licensed Features screen appears. Figure 6-3 Licensed Features Tsunami 800 & 8000 Series - Software Management Guide 194 Management Given below is the table which explains each of the parameters:

Parameter Description Product Description Description about the device. Number of Radios The number of radios the device supports. Number of Ethernet Interfaces Radio 1 Allowed Frequency Band Maximum Output Bandwidth Maximum Input Bandwidth The number of Ethernet interfaces supported by the device. The operational frequency band supported by the device radio. The maximum output bandwidth limit of the device. It is represented in mbps. The maximum input bandwidth limit of the device. It is represented in mbps.

: The Input and Output Bandwidth features are referred with respect to the wireless interface. Input bandwidth refers to the data received on the wireless interface and output bandwidth refers to the data sent out of the wireless interface. Maximum Aggregate Bandwidth The maximum cumulative bandwidth of the device, which is the sum of configured output and input bandwidths. Product Family Represents the product family of the device. Product Class Represents the product class of the device, which is either indoor or outdoor. Allowed Operational Modes of Radio1 Maximum SUs Allowed MAC address of the Device is Represents the operational mode of the device, that is, BSU/SU/End Point A/End Point B. The maximum number of SUs that a BSU supports. The MAC address of the device. 6.1.3.1 License Upgrade Procedure In order to get additional bandwidth, Upgrade the License by following the procedure given below:

To purchase a license upgrade, please contact your Proxim Sales Representative; to generate a unique license file for Upgrade the bandwidth using the license file(.bin extension) generated in the above step. For more details, refer Retrieve the license information (License Info file with .lic extension) from the device. For more details, refer 

 section.

your device, please refer to the Technical Note available on Proxim support site:

 section.

195 The File Management tab enables you to upgrade the firmware and configuration files onto the device, and retrieve configuration and log files from the device through Hypertext Transfer Protocol (HTTP) and Trivial File Transfer Protocol (TFTP). 6.2 File Management Tsunami 800 & 8000 Series - Software Management Guide

: The instructions listed above are based on the assumption that you are using the SolarWinds TFTP server; otherwise 6.2.1 TFTP Server Management A Trivial File Transfer Protocol (TFTP) server lets you transfer files across a network. By using TFTP, you can retrieve files from the device for backup or copying, and you can upgrade the firmware or the configuration files onto the device. You can

. You can also download the latest TFTP The upload or download directory is correctly set (the default directory is C:\TFTP-Root). The TFTP server is running during file upload and download. You can check the connectivity between the device and the TFTP server by pinging the device from the Personal Computer that hosts the TFTP server. The ping program should show replies from the device. The TFTP server should be configured to transmit and receive files (on the Security tab under File > Configure), with no automatic shutdown or time-out (on the Auto-Close tab).

While using TFTP server, ensure the following:

The required firmware file is present in the directory. download the SolarWinds TFTP server application from

software from SolarWinds Web site at the configuration may vary. 6.2.2 Text Based Configuration (TBC) File Management Text Based Configuration (TBC) file is a simple text file that holds device template configurations. The device supports the TBC file in XML format which can be edited in any XML or text editors. You can generate the TBC file from the CLI Session and manually edit the configurations and then load the edited TBC file to the device so that the edited configurations are applied onto the device. It differs mainly from the binary configuration file in terms of manual edition of configurations. The generated TBC file is a template which has only the default and modified configurations on the live CLI session. 6.2.2.1 Generating TBC File The TBC file is generated through CLI by executing generate command. While generating the TBC file from CLI, there is an option to generate it with or without all Management and Security Passwords. The management passwords include Network-Secret/Encryption-Key(s)/RADIUS-Shared-Secret. If included, these passwords become a part of the generated TBC file and are in a readable form. If excluded, all these passwords are not part of the generated TBC file. include CLI/WEB/SNMP passwords. The security passwords The commands used for the generation of TBC file are:

The generated TBC file contains, Default configurations

0 0 1 1 2 2 3 3 2 2 4 4 5 5 6 6 2 2 6 6 7 7 8 8

9 9

6 6

9 6

9

Any user-added or edited configurations on current live CLI session The generated Text Based Template Configuration file appears as shown below:

Tsunami 800 & 8000 Series - Software Management Guide 196 Management Figure 6-4 TBC File in xml Format 6.2.2.2 Editing the TBC File The TBC file can easily be opened and edited in any standard Text-Editors like Wordpad, MS-Word, Notepad++, Standard XML Editors. Proxim recommends XML Notepad 7 editor for editing the TBC file. You can modify any value between the double quotes() in the TBC file. It is recommended not to change the text outside the double quotes () or XML tags in the TBC file. Remove unchanged configurations from the TBC file before loading onto the device. Tsunami 800 & 8000 Series - Software Management Guide 197 Management 6.2.2.3 Loading the TBC file The TBC file can be loaded onto the device by using either SNMP, Web Interface or CLI. You can either use TFTP or HTTP to load the TBC file. By using Web Interface, you can load the TBC file by navigating to MANAGEMENT > File Management > Upgrade Configuration. To load the TBC file, it should be generated or downloaded onto the device. While loading the TBC file onto the device, any file name is accepted. Once loaded, the TBC file name is renamed to PXM-TBC.xml. If the TBC file does not contain correct XML syntax, the file will be discarded with DOM error and no configurations will be loaded. All duplicate values entered are considered as errors while loading and syslogs will be generated accordingly. Therefore, it is recommended to delete all unchanged parameters from the TBC file during its edition. Commit is required to retain the configurations across reboots after loading the TBC file.

: Both Commit and Reboot are required to accept the modifications done in the TBC File. Only reboot is required to reject the modifications. Loading the TBC file is allowed only once in an active device session (that is, if TBC file is loaded, reboot is required to apply all configurations or to load another TBC file). All configurations in the TBC file are loaded to the device irrespective of their default or modified or added configurations. Loading the TBC file takes approximately 10-20 seconds depending on the number of configurations added.

If you get any timeout errors while loading TBC file from SNMP interface, increase the time-out value to more than 30 seconds in the MIB Browser. 6.2.3 Upgrade Firmware You can update the device with the latest firmware either through HTTP or TFTP.

Remove any unmodified parameters from the TBC file, before loading it. Make sure the firmware being loaded is compatible to the device being upgraded. 1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > HTTP. To upgrade the firmware via HTTP, do the following:

6.2.3.1 Upgrade Firmware via HTTP In a point-to-multipoint network, it is recommended to upgrade the base station first and then the subscriber(s). In a point-to-point network, it is recommended to upgrade the End Point A first and then the End Point B. Tsunami 800 & 8000 Series - Software Management Guide 198 Management Figure 6-5 Upgrade Firmware - HTTP 2. In the HTTP screen, click Browse to select the latest firmware file from the desired location. Ensure that the file name does not contain any space or special characters. 3. Click Upgrade. 6.2.3.2 Upgrade Firmware via TFTP To upgrade the firmware via TFTP Server, do the following:

1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > TFTP. Figure 6-6 Upgrade Firmware - TFTP 2. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the latest firmware file (including the file extension) that has to be loaded onto the device in the File Name box. 4. To upgrade the device with new firmware click Upgrade and then reboot the device, or click Upgrade & Reboot. Tsunami 800 & 8000 Series - Software Management Guide 199

Management After upgrading the device with the new firmware, reboot the device; Otherwise the device will continue to run with the old firmware. It is recommended not to navigate away from the upgrade screen, while the upgrade is in progress. 6.2.4 Upgrade Configuration You can upgrade the device with the latest configuration files either through HTTP or TFTP.

: Make sure the configuration file being loaded into the device is compatible. That is, the configuration file being loaded should have been retrieved from a device of the same SKU. 6.2.4.1 Upgrade Configuration via HTTP To upgrade the configuration files by using HTTP, do the following:

1. Navigate to MANAGEMENT > File Management > Upgrade Configuration > HTTP. Figure 6-7 Upgrade Configuration - HTTP 2. 3. 4. 5. In the HTTP screen, click Browse to locate the configuration file. Select a Binary Configuration file or a Config Profile file, or a PXM-TBC.xml for Text Based Configuration file. Make sure that the file name does not contain any space or special characters. If you are upgrading the device with Binary Configuration file then click Upgrade and then reboot the device. If you are upgrading the device with Config Profile file then click Upgrade and then reboot the device. On upgrade, the device shall come up with the loaded profile. If the configuration profile is not compatible, then on reboot, the device will rollback to its old configuration. If you are upgrading the device with Text Based Configuration file then click Upgrade to upgrade the device with the config file and then click Load for loading the config file onto the device. Alternatively, you can perform both upgrade and load operation in one single step, by clicking Upgrade & Load. Tsunami 800 & 8000 Series - Software Management Guide 200 6.2.4.2 Upgrade Configuration via TFTP To upgrade the configuration files by using TFTP Server, do the following:

1. Navigate to MANAGEMENT > File Management > Update Configuration > TFTP. Management Figure 6-8 Upgrade Binary Configuration via TFTP 2. You can update the device with three types of configuration files: Binary, Text Based and Config Profile. To update the device with Binary Configuration file, select Binary Config. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Binary file (including the file extension) that has to be downloaded onto the device in the File Name box. 3. To update the device with Text Based Configuration files, select Text Based Config. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Text Based file (including the file extension) that has to be downloaded onto the device in the File Name box. Figure 6-9 Upgrade Text Based Configuration via TFTP Tsunami 800 & 8000 Series - Software Management Guide 201 4. To update the device with Configuration Profile files, select Config Profile. Management Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Config Profile file (including the file extension) that has to be downloaded onto the device in the File Name box. Figure 6-10 Upgrade Configuration Profile via TFTP 5. 6. 7. If you are upgrading the device with Binary Configuration file then click Upgrade and then reboot the device, or click Upgrade & Reboot. If you are upgrading the device with Text Based Configuration file, click Upload and then click Apply. If you are upgrading the device with Config profile file then click Upload and then reboot the device, or click Apply

& Reboot.

: It is recommended not to navigate away from the upgrade screen, while the upgrade is in progress. 6.2.5 Upgrade License 6.2.5.1 Upgrade License via HTTP more details. You can upgrade the license file on the device either through HTTP or TFTP. Refer ) To upgrade the license using HTTP, do the following:

1. Navigate to MANAGEMENT > File Management > Upgrade License > HTTP.

A

 section for Tsunami 800 & 8000 Series - Software Management Guide 202 Management Figure 6-11 Upgrade License via HTTP 2. In the HTTP screen, click Browse to locate the license upgrade(.bin) file to be loaded on the device. 3. Click Upgrade button to upgrade the license on the device and then reboot the device. 6.2.5.2 Upgrade License via TFTP To upgrade the license file using TFTP Server, do the following:

1. Navigate to MANAGEMENT > File Management > Update License > TFTP. Figure 6-12 Upgrade License via TFTP 2. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the file (including the file extension) that has to be loaded on the device, in the File Name box. 4. Click Upgrade button to upgrade the license on the device and then reboot the device.

It is applicable only to MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, and QB-825-LNK-50+ devices. Tsunami 800 & 8000 Series - Software Management Guide 203 Upgrade license can be done through CLI/Web Interface/SNMP. Management 6.2.6 Retrieve From Device The Retrieve From Device tab allows you to retrieve logs, config files, and license info from the device either through HTTP or TFTP. 6.2.6.1 Retrieve from Device via HTTP To retrieve files from the device by using HTTP, do the following:

1. Navigate to MANAGEMENT > File Management > Retrieve from Device > HTTP. Figure 6-13 Retrieve Files via HTTP 2. Select the type of file that you want to retrieve from the device from the File Type drop down box. The files may vary depending on your device. The File Types are:

a. Config b. Event Log c. Temperature Log d. Text Based Template Config e. Debug Log f. Config Profile g. License Info The Config Profile is used for replicating the configuration of a master device on to other similar devices by excluding the unique parameters like System information, IP configuration, Ethernet configuration, Wireless excluded. On selecting config profile type the following screen appears:

configuration based on the selection# By default, System Information and IP Configuration parameters are Tsunami 800 & 8000 Series - Software Management Guide 204 Management Figure 6-14 Retrieve Config Profile File via HTTP After excluding the unique parameters, click Create Profile for creating the profile and then click Retrieve. When the retrieved configuration profile file is loaded on target devices, the target devices will come up with configuration of the master device except the excluded parameters. The excluded parameters are retained as configured on the target device.

: Config Profile is applicable only to the compatible devices. 3. Click Retrieve. Based on the selected file, the following Download screen appears. 4. Right-click the Download link and select Save Target As or Save Link As to save the file to the desired location. Figure 6-15 Download Screen Tsunami 800 & 8000 Series - Software Management Guide 205 6.2.6.2 TFTP Retrieve To retrieve files from the device by using TFTP, do the following:

1. Navigate to MANAGEMENT > File Management > Retrieve from Device > TFTP. Management Figure 6-16 Retrieve Files via TFTP 2. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the file (including the file extension) that has to be retrieved from the device, in the File Name box. 4. Select the file type that you want to retrieve from the device, from the File Type drop down box. The file types are:

a. Config b. Event Log c. Temperature Log d. Text Based Template Config e. Debug Log f. Config Profile g. License Info The Config Profile is used for replicating the configuration of a master device on to other similar devices by excluding the unique parameters like System information, IP configuration, Ethernet configuration, Wireless configuration based on the selection. By default, System Information and IP Configuration parameters are excluded. On selecting config profile type the following screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 206 Management Figure 6-17 Retrieve Config Profile File via TFTP After excluding the unique parameters, click Create Profile for creating the profile and then click Retrieve. When the retrieved configuration profile file is loaded on the target devices, the target devices will come up with configuration of the master device except the excluded parameters. The excluded parameters are retained as configured on the target device. 5. Click Retrieve. The retrieved file can be found in the TFTP Server folder. cannot be retrieved. MP-825-SUR-50+, and QB-825-LNK-50+ devices. Config Profile is applicable only to the compatible devices. When the device is running with default factory settings, there is no Binary Configuration file present and hence it Similarly, the Text Based Template Configuration file does not exist if it is not generated from the CLI. You can retrieve Event Logs only when they are generated by the device. Retrieval of license info file (CLI/Web Interface/SNMP) is supported only by MP-820-BSU-100, MP-820-SUA-50+,

For more information on license upgrade, refer )

 sections.

 and '

A

To configure HTTP/HTTPS interface parameters, navigate to MANAGEMENT > Services > HTTP / HTTPS. The Services tab lets you configure the HTTP/HTTPS, Telnet/SSH and SNMP interface parameters. 6.3.1 HTTP/HTTPS 6.3 Services Tsunami 800 & 8000 Series - Software Management Guide 207 Management Given below is the table which explains HTTP/HTTPS parameters and the method to configure the configurable parameter(s). Figure 6-18 HTTP/HTTPS Parameter Admin Password Description By default, the Administrator password to access HTTP/HTTPS interface is public. For security reasons, it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.

: The following special characters are not allowed in the password:

- = \ ? / space Monitor Password The Administrator user has the privilege to change the Monitor user password. By default, the Monitor user password to access HTTP/HTTPS interface is public. For security reasons it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.

: The following special characters are not allowed in the password:

- = \ ? / space HTTP HTTP Port By default, a user can manage the device through Web Interface. To prevent access to the device through Web Interface, select Disable. Represents the HTTP port to manage the device through Web Interface. By default, the HTTP port is 80. Tsunami 800 & 8000 Series - Software Management Guide 208 Management Parameter HTTPS By default, a user can manage the device through Web Interface over secure socket Layer

(HTTPS). To prevent access to the device through HTTPS, select Disable. Description

: The password configuration for HTTPS is same as configured for HTTP. After configuring the required parameters, click OK, COMMIT and then REBOOT. 6.3.2 Telnet/SSH To configure Telnet/SSH interface parameters, navigate to MANAGEMENT > Services > Telnet / SSH. Figure 6-19 Telnet/SSH Tsunami 800 & 8000 Series - Software Management Guide 209 Given below is the table which explains Telnet/SSH parameters and the method to configure the configurable parameter(s):

Management Parameter Admin Password Description By default, the Administrator password to access Telnet/SSH interface is public. For security reasons, it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.

: The following special characters are not allowed in the password:

- = \ ? / space Monitor Password The Administrator user has the privilege to change the Monitor user password. By default, the Monitor user password to access Telnet/SSH interface is public. For security reasons it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.

: The following special characters are not allowed in the password:

- = \ ? / space Telnet By default, a user can manage the device through Telnet. To prevent access to the device through Telnet, select Disable. Telnet Port Represents the port to manage the device using Telnet. By default, the Telnet port is 23. Telnet Sessions SSH SSH Port SSH Sessions The number of Telnet sessions which controls the number of active Telnet connections. A user is restricted to configure a maximum of 3 Telnet sessions. By default, the number of Telnet sessions allowed is 2. By default, a user can manage the device through SSH. To prevent access to the device through SSH, select Disable. Represents the port to manage the device using Secure Shell. By default, the Secure Shell port is 22. Represents the number of SSH sessions which controls the number of active SSH connections. A user is restricted to configure a maximum of 3 SSH sessions. By default, the number of SSH sessions allowed is 1.

: The total number of CLI sessions allowed is 3, so the sum of Telnet and SSH sessions cannot be more than 3. For example, if you configure the number of Telnet sessions as 2, then the number of SSH sessions can only be a value 0 or 1. After configuring the required parameters, click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 210 6.3.3 SNMP To configure SNMP interface parameters, navigate to MANAGEMENT > Services > SNMP. Management Figure 6-20 SNMPv1-v2c Tsunami 800 & 8000 Series - Software Management Guide 211 Management Given below is the table which explains SNMP parameters and the method to configure the configurable parameter(s):

Figure 6-21 SNMPv3 Parameter SNMP By default, the user has the access to manage the device through SNMP Interface. To prevent access to the device through SNMP, select Disable. Description

: Any change in the SNMP status will affect the Network Management System access. Version Allows you to configure the SNMP version. The supported SNMP versions are v1-v2c and v3. By default, the SNMP version is v1-v2c. SNMP v1-v2c Specific Parameters Read Password Represents the read only community string used in SNMP Protocol. It is sent along with each SNMP GET / WALK / GETNEXT / GETBULK request to allow or deny access to the device. This password should be same as read password set in the NMS or MIB browser. The default password is public. The password should be of minimum 6 and maximum 32 characters. Tsunami 800 & 8000 Series - Software Management Guide 212 Management Parameter Description

: The following special characters are not allowed in the password:

- = \ ? / space Read/Write Password Represents the read-write community string used in SNMP Protocol. It is sent along with each SNMP GET / WALK / GETNEXT / SET request to allow or deny access to the device. This password should be same as read-write password set in the NMS or MIB browser. The default password is public. The password should be of minimum 6 and maximum 32 characters.

: The following special characters are not allowed in the password:

- = \ ? / space SNMP v3 Specific Parameters Security level The supported security levels for the device are AuthNoPriv and AuthPriv. Select AuthNoPriv for Extensible Authentication or AuthPriv for both Authentication and Privacy (Encryption). Priv Protocol Applicable only when the Security Level is set to AuthPriv. Represents the type of privacy (or encryption) protocol. Select the encryption standard as either AES-128 (Advanced Encryption Standard) or DES (Data Encryption Standard). The default Priv Protocol is AES-128.

: The following special characters are not allowed in the password:

- = \ ? / space Priv Password Applicable only when the Security Level is set to AuthPriv. Represents the pass key for the selected Privacy protocol. The default password is public123. The password should be of minimum 8 and maximum 32 characters.

: The following special characters are not allowed in the password:

- = \ ? / space Auth Protocol Represents the type of Authentication protocol. Select the encryption standard as either SHA (Secure Hash Algorithm) or MD5 (Message-Digest algorithm). The default Auth Protocol is SHA. Auth Password Represents the pass key for the selected Authentication protocol. The default password is public123. The password should be of minimum 8 and maximum 32 characters. After configuring the required parameters, click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 213 Management 6.3.3.1 SNMP Trap Host Table The SNMP Trap Host table allows you to add a maximum of 5 Trap servers IP address to which the SNMP traps will be delivered. By default, the SNMP traps are delivered to 169.254.128.133.

: The default SNMP Trap Host Table entry cannot be deleted. To add entries to the Trap Host Table, click Add in the Services screen. The SNMP Trap Host Table Add Row screen appears:

Configure the following parameters:

Figure 6-22 Add Entries to SNMP Host Table IP Address: Based on the IP mode, enter the IPv4 or IPv6 address of the Trap server to which SNMP traps will be delivered.

: IPv6 address should be the global IP address and not the link local IP address. Password: Type the password to authenticate the Trap Server. The following special characters are not allowed in the password: - = \ ? / space

: Applicable only to SNMP v1-v2c. Comment: Type comments, if any. Entry Status: Select the entry status as either Enable or Disable. If enabled, the device will send SNMP traps to the authenticated Trap Server. After configuring the required parameters, click Add and then COMMIT. 6.3.3.2 Edit SNMP Trap Host Table Edit the desired SNMP Trap Host Table entries and click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 214 Management 6.3.4 Logs The device supports two types of log mechanisms:

1. Event Log: Based on the configured event log priority, all the log messages are logged and used for any analysis. This log messages remain until they are cleared by the user. 2. Syslog: They are similar to Event logs except that they are cleared on device reboot. To configure Event log and Syslog priority, navigate to MANAGEMENT > Services > Logs. The following screen appears:

Event Log Priority: By default, the priority is set to Notice. You can configure the event log priority as one of the following:

Figure 6-23 Logs Emergency Alert Critical Error Warning Notice Info Debug Please note that the priorities are listed in the order of their severity, where Emergency takes the highest severity and Debug the lowest. When the log priority is configured as high, all the logs with low priority are also logged. For example, if Event Log Priority is set to Notice, then the device will log all logs with priorities Notice, Warning, Error, Critical, Alert and Emergency. Syslog Status: By default, Syslog Status is enabled and default priority is Critical. If desired, you can choose to disable. Syslog Priority: Configuration is same as Event Log Priority. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 215 Management 6.3.4.1 Configure a Remote Syslog host Configure a syslog host (server) in order to forward syslog messages to it.

: You can configure only one syslog host. Follow the following steps to configure a remote syslog host:

1. Click Add in the Syslog Host Table screen. The Syslog Host Table Add Row screen appears:

2. IP Address: Based on the IP mode, enter IPv4 or IPv6 address of the Syslog host. Figure 6-24 Syslog Host Table Add Row

: IPv6 address should be the global IP address and not the link local IP address. 3. Host Port: Represents the port on which the Syslog host listens to the log messages sent by the device. The default port is 514.

: The user must configure the correct port number on which the Syslog host is running. Choice of port number must be in line with the standards for port number assignments defined by Internet Assigned Numbers Authority (IANA). 4. Comments: Types comments, if any. 5. Click Add. The syslog host is added to the Syslog Host Table. Tsunami 800 & 8000 Series - Software Management Guide 216 Management Figure 6-25 Syslog Host Configured For some reason, if the configured syslog host parameters are changed then you can edit it directly in the Syslog Host Table entry. You can change the following parameters:

IP Address Port Host Comments Entry Status:

Enable: By default, the configured Syslog host is enabled on the device. Disable: To disable an entry in the Syslog Host Table, click Disable. Delete: To delete the configured Syslog host, click Delete. After doing the necessary changes, click OK followed by COMMIT. 6.4 Simple Network Time Protocol (SNTP) Proxims point-to-multipoint and point-to-point devices are furnished with Simple Network Time Protocol (SNTP) Client software that enables to synchronize devices time with the network time servers. The SNTP Client when enabled on the device(s), sends an NTP (Network Time Protocol) request to the configured time servers. Upon receiving the NTP response, it decodes the response and sets the received date and time on the device after adjusting the time zone and day light saving. In case, the time servers are not available, then users also have the option to manually set the date and time on the device. To synchronize devices time with time servers or manually set the time, navigate to MANAGEMENT > SNTP. The SNTP screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 217 Management Given below is the table which explains SNTP parameters and the method to configure the configurable parameter(s):

Figure 6-26 Time Synchronization Parameter Enable SNTP Status Select this parameter to enable SNTP Client on the device. If enabled, the SNTP Client tries to synchronize the devices time with the configured time servers. Description By default, the SNTP status is disabled. Primary Server IP Address/Domain Name Enter the host name, or the IP address based on IP modes (IPv4 only or IPv4 and IPv6) of the primary SNTP time server. The SNTP Client tries to synchronize devices time with the configured primary server time.

If host name is configured, instead of IP address then make sure that DNS server IP is configured on the device. IPv6 address should be the global IP address and not the link local IP address. Secondary Server IP Address/Domain Name Enter the host name, or the IP address based on IP modes (IPv4 only or IPv4 and IPv6) of the secondary SNTP time server. If the primary server is not reachable, then SNTP client tries to synchronize devices time with the secondary server time. If the SNTP client is not able to sychronize the time with both the servers

(primary and secondary), then it tries to synchronize again after every one minute. IPv6 address should be the global IP address and not the link local IP address. Tsunami 800 & 8000 Series - Software Management Guide 218

Management Parameter Time Zone Configure the time zone from the available list. This configured time zone is considered before setting the time, received from the time servers, on the device. Description Day Light Saving Time Configure the Day Light Saving time from the available list. This configured Day Light Saving time is considered before setting the time, received from the time servers, on the device. ReSync Interval Set ReSync time interval ranging from 0 to 1440 minutes. Once the time is synchronized, the SNTP Client tries to resynchronize with the time servers after every set time interval. By default, the ReSync interval is set to 60 minutes. Sync Status Specifies the SNTP Client sync status when it tries to ReSync again with the time servers. The status is as follows:

Current Date/Time Manual Time Configuration displays the status as Disabled. Displays the current date and time. Synchronized: The SNTP client has synchronized time with the time servers. Synchronizing: The SNTP client is in the process of synchronzing time with the time servers. Disabled: The SNTP client will not synchronize the time with the time servers and If SNTP Client is disabled on the device or the time servers are not available on the network, then the user can manually set the time. Enter the time manually in the format:

MM-DD-YYYY HH:MM:SS. If SNTP is enabled, it displays the time the device received from the SNTP server. If SNTP is not enabled, then it displays the time manually set by the user.

To save the configured parameters, click OK and then COMMIT. 6.5 Access Control the user has to set the time again. behind the actual time. So, it is recommended to periodically check and adjust the time. Manual time configuration is not retained across reboots. After every reboot Over a period of time, with manual time configuration, the device may lag The Access Control tab enables you to control the device management access through specified host(s). You can specify a maximum of five hosts to control device management access. To configure management access control parameters, navigate to MANAGEMENT > Access Control. The Management Access Control screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 219 Management Figure 6-27 Management Access Control By default, the Management Access Control feature is disabled on the device. To enable, select Enable from the Access Table Status box and click OK. Reboot the device, for the changes to take effect.

: Only when the Access Table Status is enabled, you can add host(s) to the Management Access Control Table. 6.5.0.1 Add Host(s) to Management Access Control Table To add a host to the Management Access Control Table, do the following:

1. Click Add in the Management Access Control screen. The Management Access Table Add Row screen appears:

Figure 6-28 Management Access Table Add Row 2. IP Address: Based on the IP mode, configure either IPv4 or IPv6 address of the host that controls the device management access. 3. Entry Status: By default, the entry status is enabled meaning which the specified host can control the device management access. Edit the status to Disable, if you do not want the host to control the device management access. 4. Click Add.

: If MAC ACL is enabled, configure at least one entry in the Management Access Table with the IP address (of the PC or the management station), in order to manage the device. 6.5.0.2 Edit Management Access Control Table Entries Edit the desired host entries and click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 220 6.6 Reset to Factory The Reset to Factory tab allows you to reset the device to its factory default state. When this operation is performed, the device will reboot automatically and comes up with default configurations. To reset the device to its factory defaults, navigate to MANAGEMENT > Reset To Factory. The Factory Reset screen appears:

Management Click OK, if you wish to proceed with factory reset, else click Cancel. Figure 6-29 Reset to Factory Defaults 6.7 Convert QB to MP The Convert QB to MP tab lets you convert a QB to SU so that the converted device can connect to a BSU and operate as a SU. This feature is applicable only to, You can convert a QB to SU mode by using two methods:

QB-8151-EPR which converts to a SU QB-8250-EPR which converts to a MP-8250-SUR QB-8150-EPR which converts to a MP-8150-SUR QB-8200-EPA which converts to a MP-8200-SUA QB-8100-EPA which converts to a MP-8100-SUA QB-8150-EPR-100 which converts to a MP-8150-SUR-100 QB-825-EPR-50 which converts to a MP-825-CPE-50 QB-825-EPR-50+ which converts to a MP-825-SUR-50+

Method 1: Web Interface Method 2: Load an SU config file (retrieved from another SU) onto the QB device and then reboot.

: Even after conversion from QB to MP, the device description still shows as QB. Tsunami 800 & 8000 Series - Software Management Guide 221 To convert a QB to SU using Web Interface, do the following:

1. Navigate to MANAGEMENT > Convert QB to MP. The Convert QB to MP screen appears:

Management Figure 6-30 Convert QB to MP 2. Click OK. 3. Reboot the device for the changes to take effect.

QB. the device will reset to factory default upon initialization and operate in QB mode. In case of Method 1 (Web Interface) conversion, QB mode configuration will be deleted. A QB after converting to SU will function in SU mode only. It will accept only MP firmware for upgrade. The version of the firmware being upgraded to should be 2.4.0 or later. If earlier version of the firmware is loaded, When upgrading a converted device from Bootloader, it must be done using a QB image, as the device is licensed as The conversion of the device from QB to SU requires a reboot. Reset to factory defaults, always results in the device initializing in QB mode. Tsunami 800 & 8000 Series - Software Management Guide 222 Monitor This chapter contains information on how to monitor the device by using Web interface. It contains information on the following:

H

E

I

C

B

F

G

7.1 System

The System tab enables to view system specific information such as LED/RSSI Display.

: 'RSSI LED' feature is applicable only to 82x devices. To view LED/RSSI Display, navigate to MONITOR > System. The LED/RSSI Display screen appears:

Figure 7-1 LED/RSSI Display When the link is established, Received Signal Strength Indicator (RSSI) LEDs on the scaling mask glow. Scaling mask LEDs indicate the received signal strength of the link. The more LEDs on the scaling mask glow, better is the signal. To select the LED Display Status, navigate to Advanced Configuration > System. By default, RSSI Display mode is enabled, if required the user can select the Disable (LEDs Off) mode. In Disable (LEDs Off) mode, all the 5 LEDs will be off. The LED behavior in RSSI Display mode is given below:

By default all the 5 LEDs will blink for an interval of 1 second to indicate the device is UP. For a BSU, in order to monitor the SU link statistics, the user should first configure the wireless MAC address of the SU. If the configured SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. Tsunami 800 & 8000 Series - Software Management Guide 223 D

B

B

For a SU, if the SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For a CPE, if the CPE is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For QB, if EndPointA is registered with EndPointB, then the LEDs will glow based on the RSSI value of each EndPoint. else all the 5 LEDs will blink. Monitor Interface Statistics allows you to monitor the status and performance of the Ethernet and Wireless interfaces of the device. 7.2 Interface Statistics 7.2.1 Ethernet Statistics To view the Ethernet interface statistics, click MONITOR > Interface Statistics. The Interface Statistics screen appears:

Figure 7-2 Ethernet Interface Statistics To view Ethernet statistics, click Ethernet 1 or Ethernet 2 depending on the Ethernet interfaces supported by your device. Given below is the table which explains the parameters displayed in the Ethernet Statistics screen:

Specifies the largest size of the data packet received or sent on the Ethernet interface. The MTU size varies from 1500 to 1514 depending on the MTU configuration (See Description Specifies the MAC address at the Ethernet protocol layer. Specifies the current operational state of the Ethernet interface. Specifies the total number of octets received on the Ethernet interface. Parameter MTU MAC Address Operational Status In Octets

Tsunami 800 & 8000 Series - Software Management Guide 224 Monitor Parameter In Unicast Packets Specifies the number of subnetwork- unicast packets delivered to the higher level protocol. Description In Non-unicast Packets Specifies the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Out Octets Out Packets Out Discards Specifies the number of inbound packets that contained errors and are restricted from being delivered. Specifies the total number of octets transmitted out from the Ethernet interface. Specifies the total number of packets requested by the higher level protocol and then, transmitted. Specifies the number of error-free outbound packets chosen to be discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Out Errors Specifies the number of outbound packets that are not transmitted because of errors. To view the updated Ethernet statistics, click Refresh. To delete the Ethernet statistics, click Clear. Tsunami 800 & 8000 Series - Software Management Guide 225 7.2.2 Wireless Statistics To view the Wireless interface statistics, click MONITOR > Interface Statistics > Wireless1. Monitor Given below is the table which explains the parameters displayed in the Wireless statistics screen:

Figure 7-3 Wireless Interface Statistics Parameter MTU Description Specifies the largest size of the data packet received or sent on the wireless interface. The MTU size can range from 350 to 3808 bytes for High throughput modes and 350 to 2304 bytes for legacy mode. The default and maximum value of the WORP MTU is 3808 bytes for higher throughput and 2304 bytes for legacy mode. MAC Address Specifies the MAC address at the wireless protocol layer. Operational Status Specifies the current operational state of the wireless interface. In Octets In Packets Specifies the total number of octets received on the wireless interface. Specifies the number of packets delivered to the higher level protocol. Tsunami 800 & 8000 Series - Software Management Guide 226 Monitor Parameter Description In Errors Out Octets Out Packets Out Discards Out Errors Retunes Specifies the number of inbound packets that contained errors and are restricted from being delivered. Specifies the total number of octets transmitted out from the wireless interface. Specifies the total number of packets requested by the higher level protocol and then, transmitted. Specifies the number of error-free outbound packets chosen to be discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Specifies the number of outbound packets that are not transmitted because of errors. Specifies the number of times the radio is re-tuned for better performance of the device. Max Tx Power Indicates the maximum power that the radio can radiate. SNR Statistics represents the signal strength with regard to the noise at the antenna ports. SNR Statistics Antenna Status Control Extension Decrypt Errors CRC Errors PHY Errors Specifies the antenna ports available for the product. Please note that the antenna ports vary depending on the product. Specifies the configuration status of the antenna ports. ON indicates that antenna port is enabled and OFF indicates that antenna port is disabled. Specifies the SNR value of the packet received at the selected channel frequency. This parameter is applicable only to the 40 MHz modes, that is, 40 PLUS and 40 Minus. It specifies the SNR value of the packet received on the extension channel (20MHz). Rx Error Details This parameter is applicable only if security is enabled. It indicates the number of received packets that failed to decrypt. Specifies the number of received packets with invalid CRC. Specifies the total Rx PHY Errors. It generally indicates the interference in the wireless medium. To view the updated Wireless statistics, click Refresh. To delete the Wireless statistics, click Clear. 7.2.3 PPPoE Statistics

: Applicable only to an SU in Routing mode. To view PPPoE interface statistics, navigate to MONITOR > Interface Statistics > PPPoE > PPP Interface Stats. Tsunami 800 & 8000 Series - Software Management Guide 227 Monitor The PPPoE interface parameters are same as the Ethernet interface parameters. Please note that if a link is not established between a PPPoE client and server, then the device displays the following message. Figure 7-4 PPPoE Interface Statistics Figure 7-5 PPPoE Server - No Link Established To view the updated PPPoE interface statistics, click Refresh. Please note that for every 4 seconds, the interface statistics gets refreshed. To view the PPPoE connection status such as the number of attempts made to start a session between PPPoE client and server, and the number of attempts failed to establish a connection, click PPPoE Connection Stats. Figure 7-6 PPPoE Connection Statistics Tsunami 800 & 8000 Series - Software Management Guide 228 To view updated connection statistics, click Refresh. To restart the session between the PPPoE client and server, click Restart PPPoE Session. On successfully re-establishing a session, the IP address of the wireless interface will be assigned again by the PPPoE server, if Address Type is set to PPPoE-ipcp. Monitor To clear the existing connection statistics, click Clear. 7.2.4 IP Tunnels

: Applicable only in Routing Mode. To view IP Tunnels interface statistics, click MONITOR > Interface Statistics > IP Tunnels. The following IP Tunnel Interface Statistics screen appears:

Given below is an explanation to each of these parameters:

Figure 7-7 IP Tunnels Interface Statistics Parameter Description Name Alias Maximum Transmission Unit

(MTU) Specifies the tunnel interface name. Specifies the supplementary tunnel interface name. Specifies the largest size packet or frame that can be sent over the tunnel interface. The MTU of the tunnel interface is derived from the underlying interface:

For IP-IP tunnel interface: MTU = Underlying interface MTU 20 bytes (IP header) For IP-GRE interface: MTU = Underlying interface MTU 24 bytes (IP header + gre protocol) Operational Status The Operational Status indicates only the tunnel interface status. The status can be either UP or DOWN.

: For the tunnel to function correctly both ends should be configured correctly. Tsunami 800 & 8000 Series - Software Management Guide 229 Parameter Details Provides a more detailed statistics about the tunnel interface. To view the detailed statistics, click

. Description Monitor Figure 7-8 Detailed IP Tunnels Interface Statistics The detailed tunnel interface parameters are similar to the Ethernet Interface Statistics. 7.3 WORP Statistics 7.3.1 General Statistics Please refer to G

 . WORP General Statistics provides general statistics about the WORP. To view General Statistics, navigate to MONITOR > WORP Statistics > Interface 1 > General Statistics. The following WORP General Statistics screen appears. Tsunami 800 & 8000 Series - Software Management Guide 230 Monitor Figure 7-9 WORP General Statistics (SU/End Point A/End Point B) Figure 7-10 WORP General Statistics (BSU) Tsunami 800 & 8000 Series - Software Management Guide 231 7.3.1.1 Basic Statistics Given below is an explanation to the basic parameters:

Monitor Parameter Description Interface Type Specifies the type of radio interface. WORP Protocol Version Specifies the version of the WORP Protocol used. This information is useful to the customer support team for debugging purpose only. Specifies the sent or received data frames through wireless interface. WORP Data Messages Poll Data Refers to the number of polls with data messages sent or received. Poll No Data Refers to the number of polls with no data messages sent or received. Reply Data Refers to the number of poll replies with data messages sent or received. Reply More Data Refers to the number of poll replies with more data messages sent or received. Reply No Data Refers to the number of poll replies with no data messages sent or received. Poll No Replies Refers to the number of times the poll messages are sent by a BSU/End Point A and received no reply from SU/End Point B. This parameter is applicable only to a BSU. Specifies the number of transmissions occurred through the interface. Data Transmission Statistics Send Success Refers to the number of data messages sent and acknowledged by the peer successfully. Send Retries Send Failures Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Refers to the number of data messages that are not acknowledged by the peer even after the specified number of retransmissions. Receive Success Refers to the number of data messages received and acknowledged successfully. Receive Retries Refers to the number of successfully received re-transmitted data messages. Receive Failures Refers to the number of data messages that were not received successfully. Registration Details Specifies the status of the entire registration process. Remote Partners Refers to the number of remote partners. For an SU/End Point A/End Point B, the number of remote partners is always zero or one. Announcements Refers to the number of Announcement messages sent or received on WORP interface. Request For Service Refers to the number of requests for service messages sent or received. Registration Requests Refers to the number of registration request messages sent or received on WORP interface. Registration Rejects Refers to the number of registration reject messages sent or received on WORP interface. Authentication Requests Refers to the number of authentication request messages sent or received on WORP interface. Tsunami 800 & 8000 Series - Software Management Guide 232 Monitor Parameter Description Authentication Confirms Refers to the number of authentication confirm messages sent or received on WORP interface. Registration Attempts Refers to the number of times a registration attempt has been initiated. Registration Incompletes Refers to the number of registration attempts that are not yet completed. Registration Timeouts Refers to the number of times the registration procedure timed out. Registration Last Reason Refers to the reason for the last registration getting aborted or failed.

: For better results, the Send Failure or Send Retrieve must be low in comparison to Send Success. The same applies for Receive Retries or Receive Failure. Click Clear to delete existing general statistics. Click Refresh to view updated WORP general statistics. 7.3.1.2 Advanced Statistics Advanced statistics is applicable only to the BSU. The Advanced Statistics screen displays the wireless transmission values used by the BSU to send announcement and broadcast messages. Given below is an explanation to the advanced parameters:

Figure 7-11 WORP Advanced Statistics Parameter Description Tx Rate Displays the Data Transmission Rate used by the BSU. Data Stream Displays the Data Streams used by the BSU. Tsunami 800 & 8000 Series - Software Management Guide 233 Monitor Parameter Description TPC EIRP Power Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio. Displays the current EIRP that a radio antenna radiates (after applying the TPC). Displays the current transmit power radiated by the radio (after applying the TPC). Tx Antenna Ports Indicates the status of the antenna ports at the BSU end. Click Refresh to view updated WORP advanced statistics. 7.3.2 Link Statistics 7.3.2.1 SU / End Point B Link Statistics

: SU Link Statistics is applicable only to a BSU, and End Point B Link Statistics is applicable only to a End Point A device. SU Link statistics provides information about the SUs connected to a BSU. Similarly, End Point B Link Statistics provides information about an End Point B currently connected to an End Point A device. To view link statistics, navigate to MONITOR > WORP Statistics > Interface 1 > SU Link Statistics. Figure 7-12 An Example - SU Link Statistics (For 82x Devices) Tsunami 800 & 8000 Series - Software Management Guide 234 Monitor Figure 7-13 An Example - SU Link Statistics (For All Devices) Given below is an explanation to each of these parameters:

Parameter SU Name/

End Point B Name MAC Address Represents the name of the SU/End Point B connected to a BSU/End Point A respectively. Description Represents the MAC address of the SU/End Point B connected to a BSU/End Point A respectively. Local Tx Rate (Mbps) Represents the data transmission rate at the local (current device) end. Remote Tx Rate

(Mbps) Represents the data transmission rate at the remote (peer) end. Local Antenna Port Info Indicates the status of the antenna ports at the local end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Local Tx Antenna Port Info Indicates the status of the antenna ports at the transmitting end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Local Rx Antenna Port Info Indicates the status of the antenna ports at the receiving end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Tsunami 800 & 8000 Series - Software Management Guide 235 Monitor Parameter Local Signal (dBm) Represents the signal level with which the device at the local end receives frames from the device at the remote end, through wireless medium. Description Local Noise (dBm) Represents the noise measured at the local end antenna ports. Local SNR (dB) Represents the SNR measured by the receiver at the local end and is based on the Local Signal and Local Noise. Remote Rx Antenna Port Info Indicates the status of the remote end antenna ports. The antenna ports status is same as explained in Local Antenna Port Info. Remote Signal (dBm) Represents the signal level with which the device at the remote end receives frames, through wireless medium. Remote Noise (dBm) Represents the noise measured at the remote end antenna ports. Remote SNR (dB) Represents the SNR measured by the receiver at the remote end and is based on the Remote Signal and Remote Noise. Current Tx Power

(dBm) TPC: Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio antenna.

: For a given data rate, if the configured TPC value is greater than the maximum transmit power supported by the radio then maximum transmit power supported by radio value is applied. EIRP: Displays the current EIRP that a radio antenna radiates (after applying the TPC). Power: Displays the current transmit power radiated by the radio (after applying the TPC). Click Refresh to view updated link statistics. To view detailed SU/End Point B Link statistics, click Details icon following screen appears depending on your device:

in the SU/End Point B Link Statistics screen. The Tsunami 800 & 8000 Series - Software Management Guide 236 Monitor Figure 7-14 An Example - SU Detailed Statistics The detailed page displays Remote SNR information, that is, the Minimum Required SNR and the Maximum Optimal SNR value for a given data rate or modulation, to achieve optimal throughput. To disconnect an SU/End Point B from BSU/End Point A respectively, click Disconnect. To view updated detailed statistics, click Refresh. To view local SNR table, click Click here for Local SNR-Table on the upper-right of SU/End Point B Link Statistics screen Tsunami 800 & 8000 Series - Software Management Guide

(Refer 

G

J

K L

 ). The following screen appears depending on your device:

237 Monitor These configured values are used by ATPC and DDRS to derive TPC and data rate for optimal throughput. Figure 7-15 An Example - Local SNR Information 7.3.2.2 BSU/End Point A Link Statistics

: BSU Link Statistics is applicable only to an SU, and End Point A Link Statistics is applicable only to an End Point B device. BSU Link statistics provides information about the BSU to which SUs are connected. Similarly, End Point A Link Statistics provides information about an End Point A currently linked to an End Point B device. Tsunami 800 & 8000 Series - Software Management Guide 238 Monitor Figure 7-16 An Example - BSU Link Statistics (For 82x Devices) Figure 7-17 An Example - BSU Link Statistics (For All Devices) To access the Radio Link Test Tool, navigate to MONITOR > WORP Statistics > Interface 1 > SU/BSU Link Statistics >

Details. Click

. The SU/BSU WORP Detailed Statistics screen appears. In this screen, click the Radio Link Test button. 7.3.3 QoS Statistics (BSU or End Point A Only) For detailed description of this tool, refer 

: This parameter is applicable only to BSU or End Point A radio modes. To view QoS Statistics, navigate to MONITOR > WORP Statistics > Interface 1 > QoS Statistics. The following QoS Summary screen appears. Tsunami 800 & 8000 Series - Software Management Guide 239 Monitor This screen shows the total, minimum and maximum bandwidth allocated per BSU/End Point A, and the minimum and maximum bandwidth allocated for each SU/End Point B registered with the BSU/End Point A respectively. Figure 7-18 QoS Summary 7.4 Active VLAN

: Active VLAN is applicable only to a device in SU (Bridge) mode. The Active VLAN page enables you to identify the VLAN Configuration mode applied on a device in SU mode. To view active VLAN applied on the device in SU mode, navigate to MONITOR > Active VLAN. The Active VLAN page appears:

The Active VLAN Config parameter helps you to identify the current VLAN configuration applied on the device in SU mode. Figure 7-19 Active VLAN Local: VLAN configuration is done locally from the device. Remote: VLAN configuration is done through RADIUS Server. Tsunami 800 & 8000 Series - Software Management Guide 240 This page also displays the VLAN parameters and their values that are configured either locally or remotely. To view active VLAN Ethernet Configuration, navigate to MONITOR > Active VLAN > Ethernet. The Active VLAN Ethernet Configuration page appears:

Monitor This page displays the VLAN Ethernet parameters and their values that are configured either locally or remotely. Figure 7-20 Active VLAN Ethernet Configuration

: Please note that the number of Ethernets vary depending on the device. 7.5 Bridge 7.5.1 Bridge Statistics The Bridge Statistics allows you to monitor the statistics of the Bridge. To view the Bridge Statistics, navigate to MONITOR > Bridge > Bridge Statistics. The following Bridge Statistics screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 241 Monitor Figure 7-21 Bridge Statistics Description Parameter The following table lists the parameters and their descriptionM Operational Status MAC Address MTU This parameter provides a description about the bridge. Represents the largest size of the data packet sent on the bridge. Represents the MAC address at the bridge protocol layer. Description Represents the current operational status of the bridge: UP (ready to pass packets) or DOWN (not ready to pass packets). In Octets Represents the total number of octets received on the bridge interface, including the framing characters. In Unicast Packets Represents the number of unicast subnetwork packets delivered to the higher level protocol. In Non-unicast Packets Represents the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Out Octets Out Packets Out Discards Represents the number of inbound packets with errors and that are restricted from being delivered. Represents the total number of octets transmitted out of the bridge, including the framing characters. Represents the total number of packets requested by higher-level protocols to be transmitted out of the bridge interface to a sub-network address, including those that were discarded or not sent. Represents the number of error-free outbound packets which are discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Tsunami 800 & 8000 Series - Software Management Guide 242 Monitor Parameter Out Errors Represents the number of outbound packets that could not be transmitted because of errors. Description To view updated Bridge statistics, click Refresh. To clear the Bridge statistics, click Clear. 7.5.2 Learn Table Learn Table allows you to view all the MAC addresses that the device has learnt on all of its interfaces. To view Learn Table statistics, navigate to MONITOR > Bridge > Learn Table. The Learn Table screen appears. The Learn Table displays the MAC address of the learnt device, the bridge port number, aging timer for each device learnt on an interface, and the local (DUT's local interfaces)/remote (learned entries through bridging) status of the learnt device. Figure 7-22 Learn Table To view updated learn table statistics, click Refresh. To clear learn table statistics, click Clear. 7.6 Network Layer 7.6.1 Routing Table Routing table displays all the active routes of the network. These can be either static or dynamic (obtained through RIP). For every route created in the network, the details of that particular link or route will get updated in this table. To view the Routing Table, navigate to MONITOR > Network Layer > Routing Table. The Routing Table screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 243 Monitor 7.6.2 IP ARP Figure 7-23 Routing Table Address Resolution Protocol (ARP) is a protocol for mapping an Internet Protocol address (IP address) to a physical address on the network. The IP ARP table is used to maintain a correlation between each IP address and its corresponding MAC address. ARP provides the protocol rules for making this correlation and providing address conversion in both directions. To view IP Address Resolution Protocol (ARP) statistics, navigate to MONITOR > Network Layer > IP ARP. The IP ARP Table screen appears. The IP ARP Table contains the following information:

Figure 7-24 IP ARP Table Net Address: This parameter represents the corresponding IP address of a node on the network. Type: This parameter represents the type of mapping, that is, Dynamic or Static. To view updated IP ARP entries, click Refresh. Index: Represents the interface type. MAC Address: Represents the MAC address of a node on the network. To clear the IP ARP entries, click Clear. Tsunami 800 & 8000 Series - Software Management Guide 244 7.6.3 ICMP Statistics The ICMP Statistics attributes enable you to monitor the message traffic that is received and transmitted by the device. To view ICMP statistics, navigate to MONITOR > Network Layer > ICMP Statistics. The ICMP Statistics screen appears. Monitor Figure 7-25 ICMP Statistics Parameter In Msgs or Out Msgs The following table lists the ICMP Statistics parameters and their descriptionM In Errors or Out Errors In Dest Unreachs or Out Dest Unreachs Description Represents the number of ICMP messages that are received/transmitted by the device. Represents the number of ICMP messages that are received/transmitted by the device but determined as having ICMP-specific errors such as Bad ICMP checksums, bad length and so on. Represents the number of ICMP destination unreachable messages that are received/transmitted by the device. In Time Excds or Out Time Excds Represents the number of ICMP time exceeded messages that are received/transmitted by the device. In Parm Probs or Out Parm Probs Represents the number of ICMP parameter problem messages that are received/transmitted by the device. In Srec Quenchs or Out Srec Quenchs Represents the number of ICMP source quench messages that are received/transmitted by the device. In Redirects or Out Redirects Represents the rate at which the ICMP redirect messages are received/transmitted by the device. In Echos Represents the rate at which the ICMP echo messages are received. In EchoReps or Out EchoReps Represents the rate at which the ICMP echo reply messages are received/transmitted by the device. Tsunami 800 & 8000 Series - Software Management Guide 245 Monitor Parameter Description In Timestamps or Out Timestamps Represents the rate at which the ICMP timestamp (request) messages are received/transmitted by the device. In Timestamps Reps or Out Timestamps Reps Represents the rate at which the ICMP timestamp reply messages are received/transmitted by the device. In Addr Masks or Out Addr Masks Represents the number of ICMP address mask request messages that are received/transmitted by the device. In Addr Mask Reps or Out Addr Mask Reps Represents the number of ICMP address mask reply messages that are received/transmitted by the device. To view updated ICMP Statistics, click Refresh. 7.6.4 IP Address Table The IP Address Table shows all IP addresses of the device. The IP Address Table screen contains IP addresses of the interface. To view table, navigate to MONITOR > Network Layer > IP Address Table. The IP Address Table screen appears. Figure 7-26 IP Address Table 7.6.5 DNS Addresses It shows DNS Addresses currently active on the device. To view DNS addresses, navigate to MONITOR > Network Layer >

DNS Addresses. The DNS Addresses screen appears. Tsunami 800 & 8000 Series - Software Management Guide 246 Figure 7-27 DNS Addresses 7.6.6 Neighbour Table

: This parameter is applicable only in IPv4 and IPv6 mode, not in IPv4 only mode. The Neighbour Table contains a list of neighbouring routers and information about them. To view Neighbour Table, navigate to MONITOR > Network Layer > Neighbour Table. The Neighbour table screen appears. Monitor Figure 7-28 Neighbour Table 7.6.7 RIP Database

: Applicable only in routing mode. The RIP Database screen contains routes (Routing Information Protocol updates) learnt from other routers. Tsunami 800 & 8000 Series - Software Management Guide 247 Figure 7-29 RIP Database Monitor 7.7 RADIUS (BSU or End Point A only)

: RADIUS is applicable only to a BSU or an End Point A device. 7.7.1 Authentication Statistics Authentication Statistics provides information on RADIUS Authentication for both the primary and backup servers for each RADIUS server profile. To view Authentication statistics, navigate to MONITOR > RADIUS > Authentication Statistics. The RADIUS Client Authentication Statistics screen appears:

Figure 7-30 Radius Client Authentication Statistics Parameter Round Trip Time The following table lists the Authentication Statistics parameters and their descriptionM Description RTMS Reqs Represents the number of RADIUS access request messages transmitted from the RADIUS client to the authentication server since client startup. This parameter represents the number of times the RADIUS access requests are being transmitted to the server from the device since the client startup. Represents the round trip time for messages exchanged between RADIUS client and authentication server since the client startup. Accepts Rejects Resp Mal Resp Bad Auths Time Outs Represents the number of RADIUS access accept messages received by the device since client startup. Represents the number of RADIUS access reject messages received by the device since client startup. Represents the number of RADIUS response packets received by the device since client startup. Represents the number of malformed RADIUS access response messages received by the device since client startup. Represents the number of malformed RADIUS access response messages containing invalid authenticators received by the device since client startup. Represents the total number of timeouts for RADIUS access request messages since client startup. Tsunami 800 & 8000 Series - Software Management Guide 248 Parameter UnKnown Types This parameter specifies the number of messages with unknown RADIUS message code since client startup. Description Packets Dropped Represents the number of RADIUS packets dropped by the device. To view updated RADIUS Client Authentication statistics, click Refresh. Monitor 7.8 IGMP

: Applicable in Bridge mode only. To view IGMP statistics, navigate to MONITOR > IGMP > IGMP Snooping Stats. The Ethernet or Wireless Multicast List screen appears:

Figure 7-31 Ethernet1 Multicast List 7.8.1 Ethernet or Wireless Multicast List The Multicast List table contains the IGMP Multicast IP and Multicast MAC address details for the Ethernet or Wireless interfaces. The following table lists the parameters and their description. Parameter Group IP MAC Address Time Elapsed Description Represents the IP address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Represents the MAC address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Represents the time elapsed since the multicast entry has been created for the Ethernet or Wireless interface. To view updated IGMP statistics, click Refresh. 7.8.2 Router Port List The Router Port List displays the list of ports on which multicast routers are attached. To view Router Port List, navigate to MONITOR > IGMP > Router Port List. The Router Port List screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 249 Monitor Figure 7-32 Router Port List The following table lists the parameters and their description. Parameter Port Number Represents the port number on which multicast router is attached (on which IGMP Query has been received). Description Time Elapsed Represents the time elapsed since the port is marked as the router port. To view updated Router Port list, click Refresh. 7.9 DHCP DHCP Leases file stores the DHCP client database that the DHCP Server has served. The information stored includes the duration of the lease, for which the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card of the DHCP client. To view DHCP Leases, navigate to MONITOR > DHCP > Leases. Figure 7-33 DHCP Leases Tsunami 800 & 8000 Series - Software Management Guide 250 Monitor 7.10 Logs 7.10.1 Event Log Event Log file keeps track of events that occur during the operation of the device. It displays the event occurring time, event type, and the name of the error or the error message. Based on the priority (the log priority is set under MANAGEMENT >

Services > Logs), the event details are logged and can be used for any future reference or troubleshooting. 7.10.1.1 View Event Log To view the event log messages, navigate to MONITOR > Logs > Event Log. The following Event Log screen appears:

Figure 7-34 Event Log Messages The maximum size of the event log file is 65 KB. If the file size exceeds 65 KB, then all the log messages are moved to a backup file and only the recent 100 lines are displayed in the log file. When the size of the log file exceeds again then it overwrites the backup file. Backup files can be retrieved by using retrieve CLI command. For more details, see Tsunami 800 and 8000 Series To retrieve the event log file from the device, see N Reference guide available at Y U X

V R _ U Q Z

V

Z P P V 7.10.1.2 Hide Event Log To hide the event log messages, click Hide Event Log. O P

. Q R O S O T Q U V W O S R X O .

: Log messages can be stored in the log file approximately up to 6 days with logging interval of 5 minutes. Tsunami 800 & 8000 Series - Software Management Guide 251 Monitor 7.10.1.3 Clear Event Log To clear the event log messages, click Clear Event Log. The messages are cleared and moved to the backup file leaving the event log file empty. An event is generated on clearing the event log messages.

: The current and the backed up event logs are stored in the flash memory and can be retrieved even after device reboot. 7.10.2 Debug Log Debug Log helps you to debug issues related to important features of the device. Currently, this feature supports only DDRS and DFS. This feature helps the engineering team to get valuable information from the field to analyze the issues and provide faster solution. This feature should be used only in consultation with the Proxim Customer Support team. Once logging is enabled, the Debug Log file can be retrieved via HTTP or TFTP. To enable Debug Log, navigate to MONITOR > Logs > Debug Log. The Debug Log screen appears:

Features: Select the appropriate features to be logged. The available features are Select All, DDRS Level 1, DDRS Level 2, DDRS Level 3 and DFS. Figure 7-35 Debug Log File Status: This parameter displays the current size of the Debug Log file. After selecting the DDRS level, click OK. To delete the Debug Log, click Clear Log. To get the updated status of the Debug Log File, Click Refresh. 7.10.3 Temperature Log

: Temperature Log is not applicable to MP-8150-CPE, MP-8160-CPE, MP-825-CPE-50, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-825-EPR/LNK-50, QB-825-EPR/LNK-50+ and QB-8150-LNK-12/50 devices. Temperature Log feature is used to log the internal temperature of the device for the configured temperature logging interval

(By default, it is 5 minutes). It also generates a trap and an event message when the internal temperature of the device Tsunami 800 & 8000 Series - Software Management Guide 252 reaches or exceeds the configured threshold range. The device issues a warning trap when the temperature is 5 Celsius less than the configured threshold range. To access this feature, navigate to MONITOR > Logs > Temperature Log. The following Temperature screen appears:

Monitor Figure 7-36 Temperature Log Current Unit Temperature: Displays the current internal temperature of the device in Celsius. High and Low Temperature Threshold:

Configure the high temperature threshold ranging from -40C to 60C. By default, it is set to 60C. Configure the low temperature threshold ranging from -40C to 60C. By default, it is set to -40C. When the current internal temperature of the device reaches or exceeds this threshold range, then a trap and event message is generated for every one hour (as long as it stays in the same state). If the temperature of the device further changes, then the device will immediately generates another trap and an event message. For example, lets say the configured threshold range is -30(low) to 40 (high). If the device temperature reaches 50 then a trap and event message is generated for every one hour till it remains at 50. So, when the temperature increases to 51 then it will immediately generate another trap and an event message. Temperature Logging Interval: A logging interval from 1 to 60 minutes with 5 minute increment can be selected. For example, if you configure logging interval as 10 minutes then the device temperature is logged for every 10 minutes.

: If the logging interval is configured 0, then the temperature log feature will be disabled. After configuring the parameters, click OK followed by COMMIT.

Tsunami 800 & 8000 Series - Software Management Guide 253 7.10.3.1 View Temperature Log To view the temperature Log, click Show Temp Log. Monitor Figure 7-37 View Temperature Log The maximum size of the temperature log file is 65 KB. If the file size exceeds 65 KB, then all the log messages are moved to a backup file and only the recent 100 lines are displayed in the log file. When the size of the log file exceeds again then it overwrites the backup file. Backup files can be retrieved by using retrieve CLI command. For more details, see Tsunami 800 and 8000 Series To retrieve the temperature log file from the device, see N Reference guide available at Y V U X

V R _ U Q

. V Z Z

P P

O P Q R O S O T Q U V W O S R X O .

: Log messages can be stored in the log file approximately up to 6 days with logging interval of 5 minutes. Tsunami 800 & 8000 Series - Software Management Guide 254 Monitor 7.10.3.2 Hide Temperature Log To hide the temperature log messages, click Hide Temp Log. 7.10.3.3 Clear Temperature Log To clear the temperature log messages, click Clear Temp Log. The messages are cleared and moved to the backup file leaving the temperature log file empty. An event is generated on clearing the temperature log messages.

: The current and the backed up temperature logs are stored in the flash memory and can be retrieved even after device reboot. 7.11 Tools 7.11.1 Wireless Site Survey

: Applicable only to a device in SU or End Point B mode. Wireless Site Survey is done by the SU or End Point B only. This feature scans all the available channels according to the current Channel Bandwidth, and collects information about all BSUs or Endpoint A configured with the same network name as SUs or End Point B. Figure 7-38 Wireless Site Survey - SU Mode To initialize the survey process, click Start. This process list the details of all the available BSUs or End Point A. To stop the site survey process, click Stop. During the scan process, click Refresh to view the latest discovered BSU/End Point A.

: Site Survey cannot be performed, when Roaming is enabled. Tsunami 800 & 8000 Series - Software Management Guide 255 7.11.2 Scan Tool With Scan Tool, you can scan all the Proxim devices available on the network. To scan the devices, navigate to MONITOR > Tools > Scan Tool. The Scan Tool screen appears. In the Scan Tool screen, select Scan Mode as IPv4. Click Scan to scan and refresh the devices on the network. The scanned devices are displayed as shown below:

Monitor Figure 7-39 An Example - Scanned Devices (IPv4) In the Scan Tool screen, select Scan Mode as IPv6 to scan the 82x devices with IPv6 mode. Click Scan to scan and refresh the devices on the network. The scanned 82x devices are displayed as shown below:

Figure 7-40 An Example - Scanned Devices (IPv6)

: ScanTool IPv6 support is applicable only for the 82x devices with IPv6 mode. 7.11.3 sFlow Proxims point-to-multipoint and point-to-point devices support sFlow technology, developed by InMon Corporation. The sFlow technology provides the ability to measure network traffic on all interfaces simultaneously by collecting, storing, and analyzing traffic data. Depicted below is the sFlow architecture that consists of a sFlow Agent and a sFlow Receiver. Tsunami 800 & 8000 Series - Software Management Guide 256 Monitor Figure 7-41 sFlow Architecture - An Example with a BSU and SUs The sFlow Agent, which is running on devices, captures traffic information received on all the Ethernet interfaces, and sends sampled packets to the sFlow Receiver for analysis. The sampling mechanism used to sample data are as follows:

Packet Flow Sampling: In this sampling, the data packets received on the Ethernet interface of the device are sampled based on a counter. With each packet received, the counter is decremented. When the counter reaches zero, the packet is packaged and sent to the sFlow Receiver for analysis. These packets are referred to as Packet Flow Samples. Counter Polling Sampling: In this sampling, the sFlow Agent sends counters periodically to the sFlow Receiver based on the set polling interval. If polling interval is set to 5 seconds then the sFlow Agent sends counters to sFlow Receiver every 5 seconds. These packets are referred to as Counter Polling Samples. The Packet Flow Samples and Counter Polling Samples are collectively sent to the sFlow Receiver as sFlow Datagrams. It is possible to enable either or both types of sampling. sFlow Sampling effects the system performance and hence care must be taken in configuring the sFlow parameters. To configure sFlow, navigate to MONITOR > Tools > sFlow. The following sFlow screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 257 Monitor This screen displays the following information about the sFlow Agent:

Figure 7-42 sFLOW Version: The version displayed is 1.3;Proxim Wireless Corp.; v6.4. The version comprises the following information:

1. sFlow MIB Version: Indicates the agents MIB version. The MIB specifies how the agent extracts and bundles sampled data, and the sFlow receiver must support the agents MIB. The sFlow MIB version is 1.3. so the sFlow Receivers version must also be at least 1.3. 2. Organization: Specifies the organization implementing sFlow Agent functionality on the device, that is, Proxim Wireless Corp. 3. Revision: Specifies the sFlow Agent version, that is, v6.4. Address Type: Specifies the protocol version for IP addresses. Agent Address: Specifies the sFlow Agents IP address. 7.11.3.1 sFlow Receiver Configuration The Receiver Configuration page allows you to configure sFlow Receiver(s), which receives samples from all agents on the network, combines and analyzes the samples to produce a report of network activity. To configure sFlow Receiver, navigate to MONITOR > Tools > sFlow and select Receiver Configuration tab. Given below is the table which explains sFlow parameters and the method to configure the configurable parameter(s):

Parameter Description S.No. Owner Represents the Receiver index number. Please note that the number of indexes depends on the Ethernet interfaces your device supports. Enter a string, which uniquely identifies the sFlow Receiver. Tsunami 800 & 8000 Series - Software Management Guide 258

Monitor Parameter Description Time Out Enter a value ranging from 30 to 31536000 seconds (365 days) in the Time Out box. The sFlow Agent sends sampled packets to the specified sFlow Receiver till it reaches zero. At zero, all the Receiver parameters are set to default values. Max Datagram Size Enter the maximum size of a sFlow datagram (in bytes), which the Receiver can receive, in the Max Datagram Size box. By default, the maximum datagram size is set to 1400 bytes. It can range from 200 to 1400 bytes. Address Type The address type supported by sFlow Receiver is ipv4, which is by default selected.

: Only IPv4 is currently supported. Receiver Address Enter the sFlow Receivers IP address in the Receiver Address box. Receiver Port By default, the sFlow Receiver listens to the sFlow datagrams on 6343 port. To change the port, enter a valid port ranging from 0 to 65535 in the Receiver Port box. Datagram Version The sFlow datagram version used is 5. Click Apply, to save the sFlow Receiver configuration parameters. Once the Receiver configurations are done, either Packet Flow sampling or Counter Polling Sampling or both can be started.

7.11.3.2 Sampling Configuration Timeout and Max Datagram Size.

` Enabling sampling effects the system performance and hence care should be taken in setting the right values for

` When the Owner string is cleared, the Flow Sampling and Counter Polling stops. 1. Navigate to MONITOR > Tools > sFlow and select Sampling Configuration tab. To configure and start packet flow sampling, do the following:

Tsunami 800 & 8000 Series - Software Management Guide 259 Monitor Figure 7-43 sFlow Sampling Configuration 2. From the Receiver Index drop-down box, select the receiver index number associated with the sFlow Receiver to which the sFlow Agent should send the sFlow Datagrams.

: If device has two Ethernet interfaces, then configure different Receiver indexes for each of the interface. 3. Type a value in the Packet Sampling Rate box. This value determines the number of packets the sFlow Agent samples from the total number of packets passing through the Ethernet interface of the device. 4. Type a value in the Maximum Header Size box, to set the amount of data (in bytes) to be included in the sFlow datagram. The sFlow Agent samples the specified number of bytes. For example, if you set the Maximum Header Size to 100, the sFlow Agent places the first 100 bytes of every sampled frame in the datagram. The value should match the size of the frame and packet header so that the entire header is forwarded. The default size is 128 bytes. The header size can range from 20 to 256 bytes.

Sampling values are set to default values. right value for Packet Sampling Rate and Maximum Header Size. 5. Next, click Apply to start packet flow sampling. Once it starts, the Time Out parameter (see a T b U c N O X O R S O Q d e ) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and U e f R g h Q i P R U

` Enabling sFlow packet sampling effects the system performance, and hence care must be taken when choosing the

` Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface. 1. Navigate to MONITOR > Tools > sFlow and select Counter Polling Configuration tab. 260 To configure and start Counter Polling sampling, do the following:

7.11.3.3 Counter Polling Configuration Tsunami 800 & 8000 Series - Software Management Guide Monitor Figure 7-44 Counter Polling Configuration 2. From the Receiver Index drop-down box, choose the receiver index number associated with the sFlow Receiver to which the sFlow Agent sends the counters.

: If Packet Flow Sampling is already configured and running, then you should configure the Receiver index same as configured in the Packet Flow Sampling for each Ethernet interface. 3. Set the polling interval by typing a value in the Interval box. Lets say, the polling interval is set to 30 seconds. So for every 30 seconds, the counters are collected and send to the sFlow Receiver. The valid range for polling interval is 0 to 231 - 1 seconds. right value sampling interval. Counter Polling values are set to default values. 4. Next, click Apply to start Counter Polling Sampling. Once it starts, the Time Out parameter (see a T b U c N O X O R S O Q d e ) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and U e f R g h Q i P R U

` Enabling sFlow counter sampling effects the system performance, and hence care must be taken when choosing the

` Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface.

If a sampling starts and there is already another sampling running then we consider the time out value of the current/already running sampling. The Console Commands feature helps Proxims Technical Support team to debug field issues. 7.11.4 Console Commands Tsunami 800 & 8000 Series - Software Management Guide 261 Monitor 7.11.5 Spectrum Analyzer

: Spectrum Analyzer is not applicable to MP-8150-CPE and QB-8150-LNK-12/50 devices. Spectrum Analyzer helps to analyze a spectrum for interference, and select a relatively low interference channel. This tool is not a replacement for the commercial Spectrum Analyzers as this is only intended to help with channel selection and diagnose performance issues.

: Only an administrator user can use Spectrum Analyzer to scan the spectrum. However, the Monitor user can view the last scanned results. To scan all the channels in the configured frequency domain, do the following:

1. Navigate to MONITOR > Tools > Spectrum Analyzer. The following Spectrum Analyzer screen appears:

Figure 7-45 An Example - Spectrum Analyzer 2. Channel Scan Time: Enter the time (ranging from 100 to 60000 milliseconds) to scan each channel. By default, the scan time is set to 1000 milliseconds. 3. Scan Iterations: Enter a number (ranging from 1 to 1000) which represents the number of times the scan iterates. By default, the scan iteration is set to 1. 4. After configuring the Channel Scan Time and Scan Iterations, click OK. Upon clicking OK, the Approximate Scan Duration parameter displays the total time (dd:hh:mm:ss) required to complete the scan. 5. Last Scanned Time: Represents the time at which the last spectrum scan was done. 6. Next click Start, to start the scan. Click Stop to stop the scan or wait for completion of the scan.

results captured at that particular instance. d d

` Spectrum Analyzer scan cannot be performed when W l is enabled. j W k e U R P X

e i V R X Y i e e

` The total duration of scan depends on the number of channels available, channel scan time and scan iterations.

` To reduce scan duration, configure the appropriate frequency filter lower and upper edges.

` While scanning, Spectrum Analyzer does not consider channel offset.

` The frequencies are scanned by 5MHz slice starting from the lower edge of the frequency filter, and displays the

` Spectrum Analyzer detects only 802.11 modulated signals. j O O O b b 262 Tsunami 800 & 8000 Series - Software Management Guide Monitor

(increase the Scan Time) to get accurate results.

` When working in a high interference network, ensure to run the spectrum analyzer with multiple iterations As the wireless link is down during spectrum analysis, the remote device cannot be accessed. Hence, if Spectrum Analyzer is started on a remote device, the results will not be available until spectrum scan is completed and wireless link gets re-established. When the Spectrum Analyzer starts, the wireless link, if established, is terminated and re-established after the scan is completed. 7. The scanned results are displayed in the form of a graph as follows:

` A minor variation in Spectrum Analyzer results can be expected due to the following reasons:

` Satellite Density Configuration

` A variation in the radio properties between various device models. Figure 7-46 An Example - Scanned Results Tsunami 800 & 8000 Series - Software Management Guide 263 Graph Results Interpretation Consider a network with a device operating on channel 122 with 20 MHz channel bandwidth. In the same vicinity, when we Monitor We recommend to avoid using these channels while installing Tsunami products, otherwise radio will report huge PHY and CRC errors. However, to make these channels usable and to ignore the low interference signals, we recommend configuring interfering signals on channels 115 to 129. It also shows strong interfering signal on channels 120 to124 indicating the presence of a device operating on channel 122, and moderate interfering signals on channels 115-119 and 125-129 (which are side band signals from the same interference source). on the devices. By default, for each channel, the graph represents the following statistics:

run the Spectrum Analyzer on a Tsunami radio it will display the results as shown in T P R a e O W O P R b b O P i j Maximum RSSI Minimum RSSI Description Parameter

Represents the maximum RSSI of all the signals received during the scan on a given channel. Represents the minimum RSSI of all the signals received during the scan on a given channel. Average RSSI Represents the average RSSI of all the signals received during the scan on a given channel. R g h Q O m n o p . From the results, we see Legend Activity Count Represents the total wireless activities (including OFDM Signal and Errors) during the scan on a given channel. Please note that the Current Iteration parameter helps to learn the current scan iteration. For example, if Scan Iteration is configured as 2, and currently only one scan cycle is complete then Current Iteration parameter displays 1. To view the statistics of a particular channel, point the cursor to that channel on the graph. The statistics is displayed as shown below:

It is also possible to view only the selected statistics on the graph. For example, to view only Minimum and Maximum RSSI on the graph, uncheck the box against Activity Count and Avg on the top of the graph. Figure 7-47 Channel Statistics Tsunami 800 & 8000 Series - Software Management Guide 264 Monitor Figure 7-48 An Example - Selective Graph Statistics At a time, the graph represents the statistics of a maximum of 32 channels. To view the graph(s) of the remaining channels, click Next (available on the upper right corner of the graph). Click Previous to view the statistics of the previous channels. To view the tabular format of the graph statistics, click Detailed Statistics on the bottom left of the graph. The detailed statistics is displayed as follows:

Figure 7-49 An Example - Detailed Statistics Tsunami 800 & 8000 Series - Software Management Guide 265 Monitor

: Spectrum Analyzer configuration parameters and results are not persistent across reboots. 7.11.6 Radio Link Test Tool In general, whenever the network has some performance issue, it is required to identify whether the issue is due to the wireless link or due to other network parameters. The Radio Link Test (RLT) tool helps to measure and diagnose any performance issues in the wireless link. At MAC level, this tool internally generates the traffic between the two radios, monitors the traffic, and generates a test report.The test report will help in analyzing the wireless link performance and other related issues such as interference, lower throughput, and wireless errors. Especially for the static link establishment, this is very helpful to check the link between the two radios when installing for the first time or if any performance issues are noticed after the installation. If the link between the radios is of expected quality, then there is no issue with the wireless link. In case, if there is any issue due to wireless parameters, the link may need some tuning in configuration such as channel, Data Rate, Tx power or distance between radios. In spite of all the testing and tuning, if the performance still fails to improve, then it may be due to installation related issues such as antenna alignment or the physical path. In the worst case, it may be a hardware related issue. It is applicable only to 82x devices. other tools like Iperf or any other commercial tools. It is recommended to use this tool with caution on live networks as it will be generating internal traffic which may impact the network performance.

` This is not a replacement for other wireless performance measuring tools and should be used in conjunction with

` Radio Link test is an experimental feature and will be improved in future releases.

` This tool can be accessed through web interface, console commands, and CLI.

` Both ends of a link cannot simultaneously run this test. Time duration for which the Radio Link Test is performed (Default: 60 seconds) Description Parameter The configuration options for the Radio Link Test tool are tabulated below:

Test Duration 7.11.6.1 Configuration Options Traffic Direction Traffic Rate Direction of the traffic (Downlink/Uplink /Bi-directional) Amount of traffic to be generated (K bps) Periodic Report Interval Time interval in which the report is presented to the user interface (seconds) Packet Size MAC Address Verbose Mode Help Version Generate packet size (Default value: 1500 bytes) Wireless MAC address of the device running in server mode Detailed statistics information List of possible options (Usage) Display tool version information Tsunami 800 & 8000 Series - Software Management Guide 266 Monitor To access this tool through web interface, navigate to MONITOR > WORP Statistics > Interface 1 > BSU/SU Link Statistics > Details. Click as shown in q e r _ i V Z b O n j s t R e u j P i P R a P R X a . The following BSU/SU WORP Detailed Statistics screen appears. Figure 7-50 An Example - SU Link Statistics Click the Radio Link Test Button. The following Radio Link Test screen appears. Figure 7-51 Radio Link Test Tool In the Radio Link Test screen, you can select the required type of traffic from the given options namely Uplink, Downlink, and Bidirection. By selecting Verbose along with any one of the traffic options, you can get a detailed test report for the traffic selected. In the above screen, for example, select Bidirection and Verbose. Next, click the START button. Tsunami 800 & 8000 Series - Software Management Guide 267 Monitor Figure 7-52 An Example - Radio Link Test (Bidirectional Traffic with Verbose mode) The test runs for 60 seconds and displays the Radio Link Test Report as shown below. Figure 7-53 An Example - Test Report (Bidirectional Traffic with Verbose mode) Tsunami 800 & 8000 Series - Software Management Guide 268 7.11.6.2 Statistics Options The test report can be analyzed by using the statistics options tabulated below:

Monitor Parameter Traffic Statistics Tx Packets Rx Packets Lost Packets Duplicated Packets Tx Rate Rx Rate Wireless Statistics Phy Errors CRC Errors Medium Busy WORP Statistics Send success Send failure Send retires Receive success Receive failures Receive retires Description Total packets transmitted from the moment user initiated the test. Total packets received from the moment user initiated the test. Packets lost due to any reason. Number of packets received in duplicate for the already received packets. The rate at which the packets are sent. The rate at which the packets are received. Total number of error packets received from the moment user initiated the test . The possible reasons:

It indicates the interference in the wireless medium Low signal level Number of packets received with invalid CRC. The possible reasons:

It indicates the interference in the wireless medium Low signal level Number of times the radio detected busy medium while trying to transmit the frame. This could be due to interference on that specific channel. Refers to the number of data messages sent and acknowledged by the peer successfully. Refers to the number of data messages that are not acknowledged by the peer even after the specified number of retransmissions. Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Refers to the number of data messages received and acknowledged successfully. Refers to the number of successfully received re-transmitted data messages. Refers to the number of data messages that were not received successfully.

Tsunami 800 & 8000 Series - Software Management Guide 269 Monitor Parameter Signal Statistics Signal Noise SNR Description Signal measured at the radio port Noise detected at the radio port Signal to Noise Ratio (dB) Using the rlt command options tabulated below, you run the radio link test tool through Web Console. Options Description

-t

-i

-s

-o Traffic Direction

-d

-u Test duration (Default: 60 seconds) Periodic report display interval (Default: 0 - disabled) Packet size (Default: 1500 bytes) Ignore timeout during test (Default: do not ignore) Downlink throughput test with specified traffic rate in K bps (Default: Unlimited) Uplink throughput test with specified traffic rate in K bps (Default: Unlimited) No option Default: Bi-Directional test with unlimited rate Miscellaneous

-h, --help Tool usage

-v, --version Tool version number

-V Verbose mode (Enables detailed statistics display)

w x

x

x

x

x

w

w x y z

x

x

v w x x y

z

Tsunami 800 & 8000 Series - Software Management Guide 270 To access this tool through Web Console, navigate to MONITOR > Tools > Console Commands. In the Web Console screen do the following:

Monitor Figure 7-54 An Example - Radio Link Test Through Web Console To run the Radio Link Test tool through Command Line Interface (CLI), refer the Tsunami 800 and 8000 Series Reference Guide. 7.12 SNMP v3 Statistics The command execution is displayed in the Web Console screen. Command: Type the required rlt command. Click the Execute button.

SNMP v3 statistics can be viewed only when SNMPv3 feature is enabled on the device. See j

. To view the SNMPv3 Statistics, navigate to MONITOR > SNMPV3 Statistics. The following SNMP v3 Statistics screen appears:

Tsunami 800 & 8000 Series - Software Management Guide 271 Monitor Figure 7-55 SNMP v3 Statistics Parameter Unsupported Sec Levels The following table lists the SNMP v3 parameters and their description Not In Time Windows Unknown User Names This parameter specifies the total number of packets dropped by the SNMP engine because they requested a security level that was unknown to the SNMP engine or otherwise unavailable. This parameter specifies the total number of packets dropped by the SNMP engine because they appeared outside the authoritative SNMP engine's window. This parameter specifies the total number of packets dropped by the SNMP engine because they correspond to a user that is unknown to an SNMP engine. Description Unknown Engine IDs This parameter specifies the total number of packets dropped by the SNMP engine because they correspond to an SNMP Engine ID that is unknown to an SNMP engine. Wrong Digests This parameter specifies the total number of packets dropped by the SNMP engine because they do not contain the expected digest value. Decryption Errors This parameter specifies the total number of packets dropped by the SNMP engine because they could not be decrypted. Tsunami 800 & 8000 Series - Software Management Guide 272 Troubleshooting 8 This chapter helps you to address the problems that might arise while using our device. If the procedures discussed in this chapter does not provide a solution, or the solution does not solve your problem, check our support site at which stores all resolved problems in its solution database. Alternatively, you can post a question on Before you start troubleshooting, check the details in the product documentation available on the support site. For details about RADIUS, TFTP, Terminal and Telnet programs, and Web Browsers, refer to their appropriate documentation. O X U S O Q

Q U X O h Q O a . R P

Q S X X U U V This chapter provides information on the following:

the support site, to a technical person who will reply to your email. Y P P Z

V

Z Q U _ R V In some cases, rebooting the device solves the problem. If nothing else helps, refer to N

U r e O d

U e e O X P

h U O g Q j

P j O h Z i q

P i R b Z Z X

O O Q R a b a

r k R Q O

a R Q O b O a

O N Q S U X O

V h Q P X O Z j

i b O X a R b j Q f O t h a l

d Y O O U Q h g a O g e Y u b U R X a a d U P q T e e t e O e e e e h O U U e e O U O O O O U e g h i U e h O Z O U h O Y U U e g h O e O e i O i i U e i O i i e U h O i O a a X a a a a a X X a a X

X a

a S X a k Q Q Q Q Q Q Q Q Q l R R P P P P f P P P f P P f P R R R R R R R R R b R R b R R b Tsunami 800 & 8000 Series - Software Management Guide 273 8.1 PoE Injector Problem The Device Does Not Work There is No Data Link Overload Indications Troubleshooting Solution Check the power plug and hub. Verify that the indicator on the device port is ON. Try to connect the device to a different PoE Injector hub. MP-825-CPE-50, QB-825-EPR/LNK-50, and QB-8150-LNK-12/50 Category 5/5e cable in case of MP-8150-CPE, MP-8160-CPE-A100, If the Ethernet link goes down, check the cable, cable type, switch and hub. Category 5e/6 cable in case of MP-8100-BSU, MP-8100-SUA, MP-8150-SUR, Category 5e/6 cable in case of MP-8100-BSU, MP-8100-SUA, MP-8150-SUR, Try using a different Ethernet cable if it works, there is probably a fault in the cable or its connection. Try a different port on the same PoE Injector hub (remember to move the input port accordingly) if it works then there is a problem in the previous RJ45 port or a bad RJ45 port connection. MP-8150-SUR-100, MP-8160-BSU, MP-8160-BS9, MP-8160-SUA, QB-8100-EPA/LNK, QB-8150-EPR/LNK, QB-8150-LNK-100, QB-8151-EPR/LNK, MP-8200-BSU, MP-8250-BS9, MP-8250-BS1, MP-8200-SUA, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-825-EPR/LNK-50+, and QB-8200-LNK devices Verify that the Ethernet cable from PoE Injector hub to the Ethernet port of the device is properly connected.

` Make sure that you are using a standard UTP

` Make sure that you are using a standard UTP

` Move the device into a different output port (remember to move the input port MP-8150-SUR-100, MP-8160-BSU, MP-8160-BS9, MP-8160-SUA, QB-8100-EPA/LNK, QB-8150-EPR/LNK, QB-8150-LNK-100, QB-8151-EPR/LNK, MP-8200-BSU, MP-8250-BS9, MP-8250-BS1, MP-8200-SUA, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-825-EPR/LNK-50+, and QB-8200-LNK devices Try to re-connect the cable to a different output port (remember to move the input port accordingly) if it works then there is a fault probably in the output or input port of the PoE Injector hub or a bad RJ45 connection. Try to connect a different device to the same port on the PoE Injector hub if it works and a link is established then there is probably a fault in the data link of the device. accordingly) - if it works then there is a fault probably in the previous RJ45 port or bad RJ45 port connection. The length of the cable from the Ethernet port of the device to the PoE should be less than 100 meters (approximately 325 feet). Category 5/5e cable in case of MP-8150-CPE, MP-8160-CPE-A100, Ensure that there is no short over on any of the connected cables. MP-825-CPE-50, QB-825-EPR/LNK-50, and QB-8150-LNK-12/50 Connect the device to a PoE Injector. Tsunami 800 & 8000 Series - Software Management Guide 274 8.2 Connectivity Issues Connectivity issues include any problem that prevents from powering or connecting to the device. Troubleshooting Problem Does Not Boot - No LED Activity Ethernet Link Does Not Work Serial Link Does Not Work Cannot Access the Web Interface Solution Check the Ethernet LED None;

support serial interface. configured to the following values:

Line Feeds with Carriage Returns Solid Green: The Ethernet link is up. Blinking Green: The Ethernet link is down. Double-check the physical network connections. Com Port: (COM1, COM2 and so on depending on your computer);

Baud rate: 115200; Data bits: 8; Stop bits: 1; Flow Control: None; Parity:

: Not applicable to MP-825-CPE-50, and MP-8160-CPE-A100 as it does not

(In HyperTerminal select: File > Properties > Settings > ASCII Setup > Send Line Ends with Line Feeds)

` Make sure the power source is ON.

` Make sure all the cables to the device are connected properly.

` Make sure your PC terminal program (such as HyperTerminal) is active and

` Open a command prompt window and type the Ping command along with the IP

address of the device. For example, ping 10.0.0.1. If the device does not respond, check if you have the correct IP address. If the device responds then it means the Ethernet connection is working properly. Ensure that you are not using a proxy server for the network connection with your Web browser. Ensure that you have not exceeded the maximum number of Web Interfaces or CLI sessions. Double-check the physical network connections. Use a well-known device to ensure the network connection is functioning properly. Ensure that you are using Microsoft Internet Explorer 7.0 (or later) or Mozilla Firefox 3.0 (or later).

: At any point of time, if the device is unable to connect to your network, reset Troubleshoot the network infrastructure (check switches, routers, and so on). the device by unplugging and plugging the cables from the PoE. Tsunami 800 & 8000 Series - Software Management Guide 275 8.3 Surge or Lightning Issues (For Connectorized devices) Troubleshooting Problem Surge or Lighting Problem In case of any lightning or surge occurrence, check for the conditions specified below:

Solution Check the RF signals by referring to RSSI statistics and if the signal strength has been lowered considerably, replace the Surge Arrestor. Unscrew the N-Type connector at the top and visually inspect the Surge Arrestor for electrical burns. If any, replace it. 8.4 Setup and Configuration Issues Problem Device Reboots Continuously Lost Telnet or SNMP Password Device Responds Slowly Incorrect Device IP Address Solution One of the reason for the device to reboot continuously is that the radio card is not properly placed in the mini-PCI slot. When you power on the device and you do not see the WIRELESS NETWORK1 PASSED in the POST message in the Serial Console,

. If the device takes a long time to respond, it could mean that:

parameters, but does not affect the image of the device. The default HTTP, Telnet, and SNMP username is admin and password is public. P P O procedure. This procedure resets system and network The IP address of the device is already in use. Verify that the IP address is assigned only to the device you are using. Do this by switching off the device and then pinging the IP address. If there is a response to the ping, another device in the network is using the same IP address. If the device uses a static IP address, switching to DHCP mode could solve this problem. V V V Z Z U U

_ X Q

R b The default IP address assignment mode is Static and the default IP address of the device is 169.254.128.132. If the IP address assignment mode is set to Dynamic, then the DHCP Server will assign an IP address automatically to the device. If the DHCP server is not available on your network, then the fall back IP address (169.254.128.132) of the device is used. Use ScanTool, to find the current IP address of the device. Once you have the current IP address, use Web Interface or CLI Interface to change the device IP settings, if necessary. If you are using static IP address assignment, and cannot access the device over R U i e U No DHCP server is available.

please contact Proxims support site at Y Perform P i Q O Z

Ethernet, refer to Perform Z O Q i P R U e The network traffic is more. R U e i e i P R R b R b q O Q O Y P g O procedure. This will reset the device to static mode. h e g t a a a R d Tsunami 800 & 8000 Series - Software Management Guide 276 Problem HTTP Interface or Telnet Does Not Work Telnet CLI Does Not Work TFTP Server Does Not Work Changes in Web Interface Do Not Take Effect Troubleshooting Solution

Broken Page icon Mozilla Firefox 3.0 or later Microsoft Internet Explorer 7.0 or later available on the right side of address bar. in the address bar of the browser, for example http://169.254.128.132. and Password. The default HTTP username is admin and password is public. Use CLI, to check the IP Access Table which can restrict access to Telnet and HTTP. Internet Options -> Security -> Internet -> Custom Level -> Scripting ->

Active Scripting to enable active scripting.

` Make sure you are using a compatible browser:

` When working with Internet Explorer 9 in Windows 2008 Server, navigate to

` When working with Internet Explorer 10 and facing web page issues, click the

` Make sure you have the correct IP address of the device. Enter the device IP address

` When the Enter Network Password window appears, enter the User Name and

` Make sure you have the correct IP address. Enter the device IP address in the Telnet

Use HTTP, to check the IP Access Table which can restrict access to Telnet and HTTP. connection dialog, from a DOS prompt: C:\> telnet <Device IP Address>

5. Wait until the device reboots before accessing the device again. Enable Telnet in Vista or Windows 7 as it is by default disabled. The TFTP server is not properly configured and running The upload or download directory is not correctly set 4. Click COMMIT for the changes to take effect. 2. Log on to the device again and make changes. The IP address of the TFTP server is invalid 1. Restart your Web browser. The file name is not correct 3. Reboot the device. Tsunami 800 & 8000 Series - Software Management Guide 277 Troubleshooting 8.5 Application Specific Troubleshooting Problem RADIUS Authentication Server Services unavailable Solution If RADIUS Authentication is enabled on the device, then make sure that your networks RADIUS servers are operational. Otherwise, clients will not be able to log on to the device. There are several reasons for the authentication servers services to be unavailable. To make it available, TFTP Server After the TFTP server is installed:

configured on the device. Check the RADIUS Authentication Servers Shared Secret and Destination Port number (default is 1812; for RADIUS Accounting, the default is 1813). If a TFTP server is not configured and running, you will not be able to download and upload images and configuration files to or from the device. Remember that the TFTP server need not be local, as long as you have a valid TFTP IP address. Note that you do not need a TFTP server running unless you want to transfer files to or from the device.

` Make sure you have the proper RADIUS authentication server information setup

` Make sure the RADIUS authentication server RAS setup matches the device.

` Make sure you have the proper TFTP server IP Address, the proper device image

` Make sure the TFTP server is configured to both Transmit and Receive files (on the TFTP servers Security tab), with no automatic shutdown or time-out (on the Auto Close tab). Check to see that TFTP is configured to point to the directory containing the device Image. file name, and that the TFTP server is connected. Tsunami 800 & 8000 Series - Software Management Guide 278 8.6 Wireless Link Issues Given below are the possible reasons for a wireless link not getting established and the relevant observations. Troubleshooting Reason(s) Mismatch in network name Incorrect or invalid configured BSU/End Point A name Mismatch in network secret Encryption set to No Encryption in BSU/End Point A and AES Encryption in SU/End Point B Encryption set to AES Encryption in BSU/End Point A and No Encryption in SU/End Point B Encryption set to AES Encryption in both BSU/End Point A and SU/End Point B. A mismatch in Encryption key BSU exceeds the maximum SU limit Observation The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A and SU/End Point B. The WORP counters are not affected. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in SU/End Point B. The WORP counters are not affected. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A and SU/End Point B. The WORP counters are incremented (Req for Serv, Reg Req, Auth Req, Reg Attempts, Reg LastReason: Incorrect Parameter) on both ends. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A; No decrypt errors are observed in SU/End Point B. In SU/End Point B, the WORP counters (Announcements, Req for Serv, Reg Attempts, Reg incomplete, Reg timeout, Reg Last Reason: Timeout) are incremented. In BSU/End Point A, no WORP counters are incremented except announcements. The remote device is not listed in the Site Survey. The Wireless Statistics counters and WORP counters are not incremented in SU/End Point B. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented only in SU/End Point B. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in SU/End Point B but fails to authenticate. The WORP counters (Announcements, Req for Serv, Reg Attempts, Reg Incompletes, Reg Timeouts, Reg Last Reason: Timeout) are incremented in SU/End Point B. The remote device is listed in the Site Survey. Tsunami 800 & 8000 Series - Software Management Guide 279

Troubleshooting Reason(s) With multiple link profiles, the wireless network performance is getting affected. Observation The overall performance of the wireless network gets affected when using multiple link profiles and atleast one of the subscriber is operating with a lower data rate. For example, consider a wireless network with a BSU and 5 SU profiles. Each SU is transmitting data at a data rate as tabulated below. As SU1 is operating at a lower data rate (6.5 Mbps), the entire performance of the network gets affected. SU Profile(s) Data Rate Throughput SU1 SU2 SU3 SU4 SU5 6.5 Mbps 39 Mbps 78 Mbps 130 Mbps 78 Mbps Aggregated throughput can be a maximum of 13 Mbps In order to optimize the network performance, apply QoS. Given below is an example on how the network performance can be improved by applying QoS. QoS is applied for SU1 with the following configuration:

PIR based on the ToS value 96 SFC with MIR/CIR= 1Mbps; Priority = 3; Latency/Jitter=10ms Subscribers SU2...SU5 use the default QoS configuration.

Profiles Data Rate Throughput SU1 SU2 SU3 SU4 SU5 6.5 Mbps 39 Mbps 78 Mbps 130 Mbps 78 Mbps With QoS applied for SU1, expected throughput is 26 Mbps

: Given above is just an example and values might vary from case-to-case. Tsunami 800 & 8000 Series - Software Management Guide 280 Reason(s) Interference issues due to wider beam width of the antenna 8.7 Wired (Ethernet) Interface Validation Problem Wired (Ethernet) Interface Validation Troubleshooting Observation Run iperf commands Solution DFS bands DDRS operation at lower data rates SNR value fluctuations between the Antenna (A1/A2) ports Higher number of PHY errors which may result in false RADAR detection in To overcome these issues, use a spectrum analyzer and switch to a noise-free channel. QB-825-EPR/LNK-50+ uses a wider beam width antenna (up to 38 o) with a gain of 15dBi. Due to its wider beam width, it may pick up more interfering signals and may report large number of errors compared to other Tsunami products. Wireless interference may also lead to:

` MP-825-CPE-50, MP-825-SUR-50+, QB-825-EPR/LNK-50, and

` Make sure the connection established is of same speed and full duplex is as expected

` With auto negotiation, if you notice this issue, then try manually setting the speed

Use iperf commands with w option as 202k. The throughput is expected to be equal in both directions and should be comparable from laptop to laptop or desktop to desktop performance Check speed and duplex settings between the device and Personal Computer or switch or router connected Update the Ethernet driver in the Personal Computer to the latest one

(10 or 100 or 1000) and duplex If the above throughput value is not in the expected range, Tsunami 800 & 8000 Series - Software Management Guide 281 8.8 Wireless Interface Validation Troubleshooting Problem Wireless Interface Validation Run iperf commands (You can run Embedded iperf commands only through Telnet.) Solution If the expected throughput is not achieved, then check the following:

connectivity server is running P -> No of pairs (Streams) iperf s w 202k (command for iperf server) RF cables, used between antenna and device Use d option to run bidirectional throughput Select Single stream instead of Dual stream mode DDRS - with single stream data rate or with Auto mode Avoid nearby metal surfaces, if you are using Omni antenna If in RMA (Returned from Customer), check the RF cable to radio port Signal difference of <=5 dBm is considered as balanced and recommended If the chains are not balanced, then look at the alignment and connectors of Ipaddress -> of the SU/End Point B or BSU/End Point A device where the iperf Use r option to run unidirectional throughput one after another without changing the server and SU ends Note whether the antenna ports are balanced SNR/RSSI provided for Local and Remote in the BSU/SU Link Statistics page or by using aad command Iperf c ipaddress w 202k t time Period I <intermediateResultInterval> P <4 or 6> (command to run iperf client)

` Antenna Alignment

` Data Streams

` Antenna Port Selection

` Use Wi-Spy or similar tool and check the environment for better channel For devices with 3x3 MIMO radio, make sure you are either enabling all antenna ports for 3x3 MIMO or using A1 and A3 antenna ports for 2x2 MIMO mode Dual stream data rates can be used only when the signal in both antenna ports is balanced. Monitor Interface Statistics page. If this count increments steadily (Refreshing the web page is required) then Enabling all antenna port will not cause any issue even if it is not in use. Check for CRC errors, PHY errors, WORP Retries and WORP Failures in For using single stream, it is mandatory to select antenna port A1 For devices with 2x2 MIMO radio, use A1 and A2 antenna ports Either change the channel and check for a better channel Bad Channel Tsunami 800 & 8000 Series - Software Management Guide 282 Problem Wireless Interface Validation Troubleshooting Solution

` Data Rate Issues

Ensure same data rates are selected if you are using fixed data rate between BSU/SU and End Point A/End Point B to have predictable throughput and link Alternatively, use DDRS with Auto mode enabled Performance and Stability Issues Check the distance between two co-locating devices. The distance between two co-locating devices should be minimum 3 meters, in order to achieve good throughput and maintain link stability. The operating adjacent channel should maintain 5MHz spacing if managed by a single administrator. When DDRS is disabled, check the Minimum Required SNR for the current data rate by navigating to MONITOR --> WORP Statistics --> Interface 1

--> Link Statistics Page --> Click here for Local SNR-Table. If the current SNR is not meeting the minimum required SNR criteria for the current data rate, then accordingly reduce the data rate. If SNR is more than the maximum optimal SNR limit (MONITOR --> WORP Statistics --> Interface 1 --> Link Statistics Page --> Click here for Local SNR-Table) then it causes radio receiver saturation thus impacting the performance of the link. To overcome this situation, set the TPC appropriately or enable ATPC to adjust the signal level automatically. Also, enabling DDRS can help in choosing right data rate automatically. To measure and diagnose any performance issues in the wireless link, use the Radio Link Test Tool. To use this tool, navigate to MONITOR --> WORP Statistics --> Interface 1 --> Link Statistics Page --> Details -->Click 8.9 Recovery Procedures Recovery Procedure is used to restore the device to its factory default operating state. Depending on the device state, the recovery procedures can be classified under two modes:

icon. For detailed description of this tool, refer N i R U t R e u O a P U U b 1. Operational Mode: Device is up and in running state. 2. Bootloader Mode: Device operating image is deleted. Tsunami 800 & 8000 Series - Software Management Guide 283 Troubleshooting 8.9.1 Operational Mode S.No 1 Scenario Recovery Procedure Restore the device to its factory default configuration while accessing it through web interface In the web interface, navigate to MANAGEMENT > Reset to Factory. The Factory Reset screen appears:

In the screen, click OK. The device now reboots and comes with:

2 The device is not accessible for reasons such as user has forgotten the web interface login password, Management VLAN Id is changed, wrong VLAN configuration. Press and hold the Reload button (use a pin or the end of a paper clip) on the POE injector for a time frame as mentioned in the following table:

Device Timings 5 to 6 seconds IP Address: 169.254.128.132 Password: public

` Username: admin

MP-8100-BSU; MP-8100-SUA MP-8150-SUR; MP-8150-SUR-100 MP-8160-BSU; MP-8160-BS9 MP-8160-SUA; MP-8200-BSU MP-8250-BS9; MP-8250-BS1 MP-8200-SUA; MP-8250-SUR MP-825-CPE-50; MP-825-SUR-50+;

MP-820-BSU-100; MP-820-SUA-50+

QB-825-EPR/LNK-50+;

QB-825-EPR/LNK-50;

QB-8100-EPA/LNK; QB-8150-EPR/LNK QB-8150-LNK-100; QB-8151-EPR/LNK QB-8200-EPA / LNK; QB-8250-EPR / LNK MP-8150-CPE; MP-8160-CPE-A100;

QB-8150-LNK-12; QB-8150-LNK-50 15 seconds

To use this procedure, use a PoE injector with Reload functionality. The device operating image will get deleted, if you press the button for more than the above mentioned time. The timings mentioned above are valid from the time the device is powered UP (that is during POST). The device now reboots and comes with: IP Address: 169.254.128.132;

Username: admin; and Password: public

Tsunami 800 & 8000 Series - Software Management Guide 284 8.9.2 Bootloader Mode Troubleshooting S.No 1 Scenario Recovery Procedure a) The device operating image is corrupted for reasons such as power interruption while upgrading

(For 82x devices). b) The device operating image is corrupted for reasons such as power interruption while upgrading

(For all devices). 2 The device is not accessible for reasons such as user has forgotten the web interface login password, Management VLAN Id is changed, and wrong VLAN configuration. And, you do not have a reload capable PoE but Serial access is possible

Do one of the following:

No reload via Ethernet cross cable. It is not applicable to MP-825-CPE-50 and QB-825-EPR/LNK-50 devices. injector (use a pin or the end of a paper clip) for 15 seconds. By doing so, the operating image will get deleted. After powering-up the device, press and hold the Reload button on the PoE injector (use a pin or the end of a paper clip) for first 15 seconds and then release the button between 15-30 seconds. By doing so, the operating image will get deleted.

After deleting the operating image, refer s b and s P Y O j X i e U U a R e g P Y O d sections to load the firmware onto the device. U U P b U i O Q t

` While powering the device, press and hold the Reload button on the PoE

After deleting the operating image, refer s b and s O Y P g e R a U U e i X j O Y P d sections to load the firmware onto the device. U U P b U i O Q t If you are having serial access to the device during POST, press SHIFT+u to enter into forced user mode of the bootloader. From the Bootloader prompt, enter the command config_delete. If you are having serial access to the device during POST, press SHIFT+u to enter into forced user mode of the bootloader. From the Bootloader prompt, enter the command firmware_delete. Use a 4-pair (Gigabit) cross over Ethernet cable between the PoE and the device. By doing so, the reload functionality gets activated and forcibly deletes the operating image. The device now reboots and comes with: IP Address: 169.254.128.132;

Username: admin; and Password: public Next, issue the command reboot. e e g g a a R R 8.9.3 Load a New Image Follow one of the procedures below to load a new image to the device:

s s a a R R e e g g P P Y Y O O j X U i U e P U b U i U b O Q d t Tsunami 800 & 8000 Series - Software Management Guide 285 Troubleshooting

: A new image cannot be downloaded using Bootloader CLI onto MP-825-CPE-50, MP-8160-CPE-A100 and QB-825-EPR-50 as it does not provide a serial interface. 8.9.3.1 Using the ScanTool To download the firmware image to the device, you will need an Ethernet connection to the computer on which the TFTP server resides and to a computer that is running ScanTool (this is either two separate computers connected to the same network or a single computer running both programs). ScanTool automatically detects the device that does not have a valid software image. The TFTP Server and Image File Name screen so that you can download a new image to the device. (These fields Before starting the download process, you need to know the device IP Address, Subnet Mask, the TFTP Server IP Address, and the Image file name. Make sure the TFTP server is running and properly configured to point to the folder containing the image to be downloaded. Follow these steps to download a software image to the device by using ScanTool:

e R P R i b R i P R U e . Download Procedure Preparing to Download the Device Image parameters are enabled in the ScanTools are disabled, if ScanTool detects a software image on the device). See 1. Download the latest software from Y V U X

V R _ available when no image is installed on the device. 4. Set IP Address Type to Static. 2. Launch Proxims ScanTool.

V Z Z U

Q

P P

3. Highlight the entry for the device that you want to update and click Change.

: You need to assign static IP information temporarily to the device since its DHCP client functionality is not 5. Now enter the IP address, Subnet mask, Default-gateway, Server - IP address and the image filename. 6. Click OK. The device will reboot and the download starts automatically. 7. Click OK when prompted to return to the Scan List screen after the device has been updated successfully. 8. Click Cancel to close the ScanTool. After the download process is completed, the device will reboot and initialize. After successful initialization, the device is ready to be configured. 8.9.3.2 Using the Bootloader CLI To download the new device image, you will need an Ethernet connection to the computer on which the TFTP server resides. This can be any computer on the LAN or connected to the device with an Ethernet cable. You must also connect the device to a computer with a standard serial cable and use a terminal client. From the terminal, enter the CLI commands to set the IP address of the device and to download the device image. Preparing to Download the device image Before starting, you need to know the device IP Address, Subnet Mask, the TFTP Server IP Address, and the device image file name. Make sure the TFTP server is running and configured to point to the default directory containing the image to be downloaded. Tsunami 800 & 8000 Series - Software Management Guide 286

, and copy it to the default directory of the TFTP server. Troubleshooting

, and copy it to the default directory of the TFTP server. 2. Connect the device serial port to your computers serial port. 3. Open your terminal emulator program and set the following connection properties:

Com Port: COM1, COM2 and so on, depending on your computer 4. Under File > Properties > Settings > ASCII Setup, enable the Send line ends with line feeds option. Terminal Emulator program sends a line return at the end of each line of code. The terminal display shows Power On Self Tests (POST) activity. After approximately 30 seconds, a message indicates:

Starting ScanTool interface, press any key to enter CLI 5. After this message appears, press any key. Now the bootloader prompt appears as below:

Download Procedure Stop Bits: 1 Data Bits: 8 Baud Rate: 115200 Flow Control: None 1. Download the latest software from Y

5. Enter the following commands:

Parity: None P P Z

V

Z Q

U _ V R X U V 8.9.4.1 Hardware and Software Requirements Standard serial (RS-232) cable ASCII Terminal software

The device will reboot and then download the image file. When the download process is complete, configure the device. 8.9.4 Setting IP Address using Serial Port If the ScanTool fails to scan the device and users knows the login credentials then you can set the IP address for the device using serial port. Tsunami 800 & 8000 Series - Software Management Guide 287 Troubleshooting 8.9.4.2 Attach the Serial Port Cable 1. Connect one end of the serial cable to the device and the other end to a serial port on your computer. 2. Power on the computer and the device. 8.9.4.3 Initializing the IP Address using CLI After connecting the cable to the serial port, you can use the CLI to communicate with the device. CLI supports the most-generic terminal emulation programs. In addition, many web sites offer shareware or commercial terminal programs that you can download. Once the IP address has been assigned, you can use the HTTP interface or the Telnet to complete the configuration. Follow these steps to assign an IP address to the device:

1. Open your terminal emulation program and set the following connection properties:

Com Port: COM1, COM2, and so on depending on your computer Baud Rate: 115200 Data Bits: 8 Stop Bits: 1 Flow Control: None Parity: None The terminal display shows Power On Self Tests (POST) activity, and then displays the software version. It prompts you to enter the CLI username and password. The commands to enter the username and password are as follows:

This process may take up to 90 seconds. Subnet mask). 3. Change the IP address and other network values using the following CLI commands (use your own IP address and Tsunami 800 & 8000 Series - Software Management Guide 288 2. Enter the CLI Username and password. By default username is admin and password is public. The terminal displays a welcome message and then the CLI Prompt. Enter show ip as shown below:

Troubleshooting 4. After the device reboots, verify the new IP address by reconnecting to the CLI. Alternatively, you can ping the device from a network computer to confirm that the new IP address has taken effect. When a proper IP address is set, use HTTP interface or Telnet to configure the rest of the operating parameters of the device. 8.10 Spectrum Analyzer The ultimate way to discover whether there is a source of interference is to use a Spectrum Analyzer. Usually, the antenna is connected to the analyzer when measuring. By turning the antenna 360, one can check the direction of the interference. The analyzer will also display the frequencies and the level of signal is detected. Proxim recommends performing the test at various locations to find the most ideal location for the equipment. 8.10.1 Avoiding Interference When a source of interference is identified and when the level and frequencies are known, the next step is to avoid the interference. Some of the following actions can be tried:

Change the channel to a frequency that has no or least interference. Try changing the antenna polarization. A small beam antenna looks only in one particular direction. Because of the higher gain of such an antenna, lowering the output power or adding extra attenuation might be required to stay legal. This solution cannot help when the source of interference is right behind the remote site. Adjusting the antenna angle/height can help to reduce the interference. Move the antennas to a different location on the premises. This causes the devices to look from a different angle, causing a different pattern in the reception of the signals. Use obstructions such as buildings, when possible, to shield from the interference. 8.10.2 Conclusion A spectrum analyzer can be a great help to identify whether interference might be causing link problems on the device. Before checking for interference, the link should be verified by testing in an isolated environment, to make sure that the hardware works and your configurations are correct. The path analysis, cabling and antennas should be checked as well. Base Announces should increase continuously. Registration Requests and Authentication Requests should be divisible by 3. WORP is designed in a way that each registration sequence starts with 3 identical requests. It is not a problem if, once in a while, one of those requests is missing. Missing requests frequently is to be avoided. Tsunami 800 & 8000 Series - Software Management Guide 289

Troubleshooting same on both sides. This should be the case if output power is the same. Two different RSLs indicate a broken transmitter or receiver. A significant difference between Local Noise and Remote Noise could indicate a source of interference near the site with the highest noise. Normally, noise is about 80 dBm at 36 Mbps. This number can vary from situation to situation, of course, also in a healthy environment.

` Monitor / Per Station (Information per connected remote partner): Check that the received signal level (RSL) is the 8.11.1 Unable to Retrieve Event Logs through HTTPS 8.11 Miscellaneous If using Internet Explorer 7 and are not able to retrieve event logs through HTTPS, do the following:

1. Open Internet Explorer 2. Navigate to Tool > Internet Options > Advanced 3. Go to Security and uncheck/unselect Do not save encrypted pages to disk Alternatively, use Mozilla Firefox 3.5 or later. Tsunami 800 & 8000 Series - Software Management Guide 290 Feature Applicability Given below are the feature(s) applicable to the respective point-to-point devices:

Tsunami 800 & 8000 Series - Software Management Guide 291 Given below are the feature(s) applicable to the respective point-to-multipoint devices:

Feature Applicability Tsunami 800 & 8000 Series - Software Management Guide 292 Parameters Requiring Reboot Given below are the parameters that require the device to reboot. Parameter(s) Web Page(s) Applicable Device Mode*

System Configuration Radio Mode Frequency Domain BASIC CONFIGURATION ADVANCED CONFIGURATION -> System BASIC CONFIGURATION ADVANCED CONFIGURATION -> System Network Mode ADVANCED CONFIGURATION -> System Maximum MTU ADVANCED CONFIGURATION -> System ADVANCED CONFIGURATION -> System ADVANCED CONFIGURATION -> System IP Configuration (Bridge Mode) BASIC CONFIGURATION ADVANCED CONFIGURATION -> Network -> IP Configuration IP Configuration (Routing Mode) BASIC CONFIGURATION ADVANCED CONFIGURATION -> Network -> IP Configuration Frequency Filter Lower Edge Frequency Filter Upper Edge Ethernet Default Gateway IP Address DNS Ethernet Wireless Wireless (With PPPoE) Default Gateway IP Address DNS (Primary and Secondary Address) All All All All All All All All All All All SU Mode All All Status ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Dynamic Start Port ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Dynamic End Port ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode NAT Status ADVANCED CONFIGURATION -> Network -> PPPoE Client SU Mode Admin Status ADVANCED CONFIGURATION -> Network -> Ethernet All Ethernet Interface Properties PPPoE Tsunami 800 & 8000 Series - Software Management Guide 293 Parameters Requiring Reboot Parameter(s) Web Page(s) Applicable Device Mode*

Channel Bandwidth BASIC CONFIGURATION ADVANCED CONFIGURATION -> Wireless -> Interface1 ->

Properties All Wireless Properties Channel Offset ADVANCED CONFIGURATION -> Wireless -> Properties Applicable only to, Auto Channel Selection Legacy Mode BASIC CONFIGURATION ADVANCED CONFIGURATION -> Wireless -> Interface1 ->

Properties BASIC CONFIGURATION ADVANCED CONFIGURATION -> Wireless -> Interface1 ->

Properties Applicable only to BSU. Applicable only to, MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-CPE-50 MP-8150-CPE MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE-A100 QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

QB-8150-LNK-12/50 MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-CPE-50 MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-CPE MP-8150-SUR-100 MP-8200-BSU MP-8200-SUA MP-8250-BS9 MP-8250-BS1 MP-8250-SUR Frequency Extension ADVANCED CONFIGURATION -> Wireless -> Interface1 ->

All Properties -> MIMO Properties -> MIMO Upgrade Firmware MANAGEMENT -> File Management -> Upgrade Firmware All Upgrade Firmware and Configuration Tsunami 800 & 8000 Series - Software Management Guide 294 Parameters Requiring Reboot Web Page(s) Applicable Device Mode*

MANAGEMENT -> File Management -> Upgrade Configuration All HTTP / HTTPS MANAGEMENT -> Services -> HTTP / HTTPS All All All All All Parameter(s) Upgrade Configuration Admin Password Monitor Password HTTP HTTP Port HTTPS Parameter(s) Web Page(s) Applicable Device Mode*

SNMP (If SNMP v1-v2c is enabled) SNMP Version Read Password Read / Write Password SNMP Trap Host Table SNMP Version Security Level Priv Protocol Priv Password Auth Protocol Auth Password SNMP Trap Host Table MANAGEMENT -> Services -> SNMP SNMP (If SNMP v3 is enabled) MANAGEMENT -> Services -> SNMP Telnet / SSH All All All All All All All All All All All All All Tsunami 800 & 8000 Series - Software Management Guide 295 Parameters Requiring Reboot Web Page(s) Applicable Device Mode*

Parameter(s) Admin Password Monitor Password Telnet Telnet Port Telnet Sessions SSH SSH Port SSH Sessions Access Table Status Management Access Control Table MANAGEMENT -> Services -> Telnet / SSH Management Access Control MANAGEMENT -> Access Control All All All All All All All All All All All Reset to Factory MANAGEMENT -> Reset to Factory Convert QB to MP MANAGEMENT -> Convert QB to MP Applicable only to

* BSU: Refers to a Base Station SU Mode: Refers to both SU and CPE End Point A Mode: Refers to a device in End Point A mode End Point B Mode: Refers to a device in End Point B mode QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8200-LNK Tsunami 800 & 8000 Series - Software Management Guide 296 Frequency Domains and Channels Introduction The Tsunami point-to-point and point-to-multipoint products are available in two SKUs: United States (US) and rest of the World (WD) markets. Depending on the SKU, the device is hard programmed at factory per the regulatory domain. Regulatory domain controls the list of frequency domains that are available in that SKU. Further each frequency domain will define the country specific regulatory rules and frequency bands. The frequency domains can be easily configured using the Web Interface as it is a drop down list with all the available domains. The following table lists all the Tsunami 800 and 8000 Series products with the applicable frequency domains and their corresponding ENUM values, SKUs supported and licensed frequency bands. US Frequency Domains Point to Multipoint Devices Product(s) MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8150-CPE MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR MP-820-BSU-100 MP-820-SUA-50+

MP-825-CPE-50 MP-825-SUR-50+

Licensed Bands (in GHz) 2.4, 4.9, 5.0 5.0 5.0 4.9, 5.0 5.0 i s n a m o D y c n e u q e r F United States 5 GHz - US*

United States 5.8 GHz - US*

United States 2.4 GHz - US*

US2 (5.3 and 5.8GHz) - US*

United States 4.9 GHz l s e u a V M U N E 1 2 3 22 28 Point to Point Devices Product(s) QB-8100-EPA/LNK QB-8150-EPR QB-8150-LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8150-LNK-12#

QB-8150-LNK-50 QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

US 2.4, 5.0 US 5.0 US 5.0 US 4.9, 5.0 US 5.0 Licensed Bands (in GHz) United States 5 GHz - US*

United States 5.8GHz - US*

United States 2.4 GHz - US*

US2 (5.3 and 5.8GHz) - US*

United States 4.9 GHz s n i a m o D y c n e u q e r F 1 2 3 22 28 s e u l a V M U N E Tsunami 800 & 8000 Series - Software Management Guide

297 World Frequency Domains Frequency Domains and Channels Product(s) MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-CPE MP-8150-SUR-100 Point to Multipoint Devices MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-CPE-50 Licensed Bands (in GHz) WD 2.4, 4.9, 5.0 WD 4.9, 5.0 WD 5.0 WD 6.4 WD 4.9, 5.0 WD 5.0 i s n a m o D y c n e u q e r F World 5 GHz World 4.9 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Canada 5 GHz WD Europe 5.8 GHz WD Europe 5.4 GHz WD-Europe 2.4 GHz Russia 5 GHz Taiwan 5 GHz WD United States 5 GHz Canada 5.8 GHz World 6.4 GHz WD UK 5.8 GHz World 5.9 GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz Australia 5.4 GHz Australia 5.8 GHz WD United States 4.9 GHz Canada 4.9 GHz WD Japan 4.9 GHz Legacy 5GHz WD Japan 5.6 GHz WD United States 5.8 World 5.8 GHz Indonesia 5.7 GHz l s e u a V M U N E 4 5 6 7 8 9 10 11 12 13 14 15 16 17 20 21 23 24 25 26 27 29 30 31 32 33 34 40 41 Tsunami 800 & 8000 Series - Software Management Guide 298 Frequency Domains and Channels Point to Point Devices Product(s) QB-8100-EPA/LNK QB-8150-EPR QB-8150-LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8150-LNK-12#

QB-8150-LNK-50 QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

Licensed Bands (in GHz) WD 2.4, 4.9, 5.0 WD 4.9, 5.0 WD 5.0 WD 4.9, 5.0 WD 5.0 i s n a m o D y c n e u q e r F World 5 GHz World 4.9 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Canada 5 GHz WD-Europe 5.8 GHz WD-Europe 5.4 GHz WD-Europe 2.4 GHz Russia 5 GHz Taiwan 5 GHz WD United States 5 GHz Canada 5.8 GHz World 6.4 GHz World UK 5.8 GHz World 5.9 GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz Australia 5.4 GHz Australia 5.8 GHz WD United States 4.9 GHz Canada 4.9 GHz WD Japan 4.9 GHz Legacy 5 GHz WD Japan 5.6 GHz WD United States 5.8 GHz World 5.8 GHz Indonesia 5.7 GHz l s e u a V M U N E 4 5 6 7 8 9 10 11 12 13 14 15 16 17 20 21 23 24 25 26 27 29 30 31 32 33 34 40 41 Tsunami 800 & 8000 Series - Software Management Guide 299 Europe and Japan Frequency Domains Frequency Domains and Channels Point to Multipoint Devices Product(s) MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-CPE-50 Licensed Bands (in GHz) EU 2.4, 4.9, 5.0 EU 4.9, 5.0 EU 4.9, 5.0 JP 4.9, 5.0 EU 4.9, 5.0 EU 5.0 i s n a m o D y c n e u q e r F Japan 2.4 GHz Japan 4.9 GHz UK 5.8 GHz Europe 5.8 GHz Europe 5.4 GHz Europe 2.4 GHz Japan 5.6 GHz l s e u a V M U N E 18 19 35 36 37 38 39 Point to Point Devices Product(s) QB-8100-EPA/LNK QB-8150-EPR QB-8150-LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

Licensed Bands (in GHz) EU 2.4, 4.9, 5.0 EU 4.9, 5.0 JP 4.9, 5.0 EU 4.9, 5.0 EU 5.0 i s n a m o D y c n e u q e r F Japan 2.4 GHz Japan 4.9 GHz UK 5.8 GHz Europe 5.8 GHz Europe 5.4 GHz Europe 2.4 GHz Japan 5.6 GHz l s e u a V M U N E 18 19 35 36 37 38 39 When the device is configured by using CLI or SNMP, care has to be taken to set the domains by using a predefined ENUM value. Example: The CLI commands to set WORLD 5 GHz as frequency domain are as follows:

D

6

A

1 6

7

. 7

9

C 0

. 5

B

6

2

E

8

D

0

1

7

2

9

0

1

1

3

4

4

E

) 1

, 0

. 9

0

1

1

1

1

7

G 0

7

9

9

0 4

0 2

9 9

1

. G 7

. 5 1 1

1

0 0

. B

. 1

. 5

3

4 4 4

4

5 7 7

1

0

F 1

. 4

1

. 9 0

, 4

7

300 Tsunami 800 & 8000 Series - Software Management Guide Frequency Domains and Channels

: All DFS countries support only 20 and 40 MHz channel bandwidths. 2.4 GHz Channels Frequency Frequency Allowed Channels (Center Frequency in GHz) Domain Band

(Start Frequency ~

End Frequency in MHz) United States 2.4 GHz 2412 ~ 2462 World 2.3 GHz 2277 ~ 2397 World 2.4 GHz 2412 ~ 2472 World 2.5 GHz 2477 ~ 2507 WD-Europe 2.4 GHz 2412 ~ 2472 Europe 2.4 GHz 2412 ~ 2472 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz 1 (2412), 2 (2417)... 10 (2457), 11 (2462). US SKU 1 (2412), 2 (2417)... 10 (2457), 11 (2462). World SKU 1 (2412), 2 (2417)... 10 (2457), 11 (2462). 1 (2412), 2 (2417)... 6 (2437), 7 (2442). 5 (2432), 6 (2437)... 10 (2457), 11 (2462). 100 (2277), 101 (2282)... 123 (2392), 124 (2397). 100 (2277), 101 (2282)... 122 (2387), 123 (2392). 101 (2282), 102 (2287)... 121(2382), 122 (2387). 101 (2282), 102 (2287)... 117 (2362), 118 (2367). 105 (2302), 106(2307)... 121(2382), 122 (2387). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 200(2477), 201(2482)... 205 (2502), 206(2507). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 200(2477), 201(2482)... 205 (2502), 206(2507). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). EU SKU 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 201(2482), 202 (2487)... 204(2497), 205 (2502). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 8 (2447), 9 (2452). 5 (2432), 6 (2437)... 12 (2467), 13 (2472).

1 (2412), 2 (2417)... 8 (2447), 9 (2452). 5 (2432), 6 (2437)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 8 (2447), 9 (2452). 5 (2432), 6 (2437)... 12 (2467), 13 (2472). Tsunami 800 & 8000 Series - Software Management Guide 301 Frequency Domains and Channels 4.9 and 5 GHz Channels Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Domain

(Start Frequency ~

End Frequency in MHz) 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz United States 5 GHz

5260 ~ 5320 (DFS) 5500 ~ 5580 (DFS) 5660 ~ 5700 (DFS) 5745 ~ 5825 (non-DFS) US SKU

5740 ~ 5830 (Non-DFS) United States 5.8 GHz 148(5740), 149(5745)... 165(5825), 166(5830). United States2 (5.3, 5.8 GHz) 5260 ~ 5320 (DFS) 5745 ~ 5825 (Non-DFS)

149(5745), 150(5750)... 164(5820), 165(5825).

4942 ~ 4987 (Non-DFS) United States 4.9 GHz 5(4942.5), 15(4947.5)... 85(4982.5), 95(4987.5). 10(4945), 20(4950)... 80(4980), 90(4985). Japan SKU 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 133(5665), 134(5670)... 135(5675), 136(5680). 149(5745), 150(5750)... 160(5800), 161(5805). 149(5745), 150(5750)... 160(5800), 161(5805). 52(5260), 53(5265)... 59(5295), 60(5300). 149(5745), 150(5750)... 160(5800), 161(5805). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 164(5820), 165(5825). 153(5765), 154(5770)... 164(5820), 165(5825). 56(5280), 57(5285)... 63(5315), 64(5320). 153(5765), 154(5770)... 164(5820), 165(5825).

52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 164(5820), 165(5825). 149(5745), 150(5750)... 164(5820), 165(5825). 52(5260), 53(5265)... 63(5315), 64(5320). 149(5745), 150(5750)... 164(5820), 165(5825). 20(4950), 30(4955)... 70(4975), 80(4980). Japan 4.9 4912 ~ 4980 (Non-DFS) 182(4912.5), 183(4917.5)... 188(4942.5), 189(4947.5). 183(4915), 184(4920)... 188(4940), 189(4945). 184(4920), 188(4940)... 192(4960), 196(4980). 184(4920), 185(4925), 191(4955)... 192(4960). 188(4940), 189(4945), 195(4975)... 196(4980). Tsunami 800 & 8000 Series - Software Management Guide 302 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS 40 MINUS Domain

(Start Frequency ~

End Frequency in MHz) 5 MHz Japan 5.6 5500 ~ 5700 (DFS)

WD United States 5 GHz 5255 ~ 5325 (DFS) 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS) 5740 ~ 5830 (non-DFS) World SKU

100(5500) 104(5520) 108(5540) 112(5560) 116(5580) 120(5600) 124(5620) 128(5640) 132(5660) 136(5680) 140(5700) 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 164(5820), 165(5825) 32(5160), 33(5165)... 213(6065), 214(6070). MHz MHz 100(5500) 108(5540) 116(5580) 124(5620) 136(5680) 104(5520) 112(5560) 120(5600) 128(5640) 140(5700) 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 133(5665), 134(5670), 135(5675), 136(5680). 149(5745), 150(5750)... 160(5800), 161(5805). 32(5160), 33(5165)... 209(6045), 210(6050). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 164(5820), 165(5825). 36(5180), 37(5185)... 213(6065), 214(6070). 186(4930), 187(4935), 188(4940), 10(4945), 20(4950) 90(4985), 100(4990). World 5 GHz 5155 ~ 6075 (Non-DFS) Please note that 8200 &

82x SKUs support upto 5920 MHz frequency. 4905 ~ 4995 (Non-DFS) World 4.9 GHz 31(5155), 32(5160)... 214(6070), 215(6075). 31(5155), 32(5160)... 214(6070), 215(6075). 181(4905), 182(4910) 187(4935), 188(4940). 10(4945), 20(4950) 100(4990), 110(4995). 181(4905), 182(4910) 187(4935), 188(4940). 10(4945), 20(4950) 100(4990), 110(4995). 182(4910), 183(4915) 187(4935), 188(4940). 10(4945), 20(4950) 90(4985), 100(4990). 182(4910), 183(4915) 187(4935), 188(4940). 10(4945), 20(4950) 50(4965), 60(4970). Tsunami 800 & 8000 Series - Software Management Guide 303 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS 40 MINUS 5 MHz 176(5880), 177(5885)... 183(5915), 184(5920). 176(5880), 177(5885)... 183(5915), 184(5920). Domain World 5.9 GHz

(Start Frequency ~

End Frequency in MHz) 5880 ~ 5920 (Non-DFS) Canada 5 GHz 5255 ~ 5325 (DFS) 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS) WD-Europe 5.4 GHz 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS)

WD-Europe 5.8 GHz 5735 ~ 5870 (DFS)

Russia 5 GHz 5155 ~ 6075 (Non-DFS) Please note that 8200 &

82x SKUs support upto 5920 MHz frequency. 31(5155), 32(5160)... 214(6070), 215(6075). 31(5155), 32(5160)... 214(6070), 215(6075). Taiwan 5 GHz 5495 ~ 5705 (DFS) 5740 ~ 5810 (Non-DFS)

MHz MHz 177(5885) 178(5890) 179(5895) 181(5905) 182(5910) 183(5915) 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 149(5745), 150(5750) 168(5840), 169(5845). 32(5160), 33(5165)... 209(6045), 210(6050). 100(5500), 101(5505)... 135(5675), 136(5680). 149(5745), 150(5750)... 156(5780), 157(5785). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 172(5860), 173(5865). 36(5180), 37(5185)... 213(6065), 214(6070). 104(5520), 105(5525)... 139(5695), 140(5700). 153(5765), 154(5770)... 160(5800), 161(5805). 177(5885), 178(5890)... 182(5910), 183(5915). 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 172(5860), 173(5865). 32(5160), 33(5165)... 213(6065), 214(6070). 100(5500), 101(5505)... 139(5695), 140(5700). 149(5745), 150(5750)... 160(5800), 161(5805). Tsunami 800 & 8000 Series - Software Management Guide 304 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS 40 MINUS Domain India 5.8 GHz Canada 5.8 GHz

(Start Frequency ~

End Frequency in MHz) 5830 ~ 5870 (Non-DFS) 5735 ~ 5855 (Non-DFS) WD U.K 5.8 GHz 5730 ~ 5790 (DFS) 5820 ~ 5845 (DFS) Australia 5.4 GHz 5475 ~ 5595 (DFS) 5655 ~ 5720 (DFS) 5 MHz 166(5830), 167(5835)... 173(5865), 174(5870). 147(5735), 148(5740)... 170(5850), 171(5855).

166(5830), 167(5835)... 173(5865), 174(5870). 147(5735), 148(5740)... 170(5850), 171(5855).

Australia 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz 5730 ~ 5845 (Non-DFS) 146(5730), 147(5735) 168(5840), 169(5845). 146(5730), 147(5735)... 148(5740), 169(5845). 5475 ~ 5720 (DFS)

5730 ~ 5845 (Non-DFS) Canada 4.9 GHz 4945 ~ 4985 (Non-DFS) 146(5730), 147(5735)... 168(5840), 169(5845). 10(4945), 20(4950)... 80(4980), 90(4985). 146(5730), 147(5735)... 168(5840), 169(5845). 10(4945), 20(4950)... 80(4980), 90(4985). MHz MHz 167(5835) 168(5840) 169(5845) 171(5855) 172(5860) 173(5865) 148(5740), 149(5745)... 165(5825), 166(5830). 147(5735), 148(5740)... 152(5760), 153(5765). 152(5760), 153(5765)... 169(5845), 170(5850). 151(5755), 152(5760)... 156(5780), 157(5785). 96(5480), 97(5485) 113(5565), 114(5570). 132(5660), 133(5665) 138(5690), 139(5695). 147(5735), 148(5740)... 163(5815), 164(5820). 96(5480), 97(5485) 138(5690), 139(5695). 147(5735), 148(5740)... 163(5815), 164(5820). 100(5500), 101(5505) 117(5585), 118(5590). 136(5680), 137(5685) 142(5710), 143(5715). 151(5755), 152(5760) 167(5835), 168(5840). 100(5500), 101(5505) 142(5710), 143(5715). 151(5755), 152(5760)... 167(5835), 168(5840). 20(4950), 30(4955), 40(4960). 60(4970), 70(4975), 80(4980). 167(5835), 168(5840)... 172(5860), 173(5865). 148(5740), 149(5745)... 169(5845), 170(5850). 147(5735), 148(5740)... 156(5780), 157(5785). 167(5835). 96(5480), 97(5485) 117(5585), 118(5590). 132(5660), 133(5665) 142(5710), 143(5715). 147(5735), 148(5740) 167(5835), 168(5840). 96(5480), 97(5485) 142(5710), 143(5715). 147(5735), 148(5740)... 167(5835), 168(5840). 20(4950), 30(4955)... 70(4975), 80(4980). Tsunami 800 & 8000 Series - Software Management Guide 305 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels Domain

(Start Frequency ~

End Frequency in MHz) Legacy 5GHz 5150 ~ 6080 (Non-DFS) Please note that 8200 &

82x SKUs support upto 5920 MHz frequency. 4912 ~ 4980 (Non-DFS) Please note that 8100 SKUs does not support this frequency. WD Japan 4.9 WD-Japan 5.6 5500 ~ 5700 (DFS)

5 MHz 30(5150), 31(5155)... 215(6075), 216(6080). 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz 30(5150), 32(5160)... 214(6070), 216(6080). 30(5150), 34(5170)... 210(6050), 216(6070).

182(4912.5), 183(4917.5)... 188(4942.5), 189(4947.5). 183(4915), 184(4920)... 188(4940), 189(4945). 184(4920), 188(4940), 192(4960), 196(4980). 184(4920) 192(4960) 188(4940) 196(4980) 100(5500) 104(5520) 108(5540) 112(5560) 116(5580) 120(5600) 124(5620) 128(5640) 132(5660) 136(5680) 140(5700) 20(4950), 30(4955)... 70(4975), 80(4980). 149(5745), 150(5750)... 164(5820), 165(5825). 145(5725), 146(5730)... 169(5845), 170(5850). 147(5735), 148(5740)... 162(5810), 163(5815). 100(5500) 108(5540) 116(5580) 124(5620) 136(5680) 104(5520) 112(5560) 120(5600) 128(5640) 140(5700)

149(5745), 150(5750)... 160(5800), 161(5805). 145(5725), 146(5730)... 165(5825), 166(5830). 147(5735), 148(5740)... 158(5790), 159(5795). 153(5765), 154(5770)... 164(5820), 165(5825). 149(5745), 150(5750)... 169(5845), 170(5850). 151(5755), 152(5760)... 162(5810), 163(5815). WD United States 4.9 GHz WD United States 5.8 GHz World 5.8 GHz 4942 ~ 4987 (Non-DFS) 5740 ~ 5830 (Non-DFS) 5720 ~ 5855 (Non-DFS) Indonesia 5.7 GHz 5730 ~ 5820 (Non-DFS) 5(4942.5), 15(4947.5)... 85(4982.5), 95(4987.5), 148(5740), 149(5745)... 165(5825), 166(5830). 144(5720), 145(5725)... 170(5850), 171(5855). 146(5730), 147(5735)... 163(5815), 164(5820). 10(4945), 20(4950)... 80(4980), 90(4985). 149(5745), 150(5750)... 164(5820), 165(5825). 144(5720), 145(5725)... 170(5850), 171(5855). 146(5730), 147(5735)... 163(5815), 164(5820). Tsunami 800 & 8000 Series - Software Management Guide 306 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Domain

(Start Frequency ~

End Frequency in MHz) 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz Frequency Domains and Channels U.K 5.8 GHz 5730 ~ 5790 (DFS) 5820 ~ 5845 (DFS) Europe 5.8 GHz 5735 ~ 5870 (DFS) Europe 5.4 GHz 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS)

EU SKU

147(5735), 148(5740)... 156(5780), 157(5785). 167(5835) 149(5745), 150(5750)... 172(5860), 173(5865). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 147(5735), 148(5740)... 152(5760), 153(5765). 151(5755), 152(5760)... 156(5780), 157(5785). 149(5745), 150(5750) 168(5840), 169(5845). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 153(5765), 154(5770)... 172(5860), 173(5865). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). Tsunami 800 & 8000 Series - Software Management Guide 307 Frequency Domains and Channels 6.4 GHz Channels Frequency Frequency Band Allowed Channels (Center Frequency) Domain

(Start Frequency ~

End Frequency in MHz) World 6.4 GHz 5905 ~ 6420 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz 181 (5905), 182 (5910)... 283 (6415), 284 (6420). 181 (5905), 182 (5910)... 283 (6415), 284 (6420). 182 (5910), 183 (5915)... 282 (6410), 283 (6415). 182 (5910), 183 (5915)... 278 (6390), 279 (6395). 186 (5930) 187 (5935)... 282 (6410), 283 (6415).

: The center frequency listed in the above tables are based on channel offset set to 0. If channel offset is set to any value other than 0 then the center frequency will be shifted accordingly. You can set the channel offset ranging from

-2 in MP-8150-CPE, MP-8160-BSU, MP-8160-SUA, MP-8160-CPE-A100, MP-825-CPE-50, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-8150-EPR/LNK-12/50, QB-825-EPR/LNK-50, and QB-825-EPR/LNK-50+. to +2 MHz Details for 40MHz Bandwidth While choosing 40MHz bandwidth, you can select 40 PLUS (Upper Extension) or 40 MINUS (Lower Extension). 40 PLUS means the center frequency calculation is done for 20MHz and add another 20MHz to the top edge of 20MHz. 40 MINUS means the center frequency calculation is done for 20MHz and add another 20MHz to the bottom edge of 20MHz. For 40 PLUS 2.4GHz ->

Channel 1 = 2412 MHz Bandwidth starts from 2403 MHz and ends at 2442 MHz 5GHz ->

Channel 52 = 5260 MHz Bandwidth starts from 5251 MHz and ends at 5290 MHz Tsunami 800 & 8000 Series - Software Management Guide 308 6.4GHz ->

Channel 181 = 5910 MHz Bandwidth starts from 5901 MHz and ends at 5940 MHz Frequency Domains and Channels For 40 MINUS 2.4GHz ->

Channel 5 = 2432 MHz Bandwidth starts from 2403 MHz and ends at 2442 MHz 5GHz ->

Channel 56 = 5280 MHz Bandwidth starts from 5251 MHz and ends at 5290 MHz 6.4GHz ->

Channel 186 = 5930 MHz Bandwidth starts from 5901 MHz and ends at 5940 MHz Tsunami 800 & 8000 Series - Software Management Guide 309 Frequency Domains and Channels Tsunami 800 & 8000 Series - Software Management Guide 310 LACP - Device Management Tsunami Quickbridge devices that are part of the LACP link cannot be managed through the switches, so it is recommended to use the second Ethernet port for management.

When using second Ethernet port for management, ensure to disable Auto Shutdown for Ethernet2. See H L M P ). I O K N J STP/LACP Frames should be set to passthru. See Q plugged-in) or Gigabit 48 VDC Injector (GIG-POE-INJ-48VDC-T) (without 48 VDC power plugged-in). Directly connecting the Ethernet port2 of the device to the PC Ethernet NIC may damage the PC NIC port or Ethernet port on the switch.

: The second Ethernet port is POE out; it should be connected via a passive POE (Without the AC power Y X I K T P V N V T P Z U W U

J J R S R R S In this chapter, we have chosen the following two examples to explain the device management in the LACP link, by using the second Ethernet port. Example1 Tsunami 800 & 8000 Series - Software Management Guide 311 Figure D-1 Device Management with No VLAN LACP - Device Management In this example, we have considered a network with two QuickBridge links each supporting LACP mode. In this setup, VLAN is not configured on both LACP switches and devices. The Ethernet1 of all the devices is connected to the LACP port and is used for data transfer. To manage the devices, use a dedicated management Personal Computer per QuickBridge link. Use Ethernet2 port of the device to connect the Personal Computer.

: In Fail Over Mode (if one of the link goes down), the remote device of a particular link cannot be managed. Example2 Figure D-2 Device Management with VLAN In this example, we have considered a network with two QuickBridge links each supporting LACP mode. In this setup, Ethernet 1 of all the devices is connected to the LACP port, with no VLAN. The Ethernet 2 of all the devices is connected to the tagged VLAN management port with Spanning Tree enabled. To manage all the devices in the QuickBridge network, use one dedicated management Personal Computer connected to the untagged VLAN port of the switch. To manage the devices, configure same management VLAN Id on all the devices. The Ethernet 1 should be configured in transparent VLAN mode to allow data transfer. The Ethernet2 can be configured either in transparent mode or trunk mode to allow management traffic to the devices. With Spanning Tree enabled on the LACP Switches, you will be able to manage all the QuickBridge devices, even if one of the wireless link goes down. For VLAN configuration, refer \

H

W X U R N V T _ K N T Y P S Z

[ . Tsunami 800 & 8000 Series - Software Management Guide 312 QinQ The Subscribers and End Point devices support QinQ VLAN feature that enables service providers to use a single VLAN ID to support multiple customer VLANs by encapsulating the 802.1Q VLAN tag within another 802.1Q frame. The benefits with QinQ are as follows:

Increases the VLAN space in a provider network or enterprise backbone Reduce the number of VLANs that a provider needs to support within the provider network for the same number of customers Enables customers to plan their own VLAN IDs, without running into conflicts with service provider VLAN IDs Provides a simple Layer 2 VPN solution for small-sized MAN (Metropolitan Area Networks) or Intranet Provides customer traffic isolation at Layer 2 within a service provider network Consider a BSU and SU network, with QinQ (Double VLAN (Q in Q) Status) enabled on the SU. Subscriber:

Based on the Ethernet VLAN configuration on the Subscriber, the data packets are tagged as follows:

Different outer VLAN IDs can be configured for different SUs, but those VLAN IDs should also be configured on the In case of downlink traffic, SU always expects double tagged packet from the wireless side. If the outer VLAN tag BSU Ethernet.

: When Double VLAN is enabled on the device, the Port VLAN ID should not be set to -1.

: When Double VLAN is enabled on the device, the Access VLAN ID should not be set to -1. Transparent Mode: When QinQ is enabled, SU cannot be configured in the Transparent mode. Trunk Mode: SU expects a tagged packet (inner tag) and tags the packet with Service VLAN ID as outer tag. matches with Service VLAN ID then SU will untag the packet and forward to Ethernet. Based on Ethernet VLAN configuration, the data packets are handled accordingly. When the outer VLAN tag does not match the Service VLAN ID, the packet is dropped. Access Mode: SU double tags the packet with Access VLAN ID as inner tag and Service VLAN ID as outer tag. Trunk Mode: The outer tag of the packet arriving at the Ethernet side should match with the VLAN ID configured in the trunk table. Transparent Mode: When configured in transparent mode, ensure the data packet is double tagged. VLAN ID. 313 BSU always considers the first VLAN tag available in the packet; in case of double tagged packet it is the outer Base Station:

Tsunami 800 & 8000 Series - Software Management Guide QinQ Device Management From the BSU Ethernet side, the BSU/SU can be managed with a single VLAN tagged packet that matches the Management VLAN ID. From the SU Ethernet side, only SU can be managed with a single VLAN tagged packet that matches the Management VLAN ID; BSU cannot be managed from the SU Ethernet side.

In a QuickBridge link, Q-in-Q should be enabled either on an End Point A or an End Point B. The user configurable TPID is only used in the Service Provider VLAN tag. The Inner or customer VLAN tag should always have TPID as 0x8100. An Example:

The following diagram is the pictorial representation of how traffic flows in a QinQ enabled network. The Computer behind SU can be used to manage the SU. To manage BSU, connect another Computer to BSU Ethernet port through a VLAN switch with PVID as 100. Tsunami 800 & 8000 Series - Software Management Guide 314 BSU Redundancy The BSU Redundancy feature can help in reducing the network outage in case of the Primary BSU failure. This feature enables the SU to keep track of the Primary and the Secondary BSU availability through a proprietary protocol. This allows the SU to switch between the Primary and the Secondary BSU depending on the link status. If both the Primary and the Secondary BSU are not available, the SU attempts to find any other BSU within its network. Configuration Guidelines This feature is activated only on a SU. By default, it is disabled. Example The Primary and the Secondary BSU names should be unique. Use a non-empty string to enable this feature and an empty string to disable this feature. It is expected that the Primary and the Secondary BSUs are connected to the same L2 Broadcast domain and are configured with the same Network Name as the SU. When this feature is enabled, it is mandatory to configure both the Primary and the Secondary BSU name on the SU.

z

y y

a

b

e i u

k v a w b x y

q g z

f b

r Tsunami 800 & 8000 Series - Software Management Guide 315 Figure F-1 An Example - BSU Redundancy Feature b

c d e f g d h

g i j

k a b

l b m n l

o g d h i j p q g d n d

o s g j m g q k j n f g e i t Log Samples for BSU Redundancy SU - During Boot Up BSU Redundancy SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR: A1:46 A2:0 A3:40[dB]) at WORP port[ 0 ]. SU registered with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff) on channel 60(0x78043C) (SNR: A1:51 A2:0 A3:49[dB]) at WORP port[ 0 ]. After getting connected to the Primary BSU, the SU should discover the secondary BSU. Primary BSU Down - Connected to Secondary BSU SU is trying to register with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). Link Profile Index: 1. kernel:Worp: Link Profile Index: 1. Channel 60 is set as the current channel. Channel 160 is set as the current channel. SU received QoS Class: Unlimited Best Effort (indx: 1). SU received QoS Class: Unlimited Best Effort (indx: 1). SU unregistered from BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). Wireless: WORP Link Established with Primary BSU: BSU1 Wireless: SU discovered Secondary BSU:BSU2 on channel:60 Wireless: WORP Link Established with Secondary BSU: BSU2 1Wireless: WORP Link Established with Secondary BSU: BSU2 01:52:25 kernel:Worp: Link Profile Index: 1. 01:52:25: Wireless: WORP Link Established with Other BSU: BSU3 Connected to Other BSU 01:52:25 kernel:Worp: WARNING: Channel 100 is set as the current channel. 01:52:25 kernel:Worp: SU is trying to register with BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5). 01:52:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (index: 1). 01:52:25 kernel:Worp: SU registered with BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5) on channel 100(0xC80464) (SNR:

A1:58 A2:0 A3:54[dB]) at WORP port[ 0 ]. 01:54:35: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 01:54:35: Wireless: SU discovered Primary BSU:BSU1 on channel:160 SU should discover both the Primary and the Secondary BSU, and connect to the Primary BSU after the switch time interval. BSU Switch Time Interval - 15 Minutes 00:08:34: Wireless: SU discovered Primary BSU:BSU1 on channel:160 00:23:34 kernel:Worp: SU unregistered from BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 00:23:34 kernel:Worp: WARNING: Channel 0 is set as the current channel. 00:23:35 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 00:23:35 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). Tsunami 800 & 8000 Series - Software Management Guide 316 00:23:35 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR:

A1:43 A2:0 A3:36[dB]) at WORP port[ 0 ]. 00:23:35 kernel:Worp: Link Profile Index: 1. 00:23:35: Wireless: WORP Link Established with Primary BSU: BSU1 00:24:34: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 BSU Redundancy Connect to Primary BSU 01:59:25: Wireless: WORP Link Established with Other BSU: BSU3 02:02:25 kernel:Worp: SU unregistered from BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5).. 02:02:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 02:02:25: Wireless: SU discovered Primary BSU:BSU1 on channel:160 02:02:25 kernel:Worp: SU is trying to register with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 02:02:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). 02:02:25 kernel:Worp: SU registered with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff) on channel 60(0x78043C) (SNR:

A1:37 A2:0 A3:35[dB]) at WORP port[ 0 ]. 02:02:25: Wireless: WORP Link Established with Secondary BSU: BSU2 02:04:25 kernel:Worp: SU unregistered from BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 02:04:25 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 02:04:25 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0)

(SNR: A1:46 A2:0 A3:42[dB]) at WORP port[ 0 ]. 02:05:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 02:04:25: Wireless: WORP Link Established with Primary BSU: BSU1 No Response Message 03:32:25 kernel:Worp: WARNING: Channel 0 is set as the current channel. 03:32:25 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 03:32:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). 03:32:25 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR:

A1:45 A2:0 A3:42[dB]) at WORP port[ 0 ]. 03:32:25 kernel:Worp: Link Profile Index: 1. 03:32:25: Wireless: WORP Link Established with Primary BSU: BSU1 03:33:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 03:40:43: Wireless: Secondary BSU: BSU2 not Available Tsunami 800 & 8000 Series - Software Management Guide 317 Bootloader CLI and ScanTool Bootloader CLI The Bootloader CLI is a minimal subset of the normal CLI that is used to perform initial configuration of the device. The Bootloader CLI is available when the device embedded software is not running. This interface is only accessible through the serial interface, if:

The device does not contain a software image An existing image is corrupted An automatic (default) download of image over TFTP has failed The Bootloader CLI provides the ability to configure the initial setup parameters; and depending on this configuration, a software file is downloaded to the device during startup. The Bootloader CLI supports the following commands:

: Restore the factory settings The Bootloader CLI supports the following parameters (for viewing and modifying):

: Image file name (including the file extension) If the Bootloader fails to load the firmware from flash, it tries to get the firmware from the network. While trying to get firmware from the network, the device should be powered on using Ethernet 1 interface of the device. The default configuration of the Bootloader parameters are as follows:

: Print Online Help

: Reboot the device

: Set the parameters

: Show the parameters

: IP Address

: System Name

: Gateway IP Address

: Server IP Address

: IP Address Type

: Net Mask Parameter Value ipaddr netmask 169.254.128.132 255.255.255.0 gatewayip 169.254.128.132 systemname systemname serverip filename 169.254.128.133 imagename ipaddrtype dynamic Tsunami 800 & 8000 Series - Software Management Guide 318 Bootloader CLI and ScanTool command to set the parameter To Load the Firmware from the Network To Load the Firmware by using Dynamic IP Parameters 1. Set the ipaddrtype to dynamic 2. Run the BOOTP and TFTP Servers followed by device reboot command to view the parameters and their values, and use the When the device reboots, the device gets the IP Address and Boot filename from the BOOTP server. You need not change any of the default Bootloader parameters. After BOOTP succeeds, the device initiates a TFTP request with the filename it gets from BOOTP. To Load the Firmware by using Static IP Parameters ipaddrtype to static. 2. Run the TFTP Server followed by device reboot. command to set the IP parameters like ipaddr, serverip, filename and also set the parameter When the device reboots, the TFTP request is initiated with the value taken from the parameter filename. This request is sent to the IP address set as serverip. In this case, the TFTP Server should be reachable to the device. value. Use the 1. Use the ScanTool If you want to access the device with ScanTool, then the host running the ScanTool should also be in the same network as the device. The ScanTool broadcast requests are discarded by the routers if the device and the host running the ScanTool are in different network. This means that the ScanTool cannot discover the device. A device in Bootloader can be recognized by looking at the system description. If the system description does not contain any build number in braces, conclude that the device is in Bootloader mode. For example:

MP-8100-BSU-WD

- Description of the device vX.Y.Z - Firmware Version SN-11Pl15010031 - Serial Number BL-v1.3.1 - Bootloader version Figure G-1 Scan Tool View of a Device in Bootloader Mode (An Example) Tsunami 800 & 8000 Series - Software Management Guide 319 SNR Information Given below are the SNR values for the following devices:

QB-8151-EPR/LNK QB-8150-EPR/LNK QB-8100-EPA/LNK QB-8150-LNK-100 MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Modulation QPSK 1/2 BPSK 1/2 Single Single No of MCS Index MCS0 MCS1 Streams MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 2.4 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 10 15 21 23 26 29 30 32 12 20 22 23 27 30 36 39 86 86 84 82 80 79 79 78 86 84 82 80 80 79 78 78 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 10 16 21 23 26 29 31 32 14 21 23 23 27 30 35 38 86 86 84 82 80 79 78 78 86 84 82 80 80 79 77 77 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 12 21 21 23 25 27 30 32 14 21 22 24 30 34 37 39 86 86 84 82 80 78 77 77 86 84 82 80 78 78 77 76 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 81 108 162 216 243 270 30 60 90 120 180 240 270 300 26 26 26 30 33 37 40 42 16 26 28 32 35 37 43 45 80 80 79 77 77 76 75 75 80 80 79 77 77 76 75 75 Tsunami 800 & 8000 Series - Software Management Guide 320 SNR Information 5 GHz MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS0 BPSK 1/2 Single MCS1 QPSK 1/2 Single MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6 8 10 14 17 22 25 28 8 12 14 16 20 25 29 30 86 86 84 82 80 79 79 78 86 84 82 80 80 79 78 78 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 7 8 13 16 20 24 26 29 9 12 15 16 21 26 29 30 86 86 84 82 80 79 78 78 86 84 82 80 80 79 77 77 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 6 9 11 14 18 22 25 28 9 12 14 16 20 26 29 30 86 86 84 82 80 78 77 77 86 84 82 80 78 78 77 76 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 81 108 162 216 243 270 30 60 90 120 180 240 270 300 9 11 15 16 20 24 27 30 9 13 17 22 25 27 30 33 80 80 79 77 77 76 75 75 80 80 79 77 77 76 75 75 Given below are the SNR values for the following device(s) in legacy mode:

MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Data Rate 2.25 1.5 10 10 5 MHz Min SNR Modulation BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 3 4.5 6 9 12 14 17 20 2.4 GHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 GHz Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR 84 84 84 84 82 82 3 4.5 6 9 12 18 10 11 11 13 17 23 84 84 84 84 80 78 6 9 12 18 24 36 13 13 15 15 22 25 84 84 84 84 80 73 8 9 10 12 16 18 84 84 82 82 82 82 8 9 10 11 16 18 84 84 82 82 82 80 7 8 9 12 15 18 81 81 81 81 80 80 321 Tsunami 800 & 8000 Series - Software Management Guide SNR Information Modulation 5 MHz 2.4 GHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 GHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR 64QAM 2/3 12 64QAM 3/4 13.5 27 29 81 80 24 27 29 30 76 74 48 54 28 29 73 72 24 27 80 80 24 27 80 80 24 27 78 76 Given below are the SNR values for the following devices:

QB-8150-LNK-12/50 MP-8150-CPE Modulation QPSK 1/2 BPSK 1/2 MCS Index MCS0 MCS1 No of Streams Single Single MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 5 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 8 8 10 13 16 20 22 24 9 10 12 16 19 24 29 33 82 82 82 82 82 81 80 80 82 82 82 82 80 80 80 80 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 8 9 11 15 19 22 24 26 8 10 12 16 20 24 30 33 82 82 82 82 82 81 80 80 82 82 82 82 82 80 78 78 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 8 9 11 17 19 23 25 26 9 12 13 18 19 24 27 32 82 82 82 82 82 81 13.5 27 40.5 54 81 15 30 45 60 90 108 120 80 121.5 135 80 82 82 82 82 82 80 78 78 135 150 27 54 81 108 162 216 243 270 30 60 90 120 180 240 270 300 8 9 11 16 18 23 24 26 9 11 13 15 20 24 29 32 82 82 80 80 80 79 79 79 82 80 80 78 68 60 58 56 Tsunami 800 & 8000 Series - Software Management Guide 322 Given below are the SNR values for the following device(s) in legacy mode:

SNR Information QB-8150-LNK-12/50 MP-8150-CPE Modulation 5 MHz 5 GHz 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 1.5 2.25 3 4.5 6 9 12 64QAM 3/4 13.5 7 8 9 12 16 20 24 27 81 81 80 78 76 72 69 68 3 4.5 6 9 12 18 24 27 7 8 9 12 16 20 24 27 81 81 80 78 76 71 69 68 6 9 12 18 24 36 48 54 7 8 9 12 16 20 24 27 81 81 79 78 73 71 69 66 Given below are the SNR values for the following devices:

MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE Modulation QPSK 1/2 BPSK 1/2 MCS Index MCS0 MCS1 No of Streams Single Single MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 Dual Dual 6.4 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 6 8 10 13 16 21 22 24 8 10 87 87 86 84 80 74 70 67 87 87 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 6 8 10 14 16 21 23 24 8 10 87 87 84 84 78 70 67 65 87 87 6.5 13 19.5 26 39 52 58.5 65 13 26 6 7 10 13 16 20 22 24 7 11 87 87 86 82 76 70 67 65 86 84 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 30 60 7 8 12 13 19 21 24 27 10 12 87 86 82 74 70 62 56 55 86 82 Tsunami 800 & 8000 Series - Software Management Guide 323 SNR Information 6.4 GHz MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS10 QPSK 3/4 Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 9.7 13 19.5 26 29.3 32.5 15 16 20 25 27 28 84 80 74 70 66 64 19.5 26 39 52 58.5 65 13 17 23 24 27 29 84 80 74 66 62 62 39 52 78 104 117 130 13 17 20 24 27 29 82 78 71 65 62 62 81 108 162 216 243 270 90 120 180 240 270 300 15 18 22 25 27 30 75 74 56 55 53 52 Given below are the SNR values for the following devices:

QB-8250-EPR/LNK QB-8200-EPA/LNK MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR Modulation QPSK 1/2 BPSK 1/2 No of Single Single MCS Index MCS0 MCS1 Streams MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual 4.900 - 5.925 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 7 9 11 15 19 23 25 28 8 12 15 18 20 25 29 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 7 10 13 16 20 24 26 29 9 12 15 18 21 26 29 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 7 11 13 16 20 24 26 29 9 12 15 18 21 26 29 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 81 108 162 216 243 30 60 90 120 180 240 270 9 10 14 16 20 24 27 29 10 13 16 20 24 27 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 Tsunami 800 & 8000 Series - Software Management Guide 324 SNR Information MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS15 64 QAM 5/6 Dual 32.5 30 50 65 30 50 130 30 50 270 300 33 50 4.900 - 5.925 GHz Given below are the SNR values for the following device(s) in legacy mode:

MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR BPSK 1/2 BPSK 3/4 Modulation QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 4.900 - 5.925 GHz 5 MHz 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR 1.5 2.25 3 4.5 6 9 12 7 8 10 12 16 20 25 80 80 79 78 77 76 74 73 3 4.5 6 9 12 18 24 27 7 9 10 12 16 20 24 27 80 79 77 76 74 72 70 68 6 9 12 18 24 36 48 54 8 9 10 12 16 21 25 79 77 76 74 73 72 69 27 68 64QAM 3/4 13.5 27 Tsunami 800 & 8000 Series - Software Management Guide 325 Given below are the SNR values for the following device:

SNR Information QB-825-EPR/LNK-50 MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-CPE-50 QB-825-EPR/LNK-50 Modulation QPSK 1/2 BPSK 1/2 No of Single Single Streams MCS Index MCS0 MCS1 MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 5 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13.0 14.6 16.2 3.3 6.5 9.7 13.0 19.5 26.0 29.3 32.5 9 10 13 17 20 24 26 30 10 13 15 18 23 27 29 31 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 9 10 13 17 21 25 27 29 10 12 16 19 23 26 29 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 9 12 13 16 22 25 27 30 10 12 15 17 23 27 30 31 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 13.5 27 40.5 54 81 108 121.5 135 27 54 81 108 162 216 243 270

9 11 15 16 24 28 29 30 10 13 17 22 25 27 30 33 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 Tsunami 800 & 8000 Series - Software Management Guide 326 Given below are the SNR values for the following device in legacy mode:

SNR Information MP-820-BSU-100 MP-820-SUA-50+

MP-825-CPE-50 MP-825-SUR-50+

Modulation 10 MHz 20 MHz 5 GHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR 3 4.5 6 9 12 18 24 27 8 9 11 12 16 21 24 28 50 50 50 50 50 50 50 50 6 9 12 18 24 36 48 54 8 9 12 13 16 21 25 28 50 50 50 50 50 50 50 50 BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 64QAM 3/4 Tsunami 800 & 8000 Series - Software Management Guide 327 Configuration File Cross-loading across the Products Proxim portfolio comprises different product lines and SKUs which differ in features and capabilities depending on the hardware platform and the country setting or licensing used in them. This document describes the process to successfully apply the configuration file on a device(s) and the software checks run while applying the configuration file on a device(s). The user can apply a configuration file retrieved from a (Source) device to another compatible (Target) device. In order to successfully apply the configuration file, the following criteria should be met. 1. The Hardware Inventory Component ID should be same for both the source device and the target device. Hardware Inventory Component ID Products 2000 2001 2003 2005 2006 AP-800; AP-8000 MP-8100-BSU; MP-8100-SUA; MP-8150-SUR MP-8150-SUR-100 MP-8160-BSU; MP-8160-SUA; MP-8160-BS9 MP-8200-BSU; MP-8200-SUA; MP-8250-BS9/SUR QB-8xxx-EPA; QB-8xxx-EPR;

MP-8150-CPE Tsunami 82x Series AP-8100 Domains are listed below:

though they share the same component ID. and vice versa even though they share the same component ID. 2. The Regulatory Domain should be same in both the source device and the target device.The available Regulatory The configuration file can be applied only to the devices of the same family. The configuration file retrieved from an 8xx series device cannot be applied to a device from 81xx series. The configuration file of a MP-8160-BSU/MP-8160-SUA device cannot be applied to an 8100/8200 series device The configuration file of a MP-8150-CPE device cannot be applied to a MP-8160-CPE device and vice versa even WD SKU is compatible only with the EU SKU. For example, if the configuration file retrieved from a WD SKU If the above criteria are met, the configuration file can be successfully applied on the target device else an error message is thrown. Once the configuration file is loaded and the device is rebooted, the software tries to apply the new configuration file during the system boot-up process. device is loaded on a US or JP SKU target device then the upgrade fails. 328 Tsunami 800 & 8000 Series - Software Management Guide Configuration File Cross-loading across the Products Sometimes, a device from a particular product series may have different a license information compared to other devices of the same series. Therefore, the start-up process validates the configuration file against the license file of the device before applying the configuration file. The configuration file is valid, if the following conditions are met:

1. The input bandwidth limit in the configuration file should be less than or equal to the input bandwidth limit in the license file. 2. The output bandwidth limit in the configuration file should be less than or equal to the output bandwidth limit in the license file. 3. The sum of the input and output bandwidth limit in the configuration file should be less than or equal to the cumulative bandwidth limit in the license file. 4. The frequency band (2.4, 4.9, and 5 G Hz) in the configuration file should match with any one of the supported frequency bands in the license file. 5. The radio operation mode (BSU/SU/AP) in the configuration file should match with any one of supported radio operating modes in the license file. 6. The number of satellites in the configuration file should be less than or equal to the number of satellites in the license file. 7. The product family (TMP/TQB/AP) value in the configuration file should match the product family value in the license file. 8. Tx/Rx antenna chain mask in the configuration file should match the Tx/Rx antenna chain mask in the license file. during initialization and the device will boot-up with the last known good configuration. Before deleting the configuration file, an eventlog is generated about the violation of the license parameters. In some cases, if the last known good configuration does not exist internally, the device can reset the configuration to factory defaults and boot up. If any one of the above conditions is not met, the configuration file will be removed by the flash control module Tsunami 800 & 8000 Series - Software Management Guide 329 Abbreviations ACL ACS AES ALG ARP A Access Control List Automatic Channel Selection Advanced Encryption Standard Application Level Gateway Address Resolution Protocol ATPC Adaptive Transmit Power Control BSU Base Station Unit B C CCP CHAP CLI CIR CPE CRC DDRS DES DFS DHCP DNS DSL EIRP EOL ETSI Compression Control Protocol Challenge Handshake Authentication Protocol Command Line Interface Committed Information Rate Customer Premises Equipment Cyclic Redundancy Check D Dynamic Data Rate Selection Data Encryption Standard Dynamic Frequency Selection Dynamic Host Configuration Protocol Domain Name System Digital Subscriber Line E Equivalent Isotropically Radiated Power End of Life European Telecommunications Standards Institute F FCC Federal Communications Commission Tsunami 800 & 8000 Series - Software Management Guide 330 FCS Frame Check Sequence Abbreviations Gbps GPL GRE HTTP HTTPS IANA IC ICMP IGMP ISP ITS LACP LAN LCP LED LGPL MAN Mbps MD5 MIB MIMO MIR MP MPPE Gigabit Per Second General Public License Generic Routing Encapsulation G H HyperText Transfer Protocol HyperText Transfer Protocol Secure I Internet Assigned Numbers Authority (IANA) Industry Canada Internet Control Message Protocol Internet Group Management Protocol Internet Service Provider Intelligent Transportation System L Link Aggregation Control Protocol Local Area Network Link Configuration Protocol Light Emitting Diode Lesser General Public License M Metropolitan Area Networks Megabits Per Second Message-Digest algorithm Management Information Base Multiple-input and multiple-output Maximum Information Rate Multipoint Microsoft Point-to-Point Encryption MSCHAP v2 Microsoft Challenge-Handshake Authentication Protocol MTU Maximum Transmission Unit Tsunami 800 & 8000 Series - Software Management Guide 331 Abbreviations NAPT NAT NCP NBD NMS NOP PAP PC PoE PPPoE PTMP PTP PVES QB QoS N Network Address Port Translation Network Address Translation Network Control Protocol Next Business Day Network Management System Non Occupancy Period P Password Authentication Protocol Personal Computer Power Over Ethernet Point-to-point Protocol over Ethernet Point-to-multipoint Point-to-point ProximVision ES QuickBridge Quality of Service Q R RADIUS Remote Authentication Dial In User Service RAS RF RIP RMA RLT RSSI SHA SKU SNMP SNR SNTP SSH Remote Access Services Radio Frequency Routing Information Protocol Return Material Authorization Radio Link Test Received Signal Strength Indicator S Secure Hash Algorithm Stock Keeping Unit Simple Network Management Protocol Signal-to-noise Ratio Simple Network Time Protocol Secure Shell Tsunami 800 & 8000 Series - Software Management Guide 332 Abbreviations Secure Socket Layer Spanning Tree Protocol Subscriber Unit T Text Based Configuration Transmission Control Protocol Trivial File Transfer Protocol Temporal Key Integrity Protocol Transmit Power Control Tag Protocol Identifier Time to Live SSL STP SU TBC TCP TFTP TKIP TPC TPID TTL UDP UTP User Datagram Protocol Unshielded Twisted Pair VLAN Virtual Local Area Network U V W WEP WORP Wired Equivalent Privacy Wireless Outdoor Router Protocol Tsunami 800 & 8000 Series - Software Management Guide 333 Lightning Protection Lightning protection is used to maximize the reliability of the communications equipment by safely re-directing current from a lightning strike or a power surge traveling along the Cat 5/Cat5e/Cat 6 Ethernet cabling to the ground using the shortest path possible. Designing a proper grounding system prior to installing any communications equipment is critical to minimize the possibility of equipment damage, void warranties, and cause serious injury. The surge arrestor (sometimes referred to as a lightning protector) can protect your sensitive electronic equipment from high-voltage surges caused by discharges and transients at the PoE. Proxim Wireless offers superior lightning and surge protection for Tsunami series products. Contact your reseller or distributor for more information. Tsunami 800 & 8000 Series - Software Management Guide 334 Statement of Warranty Warranty Coverage Proxim Wireless Corporation warrants that its products are manufactured solely from new parts, conform substantially to specifications, and will be free of defects in material and workmanship for a Warranty Period of 1 year from the date of purchase. Repair or Replacement When Proxim determines that a returned product does not meet the warranted criteria during the warranty period, Proxim at its option, will either: (a) repair the defective product; (b) replace the defective product with a new or refurbished product that is at least equivalent to the original; or (c) refund the price paid for the defective product. Generally, products are repaired or replaced within thirty (30) business days of receipt of the product at a Proxim Logistical/Repair Center. The warranty period for repaired or replacement products is ninety (90) days or the remainder of the original warranty period, whichever is longer. These three alternatives constitute the customers sole and exclusive remedy and Proxims sole and exclusive liability under warranty provisions. Limitations of Warranty Proxims warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than Proxim, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by Proxim, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Buyers can contact Proxim Wireless Customer Service Center either by telephone or via web. Support and repair of products that are out of warranty will be subject to a fee. Contact information is shown below. Additional support information can be Contact technical support via telephone as follows:

. Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers USA and Canada Customers found at Proxim Wirelesss web site at General Procedures When contacting the Customer Service for support, Buyer should be prepared to provide the product description and serial number and a description of the problem. The serial number should be on the product. In the event the Customer Service Center determines that the problem can be corrected with a software update, Buyer might be instructed to download the update from Proxim Wirelesss web site or, if thats not possible, the update will be sent to Buyer. In the event the Customer Service Center instructs Buyer to return the product to Proxim Wireless for repair or replacement, the Customer Service Center will provide Buyer a Return Material Authorization (RMA) number and shipping instructions. Buyer must return the defective product to Proxim Wireless, properly packaged to prevent damage, shipping prepaid, with the RMA number prominently displayed on the outside of the container. Tsunami 800 and 8000 Series - Software Management Guide 335 Statement of Warranty Calls to the Customer Service Center for reasons other than product failure will not be accepted unless Buyer has purchased a Proxim Wireless Service Contract or the call is made within the warranty period. After the warranty period, Technical Support If Proxim Wireless reasonably determines that a returned product is not defective or is not covered by the terms of this Warranty, Buyer shall be charged a service charge and return shipping charges. Search Knowledgebase Other Information Create a Support Request

). is fee based (detailed in Proxim Wireless stores all resolved problems in a solution database at the following URL:

. Submit a question or open an issue to Proxim Wireless technical support staff at the following URL:

. Tsunami 800 and 8000 Series - Software Management Guide 336 Technical Services and Support Obtaining Technical Service and Support If you are having trouble using the Proxim product, please read this guide and the additional documentation provided with your product. If you require additional support to resolve your issue, please be ready to provide the following information before you contact Proxims Technical Services team:

If the product is not registered, date and location where you purchased the product

: Technical Support is free for the warranty period from the date of purchase. Part number and serial number of the suspected faulty device Network information (What kind of network are you using?) Circumstances that preceded or led up to the error Support Options Proxim eService Web Site Support Product information Registration information Trouble/error information ServPak account number Message or alarms viewed Trouble/symptom being experienced Activities completed to confirm fault Steps taken to reproduce the problem ServPak information (if a Servpak customer):

The Proxim eService Web site is available 7x24x365 at On the Proxim eService Web Site, you can access the following services:

Product Download Page: Provides quick links to product firmware, software, and documentation downloads. Proxim TV Links: A link to helpful video tutorials. Knowledgebase: A solution database of all the resolved problems. You can search by product, category, keywords, or phrases. Live Chat: Chat with a support technician on-line or request to call back at a later time. Create a Support Request: Create a support request with our technical support staff who will reply to you by email. Case Management: Login to check the status of your support cases, update your personal profile, or access restricted information and features. Provide Feedback: Submit a suggestion, complaint, or other feedback about the support site and our products. Tsunami 800 and 8000 Series - Software Management Guide 337 Telephone Support Contact technical support via telephone as follows:

Technical Services and Support USA and Canada Customers Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) ServPak Support To provide even greater investment protection, Proxim Wireless offers a cost-effective support program called ServPak. ServPak is a program of enhanced service support options that can be purchased as a bundle or individually, tailored to meet your specific needs. Whether your requirement is round the clock technical support or advance replacement service, we are confident that the level of support provided in every service in our portfolio will exceed your expectations. All ServPak service bundles are sold as service contracts that provide coverage for specific products from 1 to 3 years. Servpak bundles are considered an upgrade to the standard product warranty and not an extension. 24x7 Basic Technical Support Basic Advanced Replacement

(Two business days/

International economy shipment service) Priority Advanced Replacement

(Next business day/

International priority shipment service) Priority Comprehensive Advance Replacement

(Next business day/

International priority shipment service) 8x7 Advanced Technical Support Software Maintenance Access to Knowledge Base 24x7 Advanced Technical 24x7 Advanced Technical Support Support PVES & PV NMS PVES & PV NMS Support Support Post-Installation Optimization 50% discount on Onsite Technical Support and Services Tsunami 800 and 8000 Series - Software Management Guide 338 Technical Services and Support Additional Information on ServPak Options Advanced Replacement of Hardware In the event of a hardware failure, our guaranteed turnaround time for return to factory repair is 30 days or less. Customers who purchase this service are guaranteed replacement of refurbished or new hardware to be shipped out within one or two business days, as applicable. Options are available for shipment services depending on the customers support needs. Hardware is shipped on business days, Monday Friday excluding Holidays, 8:00 AM 3:30 PM Eastern Time. Comprehensive Advanced Replacement of Hardware In addition to ServPak Prime options, in the event of a hardware failure, Proxim will repair or replace the failed product for any reason, other than vandalism. 7x24x365 Availability Unlimited, direct access to technical support engineers 24 hours a day, 7 days a week, 365 days a year including Holidays. 8x5 Availability Unlimited, direct access to world-class technical support engineers 8 hours a day, 5 days a week, Monday through Friday from 8:00AM - 5:00PM Pacific Standard Time. Basic Technical Support Customers who purchase this service can be rest assured that their call will be answered by Proxims Tier 1 technical support and a case opened immediately to document the problem and provide initial troubleshooting to identify the solution and resolve the incident in a timely manner. Advanced Technical Support In addition to Proxims world-class Tier 1 technical support, customers will be able to have their more complex issues escalated to our world-class Tier 3 technical support engineers. Our Tier 3 engineers will review specific configurations to troubleshoot intricate issues and will also provide helpful insights regarding Proxims products and various tips from decades of collective experience in the wireless industry. Software Maintenance It's important to maintain and enhance security and performance of wireless equipment and Proxim makes this easy by providing a Software Maintenance program that enables customers to access new feature and functionality rich software upgrades and updates. Customers will also have full access to Proxim's vast Knowledgebase of technical bulletins, white papers and troubleshooting documents. Post-Installation Optimization You can consult with our technical support engineers to enhance performance and efficiency of your network. Post-installation optimization services include:

Review frequencies to select best possible channel Review Modulation, Channel Bandwidth, MIMO, and WORP settings to optimize throughput and link quality Review Satellite Density & TPC/ATPC settings Assistance with Bandwidth controls Tsunami 800 and 8000 Series - Software Management Guide 339 Technical Services and Support To purchase ServPak support services, please contact your authorized Proxim distributor. To receive more information or for questions at our website options, support visit the of

) or send an All Customers are entitled to free technical support for the Proxim products they purchase from Proxims authorized resellers

) and/or via telephone. This technical support will be provided for free for the entire time the product is covered by a Proxim warranty. The term of Proxims warranty is determined according to the agreement under which the product was sold and generally varies from 3 months to 2 years depending on the product. If a Customer disagrees with Proxims determination of warranty duration, a request for review supported by a copy of all product purchase documentation may be submitted. After the warranty period, technical support on products then being sold by Proxim will be based upon one of the following three options Customers can choose:

Customers can choose to purchase one of Proxims ServPak extended warranty and enhanced support packages for the product Customers can choose to purchase one-time per-incident technical support for the product for a fee Customers can choose to call the reseller or distributor who sold them the product for technical support Technical Support Policy Technical Support for Current Products after Warranty Period Technical Support for Current Products during Warranty Period

. on any please ServPak available Assistance with QoS, RADIUS, and VLAN settings on Proxim equipment

, call Proxim Support (For telephone numbers, see email to or distributors. Technical Support is defined as communication via the Proxim Support website (

No EOL ServPak support package is available for certain discontinued products Tech Support on Discontinued Products Technical Support on some products that Proxim has declared as EOL (End of Life) or otherwise is no longer selling is available based upon one of the following three options Customers can choose:

For some discontinued products, Customers can choose to purchase one of Proxims EOL ServPak support packages for the product No EOL ServPak support package will be available for any product discontinued more than 5 years ago Customers can choose to purchase one-time per-incident technical support for the product on a per hour basis at a rate of $125 an hour (4 hours minimum payable in advance by major credit card). This fee is payable in addition to any RMA fee that may be charged to subsequently repair the product. Customers can choose to call the reseller or distributor who sold them the product for technical support All Proxim technical support for discontinued products, whether through an EOL ServPak package or otherwise, is provided on a best effort basis and is subject to the continued availability of necessary components, equipment, and other technical resources. Note that Proxim is unable to support or warrant any equipment that has been modified, whether this modification is physical, or if third-party software codes have been loaded onto the product. Tsunami 800 and 8000 Series - Software Management Guide 340

 

 

 

 

 

 

8000 Series - Hardware Overview and Installation 3.4 MP-8160-CPE-A100 This section provides the hardware overview and installation method for MP-8160-CPE. 3.4.1 Hardware Overview A detailed description about the various components of the device are explained in the following sections. Figure 3-34 MP-8160-CPE 3.4.1.1 Ethernet Port (PoE IN and Data) The device comes with auto-sensing 10/100 BASE-T Ethernet port with configurable Tx Modes and Speeds. The Ethernet port of the device allows the user to connect to the LAN by using Cat5/Cat5e or better Ethernet cable, and also power ON the device by using the Power over Ethernet (PoE) Injector supplied with the product package. The device receives 48 VDC via a standard Cat5/Cat5e or better cable connected to the Ethernet port. Maximum power supplied to the device is 19.2 Watts. The device typically draws 5 Watts. Cat5/5e or better, STP, 24 AWG, UL rated, UV-shielded and outdoor-rated 100 ohms Type Impedance Cable Length 330 feet / 100 meters Recommended Ethernet Cable Specifications

: The total length of cabling between the Personal Computer and the device cannot exceed 100 meters (includes cable from the Personal Computer to the PoE, and the cable from the PoE to the device. Due to DC power requirements, the maximum cable length between the PoE Injector and the device is 75 meters.

: Always use a straight cable from PoE to the device. When you use a 4-pair cross over ethernet cable, the reload functionality gets activated and forcibly deletes the operating image. 3.4.1.2 Grounding Point To protect the device against lighting or ESD events, you must ground the device properly. To ensure proper grounding, use the grounding point situated at the bottom corner of the device and the grounding screw (M4 thread size) provided to attach a ground wire of at least 12 AWG stranded to the device. Tsunami 800 and 8000 Series - Hardware Installation Guide 81 8000 Series - Hardware Overview and Installation 3.4.2 Product Package Each shipment includes the items listed in the following table. Please verify that you have received all the parts in the shipment prior to installation. Whats in the Kit Image MP-8160-CPE PoE Injector and Power Cord WD - EU power cord Connector Weather Proofing Kit Pole Mounting Kit Grounding Kit Quick Installation Guide 3.4.3 Installation Procedure This section describes the steps to install and mount the device.

: The device must be installed by a trained professional who is familiar with radio frequency planning and regulatory limits. Perform the following steps to install and mount the device. Step 1: Plan for Installation There are several planning factors to be considered before installing the device. In addition to selecting the installation site, you should do the following:

Tsunami 800 and 8000 Series - Hardware Installation Guide 82 Calculate:

8000 Series - Hardware Overview and Installation Required RSL and fade margin to achieve link availability objectives. For more details on how to calculate RSL and fade margin, please refer to the Antenna Installation Guide and Proxim Link Calculator that are available on the support To make optimal use of the device, you must find a suitable location to install the hardware. Proxim recommends you do a site survey, observing the following requirements, before mounting the hardware. The location must allow easy disconnection of power to the radio, if necessary. Required transmission line types (like cable, waveguides) and lengths Step 2: Choose a Location Determine:

Plan for:

. Hardware mounting System Frequency Plan Required path availability Cable installation including egress Anticipated multi-path reflection points Lightning protection and system grounding Ensure free flow of air around the hardware. Devices continuous power consumption needs Pre-testing equipment (back-to-back test procedure) site at

Wire crimpers (if using connectors that are not pre-made) Large blade standard screwdriver Cross-tip screwdrivers Spanner 13 pole. pole. Step 5: Pole Mount the Device Step 4: Unpack the Product Package Unpack the device and its accessories from the shipping box. The radio device must be kept away from vibration and excessive heat. The installation must conform to local regulations at all times. Step 3: Gather Required Tools You should have the following tools available before installing the device:

Please make a note of the Ethernet addresses, MAC addresses and the serial number. These addresses may be used when configuring the device. Note that the serial number helps you to seek support from the Proxims Customer support team. 1. To pole-mount the device to a 1 inch diameter pole, place the mounting bracket with its small V-Groove facing the 2. To pole-mount the device to a 2.5 inch diameter pole, place the mounting bracket with its large V-Groove facing the 3. Place the device with its rear side facing the pole, and screw the M8x80mm long screws along with the spring and plain washers through the mounting bracket into the mounting holes of the device and tighten it to torque of 11 N.m/100 in-lbs. Tsunami 800 and 8000 Series - Hardware Installation Guide 83 8000 Series - Hardware Overview and Installation Figure 3-35 Pole-Mounting Step 6: Weatherproof RJ45 Connectors The following steps explain how to weatherproof the RJ45 connector:

1. Use a straight-through cable (Cat5/5e or better) with one end bare. 2. Connect the crimped RJ45 connector end of the cable into the RJ45 Ethernet port inside the enclosure. The cable connector should latch into the Ethernet port. 3. Slide the Flat Washer (A) into the Connector Body (B) to make it waterproof and onto the bare end of the cable. Next, fasten the Connector Body into the Ethernet connector hole on the device. 4. Slide the tube-shaped Compression Washer (C) into the Compression Ring (D) and onto the cable from the bare end, and insert into the fixed Connector Body. 5. Slide the Sealing Nut (E) over the bare end of the cable and fasten it on the fixed Connector Body. 6. Crimp the bare end of the cable with RJ45 connector and connect it to the LAN+DC port on the PoE Injector. Additional Weatherproofing Steps Figure 3-36 Weatherproofing RJ45 Connectors Step 7: Plug in the Cables To add an additional layer of protection to the connectors against the environment, see 

: Unscrew the sealing cap for installation of the cable.

1. Plug one end of the Cat5/5e cable into the Ethernet port of the device by following the Weatherproofing steps as explained in Step 5. Connect the other end of the Cat5/5e or better cable to the LAN +DC port on the PoE Injector.

Tsunami 800 and 8000 Series - Hardware Installation Guide 84 8000 Series - Hardware Overview and Installation

: Always use a straight cable from PoE to the device. When you use a 4-pair cross over ethernet cable, the reload functionality gets activated and forcibly deletes the operating image. Figure 3-37 Cables Plugged In 2. To connect the device through a hub or a switch to a Personal Computer, connect an Ethernet cable between the network interface card in the Personal Computer and the hub/switch, and between the hub/switch and the RJ45 LAN port on the PoE Injector. 3. To connect the device directly to a Personal Computer, connect an Ethernet cable between the network interface card in the Personal Computer and the RJ45 LAN port on the PoE Injector. Step 8: Install Surge Protector Proxim recommends two approved lightning surge protectors to be installed, one near to the device and the other at the building ingress point.

: To buy a suitable Surge Protector, place an order separately with your distributor. Perform the following steps to ensure proper surge protection:

1. Mount the surge protector near the outdoor device and use 10 AWG or larger wire to connect the protectors ground lug to the appropriate mounting ground point. The outdoor device and co-located surge protector should have a common grounding point using the shortest possible grounding cable. 2. Mount a second surge protector near the building ingress and use 10 AWG or larger wire to connect the surge protectors ground lug to earth ground as shown in the following figure. Tsunami 800 and 8000 Series - Hardware Installation Guide 85 Figure 3-38 Surge Protector 8000 Series - Hardware Overview and Installation

: Use Outdoor-rated, UV protected, shielded Cat5/Cat5e cable for the following. 3. Connect an RJ45 terminated cable between the indoor equipment and to the port on the surge protector at the building ingress. 4. Connect a short RJ45 terminated cable between the outdoor equipment and the port on the co-located surge protector. 5. Connect an RJ45 terminated cable between the two surge protectors on their remaining ports.

: Ensure to loop the cable before entering the premise to prevent water ingress. Step 9: Ground the Device To ensure proper grounding, use the grounding point situated at the bottom corner of the device and the grounding screw provided to attach a ground wire of at least 12 AWG stranded to the device. It is important that the following grounding guidelines are followed to protect the device against lighting or ESD events:

1. Connect one end of the grounding cable to the device and the other end to the closest earthing system point at the installation. 2. Cut any extra ground wire length when finished connecting it to the single point earth ground. 3. Avoid sharp bends and never loop or coil up the ground wire, always connect it straight to ground. 4. A good earth ground impedance is less than 1.0 ohm. 5. Make sure all connections are fastened securely and are tight. 6. Never install during a storm and always follow your local safety codes. Connect the grounding wire, which is supplied with the product package, to the grounding lug:

Step 10: Power ON the Device Figure 3-39 Ground the Device Plug in the power cord into a power outlet after having connected the PoE Injector and the device using Cat5/5e cable. There is no ON/OFF switch on the device. To disconnect power, unplug the RJ45 connector from the LAN+DC port on the PoE injector. Step 11: View LEDs When the device is powered on, it performs startup diagnostics. When startup is complete, the LEDs show the devices operational state. The LEDs are available at the devices Ethernet connector inside the enclosure. You can see the LED through the Ethernet connector. The LEDs will not be visible if the RJ45 connector is weatherproofed. Tsunami 800 and 8000 Series - Hardware Installation Guide 86 8000 Series - Hardware Overview and Installation The following table describes the status of LED:

Figure 3-40 LED Indicators LED State Ethernet Interface Power/Ethernet LED Wireless LED Off Amber No Power Radio is not present or failed to detect No Application Image detected

(ScanTool mode) Power is ON and device detects Reload signal Blinking Green Power is ON and the Ethernet link is DOWN Radio is detected but wireless link has not been established yet Solid Green Power is ON and the Ethernet link is UP Radio is detected and wireless link has been established Tsunami 800 and 8000 Series - Hardware Installation Guide 87 3.5 MP-8150-SUR-100 / QB-8150-LNK-100 This section provides the hardware overview and installation method for the following product(s):

8000 Series - Hardware Overview and Installation 3.5.1 Hardware Overview QB-8150-LNK-100 MP-8150-SUR-100 A detailed description about the various components of the device are explained in the following sections. Figure 3-41 MP-8150-SUR-100 / QB-8150-EPR-100 3.5.1.1 Gigabit Ethernet Port The device comes with one auto-sensing 10/100/1000 BASE-T Ethernet port with configurable Tx Modes and speeds. The Gigabit Ethernet port (PoE IN and Data) of the device allows the user to connect to the LAN by using Cat5e/Cat6 Ethernet cable, and also power ON the device by using the Power over Ethernet (PoE) Injector supplied with the product package. The device receives 48 VDC via a a standard Cat5e/Cat6 cable connected between the PoE and the device. Above 0 Celsius internal temperature, the device does not regulate its temperature, so the power drawn is generally lower in this temperature range. When the internal temperature gets close to the limits, the device starts to heat itself and the power draw increases. Powering the device when it is cold, triggers a special self-heat mode where the device is inoperable until the internal temperature is above -20 Celsius. This is signaled by a solid yellow LED on the Ethernet connector. Once the internal temperature is above -20 Celsius, the device boots normally. Maximum power supplied to the device is 32 Watts and the device typically draws 6 Watts. Cat5e/Cat6, STP, 24 AWG, UL rated, UV-shielded and outdoor-rated 100 ohms Recommended Ethernet Cable Specifications Type Impedance Cable Length 330 feet / 100 meters

: The total length of cabling between the Personal Computer and the device cannot exceed 100 meters (includes cable from the Personal Computer to the PoE, and the cable from the PoE to the device). Due to DC power requirements, the maximum cable length between the PoE Injector and the device is 75 meters.

: Always use a straight cable from PoE to the device. When you use a 4-pair cross over ethernet cable, the reload functionality gets activated and forcibly deletes the operating image. Tsunami 800 and 8000 Series - Hardware Installation Guide 88 8000 Series - Hardware Overview and Installation 3.5.1.2 Serial Port The Serial Port is used for debugging and management, and Audible Antenna Alignment through Command Line Interface

(CLI). The serial connection is established with an RJ11 to DB9 connector (also referred to as a dongle) by connecting the RJ11 end of the dongle connector to the device and the other end to your Personal Computer. The pin assignments for DB9 connector are as follows:

Figure 3-42 Serial Components D-Shell 1 2 3 4 5 6 7 8 9 RJ11 NC 2 4 NC 1 + 3 + 5 6 NC NC NC

: The pin6 on RJ11 connector is used as input for 12V DC IN for diagnostic purpose. Supplying power on this pin, when the device is powered by POE injector, might damage the device. 3.5.1.3 Grounding Point To protect the device against lighting or ESD events, you must ground the device properly. To ensure proper grounding, use either of the ground points that are situated at the bottom corner of the device and the grounding screw (#8-32 thread size) provided to attach a ground wire of at least 10 AWG stranded to the device. Tsunami 800 and 8000 Series - Hardware Installation Guide 89 8000 Series - Hardware Overview and Installation 3.5.2 Product Package Each shipment includes the items listed in the following table. Please verify that you have received all the parts in the shipment, prior to installation. Whats in the Kit Image MP-8150-SUR-100/

QB-8150-EPR-100 PoE Injector with Country specific Power Cord WD - US, UK and EU power cords US - US power cord EU - UK and EU power cords RJ11 to DB9 Serial Connector Connector Weather Proofing Kit EMI Toroid Grounding Kit Quick Installation Guide Tsunami 800 and 8000 Series - Hardware Installation Guide 90 8000 Series - Hardware Overview and Installation Whats in the Kit Mounting Kit and Hardware Image The mounting kit includes the following:

The following table lists the items included with the mounting kit:

Description Image Extension arm Mounting clamp for wall/pole Mounting plate to enclosure Mounting clamp for pole mounting Plain washer #5/16 Quantity 6 each 2 each Hex Cap Screw NC 5/16-18 x 35 2 each Nut NC 5/16-18 4 each Helical Spring Lock Washer #1/4 4 each Helical Spring Lock Washer #5/16 2 each Hex Cap Screw NC 5/16-18 x 80 4 each 68764, Screw, Machine, Pan, Philips, 1/4"-20, 5/8"L

: QB-8150-LNK-100 contains two sets of all the above accessories. 3.5.3 Installation Procedure This section describes the steps to install and mount the device(s).

: The device must be installed by a trained professional who is familiar with radio frequency planning and the regulatory limits. Tsunami 800 and 8000 Series - Hardware Installation Guide 91 8000 Series - Hardware Overview and Installation Perform the following steps to install and mount the device. Step 1: Plan for Installation There are several planning factors to be considered before installing the device. In addition to selecting the installation site, you should do the following:

Calculate:

Required RSL and fade margin to achieve link availability objectives. For more details on how to calculate RSL and fade margin, please refer to the Antenna Installation Guide and Proxim Link Calculator that are available on the support To make optimal use of the device, you must find a suitable location to install the hardware. The range of the radio device largely depends upon the position of the antenna. Proxim recommends you do a site survey, observing the following requirements, before mounting the hardware. The devices are designed to directly mount to a pole. Using the supplied brackets and hardware, you can mount them to a 1.25 inch to 3-inch pole (outside diameter). Longer bolts (not supplied) are required for mounting the device to a larger diameter pole. By using just one of the pole mounting brackets, you can mount the device to a wall or other flat surface. Step 2: Choose a Location Determine:

Plan for:

The location must allow easy disconnection of power to the radio, if necessary.

. Hardware mounting System frequency plan Required path availability Cable installation including egress Anticipated multi-path reflection points Lightning protection and system grounding Ensure free flow of air around the hardware. Devices continuous power consumption needs Pre-testing equipment (back-to-back test procedure) Required antenna mounting height to obtain proper path clearance Required transmission line types (like cable, waveguides) and lengths site at

Wire crimpers (if using connectors that are not pre-made) Weatherproofing material for sealing external connectors (such as butyl tape) The radio device must be kept away from vibration and excessive heat. The installation must conform to local regulations at all times. Large blade standard screwdriver Small blade standard screwdriver Adjustable 6 wrench Cross-tip screwdrivers Step 3: Gather Required Tools You should have the following tools available before installing the device:

Straight-through UV-protected STP-rated Cat5e/Cat6 Ethernet cable for connecting to PC, or cable for connecting to a hub or a switch. Tsunami 800 and 8000 Series - Hardware Installation Guide 92 8000 Series - Hardware Overview and Installation Step 4: Unpack the Product Package 1. Unpack the device and its accessories from the shipping box. 2. Please make a note of the Ethernet addresses, MAC addresses and the serial number. These addresses may be used when configuring the device. Note that the serial number helps you to seek support from the Proxims Customer support team. Step 5: Weatherproofing RJ45 Connectors The following steps explain how to weatherproof the RJ45 connectors:

1. Use a straight-through cable (Cat5e/Cat6) with one end bare. 2. Connect the crimped RJ45 connector end of the cable into the RJ45 Ethernet port inside the enclosure. The cable connector should latch into the Ethernet port. 3. Slide the Flat Washer (A) into the Connector Body (B) to make it waterproof and onto the bare end of the cable. Next, fasten the Connector Body into the Ethernet connector hole on the device. 4. Slide the tube-shaped Compression Washer (C) into the Compression Ring (D) and onto the cable from the bare end, and insert into the fixed Connector Body. 5. Slide the Sealing Nut (E) over the bare end of the cable and fasten it on the fixed Connector Body. 6. Crimp the bare end of the cable with RJ45 connector and connect it to the PWR LAN-OUT port on the PoE Injector. 7. Open the notch on both sides of the toroid and fix it on Ethernet cable. Then, lock the notch of the Toroid by pressing it.

: To avoid electro magnetic emissions, please ensure to fix Toroid to the Ethernet cable. Additional Weatherproofing Steps Figure 3-43 Weatherproofing RJ45 Connector Step 6: Assemble Mounting Hardware To add an additional layer of protection to the connectors against the environment, see 

Fix the Mounting Plate (A) by using the provided screws and washers (Torque 9 N.m/75 in-lbs) onto the bottom of the device. Fix the Extension Arm (B) to the fixed mounting plate with the provided screw, nut and washers. The extension arm gives the device more possible tilt, letting you adjust for azimuth or elevation over a larger angle. Fix the Mounting Bracket (C) to the fixed Extension Arm with the provided screw, nut and washers. Tighten the assembled parts (Torque 15 N.m/130 in-lbs). The last picture in the following figure shows the fully assembled mounting hardware fixed to the device.

Tsunami 800 and 8000 Series - Hardware Installation Guide 93 8000 Series - Hardware Overview and Installation Figure 3-44 Assemble the Mounting Hardware

: This figure is for illustration only. Device should be mounted in square position with Ethernet/Serial port facing downward. Step 7: Mount the Device 1. To pole-mount the device, insert the provided screws through bracket (F). Fasten around the pole to bracket (C) and secure (Torque 11 N.m/100 in-lbs). 2. To wall-mount the device, mount the bracket to a wall using 4 screws (not provided). Figure 3-45 Pole Mounting Figure 3-46 Wall Mounting Tsunami 800 and 8000 Series - Hardware Installation Guide 94 8000 Series - Hardware Overview and Installation Step 8: Plug in the Cables

: Unscrew the sealing cap for installation of the cable. Always use a straight cable from PoE to the device. When you use a 4-pair cross over ethernet cable, the reload functionality gets activated and forcibly deletes the operating image. 1. Plug one end of the straight-through Cat5e/Cat6 cable into the Ethernet Port interface of the device by following the Weatherproofing steps explained under Step 5. Connect the other end of the cable into the PWR LAN-OUT port on the PoE Injector. Figure 3-47 Cable Plugged In 2. Optionally, plug the Serial cable into the serial RJ11 telephone jack inside the enclosure for debugging and management, and audible antenna alignment. 3. To connect the device through a hub or a switch to a Personal Computer, connect an Ethernet cable between the network interface card in the Personal Computer and the hub, and between the hub and the RJ45 LAN-IN port on the PoE Injector. 4. To connect the device directly to a Personal Computer, connect an Ethernet cable between the network interface card in the Personal Computer and the RJ45 LAN-IN port on the PoE Injector. Step 9: Install Surge Protector Proxim recommends two approved lightning surge protectors to be installed, one near to the device and the other at the building ingress point.

: To buy a suitable Surge Protector, place an order separately with your distributor. Perform the following steps to ensure proper surge protection:

1. Mount the surge protector near the outdoor device and use 10 AWG or larger wire to connect the protectors ground lug to the appropriate mounting ground point. The outdoor device and co-located surge protector should have a common grounding point by using the shortest possible grounding cable. 2. Mount a second surge protector near the building ingress and use 10 AWG or larger wire to connect the surge protectors ground lug to earth ground as shown in the following figure. Tsunami 800 and 8000 Series - Hardware Installation Guide 95 8000 Series - Hardware Overview and Installation Figure 3-48 Surge Protector

: Use Outdoor-rated, UV protected, shielded Cat5e/Cat6 cable for the following. 3. Connect an RJ45 terminated cable between the indoor equipment and to the port on the surge protector at the building ingress. 4. Connect a short RJ45 terminated cable between the outdoor equipment and the port on the co-located surge protector. 5. Connect an RJ45 terminated cable between the two surge protectors on their remaining ports.

: Ensure to loop the cable before entering the premise to prevent water ingress. Step 10: Ground the Unit To ensure proper grounding, use either of the ground points which are situated at the bottom corners of the device and the grounding screw provided to attach a ground wire of at least 10 AWG stranded to the device. It is important that the following grounding guidelines are followed to protect the device against lighting or ESD events:

2. Cut any extra ground wire length when finished connecting it to the single point earth ground. 3. Avoid sharp bends and never loop or coil up the ground wire, always connect it straight to ground. earthing system point at the installation. 4. A good earth ground impedance is less than 1.0 ohm. 1. Connect one end of the grounding cable to the device as shown in the 

7. Make sure all connections are fastened securely and are tight. single common ground. rod.

 and the other end to the closest 6. Connect the surge protector ground wire and equipment ground (both power ground and telecomm ground) to a 5. Measure ground impedance at the point where the surge protector ground wire is connected and not at the ground 8. Never install during a storm and always follow your local safety codes. Tsunami 800 and 8000 Series - Hardware Installation Guide 96 8000 Series - Hardware Overview and Installation

Step 11: Power ON the Device Figure 3-49 Ground the Device Plug in the power cord into a power outlet after having connected the PoE Injector and the device using straight-through Cat5e/Cat6 cable. There is no ON/OFF switch on the device. To disconnect power, unplug the RJ45 connector from the PWR LAN-OUT port on the PoE injector. Step 12: View LEDs When the device is powered on, it performs startup diagnostics. When startup is complete, the LEDs show the devices operational state. The LEDs are available at the devices Ethernet connector inside the enclosure. You can see the LEDs through the ethernet connector. The LEDs will not be visible if the RJ45 connector is weatherproofed. Figure 3-50 View LEDs The following table states the status of LEDs and the corresponding operational state of the device:

LED State Power/Ethernet LED Wireless LED Ethernet Yellow Device is self heating (Cold Start) Off Blinking Green-Fast Blinking Green

(5 times) and turns off Green No Power Power is ON and the Ethernet link on Ethernet is DOWN Bootloader detected no image Power is ON and the device detects Reload signal Radio is not present or failed to detect Radio is ON and wireless link has not been established yet Not Applicable Power is ON and the Ethernet link on Ethernet is UP Wireless link has been established Tsunami 800 and 8000 Series - Hardware Installation Guide 97 8000 Series - Hardware Overview and Installation 3.6 MP-8200-BSU / MP-8200-SUA / MP-8250-SUR / QB-8200-EPA&LNK

/QB-8250-EPR&LNK / MP-8250-BS9 / MP-8250-BS1 This section provides the hardware overview and installation procedure for the following product(s):

QB-8200-EPA/LNK QB-8250-EPR/LNK MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR 3.6.1 Hardware Overview Figure 3-51 MP-8200-BSU / MP-8200-SUA / QB-8200-EPA Figure 3-52 MP-8250-SUR / MP-8250-BS9 / MP-8250-BS1 / QB-8250-EPR A detailed description about the various components of the device are explained in the following sections. 3.6.1.1 Gigabit Ethernet Ports The device comes with two auto-sensing 10/100/1000 BASE-T Ethernet ports with configurable Tx Modes and Speeds. Tsunami 800 and 8000 Series - Hardware Installation Guide 98 8000 Series - Hardware Overview and Installation 3.6.1.1.1 a) Ethernet Port 1 The Gigabit Ethernet port 1 (PoE IN and Data) of the device allows the user to connect to the LAN by using Cat5e/Cat6 Ethernet cable, and also power ON the device by using the Power over Ethernet (PoE) Injector supplied with the product package. The device receives 48 VDC via a standard Cat5e/Cat6 cable connected between the PoE and the device. Above 0 Celsius internal temperature, the device need not regulate its temperature, so the power drawn is generally lower in this temperature range. When the internal temperature gets close to the limits, the device starts to heat itself and the power draw increases. Powering the device when it is cold, triggers a special self-heat mode where the device is inoperable until the internal temperature is above -20 Celsius. This is signaled by a solid yellow LED on the Ethernet connector. Once the internal temperature is above -20 Celsius, the device boots normally. Maximum power supplied to the device is 32 Watts and the device typically draws 12 Watts. Cat5e/Cat6, STP, 24 AWG, UL rated, UV-shielded and outdoor-rated 100 ohms Recommended Ethernet Cable Specifications Type Impedance Cable Length 330 feet / 100 meters

: The total length of cabling between the Personal Computer and the device cannot exceed 100 meters (includes cable from the Personal Computer to the PoE, and the cable from the PoE to the device. Due to DC power requirements, the maximum cable length between the PoE Injector and the device is 75 meters.

: Always use a straight cable from PoE to the device. When you use a 4-pair cross over ethernet cable, the reload functionality gets activated and forcibly deletes the operating image. 3.6.1.1.2 b) Ethernet Port 2 The Gigabit Ethernet Port 2 is used for PoE OUT and data. While using this port, the following points should be considered:

48 VDC (15 W average) is present on the second Ethernet port. Make sure the connected device can support this voltage. If power from the second Ethernet Port is desired, then Proxim recommends you to use 60W PoE (not supplied). If a device is connected to the second Ethernet port for data only, then use a PoE Splitter (not supplied). 3.6.1.2 Serial Port The Serial Port is used for debugging and management, and Audible Antenna Alignment through Command Line Interface

(CLI). The serial connection is established with an RJ11 to DB9 connector (also referred to as a dongle) by connecting the RJ1 end of the dongle connector to the device and the other end to your Personal Computer. Tsunami 800 and 8000 Series - Hardware Installation Guide 99 8000 Series - Hardware Overview and Installation The pin assignments for DB9 connector are as follows:

Figure 3-53 Serial Components D-Shell 1 2 3 4 5 6 7 8 9 RJ11 NC 2 4 NC 1 + 3 + 5 6 NC NC NC

: The pin6 on RJ11 connector is used as input for 12V DC IN for diagnostic purpose. Supplying power on this pin, when the device is powered by POE injector, might damage the device. 3.6.1.3 Antenna Ports

: Applicable only to MP-8200-BSU, MP-8200-SUA and QB-8200-EPA/LNK. The Antenna Ports A1, A2 and A3 are used to connect external antenna (s). These antenna connectors are of N-Type female with built-in surge protection.

: Use antenna port A1 for single polarization antennas, and antenna ports A1 and A3 for dual polarization antennas. By default, A1 and A3 ports are enabled. Enable A2 port, in case you are using 3*3 antennas. Tsunami 800 and 8000 Series - Hardware Installation Guide

: When using a single polarized or dual polarized antenna, ensure to terminate the unused antenna ports card. To buy an additional N-male 50 Ohm Terminator, place an order separately with your distributor.

(supplied with the product package). Not doing so may damage the radio 100 with 8000 Series - Hardware Overview and Installation 3.6.1.4 Grounding Points To protect the device against lighting or ESD events, you must ground the device properly. To ensure proper grounding, use either of the ground points that are situated at the bottom corner of the device and the grounding screw (#8-32 thread size) provided to attach a ground wire of at least 10 AWG stranded to the device. 3.6.2 Product Package Each shipment includes the items listed in the following table. Please verify that you have received all the parts in this shipment, prior to installation. Whats in the Kit Image MP-8200-BSU/SUA QB-8200-EPA MP-8250-SUR / QB-8250-EPR MP-8250-BS9/BS1 MP-8200-BSU/

MP-8250-BS9/

MP-8250-BS1/

MP-8200-SUA/

MP-8250-SUR/

QB-8200-EPA/LNK QB-8250-EPR/LNK PoE Injector with Country specific Power Cord WD - US, UK and EU power cords US and JP* - US power cord EU - UK and EU power cords

* Not for MP-8250-BS9, MP-8250-BS1 RJ11 to DB9 Serial Connector Connector Weather Proofing Kit (2 sets) PoE Surge Arrestor Grounding Kit Tsunami 800 and 8000 Series - Hardware Installation Guide 101 8000 Series - Hardware Overview and Installation Whats in the Kit Image N-male 50 Ohm Terminator Supplied with MP-8200-BSU, MP-8200-SUA and QB-8200-EPA/LNK devices only Quick Installation Guide Mounting Kit and Hardware The mounting kit includes the following:

The following table lists the items included with the mounting kit:

Image Extension arm Mounting clamp for wall/pole Mounting plate to enclosure Mounting clamp for pole mounting Plain washer #5/16 Description Quantity 6 each 2 each Nut NC 5/16-18 2 each Hex Cap Screw NC 5/16-18 x 35 4 each Helical Spring Lock Washer #1/4 4 each Helical Spring Lock Washer #5/16 2 each Hex Cap Screw NC 5/16-18 x 80 4 each 68764, Screw, Machine, Pan, Philips, 1/4"-20, 5/8"L

: QB-8200-LNK and QB-8250-LNK contains two sets of all the above accessories. Tsunami 800 and 8000 Series - Hardware Installation Guide 102 3.6.3 Installation Procedure This section describes the steps to install and mount the device(s). 8000 Series - Hardware Overview and Installation

: Please note that we have taken MP-8200-BSU as an example to explain the steps to install and mount the device. Please correlate the same with your device.

: The device must be installed by a trained professional who is familiar with radio frequency planning and regulatory limits. Perform the following steps to install and mount the device. Step 1: Plan for Installation There are several planning factors to be considered before installing the device. In addition to selecting the installation site, you should do the following:

Calculate:

Required RSL and fade margin to achieve link availability objectives. For more details on how to calculate RSL and fade margin, please refer to the Tsunami 800 and 8000 Series - Antenna Installation Guide and Proxim Link Calculator

. Required path availability Anticipated multi-path reflection points that are available on the support site at

System frequency plan

Required antenna mounting height to obtain proper path clearance Required transmission line types (like cable, waveguides) and lengths Determine:

Plan for:

Devices continuous power consumption needs Lightning protection and system grounding Hardware mounting Cable installation including egress Pre-testing equipment (back-to-back test procedure) Step 2: Choose a Location To make optimal use of the device, you must find a suitable location to install the hardware. The range of the radio device largely depends upon the position of the antenna. Proxim recommends you do a site survey, observing the following requirements, before mounting the hardware. The location must allow easy disconnection of power to the radio, if necessary. Ensure free flow of air around the hardware. The radio device must be kept away from vibration and excessive heat. The installation must conform to local regulations at all times. The devices are designed to directly mount to a pole. Using the supplied brackets and hardware, you can mount them to a 1.25 inch to 3-inch pole (outside diameter). Longer bolts (not supplied) are required for mounting the device to a larger diameter pole. Using just one of the pole mounting brackets, you can mount the device to a wall or other flat surface. Tsunami 800 and 8000 Series - Hardware Installation Guide 103 Step 3: Gather Required Tools You should have the following tools available before installing the device:

8000 Series - Hardware Overview and Installation Straight-through UV-protected STP-rated Cat5e/Cat6 Ethernet cable for connecting to PC, or cable for connecting to a hub or a switch. Cross-tip screwdrivers Adjustable 6 wrench Small blade standard screwdriver Large blade standard screwdriver Wire crimpers (if using connectors that are not pre-made) Weatherproofing material for sealing external connectors (such as butyl tape) 1. Unpack the device and its accessories from the shipping box. Step 5: Weatherproofing RJ45 Connectors Step 4: Unpack the Product Package 2. Please make a note of the Ethernet addresses, MAC addresses and the serial number. These addresses may be used when configuring the device. Note that the serial number helps you to seek support from the Proxims Customer support team. The following steps explain how to weatherproof the RJ45 connectors:

1. Use a straight-through cable (Cat5e/Cat6) with one end bare. 2. Connect the crimped RJ45 connector end of the cable into the RJ45 Ethernet port inside the enclosure. The cable connector should latch into the Ethernet port. 3. Slide the Flat Washer (A) into the Connector Body (B) to make it waterproof and onto the bare end of the cable. Next, fasten the Connector Body into the Ethernet connector hole on the device. 4. Slide the tube-shaped Compression Washer (C) into the Compression Ring (D) and onto the cable from the bare end, and insert into the fixed Connector Body. 5. Slide the Sealing Nut (E) over the bare end of the cable and fasten it on the fixed Connector Body. 6. Crimp the bare end of the cable with RJ45 connector and connect it to the PWR LAN-OUT port on the PoE Injector. Additional Weatherproofing Steps Figure 3-54 Weatherproofing RJ45 Connector For detailed explanation to weatherproof RF connections, refer to Tsunami 800 and 8000 Series Antenna Installation Step 6: Assemble Mounting Hardware

. For detailed explanation to weatherproof RJ45 connectors, refer to 

Guide, which is available at

Tsunami 800 and 8000 Series - Hardware Installation Guide

 . 104 1. Fix the Mounting Plate (A) by using the provided screws and washers (Torque 9 N.m/75 in-lbs). 8000 Series - Hardware Overview and Installation Mounting Plate Fixing Mounting Plate to the device Mounting Plate fixed to the Device 2. Fix the Extension Arm (B) to the fixed Mounting Plate with the provided screw, nut and washers. The Extension Arm gives the device more possible tilt, letting you adjust for azimuth or elevation over a larger angle.

Extension Arm Mounting Plate fixed to the device Extension Arm fixed to Mounting Plate 3. Fix the Mounting Bracket (C) to fixed Extension Arm with the provided screw, nut and washers.

& Mounting Bracket 4. Tighten the assembled parts (Torque 15 N.m/130 in-lbs). Extension Arm fixed to Mounting Plate Mounting Bracket fixed to Extension Arm The following figure shows the fully assembled mounting hardware fixed to the device. Tsunami 800 and 8000 Series - Hardware Installation Guide 105 8000 Series - Hardware Overview and Installation Step 7: Mount the Device Figure 3-55 Assembled Device 1. To pole-mount the device, insert the provided screws and washers through bracket (F). Fasten around the pole to bracket (C) and secure (Torque 11 N.m/100 in-lbs). 2. To wall-mount the device, mount the bracket (C) to a wall by using 4 screws (not supplied), as shown:

Figure 3-56 Pole Mounting Figure 3-57 Wall Mounting Step 8: Plug in the Cables

: Unscrew the sealing cap for installation of the cable. 1. Plug one end of the straight-through Cat5e/Cat6 cable into the Ethernet Port 1 of the device by following the Weatherproofing steps explained under Step5. Connect the other end of the cable into the PWR LAN-OUT port on the PoE Injector.

: Always use a straight cable from PoE to the device. When you use a 4-pair cross over ethernet cable, the reload functionality gets activated and forcibly deletes the operating image. Tsunami 800 and 8000 Series - Hardware Installation Guide 106 8000 Series - Hardware Overview and Installation 2. Plugging in the second Cat5e/Cat6 cable into the Ethernet Port 2 interface of the device is optional. While using the second Ethernet Port for PoE OUT and data, the following should be considered:

Figure 3-58 Cable Plugged In 48 VDC (15 W average) is present on the second Ethernet port. Make sure the connected device can support this voltage. If power from the second Ethernet Port is desired, then Proxim recommends to use 60W PoE (not supplied). If the device is connected to the second Ethernet port for data, then use a PoE Splitter (not supplied) 3. Optionally, connect a RJ11 to DB9 Serial Connector to devices Serial Port for debugging and management, and audible antenna alignment. Figure 3-59 PoE Injector 4. To connect the device through a hub or a switch to a Personal Computer, connect an Ethernet cable between the network interface card in the Personal Computer and the hub, and between the hub and the RJ45 LAN-IN port on the PoE Injector. 5. To connect the device directly to a Personal Computer, connect an Ethernet cable between the network interface card in the Personal Computer and the RJ45 LAN-IN port on the PoE Injector. Step 9: Connect the Antenna

: Applicable only to MP-8200-BSU, MP-8200-SUA and QB-8200-EPA/LNK. Connect the antenna to the device by connecting the straight N-male end of the cable to the device antenna port and the right angle N-male end of the cable at the antenna.

antennas. configuration. Record which port each antenna polarization is associated with, to ensure that each side matches and aid in Ensure to use antenna port A1 for single polarization antennas, and antenna ports A1 and A3 for dual polarization 107 Tsunami 800 and 8000 Series - Hardware Installation Guide 8000 Series - Hardware Overview and Installation Step 10: Install Surge Protector Proxim recommends two approved lightning surge protectors to be installed, one near to the device and the other at the building ingress point.

: For an additional Surge Protector, place an order separately with your distributor. Perform the following steps to ensure proper surge protection:

1. Mount the provided surge protector near the outdoor device and use 10 AWG or a better gauge wire to connect the protectors ground lug to the appropriate mounting ground point. The outdoor device and co-located surge protector should have a common grounding point using the shortest possible grounding cable. 2. Mount a second surge protector near the building ingress and use 10 AWG or a better gauge wire to connect the surge protectors ground lug to earth ground as shown in the figure below. Figure 3-60 Surge Protector

: Use Outdoor-rated, UV protected, shielded Cat5e/Cat6 cable for the following:

3. Connect an RJ45 terminated cable between the indoor device and to the port on the surge protector at the building ingress. 4. Connect a short RJ45 terminated cable between the outdoor device and the port on the co-located surge protector. 5. Connect an RJ45 terminated cable between the two surge protectors on their remaining ports.

: Ensure to loop the cable before entering the premise to prevent water ingress. Tsunami 800 and 8000 Series - Hardware Installation Guide 108 8000 Series - Hardware Overview and Installation Step 11: Ground the Unit To ensure proper grounding, use either of the ground points which are situated at the bottom corners of the device and the grounding screw(#8-32 thread size) provided to attach a ground wire of at least 10 AWG stranded to the device. It is important that the following ground guidelines are followed during installations to protect the device against lighting or ESD events:

1. Connect one end of the grounding cable to the device and the other end to the closest earthing system point at the installation. 2. Cut any extra ground wire length when finished connecting it to the single point earth ground. 3. Avoid sharp bends and never loop or coil up the ground wire, always connect it straight to ground. 4. A good earth ground impedance is less than 1.0 ohm. 5. Measure ground impedance at the point where the protector ground wire is connected and not at the ground rod. 6. Connect the surge protector ground wire and equipment ground (both power ground and telecomm ground) to a single common ground. 7. Make sure all connections are fastened securely and are tight. 8. Never install during a storm and always follow your local safety codes. Connect the grounding wire, which is supplied with the product package, to the device as shown below:

Step 12: Power ON the Device Figure 3-61 Ground the Device Plug in the power cord into a power outlet after having connected the Power Injector and the radio device by using straight-through Cat5e/Cat6 cable. There is no ON/OFF switch on the device. To disconnect power, unplug the RJ45 connector from the PWR LAN-OUT port on the power injector. Step 13: View LEDs When the device is powered on, it performs startup diagnostics. When startup is complete, the LEDs show the devices operational state. The LEDs are available at the devices Ethernet connector inside the enclosure. You can see the LEDs through the ethernet connector. The LEDs will not be visible if the RJ45 connector is weatherproofed.

Figure 3-62 View LEDs Tsunami 800 and 8000 Series - Hardware Installation Guide 109 8000 Series - Hardware Overview and Installation The following table states the status of LEDs and the corresponding operational state of the device:

LED State Ethernet 1 Yellow Off Blinking Green-Fast Blinking Green (5 times) and turns off Green LED State Yellow Off Blinking Green-Fast Blinking Green (5 times) and turns off Green Power/Ethernet LED Device is self heating (Cold Start) No Power Power is on and the Ethernet link on Ethernet 1 is down Bootloader detected no image Wireless LED Power is on and the device detects Reload signal Radio is not present or failed to detect Radio is on and wireless link has not been established yet Not Applicable Power is on and the Ethernet link on Ethernet 1 is up Wireless link has been established Power/Ethernet LED Wireless LED Ethernet 2 Not Applicable No Power Power is on and the Ethernet link on Ethernet 2 is down Bootloader detected no image Power is on and the Ethernet link on Ethernet 2 is up Not Applicable Normal Operation Not Applicable Not Applicable Not Applicable Step 14: Align the Antennas Antenna alignment is the process of physically aligning the antenna of the radio receiver and transmitter to have the best possible link established between them. The antenna alignment process is usually performed during installation and after major repairs. If you are installing external antennas, refer to the documentation that accompanies the antenna for installation instructions. The device has an audible antenna alignment tool that can be activated by plugging in the supplied RJ11 serial dongle. It is audible upto 30 minutes. The CLI command enables both audible and numerical feedback as the CLI shows the running Signal-to-Noise Ratio (SNR) values twice a second. The output from the beeper for antenna alignment consists of short beeps with a variable interval. The interval changes with the SNR level to assist in correctly aligning the antenna. An increase in signal level is indicated by a shorter interval between beeps and a reduction in signal level results in beeps longer apart. The alignment process averages the SNR, which is represented by an average length beep. When a higher SNR is received, the beep period becomes shorter, dependent upon the difference to the average. A lower SNR results in a longer period between beeps. Tsunami 800 and 8000 Series - Hardware Installation Guide 110 8000 Series - Hardware Overview and Installation Figure 3-63 Beep Interval When the antenna is aimed, the beep intuitively represents whether the SNR is rising or falling. The higher the SNR rises, the shorter the period of the beep is heard and the higher the frequency of the beep. When you change the position of the antenna, SNR averaging settles at the new value and the beeping returns to the average length so the antenna can again be aimed for rising SNR. Aiming is complete if moving in any direction results in a falling SNR value (which can be heard as longer periods between beeps).

The range of the average SNR has been limited to values from 5 to 43; therefore, anything over 43 always results in a short period between beeps and values below 5 always have a long period. The Antenna Alignment Display (AAD) CLI output is disabled automatically 30 minutes after it is enabled to remove the load of extra messages on the wireless interface. The default telnet time-out is 300 seconds (5 minutes). Antenna Alignment Commands To enable the antenna alignment display from the CLI prompt, enter the following commands:

: Enables display of the local signal, noise and SNR.

: Enables display of the remote signal, noise and SNR.

: Enables display of local and remote signal, noise and SNR.

: Use a flat blade screw driver to disconnect and pull out the Serial cable from the enclosure after the antenna alignment is done. After withdrawing the cables, seal the serial port carefully to avoid water seepage.

. 0

, 1

) Tsunami 800 and 8000 Series - Hardware Installation Guide 111 Technical Specifications This chapter provides information on the following topics:

4 4

6 6

8

2

7

5 4 6 9 7 6

4

3 3

3 8

8 4

2

Model

3

5

Part Number Device Models

Description Base Stations MP-820-BSU-100-WD 901-00133 MP 820 Base Station Unit, 100 Mbps, GPS Sync Ready, 2x2 MIMO, 2 N-Type Connectors -

MP-820-BSU-100-US WD PoE 901-00135 MP 820 Base Station Unit, 100 Mbps, GPS Sync Ready, 2x2 MIMO, 2 N-Type Connectors -

US PoE MP-820-BSU-100-EU 901-00162 MP 820 Base Station Unit, 100 Mbps, GPS Sync Ready, 2x2 MIMO, 2 N-Type Connectors -

EU PoE MP-825-BS3-100-WD 901-00184 MP 820 Base Station Unit, 100 Mbps, GPS Sync Ready, 2x2 MIMO, 15 dBi Integrated Antenna - WD PoE MP-825-BS3-100-US 901-00185 MP 820 Base Station Unit, 100 Mbps, GPS Sync Ready, 2x2 MIMO, 15 dBi Integrated Antenna - US PoE MP-825-BS3-100-EU 901-00186 MP 820 Base Station Unit, 100 Mbps, GPS Sync Ready, 2x2 MIMO, 15 dBi Integrated Antenna - EU PoE MP-8100-BSU-US MP-8100-BSU-WD 76705 76708 MP 8100 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - US PoE MP 8100 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - WD PoE MP-8100-BSU-EU 901-00158 MP 8100 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - EU PoE MP-8160-BSU-WD 901-00109 MP 8160 Base Station Unit, 300Mbps, 2x2 MIMO, 2 N-Type Connectors - WD PoE MP-8160-BS9-WD 901-00120 MP 8160 Base Station Unit, 300Mbps, 2x2 MIMO, 16 dBi Integrated 90 degree Sector Antenna - WD PoE Tsunami 800 and 8000 Series - Hardware Installation Guide 112 Technical Specifications MP-8200-BSU-US 901-00118 MP 8200 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - US PoE MP-8200-BSU-WD 901-00116 MP 8200 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - WD PoE MP-8200-BSU-JP 901-00148 MP 8200 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - JP PoE MP-8200-BSU-EU 901-00155 MP 8200 Base Station Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - EU PoE MP-8250-BS9-US 901-00119 MP 8250 Base Station Unit, 300 Mbps, 2x2 MIMO, 16 dBi Integrated 90o Sector Antenna - US PoE MP-8250-BS9-WD 901-00117 MP 8250 Base Station Unit, 300 Mbps, 2x2 MIMO, 16 dBi Integrated 90o Sector Antenna - WD PoE MP-8250-BS9-EU 901-00165 MP 8250 Base Station Unit, 300 Mbps, 2x2 MIMO, 16 dBi Integrated 90o Sector Antenna - EU PoE MP-8250-BS1-US 901-00170 MP 8250 Base Station Unit, 300 Mbps, 2x2 MIMO, 23 dBi Integrated 10o Panel Antenna - US PoE MP-8250-BS1-WD 901-00171 MP 8250 Base Station Unit, 300 Mbps, 2x2 MIMO, 23 dBi Integrated 10o Panel Antenna - WD PoE MP-8250-BS1-EU 901-00172 MP 8250 Base Station Unit, 300 Mbps, 2x2 MIMO, 23 dBi Integrated 10o Panel Antenna - EU PoE Subscribers MP-8100-SUA-US MP-8100-SUA-WD 76706 76709 MP 8100 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - US PoE MP 8100 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - WD PoE MP-8100-SUA-EU 901-00160 MP 8100 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - EU PoE MP-8150-SUR-US MP-8150-SUR-WD 76707 76710 MP 8150 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - US PoE MP 8150 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - WD PoE MP-8150-SUR-EU 901-00159 MP 8150 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - EU PoE MP-8150-CPE-100a-US 901-00012 MP 8150 CPE, 100Mbps, 2x2 MIMO, 16 dBi Integrated Antenna - US PoE MP-8150-CPE-100a-WD 901-00014 MP 8150 CPE, 100Mbps, 2x2 MIMO, 16 dBi Integrated Antenna - WD PoE MP-8150-CPE-A100 901-00050 MP 8150 CPE, 100Mbps, 2x2 MIMO, 16 dBi Integrated Antenna - WD PoE MP-8150-SUR-100-US 901-00145 MP 8150 Subscriber Unit, 2x50 Mbps, MIMO 2x2, 21dBi Integrated Antenna - US PoE MP-8150-SUR-100-WD 901-00146 MP 8150 Subscriber Unit, 2x50 Mbps, MIMO 2x2, 21dBi Integrated Antenna - WD PoE MP-8150-SUR-100-EU 901-00161 MP 8150 Subscriber Unit, 2x50 Mbps, MIMO 2x2, 21dBi Integrated Antenna - EU PoE MP-8160-SUA-WD 901-00111 MP 8160 Subscriber Unit, 300 Mbps, 2x2 MIMO, 2 N-Type connectors - WD PoE MP-8160-CPE-A100-WD 901-00110 MP 8160 CPE, 100Mbps, 2x2 MIMO, 15 dBi Integrated Antenna - WD PoE MP-826-CPE-50-WD 901-00153 MP 826 Customer Premise Equipment , 50 Mbps, 2x2 MIMO, 15dBi integrated antenna -

World PoE MP-8200-SUA-US 901-00123 MP 8200 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - US PoE MP-8200-SUA-WD 901-00121 MP 8200 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - WD PoE MP-8200-SUA-JP 901-00151 MP 8200 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - JP PoE MP-8200-SUA-EU 901-00157 MP 8200 Subscriber Unit, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - EU PoE MP-8250-SUR-US 901-00124 MP 8250 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna US PoE MP-8250-SUR-WD 901-00122 MP 8250 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna WD PoE MP-8250-SUR-JP 901-00152 MP 8250 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna JP PoE Tsunami 800 and 8000 Series - Hardware Installation Guide 113 Technical Specifications MP-8250-SUR-EU 901-00156 MP 8250 Subscriber Unit, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna EU PoE MP-820-SUA-50+-WD 901-00134 MP 820 Subscriber Unit, 50 Mbps (Upgradable to 100 Mbps), 2x2 MIMO, 2 N-Type Connectors - WD PoE MP-820-SUA-50+-US 901-00136 MP 820 Subscriber Unit, 50 Mbps (Upgradable to 100 Mbps), 2x2 MIMO, 2 N-Type Connectors - US PoE MP-820-SUA-50+-EU 901-00163 MP 820 Subscriber Unit, 50 Mbps (Upgradable to 100 Mbps), 2x2 MIMO, 2 N-Type Connectors - EU PoE MP-825-SUR-50+-WD 901-00175 MP 825 Subscriber Unit, 50 Mbps (Upgradable to 100 Mbps), 2x2 MIMO, 15 dBi, Panel Antenna - WD PoE MP-825-SUR-50+-US 901-00176 MP 825 Subscriber Unit, 50 Mbps (Upgradable to 100 Mbps), 2x2 MIMO, 15 dBi, Panel Antenna - US PoE MP-825-SUR-50+-EU 901-00177 MP 825 Subscriber Unit, 50 Mbps (Upgradable to 100 Mbps), 2x2 MIMO, 15 dBi, Panel Antenna - EU PoE MP-825-CPE-50-US 901-00137 MP 825 Customer Premise Equipment, 50 Mbps, MIMO 2x2, 15 dBi integrated antenna -

US PoE MP-825-CPE-50-WD 901-00138 MP 825 Customer Premise Equipment, 50 Mbps, MIMO 2x2, 15 dBi integrated antenna -

WD PoE MP-825-CPE-50-EU 901-00154 MP 825 Customer Premise Equipment, 50 Mbps, MIMO 2x2, 15 dBi integrated antenna -

EU PoE MP-825-CPE-100-WD 901-00187 MP 825 Customer Premise Equipment, 100 Mbps, MIMO 2x2, 15 dBi integrated antenna

- WD PoE MP-825-CPE-100-US 901-00188 MP 825 Customer Premise Equipment, 100 Mbps, MIMO 2x2, 15 dBi integrated antenna

- US PoE MP-825-CPE-100-EU 901-00189 MP 825 Customer Premise Equipment, 100 Mbps, MIMO 2x2, 15 dBi integrated antenna

- EU PoE Quick Bridges QB-8100-EPA-US QB-8100-EPA-WD 76946 76947 QB 8100 End Point A, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - US PoE QB 8100 End Point A, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - WD PoE QB-8100-EPA-EU 902-00663 QB 8100 End Point A, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - EU PoE QB-8100-LNK-US 77519 QB 8100 Link (A pair of QB-8100-EPA-US devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - US PoE QB-8100-LNK-WD 77518 QB 8100 Link (A pair of QB-8100-EPA-WD devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - WD PoE QB-8100-LNK-EU 902-00661 QB 8100 Link (A pair of QB-8100-EPA-EU devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - EU PoE QB-8150-EPR-US 76821 QB 8150 End Point Ruggedized, 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - US PoE QB-8150-EPR-WD 76823 QB 8150 End Point Ruggedized, 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - WD PoE QB-8150-EPR-EU 902-00662 QB 8150 End Point Ruggedized, 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - EU PoE QB-8150-LNK-US 76822 QB 8150 Link (A pair of QB-8150-EPR-US devices), 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - US PoE QB-8150-LNK-WD 76824 QB 8150 Link (A pair of QB-8150-EPR-WD devices), 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - WD PoE Tsunami 800 and 8000 Series - Hardware Installation Guide 114 Technical Specifications QB-8150-LNK-EU 902-00660 QB 8150 Link (A pair of QB-8150-EPR-EU devices), 300 Mbps, 2x2 MIMO, 23 dBi Integrated Antenna - EU PoE QB-8150-LNK-12-WD 902-00056 QB 8150 Link (A pair of QB-8150-EPR-12-WD devices), 12 Mbps, 2x2 MIMO, 16 dBi Integrated Antenna - WD PoE QB-8150-LNK-50-US 902-00063 QB 8150 Link (A pair of QB-8150-EPR-50-US devices), 50 Mbps, 2x2 MIMO, 16 dBi Integrated Antenna - US PoE QB-8150-LNK-50-WD 902-00064 QB 8150 Link (A pair of QB-8150-EPR-50-WD devices), 50 Mbps, 2x2 MIMO, 16 dBi Integrated Antenna - WD PoE QB-8150-LNK-100-US 902-00644 QB 8150 Link (A pair of QB-8150-EPR-100-US devices), 2x50 Mbps, MIMO 2x2, 21 dBi Integrated Antenna - US PoE QB-8150-LNK-100-WD 902-00645 QB 8150 Link (A pair of QB-8150-EPR-100-WD devices), 2x50 Mbps, MIMO 2x2, 21 dBi Integrated Antenna - WD PoE QB-8151-EPR-US 902-00748 QB 8151 End Point Ruggedized, 300 Mbps, 2x2 MIMO, 21 dBi Integrated Antenna - US PoE QB-8151-EPR-WD 902-00750 QB 8151 End Point Ruggedized, 300 Mbps, 2x2 MIMO, 21 dBi Integrated Antenna - WD PoE QB-8151-LNK-US 902-00749 QB 8151 Link (A pair of QB-8151-EPR-US devices), 300 Mbps, 2x2 MIMO, 21 dBi Integrated Antenna - US PoE QB-8151-LNK-WD 902-00751 QB 8151 Link (A pair of QB-8151-EPR-WD devices), 300 Mbps, 2x2 MIMO, 21 dBi Integrated Antenna - WD PoE QB-8200-EPA-US 902-00595 QB 8200 End Point, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - US PoE QB-8200-EPA-WD 902-00594 QB 8200 End Point, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - WD PoE QB-8200-EPA-JP 902-00654 QB 8200 End Point, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - JP PoE QB-8200-EPA-EU 902-00668 QB 8200 End Point, 300 Mbps, 3x3 MIMO, 3 N-Type Connectors - EU PoE QB-8200-LNK-US 902-00599 QB 8200 Link (A pair of QB-8200-EPA-US devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - US PoE QB-8200-LNK-WD 902-00598 QB 8200 Link (A pair of QB-8200-EPA-WD devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - WD PoE QB-8200-LNK-JP 902-00655 QB 8200 Link (A pair of QB-8200-EPA-JP devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - JP PoE QB-8200-LNK-EU 902-00658 QB 8200 Link (A pair of QB-8200-EPA-EU devices), 300 Mbps, 3x3 MIMO, 3 N - Type Connectors - EU PoE QB-8250-EPR-US 902-00600 QB 8250 End Point, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - US PoE QB-8250-EPR-WD 902-00596 QB 8250 End Point, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - WD PoE QB-8250-EPR-JP 902-00656 QB 8250 End Point, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - JP PoE QB-8250-EPR-EU 902-00669 QB 8250 End Point, 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - EU PoE QB-8250-LNK-US 902-00601 QB 8250 Link (A pair of QB-8250-EPR-US devices), 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - US PoE QB-8250-LNK-WD 902-00597 QB 8250 Link (A pair of QB-8250-EPR-WD devices), 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - WD PoE QB-8250-LNK-JP 902-00657 QB 8250 Link (A pair of QB-8250-EPR-JP devices), 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - JP PoE QB-8250-LNK-EU 902-00659 QB 8250 Link (A pair of QB-8250-EPR-EU devices), 300 Mbps, 2x2 MIMO, 23 dBi, Panel Antenna - EU PoE Tsunami 800 and 8000 Series - Hardware Installation Guide 115 Technical Specifications QB-825-EPR-50-US 902-00743 QB 825 End Point, 50 Mbps, 2x2 MIMO, 15 dBi Antenna - US PoE QB-825-EPR-50-WD 902-00745 QB 825 End Point, 50 Mbps, 2x2 MIMO, 15 dBi Antenna - WD PoE QB-825-LNK-50-US 902-00744 QB 825 Link (A pair of QB-825-EPR-50-US devices), 50 Mbps, 2x2 MIMO, 15 dBi Antenna

- US PoE QB-825-LNK-50-WD 902-00746 QB 825 Link (A pair of QB-825-EPR-50-WD devices), 50 Mbps, 2x2 MIMO, 15 dBi Antenna - WD PoE QB-825-LNK-50+-WD 902-00637 QB 825 Link (A pair of QB-825-EPR-50+-WD devices), GPS Sync Ready, 50 Mbps

(Upgradable to 100 Mbps), 2x2 MIMO, 15 dBi Antenna - WD PoE QB-825-LNK-50+-US 902-00638 QB-825-LNK-50+-EU 902-00665 QB 825 Link (A pair of QB-825-EPR-50+-US devices), GPS Sync Ready, 50 Mbps

(Upgradable to 100 Mbps), 2x2 MIMO, 15 dBi Antenna - US PoE QB 825 Link (A pair of QB-825-EPR-50+-EU devices), GPS Sync Ready, 50 Mbps

(Upgradable to 100 Mbps), 2x2 MIMO, 15 dBi Antenna - EU PoE Accessories Part Numbers

A B C C D E F G

H I D J K K L M N

F

O P G B C D E F Q J R S T H R

U 76590 76591 76592 25m, RJ45 terminated, UV Rated, STP CAT5e cable for outdoor use 50m, RJ45 terminated, UV Rated, STP CAT5e cable for outdoor use 75m, RJ45 terminated, UV Rated, STP CAT5e cable for outdoor use Accessories 949-00075 6 ft Super-Low Loss Coaxial Antenna Cable, 0.600, Standard N-Male to Right Angle N-Male 235-00001 Surge Protector, Gigabit Surge Protector with Shielded RJ45 Connector 76593 76346 Weatherproof Cable Gland Connector 32W Gigabit PoE injector with RJ45 Connector and Reload button 949-00019 4.9 - 6.1 GHz, Dual Polarity, Vertical and Horizontal, 30 dBi Panel Antenna 76955 77067 77551 4.9 - 5.875 GHz, Dual Polarity, Slanted (45) or V/H, 23 dBi Panel Antenna 4.9 - 6.1 GHz, Dual Polarity, Slanted (45), 17 dBi Sector Antenna - 60 degrees 5.1 - 6.1 GHz, Triple Polarization MIMO, Slanted (45) and Vertical, 17 dBi Panel Antenna 949-00012 4.9-5.95GHz, Dual Polarity, Vertical and Horizontal, 14 dBi Sector Antenna- 90 degrees. Mounting kit included. 77552 4.9 - 6.1 GHz, Triple Polarizations MIMO, Slanted (45) and Vertical, 16 dBi Sector Antenna - 90 degrees 949-00011 4.9-6GHz, Dual Polarity, Vertical /Horizontal,16.5 dBi Sector Antenna - 60 degrees. Mounting kit included. 949-00024 5.9-6.425 GHz Dual Polarized Base Station Antenna 90 degrees 949-00025 5.9-6.425 GHz Dual Polarized Base Station Antenna 60 degrees 949-00026 5.7-6.425 GHz Dual Polarized Subscriber Antenna 949-00045 Cable Feed-Through Sealing Cap kits, PACK OF 20 ( MP/QB.11) 125-00003 2-6 GHz High Performance RF Lightning Arrestor, N-Female to N-Male Protected 76409 Outdoor Universal Mounting Kit for TMP.11; TMP.16; TMP8000 Tsunami 800 and 8000 Series - Hardware Installation Guide 116 400-00002 PoE Gigabit 48V DC Injector with terminal Jack - 25 pack 949-00027 2.3-2.7 GHz, Dual Polarity, Vertical and Horizontal, 20 dBi Panel Antenna 949-00083 Spare gas capsule for Tsunami 8100 N-Type connector Technical Specifications 1087-UMK 210-00046 949-00017 6 ft Super-Low Loss Coaxial Antenna Cable, 0.600, St-N - Male-Male N Male Terminator 50 Ohm, 0-6 GHz Universal Mounting Bracket for Wall Mounting. Refer V

3

4

W

Tsunami 800 and 8000 Series - Hardware Installation Guide 117 OFDM Modulation Rates Given below are the OFDM modulation rates for the Tsunami 800 and 8000 series products:

5 MHz 10 MHz 20 MHz 40 MHz Data Rates (Mbps) Technical Specifications Modulation Full GI-800ns Full GI-800ns Full GI-800ns Longer Range Higher Throughput Longer Range Higher Throughput Longer Range Higher Throughput Short GI-400ns Higher Longer Range Throughput BPSK 1/2 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 64QAM 3/4 64QAM 5/6 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 15 30 45 60 90 120 135 150 30 60 90 120 180 240 270 300 Note: Maximum Packet Size = 1500 Bytes (excluding one VLAN header, Ethernet header and FCS). Full GI-800ns Longer Range Higher Throughput 13.5 27 40.5 54 81 108 121.5 135 27 54 81 108 162 216 243 270 Products Modulation Legacy Data Rates (Mbps) 5 MHz 10 MHz 20 MHz BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 64QAM 3/4 1.5 2.25 3 4.5 6 9 12 13.5 3 4.5 6 9 12 18 24 27 6 9 12 18 24 36 48 54 MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8150-CPE MP-8200-BSU MP-8200-SUA MP-8250-SUR MP-8250-BS9 MP-8250-BS1 MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 MP-825-CPE-50 MP-825-CPE-100 Wireless Protocol Category Specification Wireless Protocol WORP (Wireless Outdoor Router Protocol) Tsunami 800 and 8000 Series - Hardware Installation Guide 118 Technical Specifications Interfaces Products Category Specification MP-8100-BSU; MP-8100-SUA MP-8150-SUR; MP-8160-BSU MP-8160-SUA; MP-8160-BS9 MP-8200-BSU; MP-8200-SUA MP-8250-SUR; MP-8250-BS9; MP-8250-BS1 QB-8100-EPA/LNK; QB-8150-EPR/LNK QB-8151-EPR/LNK QB-8200-EPA/LNK; QB-8250-EPR/LNK Wired Ethernet Two auto MDI-X RJ45 Gigabit Ethernet Ports Port #1 with PoE IN and Data Port #2 with PoE OUT (802.3af pin-out) and Data Serial Connector RJ11 port built-in, DB9 Female via a converter included MP-8150-CPE MP-8160-CPE-A100 MP-825-CPE-100 MP-825-CPE-50 MP-826-CPE-50 QB-825-EPR/LNK-50 QB-8150-LNK-12/50 MP-8150-SUR-100 QB-8150-LNK-100 MP-820-BSU-100 MP-820-SUA-50+

MP-825-BS3-100 MP-825-SUR-50+

QB-825-EPR/LNK-50+

Wired Ethernet One auto MDI-X RJ45 100 Mbps Ethernet Port Serial Connector *

RS 232 Serial (RJ11 to DB9) Wired Ethernet One auto MDI-X RJ45 Gigabit Ethernet Port Serial Connector RS 232 Serial (RJ11 to DB9)

* Not applicable to MP-8160-CPE-A100, MP-825-CPE-100, MP-825-CPE-50, MP-826-CPE-50 and QB-825-EPR/LNK-50. Tsunami 800 and 8000 Series - Hardware Installation Guide 119 Transmit Power Settings Products Stream Modulation Tx Power* for 20/40 MHz (+3/-2dB) 2.4 and 5 GHz Technical Specifications Single (or) Dual Stream MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Note:

Output Power Attenuation: 0 25 dB, in 1 dB steps Total EIRP must be calculated based on the antenna gain 21 21 21 21 21 19 18 17

* Tx Power indicates the power at the radio ports.

* In case of connectorized devices, the Tx Power at the antenna ports is 1 dB lower than the above tabulated values.

* Tx Power indicates the combined power for two Antenna ports. In order to use third antenna port, add 1.8 dB to the above values. Products Stream Modulation Tx Power* for 5/10/20 MHz (+/-1dB) Tx Power* for 40 MHz (+/-1dB) 4.9 - 5.925 GHz MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA/LNK QB-8250-EPR/LNK Single

(or) Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Note:

Output Power Attenuation: 0 25 dB, in 1 dB steps Total EIRP must be calculated based on the antenna gain 24 24 23 22 21 20 19 18 22 22 22 21 20 19 18 17

* Tx Power indicates the power at the radio ports.

* In case of connectorized devices, the Tx Power at the antenna ports is 1 dB lower than the above tabulated values.

* Tx Power indicates the combined power for two Antenna ports. In order to use third antenna port, add 1.8 dB to the above values. Tsunami 800 and 8000 Series - Hardware Installation Guide 120 Technical Specifications Products Stream Modulation Tx Power* for 5/10/20/40 MHz (+/-1dB) 6.4 GHz MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE-A100 Single (or) Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 25 25 25 25 23 22 19 16 Note:

Output Power Attenuation: 0 25 dB, in 1 dB steps Total EIRP must be calculated based on the antenna gain

* Tx Power indicates combined power at the radio ports.

* In case of connectorized devices, the Tx Power at the antenna ports is 1 dB lower than the above tabulated values. Products Stream Modulation Tx Power* (dBm) for 20/40 MHz 5 GHz MP-8150-CPE QB-8150-LNK-12/50 Single (or) Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 23 23 23 23 22 21 20 19 Note:

Output Power Attenuation: 0 23 dB, in 1 dB steps Output Power Values will have a tolerance of +/-1 dB Total EIRP must be calculated based on integrated 16 dBi antenna gain

* Tx Power for 5GHz indicates the combined power. Tsunami 800 and 8000 Series - Hardware Installation Guide 121 Technical Specifications 5.150 - 5.925 GHz Products Stream Modulation Single (or) Dual Stream MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 MP-825-CPE-50 MP-825-CPE-100 QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Tx Power* (dBm) 40 MHz 20 MHz 10 MHz 5 MHz 26 26 25 24 23 22 21 17 26 25 24 24 23 22 21 18 26 25 25 24 23 22 21 18 26 26 25 24 23 22 21 18

: Integrated 15 dBi dual Polarized (H+V) panel antenna (14 dBi beyond 5.850 GHz) Note:

Output Power Attenuation: 0 15 dB, in 1 dB steps Output Power Values will have a tolerance of +/-2 dB (It is at the lower limit beyond 5.850 GHz) Total EIRP must be calculated based on integrated 15 dBi antenna gain

* Tx Power for 5GHz indicates the combined power. 5.900 - 6.425 GHz Products Stream Modulation MP-826-CPE-50 Single Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Tx Power* (dBm) 40 MHz 20 MHz 10 MHz 5 MHz 25 25 25 24 23 23 21 20 25 25 25 25 24 23 21 20 25 25 25 25 24 23 21 20 25 25 25 25 24 23 21 20 Tsunami 800 and 8000 Series - Hardware Installation Guide 122 Technical Specifications 5.900 - 6.425 GHz Note:

Output Power Attenuation: 0 22 dB, in 1 dB steps Output Power Values will have a tolerance of +/-2 dB Total EIRP must be calculated based on integrated 15 dBi antenna gain

* Tx Power findicated above is the combined power. Receive Sensitivity Products Stream Modulation 2.4 GHz 5 GHz Receive Sensitivity (dBm) Single Stream MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK Dual Stream 40 MHz 20 MHz 10 MHz 5 MHz 40 MHz 20 MHz 10 MHz 5 MHz BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6

-89

-89

-88

-85

-82

-77

-76

-74

-85

-83

-79

-77

-73

-68

-66

-64

-92

-91

-89

-87

-85

-78

-77

-73

-87

-85

-81

-78

-75

-71

-68

-66

-95

-95

-92

-88

-84

-83

-81

-79

-90

-87

-84

-82

-78

-74

-71

-70

-96

-96

-94

-93

-90

-84

-83

-81

-93

-89

-86

-85

-80

-76

-74

-72

-87

-87

-84

-81

-78

-73

-72

-70

-87

-84

-81

-78

-75

-71

-69

-68

-92

-89

-87

-83

-80

-75

-74

-72

-90

-87

-84

-81

-78

-73

-72

-70

-94

-91

-89

-86

-83

-78

-77

-75

-92

-89

-87

-84

-80

-76

-74

-73

-97

-95

-92

-89

-86

-81

-80

-78

-95

-92

-90

-87

-83

-79

-78

-76 Note: Receive Sensitivity values should be considered with a tolerance +/- 2 dB. Tsunami 800 and 8000 Series - Hardware Installation Guide 123 Technical Specifications Products Stream Legacy Data Rate Receive Sensitivity (dBm)

(Mbps) 5 GHz 20 MHz 10 MHz 5 MHz MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Single Stream 6 9 12 18 24 36 48 54

-91

-91

-92

-90

-86

-83

-78

-77

-94

-94

-94

-92

-88

-85

-81

-79

-97

-97

-96

-95

-92

-88

-84

-82 Tsunami 800 and 8000 Series - Hardware Installation Guide 124 Technical Specifications Products Stream Modulation Receive Sensitivity (dBm) 4.900 - 5.925 GHz 40 MHz 20 MHz 10 MHz 5 MHz MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA/LNK QB-8250-EPR/LNK Single Stream Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6

-85

-85

-83

-80

-76

-72

-70

-68

-85

-82

-80

-77

-74

-69

-68

-66

-90

-87

-85

-82

-78

-74

-72

-71

-88

-85

-83

-79

-76

-72

-70

-69

-92

-90

-88

-84

-81

-76

-75

-73

-90

-87

-85

-82

-79

-74

-73

-71

-95

-92

-90

-87

-84

-80

-77

-76

-93

-91

-88

-85

-82

-77

-76

-74 Note: Receive Sensitivity values should be considered with a tolerance +/- 2 dB. Tsunami 800 and 8000 Series - Hardware Installation Guide 125 Technical Specifications Products Stream Legacy Data Rate 4.900 - 5.925 GHz Receive Sensitivity (dBm)

(Mbps) 20 MHz 10 MHz 5 MHz Single Stream MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR 6 9 12 18 24 36 48 54

-89

-90

-90

-88

-84

-81

-77

-75

-92

-92

-92

-90

-87

-84

-79

-78

-95

-95

-95

-93

-90

-87

-82

-80 Tsunami 800 and 8000 Series - Hardware Installation Guide 126 Technical Specifications Products Stream Modulation Receive Sensitivity (dBm) 6.4 GHz 40 MHz 20 MHZ 10 MHZ 5 MHZ MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE-A100 Single Stream Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6

-90

-88

-86

-82

-79

-75

-73

-72

-88

-86

-83

-80

-77

-72

-71

-69

-92

-90

-87

-84

-80

-77

-75

-73

-90

-87

-85

-81

-78

-74

-72

-70

-95

-92

-90

-87

-83

-79

-77

-76

-92

-90

-87

-84

-81

-76

-75

-73

-98

-96

-94

-91

-87

-83

-81

-80

-96

-93

-91

-88

-85

-80

-78

-76 Note: Receive Sensitivity values should be considered with a tolerance +/- 2 dB. Tsunami 800 and 8000 Series - Hardware Installation Guide 127 Technical Specifications Products Stream Modulation 5 GHz Receive Sensitivity (dBm) 40 MHz 20 MHz 10 MHz 5 MHz MP-8150-CPE QB-8150-LNK-12/50 Single Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6

-89.0

-89.0

-87.0

-84.0

-81.0

-77.0

-75.0

-73.0

-89.0

-89.0

-87.0

-84.0

-81.0

-77.0

-75.0

-73.0

-93.0

-92.0

-90.0

-86.0

-83.0

-80.0

-78.0

-76.0

-93.0

-92.0

-90.0

-86.0

-83.0

-80.0

-78.0

-76.0

-95

-93

-90

-87

-84

-79

-78

-76

-93

-90

-87

-84

-81

-77

-75

-73

-96

-94

-92

-89

-86

-81

-80

-78

-94

-91

-89

-87

-83

-79

-77

-75 Note: Receive Sensitivity values should be considered with a tolerance +/- 2 dB. Tsunami 800 and 8000 Series - Hardware Installation Guide 128 Technical Specifications Products Stream Modulation Receive Sensitivity (dBm) 5.150 - 5.925 GHz 40 MHz 20 MHz 10 MHz 5 MHz Single Stream MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 MP-825-CPE-50 MP-825-CPE-100 QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6

-88

-87

-85

-82

-79

-75

-73

-72

-88

-85

-83

-80

-77

-72

-70

-69

-92

-90

-88

-85

-81

-77

-75

-74

-91

-88

-85

-83

-79

-75

-73

-71

-93

-92

-90

-87

-83

-79

-77

-75

-93

-90

-87

-85

-81

-77

-74

-72

-94

-93

-91

-89

-85

-81

-79

-77

-94

-92

-89

-87

-83

-79

-77

-75

: Integrated 15 dBi dual Polarized (H+V) panel antenna (14 dBi beyond 5.850 GHz) Note: Receive Sensitivity values should be considered with a tolerance +/- 2 dB. Tsunami 800 and 8000 Series - Hardware Installation Guide 129 Technical Specifications Products Stream Legacy Data Rate

(Mbps) Receive Sensitivity (dBm) 5.150 - 5.925 GHz 20 MHz 10 MHz 5 MHz Single Stream MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 MP-825-CPE-50 MP-825-CPE-100 6 9 12 18 24 36 48 54

-92

-92

-92

-90

-86

-83

-79

-77

-93

-93

-93

-91

-88

-85

-81

-79

-94

-94

-94

-92

-90

-87

-83

-81 Products Stream Modulation Receive Sensitivity (dBm) 5.900 - 6.425 GHz 40 MHz 20 MHz 10 MHz 5 MHz MP-826-CPE-50 Single Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6 Dual Stream BPSK 1/2 QPSK 1/2 QPSK 3/4 16 QAM 1/2 16 QAM 3/4 64 QAM 2/3 64 QAM 3/4 64 QAM 5/6

-89

-87

-85

-82

-78

-74

-72

-69

-88

-85

-82

-79

-75

-70

-68

-61

-92

-90

-87

-84

-80

-76

-74

-72

-90

-87

-84

-81

-78

-73

-71

-68

-95

-93

-90

-87

-83

-79

-77

-75

-93

-90

-87

-84

-81

-75

-73

-70

-97

-95

-92

-89

-86

-81

-79

-77

-96

-92

-90

-87

-83

-78

-76

-73 Note: Receive Sensitivity values should be considered with a tolerance +/- 2 dB. Tsunami 800 and 8000 Series - Hardware Installation Guide 130 Technical Specifications Management Category Specification Local*

Remote X Y Z

a

b

Z c d e f g h i e j d k e l g i i m c RS232 serial CLI (up to 115200 bps) d Telnet and SSH, Web GUI (http) and SSL (https), TFTP SNMP v1, v2c and v3 SNMP trap and Syslog e f n o e j d k e o i m c d e f n o e j d k e g i i m c d e f n h e j d k e o i

p q r s e f n o e k d t u v Y w e o i x Tsunami 800 and 8000 Series - Hardware Installation Guide 131 Power Supply Products Category Specification Technical Specifications Input Voltage MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8200-EPA/LNK QB-8250-EPR/LNK Via RJ-45 Ethernet interface supplying 48 VDC and 0.67A on Ethernet Port#1 12 V-DC through RJ-11 serial port (for diagnostic purpose)

: Only one of the above input voltage options should be used at a time, to power on the device. Combination of any two options, may damage the device. Tabulated below are the power consumption details. Products Typical Consumption (With Consumption Heaters ON) 6 Watts 17 Watts maximum, with two heaters ON 12 Watts 22 Watts maximum, with two heaters ON MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8250-EPR/LNK MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA/LNK QB-8250-EPR/LNK Output Voltage*

48VDC through Ethernet Port #2. Power Always ON.

: Output voltage of 48VDC requires a 60-80W high power POE, available with Proxim Wireless Corporation on request. Power over Ethernet Injector Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 5.24x2.13x1.42 inches(133x54x36 mm) Temp: 0 to 40 C Input: 100 250 V-AC (47 63 Hz) y y Output: 48 V-DC at 0.67 A (32 Watts) y y y Weight: 7 ounces (200 g) y

132 z

Tsunami 800 and 8000 Series - Hardware Installation Guide Products Category Specification Technical Specifications MP-8160-BSU MP-8160-BS9 MP-8160-SUA Input Voltage Output Voltage*

Power over Ethernet Injector Products Category MP-8150-CPE QB-8150-LNK-12 QB-8150-LNK-50 Input Voltage PoE Injector

: Only one of the above input voltage options should be used at a time, to power on the device. Combination of any two options, may damage the device. Temp: 0 to 40 C Via RJ-45 Ethernet interface supplying 48 VDC and 0.67 A on Ethernet Port#1 12 V-DC through serial port (for diagnostic purpose) Input: 100 250 V-AC (47 63 Hz) 48VDC through Ethernet Port #2. Power Always On. Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 5.24x2.13x1.42 inches(133x54x36 mm) y y y Consumption 10 Watts typical (13.8 Watts maximum with one heater ON) y y Output: 48 V-DC at 0.67 A (32 Watts) y y y Weight: 7 ounces (200 g) y y y y Consumption 7 Watts typical (13.8 Watts maximum) y y Output: 48 V-DC at 0.40 A (19 Watts) y y y Weight: 5.6 ounces (160 g) y Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 3.98 x 2.40 x 1.35 inches (101.0x61.5x32.2 mm) Via RJ-45 Ethernet interface supplying 48 VDC and 0.40 A on Ethernet Port 12 V-DC through serial port (for diagnostic purpose) Input: 100 250 V-AC (47 63 Hz) Temp: 0 to 40 C Specification

: Only one of the above input voltage options should be used at a time, to power on the device. Combination of any two options, may damage the device. Tsunami 800 and 8000 Series - Hardware Installation Guide 133 Technical Specifications Products Category Specification Via RJ-45 Ethernet interface supplying 48 VDC and 0.40A on Ethernet Port MP-826-CPE-50 Input Voltage PoE Injector Products Category MP-8160-CPE-A100 Input Voltage PoE Injector Products Category MP-825-CPE-50 MP-825-CPE-100 QB-825-EPR-50 Input Voltage PoE Injector Via RJ-45 Ethernet interface supplying 48 VDC and 0.40A on Ethernet Port Specification Temp: 0 to 40 C Temp: 0 to 40 C Input: 100 250 V-AC (47 63 Hz) Input: 100 250 V-AC (47 63 Hz) Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 3.98 x 2.40 x 1.35 inches (101.0x61.5x32.2 mm) Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 4.96 x 8.62 x 2.58 inches (126 x 219 x 65.5 mm) y y Consumption of 10 Watts typical (18 Watts max with one heater ON) y y Output: 48 V-DC at 0.40 A (19 Watts) y y y Weight: 5.6 ounces (160 g) y y y Consumption 5 Watts typical (10 Watts maximum) y y Output: 48 V-DC at 0.40 A (19 Watts) y y y Weight: 5.6 ounces (160 g) y y y Consumption 6 Watts typical (15 Watts max with two heaters ON) y y Output: 48 V-DC at 0.40 A (16 Watts) y y y Weight: 5.6 ounces (160 g) y Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 3.98 x 2.40 x 1.35 inches (101.0x61.5x32.2 mm) Input: 100 250 V-AC (47 63 Hz) Temp: 0 to 40 C Specification Via RJ-45 Ethernet interface supplying 48 VDC and 0.40A on Ethernet Port Tsunami 800 and 8000 Series - Hardware Installation Guide 134 Products Category Specification Technical Specifications Input Voltage MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 QB-825-EPR/LNK-50+

Power Consumption PoE Injector Hardware Specifications Products Radio Typical Consumption: 6 Watts Input: 100 250 V-AC (47 63 Hz) 12 V-DC through RJ-11 serial port (for diagnostic purpose)

: Only one of the above input voltage options should be used at a time, to power on the device. Combination of any two options, may damage the device. y Via RJ-45 Ethernet interface supplying 48 VDC and 0.67A on Ethernet Port#1 y y y Consumption (With Heaters ON): 16 Watts maximum, with two heaters ON y y Output: 48 V-DC at 0.67 A (32 Watts) y y y Weight: 7 ounces (200 g) y Pin-out: +48 V on pins 4/5, -48 V on pins 7/8 Size: 5.24x2.13x1.42 inches(133x54x36 mm) Temp: 0 to 40 C Clock Speed Input Power Memory Power Consumption MP-8100-BSU MP-8100-SUA QB-8100-EPA MP-8150-SUR QB-8150-EPR MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 QB-825-EPR-50+

MP-8150-SUR-100 QB-8150-EPR-100 QB-8151-EPR MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA QB-8250-EPR MP-8160-BSU MP-8160-BS9 MP-8160-SUA 2.4 and 5 GHz MIMO dual band radio 680 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.67 A 6 Watts typical (17 Watts max with two heaters ON) 4.900 to 5.925 GHz MIMO radio 680 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.67 A 6 Watts typical (17 Watts max with two heaters ON) 5.150 to 5.925 GHz MIMO radio 560 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.67 A 6 Watts typical (16 Watts max with two heaters ON) 4.900 to 5.875 GHz MIMO radio 680 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.67 A 6 Watts typical (17 Watts max with two heaters ON) 4.900 to 5.925 GHz MIMO High Power radio 680 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.67 A 12 Watts typical (22 Watts max with two heater ON) 5.900 to 6.425 GHz MIMO radio 680 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.67 A 10 Watts typical (13.8 Watts max with one heater ON) Tsunami 800 and 8000 Series - Hardware Installation Guide 135 Technical Specifications MP-8150-CPE QB-8150-EPR-12 QB-8150-EPR-50 MP-8160-CPE-A100 MP-825-CPE-50 MP-825-CPE-100 QB-825-EPR-50 MP-826-CPE-50 5.3 to 6.1GHz MIMO radio 333 MHz 333 MHz Power-over-Ethernet 48 VDC, 0.40 A 7 Watts typical (13.8 Watts max) 5.900 to 6.425 GHz MIMO radio 333 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.40 A 5 Watts typical (10 Watts max) 5.15 to 5.925 GHz MIMO radio 560 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.4 A 6 Watts typical (15 Watts max with two heaters ON) 5.900 to 6.425 GHz MIMO radio 560 MHz Flash: 16 MB RAM: 128 MB Power-over-Ethernet 48 VDC, 0.4 A 10 Watts typical (17 Watts max with one heater ON) Tsunami 800 and 8000 Series - Hardware Installation Guide 136 Integrated Antenna Specifications Products: MP-8150-SUR; QB-8150-EPR/LNK; MP-8250-SUR; MP-8250-BS1; QB-8250-LNK Feature Specification Frequency Band 4.900 5.875 GHz Technical Specifications Gain 3dB Beamwidth 3dB Beamwidth Polarization Cross Polarization Port to Port Isolation Power Handling VSWR 22 dBi (Cable loss included) 7 - 9 (Hplane) 7 - 9 (Eplane) Dual (Vertical + Horizontal)

-25 dB

-30 dB 5 W (cw) 1.7:1 Max Standard Compliance ETSI TS3, TS4, TS5 Lightning Protection DC Ground Radio Patterns Tsunami 800 and 8000 Series - Hardware Installation Guide 137 Antenna Tilt Angles and corresponding EIRP values:

: These values are applicable only to the devices operating in U-NII-1US frequency band (5.15 - 5.25GHz) Technical Specifications

-10 degree indicates that the antenna is tilted downwards 10 degrees indicates that the antenna is titled upwards

Tilt Angle Products: MP-8150-SUR; QB-8150-EPR/LNK; MP-8250-SUR; MP-8250-BS1; QB-8250-LNK Horizontal Side Vertical Side Allowed EIRP of Product Remarks Lobe Lobe Transmit Power 0

-10

-20

-30 10 20 30 12 12 19 19 12 10 0 16 16 18 19 14 13 0 7 7 13 14 7 5

-5 33 33 39 40 33 31 21 Not recommended For detailed exlplanation of the various constituents in the table, please refer Antenna Installation guide > 1.2.3.2 Antenna Tilt Angles and Corresponding EIRP values in the page number 12 Tsunami 800 and 8000 Series - Hardware Installation Guide 138 Technical Specifications Products: MP-8150-CPE; QB-8150-LNK-12/50 Feature Specification Vertical Polarization Horizontal Polarization 15 - 16 dBi 16.5o 18.3o 17.0o - 24.0o

-8 dB (Max)

-21 dB (Max) Linear, Horizontal Frequency Band 5.300 6.100 GHz Gain 15 - 16 dBi Horizontal Half Power Beam Width 17.6o 20.3o Vertical Half Power Beam Width 16.1o - 20.5o Sidelobes Level Front-to-back-ratio Polarization

-10 dB (Max) 23 dB (Max) Linear, Vertical Port to Port Isolation 27 dB (Min.) Power Handling VSWR Input Impedance 6 W (cw) 2.0:1 (Max) 50 ohm Standard Compliance ETSI TS3, TS4, TS5 Lightning Protection DC Ground Radio Patterns Tsunami 800 and 8000 Series - Hardware Installation Guide 139 Technical Specifications Product: MP-8160-CPE-A100, MP-826-CPE-50 Feature Specification Frequency Range 5900 6400 MHz Polarization Gain Vertical/Horizontal 13.5-14.5 dBi / 14.0-15 dBi Horizontal Half Power Beam Width 35-40 / 25-35 Vertical Half Power Beam Width 15- 18 VSWR Isolation Input Impedance Lightning Protection Radio Patterns (V-Polar Port) 2:1 (Max) 25 dB (Min) 50 ohm DC Ground Radio Patterns (H-Polar Port) Tsunami 800 and 8000 Series - Hardware Installation Guide 140 Technical Specifications Products: MP-8150-SUR-100; QB-8151-EPR / LNK Feature Specification Vertical Polarization Horizontal Polarization Frequency Band 4900 - 5875 MHz 21.01 dBi Linear, Horizontal Gain Horizontal Half Power Beam Width Vertical Half Power Beam Width Sidelobes Level Front-to-back-ratio Polarization Isolation Power Handling VSWR Input Impedance Lightning Protection Radio Patterns 20.01 dBi 8o (typ.) 8o (typ.)

-8 dB (Max)

-30 dB (Max) Linear, Vertical 25 dB (min.) 2W (cw) 2.0: 1 (Max) 50 ohm DC Ground Tsunami 800 and 8000 Series - Hardware Installation Guide 141 Technical Specifications Antenna Tilt Angles and corresponding EIRP values:

: These values are applicable only to the devices operating in U-NII-1US frequency band (5.15 - 5.25GHz) Products: MP-8150-SUR-100; QB-8151-EPR / LNK Tilt Angle Horizontal Side Vertical Side Allowed EIRP of Product Remarks Lobe Lobe Transmit Power 0

-10

-20

-30 10 20 30 13 13 14 14 13 7 0 13 14 14 14 11 10 0 10 10 11 11 8 4

-3 34 34 35 35 32 28 21 Not recommended Feature Specification Products: MP-8160-BS9 Frequency Range 5.7 - 6.425 GHz Polarization Gain VSWR, max. 3.5 dB Beam-Width, H-Plane 3 dB Beam-Width, E-Plane Dual, Vertical and Horizontal 16 dBi 1.7:1 90 8.5 Side Lobes, min.

-25 dB (azimuth) Cross Polarization, min. Port to Port Isolation Front to Back Ratio, min. Input Power, max Input Impedance

-18 dB

-45 dB

-40 dB 10 Watt 50 Ohm Lightning Protection DC Grounded Tsunami 800 and 8000 Series - Hardware Installation Guide 142 Feature Radio Patterns Products: MP-8160-BS9 Specification Technical Specifications MP-825-CPE-50, MP-825-CPE-100, MP-825-SUR-50+, MP-825-BS3-100, QB-825-LNK-50, and QB-825-LNK-50+

Feature Specification Vertical Polarization Horizontal Polarization Frequency Band 5.15 - 5.925 MHz Gain 15 - 16 dBi (14 dBi beyond 5.850 GHz) Horizontal Half Power Beam Width Vertical Half Power Beam Width Sidelobes Level Polarization Isolation VSWR Lightning Protection 31o 38o 14o - 16o 12 dB (Min) Dual, Vertical and Horizontal

> 30 dB typl.

< 2.0:1 (Max) DC Grounded 30o 34o 14o - 17o 10 dB (Min) Tsunami 800 and 8000 Series - Hardware Installation Guide 143 MP-825-CPE-50, MP-825-CPE-100, MP-825-SUR-50+, MP-825-BS3-100, QB-825-LNK-50, and QB-825-LNK-50+

Feature Radio Patterns (V-Polar Port) Specification Technical Specifications Radio Patterns (H-Polar Port) Antenna Tilt Angles and corresponding EIRP values:

: These values are applicable only to the devices operating in U-NII-1US frequency band (5.15 - 5.25GHz) MP-825-CPE-50, MP-825-CPE-100, MP-825-SUR-50+, MP-825-BS3-100, QB-825-LNK-50, and QB-825-LNK-50+

Tilt Angle Horizontal Side Vertical Side Allowed EIRP of Product Remarks Lobe Lobe Transmit Power 0

-10

-20

-30 10 20 30 9 13 13 13 8 0 0 13 16 16 20 13 0 0 11 15 15 15 10 2 2 30 34 34 34 29 21 21 Tsunami 800 and 8000 Series - Hardware Installation Guide 144 Technical Specifications Feature Specification Products: MP-8250-BS9 Frequency Band 4.9 6.1 MHz Gain, typ. VSWR, Max. Polarization 16 dBi 1.7:1 Dual Pol., Vertical and Horizontal 3 dB Beam-Width, H-Plane, typ. 3 dB Beam-Width, E-Plane, typ. 90o 8o Sidelobes Level, Min. V-Pol: ETSI EN 302 085 V1.2.3 CS2 H-Pol: ETSI EN 302 085 V1.2.3 CS3 Cross Polarization, min. Front to Back Ratio, min. Port to Port Isolation, min. Input power, max Input Impedance

-15 dB

-30 dB

-30 dB 10 Watt 50 Ohm Lightning Protection DC Grounded Radio Patterns (V-Polar Port) Tsunami 800 and 8000 Series - Hardware Installation Guide 145 Feature Radio Patterns (H-Polar Port) Products: MP-8250-BS9 Specification Technical Specifications Antenna Tilt Angles and corresponding EIRP values:

: These values are applicable only to the devices operating in U-NII-1US frequency band (5.15 - 5.25GHz) Tilt Angle Horizontal Side Vertical Side Allowed EIRP of Product Remarks Lobe Lobe Transmit Power Products: Products: MP-8250-BS9 0

-10

-20

-30 10 20 30 16 17 17 17 17 13 0 18 18 18 20 18 10 0 18 19 19 19 19 12 2 37 38 38 38 38 31 21 Tsunami 800 and 8000 Series - Hardware Installation Guide 146 Technical Specifications Physical Specifications Products Category Specification MP-8100-BSU, MP-8100-SUA QB-8100-EPA MP-8150-SUR QB-8150-EPR MP-8150-SUR-100 QB-8150-EPR-100 QB-8151-EPR MP-8200-BSU MP-8200-SUA QB-8200-EPA MP-8250-SUR MP-8250-BS9 MP-8250-BS1 QB-8250-EPR MP-8160-BSU MP-8160-SUA Dimensions (L x W x H) 10.79 x 11.14 x 3.38 inches (274 x 283 x 86 mm) Weight 7.7 lbs (3.5 kg) Dimensions (L x W x H) 14.57 x 14.57 x 4.47 inches (370 x 370 x 113.5 mm) Weight 9.0 lbs (4.1 kg) Dimensions (L x W x H) 14.57 x 14.57 x 4.21 inches (370 x 370 x 107 mm) Weight 8.45 lbs (3.85 kg) Dimensions (L x W x H) 10.79 x 11.14 x 3.38 inches (274 x 283 x 86 mm) Weight 7.9 lbs (3.6 kg) Dimensions (L x W x H) 14.57 x 14.57 x 4.47 inches (370 x 370 x 113.5 mm) Weight 9.26 lbs (4.2 kg) Dimensions (L x W x H) 10.79 x 11.14 x 3.38 inches (274 x 283 x 86 mm) Weight 7.38 lbs (3.35 kg) MP-8160-BS9 Dimensions (L x W x H) 14.57 x 14.57 x 4.47 in (370 x 370 x 113.5 mm) Weight 8.82 lbs (4 kg) MP-8150-CPE Dimensions (L x W x H) 7.77 x 7.56 x 3.94 inches (197.5 x 192 x 100mm) MP-8160-CPE-A100 Dimensions (L x W x H) 8.46 x 4.78 x 2.56 inches (215 x 121.5 x 65 mm) Weight 1.6 lbs (0.73 kg) MP-820-BSU-100 MP-820-SUA-50+

MP-826-CPE-50 MP-825-CPE-50 MP-825-CPE-100 MP-825-SUR-50+

MP-825-BS3-100 QB-825-EPR-50 QB-825-EPR-50+

QB-8150-EPR-12 QB-8150-EPR-50 Weight 1.93 lbs (0.88 kg) Dimensions (L x W x H) 5.02 x 8.68 x 2.85 inches (127.5 x 220.5 x 72.5 mm) Weight 2.75 lbs (1.250 kg) Dimensions (L x W x H) 4.96 x 8.62 x 2.58 inches (126 x 219 x 65.5 mm) Weight 2.1 lbs (0.95 kg) Dimensions (L x W x H) 7.77 x 7.56 x 3.94 inches (197.5 x 192 x 100mm) Weight 1.6 lbs (0.73 kg) Tsunami 800 and 8000 Series - Hardware Installation Guide 147 Environmental Specifications Products Operating Temperature Storage Temperature Humidity Technical Specifications

-40 to 60C

(-40 to 140 Fahrenheit)

-55 to 80C

(-67 to 176 Fahrenheit) 100% (non-condensing)

-35 to 55C

(-31 to 131 Fahrenheit)

-40 to 70C

(-40 to 158 Fahrenheit) Max 95% relative humidity

(non-condensing)

-40 to 55C

(-40 to 131 Fahrenheit)

-45 to 70C

(-49 to 158 Fahrenheit) Max 95% relative humidity

(non-condensing)

-40 to 55C (-40 to 131 Fahrenheit)

-55 to 70C (-67 to 158 Fahrenheit) 100% (non-condensing) MP-8100-BSU; MP-8100-SUA MP-8150-SUR; MP-8150-SUR-100 MP-8200-BSU; MP-8200-SUA MP-8250-SUR; MP-8160-BSU MP-8160-BS9; MP-8160-SUA MP-8250-BS9; MP-8250-BS1 QB-8100-EPA/LNK; QB-8150-EPR/LNK QB-8150-LNK-100; QB-8151-EPR/LNK QB-8200-EPA/LNK; QB-8250-EPR/LNK MP-8150-CPE QB-8150-LNK-12/50 MP-8160-CPE-A100 MP-826-CPE-50 MP-825-CPE-50 MP-825-CPE-100 MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 QB-825-EPR/LNK-50+

QB-825-EPR/LNK-50 Tsunami 800 and 8000 Series - Hardware Installation Guide 148 Technical Specifications MTBF Products MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8160-BSU MP-8160-BS9 MP-8160-SUA QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK MP-8150-CPE MP-8160-CPE-A100 QB-8150-LNK-12/50 MP-826-CPE-50 MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA/LNK QB-8250-EPR/LNK MP-820-BSU-100 MP-820-SUA-50+

MP-825-SUR-50+

MP-825-BS3-100 MP-825-CPE-50 MP-825-CPE-100 QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+

MTBF

>80,000 hours 75,000 hours

>2,00,000 hours

>250,000 hours

>350,000 hours Tsunami 800 and 8000 Series - Hardware Installation Guide 149 Appendix - Additional Weatherproofing Steps This chapter explains the method to add an additional layer of protection to the connectors (Ethernet) against the environment.

: We have taken MP-8100-BSU as an example to explain the weatherproofing steps. The same method should be followed to weatherproof the Ethernet connectors of the Tsunami 800 and 8000 series products. A.1 Material for Weatherproofing The material required for weatherproofing connectors are, 1. Any standard Butyl Mastic Tape 2. Any standard Vinyl Tape We have used the following Butyl Mastic Tape and Vinyl Tape as an example to demonstrate the weatherproofing steps:

A.2 Weatherproofing Steps 1. Wrap a vinyl tape in a half-lapped fashion, from the weatherproofed connector end and continue wrapping till 3 inches onto the cable.

(a)

(b) Figure A-1 Step1

(c) Tsunami 800 and 8000 Series - Hardware Installation Guide 150 2. Wrap a second layer of the vinyl tape over the first layer but in other direction. Appendix - Additional Weatherproofing Steps

(a)

(b) Figure A-2 Step2 3. Now, wrap a layer of vinyl tape with the adhesive side out as it provides sticky surface for the next layer.

(a)

(b) Figure A-3 Step3 4. Next, wrap a layer of the butyl mastic tape on the adhesive side.

(a)

(b) Figure A-4 Step3 5. Finally, wrap vinyl tap over the butyl layer.

(a)

(b) Figure A-5 Step3 Tsunami 800 and 8000 Series - Hardware Installation Guide 151 Appendix - Lightning Protection Lightning protection is used to maximize the reliability of the communications equipment by safely re-directing current from a lightning strike or a power surge traveling along the Cat 5/Cat5e/Cat 6 Ethernet cabling to the ground using the shortest path possible. Designing a proper grounding system prior to installing any communications equipment is critical to minimize the possibility of equipment damage, void warranties, and cause serious injury. The surge arrestor (sometimes referred to as a lightning protector) can protect your sensitive electronic equipment from high-voltage surges caused by discharges and transients at the PoE. Proxim Wireless offers superior lightning and surge protection for Tsunami series products. Contact your reseller or distributor for more information. Tsunami 800 and 8000 Series - Hardware Installation Guide 152 Appendix - Abbreviations AWG American Wire Gauge Abbreviations BSU CLI CPE DC ESD FCS LED MIMO MTBF OFDM PC PoE PTMP PTP QB QIG RSSI Rx SU Tx Base Station Unit Command Line Interface Customer Premises Equipment Direct Current Electrostatic Discharge Frame Check Sequence Light Emitting Diode Multiple-input and Multiple-output Mean Time Between Failures Orthogonal frequency-division multiplexing Personal Computer Power Over Ethernet Point-to-multipoint Point-to-point Quick Bridge Quick Installation Guide Received Signal Strength Indicator Receiver Subscriber Unit Transmission WORP Wireless Outdoor Router Protocol Tsunami 800 and 8000 Series - Hardware Installation Guide 153 Appendix - Statement of Warranty Warranty Coverage Proxim Wireless Corporation warrants that its products are manufactured solely from new parts, conform substantially to specifications, and will be free of defects in material and workmanship for a Warranty Period of 1 year from the date of purchase. Repair or Replacement When Proxim determines that a returned product does not meet the warranted criteria during the warranty period, Proxim at its option, will either: (a) repair the defective product; (b) replace the defective product with a new or refurbished product that is at least equivalent to the original; or (c) refund the price paid for the defective product. Generally, products are repaired or replaced within thirty (30) business days of receipt of the product at a Proxim Logistical/Repair Center. The warranty period for repaired or replacement products is ninety (90) days or the remainder of the original warranty period, whichever is longer. These three alternatives constitute the customers sole and exclusive remedy and Proxims sole and exclusive liability under warranty provisions. Limitations of Warranty Proxims warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than Proxim, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by Proxim, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Buyers can contact Proxim Wireless Customer Service Center either by telephone or via web. Support and repair of products that are out of warranty will be subject to a fee. Contact information is shown below. Additional support information can be Contact technical support via telephone as follows:

. Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers USA and Canada Customers found at Proxim Wirelesss web site at y y y y Tsunami 800 and 8000 Series - Hardware Installation Guide 154 Appendix - Statement of Warranty General Procedures When contacting the Customer Service for support, Buyer should be prepared to provide the product description and serial number and a description of the problem. The serial number should be on the product. In the event the Customer Service Center determines that the problem can be corrected with a software update, Buyer might be instructed to download the update from Proxim Wirelesss web site or, if thats not possible, the update will be sent to Buyer. In the event the Customer Service Center instructs Buyer to return the product to Proxim Wireless for repair or replacement, the Customer Service Center will provide Buyer a Return Material Authorization (RMA) number and shipping instructions. Buyer must return the defective product to Proxim Wireless, properly packaged to prevent damage, shipping prepaid, with the RMA number prominently displayed on the outside of the container. Calls to the Customer Service Center for reasons other than product failure will not be accepted unless Buyer has purchased a Proxim Wireless Service Contract or the call is made within the warranty period. After the warranty period, Technical Support If Proxim Wireless reasonably determines that a returned product is not defective or is not covered by the terms of this Warranty, Buyer shall be charged a service charge and return shipping charges. Search Knowledgebase Other Information Create a Support Request

). is fee based (detailed in Proxim Wireless stores all resolved problems in a solution database at the following URL:

. Create a support request with Proxim Wireless technical support staff at the following URL:

. Tsunami 800 and 8000 Series - Hardware Installation Guide 155 Appendix - Technical Services and Support Obtaining Technical Service and Support If you are having trouble using the Proxim product, please read this manual and the additional documentation provided with your product. If you require additional support to resolve your issue, please be ready to provide the following information before you contact Proxims Technical Services team:

If the product is not registered, date and location where you purchased the product

: Technical Support is free for the warranty period from the date of purchase. Part number and serial number of the suspected faulty device Network information (What kind of network are you using?) Circumstances that preceded or led up to the error Support Options Proxim eService Web Site Support Product information Registration information Trouble/error information ServPak account number Message or alarms viewed Trouble/symptom being experienced Activities completed to confirm fault Steps taken to reproduce the problem ServPak information (if a Servpak customer):

y y y y The Proxim eService Web site is available 7x24x365 at y y y y y y y On the Proxim eService Web Site, you can access the following services:

Product Download Page: Provides quick links to product firmware, software, and documentation downloads. Proxim TV Links: A link to helpful video tutorials. Knowledgebase: A solution database of all the resolved problems. You can search by product, category, keywords, or phrases. Live Chat: Chat with a support technician on-line or request to call back at a later time. Create a Support Request: Create a support request with our technical support staff who will reply to you by email. Case Management: Login to check the status of your support cases, update your personal profile, or access restricted information and features. Provide Feedback: Submit a suggestion, complaint, or other feedback about the support site and our products. Tsunami 800 and 8000 Series - Hardware Installation Guide 156 Telephone Support Contact technical support via telephone as follows:

USA and Canada Customers Appendix - Technical Services and Support Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers ServPak Support Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) To provide even greater investment protection, Proxim Wireless offers a cost-effective support program called ServPak. ServPak is a program of enhanced service support options that can be purchased as a bundle or individually, tailored to meet your specific needs. Whether your requirement is round the clock technical support or advance replacement service, we are confident that the level of support provided in every service in our portfolio will exceed your expectations. All ServPak service bundles are sold as service contracts that provide coverage for specific products from 1 to 3 years. Servpak bundles are considered an upgrade to the standard product warranty and not an extension. y y y y 24x7 Basic Technical Support Basic Advanced Replacement

(Two business days/

International economy shipment service) Priority Advanced Replacement

(Next business day/

International priority shipment service) Priority Comprehensive Advance Replacement

(Next business day/

International priority shipment service) 8x7 Advanced Technical Support Software Maintenance Access to Knowledge Base 24x7 Advanced Technical 24x7 Advanced Technical Support Support PVES & PV NMS PVES & PV NMS Support Support Post-Installation Optimization 50% discount on Onsite Technical Support and Services Tsunami 800 and 8000 Series - Hardware Installation Guide 157 Appendix - Technical Services and Support Additional Information on ServPak Options Advanced Replacement of Hardware In the event of a hardware failure, our guaranteed turnaround time for return to factory repair is 30 days or less. Customers who purchase this service are guaranteed replacement of refurbished or new hardware to be shipped out within one or two business days, as applicable. Options are available for shipment services depending on the customers support needs. Hardware is shipped on business days, Monday Friday excluding Holidays, 8:00 AM 3:30 PM Eastern Time. Comprehensive Advanced Replacement of Hardware In addition to ServPak Prime options, in the event of a hardware failure, Proxim will repair or replace the failed product for any reason, other than vandalism. 7x24x365 Availability Unlimited, direct access to technical support engineers 24 hours a day, 7 days a week, 365 days a year including Holidays. 8x5 Availability Unlimited, direct access to world-class technical support engineers 8 hours a day, 5 days a week, Monday through Friday from 8:00AM - 5:00PM Pacific Standard Time. Basic Technical Support Customers who purchase this service can be rest assured that their call will be answered by Proxims Tier 1 technical support and a case opened immediately to document the problem and provide initial troubleshooting to identify the solution and resolve the incident in a timely manner. Advanced Technical Support In addition to Proxims world-class Tier 1 technical support, customers will be able to have their more complex issues escalated to our world-class Tier 3 technical support engineers. Our Tier 3 engineers will review specific configurations to troubleshoot intricate issues and will also provide helpful insights regarding Proxims products and various tips from decades of collective experience in the wireless industry. Software Maintenance It's important to maintain and enhance security and performance of wireless equipment and Proxim makes this easy by providing a Software Maintenance program that enables customers to access new feature and functionality rich software upgrades and updates. Customers will also have full access to Proxim's vast Knowledgebase of technical bulletins, white papers and troubleshooting documents. Post-Installation Optimization You can consult with our technical support engineers to enhance performance and efficiency of your network. Post-installation optimization services include:

Review frequencies to select best possible channel Review Modulation, Channel Bandwidth, MIMO, and WORP settings to optimize throughput and link quality Review Satellite Density & TPC/ATPC settings Assistance with Bandwidth controls Tsunami 800 and 8000 Series - Hardware Installation Guide 158 y y y y Appendix - Technical Services and Support To purchase ServPak support services, please contact your authorized Proxim distributor. To receive more information or for questions at our website options, support visit the of

) or send an All Customers are entitled to free technical support for the Proxim products they purchase from Proxims authorized resellers

) and/or via telephone. This technical support will be provided for free for the entire time the product is covered by a Proxim warranty.The term of Proxims warranty is determined according to the agreement under which the product was sold and generally varies from 3 months to 2 years depending on the product. If a Customer disagrees with Proxims determination of warranty duration, a request for review supported by a copy of all product purchase documentation may be submitted. After the warranty period, technical support on products then being sold by Proxim will be based upon one of the following three options Customers can choose:

Customers can choose to purchase one of Proxims ServPak extended warranty and enhanced support packages for the product Customers can choose to purchase one-time per-incident technical support for the product for a fee Customers can choose to call the reseller or distributor who sold them the product for technical support Technical Support Policy Technical Support for Current Products after Warranty Period Technical Support for Current Products during Warranty Period

. on any please ServPak available Assistance with QoS, RADIUS, and VLAN settings on Proxim equipment y

, call Proxim Support (For telephone numbers, see email to or distributors. Technical Support is defined as communication via the Proxim Support website (

y y y y y y No EOL ServPak support package is available for certain discontinued products Tech Support on Discontinued Products Technical Support on some products that Proxim has declared as EOL (End of Life) or otherwise is no longer selling is available based upon one of the following three options Customers can choose:

For some discontinued products, Customers can choose to purchase one of Proxims EOL ServPak support packages for the product No EOL ServPak support package will be available for any product discontinued more than 5 years ago Customers can choose to purchase one-time per-incident technical support for the product on a per hour basis at a rate of $125 an hour (4 hours minimum payable in advance by major credit card). This fee is payable in addition to any RMA fee that may be charged to subsequently repair the product. Customers can choose to call the reseller or distributor who sold them the product for technical support All Proxim technical support for discontinued products, whether through an EOL ServPak package or otherwise, is provided on a best effort basis and is subject to the continued availability of necessary components, equipment, and other technical resources. Note that Proxim is unable to support or warrant any equipment that has been modified, whether this modification is physical, or if third-party software codes have been loaded onto the product. Tsunami 800 and 8000 Series - Hardware Installation Guide 159