6710 Access Point USER’S GUIDE " " " " " " " " " " " " " " " " " " " " " " " " " " " " P/N 961-047-081 Revision C July 1998
" NOTICE This publication contains information proprietary to Intermec Technologies Corporation. It is being supplied to you with the express understanding that the information contained herein is for the benefit of the contracting party only, and may not be copied, distributed, or displayed to third parties without the express written consent of Intermec Technologies Corporation, and shall be returned to Intermec Technologies Corporation upon written request.
FCC Computer Compliance " NOTICE This equipment meets Class B digital device limits per Part 15 of FCC Rules. These limits protect against interference in a residential area. It emits, uses, and can radiate radio frequency energy. If you do not install and use the equipment according to its instructions, it may interfere with radio signals. However, there is no guarantee that interference will not occur in a particular installation.
Canadian 2.4 GHz Radio License " NOTICE This device requires a radio license, unless it is installed totally inside a building. (Users must obtain this license) Une licence radio est requise pour ces dispositifs, sauf pour ceux installés tout à fait à l’intérieur d’un bâtiment. (Il faut que l’utilisateur obtienne cette licence.) Telephone Installation Warning Notices The following notices apply to equipment that may be connected to telephone lines or systems.
B CAUTION: Intermec Technologies Corporation suggests you buy cables from us to connect with other devices. Our cables are safe, meet FCC rules, and suit our products. Other cables may not be tested. They may cause problems from electrostatic discharge or induced energy. Our warranties do not cover loss, injury, or damage from other cables.
CONTENTS " " " " " " " " " " " " " " " " " " " " " " " " " " " " SECTION 1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Publications . . . . . . . . .
CONTENTS ii " Configuration and Management . . . . . . . . . . . . . . . . . . . . . . Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostics and Configuration Port . . . . . . . . . . . . Remote Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DHCP Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Telnet . . . . . . . . . . . . . . . . . . . . . . . .
CONTENTS Connecting to Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10BASE2 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . End of Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Middle of Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10BASE5 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . N-Series Transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . Vampire Tap . . . . . . . . . . . . . .
CONTENTS " Bridge Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Serial Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lan ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Root] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Root Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Super Root Candidates . . . . . . . . . . . . . . . . . . .
CONTENTS [Advanced RX Filter] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [Expressions] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ExprSeq . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Op . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Value Id . . . . . . . . . . .
CONTENTS vi " S-UHF Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . File Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Sign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Master Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Attach Priority . . . . . . . . . . . . . . . . . . . .
CONTENTS Fe Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TFTP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTENTS " FPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FPX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MI String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CONTENTS " APPENDIX B WLIF Specifications and Antennas . . . . . . . . . . . . . . . . . . . B-1 RM180 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Antenna Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Whip Antenna . . . . . . . . . . . . . . . . . . . . . . . . .
CONTENTS " Installation Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Predicting Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing a Single Access Point . . . . . . . . . . . . . . . . . . . Installing Multiple Access Points . . . . . . . . . . . . . . . . . . Extending Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . Reusing the Frequency . . . . . . . . . . . . . . . . . . . . . . . . Increasing System Throughput . . . . . . . . . . .
CONTENTS OWL/IP Configuration Examples . . . . . . . . . . . . . . . . . . . . . Example 1: Class C IP Addresses . . . . . . . . . . . . . . . . . Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Option A: Unicast Addressing . . . . . . . . . . . . . Option B: Directed Broadcast . . . . . . . . . . . . .
CONTENTS " MIB Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Product OIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interface Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SNMP Version 1 Configuration Group . . . . . . . . . . . . . Bridging Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Control Groups . . . . .
CONTENTS " Figure 4-1 Local Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-2 Telnet Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-3 Access Points Servicing IP Wireless Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-4 Wireless Hopping Through WLIF Radios . . . . Figure 4-5 OWL/IP Overview . . . . . . . . . . . . . . . . . . . . . . . . Figure 4-6 Web Browser Session . . . . . . . . . . . . . . . . .
CONTENTS " Table G-7 segment GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-8 dir GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-9 criticalErrors GROUP . . . . . . . . . . . . . . . . . . . . . . Table G-10 nifx GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table G-11 portState GROUP . . . . . . . . . . . . . . . . . . . . . . . . Table G-12 portStats GROUP . . . . . . . . . . . . . . . . . . . . . . . . Table G-13 ptxq GROUP . . . . . . .
Section 1 Preface " " " " " " " " " " " " " " " " " " " " " " " " " " " " Purpose of This Guide This user’s guide describes the installation, setup, and maintenance of the 6710 Access Point. This guide covers access point FLASH version 1.27 or greater and ROM version 1.12 or greater. Norand Corporation is now part of Intermec Technologies Corporation.
SECTION 1 " Preface Section 3, “Installation” Helps you prepare your site before you install the access point, and shows how to connect the access point to 10BASE-T, 10BASE2, and 10BASE5 Ethernet. Section 4, “Configuration” Describes how to create a communications session with the access point, access FLASH and ROM, and set up the access point through its configuration menus.
SECTION 1 " Preface Intended Audience This user’s guide is intended for these audiences: " " Network administrator who is familiar with various types and configurations of computer networks, how they work, and the terminology used when discussing them. Hardware installer who is responsible for performing the physical installation of the access point and any related hardware that might be required. Related Publications The following publications are available.
SECTION 1 " Preface System Management Publications NORAND Open Wireless LAN with HP OpenView for Windows User’s Guide (961-051-009) This guide describes how to install and use the OpenView for Windows network management platform by Hewlett-Packard (HP). OWLView for HP OpenView for UNIX User’s Guide (961-051-011) This guide describes how to install and use the OWLView for HP OpenView for UNIX network management platform.
Section 2 Features and Functional Overview " " " " " " " " " " " " " " " " " " " " " " " " " " " " This section describes the 6710 Access Point and how it operates on the open wireless LAN. This section also describes access point components. Description The 6710 Access Point provides transparent, wireless communications between a wired Ethernet LAN and wireless stations. Figure 2-1 shows current designs; information in this user’s guide applies to both designs.
SECTION 2 " Features and Functional Overview The access point functions as a 4-port translating bridge. Functionality within the access point can be partitioned into two major functional blocks: bridging functionality and management functionality. Bridging functions pertain to the forwarding of data through the access point. Management functionality involves configuration, software upgrade, and network management. Figure 2-2 is a simplified diagram showing the functions within the access point.
SECTION 2 " Features and Functional Overview Bridges operate at the Media Access Control (MAC) sublayer of the Data Link Layer (Layer 2) of the International Organization for Standardization (ISO) protocol model. Operating at the MAC layer allows bridges to operate transparently to commonly used network protocols such as TCP/IP, Novell SPX/IPX, NetBEUI, and DECnet. In wired LANs, bridges do the following: " " " Segment traffic for better efficiency and performance.
SECTION 2 " Features and Functional Overview Access Point Bridging Layer The 6710 Access Point functions as a bridge with up to four ports: An Ethernet port. " One or two radio ports. " An Open Wireless LAN/Internet Protocol (OWL/IP) port. The access point is a translating bridge because it forwards frames between Ethernet and wireless media that have unique physical and MAC protocol implementations. The access point implements the basic learning and forwarding functions of a simple wired LAN bridge.
SECTION 2 " Features and Functional Overview Access points automatically configure into a self-organized network using a spanning tree topology. They automatically reconfigure the network to maintain reliable operation as devices are added or removed, or in the event of some types of wired LAN failure. The spanning tree provides efficient, loop-free forwarding of frames through the network and rapid roaming of mobile stations within the network.
SECTION 2 " Features and Functional Overview Flooding Configurations Standard LAN bridges flood frames on all ports when the destination address is unknown. Additionally, many network protocols use multicast addressing for connection and status communications. A multicast frame is a special type of frame destined for more than one physical address. Standard bridges always flood multicast frames. Most wireless media supported in the access point operate at lower media speeds than Ethernet.
SECTION 2 " Features and Functional Overview Proxy ARP Server The Proxy ARP Server is an advanced flooding control capability for stations using IP. An ARP (Address Resolution Protocol) is a type of multicast message used to determine the physical (MAC) address of a station using a specific IP address. When Proxy ARP is enabled, the IP addresses of stations using IP are included in the forwarding database.
SECTION 2 " Features and Functional Overview The physical connections are on the bottom panel of the access point. The desired Ethernet medium is selectable through the device configuration menus. Section 3, “Installation,” has more information about connecting the access point to Ethernet media. Section 4, “Configuration,” describes how to set the medium through the configuration menus.
SECTION 2 " Features and Functional Overview Filtering occurs regardless of whether the destination address is in the forwarding database. Using filters can improve the performance of the access point and prevent undesired frames from being forwarded to wireless stations attached to the access point. Flooding decisions are made after frames have been received on a port and filtered. Flooding settings determine how the access point forwards frames to destination addresses not in the forwarding database.
SECTION 2 " Features and Functional Overview Configuration of individual radio options and the WLIF wireless access point configuration are discussed in Section 4, “Configuration.” OWL/IP Port The OWL/IP port is a logical port used in installations where the wireless infrastructure is required to operate across multiple IP subnets; that is, in installations where IP routers are used.
SECTION 2 " Features and Functional Overview The forwarding database entry for a station on the other side of the tunnel includes the physical port (NIC1, NIC2, or Ethernet) the frame should be forwarded through, and an indication that encapsulation is required. The receiving access point on the other side of the tunnel de-encapsulates the frame and then forwards it on the correct physical port. OWL/IP is described in more detail in Section 4, “Configuration,” and Appendix E, “OWL/IP.
SECTION 2 " Features and Functional Overview The port uses a standard PC AT style cable, and operates at speeds up to 57.6 Kbps. Configuration using this port is described in Section 4, “Configuration.” Remote Access Remote access is available over TCP/IP connections using Telnet or Hypertext Transfer Protocol (HTTP) for configuration management, and Simple Network Management Protocol (SNMP) for network management.
SECTION 2 " Features and Functional Overview HTTP The access point supports configuration using HTTP from a workstation equipped with a Web browser. Internet Explorer or Netscape Navigator is recommended. See Section 4, “Configuration,” for more information about access through a Web browser. Electronic Software Distribution The access point supports electronic software distribution, which allows software upgrades after installation.
SECTION 2 " Features and Functional Overview Network Management The access point is instrumented for network management, with variables defined in the Management Information Base (MIB). The MIB is SNMP V1 compliant. Management information can be accessed through the SNMP agent. The MIB may be ordered separately and compiled for any SNMP network management platform. Additional capabilities are supported in the OWLView network management application for HP OpenView.
SECTION 2 Features and Functional Overview Terminal Emulation Gateway Host LAN Server " Distribution LAN 6710 Access Point 6710 Access Points Wireless Hop 6710 Access Point (Designated Bridge) Secondary Ethernet LAN PEN*KEYR 6400 Computer Notebook (WLIF) Desktop PEN*KEY 6400 Computer Figure 2-3 Sample Network Configuration 6710 Access Point User’s Guide 2-15
SECTION 2 " Features and Functional Overview Components Figure 2-4 shows access point components, described on the following pages. Not shown is the mounting bracket, which attaches the access point to a wall or ceiling.
SECTION 2 " Features and Functional Overview 1. Protective cover. The cover protects two Type II or Type III PC card slots. Figure 2-5 shows where the slots are located. 1 1 1. PC card slots Figure 2-5 PC Card Slots 2. Indicator lights. Four pairs of indicator lights (LEDs) on the front panel show the status of the access point. During the power-up sequence, the lights show the results of the power-up self diagnostics and provide information about the operating status.
SECTION 2 " Features and Functional Overview 3. Rubber feet. Four nonskid rubber feet provide a stable base for the access point when you place it on a desktop or other horizontal surface. When the mounting bracket is installed for an access point mounted vertically or on the ceiling, the rubber feet provide a small amount of tension to the bracket to help hold it in place. 4. AC INPUT. The AC INPUT connector is a standard IEC type, three-prong AC input connector.
SECTION 2 " Features and Functional Overview Accessories Power Cord The power cord connects the access point to the wall outlet. The following chart lists power cord part numbers. Country Part Number Australia 321-472-001 Denmark 321-501-001 Europe 321-473-001 Italy 321-471-001 Germany 321-515-001 United Kingdom 321-474-001 United States 321-054-001 Industrial Locking Mounting Bracket The Industrial Locking Mounting Bracket “locks” the access point into the bracket.
SECTION 2 2-20 " Features and Functional Overview 6710 Access Point User’s Guide
Section 3 Installation " " " " " " " " " " " " " " " " " " " " " " " " " " " " This section describes how to: " " " " " " " Check the access point’s default configuration. Prepare for the installation. Collect the networking equipment you need. Find the best location. Connect to the Ethernet medium. Install PC cards. Apply power.
SECTION 3 " Installation Preparing for the Installation " NOTE: Someone who knows and understands all applicable local building codes and is proficient with the tools and equipment used to install FCC Class B electromechanical devices should physically install the access point. Before you install the access point, unpack it and inspect it for damage or missing parts. Save all the paperwork you received.
SECTION 3 " Installation 10BASE2 Components 10BASE2 components include a T-connector, a cable terminator, and the proper lengths of 10BASE2 coax cable. The 10BASE2 T-connector (Figure 3-1) attaches to the access point’s 10BASE2 port, and connects the access point to the middle or end of 10BASE2 cable. Figure 3-1 T-Connector A cable terminator (Figure 3-2) attaches to the T-connector. It is required for a device connected to the end of 10BASE2 cable.
SECTION 3 " Installation 10BASE5 Components 10BASE2 components include the proper lengths of 10BASE5 coax cable, an AUI drop cable (less than or equal to 50 feet/15 meters long), and a transceiver. Two types of transceivers are the intrusive N-Series transceiver and the nonintrusive vampire tap. The N-Series transceiver (Figure 3-4) is a T-shaped connector with a 15-pin AUI port and two type N connectors.
SECTION 3 " Installation Figure 3-5 Vampire Tap Communication Equipment You can access the access point’s system software configuration menus locally through the unit’s DIAG port, or remotely through a Telnet session or Web browser. Local DIAG Port Access For local access, you need the following: " " " Third-party communications software terminal emulation package with Y-modem capability (such as PROCOMM PLUS by DataStorm Technologies, Inc.). Install the program according to its user guide.
SECTION 3 " Installation For this PC Port Use Cable Part Number 9-pin 25-pin 226-106-001 (null modem cable) 321-355-001 Telnet You need the following to access the configuration menus through a Telnet session: " " " PC or workstation with an installed and configured network interface card and a Telnet application. You can also use a host capable of acting as a Telnet client. Telnet VT emulator (TNVT) installed on the PC. IP address for the access point.
SECTION 3 " Installation Finding the Best Location Site Survey Intermec strongly recommends that Intermec or certified providers conduct a site survey to determine the ideal locations for all of your network components. A proper site survey requires special equipment and training. A site survey provides an installation recommendation that addresses various factors, which can affect the performance of your wireless LAN system.
SECTION 3 " Installation " " " Ensure that a power outlet is within 6 feet of the access point. An uninterruptable power supply is recommended when the ac power system is not reliable. Ensure that LAN and ac cables can reach the access point after you install it. Leave sufficient room around the access point so you can easily attach and remove cables. Do not locate an access point with the S-UHF radio option in a computer room.
SECTION 3 " Installation Vertical and Ceiling Mounts See Figure 3-6 and the procedure following it. " NOTE: If mounting the access point on a hollow wall, secure the mounting plate to a 3/4” (thick) plywood base by four 1” X 1/4” nuts, bolts, and washers. Anchor the plywood base to two separate wall studs by four 2” X 1/4” diameter lag screws (two lag screws in each stud). 6.00" 1.00" 2.00" 1.00" 2.00” 1.
SECTION 3 " Installation 1. Inspect where the access point will be mounted and determine what hardware is needed. Different surfaces such as drywall, wood, and concrete block require different mounting hardware. For this reason, a universal mounting bracket is included with the access point. 2. Remove the mounting plate from the bottom of the access point. 3. Using the mounting plate as a template, mark where the anchors that secure the mounting plate to the surface should be located. 4.
SECTION 3 " Installation 10BASE2 Ethernet The access point connects to the end or middle of the 10BASE2 cable segment. " NOTE: Cable lengths between network devices on the 10BASE2 Ethernet LAN must meet ANSI/IEEE standards. End of Segment See Figure 3-7 and the procedure following it. 10 BASE 2 10 BASE T DIAG AUI AC INPUT 100/240 VAC 1 2 3 1. Cable terminator (50 ohm) 2. T-connector 3. 10BASE2 cable Figure 3-7 End of 10BASE2 Segment 1. Plug the T-connector (2) into the 10 BASE 2 port. 2.
SECTION 3 " Installation Middle of Segment See Figure 3-8 and the procedure following it. 10 BASE 2 10 BASE T DIAG AUI AC INPUT 100/240 VAC 1 2 1 1. 10BASE2 cable 2. T-connector Figure 3-8 Middle of 10BASE2 Segment 1. Plug the T-connector (2) into the 10 BASE 2 port. 2. Plug one end of the Ethernet coaxial cable (1) into an open end of the T-connector. Align the notches in the cable end with the posts on the T-connector, push the cable in, and twist about one-quarter turn. 3.
SECTION 3 " Installation 10BASE5 Ethernet The access point connects to 10BASE5 through an N-Series transceiver or vampire tap. " NOTE: Cable lengths between network devices on the 10BASE5 Ethernet LAN must meet ANSI/IEEE standards. N-Series Transceiver See Figure 3-9 and the following procedure. 1. Attach one end of the drop cable (1) to the AUI port. 2. Route the drop cable to the 10BASE5 cable (4) and determine a suitable spot to cut the cable and attach the transceiver (3). 3.
SECTION 3 " Installation 10 BASE 2 DIAG AUI 10 BASE T AC INPUT 100/240 VAC 1 3 2 4 1. 2 3. 4.
SECTION 3 10 BASE 2 10 BASE T " Installation DIAG AUI AC INPUT 100/240 VAC 1 3 2 4 1. 2. 3. 4.
SECTION 3 " Installation 10BASE-T Ethernet See Figure 3-11 and the procedure following it. 10 BASE 2 10 BASE T AUI DIAG AC INPUT 100/240 VAC 1 1. Cable with RJ45 plugs 2. RJ45 jack (or hub port) Figure 3-11 10BASE-T 1. Plug the cable with RJ45 jacks (1) into the 10 BASE T port. 2. Plug the other end of the cable into RJ45 jack or hub port (2).
SECTION 3 " Installation Installing PC Cards The following pages describe how to install WLIF, 900 MHz, and S-UHF PC cards. WLIF The WLIF radio option is a Type III PC card that can be installed in either slot. To install the card, see Figure 3-12. 1 2 3 4 5 6 4 7 1. 2 3. 4. 5. 6. 7.
SECTION 3 " Installation 900 MHz The 900 MHz radio option is a Type III PC card that can be installed in either slot. To install the card, see Figure 3-13. 1 2 3 4 5 4 6 7 1. 2 3. 4. 5. 6. 7.
SECTION 3 Installation " S-UHF The S-UHF radio option is a Type II PC card that can only be installed in the left-hand slot (with LEDs facing down). To install the card, see Figure 3-14. 1 1. 2 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 2 3 4 Nonskid rubber feet (4) Access point (no radio) Sliding latch (open for RM111 adapter) PC card (RM111) Flex circuit RM111 adapter Radio bracket Conductive washer End plate 4-- 40 captive thumb screws 4-- 40 x .
SECTION 3 " Installation Applying Power B CAUTION: NEVER remove the cover of the access point with power applied. ALWAYS make the access point connection before making the connection at the source (“load to source”). Damage to the radio or other devices can occur with the cover removed. " NOTE: Connect the access point to an uninterruptable power source — a power source that cannot be inadvertently turned off or otherwise disconnected.
SECTION 3 10 BASE 2 10 BASE T " Installation DIAG AUI AC INPUT 100/240 VAC 1 2 1. Receptacle on power cord 2.
SECTION 3 3-22 " Installation 6710 Access Point User’s Guide
Section 4 Configuration " " " " " " " " " " " " " " " " " " " " " " " " " " " " This section describes how to: Create a local DIAG port, Telnet, and Web browser session with the access point. " Access the access point’s FLASH and ROM. " Set up the access point through its configuration menus. You can configure the access point locally through its DIAG port, or remotely through Telnet or a Web browser. The following chart shows the sessions you can use to do other tasks.
SECTION 4 " Configuration Only one type of session can be running at a time. For example, if someone starts a Telnet session while someone else is configuring the access point through its DIAG port, the configuration through the DIAG port will terminate. Creating a Local DIAG Port Session In summary, you establish a local DIAG port session with the access point through a VT100 terminal emulation program. Most general purpose communications software (such as PROCOMM PLUS) supports this emulation.
SECTION 4 " Configuration 1 2 3 10BASE2 10BASET AUI DIAG AC INPUT 100/240 VAC 1. PC with terminal emulation program 2. Cable: 321-355-001 for a 25-pin PC COM port or Cable: 226-106-001 for a 9-pin PC COM port (standard null modem cable) 3. 6710 Access Point DIAG port Figure 4-1 Local Session 1. Ensure the terminal emulation program is installed on the PC. 2. With both the PC and access point powered OFF, connect the communication cable to the appropriate PC COM port.
SECTION 4 " Configuration 3. Connect the other end of the communication cable to the DIAG port on the access point. Turn the PC on. 4. After the PC boots, start the terminal emulation program. 5. Set the terminal emulation program’s options according to what you want to do: Access the configuration menus, or access the ROM command monitor. Accessing the Configuration Menus 1. Set the terminal emulation parameters in your communications software.
SECTION 4 " Configuration Accessing the ROM Command Monitor 1. Set the terminal emulation parameters in your communications software. If you are configuring this access point for the first time, set the parameters to the default settings for ROM mode: 9600, 8N1, full duplex If you have already changed the default settings, set the parameters to those you set in ROM mode through the ROM command monitor. 2. Plug the access point into the outlet.
SECTION 4 " Configuration Creating a Telnet Session Before you can configure the access point through Telnet, you must connect the unit to the Ethernet cable. (See Section 3, “Installation,” for help.) You must also perform initial configuration through the DIAG port to: " " " NOTE: Set an IP address or DHCP server name. You should also configure a subnet mask and IP router address. Set the Ethernet cable type.
SECTION 4 " Configuration 1. Ensure the access point is connected to the Ethernet cable, and has an assigned IP address and cable type. 2. Ensure the PC or workstation has an installed and configured Ethernet interface card. 3. Ensure the Telnet VT emulator is installed on the PC or workstation. 4. Open a new Telnet session on the PC or workstation. 5. Enter the access point’s IP address in the host name or IP address field. 6. See “Configuring the Access Point” on page 4-12.
SECTION 4 " Configuration Security Option Default Password Service Password Advanced Password CR52401 Enabled “” (empty string) Site Setting Bridge Option Default Serial Number Lan ID [Root] Root Priority [Global Radio] UHF Rfp Threshold Set Globally Value UHF Frag Size Set Globally Value Falc Frag Size Set Globally Value Awake Time Set Globally Value [Global Flooding] Inbound Multicast Unicast Outbound to Secondaries Multicast Unicast Outbound to Stations Multicast Unicast (Read-only) 0 4-8 67
SECTION 4 Option [Ports] Ethernet port: Name MAC Address Status Hello Period [Ethernet] OWL Frame Type Cable Type [Static Addresses] [Normal RX Filter] [Frame Types] Action Scope [SubTypes 1] Action SubType Scope [SubTypes 2] Action SubType Scope [Advanced RX Filter] [Expressions] ExprSeq Offset Op Value Id Action [Values] Value [Bridging] Bridge Priority Status Flood Register Default " Configuration Site Setting omde (Unique number) Enabled 2 seconds DIX Auto Detect 00:00:00:00:00:00 Pass Unlisted P
SECTION 4 " Configuration Option WLIF radio port: Name MAC Address Status Hello Period [WLIF] Security Id Node Type [Master Parms] Channel Subchannel Wireless Hops MAC Config [Manual MAC Parms] Hop Period Beacon Frequency Deferral Slot Fairness Slot Fragment Size Transmit Mode Norm Ack Retry Frag Ack Retry Norm QFSK Retry Frag QFSK Retry 900 MHz radio port: Name MAC Address Status Hello Period [Falcon] File Name Mode--Channel ARP Server Mode 4-10 6710 Access Point User’s Guide Default omdpxma (Unique
SECTION 4 Option S-UHF radio port: Name MAC Address Status Hello Period [UHF] File Name Call Sign Frequency Master Mode Attach Priority OWL/IP port: Name MAC Address Status Hello Period [OWL/IP] Mode [IP Addresses] Type Address [TX Filter] [Frame Types] Action Scope [SubTypes 1] Action SubType Scope [SubTypes 2] Action SubType Scope Default " Configuration Site Setting omduhfb (Unique number) Enabled 2 seconds synuhf_d.
SECTION 4 " Configuration Configuring the Access Point When you create a local DIAG port or remote Telnet session with the access point, the configuration program’s password screen appears: Configuration of Access Point Copyright (c) 1995-1997 Norand Corporation. All rights reserved. Portions copyright Epilogue Technology Corporation 1988-1995. All rights reserved IP: Serial: 0.0.0.0 (Unique 10-digit number.
SECTION 4 " Configuration Loading configuration from EEPROM Command File View Clear Read Write Reboot Exit ? Description File system menu View/modify the configuration Set the configuration to default values Read the configuration from EEPROM Write the configuration to EEPROM Restart using last written configuration Disconnect Display this help > The menu lists the commands you can use to do various tasks, described on the following pages. The screen also displays the command prompt (>).
SECTION 4 " Configuration Use To Read The access point’s configuration is stored in (Continued) EEPROM. You reprogram the EEPROM whenever you change the configuration, write (save) the new configuration to EEPROM, and reboot the access point. Write Write (save) a new configuration to EEPROM. This command overwrites the previous configuration. You must write the new configuration to EEPROM and reboot the access point for any changes to take effect. Reboot Reboot the access point.
SECTION 4 " Configuration Use To [Tcpip] Page 4-16 Set options necessary for communications with this access point. The options apply to all TCP/IP ports. Telnet, SNMP, and HTTP communications are supported. Control the bridging of messages among the radio and Ethernet ports for this access point. Settings to control interaction with other access points are also under the [Bridge] option. Set the configuration program’s top-level password and other security passwords.
SECTION 4 " Configuration TCP/IP Options Use [Tcpip] to set options necessary for communications with this access point, such as IP addresses. Addresses are required for remote setup or SNMP network management. Options are: IP Address IP Subnet Mask IP Router IP Frame Type DHCP DHCP Server Name Auto ARP Minutes 0.0.0.0 255.255.255.0 0.0.0.0 “Norand DHCP Server” 5 IP Address IP Address is the unique address locally assigned to this access point.
SECTION 4 " Configuration The host number is “h.h.” This Class B network address is reserved by the numbering authority for a company’s internal use. If the Class B address appears on the Internet, routers drop the data. Note the following: If the IP address is 0.0.0.0 and DHCP is set to “Enabled, if IP address is zero,” this IP address is obtained through DHCP. " If DHCP is set to Enabled, DHCP is used to obtain the IP address. " If the IP address is 0.0.0.
SECTION 4 " Configuration 16 bits of network address. " 5 bits of subnet address. Do not use all 0’s or all 1’s. " 11 bits of host address. Do not use all 0’s or all 1’s. The following chart lists IP addresses when the submask is 255.255.248.0. " Subnet 1 2 3 . . . 30 First Address 172.16.8.1 172.16.16.1 172.16.24.1 Last Address 172.16.15.254 172.16.23.254 172.16.31.254 172.16.240.1 172.16.247.
SECTION 4 " Configuration A router that connects subnet 1 to subnet 2 might have the address 172.16.8.1 on subnet 1 and 172.16.16.1 on subnet 2. A host with IP address 172.16.16.5 would specify an IP router address of 172.16.16.1 to reach host 172.16.8.10. IP routers are usually configured so a computer only needs to know one router’s address. This is true even if several routers on the segment connect to several other segments.
SECTION 4 " Configuration Setting Description Enabled DHCP always obtains IP addresses for the access point, subnet mask, and (optional) default router when the access point reboots. It also obtains the lease expiration time. If IP Address is 0.0.0.0, DHCP obtains IP addresses for the access point, subnet mask, and (optional) default router. It also obtains the lease expiration time. The access point ignores other DHCP configuration options. Disables DHCP.
SECTION 4 " Configuration The class identifier string for the access point is “Norand Access Point.” Servers use this string to identify the access point. Bootp Operation The access point can also accept addresses from a Bootp server identified in the DHCP server name field. An address offer from a Bootp server is treated as if it were an infinite lease from a DHCP server.
SECTION 4 " NOTE: " Configuration DHCP is documented in RFCs 1533, 1534, and 1541. Bootp is documented in RFC 951. Auto ARP Minutes The access point periodically sends an unsolicited ARP response so routers can update their routing tables. The response enables a network management platform to learn about the access point on the network by querying routers. Auto ARP Minutes is the number of minutes between periodic ARP requests. The prompt is: Range is: 0..120 The default is 5 minutes.
SECTION 4 " Configuration Bridge Options Use [Bridge] to configure options that define the bridging topology of the open wireless LAN. Options are: Serial Num ber Lan ID [Root] [Ports] ARP Server Mode “(Unique 10-digit number.)” 0 Serial Number Serial Number is a read-only setting that displays this access point’s unique 10-digit serial number, which identifies this unit on the network.
SECTION 4 " Configuration You should change the default of 0 to another number to avoid a potential conflict with an adjacent network. All access points and wireless stations in the same network must have the same LAN ID. " NOTE: See page 4-87 for information about combining WLIF, 900 MHz, and S-UHF radios in a common network by following basic guidelines for LAN ID and controller setup. [Root] [Root] options apply to access points configured to operate as the super root.
SECTION 4 " Configuration Super Root Selection The access point with the highest assigned root priority becomes the super root whenever it is powered on and active. If the current super root goes offline, the remaining candidates negotiate to determine which one becomes the new super root. This normally takes about 1 minute. The super root is always the access point with the highest root priority (other than 0).
SECTION 4 " Configuration The previous sample screen shows the options’ default settings, which are optimum for most installations. It is recommended that you not change the defaults. Option Description UHF Rfp Threshold This option adjusts the S-UHF protocol characteristics for smaller data frames. The recommended setting in most cases is Disabled. For installations that primarily send very small frames, Enabled at the default value of 70 may improve network response time.
SECTION 4 " Configuration Each [Global Radio] option has the following settings: Set Globally Value 0 Set Globally The value for all radios in the system is specified according to how Set Globally is configured. Setting Description Enabled If this access point is the super root, it sets the value for all stations and access points in the network. This setting has no effect in access points other than the super root. The super root does not distribute global parameters.
SECTION 4 " Configuration [Global Flooding] " NOTE: Use the same [Global Flooding] settings in all super root candidates. Use [Global Flooding] to set system-wide flooding options. The settings are sent throughout the network when and if this access point becomes the super root.
SECTION 4 " Configuration Inbound options are: Multicast Unicast Multicast and Unicast options have the following settings: Enabled Primary Disabled Setting Description Enabled Access point floods to all ports, similar to a conventional bridge. Primary Frames are flooded inbound only. This (Multicast default) setting is useful in many wireless installations where the super root, servers, or gateways for wireless stations are on the same Ethernet segment.
SECTION 4 " Configuration Setting Description Enabled All designated bridges flood to secondary LANs. This setting allows the super root to control flooding for all access points serving as designated bridges for secondary LANs (see page 4-57). Designated bridges flood according to their individual flood register settings. This setting allows individual designated bridges to be configured separately. Flooding is disabled in all designated bridges.
SECTION 4 " Configuration Flooding Level Checklist You can use the following list of questions to determine the required flooding levels for the Inbound and Outbound to Secondaries options. The list is structured so that you should skip later questions as soon as you determine the appropriate flood level settings. If your answer is “I do not know,” go to the next question. If you cannot determine the appropriate flooding levels, use the higher (multicast) flooding levels.
SECTION 4 " Configuration 2. Does the network contain only 900 MHz or S-UHF access points? Answer Settings Yes Inbound/Unicast/Disabled Outbound to Secondaries/Unicast/Disabled Comments: Unicast flooding is never required for 900 MHz or S-UHF access points, since stations supporting these media options establish reliable connections as they roam between access points. The correct port for S-UHF or 900 MHz stations is always known. 3.
SECTION 4 " Configuration 5. Do nodes in the radio network communicate with other nodes in the radio network? Answer Settings Yes Inbound/Unicast/Enabled Inbound/Multicast/Enabled Inbound/Unicast/Primary Inbound/Multicast/Primary Outbound to Secondaries/Unicast/Registered Outbound to Secondaries/Multicast/Registered No Comments: The Enabled settings facilitate peer-to-peer applications, where nodes in the open wireless LAN communicate with each other.
SECTION 4 " Configuration 7. Does the radio network contain WLIF nodes that do not periodically generate traffic? Answer Setting Yes Inbound/Unicast/Primary Outbound to Secondaries/Unicast/Registered* or Inbound/Unicast/Enabled** * Support communications with a distribution LAN. ** Supports general peer-to-peer communications. " NOTE: WLIF nodes using NORAND terminal emulation periodically generate traffic, and do not require flooding.
SECTION 4 " Configuration 8. Does the radio network contain a secondary Ethernet LAN(s) with connected nodes that do not periodically generate traffic? Answer Setting Yes Outbound to Secondaries/Unicast/Enabled Alternatively, you can configure permanent addresses in the Static Address Table (page 4-42). 9.
SECTION 4 " Configuration S-UHF Flooding Level Because of its low bandwidth, S-UHF is vulnerable to excess traffic from busy backbones. The recommended settings for S-UHF is Inbound/Disabled and Outbound to Secondaries/Disabled (for the multicast and unicast options). These settings prevent excessive traffic from being forwarded onto the RF medium. Flood Register You can use the Inbound option and Outbound to Secondaries option in combination with the Flood Register setting for the Ethernet port.
SECTION 4 " Configuration Setting Description Disabled (default) No special action is taken when an ARP is received. Multicast ARP requests are subject to the Ethernet filters and the flooding settings. The Disabled setting is useful when a system has no IP radio traffic or has stations that do not register IP addresses. ARP server converts ARPs from multicast to the unicast address of the destination station. No Flooding is the most efficient configuration, since multicast ARPs are never forwarded.
SECTION 4 " Configuration [Ports] Use [Ports] to define options for the access point’s Ethernet port, radio ports, and OWL/IP (IP tunneling) port. The following sample screen shows all the ports.
SECTION 4 " Configuration Name, MAC Address, Status, and Hello Period appear for all ports. The remaining options appear as follows: [Ethernet] [WLIF] [Falcon] [UHF] [OWL/IP] Appears if you selected “omde.” Options start on page 4-41. Appears if you selected “omdpxma” (or “omdpxmb”) and a WLIF radio is installed in either PC card slot. Options start on page 4-60. Appears if you selected “omdflca” (or “omdflcb”) and a 900 MHz radio is installed in either PC card slot. Options start on page 4-74.
SECTION 4 " Configuration Status The Status option sets the condition of the Ethernet port or radio port. Settings are: Enabled Disabled Setting Description Enabled (default) Port is available for use. Disabled Port is not available for use. Hello Period The hello period determines how frequently the access point broadcasts hello messages on the network. On Ethernet links and wireless links between access points, hello messages are used to maintain the spanning tree.
SECTION 4 " Configuration Ethernet Options Use [Ethernet] to set Ethernet port options: OWL Frame Type Cable Type [Static Addresses] [Normal RX Filter] [Advanced RX Filter] [Bridging] OWL Frame Type OWL Frame Type is the Ethernet type for communication among access points (open wireless LAN frames). Settings are: DIX SNAP Setting Description DIX (default) Adds DIX (Ethernet 2.0) header to open wireless LAN frames.
SECTION 4 " Configuration Cable Type Cable Type specifies the type of Ethernet medium to which the access point is connected. It is recommended that you explicitly set the cable type. Settings are: 10BaseT 10Base2 AUI Auto Detect Setting Description 10BaseT Selects the RJ11 connector (sets type to 10BASE-T, twisted pair). The cable type defaults to 10BASE-T if no traffic is heard on any Ethernet port (10BASE2, 10BASE5, or 10BASE-T) during a 10-second time window when the access point starts up.
SECTION 4 " Configuration 1 00.00.00.00.00.00 2 00.00.00.00.00.00 3 00.00.00.00.00.00 . . . 20 00.00.00.00.00.00 Select an address, then type 6 hexadecimal pairs for the new address at the prompt: Range is: 6 hex pairs Static addresses become permanent entries in the route table. This is useful when configuring designated bridges for secondary LANs, since it reduces the need to flood frames to wired stations on the secondary LAN segment.
SECTION 4 " Configuration [Frame Types] allows filters to be established for common networking protocols such as IP, Novell IPX, and 802.2 LLC (Logical Link Control). Separate selections are available for each of the three Ethernet standards: DIX (Ethernet 2.0), 802.3, and 802.3 SNAP. A filter may be configured to pass or drop all frames of a given type. Alternatively, filters may be set to operate on selected subtypes within each frame type category.
SECTION 4 " NOTE: " Configuration Frame Type Description DIX--IP--TCP Ports DIX--IP--UDP Ports SNAP--IP--TCP Ports SNAP--IP--UDP Ports DIX--IP--Other Protocols SNAP--IP--Other Protocols DIX--IPX Sockets SNAP--IPX Sockets 802.3--IPX Sockets DIX--Other EtherTypes SNAP--Other EtherTypes 802.2--IPX Sockets Primary Internet Protocol Suite (IP) transport protocols. 802.2--Other SAPs SAPs other than IPX or SNAP. IP protocols other than TCP or User Datagram Protocol (UDP). Novell NetWare protocol.
SECTION 4 " Configuration Setting Description Scope Defines whether the action applies to all frames of this type, or is restricted to selected subtypes: Unlisted Applies only to subtypes that are not (default) configured under [SubTypes 1] or [SubTypes 2]. All Applies to all frames of this type. [SubTypes 1] and [SubTypes 2] settings for this frame type are ignored. [SubTypes 1] The predefined subtypes in the [SubTypes 1] menu provide preconfigured filters that are useful in many networks.
SECTION 4 " Configuration Subtypes for [SubTypes 2] are: Action 1 2 3 . . . 22 SubType Value 00 00 00 00 00 00 00 00 Subtype Value DIX--IP--TCP--Port Port value in hexadecimal. DIX--IP--UDP--Port Port value in hexadecimal. DIX--IP--Protocol Protocol number in hexadecimal. DIX--IPX--Socket Socket value in hexadecimal. DIX--EtherType Specify the registered DIX type in hexadecimal.
SECTION 4 " Configuration Filtering Examples The following network examples illustrate how filters may be set to optimize wireless performance. The sample network in Figure 4-3 contains the following: " " " " " NOTE: 4-48 Wireless stations using IP. A secondary LAN containing IP and IPX hosts, linked by access points (AP) 2 and 4. An IPX router connecting to another Novell network. DIX and 802.3 SNAP frames. Many networks use only one Ethernet frame type. DIX is the most common type.
SECTION 4 AP 1 (Super Root) IP Host " Configuration Novell Server Distribution LAN IPX Router AP 3 AP 2 IP Wireless Stations AP 4 AP 5 AP 6 IP Host IPX Host Secondary LAN Figure 4-3 Access Points Servicing IP Wireless Stations Example 1 Access points 1, 3, 5, and 6 in Figure 4-3 service only IP wireless stations. In these access points it is desirable to pass necessary IP traffic, but eliminate unnecessary IPX traffic. These do not need to be forwarded to the secondary LAN.
SECTION 4 " Configuration In example 1, [Frame Types] is set as follows: DIX-IP-TCP Ports DIX-IP-UDP Ports DIX-IP-Other Protocols DIX-IPX Sockets DIX-Other EtherTypes SNAP-IP-TCP Ports SNAP-IP-UDP Ports SNAP-IP-Other Protocols SNAP-IPX Sockets SNAP-Other EtherTypes 802.3-IPX Sockets 802.2-IPX Sockets 802.
SECTION 4 " Configuration In example 2, [Frame Types] is set as follows: DIX-IP-TCP Ports DIX-IP-UDP Ports DIX-IP-Other Protocols DIX-IPX Sockets DIX-Other EtherTypes SNAP-IP-TCP Ports SNAP-IP-UDP Ports SNAP-IP-Other Protocols SNAP-IPX Sockets SNAP-Other EtherTypes 802.3-IPX Sockets 802.2-IPX Sockets 802.
SECTION 4 " Configuration [Advanced RX Filter] If you need more flexibility than that provided by [Normal RX Filter], you can use the tables for [Advanced RX Filter] to specify additional filters. Settings for [Advanced RX Filter] execute after those for [Normal RX Filter]. For example, if [Normal RX Filter] dropped a frame, the frame cannot be “undropped.” If [Normal RX Filter] passed a frame, [Advanced RX Filter] then executes.
SECTION 4 ExprSeq Offset 1 0 2 0 3 0 . . . 22 0 Mask 0 0 0 0 Op Value Id " Configuration Action 0 0 0 0 Filter expressions have the following settings: ExprSeq Offset Mask Op Value Id Action 0 0 0 ExprSeq ExprSeq contains a sequence number that orders expressions in ascending order. It is a method of changing the sequence execution. The prompt is: Range is: 0..65535 The default is 0. Change these numbers as needed for reordering.
SECTION 4 " Configuration Offset This setting defines the offset in a received Ethernet frame to match the patterns. The prompt is: Range is: 0..65535 A frame matches a pattern list if the masked bytes at the specified offset in the frame match any of the masked patterns in the pattern list. The default is 0. Mask This setting indicates the bits that are significant at the specified offset. The prompt is: Range is: 8 hex pairs The default is “” (an empty string).
SECTION 4 " Configuration Value Id The field at the specified offset is compared with values in the Value Table with the Value Id. The prompt is: Range is: 0..255 The default is 0. When using a comparison operator that requires a single value (LT, LE, GE, and GT), only the first value found will be compared. Action The Action setting instructs the Ethernet driver and indicates what should happen when this expression is true.
SECTION 4 " Configuration [Values] Use [Values] to enter pattern lists that contain byte patterns that match consecutive bytes in received Ethernet frames. Settings for [Values] are referenced by the Value Id from the Expression Table. The values to be used in a filter expression are as follows: Value Id 1 2 3 . . . 22 Value 0 0 0 0 Filter expression values have the following settings: Value Id Value Setting Description Value Id An identifier used by an expression in the Expression Table.
SECTION 4 " Configuration [Bridging] [Bridging] options are: Bridge Priority Status Flood Register 1 Bridge Priority The bridge priority allows selection of the access point serving as a designated bridge for a secondary LAN. As with the root priority, the bridge priority allows designation of access points as primary or fallback bridges. The prompt is: Range is: 0..7 " NOTE: The S-UHF radio option does not support designated bridging.
SECTION 4 " Configuration Designated Bridge Selection If the current designated bridge goes offline, the remaining candidates negotiate to determine which one becomes the new designated bridge. Summary In summary, the designated bridge: " " " Physically connects to a secondary Ethernet LAN. Is within the radio coverage area of an access point on the distribution LAN. Has the highest nonzero bridge priority.
SECTION 4 " Configuration Flood Register As the designated bridge for this secondary Ethernet LAN, the access point can register the type of frames it expects to flood — unicast, multicast, or both. This information is registered with other access points. Setting [Global Flooding] settings in the super root overrides individual Flood Register settings in designated bridges.
SECTION 4 " Configuration Setting Description Enabled Multicast and unicast flooding occurs. (The super root disables flooding if the Outbound to Secondaries Multicast or Unicast option is set to Disabled.*) * See page 4-29 for more information about Outbound to Secondaries. Global flooding settings in the super root take precedence over Flood Register settings. WLIF Options " NOTE: Appendix B provides additional information about the WLIF radio. Use [WLIF] to set Proxim 2.
SECTION 4 " Configuration The default security ID is NORANDOWL. All WLIF access points and wireless stations in the network must have the same security ID to communicate. The security ID is case sensitive. That is, if the access point’s security ID is in uppercase, the wireless station’s must also be in uppercase. Refer to the wireless station’s user guide for more information about setting its security ID.
SECTION 4 " Configuration [Master Parms] [Master Parms] contains parameters the access point needs when you configure it as a Master radio. Settings are: Channel Subchannel Wireless Hops 1 1 Channel and Subchannel Channel sets this radio’s hopping sequence. Subchannel enables access points to share the same channel without receiving another access point’s frames. The prompt for Channel and Subchannel is: Range is: 0..15 The default for Channel and Subchannel is 1.
SECTION 4 " Configuration Network With 15 or Fewer Access Points If 15 or fewer access points are on the network, the channel should be different for all access points. The subchannel can be the same as or different than the channel.
SECTION 4 " EXAMPLE 2: 4-64 Configuration If 43 access points are on the network, 1 to 15 could be assigned the channel and subchannel numbers in the previous example.
SECTION 4 " Configuration Wireless Hops To create a wireless hop, you must enable one or more WLIF radios on the distribution LAN as wireless hopping Masters and then configure the Slave stations (through [Slave Parms]) to connect to these Masters. EXAMPLE: In Figure 4-4, two access points have two WLIF radios. One radio is configured as a Master to provide the wireless connection to the distribution LAN. The other radio is configured as a Slave to service wireless station traffic.
SECTION 4 " Configuration Settings for the Master are: Enabled Disabled Setting Description Enabled Sets up this access point’s radio port to wireless hop. This access point honors connections from an access point with a Slave radio. Prevents this access point’s radio port from wireless hopping. This access point does not honor connections from an access point with a Slave radio.
SECTION 4 " " " NOTE: " Configuration An Ethernet segment. The radio range of a single access point with two radios. One radio must be operating as a Master to service wireless station traffic. The other radio must be operating as a Slave to provide the wireless hop to the distribution LAN. You must set the Root Priority for the access point with the Slave radio to 0 to prevent it from becoming the open wireless LAN super root.
SECTION 4 " Configuration The Slave access point synchronizes with Masters whose channel and subchannel appear in the list of configured Masters. Precedence is given by the order of the list. Master 1 has highest precedence; Master 8 has lowest. Channel and subchannel settings can be 0, where 0 means “do not care.” For example: You can set the Master 1 channel to 0 and subchannel to 1. The Slave synchronizes with any Master on any channel as long as the Master’s subchannel is 1.
SECTION 4 " Configuration Setting Description Default (default) Uses the factory-set settings for the radio protocol (settings are located under [Manual MAC Parms]). The Default setting should be used for normal operation. Interference Optimizes the settings for the radio protocol for better performance in environments with high interference or multipath.
SECTION 4 " Configuration Hop Period Hop Period sets the hopping time period, which determines how long the radio stays on a frequency in the hopping sequence before stepping to the next frequency. Settings are: 100 ms 200 ms 400 ms The default is 200 ms. A longer period results in better throughput. A shorter period results in faster roaming response and better immunity from interference.
SECTION 4 " Configuration Settings for both options are: Default 1 3 7 The default setting is Default. You can do the following: Reduce the number of slots on lightly-loaded networks to increase throughput. " Increase the number to help prevent repeated collisions under a heavy load. You can set Fairness Slot as follows: " " " Increase the number to prioritize the channel access for nodes that have been waiting the longest to access the channel.
SECTION 4 " Configuration Smaller fragments may allow successful operation in an environment with a high level of interference at the expense of throughput. Transmit Mode Transmit Mode modulates the transmit signal and sets the bits per second. Settings are: BFSK QFSK AUTO Setting Description BFSK Binary Frequency Shift Keying. Transmits at 0.8 Mbps per second. Data is transmitted by shifting between two frequencies to represent one bit of 0 or 1.
SECTION 4 " Configuration The number includes retries that occurred in QFSK mode, and should be larger than Norm QFSK Retry. A value of 255 (default) indicates that the radio may choose an optimum value. Frag Ack Retry Frag Ack Retry is the number of times any fragmented frame (QFSK or BFSK) is resent unsuccessfully before failure. The prompt is: Range is: 1..255 Frag Ack Retry should be larger than Frag QFSK Retry. A setting of 255 (default) indicates that the radio may choose an optimum value.
SECTION 4 " Configuration The default is 255. The retries that occur are also counted by Frag Ack Retry. Frag QFSK Retry should be smaller than Frag Ack Retry. 900 MHz Options " NOTE: Appendix C provides additional information about the 900 MHz radio. Use [Falcon] to set 900 MHz radio options: File Name Mode-Channel ”falcon_d.29k” File Name File Name is the name of the radio’s driver software. Only change this name when directed to do so by a Systems Engineer.
SECTION 4 " Configuration For example, in the United States the following combinations are valid: DS DS DS DS DS DS DS DS DS 225K-Channel 090K-Channel 090K-Channel 090K-Channel 090K-Channel 090K-Channel 090K-Channel 090K-Channel 450K-Channel 25 10 15 20 25 30 35 40 25 The following chart describes the settings shown in the previous sample screen: Setting Description DS 225K--Channel 25 Uses one Direct Sequenced channel at 225,000 bits per second.
SECTION 4 " Configuration S-UHF Options " NOTE: Appendix D provides additional information about the S-UHF radio. Use [UHF] to set S-UHF radio options: File Name Call Sign Frequency Master Mode Attach Priority " NOTE: “synuhf_d.29k” “” (First frequency in list.) Attach Priority displays if Master Mode is set to Disabled. File Name File Name is the name of the radio’s driver software. Only change this name when directed to do so by a Systems Engineer.
SECTION 4 " Configuration The callsign is granted as part of the FCC license process. Insert the callsign from the FCC license certificate at the callsign prompt. Frequency The Frequency option displays a list of frequencies programmed at the factory. Some radios have multiple frequencies. For example: 466170000 Hz 530000000 Hz The default frequency is the first frequency programmed into the list.
SECTION 4 " Configuration Setting Description Enabled The access point controls channel access for stations in its coverage area. Access point and stations coordinate channel access. Disabled (default) Attach Priority If the access point is operating with Master Mode disabled, the attach priority of the access point can be specified. Stations in the coverage area of two access points with different attach priorities normally attach to the higher priority access point.
SECTION 4 " Configuration OWL/IP Options " NOTE: Appendix E provides additional information about OWL/IP and contains configuration examples. Overview The OWL/IP extension to the open wireless LAN architecture enables a wireless LAN installation to span multiple IP subnets. OWL/IP is an advanced capability that requires basic knowledge of IP addressing conventions and routing to configure and use. You should review the following pages and Appendix E before using this capability.
SECTION 4 " Configuration Server or Gateway Super Root AP 3 IP Router Remote Subnet 1 Home Subnet AP 2 (Designated Bridge) AP 1 Tunnel Tunnel IP Router Remote Subnet 2 Non-IP Station AP 4 (Designated Bridge) IP Station Figure 4-5 OWL/IP Overview The super root can originate IP tunnels to eight or fewer IP addresses. The number of tunnels supported may be more than or fewer than eight, depending on the type of addressing used and redundancy needs within the installation.
SECTION 4 " Configuration Select primary and fallback super root access points on the home subnet. IP addresses for wireless stations used with OWL/IP must belong to the home subnet. See OWL/IP limitations in Appendix E. 2. Select access points on each remote subnet to serve as designated bridges for those subnets. Configure primary and fallback bridge priorities under the [Bridging] menu, described on page 4-57. Configure and record the IP addresses of all designated bridges.
SECTION 4 " Configuration OWL/IP Menu OWL/IP configuration menu options are: Mode [IP Addresses] [TX Filter] In summary: " " " The Mode value specifies the operation of the access point when the OWL/IP port is enabled. This value determines whether the access point is configured to serve as the originator or termination of a tunnel.
SECTION 4 " Configuration [IP Addresses] The configuration screen for [IP Addresses] is: 1 2 3 4 5 6 7 8 Type Address 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.0.0 Each line in the IP Addresses Table contains one IP address entry. Settings are: Type Address 0.0.0.
SECTION 4 " Configuration Setting Description Unicast (default) Standard IP routing is used. Frames are forwarded to the unicast MAC address of the router. This is either the default router specified in the [Tcpip] configuration menu of the access point, or an alternative router assigned by ICMP redirect. Multicast Reserved for future use. Broadcast OWL/IP frames are sent using an Ethernet broadcast address. This capability allows use of directed, and All Subnets IP addressing.
SECTION 4 " Configuration The filter configuration must be changed to allow forwarding of other desired protocols, including TCP or UDP. See Appendix E for discussion of OWL/IP restrictions and permanent filters. Filters must be configured in all super root candidates and OWL/IP designated bridges. Default filter settings for OWL/IP are shown below.
SECTION 4 " Configuration Security Options Use [Security] to set these passwords: Password Service Password Advanced Password “************” “************” Password This option is the top-level password you need to access the configuration menus. The prompt is: Range is: 16 chars Enter 16 or fewer alphanumeric characters for this password. It is case insensitive and can be any combination of letters, numbers, and symbols. For security, the password appears as asterisks on the screen.
SECTION 4 " Configuration Advanced Password When you set an advanced password, it is required to configure the following: Security/Advanced Password and Bridge/Ports/omdip The prompt is: Range is: 16 chars Enter 16 or fewer alphanumeric characters for this password. It is case insensitive and can be any combination of letters, numbers, and symbols. For security, the password appears as asterisks on the screen.
SECTION 4 " Configuration Different LAN IDs Using separate LAN IDs for each radio option configures all access points with different radios into a distinct network regardless of radio type. It may be more appropriate if the installation topology or applications supported do not fit the alternative that uses the same LAN ID. OWLView shows two distinct LANs for this type of installation. Creating a Web Browser Session " NOTE: The access point’s configuration menus are designed for HTML Level 2.
SECTION 4 Ethernet LAN " Configuration HTTP 1 2 1. Platform with Web browser 2. 6710 Access Point Figure 4-6 Web Browser Session 1. Ensure the access point is connected to the Ethernet cable and has an assigned IP address. 2. Ensure the Web browser is installed on the platform. 3. Start the browser application. 4. Enter the access point’s IP address in the browser’s Uniform Resource Locator (URL) field. For example: http://999.999.99.
SECTION 4 " Configuration 5. Enter the user name and password. Refer to the following chart for help with all fields. Setting Description Resource A number assigned to this session. The number changes every time you access the Enter Network Password screen. User name The Resource number. For example, if the Resource number is 3550, the user name is 3550. Configuration menus’ top-level password. The default password is CR52401 (case insensitive).
SECTION 4 " Configuration Access Point Configuration F Configuration Menus F Review/write Changes F Logout F Reboot Security Once you’ve successfully entered the user name and password into your browser, you are authorized to access the configuration. If five (5) minutes elapses without configuration activity, you will become unauthorized again. Only one computer at a time is allowed to be authorized for access to the configuration menus.
SECTION 4 " Configuration Configuration Guidelines Planning Your Installation To plan your installation, refer to “Finding the Best Location” in Section 3 for installation guidelines. Using the Configuration Guide The configuration guide in Table 4-1 summarizes the necessary steps to set up an open wireless LAN. The left-hand column provides basic setup information for a simple network using 6710 Access Points on a single Ethernet segment.
SECTION 4 " Configuration Table 4-1 (Continued) Configuration Guide z = required step; Z = recommended step Simple Network Advanced Functions 2. Preliminary Configuration Before Installation (Through DIAG Port): Z Set LAN ID to a nonzero value (page 4-23). z Configure access points with IP address configuration (page 4-16) or DHCP server name (page 4-20). z OWL/IP: Configure IP addresses in access points serving as super root candidates or OWL/IP designated bridge candidates.
SECTION 4 " Configuration Table 4-1 (Continued) Configuration Guide z = required step; Z = recommended step Simple Network Advanced Functions 3. Additional Configuration (Through DIAG Port, or Remotely Using Telnet or HTTP): Z z Set LAN ID to a nonzero value (page 4-23). Set Global Flooding parameters in super root candidates (page 4-28). z z z Secondary LANs: Set the Flood Register values (page 4-59) in designated bridge candidates if Global Flooding options are set to Registered (page 4-30).
Section 5 Software Download " " " " " " " " " " " " " " " " " " " " " " " " " " " " This section describes the file system structure, File Menu commands, and ROM command monitor for the access point. File System Structure The access point’s file system has four separate segments (analogous to a directory in most computer file systems): Boot Segments 1 and 2 The first two segments (1 and 2) are .75 Mb boot segments.
SECTION 5 " Software Download When you reboot the access point, the data files load into the radio module. (Note that the WLIF radio does not have a data file.) Active and Inactive Segments The access point can have an active boot and data segment, as well as an inactive boot and data segment: The inactive segment is where you can download a new file. " The active segment contains the files that are loaded at boot time.
SECTION 5 " Software Download RAM Segment The file system supports a fifth segment known as the RAM segment. The RAM segment is similar to the other segments, except the file contents are stored in RAM and the segment’s contents are lost when you reboot the access point. The RAM segment is limited to a maximum of 4096 bytes. It is used to hold small script files during the software download process.
SECTION 5 " Software Download File Names Several file system commands require you to enter file names. You can precede file names by a segment number or name followed by a colon. EXAMPLE 1: AB:USTART29.BIN refers to the file USTART29.BIN in the active boot segment (segment 1 or 2). EXAMPLE 2: 1:USTART29.BIN refers to the file USTART29.BIN in segment 1.
SECTION 5 " Software Download The File Menu appears: Loading configuration from EEPROM Command Fb Fd Fdel Fe Tftp Script SDVars Exit Description fb fd ( | all) - directory list fdel - delete file fe ( | all) - erase segment(s) File transfer Execute script files Software download variables Return to main menu File> Fb Command Use Fb to make inactive segments active.
SECTION 5 " EXAMPLE 2: Software Download This command makes segment 1 the active boot segment and segment 4 the active data segment: File>fb 1 4 You can use an asterisk (*) in place of either or to tell the access point to not change that segment.
SECTION 5 " Software Download Following are field descriptions: “File Directory name” lists the names of all files currently loaded in FLASH. " “seg” is the segment in which the boot file is loaded. (R indicates the RAM segment.) " “type” is the type of file: E for executable (boot file), D for data. " “length” is the file size in bytes. " “date” and “time” are the date and time the file was created. " “ver” is the file version number in the format vxx.xx.
SECTION 5 " Software Download Fe Command Fe erases files in a specified segment of FLASH memory. Once you have erased the files, you can restore them only by reloading them from another source. The command’s format is: File>fe is a segment number, a segment name, or the word “all.” Specifying “all” erases all FLASH file segments but does not erase the RAM segment.
SECTION 5 " Software Download As a server, the access point can service read and write requests from an access point client. To operate as a TFTP server, the access point must be loaded with these software versions: " ROM version 1.13 or greater " FLASH (USTART29.BIN) version 1.23 or greater " As a client, the access point can read files from and write files to any TFTP server on the network. The client always requests octet mode.
SECTION 5 " Software Download Server Start Use Server Start to enable the access point as a TFTP server. The format is: File>tftp server start After you issue this command, the access point responds to TFTP client requests directed to its IP address. When acting as a server, the access point TFTP supports up to four concurrent TFTP sessions. Server Stop Use Server Stop to stop the access point from being a TFTP server when you are done transferring files.
SECTION 5 " Software Download Get Use Get on an access point client to download software from a TFTP server (a PC or another access point). The format is: File>tftp get " " " EXAMPLE 1: is the IP address of the server (or “*” which indicates the value of the ServerIpAddress variable, described later in this section). is the name of the file to get from the server.
SECTION 5 " Software Download Put Use Put on an access point client to copy a file to the server (a PC or another access point). The format is: File>tftp put " " " EXAMPLE: is the IP address of the server, or “*” which stands for the value of the ServerIpAddress variable (described on page 5-18). is the name of the file as it will appear on the server.
SECTION 5 " Software Download The first command establishes a TFTP session with the server, gets the script file from the server, and places the file in the RAM file segment, giving it the name “sysswdl.” The second command runs the script from the RAM segment. The script file should contain the same commands you would use from the command line to erase the appropriate file segments, download the new file(s), and reboot using the new software.
SECTION 5 " Software Download FHDR29K -d -v1.00 SCRIPT.TXT SCRIPT.DAT " " “-d” marks the file as data instead of executable. This prevents the access point from trying to execute the file. “-v1.00” sets the file’s version to 1.00. The file type and version appear in the directory information on the access point. Sample Script File #This sample script file assumes the server IP #address has been set either from the command #line or via SNMP. It also assumes the files #USTART29.BIN and falcon_d.
SECTION 5 " Software Download Script File Command Summary Following is a description of the commands you can include in a download script file. You can issue these commands manually from the access point from the “>” prompt on the command line. Most script file commands are executed from within the file command submenu.
SECTION 5 " Software Download In addition, all commands are case insensitive, so: FILE FE ID: is the same as: file fe id: TFTP Client Command Retry When executing a script file, the access point retries TFTP client commands GET and PUT until the command completes successfully. If the first attempt to transfer the file fails, the access point retries after a one-minute delay. With each successive failure, the retry time doubles until it reaches 8 minutes.
SECTION 5 " Software Download SDVars Command Use the SDVars command to display the following arguments: Argument Get Set ? Description Get Set Display this help File> Use the Set argument with a range of software download variables.
SECTION 5 " Software Download ServerIpAddress ServerIpAddress contains the IP address of the TFTP server to use to retrieve the download script file. This address is also used when you specify an asterisk as the IP address of the tftp get or tftp put command. The format of the ServerIpAddress variable is: File>sdvars set serveripaddress EXAMPLE: This command line sets the IP address of the server to 1.2.3.4: File>sdvars set serveripaddress 1.2.3.
SECTION 5 " Software Download As long as the StartTime has not counted to zero on its own, the timer stops and the software download process halts. When the timer does count down to zero, it uses the ServerIpAddress value and the ScriptFilename value to get the script file. If either of these is not set, an error is noted in the status variable and the software download process is aborted.
SECTION 5 " Software Download file sdvars set file fe ab: file sdvars set file tftp get * file sdvars set reboot checkpoint 1 checkpoint 2 ustart29.bin ab: checkpoint 3 When the software download is started, you can use SNMP to query its progress by reading the checkpoint variable. If the variable has a value of 2, for example, you know that the access point is trying to execute the tftp get statement. If the value is 3, you know the script has completed and the reboot statement was executed.
SECTION 5 " Software Download SetActivePointers Use SetActivePointers to make inactive access point segments active, but only immediately before rebooting. The variable’s format is: File>sdvars set setactivepointers The default value is “none.” Setting the value to “boot” or “data” affects only the given segment. Setting the value to “both” changes both segments.
SECTION 5 " Software Download ROM Command Monitor Certain functions available through the ROM command monitor can erase your configuration information. Intermec STRONGLY RECOMMENDS that you only use this option when absolutely necessary (for example, to upgrade your FLASH software or when instructed to do so, and under the supervision or direction of qualified Intermec personnel). Starting the Command Monitor You can access the ROM command monitor only through the DIAG port.
SECTION 5 " Software Download Viewing ROM Commands To view ROM commands, type any invalid command (such as “?”) to display the command monitor’s Main Menu: B FX s FC s FD - Reboot Ymodem File Download Move file to Flash File System Directory FR PWD NPWD SR z - Run Flash Boot File Password Menu Norand Password Menu Serial Baud Rate ap> The following paragraphs describe each option.
SECTION 5 " Software Download FR " NOTE: The first executable file in the access point boot segment must be the access point boot file. FR finds the first executable file in the access point’s boot segment, and tries to run the file. NPWD NPWD is for internal use by service personnel only. SR z Serial baud rate command SR z sets the baud rate of the access point.
SECTION 5 " Software Download PWD PWD opens a password-protected menu that contains file management commands. Some of the commands delete files. Others redefine the access point’s file structure. In either case the commands can cause undesirable results if not properly executed. If in doubt on the proper procedure to use, contact Technical Support for assistance.
SECTION 5 " Software Download FI FI is a destructive command that erases all downloaded files in FLASH memory. FS s n FS is a destructive command that redefines the default (factory set) file segments in FLASH memory. FB s FB s designates which segment(s) of FLASH memory the boot program is located in. If the access point boot program is located in a segment other than what is designated, the boot program will not run. See “Fb Command” on page 5-5 for more information.
SECTION 5 " " " " " " Software Download Names of all files on the card. Type of file (executable, data, text). Size (in bytes) of each file. Date of each file. Version number of each file, in the format Vxx.xx. FPE FPE erases the entire contents of a PC card installed in PC card slot NIC2 on the access point. Individual files cannot be deleted. When you issue the FPE command, each location on a PC card installed in slot NIC2 is overwritten with 0’s.
SECTION 5 " Software Download When the ROM command monitor is in quiet mode you must send three or more consecutive exclamation points ( ! ) to the DIAG port during the boot sequence to invoke the command monitor prompt (ap>). Because the access point is in quiet mode no prompts appear to show you when to type the exclamation points.
SECTION 5 " Software Download Exiting the ROM Command Monitor Exit the command monitor by running the Reboot command (B) or Run Flash Boot File command (FR) on the ROM command monitor’s Main Menu. Software Download Example The FLASH program for the access point is called USTART29.BIN. A simple method for upgrading an access point with new FLASH is to set one up as a TFTP server and then download new FLASH into another access point (the client).
SECTION 5 " Software Download " " " " You have established a connection between a PC and the access point’s DIAG port, and have accessed the ROM command monitor. An old version of FLASH is in segment 1. The new version of FLASH is going into segment 1. Segment 2 is the active boot segment. 1. When the access point has entered the ROM command monitor, type the following commands to upgrade the unit. Command Description ap>pwd Enter the password menu. Enter the password.
SECTION 5 " Software Download Starting the TFTP Server 1. Configure the access point that you just upgraded to be the TFTP server by typing: File>tftp server start 2. To check the status of the TFTP server, type: File>tftp server log If the server is active its response is: The TFTP server is running. Upgrading TFTP Clients The following procedure assumes that you are downloading USTART29.BIN into an inactive boot segment and the 900 MHz radio’s data file into an inactive data segment. 1.
SECTION 5 " Software Download Command Description File>tftp get 1.2.3.4 falcon_d.29k id: Copy self-extracting data file FALCON_D.29K from the server to the client’s inactive data segment. File>fb ib: id: Make the client’s inactive boot and data segments the active segments. File>fd Display the FLASH file directory to verify that the boot and data segments are the active segments. File>exit Exit the File Menu and return to the Main Menu. >reboot Run the new FLASH file by restarting the access point.
Section 6 Indicator Lights " " " " " " " " " " " " " " " " " " " " " " " " " " " " This section describes the access point’s indicator lights and how to read them. This section also provides troubleshooting information you can use to isolate a faulty access point. Overview The eight indicator lights on the access point’s front panel are the best indicators of how the unit is working.
SECTION 6 " Indicator Lights Each indicator light is labeled according to function. The following chart lists the groups and their indicator lights. Group Indicator Lights ETHERNET LINK and POLARITY STATUS STATUS and MODE NETWORK MODE R-LINK and W-LINK PCMCIA NIC1 and NIC2 ETHERNET Lights ETHERNET indicator lights show the status of the access point’s Ethernet connection. Table 6-1 shows what the lights mean when ON and OFF.
SECTION 6 " Indicator Lights STATUS The STATUS (left) light indicates the access point’s operating status. When the light is OFF, the access point is operating normally. When the light is ON, it is in error mode. " NOTE: In certain cases the following text refers to the indicator lights by number. Lights are numbered from left to right. Light 1 is labeled LINK and Light 8 is labeled NIC2.
SECTION 6 " NOTE: " Indicator Lights Contact the Customer Response Center for help with the following. Error Status Description Hardware errors 1, 2, and 3 These errors indicate an internal hardware error or malfunction. The errors can occur when you apply power to the access point. If it encounters a hardware error, it no longer functions. Internal serial loopback test failed This failure occurs if the access point does not successfully complete the power-on self-test.
SECTION 6 " Indicator Lights Table 6-3 MODE Indicator Light Status Indication ON Unit is not functional and is locked up. BLINK Unit is in network mode, the normal operating condition. Unit is in command mode. It enters this mode when it detects a key press from an attached PC before it enters the boot mode, or when it detects an incoming signal from an attached modem. OFF NETWORK MODE Lights NETWORK MODE indicator lights show the status of the access point’s network link.
SECTION 6 " Indicator Lights PCMCIA Lights PCMCIA indicator lights show the status of the two PC card slots, which are labeled NIC1 and NIC2. The left light shows the status of NIC1; the right light shows the status of NIC2. Table 6-5 shows light indications for both ports. Table 6-5 PCMCIA Indicator Lights Status Indication OFF A functional or enabled radio is not installed in the slot. A functional and enabled radio is installed in the slot.
SECTION 6 " Indicator Lights Power-Up Sequence When you power on the access point, it performs a power-up sequence that does the following: Tests the indicator lights. " Tests the functional circuits. " Determines the operational status. " Determines the boot sequence. You can monitor the power-up sequence through the indicator lights. During power-up the lights operate in this order: " 1. LINK indicator light turns ON and stays ON. 2.
SECTION 6 6-8 " Indicator Lights 6710 Access Point User’s Guide
Appendix A Access Point Specifications " " " " " " " " " " " " " " " " " " " " " " " " " " " " Product Specifications Processor: AMD 29200 RISC Memory: 4 MB RAM/2 MB FLASH ROM Distribution LAN compatibility: ANSI/IEEE 802.3 (Ethernet communication standard) and DIX Version 2.
APPENDIX A " Access Point Specifications The access point complies with the following standards.
Appendix B WLIF Specifications and Antennas " " " " " " " " " " " " " " " " " " " " " " " " " " " " RM180 The model name for the WLIF radio option is RM180, a Type III PC card. Following are networking specifications. Frequency band: Compatibility: Range: Coverage: Data rate: 6710 Access Point: Ethernet compatibility: 2.401 to 2.
APPENDIX B " WLIF Specifications and Antennas Optional interbuilding Yes wireless bridge: Operating temperature: --4 dF to 122 dF (--20 dC to 50 dC) Regulatory compliance: FCC 15.247 Industry Canada RSS 210 European Union ETS 300-328 CE EMC-EEC in Europe MKK standard in Japan Consult a Sales Representative for availability. Radio Operation Wireless devices with the WLIF radio can operate in most areas that allow use of spread spectrum wireless communications at 2.
APPENDIX B " WLIF Specifications and Antennas Antenna Regulations For WLIF systems, regulations require the antenna and antenna connector on the access point to be unique and not commercially available. This ensures that the RF output of the radio stays within the limits specified by the regulating agencies. Whip Antenna The standard WLIF whip antenna can be used throughout Europe. Its part number is 805-486-001.
APPENDIX B " WLIF Specifications and Antennas Cable Length Kit Part Number 10 feet 203-423-001 20 feet 203-423-002 30 feet 203-423-003 Medium Gain Collinear Dipole The medium gain collinear dipole is a linear polarized antenna that works best in semi-open areas such as loading dock bays, open high ceiling office environments and in areas where penetration through several racks or a single office wall is required. The following chart lists kit part numbers.
APPENDIX B " WLIF Specifications and Antennas High Gain Yagi The high gain yagi is a linear polarized antenna typically used in heavy racking where there are long corridors that cannot be penetrated through the side using collinears. The following chart lists kit part numbers.
APPENDIX B " WLIF Specifications and Antennas Model 2100 Antennas and Cables 2.4 GHz Antennas Part Number 805-486-001 066147 063363 065349 067261 067262 067263 Antenna, 2.4 GHz Whip (page B-3) Omni 3 dBi omni 9 dBi omni 3 dBi mini omni 5 dBi dual flat 9 dBi flat panel 2.4 GHz Antenna Cables and Connectors Part Number 226-295-001 064616 063245 063246 063198 061868 586610 589377 064432 061475 063146 B-6 6710 Access Point User’s Guide Description 6710 adapter cable (to cable) (page B-5) Cable, 2.
Appendix C 900 MHz Specifications and Antennas " " " " " " " " " " " " " " " " " " " " " " " " " " " " RM160 The model name for the 900 MHz radio is RM160, a Type III PC card. Following are networking specifications.
APPENDIX C " 900 MHz Specifications and Antennas Radio Operation Wireless devices with the 900 MHz option can operate in Australia and in most countries in North and South America. Contact a Sales Representative for current information about countries in which the product is approved for use and countries in which submission for type approval is planned. Part Numbers The following chart lists RM160 part numbers and special comments.
APPENDIX C " 900 MHz Specifications and Antennas Remote Antenna Kits Remote antenna kits allow a variety of antenna configurations (for a radio installed in the access point) to be located up to 30 feet from the access point. Contact your Sales Representative for information about the antenna kit most suitable for your installation. " NOTE: FCC and DOC regulations require that qualified personnel install remote antennas. Contact your Sales Representative for more information.
APPENDIX C C-4 " 900 MHz Specifications and Antennas 6710 Access Point User’s Guide
Appendix D S-UHF Specifications and Antennas " " " " " " " " " " " " " " " " " " " " " " " " " " " " RM111 The model name for the S-UHF radio option is RM111, a Type II PC card. Following are networking specifications. Frequency band: 430 to 450 MHz or 450 to 470 MHz Range: Up to 3500 feet line of sight Coverage: Data rate 800,000 square feet (72,000 square meters) in typical indoor installations 19.2 Kbps (14.
APPENDIX D " S-UHF Specifications and Antennas Regulatory compliance: FCC Part 90 (pending) ETS 300-220 CE 300-339 (Europe) MPT 1329 FTZ 2014 Consult a local sales office for the current regulatory status. Radio Operation Wireless devices with the S-UHF option can operate in selected countries in Europe, Asia (except Japan), Australia, and most countries in North and South America.
APPENDIX D " S-UHF Specifications and Antennas Wireless Hops Because of the low data rate, wireless hops are not supported for S-UHF systems. Antenna Connector The S-UHF antenna uses a standard BNC connector. Whip Antennas For S-UHF, the standard whip antenna is the primary antenna. Its part number is 805-511-001. A cabled external antenna is required in cases where the access point and antenna cannot be installed at the same location.
APPENDIX D " S-UHF Specifications and Antennas Site License Operation of S-UHF requires a site license in the United States and some other countries. Consult Sales Administration (in the United States) or the appropriate National Regulatory Agency (outside the United States) for information about the appropriate application process.
APPENDIX D " S-UHF Specifications and Antennas # Frequencies # Wireless Stations 1 32 2 60 3 80 4 100 Installation Guidelines The following pages contain guidelines for predicting the coverage area and installing single and multiple access points. Predicting Coverage Table D-1 shows predicted indoor coverage areas for an access point with the S-UHF radio. The table was generated using a mathematical mode. Areas are in square meters. For square feet, multiply the area in square meters by 10.
APPENDIX D " S-UHF Specifications and Antennas Installing a Single Access Point You can install a single access point when wireless station populations, system transaction rates, and coverage requirements permit. Following are some factors to consider: For large coverage areas, it is necessary to locate the access point optimally to maximize coverage.
APPENDIX D " S-UHF Specifications and Antennas Figure D-1 Extending Coverage In this type of installation, the access point coverage areas are overlapped minimally to provide seamless coverage. The access points may all use a common frequency, requiring adherence to the system terminal population and transaction rate limits for one frequency. You can also install access points on different frequencies. In this case, you may be able to increase the wireless station population and transaction rate.
APPENDIX D " NOTE: " S-UHF Specifications and Antennas A site survey is required for this type of installation. - 105 dBm Access Point A Access Point B Figure D-2 Frequency Reuse In this type of installation, you can install access points on the same frequency. Each access point can sustain the single frequency wireless station population and transaction rate.
APPENDIX D " S-UHF Specifications and Antennas Two configuration options are possible: Option 1: Option 2: Configure wireless stations for frequency agile operation. Configure wireless stations for single frequency operation, splitting the wireless station population equally among the available frequencies. Both options require that you configure the access points on unique frequencies.
APPENDIX D " S-UHF Specifications and Antennas 32 or fewer wireless stations in this area 60 wireless stations maximum in overlap area (two frequencies) 100 wireless stations maximum in overlap area (four frequencies) Figure D-3 Increased System Throughput Frequency and Separation Guidelines When using overlapping access points, you must provide minimum physical separation between access point antennas.
Appendix E OWL/IP " " " " " " " " " " " " " " " " " " " " " " " " " " " " Introduction Wireless networks may be installed in environments that are segmented by IP routers. If OWL/IP is not enabled, the presence of a router generally defines the physical boundary of the wireless network. Wireless coverage can be provided by installing multiple independent wireless networks, each with its own LAN ID, super root and set of wireless stations.
APPENDIX E " OWL/IP OWL/IP is activated by enabling the OWL/IP port in the access point. The port is an entryway to an IP tunnel originated by the super root on the home subnet, and terminated by a designated bridge operating on a remote subnet. Frames are encapsulated using the GRE protocol running over IP. The super root can originate IP tunnels to eight or fewer IP addresses.
APPENDIX E " OWL/IP For network protocols that an IP router is configured to bridge. Many routers may be installed to bridge specific frame types. These routers are often referred to as B-routers. " For network protocols a router is capable of routing. For example, IPX frames should not be tunneled through a router capable of routing both IP and IPX frames.
APPENDIX E " OWL/IP Addressing Limitations and Flooding Restrictions Wireless stations using IP must be assigned addresses on the home subnet. The ARP server capability can be enabled to reduce propagation of ARPs through tunnels. IP servers can be located on any subnet; however, it is desirable to choose the subnet containing servers used extensively by client wireless stations as the home subnet if possible.
APPENDIX E " OWL/IP DGP (86) (Dissimilar Gateway Protocol) EGP (8) (Exterior Gateway Protocol) IDPR (35) (Inter-Domain Policy Routing Protocol) IDRP (45) (Inter-Domain Routing Protocol) IGP (9) (Interior Gateway Protocol) IGRP (88) (Interior Gateway Routing Protocol) MHRP (48) (Mobile Host Routing Protocol) OSPFIGP (89) (Open Shortest Path First Interior Gateway Protocol) " IP ICMP types, including: IPv6 Mobile IP Router Advertisement Router Selection " IP/UDP frames with these destination protocol po
APPENDIX E " OWL/IP Default Filter Settings The default settings for [TX Filter] are set to pass the following frame types (and drop all others): " " " DIX 0875B NNL DIX 0806 ARP IP Protocol ICMP (1) supporting the following frame types: Address Mask Reply (18) Address Mask Request (17) Alternate Host Address (6) Destination Unreachable (3) Echo Reply (0) Echo Request (8) Parameter Problem (12) Redirect (5) Source Quench (4) Time Exceeded (11) Time Stamp (13) Time Stamp Reply (14) Trace Route (30) Subn
APPENDIX E " OWL/IP Password Security The access point has two levels of password security. Knowledge of the standard password allows general access to the configuration menus. If desired, the OWL/IP configuration can be access protected by enabling the Advanced Password in the [Security] menu. Operation OWL/IP uses IP encapsulation to establish a virtual LAN segment through an IP router. The OWL/IP tunnel becomes a branch in the spanning tree.
APPENDIX E " AP 4 AP 5 OWL/IP AP 3 (Designated Bridge) Wireless Link AP 1 Secondary LAN AP 2 (Super Root) Distribution LAN Wireless Station Wireless Station Wireless Station Figure E-1 Secondary LAN AP 5 AP 4 AP 1 (Super Root) AP 3 (Designated Bridge) AP 2 IP Network Secondary LAN Remote Subnet IP Router Wireless Station Distribution LAN Home Subnet Wireless Station Wireless Station Figure E-2 OWL/IP Tunnel E-8 IP Router 6710 Access Point User’s Guide
APPENDIX E " OWL/IP Following are three primary differences between secondary LANs separated by wireless links and secondary LANs separated by OWL/IP tunnels: " " " Any access point on the distribution LAN can provide wireless connectivity for a designated bridge on a secondary Ethernet LAN. Only the super root can originate OWL/IP connections to designated bridges on remote subnets.
APPENDIX E " OWL/IP If a super root candidate receives a hello from an access point with a higher root priority (or equal root priority from a higher MAC address), it stops sending hellos. This root election protocol continues until only one super root access point sends hellos. After the super root is established, other access points attach to the super root forming the spanning tree.
APPENDIX E " OWL/IP Frame Forwarding MAC frames originating on the home subnet are encapsulated in the super root, forwarded through the IP network, deencapsulated in the designated bridge, and forwarded to the appropriate access point for delivery to the intended wireless station. The same process is used in reverse between the designated bridge and the super root for inbound frames. The encapsulation uses the standard IP GRE protocol.
APPENDIX E " OWL/IP Additionally, IP frames are only forwarded inbound if the IP address belongs to the home subnet (see “Subnet Filtering,” page E-6). Station Mobility As stations move through a facility, they roam between access point coverage areas. In large installations, these access points may be on different IP subnets. OWL/IP is designed to support rapid roaming in these environments.
APPENDIX E " OWL/IP Table E-1 Mobile IP Comparison Comparison Mobile IP OWL/IP Software compatibility: Requires a Mobile IP client software stack in IP wireless stations. Allows use of existing IP software stacks in wireless stations. Addressing limitations for IP stations: None. Requires that IP station addresses belong to the home subnet. Routing of non-IP protocols: Is not allowed. Scalability: Special network software: Is configurable through [TX Filter].
APPENDIX E " OWL/IP AP 1 (Super Root) 192.168.15.101 AP 3 192.168.17.188 192.168.17.1 192.168.15.1 IP Router AP 4 (Designated Bridge) 192.168.17.16 Server for IP Stations 192.168.15.17 Home Subnet AP 2 192.168.15.36 Server for NNL Stations 192.168.23.1 IP Router IP Station 192.168.15.227 NNL Station Subnet Mask: 255.255.255.0 IP Station 192.168.15.228 Figure E-3 Example Class C Configuration E-14 6710 Access Point User’s Guide AP 5 (Designated Bridge) 192.168.23.
APPENDIX E " OWL/IP Step 1 " " " " " " Access points are assigned IP addresses for the appropriate subnets. Subnet 192.168.15.0 is designated as the home subnet, since it contains the servers used by wireless stations. Wireless stations that require IP connectivity are given IP addresses on this subnet. Access point (AP) 1 is selected as the primary super root and assigned root priority 3. AP 2 is selected as the fallback super root and assigned root priority 1.
APPENDIX E " OWL/IP Option A: Unicast Addressing In this example, unicast IP addresses are entered in the table for each designated bridge. The two designated bridges on subnet 192.168.17.0 negotiate which access point serves as the designated bridge for that subnet. AP 4 has the highest bridge priority, so AP 3 becomes the designated bridge only if AP 4 fails or loses its network connection. AP 5 is the only access point on subnet 192.168.23.0, so no fallback is available.
APPENDIX E 1 2 3 4 5 6 7 8 Type " OWL/IP Address 192.168.17.255 192.168.23.255 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 Step 4: Set TX Filters Support for both NNL and IP stations is required. This example assumes DIX Ethernet is supported, but 802.3 and SNAP are not required. NNL is enabled by the default settings.
APPENDIX E " OWL/IP Alternatively, if a limited set of known applications is to be supported, filters may be set to selectively pass listed Port numbers. Following is the [Frame Types] screen: DIX-IP-TCP Ports DIX-IP-UDP Ports Action Scope For example, to support FTP (data and control) and Telnet, enable protocol ports 20, 21, and 23, respectively. The above IP port numbers are specified as decimal values.
APPENDIX E " OWL/IP Example 2: Class B IP Address Using Subnetting The example in Figure E-4 uses the Class B address of 172.16.0.0 and a subnet mask of 255.255.248.0. This provides 30 subnets of 2046 hosts each. Subnet addressing for this network is described under “IP Subnet Mask” in Section 4, “Configuration.” In this example, each subnet has about 10 access points. The home subnet contains the address range of 172.16.16.1 through 172.16.23.254.
APPENDIX E " OWL/IP AP 2 172.16.19.36 AP 1 (Super Root) 172.16.16.101 Server for NNL Stations Server for IP Stations 172.16.23.141 172.16.8.1 IP Router 172.16.16.1 Home Subnet AP 11 172.16.32.2 AP 12 172.16.32.3 AP 13 172.16.32.4 AP 22 172.16.40.3 AP 23 172.16.40.4 AP 32 172.16.48.3 AP 33 172.16.48.4 172.16.8.2 IP Router 172.16.32.1 AP 21 172.16.40.2 172.16.8.3 IP Router 172.16.40.1 AP 31 172.16.48.2 172.16.8.4 IP Router 172.16.48.
APPENDIX E " OWL/IP Step 3 The two super root candidates are configured to originate tunnels. Option A: Unicast Addressing In this example, unicast IP addresses are entered in the table for each designated bridge. The two designated bridges on each subnet will negotiate which access point serves as the designated bridge for that subnet. Use of two designated bridge candidates on each subnet restricts the number of subnets that can be supported to four.
APPENDIX E " OWL/IP 1 2 3 4 5 6 7 8 Type Address 172.16.23.255 172.16.31.255 172.16.39.255 172.16.47.255 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 Option C: All Subnets Broadcast In this example, an All Subnets broadcast address is used. This broadcast is forwarded throughout the network and received by designated bridges on all subnets. See Comments on the next page before using the All Subnets broadcast.
APPENDIX E " OWL/IP Comments: " " " " The All Subnets broadcast generates traffic to all subnets, including those that do not contain access points. Some IP routers do not support All Subnets, or may require specific configuration. There are practical limits on the number of tunnels a super root can establish and support. These limits depend on factors unique to each installation, such as network traffic. The eight tunnel addresses specified in the menu are a conservative limit for large networks.
APPENDIX E E-24 " OWL/IP 6710 Access Point User’s Guide
Appendix F Port and Cable Pin-Outs " " " " " " " " " " " " " " " " " " " " " " " " " " " " This appendix lists pin-outs for the 6710 Access Point’s DIAG and AUI ports, and the standard null modem cable. DIAG Port Pin-Outs The following chart defines the signals present on the pins for the DIAG port. Pin numbering is from left to right and top to bottom. For example, pin 1 is on the top left of the connector, and the last pin is on the bottom right.
APPENDIX F " Port and Cable Pin-Outs AUI Port Pin-Outs The following chart defines the signals present on the pins for the AUI port. Pin numbering is from left to right and top to bottom. For example, pin 1 is on the top left of the connector, and the last pin is on the bottom right.
APPENDIX F Port and Cable Pin-Outs " DIAG Port Cable DIAG Port to 9-pin Male PC Port (Standard Null Modem Cable) Part Number: 226-106-001 (6 feet) Pin 6 Pin 1 6710 PC 2 3 3 2 Pin 1 Pin 6 1 Pin 9 Pin 5 6710 9-pin, D-sub Female 4 6 5 5 6 4 8 8 Pin 5 Pin 9 PC 9-pin, D-sub Female F SHELL GND 6710 Access Point User’s Guide F-3
APPENDIX F F-4 " Port and Cable Pin-Outs 6710 Access Point User’s Guide
Appendix G MIB " " " " " " " " " " " " " " " " " " " " " " " " " " " " Product Contents The 6710 Access Point MIB is on disk part number 215-894-001. Order the MIB through your Sales Representative.
APPENDIX G " MIB These MIBs are on the 6710 Access Point’s MIB disk. You need to load the MIBs onto your management platform to query the access point for these management objects. Getting Started Install the MIBs onto your management platform in this order: 1. RFC1213.MIB 2. RFC1398.MIB 3. 6710MIB.MIB " NOTE: If you are using HP OpenView for Windows, use the OpenView Control/SNMP Manager/Manage Database menu items to add the previous listed MIBs to the HP OpenView MIB database.
APPENDIX G " MIB Table G-1 MIB-II Information MIB Family OID Purpose System 1.3.6.1.2.1.1 Model and device type Interfaces 1.3.6.1.2.1.2 I/O ports AT 1.3.6.1.2.1.3 Table of IP to MAC/DLC address IP 1.3.6.1.2.1.4 IP process ICMP 1.3.6.1.2.1.5 ICMP process TCP 1.3.6.1.2.1.6 TCP process UDP 1.3.6.1.2.1.7 UDP process EGP * 1.3.6.1.2.1.8 EGP process CMOT * 1.3.6.1.2.1.9 Historical inclusion for OSI support Groups Transmission 1.3.6.1.2.1.
APPENDIX G EXAMPLE: " MIB Device system information is found under nSystem, similar to MIB-II System. The OID for the nSystem group ends in “1,” just as the OID for MIB-II system ends in “1.” Table G-2 shows access point MIB information. Table G-2 MIB Information MIB Family OID Purpose Groups nSystem 1.3.6.1.4.1.469.1000.2.1 Model, device type, software, file system hw, file, fsinfo, segment, dir, sysErrors, criticalErrors nInterfaces 1.3.6.1.4.1.469.1000.2.
APPENDIX G " NOTE: " MIB Community strings are case-sensitive. Community String Access Type public READ-ONLY CR52401 READ-WRITE secret SUPER-USER Description of Access Type May read MIB objects, but not write or change values. EXCLUSIONS: Will not be able to read or write the Community Table. May read MIB objects. May write to MIB objects that have read-write access. EXCLUSIONS: Will not be able to read or write the Community Table. May read MIB objects.
APPENDIX G " MIB MIB-II Notes System Group Three fields in the MIB-II system group are writable. Those fields are: sysContact, sysName, and sysLocation. It is important that these values be preserved in case the 6710 Access Point is powered (off and on) or rebooted. The following lists the number of characters for each field that will be preserved in the event of a power (off and on) or reboot. sysContact: sysName: sysLocation: 31 characters 31 characters 39 characters Interfaces Group The ifTable.
APPENDIX G " MIB Table G-3 MIB Directory Group Group MIB Summary Definition Meaning Product OIDs products INTERMECR Products System Information G-8 G-24 hw Hardware Information G-9 G-24 fsinfo File System Information G-10 G-25 segment File Segment Information G-10 G-26 dir Software Directory Listing G-11 G-28 criticalErrors Critical Errors Information G-11 G-30 Interface Information nifx Norand Extensions to Interfaces Table G-12 G-32 portState Port State Information G-13
APPENDIX G " MIB MIB Outline Product OIDs This group contains an Object IDentification (OID) for each INTERMEC device. Table G-4 products GROUP Device Products norand.manage.products.x (1.3.6.1.4.1.469.1000.1.
APPENDIX G " MIB System Information The following groups contain system level objects describing hardware and file system configuration properties. The groups also contain information about critical errors. " NOTE: The MIB definition for each group starts on the page given below.
APPENDIX G " MIB Table G-6 fsinfo GROUP OID Device File System Information norand.manage.norandNet.nSystem.file.fsinfo.x (1.3.6.1.4.1.469.1000.2.1.3.1.x) Object Name Object Type Access 1 fsEnabled INTEGER read 2 fsMaxSectors INTEGER read 3 fsSectorSize INTEGER read 4 fsNumSegments INTEGER read 5 fsNumFiles Gauge read 6 fsBootSegment INTEGER read 7 fsDataSegment INTEGER read Table G-7 segment GROUP Device File Segment Information norand.manage.norandNet.nSystem.file.segment.
APPENDIX G " MIB Table G-8 dir GROUP Device Software Directory Listing norand.manage.norandNet.nSystem.file.dir.x (1.3.6.1.4.1.469.1000.2.1.3.3.x) OID Object Name Object Type Access 2.1.1 dirIndex INTEGER read 2.1.2 dirName DisplayString read 2.1.3 dirSegment INTEGER read 2.1.4 dirType INTEGER read 2.1.5 dirSize INTEGER read 2.1.6 dirDate DisplayString read 2.1.7 dirTime DisplayString read 2.1.
APPENDIX G " MIB Interface Information The following groups relate information about Norand interfaces, port state, port statistics, port transmit queue, and pending message services. " NOTE: The MIB definition for each group starts on the page given below.
APPENDIX G " MIB Table G-11 portState GROUP Device Port State Information norand.manage.norandNet.nInterfaces.portState.x (1.3.6.1.4.1.469.1000.2.2.3.x) OID Object Name Object Type Access 4.1.1 psPort INTEGER read 4.1.2 psIfIndex INTEGER read 4.1.3 psAddress PhysAddress read 4.1.4 psType INTEGER read 4.1.5 psState INTEGER read 4.1.6 psCost INTEGER read 4.1.7 psHelloPeriod INTEGER read 4.1.8 psHelloCount Counter read 4.1.9 psMacdWindow INTEGER read 4.1.
APPENDIX G " MIB Table G-12 portStats GROUP Device Port Statistics norand.manage.norandNet.nInterfaces.portStats.x (1.3.6.1.4.1.469.1000.2.2.4.x) Object Type Access OID Object Name G-14 4.1.1 pstcPort INTEGER read 4.1.2 pstcInOWLPkts Counter read 4.1.3 pstcInUcastOWLDataPkts Counter read 4.1.4 pstcInNUcastOWLDataPkts Counter read 4.1.5 pstcInOWLErrors Counter read 4.1.6 pstcOutOWLPkts Counter read 4.1.7 pstcOutUcastOWLDataPkts Counter read 4.1.
APPENDIX G " MIB Table G-13 ptxq GROUP Device Port Transmit Queue norand.manage.norandNet.nInterfaces.ptxq.x (1.3.6.1.4.1.469.1000.2.2.5.x) OID Object Name Object Type Access 1.1.1 ptxqPort INTEGER read 1.1.2 ptxqRegQSize Gauge read 1.1.3 ptxqRegQMax INTEGER read 1.1.4 ptxqExpQSize Gauge read 1.1.5 ptxqExpQMax INTEGER read 1.1.6 ptxqQHpCount Counter read 1.1.7 ptxqQExpCount Counter read 1.1.8 ptxqQRegCount Counter read 1.1.9 ptxqQHpDiscards Counter read 1.1.
APPENDIX G " MIB Table G-14 pmsg GROUP G-16 OID Device Pending Message Service norand.manage.norandNet.nInterfaces.pmsg.x (1.3.6.1.4.1.469.1000.2.2.6.x) Object Name Object Type Access 1.1.1 pmsgPort INTEGER read 1.1.2 pmsgPendRecCurrent Gauge read 1.1.3 pmsgPendRecMax INTEGER read 1.1.4 pmsgPendMsgCurrent Gauge read 1.1.5 pmsgPendMsgMax INTEGER read 1.1.6 pmsgPendMsgTotal Counter read 1.1.7 pmsgPendMsgDiscards Counter read 1.1.
APPENDIX G " MIB SNMP Version 1 Configuration Group This group contains objects that configure the version 1 Simple Network Management Protocol (SNMP) agent. " NOTE: The MIB definition for each group starts on the page given below. " " community trapTarget Community Table (page G-52) Trap Target Table (page G-55) Table G-15 community TABLE OID Device SNMP v1 Configurations norand.manage.norandNet.nSNMP.v1Config.x (1.3.6.1.4.1.469.1000.2.11.1.x) Object Name Object Type Access 2.1.
APPENDIX G " MIB Bridging Parameters The following groups contain objects relating to the wireless transparent bridging operation. " NOTE: The MIB definition for each group starts on the page given below. " " " " " rt brg addr brgState bridgeStats Route Table (page G-56) Bridge Table (page G-61) Address Table (page G-63) Bridge State Information (page G-64) Bridge Statistics (page G-69) Table G-17 rt GROUP Device Route Table norand.manage.norandNet.nBridge.rt.x (1.3.6.1.4.1.469.1000.2.17.2.
APPENDIX G " MIB Table G-17 (Continued) rt GROUP OID Device Route Table norand.manage.norandNet.nBridge.rt.x (1.3.6.1.4.1.469.1000.2.17.2.x) Object Name Object Type Access 2.1.10 rtHopEaddr PhysAddress read 2.1.11 rtIsBound INTEGER read 2.1.12 rtIsRemote INTEGER read 2.1.13 rtIsChild INTEGER read 2.1.14 rtIsAp INTEGER read 2.1.15 rtIsDistributed INTEGER read 2.1.16 rtIsRemoteLan INTEGER read 2.1.17 rtNS INTEGER read 2.1.
APPENDIX G " MIB Table G-19 addr GROUP OID Address Table norand.manage.norandNet.nBridge.addr.x (1.3.6.1.4.1.469.1000.2.17.4.x) Object Name Object Type Access 2.1.1 addrDestination PhysAddress read 2.1.2 addrAge INTEGER read 2.1.3 addrNodeId INTEGER read 2.1.4 addrAlias DisplayString read 2.1.5 addrDeviceId INTEGER read 2.1.6 addrIpAddress IPAddress read Table G-20 brgState GROUP Bridge State Information norand.manage.norandNet.nBridge.brgState.x (1.3.6.1.4.1.469.1000.2.17.6.
APPENDIX G " MIB Table G-20 (Continued) brgState GROUP OID Bridge State Information norand.manage.norandNet.nBridge.brgState.x (1.3.6.1.4.1.469.1000.2.17.6.
APPENDIX G " MIB Table G-21 bridgeStats GROUP OID Bridge Statistics norand.manage.norandNet.nBridge.bridgeStats.x (1.3.6.1.4.1.469.1000.2.17.7.
APPENDIX G " MIB Table G-22 powerUp GROUP Device Power Up Objects norand.manage.norandNet.nControl.powerUp.x (1.3.6.1.4.1.469.1000.2.105.1.x) OID Object Name Object Type Access 1 pwrPowerUpCount Counter read 2 pwrNextPowerUpTime TimeTicks write Table G-23 softwareDownLoad GROUP Device Software Download norand.manage.norandNet.nControl.softwareDownLoad.x (1.3.6.1.4.1.469.1000.2.105.2.
APPENDIX G ------ " MIB ****************************************************************** * * 6710MIB.MIB Version 1.
APPENDIX G MIB " hwRevision OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION ”The revision level of the hardware device.” ::= { hw 3 } hwSerialNo OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION ”The serial number of the hardware device.” ::= { hw 4 } hwID OBJECT-TYPE SYNTAX INTEGER (0..2147483647) ACCESS read-only STATUS mandatory DESCRIPTION ”The device identifier of the hardware device.
APPENDIX G " MIB fsSectorSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The size of a physical sector in bytes.
APPENDIX G " MIB segTable OBJECT-TYPE SYNTAX SEQUENCE OF SEGEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”” ::= { segment 2 } -- Row Definition segEntry OBJECT-TYPE SYNTAX SEGEntry ACCESS not-accessible STATUS mandatory INDEX { segID } ::= { segTable 1 } -- Columnar Object Definitions SEGEntry ::= SEQUENCE { segID segFirstSector segLastSector segStatus segSize segFree } INTEGER, INTEGER, INTEGER, INTEGER, INTEGER, INTEGER segID OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DE
APPENDIX G " MIB segLastSector OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The last physical sector in the segment (FIRST_SECTOR - (MAX_SECTORS + 1))” ::= { segEntry 3 } segStatus OBJECT-TYPE SYNTAX INTEGER { valid(1), invalid(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”The segment status: valid = 1, invalid = 2 ” ::= { segEntry 4 } segSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The segment size in bytes” ::= { segEntry 5 } segFree
APPENDIX G " MIB dirEntry OBJECT-TYPE SYNTAX DIREntry ACCESS not-accessible STATUS mandatory INDEX { dirIndex } ::= { dirTable 1 } -- Columnar Object Definitions DIREntry ::= SEQUENCE { dirIndex dirName dirSegment dirType dirSize dirDate dirTime dirVersion } INTEGER, DisplayString, INTEGER, INTEGER, INTEGER, DisplayString, DisplayString, DisplayString dirIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Directory Index” ::= { dirEntry 1 } dirName OBJECT-TYPE SYNTAX Display
APPENDIX G " MIB dirType OBJECT-TYPE SYNTAX INTEGER { executable(1), data(2), invalid(3) } ACCESS read-only STATUS mandatory DESCRIPTION ”File type: executable = 1, data = 2, invalid = 3 ” ::= { dirEntry 4 } dirSize OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The file size in bytes” ::= { dirEntry 5 } dirDate OBJECT-TYPE SYNTAX DisplayString (SIZE (0..12)) ACCESS read-only STATUS mandatory DESCRIPTION ”The file date in MM-DD-YYYY display format.
APPENDIX G MIB " ceEnabled OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”A value of true(1) signifies that the critical error log was successfully initialized as part of the power-up sequence. Any errors in that initialization process result in a value of false(2).” ::= { criticalErrors 1 } ceOverflow OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Overflow error code.
APPENDIX G " MIB CELogEntry ::= SEQUENCE { ceLogErrorCode INTEGER, ceLogErrorCount Counter } ceLogErrorCode OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Critical error code. A 16-bit value which uniquely indentifies a system software error. The error codes are intended for internal Norand use.
" MIB 6710 Access Point User’s Guide G-33 APPENDIX G NIFXEntry ::= SEQUENCE { nifxIndex nifxType nifxInDisabledDiscards nifxInOverruns nifxInHWOverruns nifxInUcastDPkts nifxInNUcastDPkts nifxInLenErrors nifxExcessiveDeferrals nifxInNetIDDiscards nifxInFragDiscards nifxInUFilterDiscards nifxInNUFilterDiscards nifxInQFullDiscards } nifxIndex SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Interface index” ::={ nifxEntry 1 } nifxType SYNTAX INTEGER { INTEGER, INTEGER, Counter, Counter, Coun
APPENDIX G " MIB nifxInDisabledDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of received unicast frames which do not require forwarding.
APPENDIX G " MIB nifxInLenErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number received frames with length errors” ::={ nifxEntry 8 } nifxExcessiveDeferrals OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of aborted transmissions due to excessive deferrals” ::={ nifxEntry 9 } nifxInNetIDDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of received frames discarded because the LAN ID did
APPENDIX G " MIB nifxInNUFilterDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of enabled received multicast frames discarded due to a multicast filter expression” ::={ nifxEntry 13 } nifxInQFullDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of received frames discarded because the frame could not be queued for the MAC-R task” ::={ nifxEntry 14 } portState OBJECT IDENTIFIER ::= { nInterfaces 3 } -- The Port Sta
APPENDIX G PSEntry ::= SEQUENCE { psPort psIfIndex psAddress psType psState psCost psHelloPeriod psHelloCount psMacdWindow psMacdQSize psMacdTimeouts psIsPrimary psIsSecondary psIsSecondaryCandidate psSecondaryUniFlooding psSecondaryMultiFlooding psIsRadio psPendEnabled } psPort SYNTAX INTEGER (1..4) ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-R port ID (1-4). identifies the port.
APPENDIX G " MIB psType SYNTAX INTEGER { OBJECT-TYPE ether(4), bb485(33), owlIP(66), proxim24(132), nor24(195), falcon902(197), uhf(198) } ACCESS read-only STATUS mandatory DESCRIPTION ”Norand port type: ether = 4, Proxim = 196, Falcon = 197, UHF = 198” ::= { psEntry 4 } psState OBJECT-TYPE SYNTAX INTEGER { disabled(0), idle(1), open(2), receive(3), transmit(4) } ACCESS read-only STATUS mandatory DESCRIPTION ”Port state: disabled = 0, idle = 1, open = 2, receive = 3, transmit = 4 ” ::= { psEntry 5 } ps
APPENDIX G " MIB psHelloPeriod OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Inter-HELLO time (.01 secs.)” ::= { psEntry 7 } psHelloCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”HELLO transmit count” ::= { psEntry 8 } psMacdWindow OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Max.
APPENDIX G " MIB psIsSecondary OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”TRUE, for secondary bridge ports” ::= { psEntry 13 } psIsSecondaryCandidate OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”TRUE, if secondary bridge port candidates” ::= { psEntry 14 } psSecondaryUniFlooding OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”TRUE, for secondary bridge po
APPENDIX G portStats " MIB OBJECT IDENTIFIER ::= { nInterfaces 4 } pstcTable OBJECT-TYPE SYNTAX SEQUENCE OF PSTCEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”MAC-R port state variables” ::= { portStats 4 } pstcEntry SYNTAX PSTCEntry ACCESS not-accessible STATUS mandatory INDEX { pstcPort } ::= { pstcTable 1 } OBJECT-TYPE PSTCEntry ::= SEQUENCE { pstcPort pstcInOWLPkts pstcInUcastOWLDataPkts pstcInNUcastOWLDataPkts pstcInOWLErrors pstcOutOWLPkts pstcOutUcastOWLDataPkts pstcOutNUcastOWLData
APPENDIX G " MIB pstcPort SYNTAX INTEGER (1..4) ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-R port ID (1-4). identifies the port.
" MIB 6710 Access Point User’s Guide G-43 APPENDIX G pstcOutUcastOWLDataPkts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Total unicast OWL data packets sent” ::= { pstcEntry 7 } pstcOutNUcastOWLDataPkts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Total multicast OWL data packets sent” ::= { pstcEntry 8 } pstcOutOWLErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”OWL packet send errors” ::= { pstcEntry 9 } pstcPa
APPENDIX G " MIB pstcInNUcastRelayPkts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Received multicast relay packets” ::= { pstcEntry 13 } pstcOutUcastRelayPkts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Total unicast relay packets sent” ::= { pstcEntry 14 } pstcOutNUcastRelayPkts OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Total multicast relay packets sent” ::= { pstcEntry 15 } pstcInUcastInbound OBJECT-TYPE SYNTA
APPENDIX G " MIB pstcInUcastFlood OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Received unicast data packets with an unknown destination” ::= { pstcEntry 19 } pstcInUcastDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Received unicast data packets discarded” ::= { pstcEntry 20 } pstcInNUcastDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Received multicast data packets discarded” ::= { pstcEntry 21 } pstcIn
APPENDIX G " MIB ptxq OBJECT IDENTIFIER ::= { nInterfaces 5 } ptxqTable OBJECT-TYPE SYNTAX SEQUENCE OF PTXQEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”The Port Transmit Queue Table” ::= { ptxq 1 } ptxqEntry OBJECT-TYPE SYNTAX PTXQEntry ACCESS not-accessible STATUS mandatory INDEX { ptxqPort } ::= { ptxqTable 1 } PTXQEntry ::= SEQUENCE { ptxqPort ptxqRegQSize ptxqRegQMax ptxqExpQSize ptxqExpQMax ptxqQHpCount ptxqQRegCount ptxqQExpCount ptxqQHpDiscards ptxqQRegDiscards ptxqQExpDiscards ptxq
APPENDIX G " MIB ptxqRegQSize OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION ”Current regular queue size (0-REG_Q_MAX). The number of regular priority packets which are currently queued for transmission on the port.” ::= { ptxqEntry 2 } ptxqRegQMax OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The maximum number of regular priority packets which can be queued for transmission on the port.
APPENDIX G " MIB ptxqQExpCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of attempts to queue an expedited priority packet for transmission” ::= { ptxqEntry 7 } ptxqQRegCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of attempts to queue a regular priority packet for transmission” ::= { ptxqEntry 8 } ptxqQHpDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of failed attemts to
APPENDIX G " MIB ptxqMultiQSize OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION ”Current multicast queue size. The number of multicast packets which are queued for transmission on the (radio) port. Multicast packets are transmitted after HELLO packets on OWL radio ports.” ::= { ptxqEntry 12 } ptxqMultiQMax OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The maximum number of multicast packets which will be queued for transmission on the (radio) port.
APPENDIX G " MIB PmsgEntry ::= SEQUENCE { pmsgPort pmsgPendRecCurrent pmsgPendRecMax pmsgPendMsgCurrent pmsgPendMsgMax pmsgPendMsgTotal pmsgPendMsgDiscards pmsgPendRecOverflowErrors pmsgPendMsgOverflowErrors pmsgPendAgedRecCount pmsgPendAgedMsgCount } INTEGER, Gauge, INTEGER, Gauge, INTEGER, Counter, Counter, Counter, Counter, Counter, Counter pmsgPort OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-R port ID (1-4). A number which uniquely indentifies the port.
APPENDIX G " MIB pmsgPendMsgMax OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Maximum pending message count” ::= { pmsgEntry 5 } pmsgPendMsgTotal OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Total pending message count” ::= { pmsgEntry 6 } pmsgPendMsgDiscards OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of pending messages in-queue which were discarded before they could be delivered because the terminal’s que
APPENDIX G " MIB pmsgPendAgedRecCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of terminal records discarded due to maximum age (12 minutes)” ::= { pmsgEntry 10 } pmsgPendAgedMsgCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”The number of pending messages which were discarded due to maximum age.
APPENDIX G " MIB communityTable OBJECT-TYPE SYNTAX SEQUENCE OF CommunityEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”The community table is used to define communities and their access privileges.
APPENDIX G " MIB CommunityEntry ::= SEQUENCE { communityIndex communityStatus communityName communityPrivileges } INTEGER, INTEGER, DisplayString, INTEGER -- Leaf Definition communityIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Identifies the community row” ::= { communityEntry 1 } communityStatus SYNTAX INTEGER { OBJECT-TYPE enabled(1), disabled(2), deleted(3) } ACCESS read-write STATUS mandatory DESCRIPTION ”Status of a community record.
APPENDIX G " MIB communityPrivileges SYNTAX INTEGER { OBJECT-TYPE get-only(1), set-and-get(3) } ACCESS read-write STATUS mandatory DESCRIPTION ”SET and GET privileges of community.” ::= { communityEntry 4 } -- Norand trap table defines all trap target IP addresses -- Table Definition trapTargetTable OBJECT-TYPE SYNTAX SEQUENCE OF TrapTargetEntry ACCESS not-accessible STATUS mandatory DESCRIPTION ”The trap target table specifies the IP address of SNMPv1 managers that expect trap notifications.
APPENDIX G " MIB trapTargetIndex OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Identifies the trapTarget row” ::= { trapTargetEntry 1 } trapTargetStatus OBJECT-TYPE SYNTAX INTEGER { enabled(1), disabled(2), deleted(3) } ACCESS read-write STATUS mandatory DESCRIPTION ”Status of a trapTarget record.” ::= { trapTargetEntry 2 } trapTargetName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..16)) ACCESS read-write STATUS mandatory DESCRIPTION ”The authoritative name for the trapTarget.
APPENDIX G " MIB -- Row Definition rtEntry OBJECT-TYPE SYNTAX RTEntry ACCESS not-accessible STATUS mandatory INDEX { rtDestination } ::= { rtTable 1 } -- Columnar Object Definition RTEntry ::= SEQUENCE { rtDestination rtPort rtAge rtNodeId rtAttachId rtAttachTime rtApEaddr rtHopAddrLen rtHopAddr16 rtHopEaddr rtIsBound rtIsRemote rtIsChild rtIsAp rtIsDistributed rtIsRemoteLan rtNS rtNR } PhysAddress, INTEGER, INTEGER, INTEGER, INTEGER, TimeTicks, PhysAddress, INTEGER, INTEGER, PhysAddress, INTEGER, INTEG
APPENDIX G " MIB rtAge OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The time (in minutes) since the route was updated.” ::= { rtEntry 3 } rtNodeId OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION ”16-bit node ID of the destination. A 16-bit identifier which uniquely identifies an OWL node in an OWL LAN.” ::= { rtEntry 4 } rtAttachId OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION ”Attach sequence number.
APPENDIX G " MIB rtHopAddrLen OBJECT-TYPE SYNTAX INTEGER { twoByte(2), sixByte(6) } ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-D address length (2 or 6). A MAC-D entity may use either 16-bit locally assigned addresses or 48-bit 802 addresses.” ::= { rtEntry 8 } rtHopAddr16 OBJECT-TYPE SYNTAX INTEGER (0..
APPENDIX G " MIB rtIsChild OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”True if the destination is a child node” ::= { rtEntry 13 } rtIsAp OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”True if the destination is an AP” ::= { rtEntry 14 } rtIsDistributed OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”True if the path is through a distributed AP (root node on
APPENDIX G " MIB rtNR OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-R receive sequence number for terminal nodes.
APPENDIX G " MIB brgDestination OBJECT-TYPE SYNTAX PhysAddress ACCESS read-only STATUS mandatory DESCRIPTION ”The 802 address of the destination.” ::= { brgEntry 1 } brgPort OBJECT-TYPE SYNTAX INTEGER (1..4) ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-R port ID (1-4). A number which uniquely identifies the port.” ::= { brgEntry 2 } brgAge OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Time (in minutes) since the entry was updated.
APPENDIX G " MIB brgTimestamp OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION ”The time when the primary or inbound entry was added or the time when the secondary entry was added or re-attached.
APPENDIX G " MIB addrDestination OBJECT-TYPE SYNTAX PhysAddress ACCESS read-only STATUS mandatory DESCRIPTION ”The 802 address of the registered port.” ::= { addrEntry 1 } addrAge OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”The time (in minutes) since the entry was updated.” ::= { addrEntry 2 } addrNodeId OBJECT-TYPE SYNTAX INTEGER (0..
APPENDIX G " MIB bsAddress OBJECT-TYPE SYNTAX PhysAddress ACCESS read-only STATUS mandatory DESCRIPTION ”802 address of the AP” ::= { brgState 3 } bsLanId OBJECT-TYPE SYNTAX INTEGER (0..
APPENDIX G " MIB bsMyRootPriority OBJECT-TYPE SYNTAX INTEGER (0..7) ACCESS read-only STATUS mandatory DESCRIPTION ”Root priority of the AP (0-7). An AP with a root priority of 0 can not become the root node. The AP with the highest priority will become the root in an OWL LAN” ::= { brgState 9 } bsRootPort OBJECT-TYPE SYNTAX INTEGER (1..4) ACCESS read-only STATUS mandatory DESCRIPTION ”MAC-R root port number. The port number (1-4) of the port used to communicate with the parent node.
APPENDIX G " MIB bsParentAddress OBJECT-TYPE SYNTAX PhysAddress ACCESS read-only STATUS mandatory DESCRIPTION ”802 address of the parent AP” ::= { brgState 14 } bsPortCount OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Number of MAC-R ports” ::= { brgState 15 } bsNodeId OBJECT-TYPE SYNTAX INTEGER (0..65535) ACCESS read-only STATUS mandatory DESCRIPTION ”16-bit node ID (0-65535). The node ID uniquely identifies the node in an OWL LAN.
APPENDIX G " MIB bsDetachReason OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION ”Last detach reason code. The code indicates the reason that the AP became unattached for the last occurrence.
APPENDIX G MIB " bsIsPrimaryBridge OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”TRUE, if the AP bridges to the distribution LAN” ::= { brgState 24 } bsIsSecondaryBridge OBJECT-TYPE SYNTAX INTEGER { true(1), false(2) } ACCESS read-only STATUS mandatory DESCRIPTION ”TRUE, if the AP is the designated bridge for a secondary LAN” ::= { brgState 25 } bsUniFilterExpr OBJECT-TYPE SYNTAX INTEGER (0..
APPENDIX G " MIB bstcChildCount OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION ”Number of attached children” ::= { bridgeStats 4 } bstcChildApCount OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION ”Number of attached AP children” ::= { bridgeStats 5 } bstcRemoteCount OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION ”Non-OWL bridge table entries” ::= { bridgeStats 6 } bstcPrimaryCount OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS manda
" MIB 6710 Access Point User’s Guide G-71 APPENDIX G bstcRemoteLanCount OBJECT-TYPE SYNTAX Gauge ACCESS read-only STATUS mandatory DESCRIPTION ”Route entries for remote LANs” ::= { bridgeStats 10 } bstcRouteGetErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Route table overflow errors” ::= { bridgeStats 11 } bstcEntryGetErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Bridge table overflow errors” ::= { bridgeStats 12 } bstcRmtLanGetError
APPENDIX G " MIB bstcEntrySeqErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Out-of-sequence bridge entry update errors” ::= { bridgeStats 16 } bstcInvalidUpdateErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION ”Invalid route update errors” ::= { bridgeStats 17 } nControl OBJECT IDENTIFIER ::= { norandNET 105 } powerUp OBJECT IDENTIFIER ::= { nControl 1 } pwrPowerUpCount OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIP
" MIB 6710 Access Point User’s Guide G-73 APPENDIX G sdServerIpAddress OBJECT-TYPE SYNTAX IpAddress ACCESS read-write STATUS mandatory DESCRIPTION ”TFTP server IP address” ::= { softwareDownLoad 2 } sdScriptFilename OBJECT-TYPE SYNTAX DisplayString (SIZE (0..
APPENDIX G " MIB sdCheckPoint OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION ”An application variable intended to contain a number relating the progress of the current software download” ::= { softwareDownLoad 6 } sdSetActivePointers OBJECT-TYPE SYNTAX INTEGER { none(1), boot(2), data(3), both(4) } ACCESS read-write STATUS mandatory DESCRIPTION ”If the device reboots due to the expiration of the pwrNextPwrUpTime timer, this value specifies which active pointers will be toggled
Glossary " " " " " " " " " " " " " " " " " " " " " " " " " " " " Access Point Access points provide the following functions: " " " " A wired bridge is an access point that attaches to the network through an Ethernet link and has bridging enabled (through access point configuration menus). A wired bridge converts wireless LAN frames to Ethernet frames, and Ethernet frames to wireless LAN frames. A wired bridge also forwards wireless LAN frames to wireless LAN nodes.
GLOSSARY " Bridging In this manual, bridging refers to the translational bridging process of converting open wireless LAN frames to Ethernet frames, and Ethernet frames to open wireless LAN frames. Broadcast A broadcast is a transmission to all wireless stations at the same time. Channel Channel refers to a logical data channel. A port may contain one or more channels. Data for any given wireless station is contiguous on a channel.
GLOSSARY " Implementation of the DHCP client simplifies installation because the devices automatically receive IP addresses from a DHCP server on the network. (The DHCP client also accepts addresses from a Bootp server.) Direct Sequence Direct sequence is a spread spectrum technique by which the transmitted signal is spread over a wide frequency range. In a direct sequence system, the bandwidth is large relative to the data rate.
GLOSSARY " Frame A frame is a series of bytes of data encapsulated with a header (and trailer). Frame is often used interchangeably with packet, although technically a packet refers to data from the network layer of the protocol stack. Frequency Agile The frequency agile system software allows access points to be individually configured to operate on one of several preprogrammed frequencies.
GLOSSARY " IP Subnet An IP subnet is a single member of the collection of hardware networks that compose an IP network. Host addresses on a given subnet share an IP network number with hosts on all other subnets of that IP network, but the local address part is divided into subnet-number and hostnumber fields to indicate which subnet a host is on. IP Wireless Station An IP wireless station is any PC-compatible computing station running IP.
GLOSSARY " Multicast Address A multicast address is a form of broadcast address through which copies of the frame are delivered to a subset of all possible destinations with a common multicast address. NNL Wireless Station An NNL wireless station is a terminal emulation station. These stations use an optimized transport protocol for reliable operation in wireless environments. Octet An octet is a byte composed of eight bits.
GLOSSARY " Outbound Frames Frames moving away from the distribution LAN are outbound. Primary LAN See Distribution LAN. Radio Network The radio network consists of radio-enabled network devices and communication paths. It is a group of fixed-end devices and wireless stations in which each can communicate with at least one other device through either a radio or wired Ethernet link. Secondary Ethernet LANs are part of the radio network; the distribution LAN is not part of the radio network.
GLOSSARY " ROM (Read-Only Memory) ROM contains computer instructions that cannot be reprogrammed by the user. The computer can read instructions out of ROM, but no data can be stored in ROM. The user can change some of the variables within ROM, such as the software, boot segment, data segment, and baud rate. Root Subnet The root subnet is the Ethernet segment to which the access point super root connects, which is the distribution LAN.
GLOSSARY " Single Frequency If a wireless station is using a single frequency, it operates on the selected frequency in a list of frequencies. The default is the first frequency in the list. Subnet A subnet is a single member of the collection of hardware networks that compose an IP network. Host addresses on a given subnet share an IP network number with hosts on all other subnets of that IP network.
GLOSSARY " The wireless access point provides a wireless store-and-forward operation (a hop) with each frame transmitted twice over the wireless media to reach its destination. Because frames are transmitted twice, the amount of wireless traffic over the radio network doubles. In general, the throughput of a wireless access point has about half the effective bandwidth of a wired bridge, because all frames received on the radio channel must be forwarded on the same channel.
INDEX " " " " " " " " SYMBOLS ? command, 4-14 NUMBERS 10BASE-T (UTP) Ethernet connecting to, 3-16 menu option, 4-42 network component, 3-3 port description, 2-18 10BASE2 (thin) Ethernet connecting to, 3-11, 3-12 menu option, 4-42 network components, 3-3 port description, 2-18 10BASE5 (thick) Ethernet connecting to, 3-13 menu option, 4-42 network components, 3-4 port description, 2-18 2.4 GHz radio. See WLIF radio 6710MIB.MIB, G-1, G-2 802.1d, E-4 802.2, 4-44, 4-50, 4-51 802.
INDEX " Applying power, 3-20 ARP Bootp server, 4-21 broadcasting a request, 4-21 converting multicast requests to unicast, 4-36 DHCP server, 4-21 flooding, 4-36 menu option, 4-36 minutes between requests, 4-22 overview, 2-7 server mode, 4-23, 4-36 TCP/IP nodes, 4-32 AT MIB family, G-3 Attach mechanisms, 2-6 Attach priority, 4-76, 4-78 AUI See also 10BASE5 (thick) Ethernet drop cable, 3-4 menu option, 4-42 port, 2-18, 3-13, F-2 AUTO, 4-72 Auto ARP minutes, 4-16, 4-22 Auto detect, 4-42 Awake time, 4-25, 4-2
INDEX Commands (Continued) FPC f s, 5-25, 5-26 FPD, 5-25, 5-26 FPE, 5-25, 5-27 FPX, 5-25, 5-27 FR, 5-23, 5-24 FS s n, 5-25, 5-26 FX s, 5-23 MI String, 5-25, 5-28 Move File to FLASH, 5-23 Norand Password Menu, 5-23 NPWD, 5-23, 5-24 Password Menu, 5-23 PCMCIA File Directory, 5-25, 5-26 PCMCIA File to FLASH, 5-25, 5-26 PN, 5-25, 5-27 Power-Up Normal, 5-25, 5-27 Power-Up Quiet, 5-25, 5-27 PQ, 5-25, 5-27 PWD, 5-23, 5-25 Read, 4-13, 4-14 Reboot, 4-14, 5-16, 5-23 Reset Modem Init String, 5-25, 5-28 RMI, 5-25, 5-2
INDEX " DHCP client, 2-12, 4-19 definition, Glossary-2 menu option, 4-16, 4-19 OWL/IP tunneling, 4-20 RFCs, 4-22 server name, 4-16, 4-20 DIAG port cables, F-3 connecting to PC, 4-2, 4-3 description, 2-18 Dimensions, A-2 Direct sequence, 4-75, C-1, Glossary-3 Disabling ARP server mode, 4-36, 4-37 designated bridge, 4-58 DHCP, 4-19, 4-20 Ethernet port, 4-40 flood register, 4-59 flooding, 4-29, 4-30 global parameters, 4-27 Master mode, 4-77, 4-78 radio port, 4-40 Discarding frames, 4-45, 4-62, 4-63, 4-84 Dis
INDEX Exiting configuration menus, 4-14 ROM password submenu, 5-28 [Expressions], 4-52 ExprSeq, 4-53 Exterior Gateway Protocol, E-5 F Fairness slot, 4-69, 4-70 [Falcon], 4-38, 4-39, 4-74 Falcon Frag Size, 4-25, 4-26, 4-27 Falcon radio. See 900 MHz radio Falcon_d.29k, 4-74, 5-1, 5-6, 5-14 FB s command, 5-25, 5-26 FC s command, 5-23 FCC, 4-77 FD command, 5-23, 5-25 Fd command, 5-6 FE command, 5-25 Fe command, 5-8 FFR f command, 5-25, 5-26 FHDR29K.EXE, 5-13 FI command, 5-25, 5-26 Figures.
INDEX " Frames (Continued) IPX, E-3 no flooding, 4-29 OWL/IP forwarded, E-5 forwarding, E-11 inbound, E-11 not forwarded, E-4 operation, E-7 permanent filters, E-4 restrictions, E-4 safeguards, E-3 subnet filtering, E-6 Guidelines (Continued) S-UHF frequency and separation, D-10 installation, D-5 transaction rates, D-4 Frequencies 900 MHz radio, C-1 beacon, 4-70 reusing, D-7 S-UHF radio, 4-77, D-1, D-4 separation guidelines, D-10 single, D-7, D-8, Glossary-9 source power, A-1 WLIF radio, B-1 Height, A-
INDEX Inbound and flood register, 4-36 ARP requests, 4-37 definition, Glossary-4 description, 4-28 flooding frames, 4-29 flooding level checklist, 4-31 menu option, 4-28, 4-30 OWL/IP flooding, E-4, E-6 OWL/IP frames, E-11 required flooding levels, 4-31 S-UHF radio flooding level, 4-36 Indicator lights, 2-17, 6-1 Industrial Locking Mounting Bracket, 2-19 Infinite leases, 4-21 Installation applying power, 3-20 checking default configuration, 3-1 collecting the equipment, 3-2 connecting to Ethernet, 3-10 find
INDEX " [Master Parms], 4-60, 4-62 Media Access Control sublayer.
INDEX Omduhfb, 4-38, 4-39 Omni antennas, B-6 Online help, 4-1 Op, 4-53, 4-54 Open Shortest Path First Interior Gateway Protocol, E-5 Open system, Glossary-6 Operating temperature 900 MHz radio, C-1 S-UHF radio, D-1 WLIF radio, B-2 Organizationally Unique Identifier, 4-47 Originate if Root, 4-82 OSPFIGP, E-5 OUI, 4-47 Outbound, 4-28, E-11, Glossary-7 Outbound to secondaries and flood register, 4-36, 4-59 menu option, 4-28, 4-29 required flooding levels, 4-31 S-UHF radio, 4-36 Outbound to stations menu optio
INDEX " Programmable filters, 4-52 Protocols See also specific protocols network, 2-3, 4-28, 4-44, 4-79 Proxim 2.4 GHz radio.
INDEX Routers (Continued) OWL/IP configuring routing, 4-83 frames forwarded, E-5 frames not forwarded, E-4 in sample network, E-13, E-19 installation limitations, E-2 overview, E-1 redundancy, E-10 roaming across boundaries, E-1, E-3 Telnet session, 4-6 updating routing tables, 4-22 Web browser session, 4-88 Routing Information Protocol, E-5 Rubber feet, 2-18 Run File command, 5-25, 5-26 Run Flash Boot File command, 5-23, 5-24 S S-UHF radio antenna connector, D-3 attach mechanisms, 2-6 channelization, D-1
INDEX " SNAP--IP--Other Protocols Ethernet filter, 4-44, 4-45 example, 4-50, 4-51 OWL/IP filter, 4-85 SNAP--IP--Protocol, 4-47 SNAP--IP--TCP Ports Ethernet filter, 4-44, 4-45 example, 4-50, 4-51 OWL/IP filter, 4-85 SNAP--IP--TCP--Port, 4-47 SNAP--IP--UDP Ports Ethernet filter, 4-44, 4-45 example, 4-50, 4-51 OWL/IP filter, 4-85 SNAP--IP--UDP--Port, 4-47 SNAP--IPX Sockets Ethernet filter, 4-44, 4-45 example, 4-50, 4-51 OWL/IP filter, 4-85 SNAP--IPX--Socket, 4-47 SNAP--Other EtherTypes Ethernet filter, 4-44,
INDEX Throughput S-UHF radio, D-6, D-8, D-10 WLIF radio, 4-68, 4-69 Time Exceeded, E-6 Time Stamp, E-6 Time Stamp Reply, E-6 Token Ring, 2-3 Top-level password, 4-12, 4-86 Trace Route, E-6 Transaction rates, D-4, D-6, D-8 Translating bridges, 2-2, 2-4 Transmission MIB family, G-3 Transmit mode, 4-69, 4-72, 4-73 Transmit power, D-1 Troubleshooting, 6-1 Tunnels See also OWL/IP establishing, E-10 example, E-15, E-21 flooding parameters, E-9 flooding restrictions, E-4 frame forwarding, E-11 installation limita
INDEX " Wireless stations (Continued) pending messages, 2-5 power management, 2-5 security ID, 4-60 subnet filtering, E-6 [WLIF], 4-38, 4-39, 4-60 WLIF radio antenna cables and connectors, B-6 antenna regulations, B-3 countries, B-2 data rates, B-1 dual radio options, 2-9, 4-65 flooding, 4-30 frequencies, B-1 installing, 3-17 menu options, 4-60 output power, B-1 part numbers, B-2 range, B-1 regulatory compliances, B-2 remote antenna kits, B-3 specifications, B-1 whip antenna, B-3 Write command, 4-14 Writi
