ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000 User manual

CRR-1000 Quick Start Guide
June, 2020
Revision History:
Version
Date
Description
1.0
June 01, 2020
New Document

CRR-1000 Quick Start Guide
ii
Contents
1Introduction...........................................................................................................................................1
2Console Access.....................................................................................................................................1
2.1 Serial-Console Parameters............................................................................................................1
2.2 ssh Paramaters...............................................................................................................................2
2.3 Help ‘?’ Function..........................................................................................................................2
2.4 Tab-to-Complete Function............................................................................................................2
3Common CLI Commands.....................................................................................................................2
3.1 Interface Information (show ip)....................................................................................................2
3.2 ICMP Echo (ping).........................................................................................................................3
3.3 Logging Information.....................................................................................................................3
3.3.1 Security-Related Logging (show audit)................................................................................3
3.3.2 Platform Logging (show log)................................................................................................3
3.4 View Route Information (show route)..........................................................................................4
3.5 Configuration Backup (backup save/restore)................................................................................4
3.6 Packet Inspection (net dump)........................................................................................................4
4Firewall Configuration..........................................................................................................................4
4.1 Viewing the Firewall Policy (show filter policy)..........................................................................5
4.2 Setting the Firewall Policy (set filter policy)................................................................................5
4.3 Advanced Firewall Rules..............................................................................................................5
5Network and Routing Protocol Configuration Examples .....................................................................5
5.1 FRR Configuration........................................................................................................................6
5.2 ARES Configuration.....................................................................................................................8
5.2.1 Simple Network: One Router, Two Subnets.......................................................................10
5.2.2 Static Routing: Two Routers, Three Subnets......................................................................11
5.2.3 Dynamic Routing: Two Routers, Four Subnets..................................................................12
5.2.4 Bootstrap Router Example..................................................................................................14
5.2.5 Basic Verification and Troubleshooting .............................................................................16

CRR-1000 Quick Start Guide
1Introduction
This document describes how to quickly configure a CRR-1000 router; the target audience is system
administrators who have prior experience configuring network switches, routers, and VPNs.
CRR-1000 routers can be configured with varying numbers of Ethernet interfaces. The Terms CRR-1000
and CRR are interchangeable and are used to refer the same CRR-1000 family of routers. This quick-start
guide assumes a CRR-1000 with two native CPU interfaces (eth0 and eth1) and a separate, multi-port
switch core. However, the router configuration should work the same on all CRR—1000 Variants. CPU
interfaces eth0 and eth1 are referred to as “LAN” and “WAN,” respectively. Figure 1 depicts the notional
CRR-1000, default IPv4 addresses, and subnet masks.
Figure 1. CRR-1000-2 Device Architecture and Default Addresses.
2Console Access
The CRR-1000 console and its command-line interface (CLI) can be accessed either by a serial
connection or ssh.
2.1 Serial-Console Parameters
Serial-console parameters for various CRR-1000 models are defined in the following table.
CRR-1000
Model
Console Port
Null Modem
Required
Asynchronous
Configuration
HW Flow
Control
SW Flow
Control
CRR-1000-1
RS485_2
Yes
115200/8-N-1
No
No
CRR-1000-2
J4/J5
No
115200/8-N-1
No
No
CRR-1000-3
COM1
Yes
115200/8-N-1
No
No
CRR-1000-4
USB to Serial Adapter
Yes
115200/8-N-1
No
No
CRR-1000-5
J15 Router
No
9600/8-N-1
No
No
CRR-1000-6
J54 Router
No
9600/8-N-1
No
No
Successful serial connection to the CRR-1000 results in the CLI prompt being displayed:
Switch
Core
eth0
eth1
…
LAN ports WAN port
tty
RS-232
serial
"RLAN"
"RWAN"
Router
CPU
192.168.10.254/24
192.168.100.254/24
192.168.10.1/24

CRR-1000 Quick Start Guide
2
admin@CRR>
2.2 ssh Paramaters
Username: admin
Password: admin
Example:
ssh [email protected]
After successful login, the CLI prompt is displayed:
admin@CRR>
2.3 Help ‘?’ Function
Help is available from the command line by entering the ‘?’ character followed by the <enter> key.
The help function is context-specific, i.e., it provides available options for partial commands, e.g.:
admin@CRR> configure ? <HELP>
Available commands:
configure ares - Edit ARES configuration
configure filter - Edit packet filtering rules
configure frr - Enter FRR configuration shell
configure mangle - Edit packet mangle rules
configure nat - Edit packet NAT rules
configure ntp - Edit NTP settings
Entering the ‘?’ character with no preceding command input lists all top-level commands.
2.4 Tab-to-Complete Function
The CLI supports tab completion of commands. If there is more than one option for command
completion, the CLI presents all valid options, as shown below:
admin@CRR> configure Tab
ares captain filter frr mangle nat ntp
A command history is also provided through the up/down arrow keys, which allows the user to cycle
through previous commands.
3Common CLI Commands
The following is a list of commonly used commands on the CRR-1000.
3.1 Interface Information (show ip)
To view a router’s physical interface information such as hardware address, IP addresses, and link state,
enter “show ip” command, e.g.,:
admin@CRR> show ip
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever

CRR-1000 Quick Start Guide
3
inet 127.255.0.1/32 scope host lo
valid_lft forever preferred_lft forever
inet 10.255.255.10/32 scope global lo.master
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 08:00:27:b2:4a:fe brd ff:ff:ff:ff:ff:ff
inet 192.168.10.254/24 brd 192.168.10.255 scope global eth0.primary
valid_lft forever preferred_lft forever
inet 192.168.100.254/24 brd 192.168.100.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:feb2:4afe/64 scope link
valid_lft forever preferred_lft forever
3.2 ICMP Echo (ping)
An ICMP echo (ping) message can be generated from the CRR-1000 router with the “ping” command,
e.g.:
admin@CRR> ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=255 time=1.48 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=255 time=0.722 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=255 time=0.667 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=255 time=0.724 ms
--- 192.168.100.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 0.667/0.899/1.484/0.339 ms
3.3 Logging Information
3.3.1 Security-Related Logging (show audit)
Audit logs contain information related to security events such as login attempts, service restarts, and
changes to the system that may have security implications. Audit logs are accessed with the “show audit”
command that takes as its single argument the corresponding audit log to be displayed. E.g.,
admin@CRR> show audit Tab
auth.log firewall.log general.log ipsec.log remote
3.3.2 Platform Logging (show log)
Platform-specific log information is accessed with the “show log” command that takes as its single
argument the corresponding platform-specific log file to be displayed. E.g.,
admin@CRR> show log Tab
kern.log local.log syslog user.log

CRR-1000 Quick Start Guide
4
3.4 View Route Information (show route)
Summary route information can be displayed with the “show route” command, e.g.,
admin@CRR> show route
default via 192.168.100.1 dev eth0
192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.254
192.168.100.0/24 dev eth0 proto kernel scope link src 192.168.100.254
The “show route” command is equivalent to the Linux “ip route show” command. Reading the output of
the command shown above, the first line indicates a default route (next hop) of 192.168.100.1 on eth0; the
second line indicates the local connection to 192.168.10.0/24 through eth0, and the third line indicates
reachability to 192.168.100.0/24 also through eth0.
3.5 Configuration Backup (backup save/restore)
CRR-1000 configurations can be saved locally, and saved configurations can similarly be restored. The
backup/store feature allows administrators to switch between candidate configurations.
The current configuration can be saved with the “backup save” command, e.g.,
admin@CRR> backup save <backup-name>
Example:
admin@CRR> backup save blue
This will save a backup of the current configuration under the name “blue”.
A previously saved configuration can be restored using the “backup restore” command, e.g.,
admin@CRR> backup restore <backup-name>
Example:
admin@CRR> backup restore blue
Refer to the user guide for additional backup options including saving configurations off of the router.
3.6 Packet Inspection (net dump)
To inspect packets transiting the router interfaces, use the “net dump” command, e.g.,
admin@CRR> net dump <interface> <protocol>
Example:
admin@CRR> net dump eth0 17
The above prints out all UDP (IP protocol 17) packets transiting eth0.
4Firewall Configuration
Built on top of Linux iptables function, the CRR-1000 firewall employs the concept of input, forward,
and output chains. Briefly, input chains apply to traffic that is destined for an interface on the the CRR-
1000, forward chains apply to traffic that is forwarded by the router (i.e., traffic that is routed), and output
chains apply to traffic that originates from the CRR-1000.
In its default, “out of the box” configuration, the CRR-1000’s firewall allows all output and forward
traffic. By default, the CRR-1000 blocks most input traffic with the notable exceptions of SSH and ping.

CRR-1000 Quick Start Guide
5
Important Note: The default firewall policy is configured to make it easy for users to access the router
over SSH, test its features, and experiment with configuration when used for the first time. For
deployment scenarios, we highly recommend changing the filter policies to DENY for all chains and
allowing network traffic to/from known destination/sources only if possible for maximum security. The
suitable configuration for a specific scenario depends on the use case.
4.1 Viewing the Firewall Policy (show filter policy)
The current firewall policy can be viewed by entering the following CLI command:
admin@CRR> show filter policy
Firewall Mode: Router
Current Policy Settings
INPUT -DENY
OUTPUT -ALLOW
FORWARD –ALLOW
4.2 Setting the Firewall Policy (set filter policy)
To change the firewall policy, use the “set filter policy” command, e.g.,
crr@CRR> set filter policy <input/output/forward> <allow/deny>
Example:
crr@CRR> set filter policy forward deny
User root attempting to restart service firewall-post
firewall-post restart successful
4.3 Advanced Firewall Rules
Best security practices dictate that firewalls only allow input, output and forward traffic that is explicitly
defined and to deny all other traffic. The following CLI command is used to specifically configure the
firewall rules:
admin@CRR> configure filter
A text editor will open and the firewall rules can be modified. The firewall is implemented through the
use of IPtables and follows the standard rule specification format where all firewall rules are saved into
the file. Refer to the user guide for more information.
5Network and Routing Protocol Configuration Examples
CRR supports many standards routing protocols as well as numerous proprietary protocols and network
functions. There are two services running on CRR that responsible for configuring such protocols and
functions. The first is FRR service which supports the standard routing protocols such as OSPF, PIM,
BGP, RIP, NHRP, etc. The second is ARES service which supports OSPF and PIM protocols as well as
proprietary protocols such ATCorp’s link sensing, automatic tunneling, and Cut-through routing. The
VPN configuration is also handled by ARES using the VPN Gateway plugin, refer to CRR user guide for
information about the VPN configuration.
It is important to note that in general you have to pick FRR or ARES to configure a certain link and not
configure the same link using both services. Otherwise there is a risk of creating link configuration
conflicts resulting in undesirable behavior. The default CRR configuration is all done using the ARES
service. If you wish to use FRR for configuration instead, please remove all link configuration from
ARES first.

CRR-1000 Quick Start Guide
6
5.1 FRR Configuration
FRR service uses the open source Free Range Routing project which supports Cisco’s IOS-like CLI to
configure the router. Depending on the CRR firmware version used and its corresponding FRR version,
online FRR documentation available at http://docs.frrouting.org/ covers all configuration options in
details. To check which FRR version is running use the following command:
admin@CRR> show version frr
FRRouting 7.3-ATC (CRR).
To start configuring links and routing protocols using FRR’s Cisco-like CLI shell use the following
command:
admin@CRR> configure frr
Hello, this is FRRouting (version 7.3-ATC).
Copyright 1996-2005 Kunihiro Ishiguro, et al.
CRR#
FRR’s shell is similar to the CRR top level CLI shell supporting TAB-complete for possible valid
completions of the partially entered command and also support for “?” to show help in the current CLI
context.
CRR# ? <HELP>
add Add registration
clear Reset functions
configure Configuration from vty interface
copy Copy from one file to another
debug Debugging functions
disable Turn off privileged mode command
enable Turn on privileged mode command
end End current mode and change to enable mode
exit Exit current mode and down to previous mode
find Find CLI command containing text
list Print command list
mtrace Multicast trace route to multicast source
no Negate a command or set its defaults
output Direct vtysh output to file
ping Send echo messages
quit Exit current mode and down to previous mode
rpki Control rpki specific settings
show Show running system information
terminal Set terminal line parameters
traceroute Trace route to destination
write Write running configuration to memory, network, or
terminal
To star the configuration you have to enter the configure mode by typing “configure terminal”. Here is a
full example to configure the IP address 10.1.2.3/24 on interface eth0 with TAB-complete and “?” for
demonstration purposes:
CRR# configure terminal
CRR(config)# ? <HELP>
access-list Add an access list entry
agentx SNMP AgentX protocol settings
allow-external-route-update Allow FRR routes to be overwritten by
external processes
banner Set banner
bfd Configure BFD peers

CRR-1000 Quick Start Guide
7
bgp BGP information
debug Debugging functions
domainname Set system's domain name
dump Dump packet
enable Modify enable password parameters
end End current mode and change to enable
mode
exit Exit current mode and down to previous
mode
find Find CLI command containing text
fpm fpm connection remote ip and port
frr FRRouting global parameters
hostname Set system's network name
interface Select an interface to configure
ip IP information
ipv6 IPv6 information
key Authentication key management
l2vpn Configure l2vpn commands
line Configure a terminal line
list Print command list
log Logging control
log-filter Filter Logs
mac Add a mac access-list
mpls Global MPLS configuration subcommands
nexthop-group Nexthop Group configuration
nhrp Next Hop Resolution Protocol functions
no Negate a command or set its defaults
output Direct vtysh output to file
password Modify the terminal connection password
pbr Policy Based Routing
pbr-map Create pbr-map or enter pbr-map command
mode
pseudowire Static pseudowire configuration
quit Exit current mode and down to previous
mode
route-map Create route-map or enter route-map
command mode
router Enable a routing process
router-id Manually set the router-id
rpki Enable rpki and enter rpki configuration
mode
service Set up miscellaneous service
terminal Set terminal line parameters
username
vni VNI corresponding to the DEFAULT VRF
vrf Select a VRF to configure
vrrp Virtual Router Redundancy Protocol
zebra Zebra information
CRR(config)#
CRR(config)# interface e Tab
IFNAME Interface's name
eth3 eth2 eth1 eth0
CRR(config)# interface eth0
CRR(config-if)# ? <HELP>

CRR-1000 Quick Start Guide
8
babel Babel interface commands
bandwidth Set bandwidth informational parameter
delay Specify interface throughput delay
description Interface specific description
eigrp EIGRP information
end End current mode and change to enable mode
exit Exit current mode and down to previous mode
find Find CLI command containing text
ip IP information
ipv6 IPv6 information
isis IS-IS routing protocol
link-detect Enable link detection on interface
link-params Configure interface link parameters
list Print command list
multicast Set multicast flag to interface
no Negate a command or set its defaults
openfabric OpenFabric routing protocol
output Direct vtysh output to file
pbr-policy Policy to use
quit Exit current mode and down to previous mode
shutdown Shutdown the selected interface
tunnel NHRP/GRE integration
vrrp Virtual Router Redundancy Protocol
CRR(config-if)# ip Tab
address Set the IP address of an interface
authentication Authentication subcommands
hello-interval Configures EIGRP hello interval
hold-time Configures EIGRP IPv4 hold time
igmp Enable IGMP operation
irdp Alter ICMP Router discovery preference on this
interface
mroute Add multicast route
multicast Generic multicast configuration options
nhrp Next Hop Resolution Protocol functions
ospf OSPF interface commands
pim PIM information
rip Routing Information Protocol
router IP router interface commands
summary-address Perform address summarization
CRR(config-if)# ip address Tab
A.B.C.D Local IP (e.g. 10.0.0.1) for P-t-P address
A.B.C.D/M IP address (e.g. 10.0.0.1/8)
CRR(config-if)# ip address 10.1.2.3/24
CRR(config-if)# exit
CRR(config)# exit
CRR#
To leave the FRR CLI shell and go back to the main CRR CLI shell enter the command:
CRR# exit
crr@CRR>
5.2 ARES Configuration
ARES service configuration is handled by editing JSON-formatted files that are syntactically verified and
processed by the system. For further information regarding JSON syntax, see https://www.json.org/

CRR-1000 Quick Start Guide
9
Figure 1, below, provides an overview of the JSON schema used by the CRR-1000.
An online, traversable version of the ARES schema can be found at:
https://www.atcorp.com/docs/crr-1000/aresprod.html
The elements in bold, such as RouterId,are required. Objects are enclosed in curly braces, and arrays are
enclosed in square brackets. Commas are required after all elements except the final element in an object
or array. Valid ARES configuration options and syntax can be found at:
https://www.atcorp.com/docs/crr-1000/
A nano-style text editor (https://www.nano-editor.org/) is invoked by the following CLI command:
admin@CRR> configure ares
Note that when exiting the editor, a syntax check is performed. Syntax errors are displayed to the user,
and the configuration file cannot be saved until they have been corrected. The most common types of
errors are missing commas, quotes, or brackets.
Configuration of the CRR-1000 begins with identifying the hardware addresses of the physical interfaces.
To view the hardware addresses of the physical interfaces connected to the router use the “show ip”
command described in Section 3.1.
In the following example, the hardware address returned by “show ip” is indicated by bold type, i.e.,
08:00:27:b2:4a:fe.
admin@CRR> show ip
<loopback interface details omitted for brevity>

CRR-1000 Quick Start Guide
10
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 08:00:27:b2:4a:fe brd ff:ff:ff:ff:ff:ff
inet 192.168.10.254/24 brd 192.168.10.255 scope global eth0.primary
valid_lft forever preferred_lft forever
Write down (or otherwise record) the hardware address of each physical interface of your CRR-1000;
they’ll be needed later.
5.2.1 Simple Network: One Router, Two Subnets
This example shows the configuration that enables static routing between two subnets; the associated
network topology is provided by the following diagram.
The corresponding configuration file is shown below. You’ll need to replace the xx:xx:xx:xx:xx:xx
hardware addresses shown below with the hardware addresses of your router (described previously).
{
"RouterId" : 10,
"Links" : [
{
"Name" : "subnetA",
"Type" : "Simple",
"Interface" : {
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.10.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "subnetB",
"Type" : "Simple",
"Interface" : {
"Name" : "eth1",
"Inet4Addresses" : [ "192.168.100.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
}
]
}
The above configuration is a single JSON object and is thus enclosed in curly braces.
The second line of the configuration file specifies the RouterId –a required entry with valid values of 2-
254. For simplicity, set your RouterId to 10; its use is discussed further in advanced routing examples.
The “Links” section defines IP addresses and corresponding interface names and hardware addresses.

CRR-1000 Quick Start Guide
11
5.2.2 Static Routing: Two Routers, Three Subnets
The CRR-1000s in this example use static routes and require the hardware addresses of the physical
interfaces, as in the previous example.
The configuration necessary for CRRAis similar to the previous exercise, except static routes will be set
up on each router to route traffic. Note in the following configuration files each router has a uniquerouter
ID.
Enter the following CLI command to edit the configuration file on each machine:
admin@CRR > configure ares
Configuration for CRRA:
{
"RouterId" : 10,
"Links" : [
{
"Name" : "subnetA",
"Type" : "Simple",
"Interface" : {
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.10.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "subnetB",
"Type" : "Simple",
"Interface" : {
"Name" : "eth1",
"Inet4Addresses" : [ "192.168.100.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
},
"Routes" : [ {"Network" : "Default4", "Via" : "192.168.100.253"} ]
}
]
}
Configuration for CRRB:
{
"RouterId" : 20,
"Links" : [
{
"Name" : "subnetB",

CRR-1000 Quick Start Guide
12
"Type" : "Simple",
"Interface" : {
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.100.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
},
"Routes" : [ {"Network" : "Default4", "Via" : "192.168.100.254"} ]
},
{
"Name" : "subnetC",
"Type" : "Simple",
"Interface" : {
"Name" : "eth1",
"Inet4Addresses" : [ "192.168.200.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
}
]
}
The changes to these configuration files set up a static route through the other CRR.
5.2.3 Dynamic Routing: Two Routers, Four Subnets
The picture below shows two CRR-1000 routers and two networks between them. In the previous
examples, the link type was configured as Simple for all links, but in this exercise the links between the
two CRRs are of type Core. Core links perform OSPF, Neighbor Discovery and Link Quality control.
Core links are only meaningful between CRRs since the Link Quality and Neighbor Discovery protocols
are unique to ARES. This exercise can be performed with Boundary links instead of Core links, in case
OSPF link sensing is not needed. Boundary links would be used, for instance, when the CRR is peering
with a non-ARES router and performing OSPF.
Enter the following CLI command on CRRAand CRRBto edit the configuration:
admin@CRR prompt> configure ares
Configuration for CRRA:
{
"RouterId" : 10,
"Links" : [
{
"Name" : "subnetA",
"Type" : "Simple",
"Interface" : {

CRR-1000 Quick Start Guide
13
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.10.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "SubnetB",
"Type" : "Core",
"Interface" : {
"Name" : "eth1",
"Inet4Addresses" : [ "192.168.100.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "SubnetD",
"Type" : "Core",
"Interface" : {
"Name" : "eth2",
"Inet4Addresses" : [ "192.168.150.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
}
]
}
Configuration for CRRB:
{
"RouterId" : 20,
"Links" : [
{
"Name" : "subnetB",
"Type" : "Core",
"Interface" : {
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.100.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : “SubnetC",
"Type" : "Simple",
"Interface" : {
"Name" : "eth1",
"Inet4Addresses" : [ "192.168.200.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "SubnetD",
"Type" : "Core",
"Interface" : {
"Name" : "eth2",
"Inet4Addresses" : [ "192.168.150.253/24" ],

CRR-1000 Quick Start Guide
14
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
}
]
}
5.2.4 Bootstrap Router Example
The Bootstrap Router is an important concept to understand when using ARES. ARES performs
neighbor discovery of other CRR-1000s via multicast. When the network link between two CRR-1000s
does not support multicast, such as certain IP radios, a Bootstrap Router is required.
In the following example the two routers are connected through an ANW2 radio network. The ANW2
radios are not configured to pass the ARES neighbor discovery multicast packets thhus a BootStrap
Router is required. The two routers are also on different subnets behind the ANW2 radios therefore a
virtual network is configured by using a Routable Address. Finally, the Next Hop is configured to be the
IP address of the radio connected to the router in order to route traffic across the ANW2 network.
Configuration for CRRA:
{
"RouterId" : 10,
"Links" : [
{
"Name" : "subnetA",
"Type" : "Simple",
"Interface" : {
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.10.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "subnetB",
"Type" : "Core",
"Interface" : {
"Name" : "eth1",

CRR-1000 Quick Start Guide
15
"Inet4Addresses" : [ "192.168.100.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "subnetRadio",
"Type" : "Core",
"Interface" : {
"Name" : "eth2",
"Inet4Addresses" : [ "192.168.50.254/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx",
"RoutableAddress": "10.0.200.50/24"
},
"NextHop": "192.168.50.1",
"NeighborDiscovery": {
"BootstrapRouter": "192.168.50.254",
"TTL": 6
}
}
]
}
Configuration for CRRB:
{
"RouterId" : 20,
"Links" : [
{
"Name" : "subnetC",
"Type" : "Simple",
"Interface" : {
"Name" : "eth0",
"Inet4Addresses" : [ "192.168.200.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : “subnetB",
"Type" : "Core",
"Interface" : {
"Name" : "eth1",
"Inet4Addresses" : [ "192.168.100.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx"
}
},
{
"Name" : "subnetRadio",
"Type" : "Core",
"Interface" : {
"Name" : "eth2",
"Inet4Addresses" : [ "192.168.51.253/24" ],
"HardwareAddress" : "xx:xx:xx:xx:xx:xx",
"RoutableAddress": "10.0.200.51/24"
},
"NextHop": “192.168.51.1",

CRR-1000 Quick Start Guide
16
"NeighborDiscovery": {
"BootstrapRouter": “192.168.50.254",
"TTL": 6
}
}
]
}
5.2.5 Basic Verification and Troubleshooting
For debugging purposes it can be very informative to view the status of the router’s links to verify they
are configured correctly and in an Up state. To view the status of the router’s links enter the following
CLI command:
admin@CRR> show ares links
** Network Master: 10.255.255.10
** 2 links
** -------------- subnetA --------------
** Up Time: 105866s
** Interface: eth0 (08:00:27:b2:4a:fe) <UP>
** Inet P:192.168.10.254/24
** Inet6
** Simple Link
** -------------- subnetB --------------
** Up Time: 438203s
** Interface: eth1 (08:00:27:b2:4a:ff) <UP>
** Inet P:192.168.100.254/24
** Inet6
** Simple Link