ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000 Panduan Memulai Cepat - Halaman 14

Jelajahi secara online atau unduh pdf Panduan Memulai Cepat untuk Router Nirkabel ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000. ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000 18 halaman.

Halaman Cetak
CRR-1000 Quick Start Guide
"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 CRR
admin@CRR prompt> configure ares
Configuration for CRR
{
"RouterId" : 10,
"Links" : [
{
"Name" : "subnetA",
"Type" : "Simple",
"Interface" : {
and CRR
A
:
A
to edit the configuration:
B
12