Rajant Support Helpdesk
Open a new ticket here:
Submit a Ticket
Frequently Asked Questions
No, Rajant BreadCrumb management tools (BC|Commander, BC|Connector, BC|Enterprise, and BCAPI) do not use the Log4j library and are not affected by the CVE-2021-44228 vulnerability. Please submit a ticket if you have any questions.
.Partners can submit support requests via https://helpdesk.rajant.com/helpdesk/customer-care-1/submit which creates an email chain between the ticket requester and Rajant Support.
The Partner will need to enter the following information:
Partner Employee Name
Company Contact Email Address (no personal emails)
Partner/Reseller Company Name
Partner/Reseller Contact Name (Whom should Rajant contact if needed)
Subject (reason why Partner is requesting support)
A detailed description of the issues seen on the mesh
If this is a request for technical support, please provide a full mesh snapshot
After creating a support request, our team will verify that technical support is required and list all options available for the partner. After confirming that the Partner wishes to be charged for services, Rajant Support will immediately begin to identify any issues seen on the network. Rajant will send any recommendations that could possibly remedy the problem. Finally, the Support Agent will notify the Partner in the email chain that their account has been charged (X) hours. Support will follow up to ensure the issue has been resolved before closing the ticket.
Open a ticket via:
Technical support may include, but will not be limited to these topics:
-Initial Mesh Snapshot analysis and network diagnosis (~3 hours)
-Full Kinetic Mesh Detailed Report (KMDR), included in some BC|Assurance packages.
With an active BC|Assurance subscription a Partner/client will NEVER be charged for:
-Kinetic Mesh Snapshot Summary (KMSS)
-Techncial questions about BreadCrumbs/InstaMesh capabilities
-Pre-Sales Technical Support
-Issues determined to be a firmware or protocol fault
Support Hours - All technical support requests require our Partners to have time remaining on their accounts before providing analysis and/or potential diagnosis of issues on the mesh network. KMSS - Our knowledgeable Partners can expedite support to end-users by providing access to in-depth Kinetic Mesh Snapshot Summaries (KMSS) that contain important statistical data.
KMDR Credit (optional) - Access to a full Kinetic Mesh Detailed Report (KMDR), which is a very detailed version of the KMSS that includes actionable recommendations crafted by Rajant engineers to improve the overall health off a Rajant Kinetic Mesh and mitigate application performance loss due to Network Drift. At this time there are packages that include 0, 1, 2 or 3 KMDRs per year.
There are many variables that could possibly hinder a Rajant network. Therefore, it is difficult to guarantee a timeframe in which Rajant can present a diagnosis with possible suggestions. Your mesh network will be reviewed by various Rajant experts and your Support Agent will work to combine and condense all of their suggestions before reporting back. We take the utmost care to update the customer as quickly as possible with any meaningful findings we have.
-Prefer a KMSS at no hourly charge (with an active BC|Assurance subscription)
-Like to use a KMDR credit (if any remaining)
-Favor being directed to their Sales Representative to purchase hours
-Instead continue with remaining time on this particular issue (1 hour minimum). Rajant will report any findings and recommendations made during this time, and will alert the Partner after their hours have been depleted. The account will need to be re-charged before an additional support ticket can be submitted. Support will continue and hours will be logged upon account depletion. A negative balance will be deducted from the next purchase of hours.
Please click help at the top of this page and open a ticket with the subject:
'Country Code Change Request' and the following information:
End User Company Name:
End User Address:
End User Site Name:
End User Contact Name:
End User Contact Email:
Country currently set to:
Country requested to be reset to:
Model of Breadcrumbs to be reset:
Number of Breadcrumbs to be reset:
Email address of Requester (you):
Your request will be processed by the Rajant Support Team.
BreadCrumbs must share some settings in order to mesh with one another. The key requirements and BC|Commander configuration locations for those settings are as follows:
Enable Meshing: All BreadCrumbs must have meshing enabled.
Network Name: All BreadCrumbs must share the same Network Name. This should be changed from the default, "Rajant Mesh Network."
BreadCrumb Configuration -> Network -> Network Name.
Packet Cipher: All BreadCrumbs must share Packet Cipher settings. The default is "none."
BreadCrumb Configuration -> Security -> Packet Cipher.
MAC Address Cipher: All BreadCrumbs must share the same MAC Address Cipher settings. The default is "none."
BreadCrumb Configuration -> Security -> MAC Address Cipher.
Per-Hop Authentication Algorithm: All BreadCrumbs must share Per-Hop Authentication settings. The default is "none."
BreadCrumb Configuration -> Security -> Per-Hop Authentication Algorithm.
Network Key: All BreadCrumbs must share the same Network Key. The default is 64 zeros (0's).
BreadCrumb Configuration -> Security -> Network Key.
Network Key Sequence Number: All BreadCrumbs must share the same Network Key Sequence Number.
BreadCrumb Configuration -> Security -> Network Key Sequence Number.
Per Radio Mesh Cluster ID: All BreadCrumbs must share the same Mesh Cluster ID. The default setting is "cluster 0."
BreadCrumb Configuration -> Ports -> wlan (0-3) -> Mesh -> Mesh Cluster ID.
Channel Settings: In general, channel settings must be homogeneous for BreadCrumbs to communicate with each other. Meshing will also need to be enabled as well as configuring bandwidth settings so that they are homogeneous.
For this setting there is radio specific information that needs to be followed. The criteria and guidelines can be seen below.
- BreadCrumbs with 802.11a radios configured for 40 MHz mode will only mesh with radios that have identical configurations.
- BreadCrumbs with 802.11n radios configured for ht20 mode will mesh with BreadCrumbs 802.11bgan, as well as BreadCrumbs in 20 MHz (bga) mode or ht20 mode.
- BreadCrumbs with 802.11n radios configured for ht20 mode will mesh with 802.11n radios in ht40 mode but only at 20 MHz channel bandwidth.
- A BreadCrumb configured for ht40 mode will mesh with radios in 20 MHz (bga) mode but only at 20 MHz channel bandwidth, ht20 mode but only at 20 MHz channel bandwidth, and ht40 mode was long as it has the same sign (ht40+ will not mesh with ht40-).
- A radio in 10 MHz mode can only mesh with other 10 MHz mode radios, and a radio in 5 MHz mode can only mesh with 5 MHz mode radios.
BreadCrumb Configuration -> Ports -> wlan (0-3) -> Radio -> Channel Number.
FE1: 20 — 60 VDC Passive PoE
**LX5**: 18 — 48* VDC Passive PoE
ME4: 8 — 48 VDC Passive PoE
KM3: 24 — 48 VDC Passive PoE
ES1: 9 — 30 VDC Passive PoE
DX2: 8 — 60 VDC Passive PoE
JR3: 9 — 30 VDC Passive PoE .
SlipStream 12 V, 3 A (power adapter included)
For older models refer to the spec sheet at https://secure.rajant.com/
*Please note lab testing determined that operating the LX5 BreadCrumb at or above the recommended maximum input voltage of 48 volts, when other contributing factors are present, produces a greater quantity of errors that contribute to radio events. Please see TSB - LX5 Radio Reset Event Mitigation for Rajant recommended power injector options, available at secure.rajant.com.
The specifications and guidelines for directly mounting antennas is model specific. The information can be found in the User Guide for each model.
For best performance we recommend having all antennas externally mounted/connected. There is a low level of electronic interference that naturally occurs when two antennas are directly attached.
When attaching an antenna or cable for use outdoors or in damp/dusty conditions, that external connection needs its own protection. To find more information regarding water and other possible environmental ingress prevention, please refer to the Technical Service Bulletin section in that back of that specific BreadCrumb model's user guide. Waterproofing steps are provided with pictures of how to correctly seal your BreadCrumb ports, and which products we recommend for the process. Additionally, this information can be found in documentation on our support site by searching 'waterproofing' or 'sealing' under the Files tab.
Rajant support also provides a Support Portal that allows for downloads of software and user guides. Please visit https://secure.rajant.com/ and select 'Login.
Spec sheets can be found rajant.com, the Support Portal, and the Partner Portal.
LX5 and ME4 Temperature Ranges
Other Models Temperature Ranges
The status LED is used to indicate the mesh status of a BreadCrumb, as well as error codes that may occur. The BreadCrumb LED status is dependent on the firmware version, not the BreadCrumb Model. Some models do not have an indicator LED.
Solid Green - BreadCrumb is meshed and functioning correctly. There is at least one connected mesh peer transmitting with a data rate of 24 Mbps or higher.
Flashing Green - This indicates all mesh links have a data transfer rate below 24 Mbps. It can be changed to indicate the Instamesh cost to the IPv4 Gateway in BC|Commander, but the mesh peers status is default.
Solid Blue - BreadCrumb is ready to mesh, but there are no available mesh connections. Ensure the requirements for meshing are met.
Red flashing light - Severe hardware issue. Take note of the flashing error code (Error codes can be referenced in the BreadCrumb User Guide) and contact Rajant Customer Support by clicking help at the top of this page for further assistance with the issue.
Cycling Lights - Either a firmware update has been completed, the BreadCrumb is rebooting, or the "Identify" feature in BC|Commander has been used to identify the BreadCrumb.
Note: The indicator LED can be disabled or enabled by holding the button for 1 second (depends on the model) or through BC|Commander. Go to BreadCrumb Configuration -> General -> Status LED. Be aware that holding the button much longer could Zeroize (factory reset) your BreadCrumb.
Please contact your Rajant regional sales representative. They will be able to best assist you in resolving your account issue and provide suggestions for your organization. If you are not sure who your sales representative is, contact Rajant Customer Support by clicking help at the top of this page. The support team will find your sales representative and have them reach out to you.
Please contact your Rajant regional sales representative. They will assist you in resetting your account. If you are not sure who your sales representative is, contact Rajant Customer Support by clicking help at the top of this page. The support team will find your sales representative and have them reach out to you.
If the switch you are connected to or the computer running BC|Commander does not support IPv6, you will need to have an IPv4 address in the same subnet as the BreadCrumb. If the ethernet port on the switch that the PC running BC|Commander is connected to or that BreadCrumb is connected to is disabled, you will not be able to connect to the BreadCrumb directly. Consider examining or looking further into those specified settings.
In BC|Commander v11, navigate to File -> Preferences -> BreadCrumb Discovery and select Both for discovery protocol. Following the above directions should allow you to find BreadCrumbs utilizing IPv6, as long as VLANs are configured correctly or not in use.
Go to the Mesh tab in BC|Commander and select the “Scan for BreadCrumbs” option. This will search for undiscovered BreadCrumbs.
Each breadcrumb can have multiple variations in configuration. Most problems seen in a mesh can be correlated to unintentional inconsistent configurations in BC|Commander. It is very common that specific configurations can be made in individual nodes, but not in others. This can cause detrimental effects to or inhibit maximum network potential.
Mesh Analyze is the best "first glance tool" to make sure the configurations amongst desired groups of nodes and networks are as uniform as planned. To use the Mesh Analyze tool, you select the “Mesh” tab on the top left in BC|Commander and choose Analyze.
Mesh Analyze performs a link and configuration analysis against the current mesh and displays the results in the current tab. It brings up configuration inconsistencies that can be used to assist in configuring individual nodes to match. For detailed information about this feature, you can view the most recent BC|Commander User Guide via the Support Portal in the Files section.
A mesh snapshot stores details about the network running at that time. Rajant Support uses these to diagnose technical issues.
To take a snapshot in BC|Commander, select 'File' -> 'Save Mesh Snapshot As ' -> press 'OK' to begin the snapshot taking process. If all BreadCrumbs are not captured during this process, ensure they are selected in the UI and extend the snapshot timeout.
The APT Priority of a BreadCrumb determines who the APT Master is for the network. The BreadCrumb with the highest priority will be the master. If there are two BreadCrumbs with the same APT Priority, the one with the highest MAC Address will be the Master. APT Priority can be set manually if a network has a preference on the order of which BreadCrumbs will become Master.
The default APT Priority for most BreadCrumbs is 100. The SlipStream has an APT Priority of 110 by default since it is designed for the role of APT Master and dedicated to the aggregation of wired traffic. Some other models such as the JR3 have a lower default APT Priority and are not designed to handle being APT Master.
By default a BreadCrumb starting up or connecting to the ethernet for the first time will not take over from the current APT Master to avoid network disruption, even if it has a higher APT Priority. The new BreadCrumb will become the next highest APT Priority should the current APT Master be disconnected or restarted. This can be changed so that the highest priority BreadCrumb always becomes the Master right away via the "Request Fallback" feature on the desired Ethernet port in the specific BreadCrumb's configuration settings.
The colored dot (Flag) next to each BreadCrumb indicates the current status of a BreadCrumb. There are four colors that these indicators can be.
Green - The BreadCrumb is connected to BC|Commander.
Red - The BreadCrumb was previously connected to the network and/or BC|Commander but is not currently connected. This could be an indicator that the password is entered incorrectly if you just opened BC|Commander and attempted to authenticate. To find out, right click on the column header and add the "Connection Status" column. It will indicate if a red dot means login failure or disconnected.
Grey - BreadCrumb is disconnected. May appear white or grey. If you just opened BC|Commander and have not entered BreadCrumb login information yet, you may see this color on discovered BreadCrumbs.
Blue - Attempting to connect to this BreadCrumb with BC|Commander.
Other Flags - These (if any) will show in addition to the main flags listed above.
Gold Key - Crypto Officer
Silver Key - Admin
Magnifying Glass: View Only
Red X: Severe error detected, see alerts section.
Yellow Caution Triangle: Warnings detected, see alerts section.
Yellow Circle Arrow: Rebooting.
BreadCrumb networks are designed for easy use and setup by using default settings. This allows them to mesh right out of the box. It is recommended for all passwords (crypto officer, admin, view, and the Network Key) be changed on established networks. This alert appears to remind you to change the settings so that an unauthorized BreadCrumb will not connect to your mesh network, and so unknown users on the LAN (or from any BreadCrumb's Ethernet) will not be able to configure the network without knowing the non-default passphrases/keys you set.
BC|Enterprise is a web based application that helps monitor network performance. The program is "always on," monitoring and gathering data. The data is examined using either individual BreadCrumbs or groups specified by the network administrator. The program can be utilized on site or remotely, and supports multiple user accounts.
When making changes to BC|Enterprise and the user has saved those changes, a prompt appears stating that settings are being changed and that the program is being restarted. In order for the program to restart automatically, a step after installation must be enabled. For a Windows machine you will need to go to the Windows Service Controller, and select “Rajant BC|Enterprise Service,” right click and select “Choose Properties.” In the “Service Properties” dialog box that appears make sure that “Automatic” is set for the startup type. On the “Recovery” tab, “First Failure,” “Second Failure,” and “Subsequent Failure” need to be set to “Restart Service.” Lastly, the “Restart Services After” option needs to be set to 0 minutes.
Detailed instructions and screenshots of this process can be found in the BC|Enterprise User Guide in section Section 2.3.2: Installing on 64-bit Microsoft Windows and look at Figure - C. Information on completing this process for other operating systems are also included.
The values that appear in the Channel Activity graphs are always the correct instantaneous channel activity value. The gaps that are seen in these graphs do not indicate problems for the BreadCrumb. The gaps in this graph typically occur for two different reasons. The first is that there is no difference between two update packets. When this occurs the formula that is programmed to calculate the channel activity can not be completed because of a missing value in the calculations. The second is that when BC|Enterprise has received an update that did not include radio time counter information. When the data is received without this information, BC|Enterprise assumes that the radio had been reset and does not generate channel activity values for this time period.
The gaps in this graph can be avoided by increasing the time between BreadCrumb updates in BC|Connector. By increasing this value, the likelihood of a time difference in the radios increases. Locate the “General Watch Interval” (general.watch) and change the value. The default setting is every 8 seconds, the recommended increased amount is 30 seconds.
Please note that the following answer assumes BC|Connector is functioning properly and the BreadCrumbs have been running for an extended period of time.
The charts titled “Top TX Data Rate,” “Top TX Packets/sec,” “Top RX Data Rate,” and “Top RX Packets/sec” contain information that BC|Enterprise considers optional. To allow these graphs to populate, a certain setting must be enabled. Enabling this option can put strain on your network, so enabling this feature only on the BreadCrumbs that you are interested in monitoring is recommended. To enable it, go to Configure -> Instamesh -> General -> Enable Peer Statistics Reporting.
If the file is smaller than 1 GB, you can make a note in the ticket submission that the file was too large. The Support Team will then send a customized link for file uploads (or see the next paragraph to handle this in advanced). Note that this method does require a valid Support Portal login.
The upload link will be in this format:
https://secure.rajant.com/snapshot/upload?ticket= nnnnn where “ nnnnn ” is the ticket number that the snapshot is associated with. Please reply to your open Helpdesk ticket with the name of this snapshot so the Support Team will quickly know it is now available. You should open the ticket first to get a ticket number if you have not already done so and mention you are about to upload it.
If the file is larger than 1 GB, mention that in the ticket submission and the Support Team will direct you on the next course of action.
Rajant support also provides a Support Portal that allows for downloads of software and user guides. Please visit https://secure.rajant.com/ and select 'Login.'
Spec sheets can be found rajant.com, the Support Portal, and the Partner Portal.
Configuration Best Practices (by topic)
If any of the radio ports are not in use, if there is no antenna attached, then an attenuator or RF terminator should be placed on those ports and the “Enable Mesh” option in BC|Commander should be unchecked. Leaving the antennas uncapped will affect the performance of the radio and cause damage to your radio in the long term .
When determining the wlan channel settings, it is important to find the one that has the least amount of busy time. To accomplish this select each of the different available channels and select the one that displays the smallest Busy Time percentage in the “Radio” section of the “Details” pane.
When adjusting the Range for one of the wlans, it needs to be set to the maximum distance that is going to be needed for the network. If this range is set lower than is required, this could result in unnecessary retries. If the range is set too high, the maximum throughput of your network will be lowered.
Dynamic Transmit Power should be enabled. This provides peer-to-peer automatic power adjustment, which optimizes the signal-to-noise (SNR). Enabling this allows the BreadCrumb to change the power depending on the proximity of the device that it is communicating with. For example, a BreadCrumb would use high power for distant devices, and low power for those that are located in close proximity.
Radio Beacon Intervals are packets sent periodically from BreadCrumbs to indicate their presence. Rajant recommends a limit of 400 ms. If SSIDs are configured and AP mode is in use, this setting should be set to 10 times the number of BreadCrumbs. For mesh only mode, this setting is ignored and beacons are always sent once per second. Following these rules will help reduce noise and interference on your network caused by these packets.
Radio Timeout in seconds is the inactivity timer that is used to detect/remove lost connections. Recommended to be set to 3 times the number of BreadCrumbs.
An important feature to utilize is APT Timeout, which is how long an APT peer will wait before it terminates a connection because of a lack of keepalive packets received. The value also determines how long a network will wait without communication from a Master before a new one is elected. For networks with original (non-rapid) Spanning Tree a minimum value of 45,000 ms is used internally even if the configured APT timeout is less than 45,000 ms. For networks with Rapid Spanning Tree a minimum value of 8,000 ms is used internally even if the configured APT timeout is less than 8,000 ms. If you are not sure, Rajant recommends using the default value of 45,000 ms. Using a value that is too small can result in multiple APT masters and loop conditions that will be detrimental to mesh performance and stability.
For BreadCrumbs connected directly to another device that isn't a switch or router, the APT Timeout can be configured as low as 6,000 ms.
The Flood Rate setting should be utilized. It will help networks that suffer from large amounts of unnecessary packets, such as broadcast and multicast.
To access this setting, highlight the BreadCrumb(s), right click and select “Configure”. Select “InstaMess” from the navigation pane on the left side of the popup window. Scroll down until you reach “Max Flood (packets/second)”. For this field we recommend starting with a value of 20. Then select the “Max Flood per Source (packets/second)”, which we recommend starting with a value of 10.
The multicast rate for your network should be left at default settings to start with. Setting your multicast rate lower will allow the signal to reach farther but could cause congestion on your network. If you require a desired throughout, the multicast rate should be set to 1.5 to 2 times that amount. Higher multicast rates will have less range and may be transmitted at lower power.
Under the Security settings in BC|Commander, the Network Key needs to be set. Once you have set this value you CAN NOT read it back from the BreadCrumb, so make sure that that information is saved somewhere. Also, there are other passphrases, such as the SSID WPA2 passphrase, that cannot be read back. Remember all BreadCrumbs must have the same Network Name and Network Key in order to mesh with other BreadCrumbs.