LMS4000 900 MHz Radio Network User Guide APCD-LM043-4.
WaveRider Communications Inc. Software License Agreement This is a legal agreement between you (either an individual or an entity) and WaveRider Communications Inc. for the use of WaveRider computer software, hereinafter the “LICENSED SOFTWARE”. By using the LICENSED SOFTWARE installed in this product, you acknowledge that you have read this license agreement, understand it, and agree to be bound by its terms.
The following are trademarks or registered trademarks of their respective companies or organizations: Microsoft Windows NT 4.0 Workstation (with Service Pack 6a), Microsoft Access, Microsoft SQL Server, Microsoft SQL Agent / Microsoft Corporation Vircom VOP Radius Server / Vircom Inc. Castlerock SNMPc Server / Castle Rock Computing APS PowerChute PLUS / American Power Conversion Veritas Backup Exec / VERITAS Software © 2002 by WaveRider Communications Inc. All rights reserved.
Warranty In the following warranty text, “WaveRider®” shall mean WaveRider Communications Inc. This WaveRider product is warranted against defects in material and workmanship for a period of one (1) year from the date of purchase. During this warranty period WaveRider will, at its option, either repair or replace products that prove to be defective. For warranty service or repair, the product must be returned to a service facility designated by WaveRider.
Contents Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Network Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 5 Radio Network Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.1 Design Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 5.2 Basic System Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 5.2.1 Overview of Basic System Design . . .
8.5 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 8.6 Configuring the Customer List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 9 Installing the EUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 9.1 Before you Start the EUM Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.2 Other EUM Programming Considerations . . .
Appendix A Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Appendix B Factory Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Appendix C Command-Line Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Appendix D Antenna Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Appendix E CCU/EUM Data Tables . . . . .
Figures Figure 1 Quick Startup — CCU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Figure 2 Quick Startup — EUM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Figure 3 Quick Startup — Ping Test (from console port) . . . . . . . . . . . . . . . . . . . . . . 9 Figure 4 Quick Startup — Ping Test (from EUM Ethernet port) . . . . . . . . . . . . . . . . 10 Figure 5 Quick Startup — Connecting to the Internet . . . . . . . . . . . . . . . . . .
x Figure 34 EUM LEDs and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Figure 35 CCU LEDs and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Figure 36 Ethernet LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Figure 37 EUM Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Figure 38 Connecting the EUM Components .
Tables Table 1 Console Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Table 2 Quick Startup — EUM Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Table 3 CCU Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 4 EUM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Table 5 End-user PC Configuration . . . .
xii Table 34 Remote Troubleshooting — CCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Table 35 Local Troubleshooting — CCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Table 36 General Network Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 Table 37 Ethernet Cabling Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 Table 38 Radio Specifications . . . . . . . . . . . . . . . . . .
Table 72 WaveRider CCU Registration Table MIB . . . . . . . . . . . . . . . . . . . . . . . . . 211 Table 73 WaveRider CCU Authorization Table MIB . . . . . . . . . . . . . . . . . . . . . . . . 212 Table 74 WaveRider CCU Authorization Table MIB . . . . . . . . . . . . . . . . . . . . . . . . 212 Table 75 CCU RFC MIB-II Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Table 76 WaveRider EUM Base MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
— This page is intentionally left blank —
Preface About this Manual WaveRider recommends that you read the following sections before proceeding with the instructions in this guide: • Software License Agreement on page ii • Warranty on page iv • Warnings and Advisories on page xvii • Conventions on page xv NOTE: The information contained in this manual is subject to change without notice. The reader should consult the WaveRider web site for updates. The procedures in this document are centered around the command-line interface (CLI).
Regulatory Notices This device has been designed to operate with several different antenna types. The gain of each antenna type shall not exceed the maximum antenna system gain as given in Appendix D on page 181. Antennas having a higher gain are strictly prohibited by Industry Canada and FCC regulations. The required antenna impedance is 50 ohms. Industry Canada CCU and EUM The IC Certification Number for the CCU and EUM is 3225104140A. Operators must be familiar with IC RSS-210 and RSS-102.
Operational Requirements CCU and EUM In accordance with the FCC Part 15 regulations: 1. The maximum peak power output of the intentional radiator shall not exceed one (1) watt for all spread spectrum systems operating in the 902 to 928MHz band. This power is measured at the antenna port of the CCU or the EUM. 2.
WARNING! To comply with FCC RF exposure limits, the antennas for the CCU must be fix-mounted on outdoor permanent structures to provide a separation distance of 2m or more from all persons to satisfy RF exposure requirements. The distance is measured from the front of the antenna to the human body. It is recommended that the antenna be installed in a location with minimal pathway disruption by nearby personnel.
1 Introduction The LMS4000 system provides 900MHz and 2.4GHz wireless. high-speed Internet connectivity to business and residential subscribers.
1 Introduction channel. Even with large numbers of subscribers, end users generally perceive that they have the entire channel to themselves. • Grade of Service Support: The Polling MAC supports up to four end-user grades of service, which allows the system operator to segment service offerings for those users that demand and are willing to pay for higher grades of service, and those that are only willing to pay for a more basic grade of service.
1 Introduction • SNMP Support: Using WaveRider-supplied SNMP MIBs, network operators can integrate the LMS4000 with their existing network management system to allow monitoring of CCUs and EUMs from an existing and/or centralized SNMP manager. Once SNMP is configured, the operator can monitor system events, parameters, and statistics in real time. Statistics can be processed in the SNMP manager to provide alarms, trend data, graphical outputs, and derived performance data.
— This page is intentionally left blank —
2 Quick Startup This section outlines the procedure for setting up a very simple LMS4000 900 MHz radio network consisting of one CCU and one EUM. This simple network, which can be set up in a lab environment, helps you become familiar with basic LMS4000 configuration and operation. As you become more confident and are ready to progress to customer installations, WaveRider recommends you read the other sections in the manual.
2 Quick Startup 2.2 Equipment Setup 1. Remove the equipment from the boxes and set up the physical configuration shown in Figure 1. Use this setup procedure to configure the CCU, while keeping the following points in mind: • Maintain the order of installation shown in Figure 1. • Maintain at least 3 to 5 meters of physical separation between CCUs and EUMs. • Ensure the paths between the CCU and EUMs are relatively free from obstruction.
2 Quick Startup 2.3 CCU Configuration 1. Start the PC terminal emulation software. You will receive the following prompt: WaveRider Communications, Inc. LMS3000 Password: The default password is a carriage return. Console> The default prompt on your CCU is the CCU Ethernet MAC address. 2. Type the following commands to configure the CCU: Console> ip ethernet 192.168.10.10 24 Console> ip radio 10.0.0.1 22 Console> ip gateway 192.168.10.
2 Quick Startup 2.4 EUM Configuration 1. Connect the PC to the console port of the EUM, as shown in Figure 2. 1 CCU set-up antenna RS232 cable Radio Link EUM3000 CCU3000 EUM Power Supply CCU power supply EUM Antenna Figure 2 Quick Startup — EUM Configuration 2. Start the terminal emulation software. 3. Type the following commands to configure the EUM: WaveRider Communications, Inc. LMS3000 Password: Console> ip ethernet 10.0.0.2 22 Console> ip gateway 10.0.0.
2 Quick Startup 5. Confirm that the EUM has been properly configured, as follows: Console> ip Ethernet/USB IP Address: 10.0.0.2 Ethernet/USB Net Mask : fffffc00 Gateway IP Address: 10.0.0.1 Console> radio RF Power: HIGH Radio Frequency: 9150 Console> 2.5 Testing CCU–EUM Communications Once you have completed the configuration of the Quick Startup, you can test communications between the CCU and the EUM by pinging the CCU through the EUM console port. To Run a Ping Test Through the EUM Console Port 1.
2 Quick Startup 64 bytes from 10.0.0.1: icmp_seq=6. time=16. ms 64 bytes from 10.0.0.1: icmp_seq=7. time=64. ms 64 bytes from 10.0.0.1: icmp_seq=8. time=64. ms ----10.0.0.1 PING Statistics---8 packets transmitted, 8 packets received, 0% packet loss round-trip (ms) min/avg/max = 16/52/112 console> This test verifies the radio link between the EUM and the CCU. To Run a Ping Test Through the EUM Ethernet Port 1. Connect the PC to the EUM Ethernet port, as shown in Figure 4.
2 Quick Startup 2.6 Connecting the Quick Startup to the Internet Once you have verified that the CCU and EUM are communicating properly, you may want to to connect the Quick Startup system to the Internet. To Connect to the Internet 1. Connect the PC to the Ethernet port of the EUM as shown in Figure 5.
2 Quick Startup 4. Select Use the following DNS server address (the exact wording depends on your operating system), and enter the IP address for the Preferred DNS Server, which is available from your Network Administrator. 5. Connect the CCU Ethernet port to the appropriate network switch or hub, or directly to the gateway router of your network. 6. From the PC, you should now be able to open your browser and surf the Web. 2.
3 Detailed Description This section describes the technologies and features used in the LMS4000 900 MHz Radio Network. 3.1 LMS4000 Overview Figure 6 is a high-level schematic of the LMS4000 system, showing the key system components and interfaces.
3 Detailed Description Network Access Point (NAP) The NAP provides the Internet connection point for one or more CAPs. An LMS4000 system can have more than one NAP. The number of NAPs depends on the geographical layout of the LMS4000 system and the location of available Internet access points. A single NAP can provide Internet connection for one CAP, or several CAPs, each either colocated with the NAP or connected to the NAP over backhaul facilities.
3 Detailed Description • Transmission line • Antenna • Ethernet switch Each of the above components is discussed in the following sections. CCU The CCU, shown in Figure 7, is the wireless access point for up to 300 end-user modems. The functional blocks of the CCU are illustrated in Figure 8.
3 Detailed Description The CCU routes IP packets received from the CCU radio port • to internal CCU processes, • through the CCU Ethernet port to any router on the Ethernet network, such as the Network Access Point, or • back out the radio port to other EUMs (EUM-to-EUM packets). The CCU routes IP packets that are received from the Network Access Point through the Ethernet port • to internal CCU processes, or • through the radio port to the destination EUM.
3 Detailed Description Cavity Filters WaveRider recommends the use of cavity filters with all CCUs and is mandatory if colocated with other CCUs. Cavity filters help to isolate the CCU from inband interferers, such as colocated CCUs or non-WaveRider ISM band equipment, as well as out-of-band interferers, such as cellular base stations and paging transmitters. Lightning Arrestors Since the CCU antenna is mounted outdoors, lightning arrestors are required with all CCU installations.
3 Detailed Description settings as the failed CCU. In this way, the CAP can be provisioned for N+1 redundancy, meaning there is one backup CCU for ‘N’ operating CCUs, up to a maximum of N=3. Figure 10 RFSM RF Distribution Panel The optional RF Distribution Panel provides • external interface to the antenna subsystem and site ground, • common surge protector mounting point for each external RF interface, and • common ground point for all CAP components.
3 Detailed Description 3.3.2 EUM The EUM, shown in Figure 11, is a wireless modem that connects to the end-user’s computer through an Ethernet connection. The EUM, which acts as a network bridge, receives data from the CCU over the 900 MHz radio link, and then forwards this data to EUM internal processes or to the end-user’s computer through the Ethernet port. In the other direction, the EUM forwards data received from the end-user’s computer over the radio link to the CCU.
3 Detailed Description EUM Antenna For many EUM installations, you can use an indoor antenna. WaveRider recommends the WaveRider directional antenna with switched-beam diversity. This antenna, shown in Figure 12, performs very well in cases where the radio path to the CCU is obstructed and/or where there is significant multipath. The diversity antenna accepts a DC signal on the antenna cable from the EUM, for beam pattern selection.
3 Detailed Description The WaveRider diversity antenna contains two vertical antenna elements mounted inside and on either side of the antenna housing. The phasing between these elements, which modifies the antenna pattern, is controlled by a DC voltage from the EUM. It produces two patterns, one perpendicular to the face of the antenna, which has a gain of about 6 dBi, and the other, a dual-beam pattern off both sides, offering about 3 dBi gain for each beam.
3 Detailed Description Lightning Arrestor A lightning arrestor is required at the EUM only if an outdoor antenna is used. 3.4 Basic Operation 3.4.1 LMS4000 Transmission Concept Conceptually, the LMS4000 900 MHz Radio Network can be thought of as an Ethernet switch with a built-in router, as shown in Figure 14.
3 Detailed Description Table 3 CCU Configuration Basic CCU Settings Advanced CCU Settings Before the system can pass traffic, input or modify the following CCU parameters: • CCU Ethernet IP address • CCU radio IP address • Gateway router IP address • Radio frequency Once the system is passing traffic, you can start to configure and fine tune the following CCU features and functions: • Grade of Service • DHCP relay • Port filtering • SNTP time clock • SNMP communities For instructions on how to set the
3 Detailed Description Table 5 End-user PC Configuration Basic End-user PC Settings Advanced End-user PC Settings In addition to the above CCU and EUM settings, the end-user’s PC must be assigned an IP address and subnet, and a static gateway address.
3 Detailed Description EUM Registration EUMs need to register with the CCU before user traffic can pass between the LMS4000 900 MHz Radio Network and the end user. The heart of EUM registration is the Authorization Table, discussed in Authorization Table (CCU only) on page 189. The EUM registration process is as follows: 1. The system operator enters the EUM’s grade of service in the CCU Authorization Table, described in Authorization Table (CCU only) on page 189. 2.
3 Detailed Description Addressing of IP Packets Figure 16 shows how the source and destination MAC and IP addresses are sent in IP packets travelling between the end-user’s PC and the Internet network servers.
3 Detailed Description 5. If the route to the destination is through the CCU Radio Port, then the CCU obtains the destination Ethernet MAC address from the ARP Table, described in ARP Table (CCU and EUM) on page 187. If the destination is not listed in the ARP Table, the CCU obtains its MAC address by issuing an ARP query. Once it gets the MAC address, it adds the entry to the ARP Table. 6.
3 Detailed Description 10. If the IP address is the same as either the CCU radio or Ethernet IP address, the packet is forwarded to the CCU application; otherwise, the CCU gets the appropriate gateway IP address from the Routing Table and the gateway MAC address from the ARP Table, and then sends the packet to the gateway (most likely the NAP router) through the Ethernet port. NOTE: The CCU and EUM pass only IP or ARP packets.
3 Detailed Description The channel bandwidth also determines the minimum adjacent channel spacing for colocated CCUs. Channels There are 101 channels in the band, set in 0.2 MHz increments: Table 6 LMS4000 900MHz Radio Network Channelization Channel Center Frequency Lowest channel 905.0 MHz ... 905.2 MHz ... 905.4 MHz ... ... ... 924.8 MHz Highest channel 925.
3 Detailed Description • Interference suppression: The same mechanism that de-spreads the desired signal in the receiver, spreads undesired signals, which then appear to the receiver as lower levels of RF noise. This effect is illustrated in Figure 18. Desired Signal Interferer Becomes Desired Signal Inteferer Before De-spreading Figure 18 After De-spreading Effect of Despreading Data Rate The raw channel bit rate is 2.75 Mbps. The maximum data rate presented to the MAC layer is 2.
3 Detailed Description The CCU and EUM transmit power can each be set to +15 dBm (LOW power setting) to address special or regional applications of the LMS4000, or for bench testing. Receive Sensitivity The receive sensitivity (received signal required to attain a raw data BER of 10-5 or better using 1000-byte packets) of the CCU and EUM is < -86 dBm, measured at the unit’s RF connector. Antenna Connector The RF connector used on the CCU and EUM is a WaveRider-proprietary connector.
3 Detailed Description NLOS exists when the path between the CCU and EUM is obstructed, or partially obstructed, by terrain, buildings, or foliage. NLOS is illustrated in Figure 19. Since radio waves reflect, refract, and diffract, a non line of sight path does not necessarily mean the EUM-CCU radio link does not have enough signal margin. It simply means that the path loss is be greater than the LOS path loss.
3 Detailed Description To illustrate the impact that proper siting of the CCU has on the LM4000 radio coverage, consider the three cases shown in Figure 20. EUM-1 Case 1 Unobstructed Path EUM-2 Case 2 Path Obstructed in Vicinity of EUM CCU Case 3 Path Obstructed in Vicinity of CCU EUM-3 Figure 20 Examples of Radio Paths • Case 1 is a clear, unobstructed path between the CCU and the EUM, with full Fresnel clearance.
3 Detailed Description You can predict the amount of path loss for each of these cases, as illustrated in Figure 21.
3 Detailed Description The following key conclusions that can be drawn from the simple example and analysis shown above: • Coverage range and fade margins are maximum when paths are clear and unobstructed. • Coverage range and fade margins are reduced for specific EUMs if there is obstructing clutter and terrain in the vicinity of these specific EUMs. • Coverage range and fade margins are reduced for all EUMs if there is obstructing clutter or terrain in the vicinity of the CCU.
3 Detailed Description 3.5.2 MAC Layer (Polling MAC) EUM States The LMS4000 900 MHz Radio Network data transmission is based on a WaveRider’s patented polling algorithm, which takes advantage of patterns found in typical Internet usage. Based on the EUM’s subscribed grade of service and current traffic level, the Polling MAC continuously adjusts the rate at which the EUM is polled. This process is illustrated in the EUM State Diagram in Figure 22.
3 Detailed Description If an EUM is issued a deregistration request, for any reason, or if it has no traffic for an extended period of time, 12 hours or so, its state changes back to unregistered. Basic Operation of the Polling MAC The Media Access Control (MAC) layer determines which unit (CCU or EUM) gets to transmit and when it gets to transmit. Through the MAC layer, the CCU determines which associated EUM gets to transmit next and indicates to the EUM that it can transmit by polling it.
3 Detailed Description have most of the channel bandwidth to themselves. This over-subscription model is the basis of Ethernet, DOCSIS cable networks, 802.11 radio networks, Bluetooth, and on a larger scale, the public switched telephone network. If a significant portion of the network traffic does not meet this typical bursty model, the Polling MAC adjusts to maximize the user capacity. In this case, the maximum number of users is less than the case where most of the traffic is bursty.
3 Detailed Description Grade of Service (GOS) In the Polling MAC, the grade of service (GOS) determines how often, and when, an associated EUM is polled. Since the EUM can only send one packet each time it is polled, the data rate is related to the polling rate. Operational objectives that are factored into the determination of the basic polling rate include the following: • Maximize overall user capacity and minimize the overhead related to empty polls.
3 Detailed Description In determining the order in which to poll the EUMs, the CCU tries to • ensure consecutive polls of an EUM occur within the range defined by the EUM's grade of service, • maintain the average time between polls defined by the grade of service, and • divide the total number of polls among EUMs consistent with the grades of service of the EUMs being polled.
3 Detailed Description Table 8 Factory Default GOS Configuration File Service Class Polling Rate (polls/second) FTP Rate (see note) Operator Assigned Best Effort 1 - 34 0 - 384 kbps Yes Bronze 1 - 90 0 - 1024 kbps Yes Silver 12 - 22 128 - 256 kbps Yes Gold 22 - 46 256 - 512 kbps Yes Broadcast Varies with channel load, from 16 to 935 Not applicable No Denied 0 0 Yes NOTE: While recognizing that the performance of data transmission through packet radio networks is randomly depen
3 Detailed Description Transmit Queue Limits CCU transmit buffer space is a limited resource shared between the EUMs. If more traffic is received at the CCU for transmission to an EUM than can actually be transmitted to it, that EUM might eventually use up all available CCU buffer space, effectively starving all other users. Therefore, the number of packets in each EUM's transmit queue is intentionally limited.
3 Detailed Description To illustrate the output of the model, consider the following example. First of all, make the following general assumptions: • LMS4000 900 raw channel rate is MHz 2.
3 Detailed Description performance based on the number of EUMs that are associated at any given time, as is illustrated in Figure 24.. 30 Frequency (%) 25 20 15 10 5 0 0 1 2 3 4 5 6 7 8 9 Associated EUMs Figure 24 Associated EUMs — 100 EUMs, 60 kbyte HTTP every 2 minutes Of the 100 EUMs, each is associated at random times and for random intervals, so the probability of having more than ‘n’ EUMs associated must be determined statistically.
3 Detailed Description By increasing the number of EUMs to 300 and maintaining the same level of traffic per EUM, the modelled performance becomes Probability that Performance was Exceeded 1 0.8 0.6 0.4 0.2 0 0 500 1000 1500 2000 Performance (kbps) Figure 25 Net Throughput per EUM — 300 EUMs, 60 kbyte HTTP every 2 minutes From Figure 25, each of the 300 end users can expect a net throughput better than 300 kbps 80% of the time, and better than 750 kbps 20% of the time.
3 Detailed Description All of these charts illustrate that many (LMS4000) users can share the limited bandwidth of the channel, yet most of the time, each perceives that they have most of the channel to themselves. Atypical Applications The Polling MAC has been optimized for normal user applications. One basic assumption that has been made in the design of the Polling MAC is that users are only associated for a small fraction of the time they are sitting in front of their computers.
3 Detailed Description • Pings (interval is typically 1 second): WaveRider recommends the operator avoid running applications that generate a lot of pings, such as What’s Up Gold. • Network gaming (interval is typically 0.25 seconds): WaveRider can provide a GOS class for managing this kind of traffic if specific end users are running this type of application. • SNMP poll (interval is typically 30 seconds): This traffic is usually generated by the operator.
3 Detailed Description the call may be affected as other users become associated, increasing the polling interval beyond 20 ms. Since the grade of service applies to an EUM and not to an individual service, a VoIP user would have to be given a very high grade of service, to the possible detriment of other end users. 3.6 CCU and EUM Feature Description 3.6.1 DHCP Relay IP address information for CCUs and EUMs are manually entered.
3 Detailed Description The gateway router can provide DHCP server functionality, or you can implement a dedicated DHCP server, as shown in Figure 27. NMS Station Internet Router Switch DHCP Server DHCP Request (UDP) DHCP Response (UDP) EUM3000 Antenna DHCP Request CCU3000 (with DHCP Relay enabled) Figure 27 End-user Computer (with DHCP enabled) DHCP Response (layer-2 messages) DHCP Relay 3.6.2 Port Filtering The CCU and EUM both support TCP and UDP port filtering.
3 Detailed Description 3.6.3 SNTP/UTC Time Clock The Simple Network Time Protocol (SNTP)/UTC feature provides LMS4000 devices with an accurate clock for time stamping events in the log file. SNTP/UTC Time Clock operation is illustrated in Figure 28.
3 Detailed Description CAUTION: The local host entry, 127.0.0.1, is required to avoid the problem where the CCU cannot find a real NTP server (i.e., if the network is down). 3.6.4 Customer List For each EUM, the system operator can control the number of end-user computers that can access the LMS4000 network for the purpose of controlling network performance or service differentiation. The use of this list is described in Customer Table (EUM only) on page 192. 3.6.
3 Detailed Description CAUTION: By convention, most equipment ships with the default community strings defined in Table 9. WaveRider recommends that you change the community strings before you bring the LMS4000 equipment online, so that outsiders cannot see information about the internal network or configure system components. Management Information Bases (MIBs) All messages sent between the SNMP server and a network device are based on number codes.
4 IP Network Planning This section describes a plan for assigning IP addresses to LMS4000 900 MHz Radio Network components. 4.1 LMS4000 IP Addressing Before discussing IP planning, there are a few concepts that are worth reviewing. The first concept is that in the LMS4000 900 MHz Radio Network, IP addresses are assigned to devices for several reasons: • The device is a router, such as the gateway (NAP) router or the CCU. IP addresses are required for each router port.
4 IP Network Planning The second concept is the segmentation of the LMS4000 network into distinct subnets, as illustrated in Figure 29. Public Network Private Network CAP01, CCU01 Radio Subnet End Users ... ... CAPn, CCUm Radio Subnet End Users ... ... CAP15, CCU03 Radio Subnet End Users CAP01, CCU01 Router Application ... CCU Ethernet Subnet Internet Gateway (NAP) Router CAPn, CCUm Router Application ...
4 IP Network Planning • CAP-NAP backhaul equipment, if provisioned • CAP and NAP UPS, if provisioned • Ethernet switches • SNMP manager, if provisioned • Gateway (NAP) router Ethernet port The number of CAPs is limited by the capacity of the gateway (NAP) router. WaveRider suggests allocating a minimum of 256 addresses to the CCU Ethernet subnet, which accommodates 15 CAPs and requires a 24-bit subnet mask. 4.
4 IP Network Planning CAP15, CCU03 Ethernet port • 192.168.10.237 /24 As noted above, the IP addressing plan for each CCU radio subnet should allow for growth to a maximally equipped system. Providing 601 IP addresses on the same subnet requires a subnet with a 22-bit mask, for example 172.16.0.0 / 22.
4 IP Network Planning 4.3 Network Address Translation The following address translation alternatives are listed for reference purposes. Choose the best alternative for your system. Your choice depends on the number of available registered IP addresses. It also depends on the nature of your subscriber base; for example, static NAT may be required to support some of your business users, but dynamic NAT may be adequate for most of your home users.
— This page is intentionally left blank —
5 Radio Network Planning An important task in the implementation of LMS4000 900MHz Radio Networks is RF system planning and design. Whether you are deploying a single CCU or a complex multi-CAP, multiCCU network, proper system design is necessary to provide and maintain high-quality service to end users in your target serving area. 5.1 Design Methodology The following sections are not intended to provide detailed system design instructions; instead, they provide system design guidelines.
5 Radio Network Planning In all cases, these wide-ranging factors drive the system design and as a result, no two systems will be implemented the same way. The design methodology presented in this chapter uses a building-block approach. If the system you are designing is based on a single CCU, you need only read and learn about the guidelines presented in Basic System Design on page 60.
5 Radio Network Planning the spectrum. Keep in mind that one of the major attractions of the ISM band is the fact that it is license free; as such, it is shared spectrum. To regulate the band, regulatory bodies, such as FCC and Industry Canada, require that new operators in the band take responsibility for resolving interference issues when their newly installed system interferes with systems that are already in operation.
5 Radio Network Planning Figure 30 shows an actual spectral sweep, recorded using a spectrum analyzer as part of a spectral survey, which shows the location of the cellular and paging transmitters in relation to the ISM band. Note the relative levels of the interfering signals.
5 Radio Network Planning approach would be to assign a higher frequency to sector A, such as 915MHz or 925MHz. Sector C Sector B CAP Sector A Cellular Transmitter Figure 31 Network Design in the Presence of Out-of-band Interference 5.2.5 Using Bandpass Filters at CAP Sites WaveRider provides high-quality, specially designed bandpass filters for use with the CCU. These filters reduce the effect of unwanted out-of-band and off-channel in-band interference.
5 Radio Network Planning engineer, as specified in Appendix A Specifications, the minimum separation between colocated channels is 6.6 MHz (an orthogonal adjacent channel) and requires a C/I ratio of 50 dB or better for non-interfering CCU operation. Once the antenna system gains and power output of the CCU radio are accounted for, the only way to practically provide adequate isolation for the required adjacent channel isolation is through the use of bandpass filters. 5.2.
5 Radio Network Planning The location of the CAP site in relation to the serving area determines whether the site will be a corner- or center-illuminated cell. Figure 32 illustrates the difference between these two methods of illumination.
5 Radio Network Planning configuration would triple the traffic-handling capacity of the site. Figure 33 illustrates the sectoring of a previously center-illuminated omnidirectional cell. CAP Figure 33 Sectored Cell Corner Illumination Corner illumination is generally used when it is not possible to establish a suitable CAP site near the middle of the target serving area.
5 Radio Network Planning multiple users, likely generates a lot more daytime traffic than a simple residential service used for Web browsing and email. In summary, the network design engineer must be aware of the intended use of the system — the customer profile, tariff rates, and committed grades of service — since these factors all influence the traffic demand on the system. 5.
5 Radio Network Planning information). Throughout this manual, however, WaveRider has referred to the standard frequency set shown in Table 11. Table 11 Standard Frequency Set 905.0MHz 915.0MHz 925.0MHz The standard frequency set represents a convenient and safe set of frequency assignments.
5 Radio Network Planning As an example, consider the frequency plan shown in Table 13. Table 13 Sample Frequency Plan — Multi-CAP Design Frequency Set A 905.0 - 911.6 - 918.4 - 925.0 Frequency Set A’ - 908.4 - 915.0 - 921.6 - In Table 13, Frequency Set A uses the minimum frequency spacing that should be considered for a single CAP site, 6.6MHz. Frequency Set A’ represents a set of channels which are interstitial to those in Frequency Set A.
5 Radio Network Planning provide enough time and resources for the engineering team to verify the design in the field through testing and signal-level measurements. Once you have established your CAP sites on the air, you can verify received signal levels throughout the network using a portable spectrum analyzer. You can then compare these with those predicted by the RF system design.
5 Radio Network Planning 5.3.6 Summary of RF Design Guidelines A summary of guidelines presented in this chapter can be found in Table 14. Table 14 Summary of RF Design Guidelines DO • DO read and understand this chapter before you start your system design activity. • DO contact WaveRider Professional Services Group if you need assistance with spectral surveys, RF coverage analyses, or system engineering. • As a first step, always DO a spectral survey.
— This page is intentionally left blank —
6 Installation/Diagnostic Tools The CCU and EUM are equipped with the following features that facilitate unit installation, operation, maintenance, monitoring, and diagnostics: • Indicators and Connectors on page 74 • Command-line Interface on page 76 • EUM Configuration Utility on page 77 • RSSI/Tx Quality/Antenna Pointing on page 77 • Transfer a File to or from a CCU Using FTP on page 78 • Operating Statistics on page 79 • SNMP on page 80 • Field Upgrade Process on page 80 • FTPing CCU
6 Installation/Diagnostic Tools 6.1 Indicators and Connectors The CCU and EUM are equipped with LED indicators that provide a visual indication of the status of the unit and its interfaces. The EUM LED indicators are illustrated in Figure 34, the CCU LED indicators in Figure 35, and a detail view of the Ethernet connector in Figure 36.
6 Installation/Diagnostic Tools 6.1.1 Network LED Table 15 Network LED LED State Ethernet Traffic Status OFF No Ethernet traffic present ON Solid Ethernet traffic present but no radio traffic Fast Flash Ethernet and radio traffic present NOTE: A Network LED fast flash flashes at 2.5 Hz, 50% duty cycle, about two or three times per second. 6.1.2 Radio LED In the following table, RSS is the Radio Signal Strength, in dBm.
6 Installation/Diagnostic Tools 6.1.4 Ethernet LEDs The Ethernet connector used in the CCU and EUM, shown in Figure 36, has two LEDs. These LEDs are described in Table 18. Traffic LED Link LED Figure 36 Ethernet LEDs Table 18 Ethernet LEDs LED State Ethernet Status Link LED If the Link LED is ON, the Ethernet physical connection is configured and working properly.
6 Installation/Diagnostic Tools Table 19 Console Settings 6.3 Bits per second 9600 Data bits 8 Parity None Stop bits 1 Flow Control None EUM Configuration Utility The EUM can also be configured and monitored using the EUM Configuration Utility, a Windows-based graphical user interface (GUI) running on a PC. The PC connects to the CCU or EUM through the DB-9 console port, the unit Ethernet port, or from anywhere in the LMS4000 900 MHz Radio Network.
6 Installation/Diagnostic Tools RSSI: RSSI: RSSI: RSSI: RSSI: RSSI: 73 73 73 74 73 74 865; 932; 933; 709; 743; 747; 0; 0; 0; 0; 0; 1; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0; 0% 0% 0% 0% 0% 0% Console> Adjust the antenna location and pointing for maximum RSSI. You may need to adjust the antenna and then step back each time to read the RSSI, so you do not obstruct the signal from the CCU.
6 Installation/Diagnostic Tools Hash mark printing On ftp: (2048 bytes/hash mark) . ftp> binary 200 Type set to I, binary mode ftp> get sa1110.bak 200 Port set okay 150 Opening BINARY mode data connection ############################################################################ ### ############################################################################ ### ################################################################## 226 Transfer complete ftp: 463713 bytes received in 10.80Seconds 42.
6 Installation/Diagnostic Tools 6.7 SNMP The CCU and EUM are SNMP-ready. To make use of the CCU and EUM SNMP capabilities, you must obtain the associated WaveRider MIBs from the technical support page at www.waverider.com and install them on your SNMP manager (SNMPc, or HP OpenView, for example).
6 Installation/Diagnostic Tools If the hash code comparison is successful, then the existing executable software is copied as a backup (.bak file), and the newly downloaded image becomes the unit executable. The unit is automatically rebooted. If the new executable is found to be corrupt for any reason, then the unit reverts to the backed-up, older image. 6.
6 Installation/Diagnostic Tools CAUTION: Use FTP to transfer configuration files between like units only; for example, from a CCU to another CCU. (Ensure the file is transferred using image or binary mode.) Although port filters are used in both the CCU and EUM, there may be differences between the port configuration file for the CCU and the port configuration file for the EUM.
7 Configuring the CCU This section explains the following procedures and topics: • CCU and EUM Serial Number, MAC Address, and Station ID on page 84 • Setting the CCU Password on page 84 • Configuring the CCU RF Parameters on page 85 • Configuring CCU IP Parameters on page 86 • Configuring DHCP Relay on page 88 • Configuring Port Filtering on page 89 • Configuring the SNTP/UTC Time Clock on page 90 • Configuring SNMP on page 93 • Adding EUMs to the Authorization Table on page 95 Before y
7 Configuring the CCU CAUTION: When entering IP addresses in the CCU or EUM, note that a leading ‘0’ forces the CCU or EUM operating system to interpret the entry as octal rather than decimal. For example, pinging 10.0.2.010 actually pings 10.0.2.8 7.
7 Configuring the CCU 4. At the Verify password prompt, type the new password again. The system displays a message that your password has been successfully changed. Example: Console> password Enter Current Password: ******** Enter New Password: ******** Verify password: ******** Saving new password Password Changed Console> CAUTION: Remember to record the password. Unlocking the CCU can only be performed by contacting WaveRider Technical Support. 7.
7 Configuring the CCU • Saves the new settings, • Reboots the CCU so that the new parameters take effect, and • Displays the CCU RF parameters. Console> Console> radio frequency 9170 Console> radio rf high Console> Console> save Basic Config saved Port Filter Config saved sntp cfg file saved Route Config saved Authorization Database saved DHCP Server Config saved Console> Console> reset rebooting CCU ... (... Power On Self Test ...) WaveRider Communications, Inc.
7 Configuring the CCU To set the CCU radio IP address 1. Type ip radio and press Enter. • is the CCU radio IP address. • is the net mask. 2. Type save or commit and press Enter. 3. Before the new CCU radio IP address will take effect, you must reboot the CCU by typing reset and pressing Enter NOTE: The CCU Ethernet and gateway IP addresses must be on the same subnet, as explained in LMS4000 IP Addressing on page 53.
7 Configuring the CCU Ethernet Net Mask : ffff0000 Gateway IP Address: 10.0.0.1 Radio IP Address: 10.5.0.1 Radio Net Mask : ffff0000 Console> 7.5 Configuring DHCP Relay To configure DHCP relay • Determine the DHCP server IP address. • Enable DHCP Relay. • Add the DHCP server to the CCU. To add a DHCP server 1. Type dhcp relay add and press Enter. • is the IP address of the DHCP server you want to add. • is the net mask of the DHCP server. 2.
7 Configuring the CCU DHCP Server Config saved Console> Console> dhcp relay DHCP Relay Enabled: DHCP Server Table: DHCP Server Table: IP Address: 192.168.50.1 Mask : ffffff00 IP Address: 192.168.50.15 Mask : ffffff00 Console> 7.6 Configuring Port Filtering To add a port filter • Determine the port number you want to filter. • Determine whether you want to filter UDP, TCP, or both types of packets. • Add the port filter to the CCU. To add a port filter 1.
7 Configuring the CCU sntp cfg file saved Route Config saved Authorization Database saved DHCP Server Config saved Console> Console> port PORT FILTERS Port Filter --------------------------------137 both 138 both 139 both 1512 both ---------------------------------Console> NOTE: The EUM factory default settings have ports 137, 138, 139, and 1512 filtered out for both TCP and UDP, to prevent Network Neighborhood from seeing other end users’ computers. 7.
7 Configuring the CCU Once again, do not delete 127.0.0.1. If you inadvertently delete it from the list, when you use the flush command, for example, it must be re-entered. NOTE: It is a good idea to ping the time servers from the CCU before adding them, to ensure you have connectivity. To set the SNTP client resynchronization time The SNTP client resynchronization period is the time between a successful CCU resynchronization and the next CCU resynchronization attempt, typically set to 3600s (one hour).
7 Configuring the CCU • Adds a local NTP server, IP address 10.0.0.1, • Sets the resynchronization time to 3600 seconds, • Sets the retry time to 30 seconds, • Enables the SNTP client, • Enables the SNTP relay, • Saves the new entries, • Displays the SNTP configuration and NTP server list, and • Displays the system time. Example: Console> time flush Console> time add 127.0.0.1 Console> time add 10.0.0.
7 Configuring the CCU 7.8 Configuring SNMP To fully configure SNMP • Set the SNMP contact (name of the WISP, for example). • Set the SNMP system location (physical location of the CCU, for example). • Add an SNMP read community. • Add an SNMP write community. • Add an SNMP trap community. To set the SNMP contact 1. Type snmp contact and press Enter. • is text field, often used for a contact name and phone number, a URL, or an email address, from 1-80 characters in length. 2.
7 Configuring the CCU Example: The following example • Sets the SNMP contact as WaveRider, • Sets the SNMP location as Calgary_South, • Adds SNMP read community WaveRider_Calgary, • Adds SNMP write community WaveRider_Calgary, • Adds SNMP trap server WaveRider_Calgary, IP address 10.0.1.68, • Saves the new settings, and • Displays the SNMP settings.
7 Configuring the CCU 7.9 Adding EUMs to the Authorization Table To add EUMs on the system, enter them in the CCU Authorization Table. To add an EUM to the CCU Authorization Table 1. Type auth add and press Enter. • is the hexadecimal representation of the EUM ID • is the grade of service that you want to assign to the EUM, one of: • be (best effort), • bronze, • silver, • gold, or • denied. 2. Type save or commit and press Enter.
— This page is intentionally left blank —
8 Configuring the EUM This chapter covers the following procedures: • Setting the EUM Password on page 98 • Configuring the EUM RF Parameters on page 98 • Configuring EUM IP Parameters on page 99 • Configuring Port Filtering on page 101 • Configuring SNMP on page 102 • Configuring the Customer List on page 104 Before you configure the EUM • Familiarize yourself with the CLI commands, syntax and shortcuts, outlined in Appendix C on page 163.
8 Configuring the EUM 8.1 Setting the EUM Password To Change the EUM Password 1. Type password and press Enter. 2. At the Enter Current Password prompt, type the old password. 3. At the Enter New Password prompt, type the new password. TIP: Passwords are alphanumeric and case-sensitive. For example, “abc” is not the same as “aBc”. 4. At the Verify password prompt, type the new password again. The system displays a message that your password has been successfully changed.
8 Configuring the EUM 2. Type save or commit and press Enter. 3. Before the new power level will take effect, you must reboot the EUM by typing reset and pressing Enter. Example: The following example • Sets the EUM operating frequency to 917 MHz, • Sets the transmit power level to high, • Saves the new settings, • Reboots the EUM so that they new parameters take effect, and • Displays the EUM RF parameters.
8 Configuring the EUM CAUTION: The EUM only accepts subnet masks using the shorthand notation; for example, it accepts ‘16’, but not ‘ffff0000’ or ‘255.255.0.0’. 2. Type save or commit and press Enter. 3. Before the new EUM Ethernet IP address will take effect, you must reboot the EUM by typing reset and pressing Enter. To set the EUM gateway IP address 1. The EUM gateway is the CCU radio, so the EUM gateway IP address is the CCU radio IP address. 2. Type ip gateway and press Enter.
8 Configuring the EUM 8.4 Configuring Port Filtering To add a port filter: • Determine the port number you want to filter. • Determine whether you want to filter UDP, TCP, or both types of packets. • Add the port filter to the EUM. To add a port filter 1. Type port add and press Enter. • is the number of the port you want to filter. • is the type of IP packet you want to filter, either udp, tcp, or both. 2. Type save or commit and press Enter.
8 Configuring the EUM 8.5 Configuring SNMP To fully configure SNMP • Set the SNMP contact (name of the WISP, for example). • Set the SNMP system location (physical location of the EUM, for example). • Add an SNMP read community. • Add an SNMP write community. • Add an SNMP trap server. To set the SNMP contact 1. Type snmp contact and press Enter. • is a name and phone number, a URL, or an email address, from 180 characters in length. 2. Type save or commit and press Enter.
8 Configuring the EUM Example: The following example • Sets the SNMP contact as WaveRider, • Sets the SNMP location as Calgary_South, • Adds the SNMP read community WaveRider_Calgary, • Adds the SNMP write community WaveRider_Calgary, • Adds the SNMP trap server WaveRider_Calgary, IP address 10.0.1.68, • Saves the new settings, and • Displays the SNMP settings.
8 Configuring the EUM 8.6 Configuring the Customer List You can set the maximum number of customers or PCs (customer_max) that can concurrently access the radio link through the EUM, as described in Customer Table (EUM only) on page 192. CAUTION: The simulation data presented in Performance Modelling on page 42 is based on one end user (one PC) per EUM.
9 9.1 Installing the EUM Before you Start the EUM Installation Before you start the EUM installation, ensure the following points have been addressed: • The EUM has been configured with at least the following settings: • • • • IP address Subnet mask Gateway IP address Radio frequency • The CCU network is installed and verified. • DHCP relay is enabled at the CCU, with network access to a valid DHCP server.
9 Installing the EUM 9.2 Other EUM Programming Considerations Although the IP settings identified above are required for basic EUM operation, you should also consider pre-configuring the following EUM parameters: SNMP SNMP communities can be configured in the EUM to enable remote monitoring of the EUM using an SNMP manager. Refer to Configuring SNMP on page 102. Customer List The factory default configuration allows only one PC to be logically connected to the EUM at any given time.
9 Installing the EUM 11. Configuring the Browser Application on page 119 12. Completing the Installation on page 120 13. Baselining the Installation on page 120 9.4 Installation Procedures 9.4.1 Opening the Box Before you install the EUM components, verify that the EUM kit is complete.
9 Installing the EUM 9.4.2 Turning off the End-user’s Cordless Phones Turn off all cordless phones in the customer’s premises, and any other equipment that uses the 900MHz ISM band. Once the installation is complete, turn this equipment back on. 9.4.3 Choosing a Location for the EUM and Antenna The location of the antenna has a significant effect on the performance of the EUM installation.
9 Installing the EUM When you have completed the above tasks, connect the EUM AC/DC adaptor to an AC power bar or outlet. Bracket Antenna Antenna Step 1 Antenna Cable Connector Ethernet 2 1 Step 3 AC Cable Pow er Bar Step 2 DC Cable EUM Connector DC Power AC/DC Adapter Connector Denotes reserved ports. Do NOT Connect. Figure 38 Connecting the EUM Components To Connect the EUM Components 1.
9 Installing the EUM NOTE: The DC power cable features a secure locking connector. To disconnect the cable, pull the collar back on the connector, then continue pulling to detach the DC power cable from the EUM. The EUM uses a custom antenna cable and connector. If you need to extend this cable, contact WaveRider. 3. Connect the AC power cord between the AC/DC adaptor and either an AC power bar (preferred) or AC outlet (Figure 40). The EUM immediately powers up since it does not have an ON/OFF switch.
9 Installing the EUM 9.4.6 Positioning the Antenna 1. To begin with, point the antenna in the general direction of the CCU, as shown in Figure 42: To Base Station Figure 42 Preliminary Orientation of the Antenna (Top View) As illustrated, for maximum signal reception, point the concave surface of the antenna toward the CCU, and ensure your body (including fingers) are not between the antenna and the CCU. 2. Monitor the Radio LED, shown in Figure 41 on page 110 and refer to Table 21.
9 Installing the EUM 9.4.7 Mounting the Antenna The antenna bracket is designed to accommodate the RF cable and act as a strain relief. To Mount the Antenna 1. Thread the attached antenna cable through the guides in the back of the antenna bracket, as necessary. Antenna Cable Bracket Guides Antenna Bracket Figure 43 NOTE: Rear View of Antenna Bracket Bending the antenna cable too sharply can degrade EUM performance. Never allow less than a 1.25 cm (0.5 in.) bend radius.
9 Installing the EUM Figure 44 shows the location of the spring clip, suction cup holes, and screw holes on the antenna bracket. Spring Clip Suction Cup Hole Screw Hole Screw Hole Suction Cup Hole Figure 44 Antenna Bracket Components Table 23 Surface Mounting Options for the Antenna Side Mount Mount the antenna on a wall, window, window frame, or solid furniture with spring clip side closest to the ceiling. Top Mount Hang the antenna from a ceiling or the shelf of a bookcase.
9 Installing the EUM WARNING! The antennas for the EUM must be fix-mounted, indoors or outdoors, to provide a separation distance of 20cm or more from all persons, to satisfy RF exposure requirements. The distance is measured from the front of the antenna to the human body. WaveRider recommends installing the antenna in a location where personnel are not able to bump into it, obstruct the signal from the base station, or trip over antenna cables. 3.
9 Installing the EUM 9.4.8 Connecting the End-user’s PC 1. Connect the end-user’s PC, shown in Figure 46, by attaching the crossover Ethernet cable that is included with the kit between the Ethernet port on the end-user’s computer and the Ethernet port on the EUM. Bracket Antenna Antenna omputer Step 4 Ethernet Cable 4 Step 1 Antenna Cable 4 Connector Ethernet 2 1 Step 3 AC Cable Power Bar Step 2 DC Cable Connector EUM DC Power AC/DC Adapter Connector Denotes reserved ports. Do NOT Connect.
9 Installing the EUM 9.4.9 Obtaining Valid IP Addresses for the End-user’s PC 1. To obtain IP addresses for the end-user’s PC, including the PC IP address, Gateway IP address, and DNS server address, the PC must request an update from the DHCP server.
9 Installing the EUM To illustrate data link testing between the PC and the EUM, consider the sample configuration shown in Figure 47. Internet Gateway Router Ethernet crossover cable Radio Link End-user's PC IP Address 10.5.6.117 Net Mask 16 Gateway IP 10.5.0.1 EUM3000 IP Address Net Mask Gateway IP CCU3000 Radio IP Address 10.5.0.1 Net Mask 16 10.5.4.117 16 10.5.0.
9 Installing the EUM Ping statistics for 10.5.4.116: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\> If you are not able to the EUM from the PC, go to Troubleshooting on page 121. Testing the Data Link from the End-user’s PC to the Network Once the connection from the PC to the EUM is confirmed, ping the EUM gateway address from a PC DOS window.
9 Installing the EUM Testing the Data Link from the End-user’s PC to the Internet Use the following test to determine whether the end-user’s PC can communicate with the Internet. Pinging an Internet site from the PC using the site’s IP address: C:\>ping 207.23.175.75 Pinging 207.23.175.75 with 32 bytes of data: Reply Reply Reply Reply from from from from 207.23.175.75: 207.23.175.75: 207.23.175.75: 207.23.175.
9 Installing the EUM 9.4.12 Completing the Installation 1. Configure the remaining PC applications, as required. 2. Re-activate the end-user’s cordless phones, and any other 900MHz ISM-band equipment that was turned off at the beginning of the installation. Note the following points: • • • Cordless phones operating in the 900MHz ISM band can disrupt service to the EUM if precautions are not taken. Browse to http://speed-test.
9 Installing the EUM Gateway IP Address: 10.5.0.1 Console> Console> radio RF Power: HIGH Radio Frequency: 9170 Console> Console> ra rssi Press any key to stop RSSI RSSI: 44 RSSI: 60 RSSI: 59 RSSI: 62 RSSI: 58 RSSI: 60 RSSI: 45 RSSI: 61 RSSI: 60 RX; 0; 712; 706; 812; 819; 809; 829; 834; 818; TX; 0; 0; 0; 0; 0; 0; 0; 0; 0; R1; 0; 0; 0; 0; 0; 0; 0; 0; 0; R2; 0; 0; 0; 0; 0; 0; 0; 0; 0; R3; 0; 0; 0; 0; 0; 0; 0; 0; 0; F;Retry% 0; 0% 0; 0% 0; 0% 0; 0% 0; 0% 0; 0% 0; 0% 0; 0% 0; 0% EUM Console> 9.4.
9 Installing the EUM A: There are two conditions that might prevent or compromise Internet access by the end-user through the EUM, even when the network is operating properly and the radio signal strength is adequate: Improper PC configuration If the PC IP address set is incorrect, then communications between the PC and the EUM will not be possible. If the DHCP function does not provide a valid IP address to the PC, then the PC IP address will have to be entered manually.
9 Installing the EUM Q: DHCP is not available on the network. Is there anything else I can do? A: DHCP is a tool that allows you to re-use IP addresses and simplifies the procedure for configuring the end-user PC. If DHCP is not available, the WISP must provide the installer with the following IP addresses for the end-user’s PC: • • • • PC IP address Subnet mask Gateway IP address DNS IP address These addresses can be directly entered into the end user’s PC through the operating system.
— This page is intentionally left blank —
10 Maintaining the Network The LMS4000 900MHz radio network requires virtually no maintenance. This chapter describes what you need to do to maintain the CCU and EUM operating environments.
10 Maintaining the Network When cleaning CCU and EUM components: • Use dry, static-free cloths to wipe dust from the devices. • Make sure you do not disconnect any cables or wires when cleaning. Checking the CCU Shelf Cooling Fans WARNING! Exercise caution when you are in close proximity to the CCU Shelf cooling fans. Disconnect AC power to the fans prior to handling.
11 Monitoring the Network Although there are a large number of detailed statistics available for the various data handling applications in the CCU (refer to Appendix H on page 223 for a complete list), there are only a few that are key for monitoring system performance on an on-going basis. These statistics are described in detail in the material below. 11.1 CCU Transmit Statistics As described in MAC Layer (Polling MAC) on page 36, the MAC continuously transmits polls to the EUMs.
11 Monitoring the Network Examining this statistic in more detail, txPayloads includes • Tx Data Payloads which, in turn, includes • • • data coming from the Ethernet port of the CCU (either end-user data or operator monitoring [SNMP] data), data coming from EUM-originated data payloads that have been “switched” to the CCU radio port (for transmission to other EUMs), and broadcast data to all EUMs(TxPayloadsBCast).
11 Monitoring the Network Table 27 Typical CCU Transmit Statistics Statistic Sample A tx Data Payloads 67,790 B tx Ctrl Payloads 901 C txPayloadsBCast 445 D txPayloads1Ok 66,001 E txPayloads2Ok 1,761 F txPayloads3Ok 281 G txPayloads4Ok 91 H txPayloadsFailRetry 102 I txPayloadsFailAssocDeleted 11 The objective of the first level analysis of this data is to determine the relative amount of radio traffic resulting from retransmissions. Ideally, the percentage would be 0.
11 Monitoring the Network Similarly, the percentage of payloads not delivered on the first transmission, but delivered on the second transmission = 1,761 / (68,235 - 66,001) = 78% It is generally a good indication if most payloads that fail on the first try are then successful with only one retry. The percentage of payloads that are not able to be delivered = 102 / 68,680 = 0.
11 Monitoring the Network 11.2 CCU Receive Statistics Similar to the case for CCU transmit statistics, there are several key CCU receive statistics that you can use to monitor on-going performance of the CCU radio network. When the CCU sends a directed poll to an EUM, it expects to get an acknowledgement.
11 Monitoring the Network 11.3 EUM Statistics Monitoring In general, the statistics collected at the EUM are the same as those collected at the CCU; however, there are some differences in meaning (see Appendix H). More significantly, of course, is that the EUM statistics are unique to the EUM, as opposed to the CCU statistics, which are a collective of the CCU and all EUM interactions. 11.3.1 EUM Transmit Statistics The relationships of the key EUM statistics are the same as those for the CCU.
11 Monitoring the Network As with the CCU transmit statistics, the following sample calculations can be made using the sample data from Table 29: Total number of desired payloads = B + C = 44,718 + 2 = 44,720 This is also equal to: (txPayloads1Ok + txPayloads2Ok + txPayloads3Ok + txPayloads 4Ok + txPayloadsFailRetry) = (36,889 + 5,216 + 1,489 + 553 + 573) = 44,720 NOTE: Due to real-time issues (the fact that at any given time, some packets are being processed or queued), the numbers frequently differ by th
11 Monitoring the Network The statistic rxPktsDuplicate measures the number of times the CCU sends the same packet of information more than one time. A high value of rxPktsDuplicate indicates that the acknowledgements from the EUM are not being properly received at the CCU. 11.3.3 User Data The actual user data is recorded by the statistics Rx Data Payloads and Tx Data Payloads. These statistics could be viewed as billable data and allow the operator to monitor actual usage at the EUM level.
12 Troubleshooting Troubleshooting an LMS4000 900 MHz radio network problem is an iterative process. First of all, you need to isolate the general location of the problem, then isolate the problem, and finally, determine the root cause of the problem.
12 Troubleshooting B. If only one EUM is affected: 12.1 • Verify that you can ping from the gateway router to other EUMs on the same CCU. If you cannot, go to A. above. • If this test is successful, go to EUM Troubleshooting on page 136. EUM Troubleshooting The following EUM troubleshooting process can be used at the time of the initial EUM installation or during follow-up service visits.
12 Troubleshooting To enable the capability, you can use the Windows utility, in Windows 95 and 98 operating systems, and the DOS utility in newer Windows operating systems. The command is used to test data links. A successful short ping test confirms connectivity but may not indicate link error rates that would cause failures in tests with longer packets. A test performed with a long-packet ping provides a better indication of the channel error rate.
12 Troubleshooting Table 30 Remote Troubleshooting — EUM (Service Not Available) What should I do? Confirm EUM status A B C D 138 What is a good result? What if I do not get a good result? Telnet to the CCU and go to the CLI prompt. Telnet is successful. Go to Test B. Check the upstream data path and equipment, or go to CCU Troubleshooting on page 145. Check the Authorization Table in the CCU. Affected EUM ID is not DENIED. The affected EUM is enabled and can transmit and receive data.
12 Troubleshooting Table 31 Remote Troubleshooting — EUM (Service Degraded) A Check the gateway to EUM link B C Confirm the status of the affected EUM D E F APCD-LM043-4.0 What does a good result mean? What if I do not get a good result? What should I do? What is a good result? From the Ethernet side of the CCU, the CCU with short and long pings. No failures or time-outs. The link to the CCU is OK. Go to Test B.
12 Troubleshooting Table 31 Remote Troubleshooting — EUM (Service Degraded) What should I do? TIP G Record key EUM statistics from (see Table 27 on page 129 and Table 28 on page 131), clear the statistics, then review and record the statistics after traffic has been passed for 10 or 15 seconds. What is a good result? The retransmission rate, defined in Monitoring the Network on page 127, is low. What does a good result mean? The slowdown is likely not due to the radio network.
12 Troubleshooting Table 32 Local Troubleshooting — EUM (Service Not Available) What should I do? What is a good result? What does a good result mean? What if I do not get a good result? Verify the data link Check the Ethernet LEDs on the PC and EUM Ethernet connectors. The Link LED is ON solid green, and the Traffic LED is flashing occasionally with traffic. Cable connection is good, and the Ethernet interfaces are active. Go to Test D. • Check the type of cable.
12 Troubleshooting Table 32 Local Troubleshooting — EUM (Service Not Available) What should I do? What does a good result mean? What if I do not get a good result? Through the DOS command line, 207.23.175.75 (WaveRider web site) No failures or time-outs. The data connection to the Internet is OK. Go to Test G. Verify network status. It is likely that all EUMs are affected. Through the DOS command line, www.waverider.com. No failures or time-outs.
12 Troubleshooting Table 33 Local Troubleshooting — EUM (Service Degraded) What should I do? Verify the logical data connection between the PC and EUM. What is a good result? What does a good result mean? Through the DOS command line, the EUM with short and long packets. No failures or time-outs. Confirms physical and logical connection to the EUM, and basic IP addressing. Go to C. Through the DOS command line, the CCU with short and long packets. No failures or time-outs.
12 Troubleshooting Table 33 Local Troubleshooting — EUM (Service Degraded) E F TIP G 144 What does a good result mean? What if I do not get a good result? What should I do? What is a good result? Open browser to http:// speed-test.net, run the download and upload tests. Throughput in both directions should be consistent with the subscribed service level, with an allowance for the overall traffic level on the CCU.
12 Troubleshooting 12.2 CCU Troubleshooting CCU troubleshooting can be broken down into several areas, based on the working history of the CCU, the nature of the reported problem, and the extent of the reported problem. For the purpose of this troubleshooting section, it is assumed that the CCU has been installed according to the guidelines provided by WaveRider and EUMs have been successfully deployed and operated.
12 Troubleshooting . Table 34 Remote Troubleshooting — CCU What should I do? What is a good result? Telnet to the CCU. Access to the CCU is available. Verifies network access connectivity down to the CCU level. Either the network connection to the CCU is down, or the CCU Ethernet port is not responding. Confirm the network connection to the CCU site. If OK, go to the local CCU tests outlined in Table 35 on page 147. Confirm EUM status at the CCU Enter the CLI, type .
12 Troubleshooting Table 34 Remote Troubleshooting — CCU Check for Key Statistics degradation What should I do? What is a good result? in the CLI, type . Key Statistics, described in Monitoring the Network on page 127, should meet general criteria listed, and/or be similar to past values. D What does a good result mean? No change in the interference environment indicated.
12 Troubleshooting Table 35 Local Troubleshooting — CCU What should I do? If a captive EUM cannot be accessed, even when set up in a high-signal receive area, replace the CCU. If access is still not possible, replace the CCU antenna system with a “test antenna”, located 15’ or so from the captive EUM, and repeat Tests G and H. TIP If only EUMs with high signal levels (i.e., typically those close to the CCU) can be accessed, suspect an interferer. Go to If You Have an Interferer on page 149.
12 Troubleshooting 12.3 If You Have an Interferer The presence of an interferer can cause a variety of performance problems in the radio network. These problems can be quite difficult to positively identify and track down. Typically, the presence of an interferer is first identified by eliminating other potential causes of the observed symptoms. Interferer problems can be inconsistent, in both the significance of the effect, as well as the duration, since interferers are frequently intermittent.
12 Troubleshooting resort. Otherwise, the level and location of the interferer has to be deduced from measurements available at the CCU and EUM. Several of these measurements are referenced in the preceding Troubleshooting sections. Some further clarifications and guidelines are listed here: 150 • A typical data transmission between the CCU and the EUM requires information packets to go both ways.
12 Troubleshooting 12.4 General Troubleshooting Information Table 36 provides troubleshooting tips related to general problems that you may be having with trying to operate over the network. Table 36 General Network Problems Symptom Potential Causes ARP table mismatches Network devices maintain an ARP table that matches an IP address with a MAC address. Every network device has a unique MAC address.
12 Troubleshooting Ethernet Cable Wiring Table 37 provides troubleshooting tips related to problems that you may be having with Ethernet cables. Table 37 Ethernet Cabling Problems Symptom Potential Causes • Unable to ping across a single piece of Ethernet cable. • Lose large-sized ping packets across a single piece of Ethernet cable. • Ethernet cable wired wrong. • Ethernet cable RJ-45 ends terminated incorrectly or badly. • Wrong cable type (crossover or straight-through) used.
12 Troubleshooting • Pin 4 = Blue • Pin 5 = White Blue • Pin 6 = Orange • Pin 7 = White Brown • Pin 8 = Brown For a crossover cable, one plug should be assembled as a standard and the other plug as follows: • Pin 1 = White Orange • Pin 2 = Orange • Pin 3 = White Green • Pin 4 = Blue • Pin 5 = White Blue • Pin 6 = Green • Pin 7 = White Brown • Pin 8 = Brown APCD-LM043-4.
— This page is intentionally left blank —
13 Specialized Applications The advanced capabilities of the LMS4000 900 MHz radio network modems can support a variety of special applications. 13.1 EUM Thin Route In some cases, it may be cost-effective to use an EUM to extend the reach of the LMS4000 900 MHz radio network to small numbers of outlying EUMs, as shown in Figure 49.
13 Specialized Applications In this EUM thin-route case, the traffic on the radio channel “b” network traverses two airlinks — the first from the users’ EUMs to the CCU on radio channel “b”, then the second from the thin-route EUM to the CCU on radio channel “a”. This situation reduces the available throughput of the CCU on radio channel “a” by the amount of the traffic on the radio channel “b” network.
Appendix A Specifications This appendix lists the following specifications for the LMS4000 900 MHz Radio Network, specifically the technical specifications for the CCU and EUM, configured for operation in the FCC/IC RF regulatory domain: • Radio Specifications on page 157 • Ethernet Interface Specifications on page 158 • Power Supply Specifications on page 158 • Environmental Specifications on page 158 Table 38 Radio Specifications Maximum Number of Operational CCUs and Orthogonal Channels 3 Max
Co-located Channel Set Center Frequencies (standard) 905 MHz, 915 MHz, 925 MHz Note: Other frequencies can be used, depending on site-specific considerations. Call WaveRider for more information. Modulation Scheme Based on DSSS (Direct-Sequence Spread Spectrum) signals, modulated with CCK (Complementary Code Keying), and Barkercoded BPSK (Binary Phase Shift Keying) and QPSK (Quaternary Phase Shift Keying) Receiver Sensitivity for BER < 10-5 Better than -86 dBm Maximum Over-the-Air, Raw Data Rate 2.
Appendix B Factory Configuration This appendix identifies the factory configuration settings for the CCU and EUM. Table 42 CCU Factory Configuration Parameter Default Configuration Console Prompt The default console prompt is the station (CCU) ID. Deregistration Count 8 DHCP Relay Disabled Ethernet IP Address 192.168.10.250 Ethernet Netmask 24 Gateway IP Address 192.168.10.
Table 42 CCU Factory Configuration Parameter Table 43 Default Configuration Radio IP Address 192.168.11.1 Radio Netmask 24 Registration Server IP Address 0.0.0.0 Registration Server Netmask 0 SNMP Contact WaveRider Communications Inc. SNMP Location www.waverider.
Table 43 EUM Factory Configuration Parameter Default Configuration Port Filters 137 (both) 138 (both) 139 (both) 1512 (both) Radio Frequency 9050 (905.0MHz) SNMP Contact WaveRider Communications Ltd. SNMP Location www.waverider.com SNMP Read Communities public SNMP Write Communities private SNMP Traps None entered SNTP Client (listen only) Enabled Yes Transmit Power HIGH . APCD-LM043-4.
— This page is intentionally left blank —
Appendix C Command-Line Syntax This appendix describes the various LMS4000 commands and syntax, and consists of the following sections: • Command-line Syntax Conventions and Shortcuts on page 163 • CCU Command-line Syntax on page 165 • EUM Command-line Syntax on page 174 NOTE: The help command on the CCU or EUM may display additional commands that are not listed in the following tables. WaveRider recommends that you use only commands listed in this Appendix.
Table 44 Command-Line Syntax Conventions Convention Use Examples monospaced font Indicates that you must type the text. Enter Bold face type indicates a keyboard key press. A plus sign (+) indicates key combinations. For example, for Ctrl+U, press and hold down the Ctrl key, then press the U key. Enter Esc Ctrl+U Specifies a variable name or other information that you must replace with a real name or value.
CCU Command-line Syntax Table 46 CCU Command-Line Syntax Command Syntax (CCU) Command Description add Displays the Address Table. add flush Removes all entries from the Address Table. add rem Removes an EUM ID from the Address Table, where: • is the EUM ID, formatted in hexadecimal as XX:XX:XX. air Displays the Registration Table. air associations Displays the maximum association count.
Command Syntax (CCU) 166 Command Description arp map Displays the ARP Map Table. arp map Maps MAC address to IP address . The MAC address is obtained from the ARP Table, or by sending out an ARP request. auth Displays the Authorization Table. auth add Adds an EUM to the Authorization Table, where: • is the EUM ID, formatted in hexadecimal as XX:XX:XX. • is the EUM grade of service, for example, gold.
Command Syntax (CCU) Command Description exit|quit Exits the current console session and returns to the password prompt. file ? Lists the file system utilities. file copy|cp
Command Syntax (CCU) 168 Command Description ip ethernet (0-32) Changes the Ethernet IP address of the CCU, where: • is the new Ethernet IP address of the CCU. • (0-32) is the netmask. ip gateway Displays the IP address of the router through which the CCU connects to the Internet. ip gateway Defines the router through which the CCU connects to the Internet, where: • is the new Ethernet IP address of the router.
Command Syntax (CCU) Command Description radio frequency Displays the CCU radio frequency in tenths of a MHz; for example, 905.0 MHz is displayed as 9050. radio frequency Changes the CCU radio frequency, where. • is the new radio frequency, in tenths of a MHz; for example, 905.0 MHz is entered as 9050. radio meter Displays the current Polling MAC load. This information is displayed for each GOS. radio rc Clears the CCU RSSI and transmit power level history.
Command Syntax (CCU) 170 Command Description route delete (0-32) Deletes a route from the routing table. • is the Ethernet IP address of the network being removed from the routing table. • is the Ethernet IP address of the gateway through which the destination device is reached. • (0-32) is the netmask for the destination network. route stats Displays the routing statistics. save|commit Saves configuration changes.
Command Syntax (CCU) Command Description snmp trap delete Deletes a trap server community, where: • is the Ethernet IP address of the trap server. • is the community name for the trap server being deleted. stats Displays the statistics for all drivers and network protocols. Do not use this command in a Telnet session since doing so will display only a partial set of stats. stats clear Clears the statistics for all drivers.
Command Syntax (CCU) 172 Command Description sys wlog Writes text to the log file. This command is useful for adding information to the log for subsequent analysis: • may be from 1-80 characters in length. time Displays the system calendar clock time. time add Adds an NTP server, where: • is the NTP server address. time client Manages the SNTP client and displays a list of NTP servers. time client disable Disables the SNTP client.
Command Syntax (CCU) Command Description time relay ip|destination |broadcast Sends NTP messages to a single EUM, where: • is the IP address of the EUM. or sends NTP messages to all EUMs if broadcast is entered. time server ? Displays NTP server utilities. time server port Changes the SNTP server port, where: • is the port number.
EUM Command-line Syntax Table 47 EUM Command-Line Syntax Command Syntax (EUM) 174 Command Description arp Displays the ARP Table. arp add [flags] Adds an entry to the ARP table, where. • is the IP address. • is the Ethernet address, in hexadecimal format. • [flags] is always set to 4, meaning the entry is permanent and doesn’t time out, as long as the CCU or EUM is ON. arp del
Command Syntax (EUM) Command Description file copy|cp Copies a file. Use this command only when upgrading the firmware. • is the name of the source file. • is the name of the destination file. file delete Deletes a file, where: • is the name of the file you want to delete. file dir|ls Lists the file directory. file get Retrieves a file from a remote location, where.
Command Syntax (EUM) 176 Command Description ip ethernet (0-32) Changes the Ethernet IP address of the EUM, where: • is the new Ethernet IP address of the EUM. • (0-32) is the netmask. ip gateway Displays the IP address of the CCU through which the EUM connects to the Internet. ip gateway Changes the CCU through which the EUM connects to the Internet, where: • is the radio IP address of the new CCU.
Command Syntax (EUM) Command Description radio rc Clears the CCU RSSI and transmit power level history. radio rf high|low Displays or sets the power of the EUM radio. Note: The EUM RF level should always be set to high. radio rh Displays the RSSI and transmit power level history. radio rssi Displays continuous RSSI readings. Press any key to halt. reg eum Forces the EUM to request registration. reset|reboot Reboots the EUM. save|commit Saves configuration changes.
Command Syntax (EUM) 178 Command Description snmp trap add Adds a trap server community, where: • is the Ethernet IP address of the EUM. • is the community name for the trap server, from 1-64 characters in length. snmp trap delete Deletes a trap server community, where: • is the Ethernet IP address of the EUM.
Command Syntax (EUM) Command Description sys prompt Changes the system prompt, where: • is the new prompt, from 1-20 characters in length. sys ss Displays the system status file. sys task Displays the task list. sys uptime Displays system uptime. sys version Displays software version information. sys wlog Writes text to the log file. This feature is useful for adding information to the log for subsequent analysis. • may be from 1-80 characters in length.
— This page is intentionally left blank —
Appendix D Antenna Guidelines WARNING! Antennas and associated transmission cable must be installed by qualified personnel, and external antennas must be properly grounded. Failure to terminate the antenna port correctly can permanently damage the EUM. WaveRider assumes no liability for failure to adhere to this recommendation or to recognized general safety precautions. The CCU and EUM have been certified for use with Omni, Disc, Patch, Yagi, and Dipole Reflector antenna types.
Calculate the antenna system gain by adding the value of the insertion loss for each component of the antenna system, excluding the antenna, and subtracting the total of that sum from the antenna gain. You can measure the insertion loss of the components, and the antenna gain, at the frequency of interest, or obtain it by referencing the manufacturer’s supplied literature.
Appendix E CCU/EUM Data Tables The CCU and EUM firmware is structured around a set of tables and files, which are discussed in the following sections in the logical order that they are actively involved in the transmission of packets from the Internet to the end-user’s PC: • Port Filter Table (CCU and EUM) on page 183 • Routing Table (CCU and EUM) on page 184 • ARP Table (CCU and EUM) on page 187 • Address Translation Table (CCU only) on page 188 • Authorization Table (CCU only) on page 189 • R
Table 49 Port Filter Table Entries Table Entry Port Filter Description The number of the port which is to be filtered. For each port listed, the CCU or EUM can be set to filter UDP, TCP, or both UDP and TCP packets. To access the Port Filter Table: Console> port PORT FILTERS Port Filter --------------------------------137 both 138 both 139 both 1512 both ---------------------------------Console> Routing Table (CCU and EUM) The Routing Table is used by the CCU to determine the routing of IP packets.
Table 51 Routing Table Entries Entry Description Destination Mask The IP address for the destination network. The subnet mask for the destination network. Type of service, for example: TOS • 0000 Default • 0001 Minimize monetary cost • 0010 Maximize reliability • 0100 Maximize throughput • 1000 Minimize delay RFC1700 and RFC1349 recommend TOS settings for various protocols, including Telnet, FTP, TFTP, ICMP and SNMP.
In the above example, the default route is defined by: Destination 0.0.0.0 Mask 0 TOS 0 Gateway 10.0.0.1 Flags RefCnt 803 0 Use Interface Proto 196587 esmc0 1 Any IP packet with a destination which is not listed in the Routing Table will be forwarded through the Ethernet port (IP address 10.0.0.1) and on to the NAP router. The radio subnet route is defined by: Destination 10.5.0.0 Mask TOS ffff0000 0 Gateway 10.5.0.
ARP Table (CCU and EUM) For each host (EUM or PC) in the system, the ARP (Address Resolution Protocol) Table displays the following information: Table 53 ARP Table Entries Table Entry destination gateway Description Host IP Address Host Ethernet MAC Address flags Refer to Routing Table (CCU and EUM) on page 184 for a description of these flags. Refcnt Number of processes currently referencing this ARP entry. If a process requires a MAC address, it looks it up in the ARP Table.
10.0.0.3 00:90:27:33:c7:e8 405 0 507 esmc0 10.0.0.10 00:a0:98:00:9b:26 405 0 1 esmc0 10.0.0.15 00:10:83:fd:61:a 405 0 781 esmc0 10.0.0.16 00:10:83:fd:e1:4e 405 0 1839 esmc0 10.0.0.17 00:b0:d0:e1:04:c0 405 0 155 esmc0 10.0.1.68 00:00:e8:4d:62:3 405 1 19054 esmc0 10.5.1.17 00:50:da:bb:d1:de 405 0 135 rdr1 10.5.2.50 00:50:ba:b3:97:cd 405 0 12 rdr1 10.5.2.
• 00:01:03:04:f7:d8End-user PC MAC Address • 00:50:c8:e0:0a:33EUM Ethernet MAC Address Authorization Table (CCU only) The Authorization Table controls the EUMs’ access to the LMS4000 900 MHz Radio Network. The Authorization Table contains the grade of service class for each EUM in the system, whether the EUM is active or not. The contents of the Authorization Table are used by the Polling MAC algorithm, and also by the CCU, to automatically build the Registration Table.
Registration Table (CCU only) The Registration Table contains a list of all registered EUMs. The CCU automatically builds and adds to this table as EUMs communicate with the CCU. Every EUM that registers with the CCU appears in this table. The EUM will be removed from the Registration Table if the: • EUM has not communicated with the CCU for more than 12 hours because: • • • • the EUM has been turned off for more than 12 hr., or the EUM has had no traffic to send for more than 12 hr.
Console> NOTE: The air command has been used to view the Registration Table, because reg is too close to reb (reboot). ARP Map Table (CCU and EUM) For each host (EUM or PC) in the system, the ARP Map Table displays the following entries: Table 55 ARP MAP Table Entries Table Entry IP Address Ethernet EUMID GOS Last Rx Description Host IP address Host Ethernet MAC address EUM ID EUM Grade of Service Number of seconds since the last payload was received from the EUM.
Customer Table (EUM only) The purpose of the Customer Table is to give the system operator control over the number of PCs that can access the Internet through the EUM. The Customer Table is optimized for the case where multiple hosts are connected to the EUM, but only one accesses the Internet at any given time. The Customer Table also acts as a bridging table, ensuring local traffic is kept local. The Customer Table presents a list of the end-user computers that are connected to the EUM.
Basic Configuration File (CCU and EUM) The Basic Configuration File (BCF) presents a summary of CCU and EUM configurable parameters, which are either the factory default settings, or those entered by the system operator. To view the BCF for an EUM, for example: Console> bcf Basic Cfg File: File File File File File ID : Time Stamp: Version : Notes : CRC : basic.cfg 3 Operator updated 0xC3 Ethernet/USB IP Address: 10.5.0.31 Ethernet/USB Net Mask : ffff0000 Gateway IP Address: 10.5.0.
File Notes : Based on TN040 Customer Port MAC Address: 00:90:c8:e0:03:75 Hardware ID: 4B Airlink MAC Address: 00:90:c8:60:03:75 Serial Number: E00375 Modem Type: EUM RF level Lo - 905.0 Mhz Med - 915.0 Mhz High - 925.0 Mhz RSSI Lo Med High level - 905.0 Mhz - 915.0 Mhz - 925.
Table 57 RSSI/RSS Cross-reference for Sample Unit (at 915MHz) RSSI RSS RSSI RSS RSSI RSS RSSI RSS RSSI RSS 39 -83dBm 48 -74dBm 57 -64dBm 66 -58dBm 75 -49dBm 40 -82dBm 49 -72dBm 58 -63dBm 67 -57dBm 76 -48dBm 41 -81dBm 50 -71dBm 59 -62dBm 68 -56dBm 77 -47dBm 42 -80dBm 51 -70dBm 60 -61dBm 69 -55dBm 78 -46dBm 43 -79dBm 52 -69dBm 61 -60dBm 70 -54dBm 79 -45dBm 44 -78dBm 53 -68dBm 62 -59dBm 71 -53dBm 80 -44dBm 45 -77dBm 54 -67dBm 63 -58dBm
IO Connections: ----------------------USB Detected True Ethernet Detected True RS232_1 Detected True RS232_2 Detected False System State: ----------------------System Operational Console> 196 APCD-LM043-4.
Appendix F Ping Commands The following table lists the options available for use with a Windows Ping test. This information was obtained from Microsoft Windows 2000 TCP/IP Protocols and Services Technical Reference, pp. 184-185. Table 58 Windows Ping Test Command Options Option Use Default -t Sends Echoes until interrupted.
Option 198 Use Default -j host-list Sends the ICMP Echoes using the Loose Source Route option and sets the next hop addresses to the IP addresses in the host list. The host list is made up of IP addresses separated by spaces corresponding to the loose source route. There can be up to nine IP addresses in the lost list. Not set -k host-list Sends the ICMP Echoes using the Strict Source Route option and sets the next hop addresses to the IP addresses in the host list.
Appendix G SNMP MIB Definitions This appendix defines the MIBs used in the CCU and EUM. These MIBs are organized under the following headings: • MIB-II Elements Supported from RFC-1213 on page 199 • WaveRider CCU Enterprise MIBs on page 203 • CCU RFC MIB-II Traps on page 212 • WaveRider EUM Enterprise MIBs on page 213 • EUM RFC MIB-II Traps on page 221 MIB-II Elements Supported from RFC-1213 The CCU and EUM support the following MIB-II groups, which are defined in detail in RFC1213.
MIB Name OID Type Status Description at 3 MIB R This group shows the address translation table, mapping Ethernet addresses to IP addresses. This group is only for MIB-I compatibility. ip 4 MIB R This group provides all of the statistics on IP traffic that is routed through the modem. For EUMs, all traffic from the end-user to the CCU bypass the IP stack in the EUM so these numbers are only for the EUM applications.
MIB Name OID Value Type ifDescr 2 String lo0: loopback esmc0: ethernet mdr1: radio A textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the hardware interface. ifType 3 Integer 6:ethernet-csmacd 6: radio interface 24: softwareLoopback The type of interface, distinguished according to the physical/link protocol(s) immediately `below' the network layer in the protocol stack.
MIB Name OID Value Type ifInDiscards 13 Counter The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being deliverable to a higher-layer protocol. One possible reason for discarding such a packet could be to free up buffer space. ifInErrors 14 Counter The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
WaveRider CCU Enterprise MIBs The structure of the CCU MIBs is illustrated in Figure 51. Enterprise (1.3.6.1.4.
CCU General Information Group All values in Table 63 are prefixed with 1.3.6.1.4.1.2979.11.1. Table 63 WaveRider CCU General Information Enterprise MIBs Accepted Values MIB Name OID Value Type Status Description ccuSerialNumber 1 String R CCU hardware serial number ccuSoftwareVersion 2 String R CCU firmware version. ccuHardwareVersion 3 String R CCU hardware version. ccuExtraFunctions 4 Integer R 0 A mask for extra functionality that may be added at a later date.
CCU Radio Statistics Group All CCU Radio Statistics Group MIB values are read only. All values in Table 65 are prefixed with 1.3.6.1.4.1.2979.11.3. Table 65 WaveRider CCU Radio Statistics MIB MIB Name OID Value Type ccuRadioStatsGeneral 1 MIB General radio statistics. ccuRadioStatsDriver 2 MIB Radio driver statistics ccuRadioStatsMAC 3 MIB Radio MAC statistics. Description CCU Radio General Statistics Group All CCU Radio General Statistics Group MIB values are read only.
MIB Name OID Value Type Description ccuRadioDrvUnknownEvent 7 Counter Number of received an unknown/no event interrupts received by the radio driver ISR. ccuRadioDrvSend 8 Counter Number of packets sent successfully by the radio driver transmit queue. ccuRadioDrvSendQFull 9 Counter Number of packets not sent because the radio driver transmit queue was full. ccuRadioDrvSendUnavailable 10 Counter Number of times invalid (null) mblks were sent to the radio driver for transmission.
MIB Name OID Value Type ccuRadioMACRxPayloadFailInvalidType 3 Counter Number of times an unknown type of payload was received from the air interface. ccuRadioMACRxPayloadFailGiant 4 Counter Number of times a payload that was too long was received from the air interface, and therefore discarded. CCURadioMACNullRxDesc 5 Counter Number of times the internal MAC receive interface was corrupted. ccuRadioMACTxDataPayloads 6 Counter Number of Ethernet frames transmitted to the air interface.
MIB Name OID Value Type ccuRadioMACRxPktsRuntFail 22 Counter Number of packets received that were shorter than the minimum size. ccuRadioMACRxPktsLongFail 23 Counter Number of packets received that were longer than the maximum size. ccuRadioMACRxPktsHCRCFail 24 Counter Number of packets received with a MAC header CRC failure (header corrupted). ccuRadioMACRxPktsICVFail 25 Counter Number of packets received with an encryption (WEP, wireless equivalent privacy) key mismatch (see note 3).
MIB Name OID Value Type ccuRadioMACTxPayloadsAssocFail 44 Counter Number of payloads returned to the host because too many other EUMs were already associated. ccuRadioMACTxPayloadsTimeout 45 Counter Number of payloads returned to the host because of timeout. ccuRadioMACTxPayloadQueueTooLong 46 Counter Number of payloads returned to the host because the transmit queue for the EUM was too long (see note 4). 47 Counter Not used.
CCU Ethernet Statistics Group All CCU Ethernet Statistics Group MIB values are read only. All values in Table 69 are prefixed with 1.3.6.1.4.1.2979.11.4. Table 69 WaveRider CCU Ethernet Statistics Group MIB 210 MIB Name OID Value Type ccuEtherInterrupts 1 Counter Total number of interrupts received by the Ethernet driver ISR, interrupt service routine. ccuEtherRxInterrupt 2 Counter Number of receive complete interrupts received by the Ethernet driver ISR.
MIB Name OID Value Type ccuEtherTxOk 18 Counter Number of packets sent correctly. ccuEtherTxTimeout 19 Counter Number of times the packet transmit has timed out. ccuEtherTxSemWait 20 Counter Number of times a transmit semaphore could not be taken in the timeout period. Description CCU Modem Information MIB All values in Table 70 are prefixed with 1.3.6.1.4.1.2979.11.5. Table 70 WaveRider CCU Modem Information MIB MIB Name OID Value Type ccuRegistration 1 MIB Registration Table.
CCU Authorization Information MIB All CCU Authorization MIB values are read only. All values in Table 73 are prefixed with 1.3.6.1.4.1.2979.11.5.2. Table 73 WaveRider CCU Authorization Table MIB MIB Name OID Value Type ccuAuthorizationCount 1 Integer ccuAuthorizationTable 2 MIB Description Number of authorized EUMs. CCU Authorization Table All CCU Authorization Table Group MIB values are read only. All values in Table 74 are prefixed with 1.3.6.1.4.1.2979.11.5.2.2.
WaveRider EUM Enterprise MIBs The structure of the EUM MIBs is illustrated in Figure 52. Enterprise (1.3.6.1.4.
EUM General Information Group All values in Table 77 are prefixed with 1.3.6.1.4.1.2979.12.1. Table 77 WaveRider EUM General Information Enterprise MIBs Accepted Values MIB Name OID Value Type Status Description eumSerialNumber 1 String R EUM hardware serial number eumSoftwareVersion 2 String R EUM firmware version. eumHardwareVersion 3 String R EUM hardware version. eumExtraFunctions 4 Integer R 0 A mask for extra functionality that may be added at a later date.
EUM Radio Statistics Group All EUM Radio Statistics Group MIB values are read only. All values in Table 79 are prefixed with 1.3.6.1.4.1.2979.12.3. Table 79 WaveRider EUM Radio Statistics MIB MIB Name OID Value Type eumRadioStatsGeneral 1 MIB General radio statistics. eumRadioStatsDriver 2 MIB Radio driver statistics eumRadioStatsMAC 3 MIB Radio MAC statistics. Description EUM Radio General Statistics Group All EUM Radio General Statistics Group MIB values are read only.
MIB Name OID Value Type Description eumRadioDrvUnknownEvent 7 Counter Number of received an unknown/no event interrupts received by the radio driver ISR. eumRadioDrvSend 8 Counter Number of packets sent successfully by the radio driver transmit queue. eumRadioDrvSendQFull 9 Counter Number of packets not sent because the radio driver transmit queue was full. eumRadioDrvSendUnavailable 10 Counter Number of times invalid (null) mblks were sent to the radio driver for transmission.
MIB Name OID Value Type eumRadioMACRxPayloadFailInvalidType 3 Counter Number of times an unknown type of payload was received from the air interface. eumRadioMACRxPayloadFailGiant 4 Counter Number of times a payload that was too long was received from the air interface, and therefore discarded. eumRadioMACNullRxDesc 5 Counter Number of times the internal MAC receive interface was corrupted. eumRadioMACTxDataPayloads 6 Counter Number of Ethernet frames transmitted to the air interface.
MIB Name OID Value Type eumRadioMACRxPktsHCRCFail 24 Counter Number of packets received with a MAC header CRC failure (header corrupted). eumRadioMACRxPktsICVFail 25 Counter Number of packets received with an encryption (WEP, wireless equivalent privacy) key mismatch (see note 3). eumRadioMACRxPktsFCSFail 26 Counter Number of packets received with a Frame Check Sequence failure (payload corrupted). 27 Not used. Returns a value of ‘0’.
MIB Name OID Value Type eumRadioMACReplyOrRssiTimeout 48 Counter Number of times the RSSI timer expired because the EUM had not received anything from the CCU for more than 0.5s. eumRadioMACRestarts 49 Counter Number of times that the MAC layer recovered from an internal error or unexpected event. eumRadioMACRegRequests 50 Counter Number of registration requests transmitted (see note 4). eumRadioMACRegResponse 51 Counter Number of registration responses received (see note 4).
220 MIB Name OID Value Type eumEtherRxOverrunInterrupt 3 Counter Number of overrun interrupts received by the Ethernet driver ISR. An overrun occurs when a received packet has exceeded the packet size, or the processor has missed one or more packets. eumEtherRxInProgressInterrupt 4 Counter Number of times a receive complete interrupt was received by the Ethernet driver ISR before the current packet was finished.
EUM RFC MIB-II Traps RFC MIB-II Traps Table 84 EUM RFC MIB-II Traps MIB Name OID coldStart 1.3.6.1.2.1.11.0.0 Power Cycle or Power On authenticationFailure 1.3.6.1.2.1.11.0.4 An SNMP request has failed due to improper authentication APCD-LM043-4.
— This page is intentionally left blank —
Appendix H Operating Statistics The CCU and EUM provide a comprehensive set of operating statistics for each of the following: • Ethernet Port • Radio Driver • MAC Interface • Routing/Bridging Protocol • Network Interface • System Load (Radio Meter) These statistics can be used as a diagnostic and troubleshooting tool when system performance is being impaired by interference, radio link degradation, network problems, atypical end-user applications, capacity issues, and so on.
To Display (all) Statistics from the CLI • At the command prompt, type stats and press Enter. The following sections describe each of the statistics in detail and the procedure for obtaining specific sets of statistics (Ethernet, Radio, and so on). Ethernet Statistics Ethernet Statistics present operational information about data passing through the CCU and EUM Ethernet ports. These statistics are described in Table 85.
Statistic Available in MIB Description RX Data 3 Number of packets received and accepted by the IP stack. RX Data Error 3 Number of packets received and rejected by the IP stack because of errors. RX Data Mblk Error 3 Number of packets lost due to insufficient memory resources. RX Data Length Error 3 Number of packets received that violate Ethernet packet length rules. RX Discards 3 Number of packets discarded because the unit was not ready to receive data.
Radio Driver Statistics Radio Driver Statistics present operational information about data passing through the CCU and EUM radio driver and ports. These statistics are described in Table 86. As indicated in Table 86, all of the Radio Driver statistics are available in a WaveRider MIB.
Statistic Available in MIB Description AMM Q Full Discard 3 Number of times a packet was discarded due to the MAC-layer shared memory transmit queue not draining. AMM Get 3 Number of packets received from the MAClayer shared memory. AMM Q Empty 3 Number of times there was a receive interrupt, but nothing available to read out of the MAClayer shared memory. Receive 3 Number of successfully received packets.
MAC Interface Statistics MAC Interface Statistics present operational information about data which is processed by the CCU and EUM MAC layer. These statistics are described in Table 87. As noted in Table 87, most of the MAC interface statistics are available in a WaveRider MIB. Table 87 MAC Interface Statistics Statistic 228 Available in MIB Description (see note 2) Rx Data Payloads 3 Number of data payloads received correctly from the air interface.
Statistic Available in MIB Description (see note 2) Atmel Fatal Error Not used. Unused Statistic Not used. rxPktsDirected 3 At the CCU, the number of times a reply from the EUM is received with the correct HCRC (header cyclic redundancy check). In the EUM, the number of times a poll for the EUM is received from the CCU with the correct HCRC. rxPktsBroadcast 3 At the CCU, the number of times an EUM succeeds in a random access. Note that all EUM packets are directed to the CCU, not broadcast.
Statistic Description (see note 2) rxPktsEmpty 3 Number of packets received that are directed to this station, but that did not contain a payload. txPkts 3 Number of packets transmitted. txPktsEmpty 3 Number of packets transmitted with no payload. txPayloads 3 Number of payloads transmitted. txPayloadsBCast 3 Number of broadcast payloads transmitted. [CCU only] txPayloads1Ok 3 Number of payloads acknowledged after the first transmission.
Statistic Available in MIB Description (see note 2) replyOrRssiTimeouts 3 At the CCU, the number of times that no response was received to a directed poll. At the EUM, the number of times the RSSI timer expired because the EUM had not received anything from the CCU for more than 0.5s. restarts 3 Number of times that a PAI (physical attachment interface) state machine restart occurred (internal error). registrationRequests 3 At the CCU, the number of registration requests received (see note 5).
• The CCU maintains a transmit queue for each EUM. The length of this queue is limited, to keep one EUM from consuming all the resources and impacting other EUMs. Discards indicate excessive load by one EUM, possibly due to large TCP windows. • Registration occurs once per EUM and/or CCU boot time.
txPayloadsFailQueueTooLong: txPayloadsEmpty: replyOrRssiTimeouts: restarts: registrationRequests: registrationResponses: deregistrationRequests: deregistrationInits: disassociationRequests: disassociationInits: newAssociations: currentAssociations: unexpectedEvents: latestTx: latestProg: latestTxPayload: latestReply: lateReplyEum: longestSearch: txDescAvail: 0 0 232598 0 0 0 0 0 5671 5702 5671 3 0 187 9881 212 9912 6294067 127 74 CCU> Routing/Bridging Protocol Statistics Routing/Bridging Protocol Statist
Statistic 234 Description Rx Eth Err - Pkt Size Number of Ethernet frames from the Ethernet port that were discarded because the frame was too large or too small to decode. Rx Eth Err - Unknown Ether Type Number of Ethernet frames from the Ethernet port that were discarded because they were neither IP nor ARP frames (example, IPX frame). Rx Eth Err - Customer Table Error Number of Ethernet frames from the Ethernet port that were discarded because the host was not allowed air access.
Statistic Description Rx Radio Err - Unknown Msg Type Number of Ethernet frames from the radio port that were discarded because of an internal routing error. Rx Radio Err - Unreg Request Number of Ethernet frames received from the radio port that were discarded because they came from an unregistered EUM. [CCU only] Rx Radio Err - Invalid NetPool Number of Ethernet frames received from the radio port that were discarded because of a specific type of memory allocation error.
CCU> stats rp ----------------Routing Protocol Statistics ----------------Rx Rx Rx Rx Rx Rx Rx Eth Eth Eth Eth Eth Eth Eth Dst Dst Err Err Err Err Err Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Radio Radio Radio Radio Radio Radio Radio Radio Radio Radio Radio Radio Radio Dst Dst Dst Dst Err Err Err Err Err Err Err Err Err Tx Tx Tx Tx Tx Tx Tx Dst Dst Err Err Err Dst Dst Eth Radio Mblk Msg Buffer Pkt Size Unregistered Unknown - - Radio To Router Mblk Msg Buffer Pkt Size Unknown Ether Type IP Filter -
CCU> stats net To view network interface ICMP statistics: CCU> stats net icmp ICMP: 3133 calls to icmp_error 0 error not generated because old message was icmp Output histogram: destination unreachable: 3133 0 message with bad code fields 0 message < minimum length 0 bad checksum 0 message with bad length Input histogram: destination unreachable: 20 0 message response generated CCU> To view network interface IP statistics: CCU> stats net ip total 2181354 badsum 0 tooshort 0 toosmall 0 badhlen 0 badlen 0 i
CCU> stats net tcp TCP: 536 packets sent 304 data packets (23557 bytes) 0 data packet (0 byte) retransmitted 222 ack-only packets (7 delayed) 0 URG only packet 0 window probe packet 0 window update packet 10 control packets 527 packets received 310 acks (for 23571 bytes) 7 duplicate acks 0 ack for unsent data 283 packets (485 bytes) received in-sequence 0 completely duplicate packet (0 byte) 0 packet with some dup.
System Load Statistics (Radio Meter) The radio meter command prints out a table of measurements that indicate the current load on the system. These statistics are only available at the CCU. The load statistics are summarized in Table 90. System Load Statistics are not available through the WaveRider MIBs. Table 90 Load Statistics (Radio Meter) Statistic Description Time Value of the CCU’s internal 32-bit microsecond timer at the instant the messages were taken.
• Violation counters could roll over after 70 seconds if the corresponding parameter was set too small. A steeply climbing violation counter indicates serious problems with either the settings or the system load.
Appendix I IP Plan — Example The following tables provide an example of an IP plan for an LMS4000 system equipped with fifteen 900 MHz CAPs. NAP IP Addressing Plan Table 91 Example - CCU Ethernet Subnet Data Subnet 192.168.10.0 Subnet Mask Bits 24 Subnet Mask 255.255.255.0 (ff.ff.ff.00) Table 92 Example - NAP IP Addressing Plan NAP Element IP Address Gateway (NAP) Router 192.168.10.1 /24 NAP Switch 192.168.10.5 /24 NAP UPS 192.168.10.6 /24 SNMP Manager 192.168.10.7 /24 APCD-LM043-4.
CCU Ethernet IP Addressing Plan Table 93 Example - CCU Ethernet IP Addressing Plan Site CCU CCU Ethernet Address Site CCU CCU Ethernet Address CAP01 CCU01 192.168.10.11 CAP09 CCU01 192.168.10.139 CCU02 192.168.10.12 CCU02 192.168.10.140 CCU03 192.168.10.13 CCU03 192.168.10.141 CCU01 192.168.10.27 CCU01 192.168.10.155 CCU02 192.168.10.28 CCU02 192.168.10.156 CCU03 192.168.10.29 CCU03 192.168.10.157 CCU01 192.168.10.43 CCU01 192.168.10.171 CCU02 192.168.10.
CCU Radio IP Addressing Plan Table 94 Example - CCU Radio Subnet Data Subnet 172.16.0.0 Subnet Mask Bits 22 Subnet Mask 255.255.252.0 (ff.ff.fc.00) Table 95 Example - CCU Radio IP Addressing Plan Site CCU Subnet CCU Radio IP Address CCU Radio Subnet Range Broadcast CAP01 CCU01 172.16.4.0 172.16.4.1 172.16.4.1 - 172.16.7.254 172.16.7.255 CCU02 172.16.8.0 172.16.8.1 172.16.8.1 - 172.16.11.254 172.16.11.255 CCU03 172.16.12.0 172.16.12.1 172.16.12.1 - 172.16.15.254 172.16.15.
Site CCU Subnet CCU Radio IP Address CCU Radio Subnet Range Broadcast CAP09 CCU01 172.16.100.0 172.16.100.1 172.16.100.1 - 172.16.103.254 172.16.103.255 CCU02 172.16.104.0 172.16.104.1 172.16.104.1 - 172.16.107.254 172.16.107.255 CCU03 172.16.108.0 172.16.108.1 172.16.108.1 - 172.16.111.254 172.16.111.255 CCU01 172.16.112.0 172.16.112.1 172.16.112.1 - 172.16.115.254 172.16.115.255 CCU02 172.16.116.0 172.16.116.1 172.16.116.1 - 172.16.119.254 172.16.119.255 CCU03 172.16.120.
EUM IP Addressing Plan Table 96 Example - EUM Subnet Data Subnet 172.16.0.0 Subnet Mask Bits 22 Subnet Mask 255.255.252.0 (ff.ff.fc.00) Table 97 Example - EUM IP Addressing Plan Site CCU Subnet ID EUM IP Address Range CAP01 CCU01 EUM001-253 172.16.4.2 - 172.16.4.254 EUM254-300 172.16.5.1 - 172.16.5.47 EUM001-253 172.16.8.2 - 172.16.8.254 EUM254-300 172.16.9.1 - 172.16.9.47 EUM001-253 172.16.12.2 - 172.16.12.254 EUM254-300 172.16.13.1 - 172.16.13.47 EUM001-253 172.16.16.2 - 172.16.
Site CCU Subnet ID EUM IP Address Range CAP05 CCU01 EUM001-253 172.16.52.2 - 172.16.52.254 EUM254-300 172.16.53.1 - 172.16.53.47 EUM001-253 172.16.56.2 - 172.16.56.254 EUM254-300 172.16.57.1 - 172.16.57.47 EUM001-253 172.16.60.2 - 172.16.60.254 EUM254-300 172.16.61.1 - 172.16.61.47 EUM001-253 172.16.64.2 - 172.16.64.254 EUM254-300 172.16.65.1 - 172.16.65.47 EUM001-253 172.16.68.2 - 172.16.68.254 EUM254-300 172.16.69.1 - 172.16.69.47 EUM001-253 172.16.72.2 - 172.16.72.
Site CCU Subnet ID EUM IP Address Range CAP10 CCU01 EUM001-253 172.16.112.2 - 172.16.112.254 EUM254-300 172.16.113.1 - 172.16.113.47 EUM001-253 172.16.116.2 - 172.16.116.254 EUM254-300 172.16.117.1 - 172.16.117.47 EUM001-253 172.16.120.2 - 172.16.120.254 EUM254-300 172.16.121.1 - 172.16.121.47 EUM001-253 172.16.124.2 - 172.16.124.254 EUM254-300 172.16.125.1 - 172.16.125.47 EUM001-253 172.16.128.2 - 172.16.128.254 EUM254-300 172.16.129.1 - 172.16.129.47 EUM001-253 172.16.132.
Site CCU Subnet ID EUM IP Address Range CAP15 CCU01 EUM001-253 172.16.172.2 - 172.16.172.254 EUM254-300 172.16.173.1 - 172.16.173.47 EUM001-253 172.16.176.2 - 172.16.176.254 EUM254-300 172.16.177.1 - 172.16.177.47 EUM001-253 172.16.180.2 - 172.16.180.254 EUM254-300 172.16.181.1 - 172.16.181.47 CCU02 CCU03 Subscriber IP Addressing Plan Table 98 Example - Subscriber Subnet Data Subnet 172.16.0.0 Subnet Mask Bits 22 Subnet Mask 255.255.252.0 (ff.ff.fc.
Site CCU Subnet ID Subscriber IP Address Range CAP03 CCU01 SUB001-253 172.16.30.1 - 172.16.30.254 SUB254-300 172.16.31.1 - 172.16.31.46 SUB001-253 172.16.34.1 - 172.16.34.254 SUB254-300 172.16.35.1 - 172.16.35.46 SUB001-253 172.16.38.1 - 172.16.38.254 SUB254-300 172.16.39.1 - 172.16.39.46 SUB001-253 172.16.42.1 - 172.16.42.254 SUB254-300 172.16.43.1 - 172.16.43.46 SUB001-253 172.16.46.1 - 172.16.46.254 SUB254-300 172.16.47.1 - 172.16.47.46 SUB001-253 172.16.50.1 - 172.16.50.
Site CCU Subnet ID Subscriber IP Address Range CAP08 CCU01 SUB001-253 172.16.90.1 - 172.16.90.254 SUB254-300 172.16.91.1 - 172.16.91.46 SUB001-253 172.16.94.1 - 172.16.94.254 SUB254-300 172.16.95.1 - 172.16.95.46 SUB001-253 172.16.98.1 - 172.16.98.254 SUB254-300 172.16.99.1 - 172.16.99.97 SUB001-253 172.16.102.1 - 172.16.102.254 SUB254-300 172.16.103.1 - 172.16.103.46 SUB001-253 172.16.106.1 - 172.16.106.254 SUB254-300 172.16.107.1 - 172.16.107.46 SUB001-253 172.16.110.1 - 172.16.
Site CCU Subnet ID Subscriber IP Address Range CAP13 CCU01 SUB001-253 172.16.150.1 - 172.16.150.254 SUB254-300 172.16.151.1 - 172.16.151.46 SUB001-253 172.16.154.1 - 172.16.154.254 SUB254-300 172.16.155.1 - 172.16.155.46 SUB001-253 172.16.158.1 - 172.16.158.254 SUB254-300 172.16.159.1 - 172.16.159.46 SUB001-253 172.16.162.1 - 172.16.162.254 SUB254-300 172.16.163.1 - 172.16.163.46 SUB001-253 172.16.166.1 - 172.16.166.254 SUB254-300 172.16.167.1 - 172.16.167.46 SUB001-253 172.16.
— This page is intentionally left blank —
Appendix J Table 100 Acronyms and Glossary Acronyms and Abbreviations Acronym or Abbreviation Definition ABWM Advanced Bandwidth Manager AC Alternating Current API Application Programming Interface ARP Address Resolution Protocol ARQ Automatic Retry Request ASCII American Standard Code for Information Interchange BCF Basic Configuration File CAP Communications Access Point CCU CAP Channel Unit CIR Committed Information Rate CLI Command Line Interface CPU Central Processing Unit
Acronym or Abbreviation 254 Definition DSR Data Set Ready DSSS Direct-sequence Spread Spectrum DTE Data Terminal Equipment ESD Electrostatic Discharge ESN Electronic Serial Number ETSI European Telecommunications Standards for Industry EUM End-user Modem FCC Federal Communications Commission (U.S.A.
Acronym or Abbreviation Definition NAT Network Address Translation NCL Network Communication Link NTP Network Time Protocol OAM Operations, Administration and Maintenance OID Object Identifier OS Operating System PAT Port Address Translation PC Personal Computer PCF Permanent Configuration File PHY Physical Layer RADIUS Remote Access Dial-in User Service RCF Route Configuration File RF Radio Frequency RIP Routing Information Protocol RMA Returned Merchandise Authorization RSS
Table 101 LMS4000 Network Glossary Term 256 Definition LMS4000 RF Subsystem The RF Equipment associated with an LMS4000, including CCUs, RFSM, antennas, and transmission lines. Bandwidth Manager The entity in the LMS4000 that uses various algorithms to manage end-user access to the network interface bandwidth, based on subscribed level of service. Broadcast (Message) A message sent by one network device to all other devices connected to the network.
Term Definition GOS (Grade of Service) A level of service associated with an EUM, which determines how often, and when, an EUM will be polled. Since an EUM can only send one packet each time it is polled, the data rate is related to the polling rate. IP (Internet Protocol) The network-layer protocol in the TCP/IP stack (defined by RFC 791).
Term 258 Definition RIP (Routing Information Protocol) A routing protocol in which network routers periodically broadcast their entire current routing database. Router A network device that routes IP messages from one physical port to another based on a table of routes that are manually entered by a crafts person (static routes) or generated by the router using a routing protocol such as RIP or OSPF. Routing The process of finding a path to a destination host through an IP network.
Term Definition TCP (Transmission Control Protocol) The connection-oriented transport layer protocol that provides reliable, full-duplex data transmission in TCP/IP networks. Telnet A terminal emulation program for TCP/IP networks. UDP (User Datagram Protocol) Part of the TCP/IP protocol suite, which provides a way for applications to access the connectionless features of IP. It provides for exchange of datagrams without acknowledgements or guaranteed delivery.
— This page is intentionally left blank —
Index A acronyms . . . . . . . . . . antenna . . . . . . . . . . . antenna guidelines connector . . . . . . . control . . . . . . . . . Atmel statistics . . . . . . . . . . . . . . . . . . 253 . . . . . . . . . . 17, 20 . . . . . . . . 181, 241 . . . . . . . . . . . . . 31 . . . . . . . . . . . . . 31 . . . . . . . . . . . . 228 B backhaul . . . . . . . . . . . bandpass filters . . . . . . broadcast applications . . . . . . . . . . . . . 156 . . . . . . . . . . . . . 63 . . . . . . . . . . . . .
temperature. MDR statistics . . MIBs . . . . . . . . . modulation . . . . . . . . . . . . . . . . . . . . . 125 . . . . . . . . . . . . . . . . . 226 . . . . . . . . . . . . . . . . . . 52 . . . . . . . . . . . . . . . . . . 29 N NAT . . . . . . . . . . . network monitoring transmit power. . . . . transmit queue limits transmit statistics . . . troubleshooting . . . . . . . . . . . . . . . . . . . 30 . . . . . . . . . . . . . . . 42 . . . . . . . . . . . . . . 127 . . . . . . . . . . . . . . 135 U . .
— This page is intentionally left blank —
Telephone: Fax: Email: URL: +1 416–502–3161 +1 416–502–2968 techsupport@waverider.com www.waverider.