[OOR-Users] Configuration Help

[Josh Rabidue]

This is the error I am receiving:

 [2018/1/21 2:49:50] INFO: Control created!
/etc/oor.conf:107: unexpected token '198.6.255.37'
[2018/1/21 2:49:50] CRIT: Parse error in file /etc/oor.conf, exiting. Check
conf                file (see oor.conf.example)
[2018/1/21 2:49:50] INFO: Exiting ...


Here is my configuration:

# General configuration
#
# debug: Debug levels [0..3]
# map-request-retries: Additional Map-Requests to send per map cache miss
# log-file: Specifies log file used in daemon mode. If it is not specified,
#   messages are written in syslog file

debug                  = 0
map-request-retries    = 2
log-file               = /var/log/oor.log

# Define the type of LISP device LISPmob will operate as
#
# operating-mode can be any of:
# xTR, RTR, MN, MS
#
operating-mode         = xTR

# For the rest of this file you can delete the sections that does not apply
to
# the LISP device selected in operating-mode


################################################
#
# MS configuration
#
# Control messages are received and generated through this interface
# Only one interface is supported

control-iface = eth0

# Define an allowed lisp-site to be registered into the Map Server. Several
# lisp-site can be defined.
#
#   eid-prefix: Accepted EID prefix (IPvX/mask)
#   key-type: Only 1 supported (HMAC-SHA-1-96)
#   key: Password to authenticate the received Map-Registers
#   iid: Instance ID associated with the lisp site [0-16777215]
#   accept-more-specifics [true/false]: Accept more specific prefixes
#     with same authentication information

lisp-site {
    eid-prefix            = 153.16.29.128/28
    key-type              = 1
    key                   = 2QSX3mNAfV
    iid                   = 0
    accept-more-specifics = false
}

#     sent (seconds) [1..rloc-probe-interval]

rloc-probing {
    rloc-probe-interval             = 30
    rloc-probe-retries              = 2
    rloc-probe-retries-interval     = 5
}

# Encapsulated Map-Requests are sent to this Map-Resolver
# You can define several Map-Resolvers, seprated by comma. Encapsulated
# Map-Request messages will be sent to only one.
#   address: IPv4 or IPv6 address of the map-resolver

map-resolver        = { asp-mr-ms 198.6.255.37, cisco-sjc-mr-ms-1
173.36.254.164, eqx-ash-mr-ms 206.223.132.89}
PETR: 69.31.31.98, 129.250.1.63
}

Here is my allocation data:
Device name: cmich-xtr
Region: US-East
Geographic location: USA - New York
EID-prefix: 153.16.29.128/28 (more specifics allowed)
EID loopback: 153.16.29.129
EID-prefix ipv6: 2610:D0:1153::/48 (more specifics allowed)
EID loopback ipv6: 2610:D0:1153::153:16:29:129
Map Servers: {ARIN} {asp-mr-ms 198.6.255.37, cisco-sjc-mr-ms-1
173.36.254.164, eqx-ash-mr-ms 206.223.132.89}
Map Server password: 2QSX3mNAfV
Map Resolvers: {ARIN} {asp-mr-ms 198.6.255.37, cisco-sjc-mr-ms-1
173.36.254.164, eqx-ash-mr-ms 206.223.132.89}
PETR: 69.31.31.98, 129.250.1.63


I am making inefficient changes in the configuration. I am using a virtual
private server using interface "eth0" on a Debian OS. If Possible could
someone provide me with a configuration that works while putting comments
explaining what is going on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openoverlayrouter.org/pipermail/users/attachments/20180120/82cc663a/attachment.html>