9 ® BreadCrumb ME3 USER GUIDE Version: 1.02 Date: April 16, 2010 Corporate Headquarters Rajant Corporation 400 East King Street Malvern, PA 19355 Tel: (484) 595-0233 Fax: (484) 595-0244 http://www.rajant.
FCC and IC Statements This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the device is operated in a commercial environment. This device generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with this instruction manual, may cause harmful interference to radio communications.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 Table of Contents Preface....................................................................................................................................v Purpose and Scope.............................................................................................................v User Information..................................................................................................................
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 5 Troubleshooting..............................................................................................................21 5.1 Sporadic Network Connectivity..................................................................................21 5.2 BreadCrumb Device Cannot Connect to BCWN.......................................................22 Appendix A: Error and Warning Codes...................................................
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 Preface Purpose and Scope This manual provides information and guidance to all personnel who are involved with and use Rajant Corporation’s BreadCrumb ME3 product. This manual begins with an introduction to the BreadCrumb Wireless Network (BCWN). It then characterizes the features of the BreadCrumb ME3. Finally, it describes common deployment scenarios and provides concise step-by-step instructions for each scenario.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 1 Introduction Rajant Corporation's (http://www.rajant.com) BreadCrumb ME3 utilizes the 802.11g wireless networking standard to form a wireless mesh network. The network is mobile, self-integrating, selfmeshing, self-healing, full-duplex and secure. The focus is on flexibility, adaptability, and simplicity.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 In many cases, BreadCrumbs will perform all of these tasks as shipped with no configuration necessary at all, providing an instant TAN (Tactical Area Network). Moreover, because BreadCrumbs use industry-standard 802.11 communications, client devices such as laptops or handheld computers require no special hardware, software, or configuration to access a BCWN. 1.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 Example 1: Suppose you have three BreadCrumbs, called A, B, and C. Each has two radios. BreadCrumb A’s radios are on channels 1 and 8, B’s are on 8 and 11, and C’s are on 1 and 11. All three BreadCrumbs are using the default ESSID of "breadcrumb54-v10.
BreadCrumb® ME3 User Guide Version: 1.02 1.3.1 Rajant Corporation 03-100116-001 Radio BreadCrumb ME3 comprises one 802.11g radio, which depending on the ME3 model, operates either in the 900 MHz or the 2.4 GHz frequency band. The ME3 model versus radio frequency options are listed in Table 1 below. Table 1: ME3 Model versus Radio Frequency. ME3 Model Radio Frequency ME3-24 2.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 Table 3: 900 MHz Radio Channels and Frequencies. Channel Number Center Frequency (MHz) 5 912 6 917 The default channel for a 900 MHz BreadCrumb radio is 6 (917 MHz). 1.3.2 Enclosure The ME3 enclosure has been designed to operate in extreme conditions with protection against ingress of dust as well as protection against immersion in water. The enclosure dimensions are 176 mm x 95 mm x 48 mm (6.94” x 3.75” x 1.88”).
BreadCrumb® ME3 User Guide Version: 1.02 1.3.3 Rajant Corporation 03-100116-001 18-Pin Amphenol Connector The majority of the signals and features of BreadCrumb ME3 can be accessed through the 18-pin Amphenol connector on the enclosure (see Figure 4). The most important of these interfaces are external power, Ethernet, and USB, which are described in more detail in the following sections. Figure 4: 18-Pin Amphenol Connector.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 the18-pin Amphenol connector on the enclosure (see Figure 3 and Figure 4). The ports support Auto MDI/MDIX allowing the use of either straight-through or crossover data cables for connections. The data interface includes electrostatic discharge, and electrical fast transient/burst immunity compliant to the IEC 61000-4-2, and IEC 61000-4-4-EFT standards, respectively.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 Table 4: Status LED Color Codes.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 • Release the switch. • When the Zeroize Keys and Restore Factory Defaults operation is complete, the Status LED changes to the error indicator of blinking red (see Table 4 above and error code 32 in Appendix A ). The BreadCrumb will then wait for about 30 seconds before rebooting automatically. Tip 1.3.6.
BreadCrumb® ME3 User Guide Version: 1.02 Warning 1.3.7 Rajant Corporation 03-100116-001 The BreadCrumb ME3 Status LED may exhibit a short blink after a warm reset condition that occurs due to system error or is initiated by the user (e.g., performing a reboot command through BC|Commander, performing the Zeroize Keys and Restore Factory Defaults procedure). The LED must be physically masked (such as adding tape to the LED lens) to guarantee that no light is emitted at any time.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 2 Using BC|Commander BC|Commander is Rajant’s software package used for monitoring the status of BreadCrumbs with version 10 firmware on a BreadCrumb Wireless Network (BCWN). BC|Commander is also used for configuring version 10 BreadCrumbs and to graphically portray the network topology. Note BC|Commander includes an option called v10 Transitional Mode.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 3 Deploying the BreadCrumb Wireless Network There are many factors which need to be taken into account when deploying the BreadCrumb Wireless Network (BCWN). Section 3.1 describes the addressing scheme of the BCWN. Section 3.2 discusses channel assignments. Section 3.3 details some of the most commonly occurring environmental factors that will have a major impact on the performance of the BCWN. Finally, section 3.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 BreadCrumb channel configuration. 3.3 Physical Placement and other Considerations Commonly occurring environmental factors have a significant impact on performance and behavior of the BreadCrumb Wireless Network. LOS (Line of Sight) obstructions, distance, weather, and device placement should all be considered when deploying a wireless network. IEEE 802.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 distance, connectivity and tactical placement is achieved. 3.3.3 Weather Precipitation and fog also act as obstructions blocking the propagation of the wireless network’s radio waves. Light fog or precipitation may result in noticeable degradation of wireless network performance. Heavy precipitation or fog may result in severe performance degradation and possible loss of network connectivity.
BreadCrumb® ME3 User Guide Version: 1.02 3.4.1 Rajant Corporation 03-100116-001 Deployment Guidelines Follow these guidelines when deploying the BCWN: 1. Placement of BCWN components (a) Elevate the BCWN components whenever possible. i. Directly on the ground, the maximum distance between any two BCWN components is approximately 300 ft. Also, the maximum distance between a wireless client and the nearest BCWN component is approximately 300 ft. ii.
Rajant Corporation 03-100116-001 BreadCrumb® ME3 User Guide Version: 1.02 BC|Commander while another deploys the BreadCrumbs. This method requires some form of communication (radio, cell phone, etc.) between the two persons. 3. Determine the location for the first BreadCrumb. 4. Power ON the device. 5. Wait approximately 90 seconds for the device to boot. 6. Power ON the BC|Commander PC. 7. Start BC|Commander. 8. The BC|Commander console should display the first BreadCrumb. 9.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 4 BreadCrumb ME3 USB Firmware Upgrade Each BreadCrumb relies on low-level software known as firmware for proper execution. Rajant periodically releases updated BreadCrumb firmware. The updated firmware must be obtained from Rajant.
BreadCrumb® ME3 User Guide Version: 1.02 Note 20 Rajant Corporation 03-100116-001 An alternative method of upgrading the firmware of a BreadCrumb ME3 is explained in the BC|Commander User Guide document. This method, called Over The Air (OTA) firmware upgrade, offers the convenience of remote and completely software controlled firmware upgrades.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 5 5.1 Troubleshooting Sporadic Network Connectivity Table 6: Sporadic Network Connectivity Issues. Problem Resolution As a BreadCrumb device’s battery approaches exhaustion, network connectivity will become sporadic for the BreadCrumb device and its associated wireless clients. Monitory battery usage and charge/replace batteries as necessary.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 Problem Resolution your wireless card. 5.2 ● Ensure that the wireless client’s IP address settings are configured properly. ● Ensure that the security settings on the client device and BreadCrumb devices match. ● Ensure that the client device is not prevented from connectingby an ACL. ● If the BreadCrumb devices comprising the network have AirFortress encryption enabled, ensure that the client does as well.
Rajant Corporation 03-100116-001 BreadCrumb® ME3 User Guide Version: 1.02 Appendix A: Error and Warning Codes All possible BreadCrumb error and warning codes are listed below: LX/LX3/ME3 Firmware Upgrade Codes (1*). 11 – Flash image file does not exist. 12 – Current flash image version is greater than versions of files found on USB drive. 13 – No flash image files found. 14 – Unable to mount USB drive. 15 – Unlocking of /dev/mtd0 failed. 16 – fconfig for SetFailsafeBoot failed.
BreadCrumb® ME3 User Guide Version: 1.02 Rajant Corporation 03-100116-001 128 – Failed to checksum file system image. 129 – Failed to create directory for next file system image. 131 – Failed to mount next file system image. 132 – Failed to create directory for settings. 133 – Failed to copy current settings to next file system image. 134 – Failed to unmount next file system image. 141 – Error retrieving flash file. ME2 Firmware Upgrade Codes (2*) 21 – Flash image file does not exist.
Rajant Corporation 03-100116-001 BreadCrumb® ME3 User Guide Version: 1.02 FIPS Codes (4*) 41 – FIPS self-tests failed. 411 – OpenSSL FIPS vector test programs not found. 412 – OpenSSL FIPS vector test hash mismatch. 413 – 802.11i AES-CCMP test vectors failed. 414 – Unable to use FIPS CCMP encryption. 415 – Kernel integrity check failed. 416 – Filesystem integrity check failed. 42 – Mixed SecNet/Non-SecNet configuration. 43 – Rekeying error. 44 – Rekeying error. 45 – Rekeying error. 46 – Rekeying error.
BreadCrumb® ME3 User Guide Version: 1.02 Battery Gas Gauge Codes (6*) 61 – Battery gas gauge i2c device could not be found. 62 – Incorrect gas gauge revision 1 EEPROM settings. 63 – Incorrect gas gauge revision 2 EEPROM settings. 64 – Incorrect gas gauge revision 3 EEPROM settings. 65 – Unknown gas gauge revision. 66 – Incorrect ME3 gas gauge revision 0 EEPROM settings. Other Codes (7*) 71 – Host flapping detected. 72 – Critical I2C failure.
