Wireless IP/Ethernet Transceiver Covering all AP and Remote Units including Mercury 900, 3650, and Option Set 1 Remotes 05-4446A01, Rev.
TABLE OF CONTENTS 1 PRODUCT OVERVIEW AND APPLICATIONS ......... 1 1.1 ABOUT THIS MANUAL................................................................................................... 3 1.1.1 Start-Up Guide .................................................................................................................... 3 1.1.2 Online Access to Manuals ................................................................................................... 3 1.1.3 Conventions Used in This Manual ............
2.4 STEP 3—CONNECT PC TO THE TRANSCEIVER...................................................... 25 2.5 STEP 4—REVIEW TRANSCEIVER CONFIGURATION 2.5.1 Getting Started 2.5.2 Procedure 2.5.3 Basic Configuration Defaults 2.6 STEP 5—CONNECT LAN OR SERIAL DATA EQUIPMENT 2.6.1 Option 1 Set (MaxRM) Connectors 2.7 STEP 6—CHECK FOR NORMAL OPERATION 25 25 25 25 26 28 29 3 EMBEDDED MANAGEMENT SYSTEM .................. 31 3.1 MS INTRODUCTION ...........................................................................
3.7.2 Wireless Security Menu ..................................................................................................... 94 3.7.3 IEEE 802.1x Device Authentication ................................................................................... 96 3.7.4 Manage Certificates .......................................................................................................... 98 3.8 REDUNDANCY CONFIGURATION (AP ONLY) ......................................................... 101 3.
5.1.8 ERP Compliance at 900 MHz .......................................................................................... 170 5.1.9 ERP Compliance at 3650 MHz ........................................................................................ 171 5.2 dBm-WATTS-VOLTS CONVERSION CHART ............................................................ 172 6 TECHNICAL REFERENCE..................................... 173 6.1 DATA INTERFACE CONNECTORS ..............................................................
The majority of GE MDS radios deployed since 1985 are still installed and performing within our customers' wireless networks. That’s because we design and manufacture our products in-house, according to ISO 9001 which allows us to control and meet stringent global quality standards.
CSA/us Notice (Remote Transceiver Only) This product is approved for use in Class 1, Division 2, Groups A, B, C & D Hazardous Locations. Such locations are defined in Article 500 of the National Fire Protection Association (NFPA) publication NFPA 70, otherwise known as the National Electrical Code. The transceiver has been recognized for use in these hazardous locations by the Canadian Standards Association (CSA) which also issues the US mark of approval (CSA/US).
To reduce potential radio interference to other users, the antenna type and its gain should be chosen so that the Equivalent Isotropic Radiated Power (EIRP) is not more than that permitted for successful communication. This device has been designed to operate with the antennas listed on Page 170 and 171. Antennas not included in this list are strictly prohibited for use with this device. The required antenna impedance is 50 ohms.
viii Mercury Reference Manual 05-4446A01, Rev.
1 PRODUCT OVERVIEW AND APPLICATIONS 1 Chapter Counter Reset Paragraph Contents 1.1 ABOUT THIS MANUAL ......................................................... 3 1.1.1 Start-Up Guide ....................................................................... 3 1.1.2 Online Access to Manuals ...................................................... 3 1.1.3 Conventions Used in This Manual ......................................... 3 1.2 PRODUCT DESCRIPTION ................................................... 4 1.
2 Mercury Reference Manual 05-4446A01, Rev.
1.1 ABOUT THIS MANUAL This Reference Manual is one of two publications provided for users of the Mercury SeriesTM transceiver system. It contains detailed product information, an overview of common applications, a screen-by-screen review of the menu system, technical specifications, suggested settings for various scenarios, and troubleshooting information. This manual should be available to all personnel responsible for network design, setup, commissioning and troubleshooting of the radios. 1.1.
Menu Strings To help show the path to a menu selection, navigation strings are used in several places in this manual. For example, suppose you want to view or set the Network Name assigned to your system. This item is located in the Network Configuration Menu, so the navigation string in the text would appear as shown: Main Menu>>Network Configuration>>Network Name By following this order of menus, you can quickly reach the desired menu. 1.
This one enclosure contains all necessary components for radio operation and data communications. Simple Installation Mercury Transceivers are designed for rapid and trouble-free installation. For basic services, you simply connect the antennas (900 or 3650 MHz as required, and GPS), connect your data equipment, apply primary power, and set some operating parameters. No license is required for 900 MHz operation in the USA, Canada, and many other countries.
serial/EIA-232-based hardware to the faster and more easily interfaced Ethernet protocol. Flexible Management You can locally or remotely configure, commission, troubleshoot, and maintain the transceiver. Four different modes of access are available: local RS-232 console terminal, local or remote IP access (via Telnet or SSH), web browser (HTTP, HTTPS), and SNMP (v1/v2/v3) All IP access interfaces are available through the unit’s wired Ethernet port and over the air.
Available Frequency Bands At the time of publication, Mercury transceivers are offered in two different frequency bands: 902-928 MHz (Mercury 900) and 3.65–3.70 GHz (Mercury 3650). The 900 MHz unit operates in a license-free spectrum (frequency hopping spread spectrum—FHSS), which may be used by anyone in the USA, provided FCC Part 15 rules are observed. Canada, and certain other countries allow license-free operation in this band—check your country’s requirements. The 3.65–3.
The internal WiFi module has FCC modular approval and may only be operated by connecting one of the GE MDS approved antennas (see 802.11 WiFi Module Specifications below) to the reverse-SMA connector on the radio’s front panel. The WiFi module can operate as an 802.11 Access Point or Infrastructure Station, according to user configuration. The operational mode (AP, Infrastructure RM) and frequency can be configured through the unit's user interface. Invisible place holder Figure 1-2.
protected chassis. For system-level information on this product, refer to MDS publication 05-4161A01. Invisible place holder Figure 1-3. MDS P23 Protected Network Station (incorporates two transceivers, with automatic switchover) 1.2.4 External GPS PPS Option The External GPS Precise Positioning Service (PPS) option allows for an external GPS device to provide the PPS input to the Mercury. This is useful in installations where multiple radios require GPS timing.
Invisible place holder Mercury remote Mercury AP Video Surveillance RTU/PLC (Ethernet) MDS NETview MS® Computer Mercury remote WAN Long Range WLAN Router RS-232 RTU/PLC (Serial) RS-232 RTU/PLC (Serial) MDS 4710 RS-232 MDS 4790 Master Radio Server (Ethernet) Control Center MDS 4710 Licensed Serial/IP Integration Mercury remote Mercury remote Mobile Data Mobile Data Figure 1-4. Integrated Mobile/Fixed Application 1.3.
1.3.3 Point-to-Point LAN Extension A point-to-point configuration (Figure 1-6) is a simple arrangement consisting of an Access Point and a Remote unit. This provides a communications link for transferring data between two locations. Invisible place holder Remote Access Point LAN/WAN LAN Figure 1-6. Typical Point-to-Point Link 1.3.4 Serial Radio Network Connectivity The transceiver provides a path for serial devices to migrate to IP/Ethernet systems.
to different SCADA hosts). A Mercury radio provides this capability using a single remote unit. The unit’s serial port can be connected via IP to different SCADA hosts, transporting different (or the same) protocols. Both data streams are completely independent, and the transceiver provides seamless simultaneous operation as shown in Figure 1-8.
rower channel to concentrate the radio energy, reaching farther distances. It is designed for industrial operation from the ground up. IP-based devices that may be used with the transceiver include new, powerful Remote Terminal Units (RTUs) and Programmable Logic Controllers (PLCs). These, as well as other devices, may be used in applications ranging from SCADA/telemetry monitoring, web-based video, security monitoring, and Voice over IP. Figure 1-9 shows a typical wireless IP network.
NOTE: Several previous GE MDS-brand products had non-standard signal lines on their interface connectors (for example, to control sleep functions and alarm lines). These special functions are not provided nor supported by the Mercury transceiver. Consult equipment manuals for complete pinout information. 1.4 NETWORK DESIGN CONSIDERATIONS 1.4.
ration is sometimes required in a network that includes a distant Remote that would otherwise be unable to communicate directly with the Access Point station due to distance or terrain. The geographic location of a repeater station is especially important. Choose a site that allows good communication with both the Access Point and the outlying Remote site. This is often on top of a hill, building, or other elevated terrain from which both sites can be “seen” by the repeater station antennas.
Invisible place holder Remote Remote LAN Remote Access Point REPEATER LAN LAN/WAN Remote LAN Figure 1-11. Typical Store-and-Forward Repeater Arrangement As with the conventional repeater described in Option 1 above, the location of a store and forward repeater is also important. A site must be chosen that allows good communication with both the Access Point and the outlying Remote site.
The Network Name and the Association Process The Network Name is the foundation for building individual radio networks. Remotes in a network with the same network name as an Access Point (AP) unit are “associated” with that AP. The use of a different Network Name does not guarantee an interference-free system. It does, however, assure that only data destined for a unique network is passed through to that network.
The transceiver is capable of dealing with many common security issues. Table 1-2 profiles security risks and how the transceiver provides a solution for minimizing vulnerability. Table 1-2. Security Risk Management Security Vulnerability GE MDS Cyber Security Solution Unauthorized access to the backbone network through a foreign remote radio • IEEE 802.
1.6 ACCESSORIES The transceiver can be used with one or more of the accessories listed in Table 1-3. Contact the factory for ordering details. Table 1-3. Accessories Accessory Description GE MDS Part No. AC Power Adapter Kit A small power supply module designed for continuous service. UL approved. Input: 120/220; Output: 13.8 Vdc @ 2.5 A 01-3682A02 OmniDirectional Antennas Rugged antennas well suited for use at Access Point installations.
Table 1-3. Accessories (Continued) 20 Accessory Description GE MDS Part No. DIN Rail Mounting Bracket Bracket used to mount the transceiver to standard 35 mm DIN rails commonly found in equipment cabinets and panels. 03-4022A03 COM1 Interface Adapter DB-25(F) to DB-9(M) shielded cable assembly (6 ft./1.8 m) for connection of equipment or other EIA-232 serial devices previously connected to “legacy” units. (Consult factory for other lengths and variations.
2 TABLETOP EVALUATION AND TEST SETUP 2 Chapter Counter Reset Paragraph Contents 2.1 OVERVIEW ........................................................................... 23 2.2 STEP 1—CONNECT THE ANTENNA PORTS...................... 23 2.3 STEP 2—CONNECT THE PRIMARY POWER ..................... 24 2.4 STEP 3—CONNECT PC TO THE TRANSCEIVER............... 25 2.5 STEP 4—REVIEW TRANSCEIVER CONFIGURATION ....... 25 2.5.1 Getting Started .......................................................................
22 Mercury Reference Manual 05-4446A01, Rev.
2.1 OVERVIEW GE MDS recommends that you set up a “tabletop network” to verify the basic operation of the transceivers. This allows experimenting with network designs, configurations, or network equipment in a convenient location. This test can be performed with any number of radios. When you are satisfied that the network is functioning properly in a benchtop setting, perform the field installation.
NOTE: Use attenuation between all units in the test setup. The amount of attenuation required depends on the number of units tested and the desired signal strength (RSSI) at each transceiver during the test. In no case should a signal greater than –50 dBm be applied to any transceiver in the test setup. GE MDS recommends an RF power output level of +20 dBm from the AP. Remote power is not setable. (See “Radio Configuration Menu” on Page 63.) 2.
2.4 STEP 3—CONNECT PC TO THE TRANSCEIVER Connect a PC’s Ethernet port to the LAN port using an Ethernet crossover cable. The LAN LED should light. Alternatively, you can use a serial cable to connect to the COM1 port (Figure 2-3 on Page 27). 2.5 STEP 4—REVIEW TRANSCEIVER CONFIGURATION 2.5.1 Getting Started Start by logging into the Access Point radio. This is done first because the Remotes are dependent on the AP’s beacon signal to achieve an “associated” state.
Table 2-1. Basic Configuration Defaults Item Menu Location Default Values/Range Network Name Main Menu>> Radio Configuration>> Network Name MDS-Mercury • 1–15 alphanumeric characters IP Address Main Menu>> Network Configuration>> IP Address 192.168.1.
Invisible place holder LAN PORT LED INDICATOR PANEL COM1 SERIAL PORT DC POWER INPUT (10—30 VDC, 2.5A) RX2 ANTENNA PORT GPS ANTENNA TX/RX1 CONNECTION ANTENNA PORT Figure 2-3. Transceiver Interface Connectors (Standard unit shown; See Figure 2-4 on Page 28 for MaxRM unit) • LED INDICATOR PANEL—Displays the basic operating status of the transceiver. See section 2.7 on Page 29 for detailed information. • COM1 SERIAL PORT— DB-9 connector used for management of the transceiver with a connected PC.
2.6.1 Option 1 Set (MaxRM) Connectors Figure 2-4 shows the interface connectors on the front panel of the Option 1 Set (MaxRM) Remote transceiver. NOTE: The use of shielded Ethernet cable is recommended for connection to the radio’s ETH port. The radio meets regulatory emission standards without shielded cable, but shielding reduces the possibility of interference in sensitive environments, and is in keeping with good engineering practice. Invisible place holder Figure 2-4.
• GPS ANTENNA PORT— Coaxial connector (SMA-type) for connection of a GPS receiving antenna. Provides 3.5 Vdc output for compatibility with powered (active) GPS antennas. Do not short this connector, as you might cause damage to the internal power supply. The GPS receiving antenna’s gain must be 16 dBi or less.
If the radio network seems to be operating properly based on observation of the unit’s LEDs, use the PING command to verify the link integrity with the Access Point. Table 2-2.
3 DEVICE MANAGEMENT 3 Chapter Counter Reset Paragraph Contents 3.1 MS INTRODUCTION............................................................. 33 3.1.1 Differences in the User Interfaces .......................................... 33 3.2 ACCESSING THE MENU SYSTEM ...................................... 35 3.2.1 Methods of Control ................................................................. 36 3.2.2 PC Connection and Log In Procedures ................................. 36 3.2.3 Navigating the Menus .
3.10 DEVICE INFORMATION MENU.......................................... 108 3.11 PERFORMANCE INFORMATION MENU ........................... 109 3.12 MAINTENANCE/TOOLS MENU.......................................... 122 3.12.1 3.12.2 Installing Firmware via TFTP .............................................. 128 Auto Firmware Upgrade Menu (AP Only) ............................ 137 3.13 PERFORMANCE OPTIMIZATION ...................................... 139 3.13.1 Proper Operation What to Look For .................
3.1 INTRODUCTION The transceiver’s embedded management system is accessible through the COM1 (serial) port, the LAN (Ethernet) port, and using over-the-air Ethernet. Telnet, SSH, HTTP/HTTPS, and SNMP are the Ethernet-based interfaces. Essentially, the same capabilities are available through any of these paths. For support of SNMP software, a set of MIB files is available for download from the GE MDS Web site at www.GEmds.com.
Figure 3-1. Embedded Management System Top-Level Flowchart 34 Mercury Reference Manual 05-4446A01, Rev. D Radio Test Performance Trend Date Format Force Switchover Adv. Config. AP Location Info (RM) NOTES • Chart shows top-level view only. See Reference Manual for details.
Figure 3-2. View of MS with a text-based program (Console Terminal shown Telnet has similar appearance) Invisible place holder Figure 3-3. View of the MS with a Browser (Selections at left provide links to the various menus) 3.2 ACCESSING THE MENU SYSTEM The radio has no external controls or adjustments. All configuration, diagnostics, and control is performed electronically using a connected PC. This section explains how to connect a PC, log into the unit, and gain access to the built-in menus.
3.2.1 Methods of Control Access the unit’s configuration menus in one of several ways: • Local Console—This is the primary method used for the examples in this manual. Connect a PC directly to the COM1 port using a serial communications cable and launch a terminal communications program such as HyperTerminal (found on most PCs by selecting Start>>Programs>>Accessories>>Communications>>HyperTerminal). This method provides text-based access to the unit’s menu screens.
Invisible place holder Transceiver Transceiver To COM1 or LAN Port (See Text) To COM1 or LAN Port (see text) PC Running Terminal Session PC Running Terminal Session (115,200 bps, 8N1) (115,200 bps, 8N1) Figure 3-4. PC Configuration Setup Starting a Local Console Session (Recommended for first-time log-in) 1. Connect a serial communications cable between the PC and the unit’s COM1 port. If necessary, a cable may be constructed for this purpose as shown in Figure 3-5.
5. Enter your password (default password is admin). For security, your password keystrokes do not appear on the screen. Press ENTER . NOTE: Passwords are case sensitive. Do not use punctuation mark characters. You may use up to 13 alpha-numeric characters. The unit responds with the Starting Information Screen (Figure 3-6). From here, you can review basic information about the unit or press G to proceed to the Main Menu. Invisible place holder Figure 3-6.
TIP: You can start a Telnet session on most PCs by selecting: Start>>Programs>>Accessories>>Command Prompt. At the command prompt window, type the word telnet, followed by the unit’s IP address (e.g., telnet 10.1.1.168). Press ENTER to receive the Telnet log in screen. NOTE: Never connect multiple units to a network with the same IP address. Address conflicts will result in improper operation. 3. Enter your username (default username is admin). Press ENTER . Next, the Password: prompt appears.
Invisible place holder Figure 3-7. Log-in Screen when using a Web Browser NOTE: Passwords are case sensitive. Do not use punctuation mark characters. You may use up to 13 alpha-numeric characters. 5. Click OK. The unit responds with a startup menu screen similar to that shown in Figure 3-8. From here, you can review basic information about the unit or click one of the menu items at the left side of the screen. Invisible place holder Figure 3-8. Starting Information Screen Web Browser Example 3.2.
associated screen where settings may be viewed or changed. In most cases, pressing the ESCAPE key moves the screen back one level in the menu tree. In general, the top portion of menu screens show read-only information (with no user selection letter). The bottom portion of the screen contains parameters you can select for further information, alteration of values, or to navigate to other submenus. NOTE: Early versions of PuTTY might not operate when using SSH to connect to the transceiver.
NOTE: In the menu descriptions that follow, parameter options/range, and any default values are displayed at the end of the text between square brackets. Note that the default setting is always shown after a semicolon: [available settings or range; default setting] 3.3 BASIC OVERVIEW OF OPERATION 3.3.1 Starting Information Screen Once you have logged into the Management System, the Starting Information Screen (Figure 3-9) appears with an overview of the transceiver and its current operating conditions.
• Alarmed—The unit has detected one or more alarms that have not been cleared. At Remote: • Scanning—The unit is looking for an Access Point beacon signal. • Ranging—Unit is adjusting power, timing, and frequency with an AP. • Connecting—The unit has found a valid beacon signal for its network. • Authenticating—Device is attempting device authentication. • Associated —The unit has successfully synchronized and associated with an Access Point.
Figure 3-10. Main Menu (AP) (AP menu shown, Remote similar; Differences noted in text below) Figure 3-11. Main Menu (MDS 3650 Remote Only) • Starting Information Screen—Select this item to return to the Start- ing Information screen described above. • Network Configuration—Tools for configuring the data network layer of the transceiver. (See “CONFIGURING NETWORK PARAMETERS” on Page 45) • Radio Configuration—Tools to configure the wireless (radio) layer of the transceiver.
• • • • • • Security Configuration—Tools to configure the security services available with the transceiver’s environment. (See “SECURITY CONFIGURATION MENU” on Page 91) Redundancy Configuration—(AP Only) Allows setting of the criteria for switchover in the event of loss of associated Remotes or excessive packet receive errors. GPS Configuration—(Remote Only; not available on MDS 3650 model) View/set parameters related to GPS streaming location output.
Figure 3-13. Network Configuration Menu (MaxRM radio) • • • • • • • 46 Network Interface Config—Presents a menu where you can view or set various parameters (VLAN Status, IP Configuration, and DHCP Server Configuration). Ethernet Port Config—Presents a menu for defining the status of the Ethernet port (enabled or disabled), port follows association, and Ethernet filtering configuration. Detailed explanations of this menu are contained in Ethernet Port Configuration Menu on Page 55.
ceeds. The transceivers use UTC (Universal Time Coordinated) with a configurable time offset. [0] NOTE: The Mercury gets time of day data from the GPS receiver if the receiver gets a satellite fix. Network Interface Configuration Submenu Invisible place holder Figure 3-14. Network Interface Configuration Submenu • VLAN Status—This selection is used to enable or disable virtual LAN operation. For details, refer to VLAN Configuration Menu on Page 47.
About Virtual LAN in Mercury A VLAN is essentially a limited broadcast domain, meaning that all members of a VLAN receive broadcast frames sent by members of the same VLAN but not frames sent by members of a different VLAN. For more information, refer to the IEEE 802.1Q standard. The transceiver supports port-based VLAN at the Ethernet interface and over the air, according to the IEEE 802.1Q standard.
• • • • • • • • • • 05-4446A01, Rev. D VLAN Status—Defines whether the radio handles Ethernet frames in “extended” 802.1Q mode or in “normal” mode in the Ethernet port. If configured with a trunk port, the Mercury passes all tagged traffic regardless of the VLAN ID. The Mercury only uses the Data VLAN ID parameter when the ETH port is configured as an Access Port. [enabled, disabled; disabled] VLAN Ethport Mode—Defines if the Ethernet port acts as a trunk port or as an access port.
Management VLAN Subnet Configuration Menu Invisible place holder Figure 3-16. Management VLAN Subnet Configuration Menu NOTE: Changes to any of the following parameters while communicating over the network (LAN or over-the-air) might cause a loss of communication with the unit you are configuring. You must re-establish communication using the new IP address. • IP Address Mode—Defines the source of the IP address of this device. Only static IP addressing mode is available when VLAN Status is enabled.
You can make a network of radios with the DHCP-provided IP address enabled or with DHCP services disabled. In this way, you can accommodate locations for which a fixed IP address is desired. NOTE: There should be only one active DHCP server in a network. If more than one DHCP server exists, network devices might randomly get their IP address from different servers every time they request one. NOTE: Combining DHCP and IEEE 802.
Invisible place holder Figure 3-18. DHCP Server Configuration (Data) Menu • DHCP Server Status—Enable/Disable the response to DHCP requests to assign an IP address. [Disabled/Enabled; Disabled] • DHCP Netmask—IP • • • • netmask to be assigned along with the IP address in response to a DHCP request. [0.0.0.0] DHCP starting address—Lowest IP address in the range of addresses provided by this device. [0.0.0.0] DHCP ending address—Highest IP address in the range of addresses provided by this device.
• IP Address Mode—Defines the source of this device’s IP address. Only static IP addressing mode is available when VLAN Status is enabled [Static; Static] • IP Address—The IPv4 local IP address. [192.168.1.1] • IP Netmask—The IPv4 local subnet mask. This value is used when the radio attempts to send a locally initiated message, from either the terminal server or the management process. [255.255.0.0] • IP Gateway—The IPv4 address of the default gateway device, typically a router. [0.0.0.
• Static IP Gateway—The IPv4 address of the network gateway device, typically a router. This field is unnecessary if DHCP is enabled. [0.0.0.0] The lower three items on the screen (Current IP Address, Netmask and Gateway) show the actual addressing at the transceiver whether it was obtained from static configuration or from a DHCP server. 802.11 Configuration Submenu Invisible place holder Figure 3-21. 802.11 Configuration Submenu • • • • • • • 54 802.
3.4.2 Ethernet Port Configuration Menu The transceiver allows for special control of the Ethernet interface, to allow traffic awareness and availability of the backhaul network for redundancy purposes. NOTE: The transceiver’s network port supports 10BaseT and 100BaseT connections. Confirm that your hub/switch is capable of auto-switching data rates. To prevent excessive Ethernet traffic from degrading performance, place the transceiver in a segment, or behind routers. Invisible place holder Figure 3-22.
Ethernet Filtering Configuration Menu Invisible place holder Figure 3-23. Ethernet Filtering Configuration Menu • Enable Filtering—Activates Ethernet [enabled, disabled; disabled] • Address 1, 2, 3, 4—Ethernet filtering. address fields. When filtering is enabled, the Mercury only accepts traffic on its Ethernet port from the configured addresses. [Valid MAC address string] 3.4.3 Bridge Configuration Invisible place holder Figure 3-24.
• Bridge Forward Delay—View/set spanning tree forwarding delay. Affects how long the bridge spends listening and learning after initialization. [4-30 seconds; 5 seconds]. 3.4.4 SNMP Agent Configuration The transceiver contains over 100 custom SNMP-manageable objects as well as the IETF standard RFC1213 for protocol statistics, also known as MIB II. You can use off-the-shelf SNMP managers to access the transceiver’s SNMP Agent’s MIB, such as Castle Rock Computing SNMPc™ and Hewlett Packard OpenView™.
Invisible place holder Figure 3-25. SNMP Server Configuration Menu This menu provides configuration and control of vital SNMP functions. • • • • • • 58 Read Community String—SNMP community name with SNMPv1/SNMPv2c read access. This string can contain up to 30 alpha-numeric characters. Write Community String—SNMP community name with SNMPv1/SNMPv2c write access. This string can contain up to 30 alpha-numeric characters. Trap Community String—SNMP community name with SNMPv1/SNMPv2c trap access.
• Trap Version—This specifies which version of SNMP is used to encode the outgoing traps. The choices are v1_traps, v2_traps, and v3_traps. When v3_traps is selected, v2-style traps are sent, but with a v3 header. [v1_traps, v2_traps, v3_traps] • Auth Traps Status—Indicates whether or not traps are generated for failed authentication of an SNMP PDU. [Disabled/Enabled; Disabled] • SNMP V3 Passwords—Determines whether v3 passwords are managed locally or via an SNMP Manager.
Invisible place holder Figure 3-27. AP Location Info Configuration Menu, TFTP Mode (Firmware version 3.0 only) Invisible place holder Figure 3-28. AP Location Info Configuration Menu, USB Mode (Firmware version 3.0 or later) • • • • • 60 selection of methods for transferring files to and from the radio available on firmware version 3.0 radios. The options are: TFTP and USB. TFTP Host Address—IP address of the TFTP server that holds the AP locations file. [any valid IP address; 0.0.0.
• Retrieve Text File—Download AP Locations text file from the server. • • Send Text File—Upload the local AP Locations file to the server. on-screen review of the AP Locations file. An example screen is shown in Figure 3-29. Invisible place holder View AP Location File—Allows Figure 3-29. AP Location Text File AP Locations File Syntax and Guidelines The AP Locations file is used by the Remote radio to determine which Access Point to connect to when operating in Hopping w/ Hand-offs mode.
• SINGLE_CHAN—Specifies the AP’s Single Frequency mode channel. The MAC label may appear twice if a P23 redundant Access Point is installed at that location. In this case, one MAC statement provides the MAC address of the A radio and the other MAC statement provides the MAC address of the B radio. The CHANNELS statement only needs to be present if the channel selection feature is used at the Access Point to limit which channels are active.
Invisible place holder Figure 3-30. SNTP Server Entry (on Network Configuration Menu) When SNTP Server is selected (item H), the area to the right of the parameter becomes active, allowing you to enter a valid SNTP server address. Press the Return key to make the address entry active. 3.5 RADIO CONFIGURATION There are two primary layers in the transceiver network—radio and data. Since the data layer is dependent on the radio layer working properly, configure and set the radio items before proceeding.
Figure 3-32. Radio Configuration Menu (From Remote Unit) Invisible place holder Figure 3-33. Radio Configuration Menu (From Option Set 1 Remote) • Network Name—The user-defined name for the wireless network. [Any 40 character string; MDS-Mercury] • Transmit Power (AP Only)—Sets/displays RF power output level in dBm. This setting should reflect local regulatory limitations and losses in antenna transmission line.
• • • • • Max Transmit Power (Remote Only)—Sets/displays maximum RF power output level in dBm of the Remote. Power level is still controlled by the AP, but it is limited to the maximum level set here. This setting should reflect local regulatory limitations and losses in antenna transmission line. (See “How Much Output Power Can be Used?” on Page 167 for information on how to calculate this value.
Invisible place holder Figure 3-35. Frequency Control Menu (900 MHz AP, Static Hopping Freq. Mode) Figure 3-36. Frequency Control Menu (900 MHz Remote, Hopping w/Hand-offs Freq. Mode) 66 Mercury Reference Manual 05-4446A01, Rev.
