BRMP is the proprietary protocol developed by RACOM. It handles the Backup routing functionality in RipEX networks with respect to radio network requirements.
does not overload the radio network,
enables more than one backup path,
deals with a random packet loss and
enables very fast path switching in cases of network failure.
The protocol always works between two particular RipEX units. Each RipEX network can contain various backup routes and each backup route consists of several alternative paths. We can even configure nested backup paths.
RipEX A sends out “Hello” packets (UDP) via all possible paths to RipEX B.
RipEX B receives these packets and records them according to the received path.
RipEX B sends the list of received “Hello” packets within its own “Hello” packet back to RipEX A.
RipEX A receives this packet and evaluates the conditions of individual paths.
Individual alternative paths can obtain the following states:
|Up||the path is functional and can be used.|
|Down||the path is not functional and cannot be used.|
|Unknown||the path’s state cannot be evaluated due to lack of information. This state is active immediately after the RipEX power-up or its state is not being evaluated, because a higher priority path is being used.|
The route is chosen in the following way:
The first available route in the table Routing / Backup is used.
In case of a lost connection, the route on the next row of the Backup table is used (Policy / Default mode).
In situations of RSS deterioration, the route on the next row in Backup table is used (Policy / Manual mode).
See the respective help for detailed parameter descriptions in RipEX web interface.