Proxim Wireless MB82HP49 Tsunami 8000 Point-to-Point and Point-to-multipoint Product User Manual

Proxim Wireless Corporation Tsunami 8000 Point-to-Point and Point-to-multipoint Product

UserManual.wiki >

Proxim Wireless >

MB82HP49 User Manual

User Manual

Tsunami® 8100 Series (Point-to-point and Point-to-multipoint Products) Software Management Guide Products Covered Tsunami® MP-8100-BSU / MP-8100-WD-HP - Tsunami® MP-8100-SUA / MP-8100-WD-HP - Tsunami® MP-8150-SUR / MP-815-WD-HP - Tsunami® MP-8150-CPE Tsunami® MP-8160-BSU - Tsunami® MP-8160-SUA - Tsunami® MP-8160-CPE Tsunami® QB-8100-EPA Tsunami® QB-8100-LNK Tsunami® QB-8150-EPR Tsunami® QB-8150-LNK Tsunami® QB-8150-LNK-12/50

Contents Preface. . . 8 1 Overview . . . ........................................................................................................................................ 10 About Tsunami® 8100 Products . 10 Wireless Network Topology . 11 Point-to-Multipoint (PTMP). . . 11 Point-to-Point Link . . . 14 Multiple-Input-Multiple-Output (MIMO) . . . . 17 Wireless Outdoor Router Protocol (WORP) . . . . 17 2 Management and Monitoring Capabilities . . . .................................................................................... 19 Web (HTTP/HTTPS) Interface . . . . 19 Command Line Interface . . . . 19 HyperTerminal . . . 19 Telnet. . . 20 Secure Shell (SSH) . . . 20 SNMP Management . . . . 20 ProximVision ES . . . . 20 3 Device Initialization . . . 21 Initialization . . . . 21 ScanTool . . . 21 Initialize Device using ScanTool. . . 22 Modifying the IP Address of the Device using ScanTool . . . 23 Logging onto the Web Interface . 23 Home Page . . . 25 COMMIT . . . 26 REBOOT. . . 27 Factory Default Configuration . 27 4 Basic Configuration . . . ....................................................................................................................... 29 5 Advanced Configuration . . . 34 System . . . . 34 Network . 35 IP Configuration (Bridge Mode) . . . 36 IP Configuration (Routing Mode) . . . 38 IP Configuration (Routing Mode with PPPoE Client Enabled) 40 Ethernet . 42 Basic Ethernet Configuration . . . 42 Advanced Configuration . . . 43 Wireless . . . . 44 Tsunami® 8100 Series - Software Management Guide 3

Wireless Outdoor Router Protocol (WORP). . . 44 Wireless Interface Properties . . . 49 MIMO Properties . . . 57 Dynamic Frequency Selection (DFS) . . . 59 DDRS. . . 64 Security . . . . 68 Wireless Security . . . 68 RADIUS . . . 71 MAC ACL . . . 73 Quality of Service (QoS) . . . . 74 QoS Concepts and Definitions . . . 74 QoS Configuration . . . 79 QoS Configuration for a Management Station . . . 96 RADIUS Based SU QoS Configuration . 100 VLAN (Bridge Mode Only) . . . . 101 System-Level VLAN Configuration . . . 101 Ethernet VLAN Configuration . . . 102 RADIUS Based SU VLAN Configuration . 107 Filtering (Bridge Only) . 109 Protocol Filter . . . 110 Static MAC Address Filter . . . 113 Advanced Filtering. . . 116 TCP/UDP Port Filter . . . 118 Storm Threshold Filter . . . 120 WORP Intra Cell Blocking. . . 121 DHCP . . . . 125 DHCP Pool. . . 125 DHCP Server . . . 126 DHCP Relay (Routing Mode only). . . 127 IGMP Snooping . . . . 128 Routing Mode Features . . . . 130 Static Route Table . . . 130 Network Address Translation (NAT) . . . 132 RIP. . . 135 PPPoE End Point (SU Only) . . . 136 IP over IP Tunneling . . . 142 6 Management. . . ...................................................................................................................................... 147 System . 147 System Information . . . 147 Inventory Management . . . 148 Licensed Features . . . 149 Tsunami® 8100 Series - Software Management Guide 4

File Management . . . . 150 TFTP Server . . . 150 Text Based Configuration (TBC) File Management . . . 151 Upgrade Firmware. . . 153 Upgrade Configuration . . . 154 Retrieve From Device . . . 156 Services . . . . 159 HTTP/HTTPS. . . 159 Telnet/SSH . . . 160 SNMP . . . 162 Logs . . . 165 Simple Network Time Protocol (SNTP) . 167 Access Control . 169 Reset to Factory . . . . 170 Convert QB to MP . . . . 171 7 Monitor . . . 173 Interface Statistics . 173 Ethernet Statistics . . . 173 Wireless Statistics 175 PPPoE Statistics . . . 176 IP Tunnels . . . 177 WORP Statistics . . . . 179 General Statistics. . . 179 SU / End Point B Link Statistics. . . 181 BSU/End Point A Link Statistics. . . 184 QoS Statistics (BSU or End Point A Only) . . . 185 Active VLAN . 186 Bridge . . . . 187 Bridge Statistics . . . 187 Learn Table . . . 188 Network Layer . . . . 189 Routing Table . . . 189 IP ARP . . . 189 ICMP Statistics. . . 190 RIP Database . . . 191 RADIUS (BSU or End Point A only) . . . . 192 Authentication Statistics . . . 192 IGMP . . . . 193 Ethernet or Wireless Multicast List . . . 193 Router Port List . . . 194 Tsunami® 8100 Series - Software Management Guide 5

DHCP . . . . 194 Logs . 195 Event Log . . . 195 Syslog . . . 196 Debug Log . . . 196 Temperature Log . . . 197 Tools . 198 Wireless Site Survey. . . 198 Scan Tool. . . 199 sFlow® . . . 199 Console Commands . . . 204 SNMP v3 Statistics . . . . 204 8 Troubleshooting . . . 205 PoE Injector . . . . 206 Connectivity Issues . 206 Surge or Lightning Issues (For Connectorized devices) . 207 Setup and Configuration Issues . . . . 208 Application Specific Troubleshooting . 209 Wireless Link Issues . 210 Wired (Ethernet) Interface Validation . . . . 211 Wireless Interface Validation . 212 Recovery Procedures . 213 Soft Reset to Factory Defaults . . . 213 Hard Reset to Factory Defaults. . . 213 Forced Reload . . . 214 Setting IP Address using Serial Port . . . 216 Spectrum Analyzer . 217 Avoiding Interference . . . 218 Conclusion . . . 218 Miscellaneous . 218 Unable to Retrieve Event Logs through HTTPS . . . 218 A Feature Applicability . . . 219 B Parameters Requiring Reboot . . . .................................................................................................... 220 C Frequency Domains and Channels . . . 223 D SNR Information. . . 231 E Bootloader CLI and ScanTool. . . 235 Tsunami® 8100 Series - Software Management Guide 6

F Lightning Protection . . . .......................................................................................... 237 G Abbreviations . . . 238 H Statement of Warranty . . . ..................................................................................... 242 I Technical Services and Support. . . ....................................................................... 244 Tsunami® 8100 Series - Software Management Guide 7

Preface Preface This chapter contains information on the following: • About this Guide • Products Covered • Audience • Prerequisites • Related Documents • Documentation Conventions About this Guide This manual gives a jump-start working knowledge on the Tsunami® 8100 products. It explains the step-by-step procedure to configure, manage and monitor these products by using Web Interface. Products Covered Tabulated below are the Tsunami® products that are covered in this guide along with the latest software version supported. Product(s) Software Version Supported Tsunami® MP-8100-BSU 2.4.0 Tsunami® MP-8100-SUA 2.4.0 Tsunami® MP-8150-SUR 2.4.0 Tsunami® MP-8150-CPE 2.4.0 Tsunami® MP-8160-BSU 2.4.0 Tsunami® MP-8160-SUA 2.4.0 Tsunami® MP-8160-CPE 2.4.0 Tsunami® QB-8100-EPA 2.4.0 Tsunami® QB-8100-LNK 2.4.0 Tsunami® QB-8150-EPR 2.4.0 Tsunami® QB-8150-LNK 2.4.0 Tsunami® QB-8150-LNK-12/50 2.4.0 Audience The intended audience for this guide is the Network Administrator who installs and/or manages the device. Prerequisites The reader of this document should have working knowledge of Wireless Networks, Local Area Networking (LAN) concepts, Network Access Infrastructures and Client-Server Applications. Tsunami® 8100 Series - Software Management Guide 8

Preface Related Documents In addition to this guide, you can refer to the following documents that are available on the Proxim’s support site http://support.proxim.com. • Quick Installation Guide (QIG) - A quick reference guide that provides essential information to install and configure the device. • Hardware Installation Guide - A guide that provides an overview about the Tsunami® products, their installation methods and hardware specifications. • Reference Guide - A guide that provides instructions on how to configure, manage and monitor the device by using Command Line Interface. • Antenna Guides - A guide that gives insight on the recommended antennas and the ways to align them. • Safety and Regulatory Compliance Guide - A guide that provides country specific safety and regulatory norms to be followed while installing the devices. Documentation Conventions Screenshots This guide uses screenshots to explain the method to configure and manage the device using Web Interface. Based on your device, the screenshots may vary. Hence, we request you to refer to the screenshots that are valid for your device. Icon Representation Name Image Meaning Note A special instruction that draws attention of a user. Important A note of significant importance that a user should be aware of. Caution A warning that cautions a user of the possible danger. Device Naming Conventions Naming Convention Description BSU Refers to a Base Station Unit Subscriber / SU Mode / SU 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 : A feature specific to a device is referred to by its name else by the common naming convention as tabulated above. Tsunami® 8100 Series - Software Management Guide 9

1 Overview This chapter contains information on the following: • About Tsunami® 8100 Products • Wireless Network Topology - Point-to-Multipoint (PTMP) - Point-to-Point Link • Multiple-Input-Multiple-Output (MIMO) • Wireless Outdoor Router Protocol (WORP) 1.1 About Tsunami® 8100 Products Proxim’s Tsunami® 8100 product series, consists of point-to-point and point-to-multipoint devices that are designed to provide wireless networking solutions to enterprises and business markets. This product series consists of the following products: Product Description Image Tsunami® The Tsunami® MP-8100 Base Station unit, is a flexible wireless MP-8100-BSU outdoor product that operates in 2.3 - 2.5 and 4.9 - 6.0 GHz frequency bands. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. Tsunami® The Tsunami® MP-8100 Subscriber unit, is a flexible wireless MP-8100-SUA outdoor product that operates in 2.3 - 2.5 and 4.9 - 6.0 GHz frequency bands. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. Tsunami® The Tsunami® MP-8150 Subscriber unit comes with a 3x3 MIMO MP-8150-SUR radio operating in 4.9 - 6.0 GHz frequency band. This connectorized device comes with a 3x3 MIMO Radio and three N-Type connectors to connect external antennas. Tsunami® The Tsunami® MP-8150 Customer Premises Equipment comes with MP-8150-CPE a high power 2x2 MIMO radio and 16 dBi integrated dual-polarized panel antenna operating in 5.3 - 6.1 GHz frequency band. Tsunami® The Tsunami® MP-8160 Base Station unit, is a flexible outdoor MP-8160-BSU product that operates in 5.9 - 6.4 GHz frequency band. This connectorized device comes with a high power 2x2 MIMO radio and two N-Type connectors to connect external antennas. Tsunami® The Tsunami® MP-8160 Subscriber unit, is a flexible outdoor MP-8160-SUA product that operates in 5.9 - 6.4 GHz frequency band. This connectorized device comes with a high power 2x2 MIMO radio and two N-Type connectors to connect external antennas. Tsunami® 8100 Series - Software Management Guide 10

Overview Tsunami® The Tsunami® MP-8160 Customer Premises Equipment comes with MP-8160-CPE a single high power 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna operating in 5.9 - 6.4 GHz frequency band. Tsunami® The Tsunami® QB-8100-EPA QuickBridge operates in 2.3 - 2.5 and QB-8100-EPA 4.9 - 6.0 GHz frequency bands. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. Tsunami® A pair of Tsunami® QB-8100-EPA devices form a link. QB-8100-LNK Tsunami® The Tsunami® QB-8150-EPR QuickBridge comes with a 2x2 MIMO QB-8150-EPR radio and 23 dBi integrated dual-polarized panel antenna operating in 4.9 - 6.0 GHz Band. Tsunami® A pair of Tsunami® QB-8150-EPR devices form a link. QB-8150-LNK Tsunami® A pair of Tsunami® QB-8150-EPR-12 devices form a link. QB-8150-LNK-12 The Tsunami® QB-8150-EPR-12 device comes with a high power 2x2 MIMO radio, 12 Mbps speed and 16 dBi integrated dual-polarized panel antenna operating in 5.3 - 6.1 GHz frequency band. Tsunami® A pair of Tsunami® QB-8150-EPR-50 devices form a link. QB-8150-LNK-50 The Tsunami® QB-8150-EPR-50 device comes with a high power 2x2 MIMO radio, 50 Mbps and 16 dBi integrated dual-polarized panel antenna operating in 5.3 - 6.1 GHz frequency band. 1.2 Wireless Network Topology 1.2.1 Point-to-Multipoint (PTMP) Point-to-multipoint is a wireless network that has a central communication device such as a Base Station Unit (BSU), providing connectivity to multiple devices such as Subscribers (SUs) or clients. Any transmission of data that originates from the BSU is received by all SUs; whereas, the data originating from any of the SU is received only by the BSU. This allows numerous sites in a wide area to share resources, including a single high-speed connection to the Internet. Tsunami® 8100 Series - Software Management Guide 11

Overview Listed below are the applications, where Proxim’s Point-to-multipoint devices can be used: • Last Mile Access: Competitive broadband service access alternative to Digital Subscriber Line (DSL) or cable for residences and T1 or Ethernet for businesses. • Security and Surveillance: High definition IP-surveillance cameras for monitoring city streets, airports, bridges, seaports, transportation hubs, offices and warehouses. Tsunami® 8100 Series - Software Management Guide 12

Overview • Metropolitan Area Network: Secure and reliable connectivity between city buildings. • Enterprise Campus Connectivity: Extend the main network to remote offices, warehouses or other buildings without leased lines. Tsunami® 8100 Series - Software Management Guide 13

Overview • Offshore Communications: Establishes connectivity between seashore and the ships that are nearing the port locations, or connectivity between off-shore oil rigs and sea shore and so on. • Wireless Intelligent Transportation System (ITS): Increases the traffic efficiency and reduces the commuting time in cities and metropolitan areas. 1.2.2 Point-to-Point Link A point-to-point link is a dedicated wireless link that connects only two stations. With a point-to-point link, you can set up a connection between two locations as an alternative to: • Leased lines in building-to-building connections • Wired Ethernet backbones between wireless access points in difficult-to-wire environments. It is easy to set up a wireless point-to-point link as shown in the following figure. Each device is set up as either an End Point A or an End Point B. Tsunami® 8100 Series - Software Management Guide 14

Overview Figure 1-1 Point-to-Point-Link Listed below are the applications, where Proxim’s Point-to-Point devices can be used: • Backhaul to a Central POP: Avoids expensive installation and recurring charge of a second wireline backhaul to a remote virtual POP. Tsunami® 8100 Series - Software Management Guide 15

Overview • Repeater: Extends distance or overcomes path blockage by adding point-to-point hops • High-bandwidth Last Mile Access: Delivers Transparent LAN Services (TLS) to corporate parks. • High Availability and Link Aggregation: Achieves high availability and link aggregation in wireless medium by using two parallel links and additional Link Aggregation Control Protocol (LACP) capable switches. This is applicable only for QB-8100-EPA/LNK and QB-8150-EPR/LNK devices. Tsunami® 8100 Series - Software Management Guide 16

Overview • Leased Line Redundancy: Eliminates recurring DS-3 leased line charges with one time installation charge of a QuickBridge link. • Inter-POP Redundancy: Avoids downtimes caused by a wireline backhaul failure by adding a QuickBridge link as an inter-POP redundancy. 1.3 Multiple-Input-Multiple-Output (MIMO) Proxim’s 81xx Point-to-point and Point-to-multipoint devices support Multiple-Input-Multiple-Output (MIMO) antenna technology that uses multiple antennas at both the transmitter and receiver to improve communication performance. The underlying technology of Proxim’s product radio(s) are based on a combination of MIMO and OFDM (Orthogonal Frequency Division Multiplexing). MIMO-OFDM combination radios solve interference, fading and multipath problems On the receiver side, having multiple receivers increases the amount of received power and also reduces multipath problems by combining the received signals for each frequency component separately. Hence, MIMO significantly improves the overall gain. MIMO also uses Spatial multiplexing transmission technique to transmit independent and separately encoded data signals from each of the multiple transmit antennas while reusing or multiplexing in the space dimension. These independent data signals are called Spatial streams. The transmitting antenna uses multiple radio Tx chains and signal paths to simultaneously transmit different data streams, whereas the receiver combines the Rx signals resulting in higher throughput. By increasing the number of receiving and transmitting antennas, the throughput of the channel increases linearly resulting in high spectral efficiency. 1.4 Wireless Outdoor Router Protocol (WORP) WORP is a protocol, designed by Proxim to optimize the performance of multi-play outdoor wireless Point-to-Point (PtP) and Point-to-Multipoint (PTMP) links using packet radio technology, including the use of cutting edge Multiple-Input-Multiple-Output (MIMO) technology. WORP overcomes the performance degradation, which standards-based wireless technologies are susceptible to when used for outdoor long-range connectivity. Benefits: • More Net Bandwidth: WORP increases the overall net bandwidth of the multipoint system. The net bandwidth using WORP is higher than any other protocol solution used in an outdoor environment. WORP is a more efficient protocol that protects the system from packet collisions and transmits the data in an optimal way, which increases the overall performance. • More Concurrent Subscribers: An outdoor point-to-multipoint solution based on 802.11 may connect from 5 to 10 remote nodes, but sometimes performance starts to suffer from collisions with as little as only 2 remote nodes. A solution using WORP, on the other hand, can connect up to 100 remote nodes without adverse effects on usable bandwidth, allowing more concurrent Subscriber Units (SU) to be active in a wireless multipoint environment. • Smart Scheduling: WORP uses smart scheduling for remote node polling to avoid wasting bandwidth on nodes that have no traffic to be sent. The Base Station Unit (BSU) dynamically decides how frequently a remote node should be polled based on the current traffic to and from each remote node and the priority settings for that traffic. The scheduling is adapted dynamically to the actual traffic and further optimized by following the bandwidth limits as configured for each remote node. • Dynamic Data Rate Selection (DDRS): DDRS enables WORP to dynamically adjust the data rate at which the wireless traffic is sent. This feature is especially important in point-to-multipoint networks, when different SUs can sustain different data rates because of the different distances from the BSU. With DDRS, WORP dynamically optimizes the wireless data rate to each of the SUs independently, keeping the overall net throughput at the highest possible level. This feature optimizes throughput even for links with different RF conditions on the BSU and SU, by optimizing downlink Tsunami® 8100 Series - Software Management Guide 17

Overview • Quality of Service: WORP ensures that the most important data arrives with priority by differentiating between priorities of traffic as defined in the profiles for QoS (Quality of Service), similar to the 802.16 WiMAX QoS standard definition. • Bandwidth Control: WORP allows service providers to control network bandwidth, protecting the network from excessive bandwidth use by any one station. Additionally, it allows service providers to differentiate their service offerings. • Asymmetric Bandwidth Controls: Asymmetric bandwidth gives network managers the ability to set different maximum bandwidth rates for a variety of customer groups. This allows service providers to further differentiate their service offerings and maximize revenues. Tsunami® 8100 Series - Software Management Guide 18

2 Management and Monitoring Capabilities A Network administrator can use the following interfaces to configure, manage and monitor the devices. • Web Interface • Command Line Interface • Simple Network Management Protocol (SNMP) • ProximVision ES (PVES) 2.1 Web (HTTP/HTTPS) Interface The Web interface (HTTP) provides easy access to configuration settings and network statistics from any computer on the network. You can access the Web interface, through LAN (switch, hub and so on), the Internet, or with an Ethernet cable connected directly to your computer’s Ethernet port. HTTPS interface provides an HTTP connection over a Secure Socket Layer (SSL). HTTPS allows the user to access the device in a secure fashion using SSL over port 443. The device supports SSLv3 with a 128-bit encryption certificate maintained by the device for secure communication between the device and the HTTP client. All communications are encrypted using the server and the client-side certificate. 2.2 Command Line Interface The Command Line Interface (CLI) is a text-based configuration utility that supports a set of keyboard commands and parameters to configure, manage and monitor the device. You can enter the command statements composed of CLI commands and their associated parameters. Commands can be issued from the keyboard for real-time control, or from scripts that automate configuration. For example, when downloading a file, an administrator enters the download CLI Command along with the IP Address, file name, and file type parameters. 2.2.1 HyperTerminal You can access the CLI over a HyperTerminal serial connection. HyperTerminal is a program that connects to other Computers, Telnet Sites, Bulletin Board Systems (BBS), Online Services, and Host Computers, by using either modem or a null modem cable. If you are using RS-232 cable, verify the following information in the HyperTerminal serial port setup: Port COM1 (default) Baud Rate 115200 Data 8-bit Parity None Stop 1-bit Flow Content None : If you are using Windows 7 then use Terminal Emulator program like Teraterm Pro for serial connection. Tsunami® 8100 Series - Software Management Guide 19

Management and Monitoring Capabilities 2.2.2 Telnet You can access the device through CLI by using Telnet. With Telnet, you can communicate with the device through LAN (switch, hub and so on), the Internet, or with an Ethernet cable connected directly to your computer’s Ethernet port. 2.2.3 Secure Shell (SSH) You can securely access the device through CLI by using Secure Shell (SSH). The device supports SSH version 2, for secure remote CLI (Telnet) sessions. SSH provides strong authentication and encryption of session data. The SSH server has host keys - a pair of asymmetric keys (a private key that resides on the device) and a public key that is distributed to clients that need to connect to the device. Clients need to verify that it is communicating with the correct SSH server. 2.3 SNMP Management You can also configure, manage and monitor the device by using the Simple Network Management Protocol (SNMP). This requires an SNMP Manager Program (sometimes called MIB browser) or a Network Manager program using SNMP. The device supports the following Management Information Base (MIB) files that describe the parameters that can be viewed and/or configured over SNMP: • PXM-SNMP.mib (Enterprise MIB) • RFC-1213.mib (MIB-II) • RFC-1215.mib (Trap MIB) • RFC-1757-RMON.mib (Remote Monitoring) • RFC-2571.mib (SNMP Framework) • RFC-3411-SNMP-FRAME-WORK.mib (SNMP Framework) • RFC-2790.mib (Host Resources) • RFC-3291-INET-ADDRESS-MIB.mib • RFC-3412.mib (SNMP-MPD-MIB) • RFC-3414.mib (SNMP-USER-BASED-SM-MIB) • SFLOW.mib The PXM MIB files are available on the Proxim support site (http://support.proxim.com). You must compile one or more of these MIB files into your SNMP program’s database before you manage your device using SNMP. The enterprise MIB (PXM-SNMP.mib) defines the Read and Read/Write objects that can be viewed or configured using SNMP. These objects correspond to most of the settings and statistics that are available with other management interfaces. The MIB can be opened with any text editor, such as Microsoft Word, Notepad, or WordPad. 2.4 ProximVision ES ProximVision ES (commonly known as PVES) is Proxim’s Network Management System that helps to manage and administer your wireless network effectively and efficiently. ProximVision ES combines industry-leading functionality with an intuitive user interface, enabling Network Administrators and Help Desk staff to support and control a wireless network. ProximVision ES offers you a single intelligent console from which you can manage, monitor, analyze and even configure your device. For more information, see ProximVision ES user guide available at the Proxim’s support site at http://support.proxim.com. : This user guide explains the method to initialize and manage the device using Web Interface only. The Reference Manual, a guide that explains the method to manage the device using Command Line Interface, can be found at Proxim’s support site (http://support.proxim.com). Tsunami® 8100 Series - Software Management Guide 20

3 Device Initialization This chapter contains information on the following: • Initialization — ScanTool — Initialize Device using ScanTool — Modifying the IP Address of the Device using ScanTool • Logging onto the Web Interface — Home Page — COMMIT — REBOOT • Factory Default Configuration 3.1 Initialization Once the device installation completes, you can access the device either through Command Line Interface, Web Interface or an SNMP Interface. : For installation procedure, please refer to the Hardware Installation guide available at Proxim’s support site (http://support.proxim.com). • To access the device using CLI commands, connect a serial RS-232 cable to the Serial port of the device. • To access the device using Web or SNMP interface, connect an Ethernet cable to the Ethernet port of the device. For all the modes of connection, you will need to configure the IP address of the device. As each network is different, a suitable IP address on the network must be assigned to the device. This IP address helps you to configure, manage and monitor the device through the Web Interface, SNMP, or Telnet/CLI. The device can have either a static or dynamic IP address. When set to static, the user has to set the IP address manually; and if set to dynamic, the IP address is obtained dynamically from the Dynamic Host Configuration Protocol (DHCP) server. By default, the device IP Address is set to 169.254.128.132. : Tsunami® MP-8160-CPE device does not have a Serial Port. However, the user has the flexibility to configure, manage and monitor the device through command mode via Telnet. 3.1.1 ScanTool Proxim’s ScanTool (Answer ID - 1735) is a software utility that runs on Microsoft Windows machine. By using ScanTool, you can • Scan devices (Proxim devices only) available on the network • Obtain device’s IP address • Modify device’s IP Configuration parameters (IP Address, Address Type, Gateway and so on) • Launch the Web interface • Switch between the network adapters, if there are multiple network adapters in the Personal Computer Tsunami® 8100 Series - Software Management Guide 21

Device Initialization : ScanTool works only for Proxim devices. Also note that you may need to disable Windows Firewall (or add an exception) for ScanTool to function or to detect the radio. 3.1.2 Initialize Device using ScanTool To scan and locate the devices on a network by using ScanTool, do the following: 1. Power on, or reset the device. 2. To download Proxim’s ScanTool, log on to Proxim’s support site at http://support.proxim.com and search for ScanTool with (Answer ID 1735). Upon successful download, start ScanTool by double-clicking the downloaded icon. 3. If your computer has more than one network adapter installed, you will be prompted to select the adapter for scanning Proxim devices. You can use either an Ethernet or a Wireless Adapter. Select an adapter and click OK. The following ScanList screen appears, which displays all devices that are connected to selected adapter. Figure 3-1 ScanList - An Example This screen contains the following device information: • MAC Address • System Name • IP Address • Uptime • System Description: The system description comprises the following information: — Device Description: For example, Tsunami MP-8100-BSU-WD — Firmware Version: For example, v2.4.0 — Serial Number : For example, SN-11PI15010031 — Bootloader Version: For example, BL - V1.3.1 4. Click Select Adapter, to change adapter settings. 5. Identify and select the MAC address of the device you want to initialize from the list and click Web Config to log on to the Web Interface. : If your device does not appear in the Scan List, click Rescan in the Scan List screen. If the device still does not appear in the list, see Troubleshooting for suggestions. Note that after rebooting the device, it may take up to five minutes for the device to appear in the Scan List. Tsunami® 8100 Series - Software Management Guide 22

Device Initialization 3.1.3 Modifying the IP Address of the Device using ScanTool To modify the IP address of a device using ScanTool, select the device from the scan list and click Change. A Change screen appears as shown in the following figure. The system automatically populates the MAC Address, System Name, TFTP Server IP Address and Image File Name of the device, which are read-only. Figure 3-2 Modifying Device’s IP Address 1. Select the IP Address Type as either static or dynamic. • Static: When set to static, the IP address of the device is changed manually. • Dynamic: When set to dynamic, the IP address is dynamically generated by the DHCP server. 2. Type the appropriate IP Address, Subnet Mask, and the Gateway IP Address parameters. 3. Enter the SNMP Read/Write password in the Read/Write Password box. By default, it is public. 4. Click OK to save the details. The device automatically reboots. To log on to the Web Interface, click Web Configuration. The user is then prompted to enter its username and password. For more information on how to login, please see Logging onto the Web Interface. 3.2 Logging onto the Web Interface Once the device is connected to your network, use a web browser to configure, manage and monitor the device. Enter the default IP address of the device (For example, http://169.254.128.132) in the address bar or access the Web Interface using ScanTool (see Initialization). You are now prompted to enter your username and password. Tsunami® 8100 Series - Software Management Guide 23

Device Initialization Figure 3-3 Login Screen Based on the access credentials, two types of users can access the device. They are, 1. Administrator User: The Administrator user administers the entire device. This user type has the write access to all the features of the device and also has the privilege to change his or her own password and that of the Monitor user (the other user type). To change the password, refer to Services. 2. Monitor User - The Monitor user has only view access to all the features of the device. This user is restricted from the following privileges: • Change the device functionality • Change his or her own password • Run any of the test tools like Link Test, Wireless Site Survey and so on. However, the user can view the logs and statistics of the test tools. The Monitor user is given the privilege to retrieve event logs and temperature logs for debugging. To logon to the device, 1. Type a valid user name in the User Name box. The user name is admin for the Administrator user and monitor for the Monitor user. 2. Type the password in the Password box. By default, the password is public for both the Administrator user and the Monitor user. : • By default the password is public. For security reasons, it is recommended to change the password after your first logon to the device. • Depending on the settings made during the device initialization, the IP address may be either a dynamic IP address assigned by a network DHCP server or a static IP address which is manually configured. Refer to ScanTool for information on how to determine the device’s IP address and manually configure a new IP address. • If the connection is slow or unable to connect, use the Internet Explorer Tools option to ensure that you are not using a proxy server for the connection. • If you are unable to log on to the configuration pages by using default user name and password, please check with the administrator or follow Forced Reload procedures. • If using Internet Explorer, and you enter wrong password consecutively for three times, the HTTP session will get disconnected. If case of other browsers, the login screen will reset until you enter correct password. • In the Internet Explorer, to get best results, click on Tools > Internet Options > General. Click Settings in the Browsing History and select “Every visit to the webpage”. Tsunami® 8100 Series - Software Management Guide 24

Device Initialization 3.2.1 Home Page Upon successful logon, the device home page appears. Figure 3-4 Home Page The home page contains the following information: • Device Description: The device description is displayed on the top-right corner of the home page. It displays the logged in user type and the device name along with the latest firmware version. • System Summary: The System Summary screen displays the summary of system information such as System Name, IP Address, Radio Mode, Interface Status, Event Log and so on. • COMMIT Button: See COMMIT • REBOOT Button: See REBOOT • Home: Display System Summary screen. • BASIC CONFIGURATION: The BASIC CONFIGURATION tab allows the user to configure the minimum set of parameters required for a device to be operational and establish link in the network. For more details, see Basic Configuration. • ADVANCED CONFIGURATION: The ADVANCED CONFIGURATION tab allows the user to configure the advanced parameters of the device. For more details, see Advanced Configuration. • MANAGEMENT Tab: The MANAGEMENT tab allows the user to manage the device. For more details, see Management. • MONITOR Tab: The MONITOR tab allows the user to monitor the device. For more details, see Monitor. Tsunami® 8100 Series - Software Management Guide 25

Device Initialization 3.2.2 COMMIT COMMIT operation is used to apply the configuration changes onto the device. When changes are made to the configuration parameters of the device, the changes will not take effect, until COMMIT is clicked. Some parameters may require system reboot for the changes to take effect. On clicking COMMIT, the system evaluates all the configuration dependencies and displays the configuration status. Before applying commit, the system displays a confirmation message, as shown in the following figure: Figure 3-5 Commit Click OK, if you wish to commit the changed parameters. On successful COMMIT operation, the following screen appears: Figure 3-6 Commit Status If the configured parameters requires reboot, on committing the following screen appears. Figure 3-7 Commit Status with Reboot Message Tsunami® 8100 Series - Software Management Guide 26

4 Basic Configuration The BASIC CONFIGURATION tab provides a one-place access to a minimum set of configuration parameters to quickly set up a Point-to-point or Point-to-multipoint network. To configure basic parameters of the device, click BASIC CONFIGURATION tab. The following screen appears: Figure 4-1 Basic Configuration (BSU) Tsunami® 8100 Series - Software Management Guide 29

Basic Configuration Figure 4-2 Basic Configuration (SU) Tsunami® 8100 Series - Software Management Guide 30

Basic Configuration Figure 4-3 Basic Configuration (End Point B) Tabulated below is the table which explains Basic parameters and the method to configure the configurable parameter(s): Parameter Description System Name Represents the system name of the device. By default, the system name is System-Name. You can change the system name to the desired one. Please note that the length of the name is limited to 64 characters. Tsunami® 8100 Series - Software Management Guide 31

Basic Configuration Parameter Description Frequency Domain This parameter specifies the country of operation, permitted frequency bands and regulatory rules for that particular country or domain. When you choose a frequency domain, the Dynamic Frequency Selection (DFS) and Automatic Transmit Power Control (ATPC) features are enabled automatically if the selected country and band has a regulatory domain that requires it. The Frequency domain selection pre-selects and displays only the allowed frequencies for the selected country or domain. : • Devices sold only in United States are pre-configured to scan and display only the outdoor frequencies permitted by the Federal Communications Commission (FCC). No other countries, channels, or frequencies can be configured. Devices sold outside United States support the selection of a country by the professional installer. Any change in the Frequency Domain, requires device reboot. • If World 5 GHz is selected from the Frequency Domain drop-down menu, channels only in the 5 GHz range are displayed for manual selection. For a non US device, the default Frequency Domain selected is World 5GHz. For more details on frequency domains, refer to Frequency Domains and Channels. Radio Mode Represents the radio mode of the device. Based on the SKU, the radio mode is set to either BSU, SU, End Point A or End Point B. In case of a BSU device, you can toggle between BSU and SU modes. Similarly in case of End Point A device, you can toggle between End Point A and End Point B. But note that a change in radio mode will reset wireless and WORP parameters of the device after reboot. Channel Bandwidth Represents the width of the frequency band that is used to transmit data on the wireless interface. By default, it is set to 20 MHz. 40 MHz can be selected for higher throughputs depending on the distance and signal quality. 5 and 10 MHz can be selected for greater flexibility in spectrum selection. Auto Channel Enables a device to select the best channel for data transmission on the wireless medium, Selection (ACS) with less interference. By default, ACS is disabled on a BSU/End Point A and enabled on a SU/End Point B device. When ACS is enabled on a BSU/End Point A, it scans all the channels and selects the best channel during the start up. If ACS is enabled on the SU/End Point B, it continuously scans all the channels till it connects to a BSU or End Point A respectively. : Irrespective of the ACS status, the BSU/Endpoint A will automatically select a new channel upon radar detection. Preferred Channel Applicable only when the Auto Channel Selection (ACS) is disabled. This parameter enables you to select a specific channel (in the specified frequency domain) for the device to operate. Active Channel Displays the current active channel on which wireless interface is operating. When the Auto Channel Selection parameter is enabled or when the device moves to a different channel because of radar detection, this parameter enables you to view the current operating channel. Tsunami® 8100 Series - Software Management Guide 32

Basic Configuration Parameter Description DDRS Status Applicable only when Dynamic Data Rate Selection (DDRS) is enabled on the device. It indicates that DDRS is enabled on the device. See DDRS. Tx Rate Applicable only when Dynamic Data Rate Selection (DDRS) is disabled on the device. This parameter represents the data transmission rate of the device. You can configure the appropriate data rate based on the signal level. : A change in Channel Bandwidth will reset the Tx Rate to default value. Network Name Network name to identify a wireless network. The network name can be of minimum 2 or maximum 32 characters. The default network name is MY_NETWORK. : For a BSU and SU to establish a wireless link, both should in the same network. The same applies to End Point A and End Point B as well. Legacy Mode Applicable only to Tsunami® MP-8100-BSU device. When enabled, allows the device to operate with the legacy products of the Tsunami® MP.11 family such as: MP.11 5054 series, 5012 series, 2454 series and so on. By default, this parameter is disabled. BSU / End Point A Applicable only to a SU/End Point B device. Name Represents the BSU/End Point A name to which SU/End Point B is connected. IP Configuration, and See Network. Default Gateway IP Address After configuring the required parameters, click OK and then COMMIT. : Reboot the device, if you have configured any of the parameters with an asterisk symbol marked against them. Tsunami® 8100 Series - Software Management Guide 33

5 Advanced Configuration The ADVANCED CONFIGURATION tab provides a means to configure the following advanced features of the device: • System • Network • Ethernet • Wireless • Security • Quality of Service (QoS) • RADIUS Based SU QoS Configuration • VLAN (Bridge Mode Only) • RADIUS Based SU VLAN Configuration • Filtering (Bridge Only) • DHCP • IGMP Snooping • Routing Mode Features 5.1 System The System tab enables you to configure system specific information. To configure system specific parameters, navigate to ADVANCED CONFIGURATION > System. The System screen appears: Figure 5-1 System Configuration Tabulated below is the table which explains System parameters and the method to configure the configurable parameter(s): Parameter Description Radio Mode Represents the radio mode of the device. Based on the device, the radio mode is set to either BSU, SU, End Point A or End Point B. In case of a BSU device, you can toggle between BSU and SU modes. Similarly in case of End Point A or End Point B device, you can toggle between End Point A and End Point B. But note that a change in radio mode will reset wireless and WORP parameters of the device after reboot. Tsunami® 8100 Series - Software Management Guide 34

Advanced Configuration Parameter Description Frequency Domain A valid frequency domain must be set before the device can be configured with any other parameters. Selecting a frequency domain makes the device compliant with the allowed frequency bands and channels for that regulatory domain. See Frequency Domain. Network Mode The device can be configured in two network modes: Bridge and Routing. By default, the network mode is Bridge mode. Active Network Mode A change in the network mode (either Bridge or Routing mode) is applied on the device only when the device is rebooted. So, when the network mode is changed and the device is not rebooted, this parameter displays the current operating network mode of the device. Maximum MTU Largest size of the data packet that can be sent to/from the Ethernet interface of the (Maximum device. By default, the MTU size is 1500 bytes. It can be configured with any value ranging Transmission Unit) from 1500 to 2048 bytes. The MTU size excludes Ethernet Header(14 bytes) + Frame Check Sequence (4 bytes) + VLAN Tag(4 bytes). : • Not all devices support this parameter. • MTU is configurable only in Tsunami® MP-8150-CPE, Tsunami® MP-8160-CPE and Tsunami® QB-8150-EPR-12/50 devices. • For optimal performance, MTU should be configured same on both local and remote devices. • By default, Maximum MTU for Tsunami® MP-8100-BSU, Tsunami® MP-8100-SUA, MP-8150-SUR, Tsunami® MP-8160-BSU, Tsunami® MP-8160-SUA, Tsunami® QB-8100-EPA, Tsunami® QB-8150-EPR is not configurable and set to 1500 excluding Ethernet Header(14 bytes) + Frame Check Sequence (4 bytes) + VLAN Tag(4 bytes). Frequency Filter Lower These parameters enable you to define the lower and upper frequency band edges, which Edge, and helps to limit the available frequency band, for a given frequency domain, to a smaller Frequency Filter Upper band. By limiting the frequency band, the time taken by a device to scan and connect to Edge any other device in the network is reduced. You can enter frequencies ranging from 0 to 10000 MHz. By default the lower frequency is set to 0 MHz and higher frequency is set to 10000 MHz. After configuring the required parameters, click OK, COMMIT and then REBOOT. 5.2 Network The Network tab allows you to view and configure the network specific information of the device. To view the current operating network mode of the device, navigate to ADVANCED CONFIGURATION > Network. If the network mode of the device is configured in Bridge mode, then following screen appears: Tsunami® 8100 Series - Software Management Guide 35

Advanced Configuration Figure 5-2 Bridge Mode If the network mode of the device is configured in Routing mode, then the following screen appears: Figure 5-3 Routing Mode 5.2.1 IP Configuration (Bridge Mode) To configure the IP parameters of the device when operating in Bridge mode, navigate to ADVANCED CONFIGURATION > Network > IP Configuration. The following IP Configuration screen appears: Figure 5-4 IP Configuration (Bridge Mode) Tabulated below is the table which explains the method to configure IP parameters in Bridge mode: Parameter Description Ethernet Please note that the number of Ethernet interfaces depend on your device. Tsunami® 8100 Series - Software Management Guide 36

Advanced Configuration Parameter Description Address Type Specifies whether the Ethernet interface parameters are to be configured through Dynamic Host Configuration Protocol (DHCP) or to be assigned statically. By default, the address type is set to Static meaning which the user can manually configure the network parameters. Select Dynamic to configure the device as a DHCP client. If Dynamic is selected, the device obtains the IP parameters from a network DHCP server automatically during the bootup. If you do not have a DHCP server or if you want to manually configure the device’s IP settings, select Static. : DHCP Client (IP Address Type Dynamic) is applicable in Bridge Mode, and is applicable on wireless interface in Routing mode only when PPPoE is enabled . IP Address Represents the IP address of the Ethernet interface. When the address type is set to Static (default address type), the static IP address by default is set to 169.254.128.132. When set to static, you can manually change the IP address. When the address type is set to Dynamic, this parameter is read-only and displays the device IP address obtained from the DHCP server. The device will fallback to 169.254.128.132, if it cannot obtain the IP address from the DHCP server. Subnet Mask Represents the subnet mask of the Ethernet interface. When the address type is set to Static (default address type), the subnet mask by default is set to 255.255.255.0. When set to static, you can manually change the subnet mask. When the address type is set to Dynamic, this parameter is read-only and displays the device current subnet mask obtained from the DHCP server. The subnet mask will fallback to 255.255.255.0, if the device cannot obtain the subnet mask from the DHCP server. Default Gateway IP Address IP Address Represents the gateway IP address of the device. When the address type is set to Static (default address type), the gateway IP address by default is set to 169.254.128.132. When set to static, you can manually change the gateway IP address. When the address type is set to Dynamic, this parameter is read-only and displays the device’s current gateway IP address that is obtained from the DHCP server. The gateway IP address will fallback to 169.254.128.132, if it cannot obtain the gateway IP address from a DHCP server. DNS Primary IP Address Represents the IP address of the Primary DNS Server. When the address type is set to Dynamic, this parameter is read-only and displays the DNS Primary IP Address obtained from the DHCP server. If the address type is set to Static, then you will have to manually enter the primary IP Address. Tsunami® 8100 Series - Software Management Guide 37

Advanced Configuration Parameter Description Secondary IP Address Represents the IP address of the Secondary DNS Server. When the address type is set to Dynamic, this parameter is read-only and displays the DNS Secondary IP Address obtained from the DHCP server. If the address type is set to Static then you will have to manually enter the secondary IP Address. After configuring the required parameters, click OK, COMMIT and then REBOOT. 5.2.2 IP Configuration (Routing Mode) To configure the IP parameters of the device when operating in Routing mode, navigate to ADVANCED CONFIGURATION > Network. The IP Configuration screen appears: Figure 5-5 IP Configuration (Routing Mode) Tabulated below is the table which explains the method to configure IP parameters in Routing mode: Parameter Description Ethernet Please note that the number of Ethernet interfaces depend on your device. Tsunami® 8100 Series - Software Management Guide 38

Advanced Configuration Parameter Description IP Address Represents the IP address of the Ethernet interface. By default, the static IP address for Ethernet1 is set to 169.254.128.132 and for Ethernet2 it is set to 169.254.129.132. You can manually change the IP address. Subnet Mask Represents the subnet mask of the Ethernet interface. By default, the static subnet mask is set to 255.255.255.0. You can manually change the subnet mask. Wireless IP Address Represents the IP address of the wireless interface. By default, the static IP address is set to 169.254.130.132. You can manually change the IP address. Subnet Mask Represents the subnet mask of the wireless interface. By default, the static subnet mask is set to 255.255.255.0. You can manually change the subnet mask. Default Gateway IP Address IP Address Represents the gateway IP address of the device. By default, the Gateway IP address is set to 169.254.128.132. You can manually change the gateway IP address. DNS Primary IP Address Represents the IP Address of the Primary DNS Server. Secondary IP Address Represents the IP Address of the Secondary DNS Server. After configuring the required parameters, click OK, COMMIT and then REBOOT. : • To obtain dynamic IP address of the SU over WORP, • Scenario 1: When BSU and SU are in Bridge Mode with DHCP Client enabled in SU, and if DHCP server is behind BSU, SU will get the IP Address over WORP. • Scenario 2: When BSU is in Routing Mode and SU is in Bridge mode and DHCP server is in a different network than SU, then we need to configure DHCP relay in BSU to get the IP for SU over WORP. • Scenario 3: When BSU is in Routing mode and SU in Bridge mode with DHCP server running on wireless interface of BSU, then SU will get the IP address from BSU. Tsunami® 8100 Series - Software Management Guide 39

Advanced Configuration 5.2.3 IP Configuration (Routing Mode with PPPoE Client Enabled) : IP Configuration in Routing mode with PPPoE client enabled is applicable only in SU mode. See PPPoE End Point (SU Only) To configure the IP parameters of the device when configured in Routing mode with PPPoE client enabled, navigate to ADVANCED CONFIGURATION > Network. The IP Configuration screen appears: Figure 5-6 IP Configuration (Routing Mode with PPPoE Client Enabled) Tabulated below is the table which explains the method to configure IP parameters in Routing mode with PPPoE client enabled: Parameter Description Ethernet Please note that the number of Ethernet interfaces depend on your device. IP Address Represents the IP address of the Ethernet interface. By default, the static IP address for Ethernet1 is set to 169.254.128.132 and 169.254.129.132 for Ethernet2. You can manually change the IP address. Subnet Mask Represents the subnet mask of the Ethernet interface. By default, the static subnet mask is set to 255.255.255.0. You can manually change the subnet mask. Tsunami® 8100 Series - Software Management Guide 40

Advanced Configuration Parameter Description Wireless (PPPoE) Address Type This parameter specifies whether the wireless interface parameters are to be configured through PPPoE server or to be assigned statically. By default, the address type is set to PPPoE-ipcp meaning which the PPPoE client obtains the IP parameters from a network PPPoE server automatically during the bootup. To manually configure the PPPoE Client’s IP settings, select Static. IP Address Represents the IP address of the wireless interface. When the address type is set to PPPoE-ipcp, this parameter is read-only and displays the PPPoE client’s IP address obtained from the PPPoE server. The client will fallback to 169.254.130.132, if it cannot obtain the IP address from the PPPoE server. When the address type is set to Static, the IP address by default is set to 169.254.130.132. You can manually change the IP address. Subnet Mask Represents the subnet mask of the wireless interface. When the address type is set to PPPoE-ipcp, this parameter is read-only and is set to Host Mask as it is a point-to-point interface. The client will fallback to 255.255.255.0, if it cannot obtain the IP address from the PPPoE server. When the address type is set to Static, the subnet mask by default is set to 255.255.255.0. You can manually change the subnet mask. Default Gateway IP Address IP Address Represents the gateway IP address of the device. When the address type is set to PPPoE-ipcp, this parameter is read-only and displays the PPPoE client’s gateway IP address (which is nothing but the IP address of the PPPoE server). If it cannot obtain the IP address from a PPPoE server, then there will be no gateway for the device. When the address type is set to Static, the gateway IP address by default is set to 169.254.128.132. You can manually change the gateway IP address. DNS Primary IP Address Represents the IP Address of the Primary DNS Server. Secondary IP Address Represents the IP Address of the Secondary DNS Server. After configuring the required parameters, click OK, COMMIT and then REBOOT. Tsunami® 8100 Series - Software Management Guide 41

Advanced Configuration 5.3 Ethernet The Ethernet tab allows you to view and configure the Ethernet interface properties of the device. 5.3.1 Basic Ethernet Configuration To view and perform basic Ethernet configuration, navigate to ADVANCED CONFIGURATION > Ethernet. The Ethernet Interface Properties screen appears: Figure 5-7 Basic Ethernet Configuration Tabulated below is the table which explains Basic Ethernet parameters and the method to configure the configurable parameter(s): Parameter Description MAC Address Displays the MAC address of the Ethernet interface. Operational Speed Displays the current operational speed of the Ethernet interface. Tabulated below is the maximum operational speed of the Ethernet interface product wise: Product Maximum Speed • Tsunami® MP-8100-BSU 1 Gbps • Tsunami® MP-8100-SUA • Tsunami® MP-8150-SUR • Tsunami® MP-8160-BSU • Tsunami® MP-8160-SUA • Tsunami® QB-8100-EPA • Tsunami® QB-8100-LNK • Tsunami® QB-8150-EPR • Tsunami® QB-8150-LNK • Tsunami® MP-8150-CPE 100 Mbps • Tsunami® MP-8160-CPE • Tsunami® QB-8150-EPR-12/50 Tsunami® 8100 Series - Software Management Guide 42

Advanced Configuration Parameter Description Operational Tx Mode Displays the current operational transmission mode of the Ethernet interface. It supports two types of transmission modes: • Half Duplex: Allows one-way data transmission at a time. • Full Duplex: Allows two-way transmission simultaneously. Speed And TxMode Enables the user to select the speed and transmission mode of the Ethernet interface. By default, it is set to Auto. When set to Auto (recommended to set), both the transmitter and the receiver negotiate and derive at the best transmission mode. : Please ensure the same transmission modes are configured on the transmitter and the receiver device. Admin Status This parameter is applicable only when the device support more than one Ethernet interface. By default, both the Ethernet interfaces of the device are enabled. The first Ethernet interface is always enabled; whereas the second Ethernet interface can be either enabled or disabled as desired. After configuring the required parameters, click OK and then COMMIT. Reboot the device, if you have changed the Admin Status configuration. 5.3.2 Advanced Configuration The Advanced Configuration feature enables you to achieve high availability and link aggregation in wireless medium by using two parallel links and additional Link Aggregation Control Protocol (LACP) capable switches. : Applicable only to Tsunami® QB-8100-EPA, Tsunami® QB-8100-LNK, Tsunami® QB-8150-EPR, and Tsunami® QB-8150-LNK. To view and perform advanced Ethernet configuration, click Advanced in the Ethernet Interface Properties screen. The following screen appears: Figure 5-8 Advanced Ethernet Configuration Tsunami® 8100 Series - Software Management Guide 43

Advanced Configuration Tabulated below is the table which explains Advanced Ethernet parameters and the method to configure the configurable parameter(s): Parameter Description Auto Shutdown This parameter facilitates LACP capable Ethernet switches to use two Quick Bridge links to achieve higher throughput and redundancy. By default, it is Disabled. If Auto Shutdown is enabled on the Ethernet Interface, then the Ethernet port will be automatically disabled, when the wireless link goes down. It will be automatically enabled once the wireless link is up again. : This feature works only if STP/LACP Frames is set to passthru (See ADVANCED CONFIGURATION > Filtering) Tsunami® Quick Bridge devices that are part of LACP link cannot be managed through the switches, so it is recommended to use the second ethernet port for management. After configuring the required parameters, click OK and then COMMIT. 5.4 Wireless The Wireless tab allows you to configure the wireless properties for the radio interface of the device. 5.4.1 Wireless Outdoor Router Protocol (WORP) WORP is protocol, designed by Proxim that protects the network from packet collisions and solves the hidden node problem to transmit the data in an optimal way. To configure the WORP properties, navigate to ADVANCED CONFIGURATION > Wireless > Interface1 > WORP. The WORP Configuration screen appears: Tsunami® 8100 Series - Software Management Guide 44

Advanced Configuration Figure 5-9 WORP Configuration Tabulated below is the table which explains WORP parameters and the method to configure the configurable parameter(s): Parameter Description Mode Represents the device type (BSU, SU, End Point A or End Point B) BSU Name Applicable only to SU. It specifies the name of the BSU to which a SU can establish wireless connection. If this parameter is left blank, SU can establish a link with any BSU. End Point A Name Applicable only in End Point B mode. It specifies the name of the End Point A to which End Point B can establish wireless connection. If this parameter is left blank, End Point B can establish a link with any End Point A. Network Name It is a unique name given to a logical network. Devices only within this logical network can establish wireless connection. The Network Name can be of 2 to 32 characters in length. By default it is MY_NETWORK. Tsunami® 8100 Series - Software Management Guide 45

Advanced Configuration Parameter Description Max SUs Represents the maximum number of SUs that can register with a BSU. The maximum SUs are limited to the licensed number of SUs. : Applicable only in BSU mode. WORP MTU WORP MTU (Maximum Transmission Unit) is the largest size of the data payload in wireless frame that can be transmitted. 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. Super Framing Super Framing refers to the mechanism that enables multiple Ethernet/802.3 frames to be packed in a single WORP data frame. When the WORP MTU size is configured larger than the Ethernet frame size, then WORP constructs a super frame with size of the WORP MTU configured and pack multiple Ethernet frames. It results in reducing the number of frames transmitted over wireless medium thereby conserving wireless medium and increasing the overall throughput. By default it is Enabled. Sleep Mode A BSU can put SUs in sleep mode when there is no data transmission during the past 15 seconds. This reduces the traffic congestion in the wireless medium and preserves the wireless bandwidth for other SUs in the network. BSU polls sleeping SUs once in every 4 seconds to maintain the wireless connection. By default, it is Disabled. : Applicable only in BSU mode. Multi Frame Bursting To achieve higher throughput, WORP protocol allows the transmitter or receiver to send multiple data frames in sequence without waiting for acknowledgment for every data frame and treats it as a single burst. During the burst transmission, the receiver is not allowed to interrupt the transmitter. After compilation of the burst, the receiver response by sending the acknowledgement. By default, the Multi Frame Bursting feature is Enabled on the device. When Multi Frame Bursting is enabled, the maximum data frames that can be transmitted for each burst can be configured as part of Quality of Service (QoS). : Though Multi Frame Bursting configuration is not applicable from SU/End Point B, the SU/End Point B does Multi Frame Bursting under the control of BSU/End Point A respectively. Tsunami® 8100 Series - Software Management Guide 46

Advanced Configuration Parameter Description Auto Multi Frame Auto Multi Frame Bursting feature takes effect only when Multi Frame Bursting feature is Bursting Enabled. When this feature is enabled, the device monitors all active QoS Service Flow Classes and determines the highest priority QoS Service Flow Class for every wireless connection. The device enables the burst transmission for the active highest priority QoS Service Flow Class and disables the burst transmission for other active lower priority QoS Service Flow Classes. By default, Auto Multi Frame Bursting is Enabled on the device. : • When using Software Version 2.4.0, it is recommended to disable Auto Multi Frame Bursting. • Though Auto Multi Frame Bursting configuration is not applicable from SU/End Point B, the SU/End Point B does Auto Multi Frame Bursting under the control of BSU/End Point A respectively. Registration Timeout Represents the maximum time for a SU to register with a BSU or vice versa, or an End Point B to register with an End Point A or vice versa. The registration timeout value can be set in the range 1 to 10 seconds. The default registration timeout value is 10 seconds. Retry Count Represents the maximum number of times the data is retransmitted by the transmitter over the wireless medium, if acknowledgement from the peer is not received. The Retry Count parameter can be configured in the range 0 to 10 seconds. By default, it is set to 3. DDRS Status : Applicable only when DDRS is enabled. It is a read-only parameter that displays the status of the DDRS feature. For more details refer to DDRS. Tx Rate Represents the modulation rate at which the packets are transmitted from the wireless device. Please note that the a change in Channel Bandwidth, Guard Interval and Number of Data Streams will reset Tx rate to default values. : Applicable only when the DDRS is disabled on the device. See DDRS. Input or Output This parameter limits the data received or transmitted to the wireless interface. It limits the Bandwidth Limit data from a minimum of 64 Kbps to the maximum value specified in the License File. : Input/Output Bandwidth throttling does not throttle broadcast/multicast traffic. These traffic can be trottled by the Maximum Information Rate (MIR) / Committed Information Rate (CIR) configured for DL-L2 Broadcast BE in QoS Service Flow. See QoS Service Flow Configuration (SFC) Tsunami® 8100 Series - Software Management Guide 47

Advanced Configuration • MAC ACL Status and Radius MAC ACL Status parameters cannot be enabled simultaneously. • When you modify WORP parameters and click COMMIT, it may result in brief interruption. 5.4.2 Wireless Interface Properties To configure the wireless interface properties, navigate to ADVANCED CONFIGURATION > Wireless > Interface 1 > Properties. The Wireless Interface Properties screen appears depending on your device: Figure 5-10 Wireless Interface Properties The Wireless Interface Properties screen is classified under two categories: Basic and Advanced. Tsunami® 8100 Series - Software Management Guide 49

Advanced Configuration Basic Configuration Under Basic Configuration screen, you can configure and view the following parameters. Parameter Descriptions Channel Bandwidth By default, the channel bandwidth is set to 20 MHz. 40 MHz can be selected for higher throughputs depending on the distance and signal quality. 5 and 10 MHz can be selected for greater flexibility in spectrum selection. : A change in Channel Bandwidth will reset the Tx Rate and Maximum EIRP to default. Channel Offset : Applicable only to Tsunami® MP-8160-BSU; Tsunami® MP-8160-SUA; Tsunami® MP-8150-CPE; Tsunami® MP-8160-CPE; Tsunami® QB-8150-EPR-12/50 devices. The Channel Offset parameter helps to change the operating channel center frequency. If the predefined center frequencies are not desirable, user can shift the center frequency to suit the requirements by configuring the Channel Offset. By default, the Channel Offset is set to 0. You can configure the Channel Offset in the range -2 to +2 MHz. For example, consider a channel number 100 with center channel frequency set to 5500 MHz. If the Channel Offset is set to 0 MHz, the center channel frequency remains at 5500 MHz. If you configure the Channel Offset to 2MHz then the center channel frequency will change to 5502MHz. Similarly for a Channel Offset of -2MHz, the center channel frequency is changed to 5498 MHz. : Even though the center channel frequency is changed, the channel number still remains same, in this case 100. Auto Channel Auto Channel Selection (ACS) enables the device to determine the best channel for Selection (ACS) wireless data transmission with less interference. If ACS is enabled on the BSU/End Point A, it scans all the channels and selects the best channel at the startup. If ACS is enabled on the SU/End Point B, it continuously scans all the channels till it finds a suitable BSU/End Point A and connects to it. By default, ACS is disabled on BSU/End Point A and enabled on SU/End Point B. : On BSU/End Point A, ACS is performed only during startup. Preferred Channel Allows the user to select and operate in the preferred channel. Preferred channel can be configured only when ACS is disabled. If Dynamic Frequency Selection (DFS) is active, the device will automatically pick a new channel when radar interference is detected. Tsunami® 8100 Series - Software Management Guide 50

Advanced Configuration Parameter Descriptions Active Channel A read-only parameter that displays the current operating channel on which the wireless interface is operating. : Active Channel can be different from Preferred Channel if radar interface is detected. Satellite Density Satellite Density setting helps achieve maximum bandwidth in a wireless network. It influences the receive sensitivity of the radio interface and improves operation in environments with high noise level. Reducing the sensitivity of the device enables unwanted “noise” to be filtered out (it disappears under the threshold). You can configure the Satellite Density to be Disable, Large, Medium, Small, Mini, or Micro. By default, Satellite Density is set to Large. The Medium, Small, Mini, and Micro settings are appropriate for higher noise environments; whereas, Large is appropriate for a lower noise environment. A long distance link can have difficulty in maintaining a connection with a small density setting because the wanted signal can disappear under the threshold. Consider both noise level and distance between the peers in a link when configuring this setting. The threshold should be chosen higher than the noise level, but sufficiently below the signal level. A safe value is 10dB below the present signal strength. If the Signal-to-Noise Ratio (SNR) is not sufficient, you may need to set a lower data rate or use antennas with higher gain to increase the margin between wanted and unwanted signals. In a point-to-multipoint link, the BSU or End Point A should have a density setting suitable for an SU or End Point B, especially the ones with the lowest signal levels (longest links). Take care when configuring a remote interface; check the available signal level first, using Remote Link Test. Tabulated below are the Sensitivity Threshold Values corresponding to various Satellite Density values: Satellite Density Receive Sensitivity Defer Threshold Threshold Large -96 dbm -62 dbm Medium -86 dbm -62 dbm Small -78 dbm -52 dbm Mini -70 dbm -42 dbm Micro -62 dbm -36 dbm : When the remote interface is accidentally set to small and communication is lost, it cannot be reconfigured remotely and a local action is required to restore the communication link. Therefore, the best place to experiment with the level is at the device that can be managed without going through the link. If the link is lost, the setting can be adjusted to the correct level to bring the link back. Tsunami® 8100 Series - Software Management Guide 51

Advanced Configuration Parameter Descriptions ATPC Status If Adaptive Transmit Power Control (ATPC) is enabled, then the device automatically adjusts the transmit power to avoid saturation of remote receiver, which could cause data errors leading to lower throughput and link outage. If disabled, user can manually adjust the transmit power. By default, ATPC is enabled on the device. Transmit Power Control (TPC) is calculated based on two factors: • Equivalent Isotropically Radiated Power (EIRP) • Maximum Optimal SNR • Antenna Gain : In BSU, the ATPC considers the EIRP only; where as in SU, End Point A and End Point B both EIRP and Maximum SNR are considered. Tsunami® 8100 Series - Software Management Guide 52

Advanced Configuration Parameter Descriptions Max EIRP The maximum effective power that a radio antenna is allowed to radiate as per the regulatory standard. By default, the maximum EIRP is set as per the regulatory requirements for each frequency domain. Tabulated below are the default maximum EIRP values that are set according to regulatory domain: Regulatory Frequency Max EIRP (dBm) Domain (MHz) PTP Mode (QB) PTMP Mode (MP) World All Unlimited (100) Unlimited (100) United States 2402-2472 32 + 2/3(antenna BSU: 36 gain) SU/CPE: 32 + 2/3 (antenna gain) 4940 - 4990 33 (20 MHz) 33 (20 MHz) 30 (10 MHz) 30 (10 MHz) 27 (5 MHz) 27 (5 MHz) 5250 - 5330 30 30 5735 - 5835 53 36 Canada 4940 - 4990 33 (20 MHz) 33 (20 MHz) 30 (10 MHz) 30 (10 MHz) 27 (5 MHz) 27 (5 MHz) 5250 - 5330 30 30 5490 - 5590 30 30 5650 - 5710 30 30 5730 - 5860 53 36 Europe 2402 - 2472 20 20 (including UK) 5490 - 5590 30 30 5650 - 5710 30 30 5735 - 5875 36 36 Russia 5150 - 5350 33 33 5350 - 5650 Unlimited (100) Unlimited (100) 5650 - 6425 53 53 Taiwan 5490 - 5710 30 30 5735 - 5835 36 36 Tsunami® 8100 Series - Software Management Guide 53

Advanced Configuration Parameter Descriptions Regulatory Frequency Max EIRP (dBm) Domain (MHz) PTP Mode PTMP Mode India 5825 - 5875 36 36 Brazil 5470 - 5725 30 30 5725 - 5850 Unlimited (100) 32 + 2/3(antenna gain) Australia 5470 - 5600 30 (20 and 40 MHz) 30 (20 and 40 MHz) 27 (10 MHz) 27 (10 MHz) 24 (5 MHz) 24 (5 MHz) 5650 - 5725 30 (20 and 40 MHz) 30 (20 and 40 MHz) 27 (10 MHz) 27 (10 MHz) 24 (5 MHz) 24 (5 MHz) 5725 - 5850 36 36 : • The maximum EIRP is not defined in the above table then it is set to 100 (unlimited EIRP). • Maximum EIRP criterion is enforced only when ATPC is enabled. Active TPC A read-only parameter which displays the TPC applied by the device to adjust the transmit power, when ATPC is enabled. : In case of BSU, the Active TPC refers to the TPC applied to the broadcast packets. To view Active TPC of each link, refer to SU / End Point B Link Statistics. Active EIRP A read-only parameter which displays the current EIRP that a radio antenna radiates. Active Power A read-only parameter which displays the current power radiated by the radio. Tsunami® 8100 Series - Software Management Guide 54

Advanced Configuration Parameter Descriptions TPC This parameter enables you to manually set the Transmit Power Control (TPC) value when ATPC is disabled. You can manually set TPC ranging from 0 to 25 dBm. With TPC, you can adjust the output power of the device to a lower level. This is performed to reduce interference with the neighboring devices. It can be helpful when higher gain antenna is used without violating the maximum radiated output power for a country or regulatory domain. By default, it is set to 0 dBm. : • TPC only lets you decrease the output power; it does not let you increase the output power beyond the maximum allowed defaults for the selected frequency and country. • TPC can be configured in the steps of 0.5 dB Antenna Gain The sensitivity of the radio card can be modified when detecting radar signals in accordance with ETSI, FCC, and IC Dynamic Frequency Selection (DFS) requirements. As the radar detection threshold is fixed by ETSI, the FCC, and IC and a variety of antennas with different gains may be attached to the device, you must adjust this threshold to account for higher than expected antenna gains. This can avoid false radar detection events which can result in frequent change in the Frequency channels. Configure the threshold for radar detection at the radio card to compensate for increased external antenna gains. The Antenna Gain value ranges from 0 to 40 dBi. For devices with connectorized antenna, the Antenna Gain by default is set to zero dBi. Tabulated below are the default Antenna Gain, for devices with integrated antenna: Product (s) Antenna Gain Tsunami® MP-8150-SUR 23 dBi Tsunami® MP-8150-CPE 16 dBi Tsunami® MP-8160-CPE 15 dBi Tsunami® QB-8150-EPR/ 23 dBi Tsunami® QB-8150-LNK Tsunami® QB-8150-EPR-12/50 16 dBi Wireless Inactivity Resets the wireless interface if there is no change in the Tx and Rx Packet Count in the Timer specified interval of time. The default value is set to 10 seconds (disabled if set to 0 seconds) and can be configured between 5 to 600 seconds. Tsunami® 8100 Series - Software Management Guide 55

Advanced Configuration Parameter Descriptions Legacy Mode When Legacy Mode is enabled, the BSU can interoperate with the legacy products of the Tsunami MP.11 family: MP.11 5054 series, 5012 series, 2454 series and so on. By default, it is disabled. : Applicable only to Tsunami® MP-8100-BSU. After configuring the required parameters, click OK and then COMMIT. Reboot the device, if you have changed any of the Wireless Interface parameters with asterisk (*) symbol marked against them. Advanced To view Advanced parameters, click Advanced tab in the Wireless Interface Properties screen. The following screen appears: Figure 5-11 Advanced Wireless Properties The following table lists the Advanced Wireless properties parameters and their description. Note that these parameters are read-only and can be configured only through CLI or SNMP. Parameter Description ATPC Lower Margin SNR Upper Limit = Maximum Optimal SNR and SNR Initial = SNR Upper Limit - ATPC Upper Margin ATPC Upper Margin SNR Lower Limit = SNR Initial - ATPC Lower Margin ATPC Algorithm, after reducing the power to honor the Maximum EIPR limit, adjusts the power based on Maximum Optimal SNR, ATPC Upper Margin and ATPC Lower Margin. To begin with, ATPC will adjust the power to bring the SNR to SNR Initial and adjusts power only when the current SNR goes beyond the SNR Upper Limit and SNR Lower Limit. Click Local SNR-Table, to view the optimal SNR values that are exchanged with the peer for optimal throughput. Tsunami® 8100 Series - Software Management Guide 56

Advanced Configuration 5.4.3 MIMO Properties The MIMO Properties tab allows you to configure the Multiple-Input-Multiple-Output (MIMO) parameters that enable to achieve high throughput and longer range. To configure MIMO properties, navigate to ADVANCED CONFIGURATION > Wireless > Interface1 > MIMO Properties. The MIMO Properties screen appears: Figure 5-12 3x3 MIMO Properties Figure 5-13 2x2 MIMO Properties Tabulated below is the table which explains MIMO parameters and the method to configure the configurable parameters: Parameter Description MIMO Properties Tsunami® 8100 Series - Software Management Guide 57

Advanced Configuration Parameter Description Frequency Extension Frequency Extension is applicable only when the Channel Bandwidth is set to 40 MHz. While choosing 40MHz bandwidth, you can select either 40 PLUS (Upper Extension Channel) or 40 MINUS (Lower Extension Channel). 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. Guard Interval Guard Interval determines the space between symbols being transmitted. The guard interval can be configured as either Short GI - 400n seconds or Full GI-800n seconds. In 802.11 standards, when 40 MHz Channel Bandwidth is configured then Short GI can be used to improve the overall performance and throughout. By default, Full GI is enabled for 5 MHz, 10 MHz and 20 MHz channels. : Short GI-400 nSec is valid only for 40 MHz channel bandwidth. Data Streams MIMO radio uses multiple antennas for transmitting and receiving the data. The data streams supported by the device are as follows: • Single: In single data stream, the data frames are transmitted in parallel over all the antennas. This stream is recommended for longer range. • Dual: In dual data stream, the data frames are distributed across the antennas and transmitted. This stream is recommended for higher throughput. : Data streams is not applicable when DDRS is enabled. Antenna Status Tx Antenna Status Allows the user to select the antenna(s) for data transmission. Select the checkbox against each antenna(s) for data transmission and click Ok. : Atleast two Tx antenna ports should be enabled when Data Stream is dual, or DDRS Stream Mode is set to auto or dual. Rx Antennas Status Allows the user to select the antenna(s) for receiving data. Select the checkbox against each antenna(s) for receiving data and click Ok. : Atleast two Rx antenna ports should be enabled when Data Stream is dual, or DDRS Stream Mode is set to auto or dual. : Modifying the Guard Interval and Data Stream configuration values, will reset the Tx Rate to default value. Tsunami® 8100 Series - Software Management Guide 58

Advanced Configuration After configuring the required parameters, click OK and then COMMIT. Reboot the device, if you have changed any of the MIMO parameters with asterisk (*) symbol marked against them. 5.4.4 Dynamic Frequency Selection (DFS) The Tsunami® products support Dynamic Frequency Selection (DFS) for FCC, IC, and ETSI regulatory domains per FCC Part 15 Rules for U-NII devices, IC RSS-210, and ETSI EN 301-893 regulations, respectively. These rules and regulations require that the devices operating in the 5 GHz band must use DFS to prevent interference with RADAR systems. : DFS is not applicable in case of Tsunami® MP-8160-BSU, Tsunami® MP-8160-SUA and Tsunami® MP-8160-CPE devices. 5.4.4.1 DFS in BSU or End Point A mode Explained below is the DFS functionality and the way it operates on a BSU or in End Point A devices. 1. Based on the selected frequency (regulatory) domain, DFS is automatically enabled on the device. 2. During bootup, • if ACS is disabled on the device, the device chooses the Preferred Channel to be the operational channel. : By default, Automatic Channel Selection (ACS) is disabled on the BSU or a device in End Point A mode. • if ACS is enabled, then the device scans all the channels and selects the channel with the best RSSI to be the operational channel. 3. Once the operating channel is selected, the device scans the channel for the presence of the RADAR for a duration of the configured Channel Wait Time (by default configured to 60 seconds). During this time, no transmission of data occurs. 4. If no RADAR is detected, the device starts operating in that channel. 5. If RADAR is detected, the channel is blacklisted for 30 minutes. Now, ACS will scan all the non-blacklisted channels and select the channel with best RSSI. Upon choosing the best channel, the device again scans the selected channel for the presence of the RADAR for a duration of the configured Channel Wait Time. Again, during this time no transmission of data occurs. 6. If no RADAR is detected, it operates in that channel else repeats step 5. 7. While operating in a channel, the device continuously monitors for potential interference from a RADAR source (this is referred to as in-service monitoring). If RADAR is detected, then the device stops transmitting in that channel. The channel is added to the blacklisted channel list. 8. A channel in the blacklisted listed can be purged once the Non Occupancy Period (NOP) has elapsed for that channel. : • When a channel is blacklisted, all its sub-channels that are part of the current channel bandwidth are also blacklisted. • For Europe 5.8 GHz channel, once the device finds a RADAR free channel (after 60 seconds RADAR scan), it does not perform scan for the next 24 hours. This is not applicable when device is rebooted or a particular channel got blacklisted earlier. • Even if the preferred channel is configured with a DFS channel manually, the SU will scan for the BSU/End PointA's channel and associates automatically. Tsunami® 8100 Series - Software Management Guide 59

Advanced Configuration 5.4.4.2 DFS in SU or End Point B Mode Explained below is the DFS functionality and the way it operates on SU or End Point B. 1. When SU/End Point B has no WORP link, it scans continuously all the channels in the configured Frequency Domain for the presence of BSU/End Point A. If suitable BSU/End Point A is found in any scanned channel, the SU or End Point B tries to establish WORP link. 2. After selecting the suitable BSU/End Point A’s channel, • If SU/End Point B DFS is disabled, then SU/End Point B tries to connect to BSU/End Point A. • If SU/End Point B DFS is enabled, the SU/End Point B scans the selected channel for the presence of the RADAR for a duration of the configured Channel Wait Time (by default configured to 60 seconds). During this time, if the SU/End Point B detects radar, the channel is blacklisted and it starts scanning on non-blacklisted channels for a BSU/End Point A as given in step 1. If no radar is detected, a connection will be established. 3. While WORP link is present, the SU/End Point B continuously monitors the current active channel for potential interference from a RADAR source (this is referred to as in-service monitoring). • If RADAR is detected, the SU/End Point B sends a message to the BSU or End Point A indicating the RADAR detection on the active channel and blacklists that channel for Non Occupancy Period (NOP). The default NOP is 30 Minutes. • On receiving the RADAR detection message from SU/End Point B, the BSU/ End Point A blacklists the active channel and ACS starts scanning for an interference free channel. : The BSU blacklist the channel only when the number of SUs reporting the RADAR equals or exceeds the configured SUs Reporting RADAR parameter. 4. A blacklisted channel can be purged once the Non Occupancy Period (NOP) has elapsed. : • On the SU/End Point B, if the preferred channel is configured with a DFS channel then SU will scan all the channels even if ACS is disabled. • When a channel is blacklisted, all its sub-channels that are part of that channel bandwidth are also blacklisted. For detailed information on DFS enabled countries, see Frequency Domains and Channels. Tsunami® 8100 Series - Software Management Guide 60

Advanced Configuration To configure DFS parameters, navigate to ADVANCED CONFIGURATION > Wireless > Interface 1 > DFS. The Dynamic Frequency Selection (DFS) screen appears. Figure 5-14 DFS Configuration (BSU Mode) Tsunami® 8100 Series - Software Management Guide 61

Advanced Configuration Figure 5-15 DFS Configuration (SU/End Point B Mode) Tabulated below is the table which explains DFS parameters and the method to configure the configurable parameter(s): Parameter Description Channel Wait Time One the device selects the best channel, it scans that channel for the presence of RADAR for a period of set Channel Wait Time. The wait time can be configured in the range 0 to 3600 sec. By default, the wait time is set to 60 seconds. SUs Reporting RADAR Applicable only to BSU. When a SU detects a RADAR, it reports to BSU. The BSU will take a decision on whether to blacklist this channel based on SUs Reporting RADAR parameter. If the number of SU reporting RADAR equals or exceed the configured SUs Reporting RADAR parameter then BSU blacklists that channel. If SUs reporting the RADAR is less than this configured value then BSU continues to operate in the same channel. The range varies depending on the product license. By default, it is set to 0. DFS Status Applicable only to SU or End Point B devices. A SU or End Point B devices have the option to either enable or disable DFS. By default, DFS is disabled. After configuring the required parameters, click OK and then COMMIT. Tsunami® 8100 Series - Software Management Guide 62

Advanced Configuration 5.4.4.3 Blacklist Information The blacklisted table displays all the channels that are blacklisted. Parameter Description Channel Number Indicates the channel that is blacklisted. Reason Specifies the reason for blacklisting a channel. Following are the reasons for blacklisting a channel: 1. Remote Radar: A SU/End Point B detects a RADAR and informs BSU/End Point A accordingly. 2. Local Radar: The device detects the RADAR on its own. 3. Unusable: For bandwidths more than 5 MHz, channels that are not usable because they fall in the frequency range of other radar/manual blacklisted channels. For example, if channel 110 is blacklisted, then channels 108, 109, 111, 112 will become unusable for 20 MHz bandwidth. 4. Manual: A channel is manually blacklisted by the administrator. Time Elapsed The time elapsed since the channel was blacklisted due to radar. When the channel is blacklisted due to the presence of a radar, it will be de-blacklisted after 30 Minutes. This parameter is applicable for radar blacklisted channels only. Click Refresh, to view updated/refreshed blacklisted channels. 5.4.4.4 Manual Blacklist This tab enables you to manually blacklist a channel. However, there are few conditions to be followed while blacklisting channels: • When ACS is disabled, the preferred channel and its sub-channels that are part of the current channel bandwidth cannot be manual blacklisted. • When WORP link is UP, the active channel and its sub-channels that are part of the current channel bandwidth cannot be manual blacklisted. • When DFS/ACS is enabled, atleast one channel and its sub-channels that are part of the current channel bandwidth should be available for operation. That is, all channels cannot be blacklisted. To manual blacklist channels, click Manual Blacklist under Dynamic Frequency Selection (DFS) screen. The following screen appears: Tsunami® 8100 Series - Software Management Guide 63

Advanced Configuration Figure 5-16 Manual Blacklist Select the channels that you want to blacklist by entering the start and end channels in the Start Channel and End Channel boxes respectively. Next, click Add. All the selected channels are added to the Blacklisted Channels table. To remove any blacklisted channel, enter the Start and End Channel of the blacklisted channels and then click Remove button. To refresh channel entries, click Refresh. 5.4.5 DDRS Dynamic Data Rate Selection (DDRS) feature adjusts the transmission data rate to an optimal value to provide the best possible throughput according to the current communication conditions and link quality. The factors for adjusting the transmission data rate are, 1. Remote average Signal-to-noise (SNR) ratio 2. Number of retransmissions DDRS can be configured separately on each device (BSU mode/ SU mode /End Point A mode/ End Point B mode). 5.4.5.1 DDRS Configuration To configure DDRS on the device, navigate to ADVANCED CONFIGURATION > Wireless > Interface 1 > DDRS. The DDRS Configuration screen appears: Tsunami® 8100 Series - Software Management Guide 64

Advanced Configuration Figure 5-17 Basic DDRS Configuration The DDRS Configuration is classified under two categories, namely, Basic and Advanced. Basic Configuration Under Basic Configuration screen, you can configure the following parameters. Parameter Description DDRS Status Enables the user the either enable or disabled DDRS feature on the device. By default, it is enabled on the device. Stream Mode Select the stream mode as either Auto, Single or Dual. By default, the Auto mode is selected. Based on the selected stream modes, DDRS dynamically chooses the data rate. • Dual: Select Dual, for higher throughput. • Single: Select Single, for reliability and longer range. • Auto: When configured to Auto, DDRS decides on the stream modes based on the environment conditions. : Stream Mode is not valid in legacy mode. Maximum Rate Represents the maximum data rate that DDRS can dynamically choose to provide the best possible throughput. The default value depends on the channel bandwidth and the number of streams. : A change in Frequency Domain, Channel Bandwidth, Guard Interval and Data Stream will reset maximum data rate to defaults. After configuring the required parameters, click OK and then COMMIT. Advanced Configuration To view Advanced Configuration parameters, click Advanced tab in the DDRS Configuration screen. The following screen appears depending on your device: Tsunami® 8100 Series - Software Management Guide 65

Advanced Configuration Figure 5-18 Advanced DDRS Configuration The following table lists the Advanced Configuration parameters and their description. Note that these parameters are read-only and can be configured only through CLI or SNMP. Parameter Description Minimum Rate and Represents the minimum and maximum data rate between which the DDRS dynamically Maximum Rate selects the transmission data rate. These varies depending on the configured Data Streams, Channel Bandwidth and Guard Interval. Lower SNR Correction Represents the margin value to be added to the Minimum Required SNR, for the purpose of removing the data rate from the valid data rate table. Doing so, avoids Hysteresis in the dynamic data rate. By default, it is configured to 10 dB. Upper SNR Correction Represents the margin value to be added to the Minimum Required SNR, for the purpose of adding the data rate to the valid data rate table. Doing so, avoids Hysteresis in the dynamic data rate. By default, it is set to 3 dB. Rate Increment RTX Represents a threshold for the percentage of retransmissions, below which the rate can be Threshold increased. By default, it is set to 25%. : If the percentage of retransmissions is between “Rate Increment RTX Threshold” and “Rate Decrement RTX Threshold” then the current operation rate is maintained. Tsunami® 8100 Series - Software Management Guide 66

Advanced Configuration Rate Decrement RTX Represents a threshold for percentage of retransmissions, above which the rate can be Threshold decreased. By default, it is set to 30%. Please note that if the percentage of retransmissions is between “Rate Increment RTX Threshold” and “Rate Decrement RTX Threshold” then the current operation rate is maintained. Chain Balance In the case of MIMO, the difference in SNR between two chains must be less than or equal Threshold to this threshold for the chains to be considered as “Balanced”. By default, it is set to 15 dB. : • This parameter is applicable only for “Auto” stream mode. • When “Auto” stream mode is configured and if chains are not balanced, then Single Stream rates are considered. Rate Back Off Interval The DDRS algorithm constantly attempts higher data rates, when the current rate is stable. If not successful, it goes back to older stable rate. Before the next attempt, it waits for a minimum duration. This duration starts with 10 seconds and increases exponentially up to Rate Back Off Interval and remains at this value. By default, it is set to 300 seconds. Click Local SNR-Table, to view the optimal SNR values that are exchanged with the peer for optimal throughput. Tsunami® 8100 Series - Software Management Guide 67

$Advanced Configuration Tabulated below is the table which explains the method to create a new Security Profile: Parameter Description Profile Name A name to uniquely identify a security profile name. Encryption Type Select encryption type as either None, WEP, TKIP or AES-CCM. 1. None - If the encryption type is selected as None, then there exist no security to the data frames transmitted over the wireless medium. 2. WEP (Wired Equivalent Privacy) - Represents the WEP Encryption type, which uses RC4 stream cipher for confidentiality and CRC-32 for integrity. The supported key lengths for WEP are 5/13/16 ASCII Characters or 10/26/32 Hexadecimal digits. - Key1 / Key 2 / Key 3 / key 4: You can configure a maximum of four WEP keys. Enter 5/13/16 ASCII Characters or 10/26/32 Hexadecimal digits for WEP keys. - Transmit Key: Select one out of the four keys described above as the default transmit key, which is used for encrypting and transmitting the data. 3. TKIP - Represents the TKIP Encryption type, which uses RC4 stream cipher for confidentiality. TKIP provides per-packet key mixing, a message integrity check and a re-keying mechanism. It uses 128-bit keys for encryption. The key length for TKIP is 16 ASCII characters or 32 Hexadecimal digits. - Key1 / Key 2 / Key 3 / key 4: You can configure a maximum of four TKIP keys. Enter 16 ASCII Characters or 32 Hexadecimal digits. - Transmit Key: Select one out of the four keys described above as the default transmit key, which is used for encrypting and transmitting the data. 4. AES-CCM - Represents CCM Protocol with AES Cipher restricted to 128 bits. • Key: Enter 16 ASCII Characters or 32 Hex Digits for AES-CCM encryption keys. Entry status Enables a user to either Enable or Disable the security profile on the device. By default, it is enabled. Network Secret Enter the WORP Protocol Secret Key, ranging from 6 to 32 characters, used for authenticating a SU with a BSU, and an End Point B with End Point A. The network secret should be same for a BSU and SU. Similarly, the network secret should be same for an End Point A and an End Point B. : • A maximum of 8 security profiles can be created. • A Quick Bridge support AES-CCM encryption type only. • Special characters like - = \ " ' ? / space are not allowed while configuring the keys. • All four Keys (Key1, Key2, Key3, Key4) must be of same length and same type, that is, all four Keys must be either ASCII Characters or Hexadecimal digits. • Transmit Key can be any one of the four keys, provided all the four keys are same in a SU and BSU, or End Point devices. • WEP and TKIP Encryption Types are supported only in legacy Modes. • The encryption mode should not be selected as AES-CCM while the device is interoperating with legacy Tsunami® MP.11 family devices which include 954-R, 2454-R, 4954-R, 5054-Series, and 5012-Series. After configuring the required parameters, click Add and then COMMIT. Tsunami® 8100 Series - Software Management Guide 70$

Advanced Configuration • Deny: Does not allow the SUs/End Point B devices configured in the MAC Access Control Table to access the wireless network. Click OK, if you have changed the Operation Type parameters. 5.5.3.1 Add SUs/End Point B to MAC Access Control Table To add entries to MAC Access Control table, click Add in the MAC Access Control screen. The MAC ACL Add Row screen appears: Figure 5-25 MAC ACL Add Row 1. Type the MAC Address of the SU/End Point B. 2. Add comments, if any. 3. Select the Entry Status as either Enable or Disable. 4. Next, click Add. : • The maximum number of SUs/End Point Bs that can be added to the MAC ACL table is 250. • Either RADIUS MAC or Local MAC can be enabled at one time. 5.5.3.2 Edit the existing SUs/End Point B from MAC Access Control Table To edit the existing SUs/End Point B from MAC Access Control Table, edit parameters from the MAC Access Control Table in MAC Access Control screen and click OK. 5.6 Quality of Service (QoS) The Quality of Service (QoS) feature is based on the 802.16 standard and defines the classes, service flows, and packet identification rules for specific types of traffic. The main priority of QoS is to guarantee a reliable and adequate transmission quality for all types of traffic under conditions of high congestion and bandwidth over-subscription. There are already several pre-defined QoS classes, SFCs and PIRs available that you may choose from which cover the most common types of traffic. If you want to configure something else, you start building the hierarchy of a QoS class by defining PIRs; you define the QoS class by associating those PIRs to relevant SFCs with priorities to each PIR within each SFC. Qos can be applied on standard 802.3 ethernet frames as well as PPPoE encapsulated frames. 5.6.1 QoS Concepts and Definitions QoS feature is applicable for BSU or End Point A only. You may define different classes of service on a BSU or End Point A that can then be assigned to the SU or End Point B that is associated, or that may get associated, with that BSU or End Point A. You can create, edit, and delete classes of service that are specified below in the following hierarchy of parameters: Tsunami® 8100 Series - Software Management Guide 74

Advanced Configuration • Packet Identification Rule (PIR) - up to 64 rules, including 18 predefined rules • Service Flow class (SFC) - up to 32 SFCs, including 8 predefined SFCs; up to 8 PIRs may be associated per SFC • Class List - Priority for each rule within each SF class - 0 to 255, with 0 being lowest priority • QoS class - up to 8 QoS classes, including 5 predefined classes; up to 8 SFCs may be associated per QoS class 5.6.1.1 Packet Identification Rule (PIR) A Packet Identification Rule is a combination of parameters that specifies what type of traffic is allowed or not allowed. You can create a maximum of 64 different PIRs, including 18 predefined PIRs. Also, you can create, edit, and delete PIRs that contain none, one, or more of the following classification fields: • Rule Name • IP ToS (Layer 3 QoS identification) • 802.1p tag (layer 2 QoS identification) • IP Protocol List containing up to 4 IP protocols • VLAN ID • PPPoE Encapsulation • Ether Type (Ethernet Protocol identification) • Up to 4 TCP/UDP Source port ranges • Up to 4 TCP/UDP Destination port ranges • Up to 4 pairs of Source IP address + Mask • Up to 4 pairs of Destination IP address + Mask • Up to 4 source MAC addresses + Mask • Up to 4 destination MAC addresses + Mask : IP Address, TCP/UDP Port, MAC Address need to be configured separately and associate those classification in PIR details if required. A good example is provided by the 18 predefined PIRs. Note that these rules help identify specific traffic types: 1. All - No classification fields, all traffic matches 2. L2 Multicast a. Ethernet Destination (dest = 0x010000000000, mask = 0x010000000000) 3. L2 Broadcast a. Ethernet Destination (dest = 0xffffffffffff, mask = 0xffffffffffff) 4. Cisco VoIP UL a. TCP/UDP Source Port Range (16,000-33,000) b. IP Protocol List (17 = UDP) 5. Vonage VoIP UL a. TCP/UDP Source Port Range (5060-5061, 10000-20000) b. IP Protocol List (17 = UDP) 6. Cisco VoIP DL a. TCP/UDP Destination Port Range (16,000-33,000) b. IP Protocol List (17 = UDP) 7. Vonage VoIP DL a. TCP/UDP Destination Port Range (5060-5061, 10000-20000) Tsunami® 8100 Series - Software Management Guide 75

Advanced Configuration • Tolerable Jitter - specified in increments of 1 ms steps from a minimum of 0 ms up to the Maximum Latency (in ms) • Traffic priority - zero (0) to seven (7), 0 being the lowest, 7 being the highest • Maximum number of data messages in a burst - one (1) to sixteen (16), which affects the percentage of the maximum throughput of the system • Entry Status - Enable, Disable, and Delete : Note that traffic priority refers to the prioritization of this specific Service Flow. The device tries to deliver the packets within the specified latency and jitter requirements, relative to the moment of receiving the packets in the device. For delay-sensitive traffic, the jitter must be equal to or less than the latency. A packet is buffered until an interval of time equal to the difference between Latency and jitter (Latency - Jitter) has elapsed. The device will attempt to deliver the packet within a time window starting at (Latency - Jitter) until the maximum Latency time is reached. If the SFC’s scheduling type is real-time polling (RTPS), and the packet is not delivered by that time, it will be discarded. This can lead to loss of packets without reaching the maximum throughput of the wireless link. For example, when the packets arrive in bursts on the Ethernet interface and the wireless interface is momentarily maxed out, then the packets at the “end” of the burst may be timed out before they can be sent. Users can set up their own traffic characteristics (MIR, CIR, latency, jitter, etc.) per service flow class to meet their unique requirements. A good example is provided by the 8 predefined SFCs: 1. UL-Unlimited BE a. Scheduling Type = Best Effort b. Service Flow Direction = Uplink c. Entry Status = Enable d. Maximum Sustained Data Rate = 102400 Mbps e. Traffic Priority = 0 2. DL-Unlimited BE (same as UL-Unlimited BE, except Service Flow Direction = Downlink) 3. DL-L2 Broadcast BE (same as UL-Unlimited BE, except Service Flow Direction = Downlink) 4. UL-G711 20 ms VoIP RTPS a. Schedule type = RTPS (Real time Polling Service) b. Service Flow Direction = Uplink c. Entry Status = Enable d. Maximum Sustained Data Rate = 88 Kbps e. Minimum Reserved Traffic Rate = 88 Kbps f. Maximum Latency = 20 milliseconds g. Traffic Priority = 1 5. DL-G711 20 ms VoIP rtPS (same as UL-G711 20ms VoIP rtPS, except Service Flow Direction = Downlink) 6. UL-G729 20 ms VoIP rtPS (same as UL-G711 20ms VoIP rtPS, except Maximum Sustained Data Rate and Committed Information rate = 66 Kbps) 7. DL-G729 20 ms VoIP rtPS (same as UL-G729 20ms VoIP rtPS, except Service Flow Direction = Downlink) 8. DL-2Mbps Video a. Schedule type = Real time Polling b. Service Flow Direction = Downlink c. Initialization State = Active d. Maximum Sustained Data Rate = 2 Mbps e. Minimum Reserved Traffic Rate = 2 Mbps f. Maximum Latency = 20 milliseconds g. Traffic Priority = 1 Tsunami® 8100 Series - Software Management Guide 77

Advanced Configuration Note that two different VoIP Service Flow classes for each direction of traffic have been defined (index numbers 4 to 7) which follow the ITU-T standard nomenclatures: G.711 refers to a type of audio companding and encoding that produces a 64 Kbps bitstream, suitable for all types of audio signals. G.729 is appropriate for voice and VoIP applications, but cannot transport music or fax tones reliably. This type of companding and encoding produces a bitstream between 6.4 and 11.8 Kbps (typically 8 Kbps) according to the quality of voice transport that is desired. 5.6.1.3 QoS Class A QoS class is defined by a set of parameters that includes the PIRs and SFCs that were previously configured. You can create up to eight different QoS classes, including five predefined QoS classes. Up to eight SF classes can be associated to each QoS class, and up to eight PIRs can be associated to each SF class. For example, a QoS class called “G711 VoIP” may include the following SFCs: “UL-G711 20 ms VoIP rtPS” and “DL-G711 20 ms VoIP rtPS”. In turn, the SFC named “UL-G711 20 ms VoIP rtPS” may include the following rules: “Cisco VoIP UL” and “Vonage VoIP UL”. You can create, edit, and delete QoS classes that contain the following parameters: • QoS class name • Service Flow (SF) class name list per QoS class (up to eight SF classes can be associated to each QoS class) • Packet Identification Rule (PIR) list per SF class (up to eight PIRs can be associated to each SF class) • Priority per rule which defines the order of execution of PIRs during packet identification process. The PIR priority is a number in the range 0-255, with priority 255 being executed first, and priority 0 being executed last. The PIR priority is defined within a QoS class and can be different for the same PIR in some other QoS class. If all PIRs within one QoS class have the same priority, the order of execution of PIR rules will be defined by the order of definition of SFCs, and by the order of definition of PIRs in each SFC, within that QoS class. A good example of this hierarchy is provided by the five predefined QoS classes: 1. Unlimited Best Effort a. SF class: UL-Unlimited BE - PIR: All; PIR Priority: 0 b. SF class: DL-Unlimited BE - PIR: All; PIR Priority: 0 2. L2 Broadcast Best Effort a. SF class: DL-L2 Broadcast BE - PIR: L2 Broadcast; PIR Priority: 0 3. G711 VoIP a. SF class: UL-G711 20 ms VoIP rtPS - PIR: Vonage VoIP UL; PIR Priority: 1 - PIR: Cisco VoIP UL; PIR Priority: 1 b. SF class: DL-G711 20 ms VoIP rtPS - PIR: Vonage VoIP DL; PIR Priority: 1 - PIR: Cisco VoIP DL; PIR Priority: 1 4. G729 VoIP a. SF class: UL-G729 20 ms VoIP rtPS - PIR: Vonage VoIP UL; PIR Priority: 1 - PIR: Cisco VoIP UL; PIR Priority: 1 b. SF class: DL-G729 20 ms VoIP rtPS - PIR: Vonage VoIP DL; PIR Priority: 1 - PIR: Cisco VoIP DL; PIR Priority: 1 5. 2Mbps Video Tsunami® 8100 Series - Software Management Guide 78

Advanced Configuration a. SF class: DL-2Mbps Video - PIR: Streaming Video (IP/TV); PIR Priority: 1 5.6.2 QoS Configuration There are several pre-defined QoS classes, SFCs, and PIRs available that cover the most common types of traffic. If you want to configure something else, build the hierarchy of a QoS class as follows: 1. Define PIR MAC Address, IP Address and TCP/UDP Port Entries. 2. Define PIRs and specify packet classification rules, associate MAC Address/IP Address/TCP-UDP Port Entries if required. 3. Define SFCs 4. Define QoS Class by associating PIRs with relevant SFC. 5. Assign priorities to each PIR within each SFC. For detailed instructions on configuring a management station (a single station used for managing an entire network), refer to QoS Configuration for a Management Station. QoS PIR MAC Address Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > MAC Address Entries, the QoS PIR MAC Address Entries screen appears: 2. Three predefined MAC Address entries are displayed in this page. You can configure a maximum of 256 entries. MAC Address and Mask combination should be unique. This MAC Address entry can be referred in the PIR Rule’s Source or Destination MAC Address Classification. MAC Entry referred by any PIR rule cannot be deleted. Figure 5-26 QoS PIR MAC Address Entries 3. Click OK. To Add a New PIR MAC Address Entry, a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > MAC Address Entries, the QoS PIR MAC Address Entries screen appears. b. Click Add on the QoS PIR MAC Address Entries screen to add a new entry. The following screen appears for configuring the MAC Entry Details. Tsunami® 8100 Series - Software Management Guide 79

Advanced Configuration Figure 5-28 QoS PIR IP Address Entries To Add a New PIR IP Address Entry, a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > IP Address Entries. The QoS PIR IP Address Entries screen appears b. Click Add on the QoS PIR IP Address Entries screen to add a new entry. The following screen appears for configuring the IP Address Entry Details. Figure 5-29 QoS PIR IP Address Add Entry c. Provide the IP Address, Subnet Mask, Comment, Entry Status details and click Add. Comment field can be used by the user to identify when this particular entry is referred in PIR Rule or QoS Class. QoS PIR TCP/UDP Port Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > TCP/UDP Port Entries. The QoS PIR TCP/UDP Port Entries screen appears. Three predefined TCP/UDP Port Entries are displayed. You can configure a maximum of 256 entries. Start Port, End Port combination should be unique. This TCP/UDP Port entry can be referred in the PIR Rule’s Source or Destination TCP/UDP Port Classification. TCP/UDP Port Entry referred by any PIR rule can not be deleted. 2. Click OK. Tsunami® 8100 Series - Software Management Guide 81

Advanced Configuration Figure 5-30 QoS PIR TCP/UDP Port Entries To Add a New PIR TCP/UDP Port Entry, a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > TCP/UDP Port Entries. The QoS PIR TCP/UDP Port Entries screen appears. b. Click Add on the QoS PIR TCP/UDP Port Entries screen to add a new entry. The following screen appears for configuring the IP Address entry details. Figure 5-31 QoS PIR TCP/UDP Port Add Entry c. Provide the Start Port, End Port, Entry Status details and click Add. Comment field can be used to identify when this particular entry is referred in PIR Rule or QoS Class. 5.6.2.1 QoS PIR Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. The QoS PIR Entries screen appears. 18 predefined PIR Rules are displayed in this page. You can configure a maximum of 64 entries. PIR Rule Name should be unique. This PIR Rule can be referred in the QoS Class’s Service Flow Details. PIR rule referred by any QoS Class cannot be deleted. 2. Click OK. Tsunami® 8100 Series - Software Management Guide 82

Advanced Configuration Figure 5-32 QoS PIR Entries To Add a New PIR Rule, a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. The QoS PIR Entries screen appears. b. Click Add on the QoS PIR Entries screen to add a new entry. The following screen appears for configuring the New PIR Entry. Figure 5-33 QoS PIR Add Entry Tsunami® 8100 Series - Software Management Guide 83

Advanced Configuration c. Provide the PIR Name, Entry Status details and click Add. PIR Rule Clarification Details 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List and click Details for editing a particular PIR Rule. Tsunami® 8100 Series - Software Management Guide 84

Advanced Configuration Figure 5-34 QoS PIR Edit Entry Tsunami® 8100 Series - Software Management Guide 85

Advanced Configuration Parameter Description Rule Name This parameter specifies the Name of the Packet Identification Rule (PIR) and can have a length of 1-32 characters. ToS Rule This parameter is used to enable or disable a TOS rule. Enter the values for the following to specify the ToS-related configuration: • ToS Low • ToS High • ToS Mask Ether Priority Rule This parameters is used to enable or disable 802.1p priority rule. Enter the values for the following to specify 802.1p priority configuration: • Priority Low • Priority High VLAN Rule This parameters allows to enable or disable VLAN rule. Enter the VLAN ID when the VLAN rule is enabled. PPPoE Encapsulation This parameter is used to classify PPPoE traffic. • If you Enable/disable the PPPoE Configuration, it will automatically disable the Ether Type Rule. User can configure it again by enabling Ether Type Rule. • When PPPoE Encapsulation is enabled, incoming packet will be checked again Ether value “0x8864” and look for PPPoE Protocol Id value “0x0021”(IP Protocol) by default. User can modify the PPPoE Protocol Id. All other classification rules which are specified in the PIR rule will work only if the PPPoE Protocol Id is “0021”. • Ether Value is not valid when PPPoE Encapsulation is enabled. Ether Type Rule This parameters is used to enable or disable Ether Type rule. Enter the values for the following to specify the Ether Type rule related configuration: • Ether Type • PPPoE Protocol Id • Ether Value : • PPPoE Protocol Id is not valid if PPPoE Encapsulation is disabled. • Ether Value is not valid if PPPoE Encapsulation is enabled. Adding Protocol ID a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The Qos PIR Edit Entry screen appears. b. Navigate to Protocol Id Entries tab and then click Add to add a new Protocol entry. The following screen appears. Tsunami® 8100 Series - Software Management Guide 86

Advanced Configuration Figure 5-35 QoS PIR Protocol ID c. Enter the details and click Add. For deleting an entry, click Delete for the corresponding entry in PIR Details screen. Adding TCP/UDP Source Port Numbers a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The Qos PIR Edit Entry screen appears. b. Navigate to TCP/UDP Source Port Entries tab and then click Add to add a new entry. The following screen appears. Figure 5-36 QoS PIR TCP/UDP Source Port Add Entry c. All the Entries present in the PIR TCP/UDP Port Entries are displayed in the TCP/UDP Port Entry Table. Select the appropriate radio button and click Add. When an entry is added for the specific PIR, the entry gets displayed in the existing TCP/UDP Port Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Adding TCP/UDP Destination Port Numbers a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The Qos PIR Edit Entry screen appears. b. Navigate to TCP/UDP Destination Port Entries tab and then click Add to add a new entry. The following screen appears. Tsunami® 8100 Series - Software Management Guide 87

Advanced Configuration Figure 5-37 QoS PIR TCP/UDP Destination Port Add Entry c. All the entries present in the PIR TCP/UDP Port Entries are displayed in the TCP/UDP Port Entry Table. Select the appropriate radio button and click Add. When an entry is added for a specific PIR, it gets displayed in the existing TCP/UDP Port Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Adding Source IP Address a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The Qos PIR Edit Entry screen appears. b. Navigate to Source IP Address Entries tab and then click Add to add a new entry. The following screen appears: Figure 5-38 QoS PIR Source IP Address Add Entry c. All the entries present in the PIR IP Address Entries are displayed in the IP Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing IP Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Adding Destination IP Address a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The Qos PIR Edit Entry screen appears. Tsunami® 8100 Series - Software Management Guide 88

Advanced Configuration b. Navigate to Destination IP Address Entries tab and then click Add to add a new entry. The following screen appears. Figure 5-39 QoS PIR Destination IP Address Add Entry c. All the entries present in the PIR IP Address Entries are displayed in the IP Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing IP Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Adding Source MAC Address a. Click Add to add a new entry. The following screen appears. Figure 5-40 QoS PIR Source MAC address Add Entry b. All the entries present in the PIR MAC Address Entries are displayed in the MAC Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing MAC Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Adding Destination MAC Address a. Click Add to add a new entry. The following screen appears. Tsunami® 8100 Series - Software Management Guide 89

Advanced Configuration Figure 5-41 QoS PIR Destination MAC address Add Entry b. All the entries present in the PIR MAC Address Entries are displayed in the MAC Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing MAC Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. 5.6.2.2 QoS Service Flow Configuration (SFC) 1. Click ADVANCED CONFIGURATION > QoS > SFC List. Eight predefined SFCs are displayed in this page. This table allows the user to configure maximum of 32 entries. Service Flow Name should be unique. This SFC can be referred in the QoS Class’ Details. SFC referred by any QoS Class cannot be deleted. Figure 5-42 QoS Service Flow Entries Tsunami® 8100 Series - Software Management Guide 90

$Advanced Configuration Adding a New Service Flow (SFC): a. Click Add to add new entry. The following screen appears for configuring the New PIR Entry. Figure 5-43 QoS Service Flow Add Entry 2. Specify details for the Service Flow Name, Scheduler Type, Traffic Direction, MIR, CIR, Max Latency, Tolerable Jitter, Traffic Priority, Max Messages in Burst and Entry Status. 3. Click Add. Parameter Description Service Flow Name Specifies the Name of the Service Flow. It can be of length 1-32 characters. T : Special characters - = \ \"\ ' ? \\ / space are not allowed. Scheduler Type Specifies the Scheduler methods to be used. Scheduler type supports BE (Best Effort), RTPS (Real-Time Polling Service). Traffic Direction Specifies the Direction (Downlink or Uplink) of the traffic in which the configuration has to be matched. MIR (Maximum Specifies the maximum bandwidth allowed for this Service Flow. This value ranges from 8 Information Rate) kbps to maximum value specified in the license file. CIR (Committed Specifies the reserved bandwidth allowed for this Service Flow. This value ranges from 0 to Information Rate) maximum value specified in the license file. Max Latency Specifies the Latency value. This value ranges from 5 to 100 ms. Tolerable Jitter Specifies the Jitter value. This value ranges from 0 to 100 ms. Traffic Priority Specifies the priority of the Service flow when multiple Service flows are assigned to single QoS Class. This value ranges from 0 to 7. Tsunami® 8100 Series - Software Management Guide 91$

$Advanced Configuration Figure 5-45 QoS Class Add Entry b. Specify the QoS Class Name, Service Flow Name PIR Rule Name Priority and Entry Status and click Add. Parameter Description Class Name Specifies the Name of the QoS Class. This name length can range from 1 to 32 characters. : Special characters - = \ \"\ ' ? \\ / space are not allowed. Service Flow Name Specifies the Service Flow to be associated with the QoS Class. Select one of the possible SFCs that have been previously configured in the SFC List. PIR Rule Name Specifies the PIR Rule need to be associated with this Service Flow. Select one of the possible PIRs that have been previously configured in the PIR List. Priority Specifies priority or order of execution of PIRs during packet identification process. The PIR priority is a number that can range from 0-255, with priority 255 being executed first, and priority 0 being executed last. The PIR priority is defined within a QoS class, and can be different for the same PIR in some other QoS class. If all PIRs within one QoS class have the same priority, the order of execution of PIR rules will be defined by the order of definition of SFCs, and by the order of definition of PIRs in each SFC, within that QoS class. Entry Status Specifies the status of the QoS Class as enable/disable. Adding Service Flows in QoS Class 1. Click on the corresponding Details of the QoS Class for adding more Service Flows. Each QoS Class can have maximum 8 Service Flows. At least there should be one service flow per QoS Class. The following screen is displayed to configure the new SFC entry inside the QoS Class. 2. Click OK. Tsunami® 8100 Series - Software Management Guide 93$

Advanced Configuration Figure 5-46 QoS Class Service Flow Details 3. Click Add. The following screen appears for association of the new SFC in this QoS Class. Figure 5-47 QoS Class Service Flow Add Entry 4. Specify the Service Flow Name, PIR Rule Name, Priority and Entry Status and click Add to add a new entry. Adding PIR in QoS Class 1. Click on the corresponding Details provided in the Service Flow of a particular QoS Class. Maximum 8 PIR rules can be associated per SFC of an QoS Class. At least there should be one PIR per SFC of an QoS Class. The following screen appears to associate the new PIR entry inside an SFC of an QoS Class. 2. Click OK. Tsunami® 8100 Series - Software Management Guide 94

Advanced Configuration Figure 5-48 QoS Class PIR Details 3. Click Add. The following screen appears for association of the new PIR rule in an SFC already associated in an QoS Class. Figure 5-49 QoS Class PIR Add Entry 4. Specify the PIR Rule Name, Priority and Entry Status and click Add to add a new entry. 5.6.2.4 QoS SU or End Point B List Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > SU or End Point B List. By default, the table does not have any entry. User can configure the Wireless MAC Address of the SU or End Point B here and associate the QoS Class that is to be used for that particular SU or End Point B. Tsunami® 8100 Series - Software Management Guide 95

Advanced Configuration Figure 5-50 QoS SU or End Point B List Entries 2. If an SU or End Point B is not in the list and is associated, the default QoS class configuration is applied. Adding a New SU or End Point B 1. Navigate to ADVANCED CONFIGURATION > QoS > SU or End Point B List. The QoS SU or End Point B Entries screen appears. 2. Click Add to add a new entry. The following QoS SU or End Point B Table Add Row screen appears. Figure 5-51 QoS SU or End Point B Table Add Row 3. Specify the Wireless Mac Address of the SU or End Point B, Class Name, Comment and Entry Status and click Add. Previously defined Class Name can be viewed in the Class Name drop-down box. : • QoS SU Entries configuration can be done locally or through a RADIUS Server. • Local configuration takes priority over RADIUS Based QoS configuration. • RADIUS Configuration is applicable only when the RADIUS MAC ACL Status is enabled on the BSU. • When the link is down, the RADIUS configuration is lost. 5.6.3 QoS Configuration for a Management Station As stated previously, the QoS feature enables prioritization of traffic and allocation of the available bandwidth based on that prioritization. The system is designed in such a way that higher priority traffic preempts lower priority traffic, keeping lower priority traffic on hold until higher priority traffic finishes. This mechanism ensures that the available bandwidth is always given first to the higher priority traffic; if all the bandwidth is not consumed, the remaining bandwidth is given to the lower priority traffic. If QoS is not properly configured, the system becomes difficult to access in heavily loaded networks. One of the side effects of this misconfiguration is ping time-out, which is usually interpreted as a disconnection of the pinged node. However, with the correct QoS configuration, every node in the network can be reached at any point of time. Tsunami® 8100 Series - Software Management Guide 96

Advanced Configuration The following configuration instructions explain how to configure the system so that configuration parameters can always be changed, and ping requests and responses get higher priority in order to show the actual connectivity of the pinged node. The configuration suggested here assumes that the whole network is managed from a single work station, called the management station. This station can be connected anywhere in the network, and can be recognized by either its IP address, or by its MAC Ethernet address if the network uses DHCP. In this configuration, any traffic coming from or going to the management station is treated as management traffic. Therefore, the management station should be used only for configuration of the Quick Bridge nodes in the network and to check connectivity of the nodes, but it should not be used for any throughput measurements. : While this QoS configuration is used, the TCP or UDP throughput should not be measured from the management station. Step 1: Add Packet Identification Rules To recognize management traffic, the system needs to recognize ARP requests or responses and any traffic coming from or going to the management station. A. Confirm the Attributes of the Existing ARP PIR The default QoS configuration contains the PIR called “ARP,” which recognizes ARP requests or responses by the protocol number 0x0806 in the Ethernet Type field of the Ethernet packet. Confirm that the ARP PIR parameters are correct, as follows: 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. 2. Click Details corresponding to the ARP PIR. 3. Confirm the following attributes: • Rule Name: ARP • Status: Enable • Enable Ether Type Rule: Yes (checkbox is selected) — Ether Type: DIX-Snap — Ether Value: 08:06(hex) B. Create New PIRs to Recognize Management Traffic To recognize the traffic coming from or going to the management station, the system must contain two additional PIRs: one with either the destination IP address or the destination MAC address equal to the management station’s IP or MAC address, and another with either the source IP address or the source MAC address equal to the management station’s IP or MAC address. The following examples explain PIR rules based on the IP Address of the Management Station. 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR list > IP Address Entries. 2. Click Add. The screen for adding the Management Station's IP Address appears. Enter proper IP Address, Subnet mask as 255.255.255.255, Entry status as Enable and then click Add. This adds the Management Station’s IP details in the IP Address Entries of the PIR List. 3. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. 4. Add PIR Rule for Source IP Address. a. Click Add. The screen for adding the New PIR Rule appears. Enter the PIR Rule Name as “Management Station SRC IP”, Entry status as Enable and click Add. This adds the new PIR rule in the PIR List. By default, no classification rules are applied. b. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. Click Details for “Management Station SRC IP” PIR rule. This displays all the classification rule details for this particular rule. Tsunami® 8100 Series - Software Management Guide 97

Advanced Configuration c. Click Add that corresponds to Source IP Address Entries. This displays a screen for referring the Management Station’s IP Address. New Entry Table displays all the IP Address Entries of the PIR List. Select the option button corresponding to the Management Station and then click Add. This adds the IP Address of the Management Station to the Existing Entries. Click Back and the new entry appears in the Source IP Address Entries Table. 5. Add PIR Rule for Destination IP Address. a. Click Add. This displays a screen for adding the New PIR Rule. Enter the PIR Rule Name as “Management Station DST IP”, Entry status as Enable and then click Add. This adds the new PIR rule in the PIR List. By default, no classification rules are applied. b. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. Click Details corresponding to the “Management Station DST IP” PIR rule. This displays the classification rule details for this particular rule. c. Click Add corresponding to Destination IP Address Entries. This displays a screen for referring the Management Station’s IP Address. New Entry Table displays all the Entries of the IP Address Entries of the PIR List. Select the option button corresponding to the Management Station and click Add. This adds the IP Address of the Management Station to the Existing Entries. Click Back and the new entry appears in the Destination IP Address Entries Table. Step 2: Add Service Flow Classes To handle management traffic, the system needs two Service Flow Classes: one for uplink traffic and one for downlink traffic. 1. Configure the Downlink Service Flow. a. Navigate to ADVANCED CONFIGURATION > QoS > SFC list. b. Click Add. c. Enter the following parameters: • Service Flow Name: DL-Management • Scheduler Type: RtPS • Traffic Direction: Downlink • MIR: 1000 • CIR: 1000 • Max Latency: 20 • Tolerable Jitter: 10 • Priority: 7 • Max Messages in Burst: 16 • Entry Status: Enable d. Click Add. The DL-Management Service Flow is added to the QoS SFC List. 2. Configure the Uplink Service Flow. a. Navigate to ADVANCED CONFIGURATION > QoS > SFC list. b. Click Add. c. Enter the following parameters: • Service Flow Name: UL-Management • Scheduler Type: RtPS • Traffic Direction: Uplink • MIR: 1000 • CIR: 1000 • Max Latency: 20 • Tolerable Jitter: 10 • Priority: 7 Tsunami® 8100 Series - Software Management Guide 98

Advanced Configuration • Max Messages in Burst: 16 • Entry Status: Enable d. Click Add. The UL-Management SF is added to the QoS SFC List. NOTE: The input and output bandwidth limits set on the End Point A or BSU or on the End Point B or SU are used for limiting aggregate bandwidth used by the SU or End Point B. These limits override any limit imposed by MIR in the SFC. Therefore, these limits should be set to at least 1000 kbps (MIR values in UL-Management and DL-Management SFCs). Step 3: Configure QoS Classes Finally, the DL-Management SFC and UL-Management SFCs created in Step 2 must be added to each QoS Class used by the Quick Bridge network. Additionally, within the QoS class, these SFC must have the three PIRs mentioned in Step 1 associated with them. 1. Add SFCs to QoS Class. a. Navigate to ADVANCED CONFIGURATION > QoS > Class list. b. Click Details corresponding to the first class (Unlimited Best Effort) you wish to modify. c. Under the QoS Class Service Flow, click Add. d. Configure the following parameters, and click Add. This adds the New SFC & PIR relation to the QoS Class. • Service Flow Name: DL-Management • PIR Rule Name: ARP • PIR Priority: 63 • Entry Status: Enable. e. Again click Add under the QoS Class Service Flow Details. f. Configure the following parameters and click Add. This adds the New SFC & PIR relation to the QoS Class. • Service Flow Name: UL-Management • PIR Rule Name: ARP • PIR Priority: 63 • Entry Status: Enable 2. Add PIRs to SFCs within the QoS Class. a. Navigate to ADVANCED CONFIGURATION > QoS > Class list. b. Click Details corresponding to the first class (Unlimited Best Effort) you wish to modify. c. Under the QoS Class Service Flow Details, click Details corresponding to the DL-Management Service Flow. d. Under the QoS Class PIR Details heading, click Add. e. Add the Management Station DST IP PIR to this Service Flow by configuring the following parameters: • PIR Rule Name: Management Station DST IP • PIR Priority: 63 • Entry Status: Enable f. Click Add. This PIR is added to the first Qos Class (Unlimited Best Effort) Service Flow’s (DL-Management) list. g. Add the Management Station SRC IP PIR to this Service Flow by configuring the following parameters: • PIR Rule Name: Management Station SRC IP • PIR Priority: 63 • Entry Status: Enable h. Return to the Class List and repeat steps 2 - 7 for the UL-Management Service Flow in this class. Tsunami® 8100 Series - Software Management Guide 99

Advanced Configuration 5.7 RADIUS Based SU QoS Configuration RADIUS based QoS configuration enables you to configure QoS parameters on a SU through RADIUS Server. This way of configuring QoS parameters, reduces the task of manually configuring QoS parameters on each SU available on the network. Explained below is the process followed to configure QoS parameters on a SU from a RADIUS Server. Figure 5-52 RADIUS Based QoS Configuration To establish a connection with the BSU, the SU sends a registration request to BSU. On receiving the registration request, the BSU sends an Access request along with the SU MAC address, to the RADIUS Server. The RADIUS Server then checks the authentication of the user. If it is an authenticated user, it sends an Access-Accept response along with Vendor assigned QoS parameter’s value to the BSU. On receiving the response, the BSU sends the response to the SU. The received QoS parameters are then applied on the SU. Tabulated below are the vendor specific attributes: Name of the attribute Vendor Attribute Attribute Value Assigned Format Attribute Number QoS Class Index 34 Decimal 1 - 8 QoS Class SU Table Status 35 Decimal 1 - Enable / 2 - Disable : • RADIUS Based QoS configuration takes priority over Local QoS configuration. • When the link is down, the configuration received from the RADIUS is lost. Tsunami® 8100 Series - Software Management Guide 100

Advanced Configuration 5.8 VLAN (Bridge Mode Only) The Virtual Local Area Network (VLAN) feature helps in logical grouping of network host on different physical LAN segments, which can communicate with each other as if they are all on the same physical LAN segment. With VLANs, you can conveniently, efficiently, and easily manage your network in the following ways: • Define groups • Reduce broadcast and multicast traffic to unnecessary destinations - Improve network performance and reduce latency • Increase security - Secure network restricts members to resources on their own VLAN The SUs 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, • 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 MANs (Metropolitan Area Networks) or intranets • Provides customer traffic isolation at Layer 2 within a service provider network : VLAN can be configured in Bridge Mode only. 5.8.1 System-Level VLAN Configuration To configure system-level VLAN parameters, navigate to ADVANCED CONFIGURATION > VLAN. The VLAN configuration screen appears. Figure 5-53 System-Level VLAN Configuration 1. VLAN Status: This parameter is used to either enable or disable VLAN feature on the device. By default, this parameter is disabled. To enable VLAN, select the VLAN Status box. If VLAN status is enabled, it indicates that locally configured VLAN parameters will be applied on the device. If VLAN status is disabled, it indicates that the device is open for remote VLAN configuration. 2. Management VLAN Id: This parameter enables the user to configure VLAN Id for management frames (SNMP, ICMP, Telnet and TFTP). The stations that manage the device must tag the management frames with the management VLAN Id. By default, the Management VLAN Id is set to -1 which indicates no tag is added to the management frame. To set VLAN tag to the management frame, enter a value ranging from 1 to 4094. Tsunami® 8100 Series - Software Management Guide 101

Advanced Configuration : Before setting the Management VLAN Id, make sure that the station that manages the device is a member of the same VLAN; else, your access to the device will be lost. 3. Management VLAN Priority: This parameter is used to set IEEE 802.1p priority for the management frames. By default, the priority is set to 0. To set the VLAN priority, enter a value ranging from 0 to 7. 4. Double VLAN (Q in Q) Status: Q in Q (also called as Double VLAN or Stacked VLAN) mechanism expands the VLAN space by tagging the tagged packets, thus producing a “double-tagged” frame. The expanded VLAN space allows the service provider to provide certain services, such as Internet access on specific VLANs for specific customers, and still allows the service provider to provide other types of services for their other customers on other VLANs. By default, Double VLAN is disabled on the device. To enable, select Enable from the Double VLAN (Q in Q) Status box and click OK. : • If Double VLAN (Q in Q) Status is enabled, device expects Double VLAN tagged packet in DownLink Direction. Management can be accessed with single VLAN/Double VLAN based on the management VLAN ID configured. • Only SU, End Point A and End Point B support Double VLAN (Q in Q) feature. 5. Service VLAN TPID: The Tag Protocol Identifier (TPID) helps to identify the frame as VLAN tagged frame. By default the Service VLAN TPID is set to 0x8100. To interwork with few vendor devices that set the TPID to 0x9100, the device allows the user to configure Service VLAN TPID as 0x9100. In this case, when a QinQ packet goes out of the device, the Ether type of outer VLAN tag is changed to 0x9100. 6. Service VLAN Id: This parameter enables the user to configure outer/service provider VLAN ID for the data frames. By default, the Service VLAN ID is set to -1 which indicates no outer/service VLAN tag is added to the data frame. To set VLAN tag to the frame, enter a value ranging from 1 to 4094. : When Double VLAN is enabled on the device, the Service VLAN ID should not be set to -1. 7. Service VLAN Priority: This parameter is used to set IEEE 802.1p priority in outer/service VLAN tag for the data frames. By default, the priority is set to 0. To set the VLAN priority, enter a value ranging from 0 to 7. 5.8.2 Ethernet VLAN Configuration You can configure VLAN on the ethernet interface(s) by using any one of the following VLAN Modes: 1. Transparent Mode 2. Access Mode 3. Trunk Mode 5.8.2.1 Transparent Mode Transparent mode can be configured in a BSU, SU and End Point devices. This mode is equivalent to NO VLAN support and is the default mode. It is used to connect VLAN aware or unaware networks. In this mode, the device transfers both tagged and untagged frames received on the Ethernet or WORP interface. To configure the Ethernet interface of the device in VLAN Transparent Mode, navigate to ADVANCED CONFIGURATION > VLAN > Ethernet. The VLAN Ethernet Configuration screen appears: Tsunami® 8100 Series - Software Management Guide 102

Advanced Configuration Figure 5-54 Transparent Mode Tabulated below is the table which explains the method to configure the device in Transparent mode: Parameters Description Interface Displays the name of the Ethernet interface. VLAN Mode Select the VLAN mode as Transparent. : When the device is configured in Double VLAN mode, do not configure the Ethernet interface of the device in Transparent Mode. Click OK and then COMMIT. : Wireless Interface of the device will always be in transparent mode. There is no support provided to edit the VLAN parameters of the wireless interface. 5.8.2.2 Access Mode Access Mode can be configured in a SU, End Point A and End Point B. This mode is used to connect VLAN aware networks with VLAN unaware networks. The ingress untagged traffic received on the Ethernet interface are tagged with the configured Access VLAN Id and Access VLAN priority before forwarding to the WORP interface. Similarly all egress tagged frames with specified VLAN Id are untagged at the Ethernet interface and then forwarded. Based on the Management VLAN ID configuration, both tagged and untagged management frames can access the device from the WORP interface. However, only untagged management frames can access the device from the Ethernet Interface; the tagged frames are dropped. To configure the Ethernet interface of the device in Access Mode, navigate to ADVANCED CONFIGURATION > VLAN > Ethernet. The VLAN Ethernet Configuration screen appears: Tsunami® 8100 Series - Software Management Guide 103

Advanced Configuration Figure 5-55 Access Mode Tabulated below is the table which explains the method to configure the device in Access Mode: Parameter Description Interface Displays the name of the Ethernet interface. VLAN Mode Select the VLAN mode as Access and click OK. Access VLAN Id Enter the Access VLAN Id in the Access VLAN Id box. The untagged data frames received at the Ethernet interface are tagged with this configured VLAN Id and then forwarded to the WORP interface. By default, the Access VLAN Id is set to -1 which indicates no tag is added to the data frame. To set Access VLAN tag to the data frame, enter a value ranging from 1 to 4094. : When Double VLAN is enabled on the device, the Access VLAN ID should not be set to -1. Access VLAN Priority This parameter is used to set IEEE 802.1p priority for the data frames. By default, the priority is set to 0. To set the Access VLAN priority, enter a value ranging from 0 to 7. Click OK and then COMMIT. 5.8.2.3 Trunk Mode Trunk Mode can be configured in a BSU, SU, End Point A and End Point B. This mode is used to connect VLAN aware networks with VLAN aware networks. In the Trunk mode, the Ethernet interface of the device forwards only those tagged frames whose VLAN Id matches with a VLAN Id present in the trunk table. If the device receives untagged frames and the Allow Untagged Frames functionality is disabled, then the untagged packets are dropped. If the Allow Untagged Frames functionality is enabled, then functionality varies based on the device: • In case of a BSU, the untagged packets are forwarded to the destination. • In case of a SU, End Point A and End Point B, the device behaves as in Access Mode for untagged traffic. The untagged frames are tagged with the configured Port VLAN ID and forwarded to the destination. Tsunami® 8100 Series - Software Management Guide 104

Advanced Configuration : Mixed VLAN Mode = Trunk Mode + Allow Untagged Frames + Port VLAN ID To configure the Ethernet interface of the device in Trunk mode, navigate to ADVANCED CONFIGURATION > VLAN > Ethernet. The VLAN Ethernet Configuration screen appears: Figure 5-56 Trunk Mode (BSU) Figure 5-57 Trunk Mode (SU/End Point A/End Point B) Tabulated below is the table which explains the method to configure the device in Trunk Mode: Parameter Description Interface Displays the name of the Ethernet interface. VLAN Mode Select the VLAN Mode as Trunk. Tsunami® 8100 Series - Software Management Guide 105

Advanced Configuration Parameter Description Allow Untagged Select Enable or Disable. By default, it is disabled. Frames • Disable: If this option is selected, the Ethernet interface forwards only tagged frames whose VLAN Id matches with a VLAN ID present in trunk table. • Enable: - In case of a BSU, when Allow Untagged Frames is enabled, the Ethernet interface of the device forwards the data packets as-is. - In case of a SU/End Point A/End Point B, when Allow Untagged Frames is enabled, the device behaves as in Access mode. Click OK. Port VLAN ID Enter the Port VLAN ID in the Port VLAN ID box. The untagged data frames received at the Ethernet interface are tagged with this port VLAN Id and then forwarded to the destination interface. By default, the Port VLAN Id is set to -1 which indicates no tag is added to the data frame. To set Port VLAN tag to the data frame, enter a value ranging from 1 to 4094. : • Applicable only on a SU, End Point A and End Point B. • When Double VLAN is enabled on the device, the Port VLAN ID should not be set to -1. • The configured Port VLAN Id should not exist in the Trunk table. Port VLAN Priority This parameter is used to set IEEE 802.1p priority for the data frames. By default, the priority is set to 0. To set the Port VLAN priority, enter a value ranging from 0 to 7. : Applicable only to SU and End Point devices. After configuring the required parameters, click OK and then COMMIT. Add VLAN IDs to Trunk Table To add VLAN IDs to the trunk table, 1. Click Add in the VLAN Ethernet Configuration screen. The VLAN Trunk Table Add Row screen appears. Figure 5-58 Add VLAN IDs to Trunk Table Tsunami® 8100 Series - Software Management Guide 106

Advanced Configuration Tabulated below is the table which explains the method to add VLAN IDs to Trunk Table: Parameter Description Trunk Id Enter VLAN ID in the Trunk Id box. Entry Status This parameter indicates the status of each VLAN Trunk Id entry. By default, the Trunk Id is enabled. To disable, select Disable from the Entry Status box. 2. Click Add. 3. To save and apply the configured parameters on the device, click COMMIT. : You can configure a maximum of 256 trunk VLAN Ids in a BSU and End Point A device, and 16 VLAN Ids in a SU and End Point B device. 5.9 RADIUS Based SU VLAN Configuration RADIUS based VLAN configuration enables you to configure VLAN parameters on a SU through RADIUS Server. This way of configuring VLAN parameters, • Reduces the task of manually configuring VLAN parameters on each SU available on the network • Allows SU to remain on the same VLAN as it moves across the network Explained below is the process followed to configure VLAN parameters on a SU from a RADIUS Server. Figure 5-59 RADIUS Based VLAN Configuration To establish a connection with the BSU, the SU sends a registration request to BSU. On receiving the registration request, the BSU sends an Access request along with the SU MAC address, to the RADIUS Server. The RADIUS Server then checks the authentication of the user. If it is an authenticated user, it sends an Access-Accept response along with Vendor assigned VLAN parameter’s value to the BSU. On receiving the response, the BSU sends the response to the SU. The received VLAN parameters are then applied on the SU. Tsunami® 8100 Series - Software Management Guide 107

Advanced Configuration Tabulated below are the vendor specific attributes: Name of the attribute Vendor Attribute Attribute Value Assigned Format Attribute Number SU_VLAN_MAC 3 MacAddr SU Mac Address VLAN_ETH1 Vlan Mode 4 Decimal 1 -Transparent Mode 2 - Trunk Mode / 3 - Access Mode SU_VLAN_Name 5 String SU VLAN Name VLAN_ETH1 Access VLAN ID 6 Decimal 1 - 4095 VLAN_ETH1 Access Vlan Priority 7 Decimal 0 - 7 Management VLAN ID attribute 8 Decimal 1 - 4095 Management VLAN Priority 9 Decimal 0 - 7 VLAN_ETH1 TrunkID 1 … 16 10 … 25 Decimal 1 - 4095 SU_VLAN_Table_Status 26 Decimal 1 - enable / 2 - disable / 3 - delete Service Vlan Id (Q-inQ) 32 Decimal 1 - 4095 Service Vlan Priority (Q-inQ) 33 Decimal 0 - 7 QoS Class Index 34 Decimal 1 - 8 QoS Class SU Table Status 35 Decimal 1 - Enable / 2 - Disable VLAN_ETH2 Vlan Mode 40 Decimal 1 - Transparent Mode 2 - Trunk Mode / 3 - Access Mode VLAN_ETH2 Access Vlan Id 41 Decimal 1 - 4095 VLAN_ETH2 Access Vlan Priority 42 Decimal 0 - 7 VLAN_ETH2 TrunkID 1 … 16 43 … 58 Decimal 1 - 4095 Double Vlan (Q-in-Q) Status 59 Decimal 1 - Enable / 2 - Disable Service Vlan TPID (Q-inQ) 60 Decimal 1 - InnerTag / 2 - Outer Tag VLAN_ETH1_Port_Vlan_Id 61 Decimal 1 - 4095 VLAN_ETH1_Port_Vlan_Pri 62 Decimal 0 - 7 VLAN_ETH1_Allow_Untag_Frames 63 Decimal 1 - Enable / 2 - Disable VLAN_ETH2_Port_Vlan_Id 64 Decimal 1 - 4095 VLAN_ETH2_Port_Vlan_Pri 65 Decimal 0 - 7 VLAN_ETH2_Allow_Untag_Frames 66 Decimal 1 - Enable / 2 - Disable Tsunami® 8100 Series - Software Management Guide 108

Advanced Configuration : • RADIUS Configuration is applicable only when the VLAN Status is disabled on the SU. • Local VLAN configuration takes priority over RADIUS Based VLAN configuration. • When the link is down, the configuration received from the RADIUS is lost. 5.10 Filtering (Bridge Only) Filtering is useful in controlling the amount of traffic exchanged between the wired and wireless networks. By using filtering methods, we can restrict any unauthorized packets from accessing the network. Filtering is available only in bridge mode. The various filtering mechanisms supported by the device are as follows: • Protocol Filter • Static MAC Address Filter • Advanced Filtering • TCP/UDP Port Filter • Storm Threshold Filter Filters get activated only when they are globally enabled on the device. To apply/configure global filters on the device, navigate to ADVANCED CONFIGURATION > Filtering. The Filtering screen appears. Figure 5-60 Filtering Tabulated below is the table which explains Filtering parameters and the method to configure the configurable parameter(s): Parameter Description Global Filter Flag By default, Global Filtering is disabled meaning which no filters are applied on the device. To apply filters on the device, enable the Global Filter Flag. Please note that if Global Filter Flag is not enabled on the device, then none of the filters can be applied on the device. Tsunami® 8100 Series - Software Management Guide 109

Advanced Configuration Parameter Description STP/LACP Frames This parameter allows you to either Block or Passthru STP/LACP frames on the network. • Passthru: By allowing the STP/LACP frames, any loops that occurs within a network can be avoided. If configured to Passthru, the STP/LACP frames in the system are bridged. • Block: When blocked, the STP/LACP frames encountered on a network are terminated at bridge. By default, STP/LACP frames are allowed on the network. : STP or LACP Frame Status will block or passthru the frames destined to IEEE 802.1D and 802.1Q reserved MAC address (01:80:C2:00:00:00 to 01:80:C2:00:00:0F). After configuring the required parameters, click OK and then COMMIT. 5.10.1 Protocol Filter The Protocol Filter blocks or forwards packets based on the protocols supported by the device. To configure Protocol Filter on the device, navigate to ADVANCED CONFIGURATION > Filtering > Protocol Filter. The Protocol Filter screen appears: Tsunami® 8100 Series - Software Management Guide 110

Advanced Configuration Figure 5-61 Protocol Filter Tsunami® 8100 Series - Software Management Guide 111

Advanced Configuration Tabulated below is the table which explains Protocol Filter parameters and the method to configure the configurable parameter(s): Parameter Description Filtering Control This parameter is used to configure the interface on which filtering has to be applied. The filtering can be applied on any of the following interfaces: • Ethernet: Packets are examined at the Ethernet interface. • Wireless: Packets are examined at the Wireless interface. • All Interfaces: Packets are examined at both Ethernet and Wireless interface. By default, the Filtering Control is set to Disable, meaning which Protocol Filters are disabled on all the interfaces. : In addition to enabling Filtering Control, the Global Filter Flag should also be enabled for the filter to take effect. Filtering Type 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: • Block: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are blocked. • 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. 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 Description Protocol Name Represents the Protocol name. The system throws an error when you try to edit the name of a default protocol. Protocol Number 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® 8100 Series - Software Management Guide 112

Advanced Configuration Entry Status Set the entry status as either Enable, Disable or Delete. • Enable: Enables filter status on a protocol. • Disable: Disables filter status on a protocol. • Delete: Deletes a protocol entry from the Protocol Filter Table. : System-defined default protocols cannot be deleted. 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. Figure 5-62 Add User-defined Protocols Enter details for all the required parameters and click Add. : 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® 8100 Series - Software Management Guide 113

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 Prevent two specific PCs from communicating Configure the following settings to prevent the wired PC and wireless PC1 from communicating: • 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 Result: Traffic between the wired PC and wireless PC1 is blocked. wireless PC2 and PC3 can still communicate with the wired PC. 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: • 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 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). 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: • 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 Tsunami® 8100 Series - Software Management Guide 114

Advanced Configuration Result: The device blocks all traffic between the wired PC and all wireless PCs. Prevent a wireless PC from communicating with the wired network Configure the following settings to prevent wireless PC 3 from communicating with any device on the Ethernet: • 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 Result: The device blocks all traffic between wireless PC 3 and the Ethernet network. 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: Figure 5-63 Static MAC Address Filter Click Add in the Static MAC Address Filter screen. The Static MAC Address Filter Add Row screen appears. Figure 5-64 Static MAC Address Filter Add Row Tsunami® 8100 Series - Software Management Guide 115

Advanced Configuration Tabulated below is the table which explains Static MAC Address Filter parameters and the method to configure the configurable parameter(s): Parameter Description Wired MAC Address Specifies the MAC address of the device on the wired network that is restricted from communicating with a device in the wireless network. 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 in the wired network. Wireless MAC Mask Specifies the range of MAC address to which this filter is to be applied. Comment Specifies the comment associated with Static MAC Filter table entry. Status Specifies the status of the newly created filter. Click Add and then COMMIT. : • A maximum of 200 MAC address filters can be added. • 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-65 Advanced Filtering Tsunami® 8100 Series - Software Management Guide 116

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 Description Protocol Name Represent the protocol name. By default, Advanced Filtering is supported on the following 5 default protocols: • Deny IPX RIP • Deny IPX SAP • Deny IPX LSP • Deny IP Broadcasts • Deny IP Multicasts Direction Represents the direction of an IP Protocol traffic that needs to be filtered. The directions that can be filtered are, • Ethernet to wireless • Wireless to ethernet • Both Entry Status If enabled, then filtering is applied on the IP protocol else not applied. : • 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. 5.10.3.1 Edit Advanced Filtering Table Entries To edit Advanced Filtering table protocols, click Edit in the Advanced Filtering screen. The Advanced Filtering - Edit Entries screen appears. Tsunami® 8100 Series - Software Management Guide 117

Advanced Configuration Figure 5-66 Advance Filtering- Edit Entries Modify the IP protocol traffic direction that needs to be filtered, and the filtering status for the desired IP Protocol. 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® 8100 Series - Software Management Guide 118

Advanced Configuration Figure 5-67 TCP/UDP Port Filter 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. 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 Description Protocol Name 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. Port Number 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, • Only Ethernet • Only Wireless • All Interfaces Entry Status Set the entry status as either Enable, Disable or Delete. • 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 attempt to delete default entries, the device throws an error. Tsunami® 8100 Series - Software Management Guide 119

Advanced Configuration 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 Port Number Port Type Filter Interface Entry Status (Enable/Disable) NETBIOS Name Service 137 UDP Ethernet Enable 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-68 Add User-defined TCP/UDP Protocols Provide details for all the parameters and click Add. To apply the configured parameters, click COMMIT. : • The TCP/UDP filtering operation is allowed only when the Global Flag and Filter Control options are enabled. • A maximum of 64 TCP/UDP Port Filter entries can be added to the table, out of which 7 are default entries. 5.10.5 Storm Threshold Filter 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. 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. Tsunami® 8100 Series - Software Management Guide 120

Advanced Configuration Figure 5-69 Storm Threshold Filter Tabulated below is the table which explains Storm Threshold Filter parameters and the method to configure the configurable parameter(s): Parameter Description Interface 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. Multicast Threshold 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. Broadcast Threshold 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. 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 a 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). Tsunami® 8100 Series - Software Management Guide 121

Advanced Configuration The following rules apply to Intra Cell Blocking Groups: • A SU can be assigned to more than one group. • A SU that has not been assigned to any group cannot communicate to any other SU connected to the same or different BSU. 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 SU2 SU6 SU8 SU4 SU3 SU1 SU9 SU5 SU8 SU7 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-70 Intra Cell Blocking This screen is classified into two categories: Intra Cell Blocking and Security Gateway. Tabulated below are the configuration details. 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. Tsunami® 8100 Series - Software Management Guide 122

Advanced Configuration Parameter Description 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 a 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 a 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: Figure 5-71 WORP Intra Cell Blocking Group Table Tsunami® 8100 Series - Software Management Guide 123

Advanced Configuration 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 SU’s MAC address and assign them to the groups. A maximum of 250 SUs can be added 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: Figure 5-72 WORP Intra Cell Blocking MAC Table To add MAC addresses, click Add. The following screen appears. Figure 5-73 WORP Intra Cell Blocking MAC Table Add Row Tsunami® 8100 Series - Software Management Guide 124

Advanced Configuration Tabulated 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 SU’s MAC address. Group ID’s 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. 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: Figure 5-74 DHCP Pool Each pool entry comprises the following tabulated information: Parameter Description Interface Specifies the interface type, that is, Bridge or Routing (Ethernet and Wireless). Start IP Address and Specifies the start and end IP address of the addresses to be added to the pool. End IP Address Delete Allows you to delete a pool entry. Tsunami® 8100 Series - Software Management Guide 125

Advanced Configuration : A maximum of five pool entries can be added 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: Figure 5-75 DHCP Pool Table Add Row 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-76 DHCP Server Tsunami® 8100 Series - Software Management Guide 126

Advanced Configuration Tabulated below is the table which explains DHCP Server parameters and the method to configure the configurable parameter(s): 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 Specifies the interface for which the DHCP Server functionality shall be configured. That is Bridge or Ethernet/Wireless in case of Routing mode. Net Mask 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. Default Lease Time 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 forwards DHCP requests to the configured DHCP Server. A maximum of 5 DHCP Servers can be configured. 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 are enabled. To view and configure DHCP Relay Server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Relay > Relay Server. The DHCP Relay screen appears: Tsunami® 8100 Series - Software Management Guide 127

Advanced Configuration Figure 5-77 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: Figure 5-78 DHCP Relay Server Add Row 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 vise-verse. 5.12 IGMP Snooping : IGMP Snooping is applicable only in a Bridge Mode. Proxim’s 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: Tsunami® 8100 Series - Software Management Guide 128

Advanced Configuration Figure 5-79 IGMP Snooping Process The router forwards the IP multicast data to the BSU/End Point A. 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. 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: • 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. Tsunami® 8100 Series - Software Management Guide 129

Advanced Configuration : • Tsunami® devices supports only passive IGMP Snooping. • IGMP versions v1,v2 and v3 are supported. • The device can add a maximum of 64 Multicast groups in the Snooping table. To configure IGMP Snooping parameters, navigate to ADVANCED CONFIGURATION > IGMP Snooping. The following IGMP Snooping screen appears: Figure 5-80 IGMP Snooping Tabulated below is the table which explains IGMP Snooping parameters and the method to configure the configurable parameter(s): Parameter Description IGMP Snooping Status 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. IGMP Membership Represents the time after which the IGMP multicast group age-outs or elapses. It ranges Aging Timer from 135 to 635 seconds. The default Aging Timer is 260 seconds. IGMP Router Port Represents the time after which the IGMP Router port age-outs or elapses. It ranges from Aging Timer 260 to 635 seconds. The default Aging Timer is 300 seconds. IGMP Forced Flood 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. 5.13 Routing Mode Features This section provides an overview of all the features applicable in routing mode only. 5.13.1 Static Route Table The Static Route Table stores the route to various destinations in the network. When packets are to be routed, the routing table is referred for the destination address. Tsunami® 8100 Series - Software Management Guide 130

Advanced Configuration To configure the static routing table, navigate to ADVANCED CONFIGURATION > Network > Static Route Table. The Static Route Table screen appears. Figure 5-81 Static Route Table Tabulated below is the table which explains Static Route Table entries and the method to configure the configurable parameter(s): Parameter Description Static Route Status If Static Route Status is enabled, the packets are sent as per route configured in the static routing table. If disabled, forwards the packet to the default gateway. Destination Address Represents the destination IP address to which the data has to be routed. Subnet Mask Represents the subnet mask of the destination IP address to which the data has to be routed. Route Next Hop Represents the IP address of the next hop to reach the destination IP address. Next hop IP should belong to at least one of the subnets connected to the device. Admin Metric It is a metric that specifies the distance to the destination IP address, usually counted in hops. The lower the metric, the better. The metrics can range from 0 to 16. Entry Status If enabled, considers the packets for routing. If disabled, forwards the packet to the default gateway. Tsunami® 8100 Series - Software Management Guide 131

Advanced Configuration 5.13.1.1 Adding Static Route Entries Click Add in the Static Route Table screen.The following Static Route Table Add Row screen appears: Figure 5-82 Static Route Table Add Row Add the route entries and click Add and then COMMIT. : • A maximum of 256 routes can be added to the static route table. • The IP address of the Next Hop must be on the subnet of one of the device’s network interfaces. 5.13.2 Network Address Translation (NAT) : NAT is applicable only to a SU and an End Point B. The Network Address Translation (NAT) feature allows hosts on the Ethernet side of the SU or End Point B device to transparently access the public network through the BSU/End Point A device. All the hosts in the private network can have simultaneous access to the public network. The SU/End Point B device supports Network Address Port Translation (NAPT) feature, where all the private IP addresses are mapped to a single public IP address. The SU/End Point B device supports both dynamic mapping (allowing private hosts to access hosts in the public network) and static mapping (allowing public hosts to access hosts in the private network) are supported. 1. Static NAT: Static mapping is used to provide inbound access. The SU/End Point B maps the public IP address and its transport identifiers to the private IP address (local host address) in the local network. This is used to provide inbound access to a local server for hosts in the public network. Static port mapping allows only one server of a particular type. A maximum of 100 entries are supported in the static port bind table. 2. Dynamic NAT: In dynamic mapping, the SU/End Point B maps the private IP addresses and its transport identifiers to transport identifiers of a single Public IP address as they originate sessions to the public network. This is used only for outbound access. : • When NAT is enabled, the network on the wireless side of the device is considered public and the network on the Ethernet side is considered private. Tsunami® 8100 Series - Software Management Guide 132

Advanced Configuration • When NAT functionality is enabled, the DHCP Relay and RIP features are not supported. The DHCP Relay Agent and RIP must be disabled before enabling NAT. To configure NAT parameters, navigate to ADVANCED CONFIGURATION > Network > NAT. The following NAT screen appears: Figure 5-83 NAT Tabulated below is the table which explains NAT parameters and the method to configure the configurable parameter(s): Parameter Description Status This parameter is used to either enable or disable NAT on a SU or an End Point A. Dynamic Start Port Represents the start and end port sessions originated from private to public host. and Dynamic End Port By default, the Dynamic Start Port is configured to 1 and Dynamic End Port is configured to 65535. Configure the start and end port as desired. : Care should be taken to avoid overlap of Dynamic Port range and Static Port range. Port Forwarding This parameter is used to either enable or disable the Static NAT feature within different Status networks. It allows public hosts to access hosts in a private network. By default, it is disabled. After configuring the required parameters, click OK and then COMMIT. : • To enable Dynamic NAT, set the NAT Status to Enable. To enable Static NAT, set the NAT Status to Enable and the Port Forwarding Status to Enable. • NAT uses the IP address of the wireless interface as the Public IP address. Tsunami® 8100 Series - Software Management Guide 133

Advanced Configuration To add entries in the NAT Port Bind Table, navigate to ADVANCED CONFIGURATION > Network > NAT > Static Port Bind. The NAT Port Bind Table screen appears. Click Add in the NAT Port Bind Table screen. The following NAT Port Bind Table Add Row appears: Figure 5-84 NAT Port Bind Table Add Row Tabulated below is the table which explains the NAT Port Bind Table entries and the method to configure the configurable parameter(s): Parameter Description Local Address Enter the local IP Address of the host on the Ethernet (private) side of the SU/End Point B. Port Type Select the Port Type as: TCP, UDP, or Both. Start and End Port Represents the start and end port for transferring the data from public to private host. Number : Care should be taken to avoid overlap of Dynamic Port range and Static Port range. Entry Status If enabled, the data is transferred from the public network to the private host, on the specified ports. After configuring the required parameters, click ADD and then COMMIT. 5.13.2.1 Supported Session Protocols Certain applications require an Application Level Gateway (ALG) to provide the required transparency for an application running on a host in a private network to connect to its counterpart running on a host in the public network. An ALG may interact with NAT to set up state information, use NAT state information, modify application-specific payload, and perform the tasks necessary to get the application running across address realms. No more than one server of a particular type is supported within the private network behind the SU/End Point B. The following table lists the supported protocols with their corresponding default ALG's: S.No. Protocol Support Applications 1 H.323 H.323 ALG Multimedia Conferencing 2 HTTP Port Mapping for inbound connection Web Browser 3 TFTP Port Mapping for inbound connection Trivial file transfer 4 Telnet Port Mapping for inbound connection Remote login Tsunami® 8100 Series - Software Management Guide 134

Advanced Configuration S.No. Protocol Support Applications 5 IRC Port Mapping for inbound connection Chat and file transfer 6 AMANDA Port Mapping for inbound connection Backup and archiving 7 FTP FTP ALG File Transfer 8 PPTP PPTP ALG VPN related 9 SNMP SNMP ALG Network Management 10 DNS Port Mapping for inbound connection Domain Name Service 5.13.3 RIP Routing Information Protocol (RIP) is a dynamic routing protocol, which can be used to automatically propagate routing table information between routers. The device can be configured in RIPv1, RIPv2, or both while operating in Routing mode. When a router receives a routing update including changes to an entry, it updates its routing table to reflect the new route. RIP maintains only the best route to a destination. Therefore, whenever new information provides a better route, the old route information is replaced. : RIP is configurable only when the devices are in Routing Mode and Network Address Translation (NAT) is disabled. To configure RIP parameters, navigate to ADVANCED CONFIGURATION > Network > RIP. The following RIP screen appears: Figure 5-85 RIP By default, RIP is not enabled on the device. To enabled, select Enable and click OK. The RIP screen is updated with the following tabulated parameters:. Parameter Description Name Displays the interface type as either Ethernet 1, Ethernet 2, or Wireless. Status Enables you to either enable or disable RIP for a particular network interface. Tsunami® 8100 Series - Software Management Guide 135

Advanced Configuration Parameter Description Authorization Type Enables you to select the appropriate Authorization Type. This parameter is not applicable if RIP v1 is selected as the Version number. Authorization Key Enter the authorization key. This parameter is not applicable if RIP v1 is selected as the Version number. It is not applicable when the Authorization Type is set to None. Version Number Select RIP Version number from the Version Number list. Available options are V1, V2 and both. The default is V2. Direction You can enable RIP for both receiving and transmitting the data. To enable RIP only for Receiving, select Rx Only. To enable RIP for both receiving and transmitting, select Rx and Tx. After configuring the required parameters, click OK and then COMMIT. : • Authorization Type and Authorization Key are valid only for RIPV2 and both versions. • The maximum metric of a RIP network is 15 hops, that is, a maximum of 15 routers can be traversed between a source and destination network before a network is considered unreachable. • By default, a RIP router will broadcast or multicast its complete routing table for every 30 seconds, regardless of whether anything has changed. • RIP supports the split horizon, poison reverse and triggered update mechanisms to prevent incorrect routing updates being propagated. 5.13.4 PPPoE End Point (SU Only) Proxim’s SU devices support Point-to-Point Protocol over Ethernet (PPPoE) which is a network protocol for transmitting PPP frames over Ethernet. This feature is commonly used by Internet Service Providers (ISPs) to establish a Digital Subscriber Line (DSL) Internet service connection with clients. The Proxim’s SU devices support PPPoE only when they are configured in Routing Mode with NAT enabled. Also, the BSU should always operate in Bridge Mode. Figure 5-86 PPPoE Architecture Given below are the stages for a PPPoE client to establish link with the PPPoE server and then transfer PPP frames over Ethernet: Tsunami® 8100 Series - Software Management Guide 136

Advanced Configuration • Discovery and Session Stage: In this stage, to initiate a PPPoE session, the PPPoE client discovers a PPPoE server (called Access Concentrator). Once discovered, a session ID is assigned and a session is established. • Point-to-point Protocol (PPP) Stages: The PPP stage comprises the following sub-stages: 1. Physical Link: For sending and receiving PPP frames, the PPP driver calls the services of PPP Channels (used in connection with serial links). A PPP channel encapsulates a mechanism for transporting PPP frames from one machine to another and then the frames are forwarded on the physical Ethernet link. 2. Link Establishment: In this stage, Link Configuration Protocol (LCP) performs the basic setup of the link. As part of this setup, the configuration process is undertaken whereby the PPPoE client and the server negotiate and agree on the parameters on how data should be passed between them. Only when both the client and server come to an agreement, the link is considered to be open and will proceed to the Authentication stage. 3. Authentication: In this stage, LCP invokes an authentication protocol (PAP/CHAP/MS CHAP v2/EAP-MD5) when PPP is configured to use authentication. 4. Encryption: In this stage, both PPPoE client and server negotiate the encryption protocol configuration. Our device support MPPE as encryption protocol. MPPE is negotiated within option 18 in the PPP Compression Control Protocol (CCP). 5. Network Layer Protocol: After successful authentication, the link proceeds to the Network-Layer Protocol stage. In this stage, the specific configuration of the appropriate network layer protocol is performed by invoking the appropriate Network Control Protocol (NCP) such as IPCP. We support only IPCP Protocol as a part of NCP. Given below are the features supported by PPPoE client: • Preferred Server Configuration by using Access Concentrator Name/Service Name • PAP/CHAP/MSCHAP v2/EAP-MD5 Authentication Protocols • IP Configuration: Static IP/ PPPoE-IPCP • Echo Interval and Echo Failure to detect server unavailability • MPPE with stateful and stateless mode aligned with 40/56/128 bit encryption To configure PPPoE feature, 1. Navigate to ADVANCED CONFIGURATION > Network > PPPoE > PPPoE Client. The following PPPoE Client screen appears: Figure 5-87 PPPoE Client Status 2. By default, the PPPoE feature is disabled on the client. To enable, select Enable from Status drop-down box. 3. Next, click OK. Please note that a change in the PPPoE client status requires you to reboot the device. 4. On enabling the PPPoE client feature, the following screen appears: Tsunami® 8100 Series - Software Management Guide 137

Advanced Configuration Figure 5-88 PPPoE Client Configuration Tsunami® 8100 Series - Software Management Guide 138

Advanced Configuration 5. Tabulated below is the table which explains PPPoE client parameters and the method to configure the configurable parameter(s): Parameter Description Authentication PPPoE supports the following types of user authentication protocols that provide Protocol varying levels of security: • None: Represents that no authentication is required for transferring PPP frames over Ethernet between PPPoE client and server. • Password Authentication Protocol (PAP): PAP is an access control protocol used to authenticate client’s password on the server. The server requests a password from the client and sends the retrieved password to an authentication server for verification. As an authentication protocol, PAP is considered the least secure because the password is not encrypted in transmission. • Challenge Handshake Authentication Protocol (CHAP): CHAP is similar to PAP with several unique characteristics. Instead of requesting a password, the server sends a challenge message to the client. The challenge message is a random value. The client encrypts the challenge message with user's password and sends the combination back to the server. The server forwards the challenge/password combination to the authentication server. The authentication server encrypts the challenge with the user's password stored in the authentication database. If the user's response is a match, the password is considered authentic. CHAP uses the model of a shared secret (the user password) to authenticate the user. The use of CHAP is considered a moderately secure method of authentication. • Microsoft Challenge-Handshake Authentication Protocol version 2 (MSCHAP v2): MSCHAP V2 is a mutual authentication method that supports password-based user or computer authentication. During the MSCHAP v2 authentication process, both the client and the server prove that they have knowledge of the user's password for authentication to succeed. Mutual authentication is provided by including an authenticator packet returned to the client after a successful server authentication.This method is proprietary to the Microsoft mostly used in windows servers and client. • EAP-MD5: EAP-MD5 enables a server to authenticate a connection request by verifying an MD5 hash of a user's password. The server sends the client a random challenge value, and the client proves its identity by hashing the challenge and its password with MD5. By default, the authentication protocol is set to CHAP. You can configure the authentication protocol to the desired one and click OK. LCP Echo Interval To check the link connection, periodically the PPPoE client sends an LCP echo-request frame to the PPPoE server. If the PPPoE server respond to the echo-request by sending an echo-reply, then the connection is alive. To configure LCP Echo Interval, enter a time ranging from 5 to 300 seconds. By default, the echo interval is set to 30 seconds. Tsunami® 8100 Series - Software Management Guide 139

Advanced Configuration Parameter Description LCP Echo Failure This parameter indicates the maximum number of consecutive failures to receive the LCP echo-reply to consider the connection to be down. To configure LCP Echo Failure value, enter a a value ranging from 1 to 25. By default, the echo failure is set to 5. On a noisy wireless link, it is recommended to set this value to higher. Preferred Service Specifies the service which the PPPoE server (Access Concentrators) provides to the Name PPPoE client. Leave this parameter blank, if PPPoE client accepts any service offered by the PPPoE server. To specify the desired service name, enter the service name ranging from 1 to 32 characters. Access Concentrator Specifies Access Concentrator (PPPoE server) name. Name Leave this parameter blank, when PPPoE client can connect to any PPPoE server on the network. To connect to a desired PPPoE server, type the server name ranging from 1 to 32 characters. User Name and Before establishing a link, the PPPoE server first authenticates the PPPoE client based Password on the User Name and Password as shared by the service provider. Type the user name and password in the User Name and Password box respectively. You can type user name ranging from 4 to 32 characters and password ranging from 6 to 32 characters. : User Name and Password parameters are not applicable when the Authentication Protocol is configured as “None”. Tsunami® 8100 Series - Software Management Guide 140

Advanced Configuration Parameter Description MPPE Status : MPPE Status parameter is applicable only when the Authentication Protocol is configured as “MSCHAP v2”. Microsoft Point-to-Point Encryption (MPPE) is a protocol for transferring encrypted data over point-to-point links. The PPPoE client negotiates on the encryption parameters based on the MPPE Status configured. The MPPE Status can be configured as following: • Mandatory: When the MPPE status is configured as Mandatory, the PPPoE client negotiates the configured MPPE parameters with the PPPoE server. If the server does not agree to the parameters then the link will not be established. • Optional: When the MPPE status is configured as Optional, the link is established with or without encryption depending on the PPPoE server configuration. If the PPPoE server supports MPPE encryption then the PPPoE client agrees with the PPPoE server’s MPPE parameters and link gets established with encryption. If the PPPoE server does not support MPPE encryption then link gets established without encryption. • Disable: When the MPPE status is configured as Disable, then the PPPoE client does not agree to the MPPE parameters suggested by the PPPoE server. Configure the desired status and click OK. Stateless Encryption Mode : This parameter is applicable only when Authentication Protocol is configured as “MSCHAP v2” and MPPE Status is configured as “Mandatory”. When stateless encryption is negotiated, the session key changes for every packet transferred. In stateless mode, the sender must change its key before encrypting and transmitting each packet and the receiver must change its key after receiving, but before decrypting, each packet. When stateful encryption is negotiated, the PPPoE server and the client monitor the synchronization of MPP encryption engine on both the sides. When one of the peer detects that they are out of sync then the peer should transmit a packet with the coherency count set to 0xFF(a flag packet); the sender must change its key before encrypting and transmitting any packet and the receiver must change its key after receiving a flag packet, but before decrypting. To enable stateless encryption, select Enable. To enable stateful encryption, select Disable. : Enabling Stateless Encryption impacts throughput. It is useful to enable Stateless encryption when packet drops are more in the wireless link. Tsunami® 8100 Series - Software Management Guide 141

Advanced Configuration Parameter Description MPPE Key Length : This parameter is applicable only when Authentication Protocol is configured as “MSCHAP v2” and MPPE Status is configured as “Mandatory”. MPPE supports 40-bit, 56-bit and 128-bit encryption key length. To configure the desired key length, select a key length from the MPPE Key Length drop-down box. Link Status Indicates the status of the PPPoE link between the PPPoE client and server. The link can be in any of the following three stages: • Disconnected: No connection is established between PPPoE client and server. • Connecting: A connection attempt is in progress between PPPoE client and server. • Connected: Connection is established between PPPoE client and server. The Link Status can be viewed in Home Page. 6. After configuring the required parameters, click OK and then COMMIT. Reboot the device, if you have changed the PPPoE Status configuration. 5.13.5 IP over IP Tunneling Proxim’s point-to-multipoint and point-to-point devices support IP Tunnelling, which serves as a communication channel between two disjoint IP networks that do not have a native routing path to communicate with each other. To enable communication between two disjoint networks using IP Tunneling, the following steps are involved: 1. The tunnel entry point receives the IP packet (Sender Source IP + Recipient IP) sent by the original sender. IP Packet Sender Source IP Recipient IP 2. The tunnel entry point encapsulates the IP packet (Sender Source IP + Recipient IP) with the IP addresses of the tunnel endpoints. The tunneled packet (Sender Source IP + Recipient IP + Tunnel Entry Point IP + Tunnel Exit Point IP) is then forwarded to the tunnel exit point. Tunneled IP Packet (Inner IP Header) (Outer IP Header) Sender Source IP Recipient IP Tunnel Entry Point IP Tunnel Exit Point IP 3. On receiving the tunneled packet, the tunnel exit point removes the tunnel IP addresses and forwards the packet to the recipient. The inner IP header Source Address and Destination Address identify the original sender and recipient of the packet, respectively. The outer IP header Source Address and Destination Address identify the endpoints of the tunnel. The following figure shows an IP tunnel configuration using two end points. Tsunami® 8100 Series - Software Management Guide 142

Advanced Configuration Figure 5-89 An Example: Tunnel Configuration Lets say that the Computer with an IP address: 10.0.0.1 wants to communicate with the Computer with an IP address: 192.168.9.101. Since there is no native routing path between these two computers, the communication can happen via the tunnel. The SU1device with wireless IP address: 20.0.0.132 and SU2 device with wireless IP address: 30.0.0.132 are the end points of the tunnel, respectively. With IP tunneling, the tunnel entry point (SU1) encapsulates the tunnel end points IP addresses (20.0.0.132 + 30.0.0.132) with the sender IP addresses (10.0.0.1 + 192.168.9.101) before sending the data through the tunnel. When the tunnel exit point (SU2) receives traffic, it removes the outer IP header before forwarding the packet to the recipient. IP Packet Sender Source IP (10.0.0.1) Recipient IP (192.168.9.101) Tunneled IP Packet (Inner IP Header) (Outer IP Header) Sender Source IP Recipient IP Tunnel Entry Point IP Tunnel Exit Point IP (10.0.0.1) (192.168.9.101) (20.0.0.132) (30.0.0.132) : IP tunnel establishment does not involve any protocol message exchange. To setup an IP tunnel, the device has to be configured properly on both the ends. By following the steps below, the tunnel is automatically established. 1. Create a tunnel (Refer to Create a Tunnel) To create a tunnel as given in Figure 5-89, do the following: SU1 Configuration — Virtual IP Address = 50.0.0.1 — Local IP Address = 20.0.0.132 Tsunami® 8100 Series - Software Management Guide 143

Advanced Configuration — Remote IP Address = 30.0.0.132 SU2 Configuration — Virtual IP address = 50.0.0.2 — Local IP Address = 30.0.0.132 — Remote IP Address = 20.0.0.132 2. Add a Static Route for Remote IP Address of the tunnel (Refer to Static Route Table) • On SU1, add a static route for 30.0.0.xxx as next hop 20.0.0.1 • On SU2, add a static route for 20.0.0.xxx as next hop 30.0.0.1 3. Add a route for the pass-through traffic through the tunnel (Next Hop IP Address should be that of the tunnel interface). • On SU1, add a static route for 192.168.9.xxx as next hop 50.0.0.1 • On SU2, add a static route for 10.0.0.xxx as next hop 50.0.0.2 5.13.5.1 Create a Tunnel To create a Tunnel interface, 1. Navigate to ADVANCED CONFIGURATION > Network > IP Tunneling. The following IP Tunneling screen appears: Figure 5-90 IP Tunneling Status 2. By default, the IP Tunneling feature is disabled on the device. To enable, select Enable from the Tunneling Status drop-down box. 3. Next, click OK. 4. On enabling the IP Tunneling feature, the following screen appears: Figure 5-91 IP Tunneling Interfaces 5. Click Add, to create a new tunnel interface. The following Tunneling Table Add Row screen appears: Tsunami® 8100 Series - Software Management Guide 144

Advanced Configuration Figure 5-92 Adding a new Tunnel Interface 6. Tabulated below is the table which explains the parameters for creating a new tunnel: Parameter Description Name Represents the name of the tunnel interface. Type a name for the tunnel interface. Encapsulation The device supports two types of network tunnels: Method • ipip: A tunnelling protocol that allow only IP traffic over the tunnel. • gre (Generic Routing Encapsulation): A tunneling protocol that allows encapsulation of a wide variety of packet types in Internet Protocol (IP) packets, thereby creating a virtual point-to-point link. Select the tunnel type as either ipip or gre. Virtual IP Address Represents the virtual IP address of the tunnel interface. Enter the virtual IP address of the tunnel interface. Local IP Address Represents the IP address of the tunnel entry point. Select the IP address of the tunnel entry point from the available list of addresses. Remote IP Address Represents the IP address of the tunnel exit point. Type the IP address of the tunnel exit point. Please note that the Remote IP address should be routable. TTL TTL stands for Time to Live. This parameter enables to configure a fixed TTL value on the tunneled packets. The TTL value can be configured in the range 0 to 255. By default, the TTL value is set to 0 meaning that tunneled packets inherit the TTL value from the IP packet originated by the sender. Entry Status By using this parameter, a tunnel interface can be enabled or disabled. By default, it is enabled. To disable, select Disable. 7. Next, click Add. : • A maximum of 16 tunnels can be created on a device. Tsunami® 8100 Series - Software Management Guide 145

Advanced Configuration • The Maximum Transmission Unit (MTU) of the tunnel interface depends on the underlying interface. • It is advised that both PPPoE and the IP Tunneling feature do not function simultaneously on the device. • IP configuration of Ethernet and Wireless interface should NOT be in the same subnet of virtual IP addresses of tunnels. 5.13.5.2 View Existing Tunnels The IP Tunneling screen displays all the tunnels created on the device. The entries against each tunnel cannot be edited. However, the status of each tunnel entry can be modified. You can either enable, disable or delete a tunnel by selecting the desired one from Entry Status box in the IP Tunneling screen. Figure 5-93 IP Tunneling Interfaces Tsunami® 8100 Series - Software Management Guide 146

6 Management This chapter provides information on how to manage the device by using Web interface. It contains information on the following: • System • File Management • Services • Simple Network Time Protocol (SNTP) • Access Control • Reset to Factory • Convert QB to MP 6.1 System The System tab enables you to configure system specific information such as System Name, contact information of the person managing the device, and view system inventory and license information. 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 Tabulated below is the table which explains System parameters and the method to configure the configurable parameter(s): Tsunami® 8100 Series - Software Management Guide 147

Management Parameter Description System Up-Time This is a read-only parameter. It represents the operational time of the device since its last reboot. System Description This is a read-only parameter. It provides system description such as system name, firmware version and the latest firmware build supported. For example: Tsunami MP-8100-BSU-WD-v2.4.0 System Name Represents the name assigned to the device. You can enter a system name of maximum 64 characters. Email Represents the email address of the person administering the device. You can enter an email address of minimum 6 and maximum 32 characters. Phone Number Represents the phone number of the person administering the device. You can enter a phone number of minimum 6 and maximum 32 characters. Location Represents the location where the device is installed. You can enter the location name of minimum 0 and maximum 255 characters. GPS Longitude Represents the longitude at which the device is installed. You can enter a longitude value of minimum 0 and maximum 255 characters. GPS Latitude Represents the latitude at which the device is installed. You can enter a latitude value of minimum 0 and maximum 255 characters. GPS Altitude 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® 8100 Series - Software Management Guide 148

Management Figure 6-2 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 Tabulated below is the table which explains each of the parameters: Parameter Description Product Description Description about the device. Tsunami® 8100 Series - Software Management Guide 149

$Management Parameter Description Number of Radios The number of radios that the device is licensed to operate. Number of Ethernet The number of Ethernet interfaces supported by the device. Interfaces Radio 1 Allowed The operational frequency band supported by the device radio. Frequency Band Maximum Output The maximum output bandwidth limit of the device. It is represented in mbps. Bandwidth Maximum Input The maximum input bandwidth limit of the device. It is represented in mbps. Bandwidth : 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 The maximum cumulative bandwidth of the device, which is the sum of configured output Bandwidth 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 Represents the operational mode of the device, that is, BSU/SU/End Point A/End Point B. Modes of Radio1 Maximum SUs The maximum number of SUs that a BSU supports. Allowed MAC address of the The MAC address of the device. Device is 6.2 File Management 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.1 TFTP Server 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 download the SolarWinds TFTP server application from http://support.proxim.com. You can also download the latest TFTP software from SolarWinds Web site at http://www.solarwinds.net. While using TFTP server, ensure the following: • The upload or download directory is correctly set (the default directory is C:\TFTP-Root). • The required firmware file is present in the directory. • 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. Tsunami® 8100 Series - Software Management Guide 150$

Management • 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). : The instructions listed above are based on the assumption that you are using the SolarWinds TFTP server; otherwise 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 CLI/WEB/SNMP passwords. The security 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. The commands used for the generation of TBC file are: T8000-00:00:01# generate tbc-with-pwds T8000-00:00:01# generate tbc-without-pwds The generated TBC file contains, • Default configurations • Any user-added or edited configurations on current live CLI session The generated Text Based Template Configuration file appears as shown below: Tsunami® 8100 Series - Software Management Guide 151

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. 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. Tsunami® 8100 Series - Software Management Guide 152

Management 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. : • Remove any unmodified parameters from the TBC file, before loading it. • 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. : Make sure the firmware being loaded is compatible to the device being upgraded. 6.2.3.1 Upgrade Firmware via HTTP To upgrade the firmware via HTTP, do the following: 1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > HTTP. 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. Tsunami® 8100 Series - Software Management Guide 153

Management 3. Click Update. 4. Once the update successfully completes, reboot the device. 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. Enter the TFTP Server IP Address in the Server IP Address box. 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 update the device with new firmware, click either Update, or Update & Reboot. If you click Update, then you should reboot the device after loading the files. Whereas, if you click Update and Reboot, the system will automatically reboot the device after loading the files. : • After updating 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 update is in progress. 6.2.4 Upgrade Configuration You can update 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. Tsunami® 8100 Series - Software Management Guide 154

Management Figure 6-7 Upgrade Configuration - HTTP 2. In the HTTP screen, click Browse to locate the configuration file. Select Flashcfg.cfg for Binary Configuration file and PXM-TBC.xml for Text Based Configuration file. Make sure that the file name does not contain any space or special characters. 3. If you are updating the device with Binary Configuration file then click Update and then reboot the device. 4. If you are updating the device with Text Based Configuration file then, a. Click Update to update the device with the config file and then click Load for loading the config file onto the device. Alternatively, you can perform both update and load operation in one single step, by clicking Update & Load. b. For the changes to take effect, click COMMIT and then REBOOT. 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. Figure 6-8 Upgrade Binary Configuration via TFTP 2. You can update the device with two configuration files: Binary and Text Based. To update the device with Binary Configuration file, select Binary Config. • Enter the TFTP server IP Address in the Server IP Address box. Tsunami® 8100 Series - Software Management Guide 155

Management • 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. • Enter the TFTP server IP Address in the Server IP Address box. • 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 4. If you are updating the device with Binary Configuration file then click Update and then reboot the device or alternatively click Update & Reboot. 5. If you are updating the device with Text Based Configuration file then • Click Update to copy the text config file onto the device and then click Load for updating the device with text config file. • Alternatively, you can perform both update and load operation in one single step, by clicking Update & Load. • For the changes to take effect, click COMMIT and then REBOOT. : It is recommended not to navigate away from the upgrade screen, while the update is in progress. 6.2.5 Retrieve From Device The Retrieve From Device tab allows you to retrieve logs and config files from the device either through HTTP or TFTP. 6.2.5.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. Tsunami® 8100 Series - Software Management Guide 156

Management Figure 6-10 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. 3. Click Retrieve. Based on the selected file, the following Download screen appears. Figure 6-11 Download Screen 4. Right-click the Download link and select Save Target As or Save Link As to save the file to the desired location. 6.2.5.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. Tsunami® 8100 Series - Software Management Guide 157

Management Figure 6-12 Retrieve Files via TFTP 2. Enter the TFTP server IP Address in the Server IP Address box. 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. 5. Click Retrieve. The retrieved file can be found in the TFTP Server folder. • When the device is running with default factory settings, there is no Binary Configuration file present and hence it cannot be retrieved. • 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. Tsunami® 8100 Series - Software Management Guide 158

$Management 6.3 Services The Services tab lets you configure the HTTP/HTTPS, Telnet/SSH and SNMP interface parameters. 6.3.1 HTTP/HTTPS To configure HTTP/HTTPS interface parameters, navigate to MANAGEMENT > Services > HTTP / HTTPS. Figure 6-13 HTTP/HTTPS Tabulated below is the table which explains HTTP/HTTPS parameters and the method to configure the configurable parameter(s). Parameter Description Admin Password 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 By default, a user can manage the device through Web Interface. To prevent access to the device through Web Interface, select Disable. HTTP Port Represents the HTTP port to manage the device using Web Interface. By default, the HTTP port is 80. Tsunami® 8100 Series - Software Management Guide 159$

$Management Parameter Description 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. : 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-14 Telnet/SSH Tabulated below is the table which explains Telnet/SSH parameters and the method to configure the configurable parameter(s): Parameter Description Admin Password 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 Tsunami® 8100 Series - Software Management Guide 160$

$Management 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 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. SSH By default, a user can manage the device through SSH. To prevent access to the device through SSH, select Disable. SSH Port Represents the port to manage the device using Secure Shell. By default, the Secure Shell port is 22. SSH Sessions 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® 8100 Series - Software Management Guide 161$

Management 6.3.3 SNMP To configure SNMP interface parameters, navigate to MANAGEMENT > Services > SNMP. Figure 6-15 SNMPv1-v2c Tsunami® 8100 Series - Software Management Guide 162

$Management Figure 6-16 SNMPv3 Tabulated below is the table which explains SNMP parameters and the method to configure the configurable parameter(s): Parameter Description 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. : 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 at 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 Tsunami® 8100 Series - Software Management Guide 163$

$Management 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 at 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. 6.3.3.1 SNMP Trap Host Table The SNMP Trap Host table allows you to add a maximum of 5 Trap server’s 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: Tsunami® 8100 Series - Software Management Guide 164$

$Management Figure 6-17 Add Entries to SNMP Host Table Configure the following parameters: • IP Address: Type the IP address of the Trap server to which SNMP traps will be delivered. • 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. 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: Tsunami® 8100 Series - Software Management Guide 165$

Management Figure 6-18 Logs • Event Log Priority: By default, the priority is set to Notice. You can configure the event log priority as one of the following: - 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. 6.3.4.1 Configure a Remote Syslog host To forward the syslog messages to a remote syslog host, do the following: 1. Click Add in the Syslog Host Table screen. The Syslog Host Table Add Row screen appears: Tsunami® 8100 Series - Software Management Guide 166

Management Figure 6-19 Syslog Host Table Add Row 2. IP Address: Enter the IP address of the Syslog host. 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. Entry Status: By default, the configured Syslog host is enabled on the device. To delete the configured Syslog host, click Delete. To disable an entry in the Syslog Host Table, click Disable. 6. Click Add. 7. Click OK and then COMMIT. 6.4 Simple Network Time Protocol (SNTP) Proxim’s point-to-multipoint and point-to-point devices are furnished with Simple Network Time Protocol (SNTP) Client software that enables to synchronize device’s 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 device’s time with time servers or manually set the time, navigate to MANAGEMENT > SNTP. The SNTP screen appears: Tsunami® 8100 Series - Software Management Guide 167

Management Figure 6-20 Time Synchronization Tabulated below is the table which explains SNTP parameters and the method to configure the configurable parameter(s): Parameter Description Enable SNTP Status Select this parameter to enable SNTP Client on the device. If enabled, the SNTP Client tries to synchronize the device’s time with the configured time servers. By default, the SNTP status is disabled. Primary Server IP Enter the host name or the IP address of the primary SNTP time server. The SNTP Client Address/Domain tries to synchronize device’s time with the configured primary server time. Name : If host name is configured, instead of IP address then make sure that DNS server IP is configured on the device. Secondary Server IP Enter the host name or the IP address of the secondary SNTP time server. If the primary Address/Domain server is not reachable, then SNTP client tries to synchronize device’s time with the Name 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. 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. 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. Tsunami® 8100 Series - Software Management Guide 168

Management Parameter Description 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. Sync Status Specifies the SNTP Client sync status when it tries to ReSync again with the time servers. The status is as follows: • Disabled: The SNTP client will not synchronize the time with the time servers and displays the status as Disabled. • Synchronizing: The SNTP client is in the process of synchronzing time with the time servers. • Synchronized: The SNTP client has synchronized time with the time servers. Current Date/Time Displays the current date and time. 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. Manual Time If SNTP Client is disabled on the device or the time servers are not available on the Configuration network, then the user can manually set the time. Enter the time manually in the format: MM-DD-YYYY HH:MM:SS. : • Manual time configuration is not retained across reboots. After every reboot the user has to set the time again. • With manual time configuration, the device may lag behind the actual time over a period of time. So, it is recommended to periodically check and adjust the time. To save the configured parameters, click Ok and then COMMIT. 6.5 Access Control The Access Control tab enables you to control the device management access through specified host(s). You can specify a maximum of 5 hosts to control device management access. To configure management access control parameters, navigate to MANAGEMENT > Access Control. The Management Access Control screen appears: Tsunami® 8100 Series - Software Management Guide 169

Management Figure 6-21 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-22 Management Access Table Add Row 2. IP Address: Type the IP 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. 6.5.0.2 Edit Management Access Control Table Entries Edit the desired host entries and click OK, COMMIT and then REBOOT. 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: Tsunami® 8100 Series - Software Management Guide 170

Management Figure 6-23 Reset to Factory Defaults Click OK, if you wish to proceed with factory reset, else click Cancel. 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 regular SU. This feature is applicable only to, • Tsunami® QB-8100-EPA which converts to a Tsunami® MP-8100-SUA, and • Tsunami® QB-8150-EPR which converts to a Tsunami® MP-8150-SUR You can convert a QB to SU mode by using two methods: • Method 1: Web Interface • Method 2: Load a 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. 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: Figure 6-24 Convert QB to MP 2. Click OK. 3. Reboot the device for the changes to take effect. : • 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, the device will reset to factory default upon initialization and operate in QB mode. • When upgrading a converted device from Bootloader, it must be done using a QB image, as the device is licensed as QB. • The conversion of the device from QB to SU requires a reboot. Tsunami® 8100 Series - Software Management Guide 171

Management • In case of Method 1 conversion, QB mode configuration will be deleted. • Reset to factory defaults, always results in the device initializing in QB mode. Tsunami® 8100 Series - Software Management Guide 172

7 Monitor This chapter contains information on how to monitor the device by using Web interface. It contains information on the following: • Interface Statistics • WORP Statistics • Active VLAN • Bridge • Network Layer • RADIUS (BSU or End Point A only) • IGMP • DHCP • Logs • Tools • SNMP v3 Statistics 7.1 Interface Statistics Interface Statistics allows you to monitor the status and performance of the Ethernet and Wireless interfaces of the device. 7.1.1 Ethernet Statistics To view the Ethernet interface statistics, click MONITOR > Interface Statistics. The Interface Statistics screen appears: Figure 7-1 Ethernet Interface Statistics Tsunami® 8100 Series - Software Management Guide 173

Monitor To view Ethernet statistics, click Ethernet 1 or Ethernet 2 depending on the Ethernet interfaces supported by your device. Tabulated below is the table which explains the parameters displayed in the Ethernet Statistics screen: Parameter Description MTU Specifies the largest size of the data packet received or sent on the Ethernet interface. MAC Address Specifies the MAC address at the Ethernet protocol layer. Operational Status Specifies the current operational state of the Ethernet interface. In Octets Specifies the total number of octets received on the Ethernet interface. In Unicast Packets Specifies the number of subnetwork- unicast packets delivered to the higher level protocol. In Non-unicast Packets Specifies the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Specifies the number of inbound packets that contained errors and are restricted from being delivered. Out Octets Specifies the total number of octets transmitted out of the Ethernet interface. Out Unicast Packets Specifies the total number of packets requested by the higher level protocol and then, transmitted to the non-unicast address. Out Discards 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 could not be transmitted because of errors. To view the updated Ethernet statistics, click Refresh. To delete the Ethernet statistics, click Clear. Tsunami® 8100 Series - Software Management Guide 174

Monitor 7.1.2 Wireless Statistics To view the Wireless interface statistics, click MONITOR > Interface Statistics > Wireless1. Figure 7-2 Wireless Interface Statistics In addition to the parameters displayed for the Ethernet interface(s), the following parameters are displayed for the wireless interface. Parameter Description Retunes Specifies the number of times the radio is retuned for better performance of the device. SNR Statistics SNR Statistics represents the signal strength with regard to the noise at the antenna ports. Antenna Specifies the antenna ports available for the product. Please note that the antenna ports vary depending on the product. Status Specifies the configuration status of the antenna ports. ON indicates that antenna port is enabled and OFF indicates that antenna port is disabled. Control Specifies the SNR value of the packet received at the selected channel frequency. Tsunami® 8100 Series - Software Management Guide 175

Monitor Parameter Description Extension 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 Decrypt Errors This parameter is applicable only if security is enabled. It indicates the number of received packets that failed to decrypt. CRC Errors Specifies the number of received packets with invalid CRC. PHY Errors 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.1.3 PPPoE Statistics : Applicable only to a SU in Routing mode. To view PPPoE interface statistics, navigate to MONITOR > Interface Statistics > PPPoE > PPP Interface Stats. Figure 7-3 PPPoE Interface Statistics 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. Tsunami® 8100 Series - Software Management Guide 176

Monitor Figure 7-4 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-5 PPPoE Connection Statistics 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. To clear the existing connection statistics, click Clear. 7.1.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: Figure 7-6 IP Tunnels Interface Statistics Tsunami® 8100 Series - Software Management Guide 177

Monitor Tabulated below is an explanation to each of these parameters: Parameter Description Name Specifies the tunnel interface name. Alias Specifies a supplementary tunnel interface name. Maximum Specifies the largest size packet or frame that can be sent over the tunnel interface. Transmission Unit (MTU) 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. Details Provides a more detailed statistics about the tunnel interface. To view the detailed statistics, click Figure 7-7 Detailed IP Tunnels Interface Statistics The detailed tunnel interface parameters are similar to the Ethernet Interface Statistics. Please refer to Ethernet Statistics. Tsunami® 8100 Series - Software Management Guide 178

Monitor 7.2 WORP Statistics 7.2.1 General Statistics 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: Figure 7-8 WORP General Statistics Tabulated below is an explanation to each of these parameters: Parameter Description Interface Type Specifies the type of radio interface. WORP Protocol Specifies the version of the WORP Protocol used. This information is useful to the customer Version support team for debugging purpose only. WORP Data Messages Specifies the sent or received data frames through wireless interface. 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 poll messages were sent by a BSU/End Point A but no reply was received by SU/End Point B. This parameter is valid only on BSU. Tsunami® 8100 Series - Software Management Guide 179

Monitor Parameter Description Data Transmission Statistics Specifies the number of transmissions occurred through the interface. Send Success Refers to the number of data messages sent and acknowledged by the peer successfully. Send Retries Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Send Failures 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 a 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 Refers to the number of authentication request messages sent or received on WORP Requests interface. Authentication Refers to the number of authentication confirm messages sent or received on WORP Confirms interface. Registration Attempts Refers to the number of times a registration attempt has been initiated. Registration Refers to the number of registration attempts that are not yet completed. Incompletes Registration Timeouts Refers to the number of times the registration procedure timed out. Registration Last Refers to the reason for the last registration getting aborted or failed. Reason : 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. Tsunami® 8100 Series - Software Management Guide 180

Monitor 7.2.2 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 / End Point B Link Statistics. Figure 7-9 An Example - SU Link Statistics Tabulated below is an explanation to each of these parameters: Parameter Description SU Name/ Represents the name of the SU/End Point B connected to a BSU/End Point A respectively. End Point B Name MAC Address 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 Represents the data transmission rate at the remote (peer) end. (Mbps) Local Antenna Port Indicates the status of the antenna ports at the local end. The following symbols indicate Info the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. 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. 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. Tsunami® 8100 Series - Software Management Guide 181

Monitor Parameter Description Remote Antenna Port Indicates the status of the remote end antenna ports. The antenna ports status is same as Info 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 Applicable only when ATPC is enabled on the device. (dBm) • TPC: Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio antenna. • 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 in the SU/End Point B Link Statistics screen. The following screen appears depending on your device: Tsunami® 8100 Series - Software Management Guide 182

Monitor Figure 7-10 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 a SU/End Point B from BSU/End Point A respectively, click Disconnect. To view updated detailed statistics, click Refresh. Tsunami® 8100 Series - Software Management Guide 183

Monitor To view local SNR table, click Click here for Local SNR-Table on the upper-right of SU/End Point B Link Statistics screen (Refer An Example - SU Link Statistics). The following screen appears depending on your device: Figure 7-11 Local SNR Information These configured values are used by ATPC and DDRS to derive TPC and data rate for optimal throughput. 7.2.3 BSU/End Point A Link Statistics : BSU Link Statistics is applicable only to a 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® 8100 Series - Software Management Guide 184

Monitor Figure 7-12 An Example - BSU Link Statistics The link statistics are similar to SU / End Point B Link Statistics. 7.2.4 QoS Statistics (BSU or End Point A Only) : 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. Figure 7-13 QoS Summary 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. Tsunami® 8100 Series - Software Management Guide 185

Monitor 7.3 Active VLAN : This parameter is applicable only to a device in SU 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: Figure 7-14 Active VLAN The Active VLAN Config parameter helps you to identify the current VLAN configuration applied on the device in SU mode. • Local: VLAN configuration is done locally from the device. • Remote: VLAN configuration is done through RADIUS Server. 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: Figure 7-15 Active VLAN Ethernet Configuration This page displays the VLAN Ethernet parameters and their values that are configured either locally or remotely. Tsunami® 8100 Series - Software Management Guide 186

Monitor : Please note that the number of Ethernets vary depending on the device. 7.4 Bridge 7.4.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: Figure 7-16 Bridge Statistics The following table lists the parameters and their description:Parameter Description Description This parameter provides a description about the bridge. MTU Represents the largest size of the data packet sent on the bridge. MAC Address Represents the MAC address at the bridge protocol layer. Operational Status 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. Tsunami® 8100 Series - Software Management Guide 187

Monitor Parameter Description In Errors Represents the number of inbound packets with errors and that are restricted from being delivered. Out Octets Represents the total number of octets transmitted out of the bridge, including the framing characters. Out Unicast Packets Represents the total number of packets requested by higher-level protocols to be transmitted out of the bridge interface to a subnetwork-unicast address, including those that were discarded or not sent. Out Discards 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. Out Errors Represents the number of outbound packets that could not be transmitted because of errors. To view updated Bridge statistics, click Refresh. To clear the Bridge statistics, click Clear. 7.4.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. Figure 7-17 Learn Table 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. To view updated learn table statistics, click Refresh. To clear learn table statistics, click Clear. Tsunami® 8100 Series - Software Management Guide 188

Monitor 7.5 Network Layer 7.5.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: Figure 7-18 Routing Table 7.5.2 IP ARP 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. Figure 7-19 IP ARP Table The IP ARP Table contains the following information: • Index: Represents the interface type. • MAC Address: Represents the MAC address of a node on the network. • 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. To clear the IP ARP entries, click Clear. Tsunami® 8100 Series - Software Management Guide 189

Monitor 7.5.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. Figure 7-20 ICMP Statistics The following table lists the ICMP Statistics parameters and their description:Parameter Description In Msgs or Out Msgs Represents the number of ICMP messages that are received/transmitted by the device. In Errors or Out Errors 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. In Dest Unreachs or Represents the number of ICMP destination unreachable messages that are Out Dest Unreachs received/transmitted by the device. In Time Excds or Out Represents the number of ICMP time exceeded messages that are received/transmitted by Time Excds the device. In Parm Probs or Out Represents the number of ICMP parameter problem messages that are Parm Probs received/transmitted by the device. In Srec Quenchs or Represents the number of ICMP source quench messages that are received/transmitted by Out Srec Quenchs the device. In Redirects or Out Represents the rate at which the ICMP redirect messages are received/transmitted by the Redirects device. In Echos Represents the rate at which the ICMP echo messages are received. In EchoReps or Out Represents the rate at which the ICMP echo reply messages are received/transmitted by EchoReps the device. Tsunami® 8100 Series - Software Management Guide 190

Monitor Parameter Description In Timestamps or Out Represents the rate at which the ICMP timestamp (request) messages are Timestamps received/transmitted by the device. In Timestamps Reps or Represents the rate at which the ICMP timestamp reply messages are received/transmitted Out Timestamps Reps by the device. In Addr Masks or Out Represents the number of ICMP address mask request messages that are Addr Masks received/transmitted by the device. In Addr Mask Reps or Represents the number of ICMP address mask reply messages that are Out Addr Mask Reps received/transmitted by the device. To view updated ICMP Statistics, click Refresh. 7.5.4 RIP Database The RIP Database screen contains routes (Routing Information Protocol updates) learnt from other routers. Figure 7-21 RIP Database Tsunami® 8100 Series - Software Management Guide 191

Monitor Parameter Description Mal Resp Represents the number of malformed RADIUS access response messages received by the device since client startup. Bad Auths Represents the number of malformed RADIUS access response messages containing invalid authenticators received by the device since client startup. Time Outs Represents the total number of timeouts for RADIUS access request messages since client startup. UnKnown Types This parameter specifies the number of messages with unknown RADIUS message code since client startup. Packets Dropped Represents the number of RADIUS packets dropped by the device. To view updated RADIUS Client Authentication statistics, click Refresh. 7.7 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-23 Ethernet1 Multicast List 7.7.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 Description Group IP Represents the IP address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. MAC Address Represents the MAC address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Tsunami® 8100 Series - Software Management Guide 193

Monitor Parameter Description Time Elapsed 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.7.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: Figure 7-24 Router Port List The following table lists the parameters and their description. Parameter Description Port Number Represents the port number on which multicast router is attached (on which IGMP Query has been received). Time Elapsed Represents the time elapsed since the port is marked as the router port. To view updated Router Port list, click Refresh. 7.8 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. Tsunami® 8100 Series - Software Management Guide 194

Monitor Figure 7-25 DHCP Leases 7.9 Logs 7.9.1 Event Log The Event Log 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. To view the Event Log, navigate to MONITOR > Logs > Event Log. The following Event Log screen appears: Figure 7-26 Event Logs Tsunami® 8100 Series - Software Management Guide 195

Monitor To hide the event logs, click Hide Event Log. To clear the event logs, click Clear Event Log. To view updated event logs, click Refresh. : The recent event logs are stored in the flash memory. 7.9.2 Syslog System log messages are generated by the system by sending requests at various instances to the system log server. To view System Logs, navigate to MONITOR > Logs > Syslog. The Syslog screen appears. Figure 7-27 System Log To clear Syslog information, click Clear Syslog. To hide Syslog information, click Hide Syslog. To refresh Syslog messages, click Refresh. 7.9.3 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: Tsunami® 8100 Series - Software Management Guide 196

Monitor Figure 7-28 Debug Log 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. 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.9.4 Temperature Log : Temperature Log are not applicable to Tsunami® MP-8150-CPE, Tsunami® MP-8160-CPE and Tsunami® QB-8150-EPR-12/50 devices. Temperature Log feature reports and logs the internal temperature of the device. When the internal temperature value reaches the minimum threshold value of -40ºC or the maximum threshold temperature of 60ºC, the internal temperature is logged and an SNMP trap is sent (At 5 Degrees before each limit, the device issues a warning trap). These threshold temperature values may be reconfigured but the values cannot exceed beyond the default values. : A recording interval from one to sixty minutes with 5-minute increments can be selected. If we configure the logging interval as “0”, temperature logs will be disabled. To view and configure threshold values, and the logging interval, navigate to MONITOR > Logs > Temperature Log. The threshold values of temperature are configured in Centigrade (Celsius) scale. The Temperature Log screen displays the Current Device Temperature in Celsius, along with High Temperature and Low Temperature Threshold values and Temperature Logging Interval. The temperature log can have a maximum size of 65 Kb; and once the limit is reached, only the last 576 logs are available. (Log storage is up to six days with the refresh time of 5 minutes). Tsunami® 8100 Series - Software Management Guide 197

Monitor Figure 7-29 Temperature Log After configuring the parameters, click OK. To view the Temperature Log, click Show Temp Log. To delete all the Temperature Logs, click Clear Temp Log. Click Refresh, to get the updated Temperature Log. 7.10 Tools 7.10.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-30 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. Click Refresh, to get the updated Wireless Site Survey. Tsunami® 8100 Series - Software Management Guide 198

Monitor 7.10.2 Scan Tool With Scan Tool, you can scan all the devices available in your network. To scan the devices, navigate to MONITOR > Tools > Scan Tool. The Scan Tool screen appears. Figure 7-31 Scanned Devices Click Scan to scan and refresh the devices on the network. 7.10.3 sFlow® Proxim’s 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. Figure 7-32 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: Tsunami® 8100 Series - Software Management Guide 199

Monitor • 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: Figure 7-33 sFLOW This screen displays the following information about the sFlow Agent: • Version: The version displayed is 1.3;Proxim Wireless Corp.; v6.4. The version comprises the following information: 1. sFlow MIB Version: Indicates the agent’s MIB version. The MIB specifies how the agent extracts and bundles sampled data, and the sFlow receiver must support the agent’s MIB. The sFlow MIB version is 1.3. so the sFlow Receiver’s 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 Agent’s IP address. Tsunami® 8100 Series - Software Management Guide 200

Monitor 7.10.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. Tabulated below is the table which explains sFlow parameters and the method to configure the configurable parameter(s): Parameter Description S.No. Represents the Receiver index number. Please note that the number of indexes depends on the ethernet interfaces your device supports. Owner Enter a string, which uniquely identifies the sFlow Receiver. 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 Receiver’s 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. : • Enabling sampling effects the system performance and hence care should be taken in setting the right values for Timeout and Max Datagram Size. • When the Owner string is cleared, the Flow Sampling and Counter Polling stops. 7.10.3.2 Sampling Configuration To configure and start packet flow sampling, do the following: 1. Navigate to MONITOR > Tools > sFlow and select Sampling Configuration tab. Tsunami® 8100 Series - Software Management Guide 201

Monitor Figure 7-34 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. 5. Next, click Apply to start packet flow sampling. Once it starts, the Time Out parameter (see sFlow Receiver Configuration) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and Sampling values are set to default values. : • Enabling sFlow packet sampling effects the system performance, and hence care must be taken when choosing the right value for Packet Sampling Rate and Maximum Header Size. • Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface. Tsunami® 8100 Series - Software Management Guide 202

Monitor 7.10.3.3 Counter Polling Configuration To configure and start Counter Polling sampling, do the following: 1. Navigate to MONITOR > Tools > sFlow and select Counter Polling Configuration tab. Figure 7-35 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. 4. Next, click Apply to start Counter Polling Sampling. Once it starts, the Time Out parameter (see sFlow Receiver Configuration) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and Counter Polling values are set to default values. • Enabling sFlow counter sampling effects the system performance, and hence care must be taken when choosing the right value sampling interval. • 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. Tsunami® 8100 Series - Software Management Guide 203

Monitor 7.10.4 Console Commands The Console Commands feature helps Proxim’s Technical Support team to debug field issues. 7.11 SNMP v3 Statistics SNMP v3 statistics can be viewed only when SNMPv3 feature is enabled on the device. See SNMP. To view the SNMPv3 Statistics, navigate to MONITOR > SNMPV3 Statistics. The following SNMP v3 Statistics screen appears: Figure 7-36 SNMP v3 Statistics The following table lists the SNMP v3 parameters and their description:Parameter Description Unsupported Sec This parameter specifies the total number of packets received by the SNMP engine, which Levels were dropped because they requested a security level that was unknown to the SNMP engine or otherwise unavailable. Not In Time Windows This parameter specifies the total number of packets received by the SNMP engine which were dropped because they appeared outside of the authoritative SNMP engine's window. Unknown User Names This parameter specifies the total number of packets received by the SNMP engine which were dropped because they correspond to an unknown user to the SNMP engine. Unknown Engine IDs This parameter specifies the total number of packets received by the SNMP engine which were dropped because they correspond an SNMP Engine ID that was unknown to the SNMP engine. Wrong Digests This parameter specifies the total number of packets received by the SNMP engine which were dropped because they did not contain the expected digest value. Decryption Errors This parameter specifies the total number of packets received by the SNMP engine which were dropped because they could not be decrypted. Tsunami® 8100 Series - Software Management Guide 204

8 Troubleshooting 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 http://support.proxim.com which stores all resolved problems in its solution database. Alternatively, you can post a question on the support site, to a technical person who will reply to your email. 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. In some cases, rebooting the device solves the problem. If nothing else helps, consider a Soft Reset to Factory Defaults or a Forced Reload. The Forced Reload option requires you to download a new firmware onto the device. This chapter provides information on the following: • PoE Injector • Connectivity Issues • Surge or Lightning Issues (For Connectorized devices) • Setup and Configuration Issues • Application Specific Troubleshooting • Wireless Link Issues • Wired (Ethernet) Interface Validation • Wireless Interface Validation • Recovery Procedures • Spectrum Analyzer • Miscellaneous Tsunami® 8100 Series - Software Management Guide 205

Troubleshooting 8.1 PoE Injector Problem Solution The Device Does Not • Make sure that you are using a standard UTP Work - Category 5e/6 cable in case of MP-8100-BSU, MP-8100-SUA, MP-8150-SUR, MP-8160-BSU, MP-8160-SUA, QB-8100-EPA and QB-8150-EPR devices - Category 5 cable in case of MP-8150-CPE, MP-8160-CPE, QB-8150-EPR-12/50 • 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. • Try to connect the device to a different PoE Injector hub. • Try using a different Ethernet cable - if it works, there is probably a fault in the cable or its connection. • Check the power plug and hub. • If the ethernet link goes down, check the cable, cable type, switch and hub. There is No Data Link • Verify that the indicator on the device port is “ON.” • 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 - Category 5e/6 cable in case of MP-8100-BSU, MP-8100-SUA, MP-8150-SUR, MP-8160-BSU, MP-8160-SUA, QB-8100-EPA and QB-8150-EPR devices - Category 5 cable in case of MP-8150-CPE, MP-8160-CPE, QB-8150-EPR-12/50 devices • The length of the cable from the Ethernet port of the device to the PoE should be less than 100 meters (approximately 325 feet). • 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. • 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. Overload Indications • Connect the device to a PoE Injector. • Ensure that there is no short over on any of the connected cables. • Move the device into a different output port (remember to move the input port accordingly) - if it works then there is a fault probably in the previous RJ45 port or bad RJ45 port connection. 8.2 Connectivity Issues Connectivity issues include any problem that prevents from powering or connecting to the device. Problem Solution Does Not Boot - No • Make sure your power source is ON. LED Activity • Make sure all the cables to the device are connected properly. Tsunami® 8100 Series - Software Management Guide 206

Troubleshooting Problem Solution Ethernet Link Does Check the Ethernet LED Not Work • Solid Green: The Ethernet link is up. • Blinking Green: The Ethernet link is down. Serial Link Does Not • Double-check the physical network connections. Work • Make sure your PC terminal program (such as HyperTerminal) is active and configured to the following values: - 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; - Line Feeds with Carriage Returns • (In HyperTerminal select: File > Properties > Settings > ASCII Setup > Send Line Ends with Line Feeds) : Not applicable to Tsunami® MP-8160-CPE as it does not support serial interface. Cannot Access the • Open a command prompt window and type the Ping command along with the IP Web Interface 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 using Microsoft Internet Explorer 7.0 (or later) or Mozilla Firefox 3.0 (or later). • 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. • Troubleshoot the network infrastructure (check switches, routers, and so on). : At any point of time, if the device is unable to connect to your network, reset the device by unplugging and plugging the cables from the PoE. 8.3 Surge or Lightning Issues (For Connectorized devices) Problem Solution Surge or Lighting In case of any lightning or surge occurrence, check for the conditions specified below: Problem • 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. Tsunami® 8100 Series - Software Management Guide 207

$Troubleshooting 8.4 Setup and Configuration Issues Problem Solution Device Reboots One of the reason for the device to reboot continuously is that the radio card is not Continuously 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, please contact Proxim’s support site at http://support.proxim.com. Lost Telnet or SNMP Perform Soft Reset to Factory Defaults procedure. This procedure resets system and Password network parameters, but does not affect the image of the device. The default HTTP, Telnet, and SNMP username is admin and password is public. Device Responds If the device takes a long time to respond, it could mean that: Slowly • No DHCP server is available. • 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. • The network traffic is more. Incorrect Device IP • The default IP address assignment mode is Static and the default IP address of the Address 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 Ethernet, refer to Initializing the IP Address using CLI. • Perform Soft Reset to Factory Defaults procedure. This will reset the device to static mode. HTTP Interface or • Make sure you are using a compatible browser: Telnet Does Not Work - Microsoft Internet Explorer 7.0 or later - Mozilla Firefox 3.0 or later • Make sure you have the correct IP address of the device. Enter the device IP address in the address bar of the browser, for example http://169.254.128.132. • When the Enter Network Password window appears, enter the User Name and 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. Telnet CLI Does Not • Make sure you have the correct IP address. Enter the device IP address in the Telnet Work connection dialog, from a DOS prompt: C:\> telnet <Device IP Address> • Use HTTP, to check the IP Access Table which can restrict access to Telnet and HTTP. • Enable Telnet in Vista or Windows 7 as it is by default disabled. Tsunami® 8100 Series - Software Management Guide 208$