Frequently Asked Questions
Please contact support at Support@rajant.com 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 Rajant Support Engineers.
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.
BreadCrumb Configuration -> Ports -> wlan (0-3) -> Mesh -> Enable Meshing.
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 provides a partner portal that allows for downloads of software and documentation. Please visit https://secure.rajant.com/ and select ‘Login’.
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" 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 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|Connector 11.22 and later require the user to update the .hocon file with new network keys and passphrase information, which is different than previous versions that used a .config file. Updating the .hocon file with the desired network key and login passphrases for co, admin, and view should be done here. This does not change the configuration of any BreadCrumbs, only what BC|Connector uses to authenticate with them and how users in other applications log into BC|Connector. If your intent is to change the login passphrases on the actual BreadCrumbs, it should be done prior to updating the .hocon file for BC|Connector.
Note: be sure to restart the BC|Connector service after changing the .hocon file for changes to take affect.