There are two data formats; those collected from the Cisco and those from the Zebra routing software. For those unfamiliar with these systems, a description of their formats follows.
The data file intervals are as follows:
MRT RIB and UPDATE files have internal timestamps in the standard Unix format, however the file names are constructed based on the time zone setting of the collector. The collectors had their time zones set to Pacific Time prior to Feb 3, 2003 at approximately 19:00 UTC. At that time all but one of the existing collectors had their time zones reset to UTC. The one exception was routeviews.eqix which was not reset to UTC until Feb 1, 2006 at approximately 21:00 UTC.
half-life | (Optional) Time (in minutes) after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period (which is 15 minutes by default). The process of reducing the penalty happens every 5 seconds. The range of the half-life period is 1 to 45 minutes. The default is 15 minutes. |
reuse | (Optional) If the penalty for a flapping route decreases enough to fall below this value, the route is unsuppressed. The process of unsuppressing routes occurs at 10-second increments. The range of the reuse value is 1 to 20000; the default is 750. |
suppress | (Optional) A route is suppressed when its penalty exceeds this limit. The range is 1 to 20000; the default is 2000. |
max-suppress-time | (Optional) Maximum time (in minutes) a route can be suppressed. The range is 1 to 20000; the default is 4 times the half-life. If the half-life value is allowed to default, the maximum suppress time defaults to 60 minutes. |
Zebra -
Zebra has a mechanism to dump BGP data built-in. It can dump it's BGP RIB,
the full BGP data stream of each peer, and various state information. The
format of these is called MRT format.
The most popular tool to extract the contents is route_btoa. route_bota
reads the MRT data and dumps it in ASCII (text). There are two forms,
described below.
The default format, often call human readable, displays a paragraph for each
MRT record. All records include the time it was recorded and it's type. The
remaining fields vary depending upon the type of record.
In the example below, the remaining fields are the attributes from a single
BGP update message.
The second format is called machine readable. The same fields are present,
but they are separated by a "|" (bar or pipe character), abbreviated in some
cases, and occupy a single line. Since BGP update messages can carry
multiple withdrawn ("unfeasible") and announced (NLRIs), a single message may
produce to multiple lines.
All records include the fields:
TIME: 05/09/03 04:01:59
TYPE: BGP4MP/MESSAGE/Update
FROM: 198.58.5.254 AS3727
TO: 198.58.5.34 AS3936
ORIGIN: IGP
ASPATH: 3727 2914 6730 8640
NEXT_HOP: 198.58.5.254
ATOMIC_AGGREGATE
AGGREGATOR: AS8640 195.141.213.58
COMMUNITY: 2914:420 2914:2000 2914:3000 3727:380
ANNOUNCE
195.28.224.0/19
BGP protocol|unix time in seconds|Withdraw or Announce|PeerIP|PeerAS|Prefix|
For withdrawn routes, the fields are:
BGP protocol|unix time in seconds|Withdraw or Announce|PeerIP|PeerAS|Prefix
For announcements, the fields are:
BGP protocol|unix time in seconds|Withdraw or Announce|PeerIP|PeerAS|Prefix|AS_PATH|Origin|Next_Hop|Local_Pref|MED|Community|AtomicAGG|AGGREGATOR|
BGP4MP|1052452930|W|198.58.5.254|3727|194.127.245.0/24
BGP4MP|1052452919|A|198.58.5.254|3727|195.28.224.0/19|3727 2914 6730 8640|IGP|198.58.5.254|0|0|2914:420 2914:2000 2914:3000 3727:380|AG|195.141.213.58|
12 Nov 2003
help@routeviews.org