CBF Networks Inc. dba Fastback Networks 107 User Manual
IBR Installation Guide
Page 20 of 21
Doc # 770-00033.0
Jan. 22, 2016
• Boot loader recovery can be accomplished by an operator via CLI.
• IBR has the ability to recover on its own from a failed software upgrade.
• Add-on licenses to increase the available throughput of IBR can be downloaded using the GUI. For
• IBR has the ability to recover on its own from a failed software upgrade.
• Add-on licenses to increase the available throughput of IBR can be downloaded using the GUI. For
additional information, see the CLI Guide.
6.4
Security
Security features of IBR include:
Security features of IBR include:
• AES encryption on over-the-air links;
• Access control lists;
• Multicast and broadcast storm control;
• Port protection and blocking
• Access control lists;
• Multicast and broadcast storm control;
• Port protection and blocking
7.
Field Test Procedure
The following procedure can be run to test a link after successful installation of IBRs and link establishment,
and at other times as necessary.
7.1
Firmware Upgrade
If it is necessary to upgrade IBR’s firmware, this can be accomplished using CLI or GUI. See the CLI Guide for
If it is necessary to upgrade IBR’s firmware, this can be accomplished using CLI or GUI. See the CLI Guide for
detailed instructions.
Note: Both radios on a link should be running the same firmware revision.
Note: Both radios on a link should be running the same firmware revision.
7.2
RFC 2544 Traffic Tests
Reboot both IBRs and after they are in-sync determine the MCS levels for each radio using the
command:
IBR# show interface radio 0 status
MCS levels will show a predicted throughput number. Both radios should be using 40 MHz bandwidth
channels or a mix of 40 MHz and 20 MHz or 10 MHz channels. If MCS is 13 13 13 13 and
- BW is 40 MHz, the predicted TPUT should be 218 Mb/s for TX and RX in both directions.
- BW is 20 MHz, the predicted TPUT should be 107 Mb/s for TX and RX in both directions.
- BW is 20 MHz, the predicted TPUT should be 107 Mb/s for TX and RX in both directions.
Connect the RFC testest and run the RFC-2544 test for TPUT/latency/jitter. For link MCS 13 13 the
expected result for 1024 byte packets for Layer 2 will be about 420 packets in each direction or 840
Mb/s in loopback mode.
7.3
Endurance Test
Establish traffic in both directions at 80% capacity and run continuously for seven (7) days.
The expected outcome is that there will be no reboots and total frame losses will be less than 5.0E-4.
Establish traffic in both directions at 80% capacity and run continuously for seven (7) days.
The expected outcome is that there will be no reboots and total frame losses will be less than 5.0E-4.
7.4
Traffic Classification Test
Configure an Ethernet tester for two streams, as follows:
- Stream 1: CoS=7; BW=50 Mbps
- Stream 2: CoS=6, BW=300 Mbps
- Stream 2: CoS=6, BW=300 Mbps
Observe that there are a negligible number of drops on Stream 1.
The expected outcome is that all higher priority traffic will be served ahead of lower priority traffic.