ramd.conf(4) Kernel Interfaces Manual ramd.conf(4)
NAME
ramd.conf - Route Administration Manager Daemon (RAMD) configuration file
SYNOPSIS
DESCRIPTION
is the configuration file for the Route Administration Manager daemon (RAMD) for IPv6. This file comprises of configuration statements
that configures and
and are referred to as routing daemons. Upon startup, the daemons read this configuration file. This file contains:
o interface configuration statements,
o protocol configuration statements,
o static route configuration statements,
o control configuration statements, and
o aggregate configuration statements.
Configuring RAMD
The RAMD configuration file, consists of a set of configuration statements that terminate with a semi-colon
These configuration statements are composed of tokens separated by white space. This structure simplifies the identification of parts of
the configuration associated with each other and with specific protocols. Comments can be specified with a pound sign at the beginning of
the line. The syntax conventions specific to the configuration file are:
Highlighting indicates keywords and special characters that the parser expects.
underline Underlining (or italic) indicates a parameters whose value can be specified.
Parameters shown in square brackets
indicate optional keywords and parameters.
The vertical bar
indicates a choice between parameters.
Parentheses group keywords and parameters.
For example, consider the following syntax description:
seconds]
The square brackets indicate that the parameter is optional. The keywords in the example configuration statement are and The vertical bar
indicates a choice between and The underline (or italic font) seconds indicates that a value must be specified.
RAMD Configuration Statement Summary
The file is divided into global section and routing protocol section. The configuration statements for the global section are given below:
Defines the autonomous system (AS) number.
Defines the originating router (BGP).
Configures kernel interface options.
Specifies the preference order of routes
to the same destination.
Configures specific interface attributes.
Specifies events to be traced.
Specifies the processing of redirect requests.
Specifies invalid destination addresses.
Configures route filtering.
Defines static routes.
Specifies routes to be imported.
Specifies routes to be exported.
RAMD Global Configuration
The sets the autonomous system number of this router to be autonomous system. This option is required if BGP is in use. The AS number is
assigned by the Network Information Center (NIC).
The syntax of the configuration statement is as follows:
This autonomous system appears only once in an AS path.
Router ID Statement
The sets the router identifier for use by the BGP protocol. This number uniquely identifies the router within the autonomous system.
The syntax of the configuration statement is as follows:
The routerid value can be an IP address of an interface or unique number. It is mandatory if BGP is configured.
Kernel Statement
The configuration statement specifies the kernel interface options that controls the retrieval of the interface and the route tables from
the kernel. Only one configuration statement can be specified in the configuration file.
The syntax of the configuration statement is as follows:
where the following means:
supports enterprise-specific Management Information Base (MIB) based on
Community-based Simple Network Management Protocol version 2 (SNMPv2C). implements EMANATE subagent.
The configuration statement lets enable or disable SNMP support.
After starting if is specified in the configuration file, registers with the SNMP master agent, snmpdm(1M). subagent accepts:
retrieves classes of variables from the MIB,
sets the value of a variable on a MIB, and
retrieves one value of the variable from the MIB operations.
By default, support is disabled; in other words, state is
Specifies the interface scan interval in seconds.
This value specifies how often scans the kernel interface table to identify the modifications. The default value is 15 seconds.
Configures polling of kernel routing table.
polls the kernel routing table, periodically.
disables
polling of the kernel routing table.
By default, route polling is disabled.
Specifies how often the kernel routing table is scanned
for modifications. The default poll interval is 30 seconds.
By default, route polling is disabled.
Specifies the duration, in minutes,
for which retains the remnant routes (routes retrieved from the kernel upon startup) in its routing table. On remnant hold timeout,
deletes all IPv6 routes except Static, Direct and Mobile IPv6 routes. By default, remnant hold time is 3 minutes. The time inter-
val can be in the range of 0-15 minutes.
Specifies that
does not delete the routes from the kernel when it exits. By default, deletes the routes from the kernel when it exits.
Specifies the events to be traced. The specified option should be separated by
commas, without any spaces between them. The valid trace options are:
Traces the list of interfaces retrieved from the kernel
interface table.
Traces the route add and delete request by
to modify the kernel routing table.
Traces the application of route filters and martian routes.
Traces the functions and their arguments.
Traces the timer events.
Traces the events without time stamp information.
Traces and information.
No tracing is done.
By default, no tracing is done.
file-size
filename Specifies the name of the trace file.
Replaces an existing trace file and the tracing starts at the
beginning of the trace file. By default, trace information is appended to the existing trace file.
Specifies the maximum size of the trace file.
The minimum size remains 10k. The default trace file size remains 10k.
Represents the size of the file in Kilobyte or Megabyte.
Specifies the maximum files.
When the trace file reaches the specified size, the files are renamed as up to the value specified in the option. The
minimum value for files remain 2.
Traces all options, except the options that you specify in this statement.
This configuration statement can be used in the and configuration section.
Preference
The preference value is an arbitrarily assigned value used to determine the order of routes to the same destination in a single routing
database. Preference is the value that uses to order the preference of routes from one protocol or peer to another. The preference value
can be set in the RAMD configuration file in different configuration statements. It can be specified in the interface configuration state-
ment to prefer one interface over the other. The preference can also be configured for the protocol.
The preference is not used to control the selection of routes within an Interior Gateway Protocol. This is accomplished automatically by
the protocol based on the metric value. Each route has only one preference value associated with it, even though the preferences can be
set at many places in the configuration file. The last or the most specific preference value set for a route is the value used. The route
with smallest preference value is the active route.
The best route is selected as follows:
1. The route with the best (numerically smallest) preference is selected.
2. If the routes are from the same protocol, the one with the lowest metric is selected.
3. If the routes have the same metric value, the route with the lowest numeric next hop address is selected.
Assigning Preferences
RAMD assigns a default preference to each source from which it receives routes. The preference values range from 0 - 255, with the lowest
number indicating the most preferred route.
The default preference values for different types of routes are:
Direct route
IS-IS route
Static route
RIPng route
BGP route
The syntax of the configuration statement is:
This configuration statement assigns preference values for routes learned from routing protocols.
Interface Configuration Statement
The interface configuration statement configures the primary address and the preference for an interface.
The syntax of the configuration statement is:
where the following means:
Sets the preference for routes to this interface when the interface is up.
The default preference is 0.
Specifies a primary address for this interface.
It overrides the address that determines to be primary.
Specifies the address that
installs as the next hop for interface routes, when multiple addresses are assigned to an interface like the ServiceGuard environ-
ment.
Replaces the next hop address with the primary address for all the
direct routes of an interface.
Replaces the next hop address with the lowest IPv6 address for all the
direct routes of an interface.
does not modify any direct routes for this interface.
The daemon does all the route modification in its routing table.
ICMPv6 Redirect Message Processing
processes the ICMPv6 redirect request and decides whether to accept the redirect. If the redirect is accepted, installs a route in its
routing table with the protocol as redirect. deletes the redirect routes from its routing table after 3 minutes.
If is configured to reject redirects, that is if option is specified in the configuration statement, it checks whether the kernel routing
table is modified by the redirect message. If the kernel routing table is modified, deletes the redirect route and restores the previous
route that was modified by the redirect message. By default, ignores the redirect messages. handles the redirect message only when the
configuration statement is specified in the configuration file.
The configuration statement does not prevent the system from sending redirects, but only from listening to them.
The syntax of the configuration statement is:
where the following means:
Specifies the preference value for the redirect routes.
By default, preference value is 30.
Specifies the list of interfaces through which
receives the redirect message.
Specifies
to ignore the redirect message received through this interface.
Specifies the list of gateways from which
has to accept redirect message. If this configuration statement is specified, ignores the redirect message from a gateway which is
not specified in this list of gateways. By default, accepts redirect message from all the directly connected gateways on the shared
network.
Martians Configuration Statement
Martians configuration statement specifies a list of invalid addresses and all routing information from these addresses is ignored. A mis-
configured system sends out invalid destination addresses. These invalid addresses are called martians. The daemon rejects these invalid
addresses.
The syntax of the configuration statement is:
This configuration statement allows additions to the list of martian addresses. See the section below for more information on specifying
ranges. Specify the option to explicitly allow a subset of a range that was disallowed. The configuration file accepts only one configu-
ration statement.
Route Filter Configuration Statement
The route filter configuration statement specifies a method to group list of network and host addresses. The RAMD configuration file con-
figures route filtering.
A definition can have multiple hosts and prefixes listed.
This route filter can be specified in and configuration statements and are referred by names.
The syntax of the configuration statement is:
where the following means:
filter-name
Specifies the unique name of the filter. filter-name must be a string and the length must not exceed 32 characters.
prefix specifies the destination network address, and prefixlength specifies the valid number of bits in the destination network
address.
Specifies the host to configure and the destination host address.
Specifies to filter all the valid IPv6 address.
Static Configuration Statement
The static configuration statement defines the static routes that are added to the kernel routing table, when starts. The configuration
statement accepts multiple static routes. Dynamic routes with better preference can override static routes.
The syntax of the configuration statement is:
where the following means:
Specifies that the type of route is a host route.
Specifies that the static route prefix is 0 and the prefix length is 0.
Specifies that the type of route is a network route.
prefix Specified the destination network address.
prefixlen Specifies the valid number of bits in the network address. For a net route, the value is between 1 and 127.
Specifies that the gateway address can be used to reach the host or
network. Alternatively, the interface name can be specified using the interface option. A gateway address or an interface
name must be specified.
Specifies the name of the interface through which the static route is reachable.
Specifies the metric with which the route is added to
the kernel. If the next hop is not directly reachable, the metric value must be greater than 1.
Specifies that does not delete this route when exits.
Specifies the preference of this route.
This overrides the global preference of static routes. The default preference is the value specified in the configuration
statement.
Import Configuration Statement
The import configuration statement control importing of routes from the routing protocols and installing them in the RAMD routing database
and kernel routing table. The import configuration statement specifies whether to update the kernel routing table or not for a protocol.
By default, installs and routes in the kernel routing table.
The syntax of the configuration statement is:
where the following means:
Installs static routes in the kernel routing table.
Installs RIPng routes in the kernel routing table.
Installs BGP routes in the kernel routing table.
Install static, RIPng and BGP routes in the kernel
routing table.
route-filter-name Specifies the route filter associated with this import policy.
Specifies that these routes provided in the route filter must be
installed in the routing table.
Specifies that these routes must not be installed in the routing table.
These routes are not exported to other protocols.
By default, the routing daemons import routes to the daemon. The daemon installs the best route in the kernel routing table.
Export Configuration Statement
The export configuration statement controls the routes that advertises to other protocols. The main difference between export and import
is that route import is controlled by source information, while route exportation is controlled by both source and destination.
The syntax of the configuration statement is:
The protocols specified before the keyword are the source protocols and
The protocols specified after the keyword are the destination protocols (daemon-name, and where daemon-name can be or
Exports direct routes to the destination protocol.
Exports static routes to the destination protocol.
Exports RIPng routes to the destination protocol.
Exports BGP routes to the destination protocol.
Export direct, static, RIPng and BGP routes to the
destination protocol.
Exports no routes to the destination protocol.
daemon-name Exports routes from the source protocols to daemon-name.
Exports routes from the source protocols to all daemons.
Exports no routes from the source protocol.
Indicates the metric value to be used for exporting these routes
to the destination.
route-filter-name Indicates the route filter associated with this export policy.
Exports only these routes to the destination protocol.
Specifies that doe not export these routes to the destination protocol.
RIPNG SECTION OF THE CONFIGURATION FILE
This section describes the RIPng statements in the RAMD configuration file.
RIPng Protocal Overview
The RIPng routing protocol is a distance vector protocol. It runs over the UDP layer. The key features of the RIPng protocol are as fol-
lows:
o RIPng routers sharing a common data link become neighbors for route exchange.
o RIPng routers exchange IPv6 reachability information in the RIPng route updates with neighbors.
o RIPng routers send the best route to RAMD to update the kernel routing table.
o RIPng routers run as a daemon process. RIPng protocol section of the RAMD configuration file, can be used to configure the RIPng dae-
mon.
is a Command Line Interface (CLI) utility that controls the operations of the RIPng daemon. The CLI utility, can be used to monitor the
RIPng information.
Enabling RIPng
The RAMD configuration file enables or disables the RIPng protocol. If the configuration statement is not specified in the configuration
file, by default, the value is Only one configuration statement can be specified in the configuration file. The syntax for is:
where the following means:
Enables or disables RIPng protocol.
By default, RIPng protocol is disabled.
Specifies the administrative status of the RIPng protocol.
By default, administrative status is up.
Enables or disables SNMP support in
When is specified, subagent registers with the snmpdm(1M) master agent and accesses the SNMP operations like and
supports enterprise-specific MIB based on SNMPv2C. implements EMANATE subagent.
By default, is
Using ram_monitor for RIPng
The RIPng routers can be monitored using The CLI port number can be specified in the RIPng section of the RAMD configuration file.
The syntax of the configuration statement is as follows:
This configuration statement specifies the TCP port number on which listens for connection. If the CLI port number is not specified, does
not service queries. Specify this CLI port number with to monitor RIPng routers.
Global Configuration Statement for RIPng
The configuration of global parameters for are explained below. These statements are defined in the RIPng section of the configuration
file.
Horizon Type
The statement in the RIPng section of the RAMD configuration file specifies the horizon type; e.g., the mode for RIPng routers to send
route updates.
The syntax of the configuration statement is as follows:
where:
Specifies that the horizon is split horizon.
The RIPng router does not send the routes learned from a peer to that peer. This is the value used when the RIPng router cre-
ates a default profile.
Specifies that the horizon is poison reverse.
The RIPng router sends the routes learned from a peer to that peer with metric set to infinity. By default, poison reverse is
enabled.
Propagation for RIPng
The propagate statement controls the propagation of static or dynamic RIPng routes to its peers. By default, both static and dynamic
routes are propagated.
The syntax of the configuration statement is as follows:
where:
Specifies that the RIPng router propagates only the dynamic routes.
Specifies that the RIPng router propagates both static and dynamic routes.
Propagation of Sitelocal Routes for RIPng
The sitelocal statement specifies if site-local address can be propagated to another system or not.
The syntax of the configuration statement is as follows:
where:
Specifies that propagation of site-local routes is allowed.
Specifies that the RIPng router must not propagate the site-local
routes.
Redistributed Routes for RIPng
The defaultmetric statement specifies the metric to be used when advertising routes through the RIPng protocol. This is applicable for the
routes learned from other protocols.
If no value is specified, the default value is 1. The metric specified in the export policy overrides this configuration.
The syntax of the configuration statement is as follows:
where metricvalue specifies the default metric value.
Maximum Routes for RIPng
The maxroutes statement specifies the maximum routes that a RIPng router can store in its routing table. By default, this is 30000.
The syntax of the configuration statement is as follows:
where numb-of-routes specifies the maximum routes that a RIPng router can store in its routing table.
Route Filtering Configuration for RIPng
The following statement is used to route filters.
The syntax of the configuration statement is as follows:
A route filter can have a combination of multiple host routes and multiple net routes. If configuration statement is specified, host and
net entries must not be specified. This route filter can be specified in the configuration statements. See the statement in the section.
Route Aggregation for RIPng
Route aggregation is the process of merging two or more routes to form a single route on the basis of matching bits in each route. It
reduces the number of routes in the RIPng route update message. The receiving RIPng neighbor router installs the aggregate route in the
kernel routing table. Hence, route aggregation reduces the number of routes in the kernel routing table.
The configuration statement can be used to generate aggregate routes. If this statement is not specified in the configuration file, RIPng
router does not perform route aggregation.
The syntax of the configuration statement is as follows:
[prefix prefixlength
where:
prefix prefixlength
Specifies the routes that can be aggregated and its prefix length.
Specifies the preference value of the aggregate route.
By default, the value is 130.
Specifies the route that
must not aggregate.
Profile Configuration for RIPng
The RIPng section provides a directive to configure a profile that can be used by the interfaces for configuration of the horizon, the
periodic update time, the triggered update delay time, the route age time, and the garbage collection time. By default, a profile is
available with poison reverse configured.
The syntax of the configuration statement is as follows:
where:
Specifies the horizon for this profile.
By default, horizon is poison reverse.
Specifies the periodic timeout interval after which
regular route updates are sent. By default, this is 30 seconds.
Specifies the interval by which the triggered update is
delayed. By default, this is 5 seconds.
Specifies the interval after which a route ages,
if there are no updates to this route. By default, this is 180 seconds.
Specifies the garbage collection time interval after which a route
must be purged from the routing table. By default, this is 120 seconds.
By default, a profile ID with "0" is created with configured values for the horizon type.
Tracing for RIPng
For RIPng, you can set tracing at protocol or event level.
The syntax of the configuration statement is as follows:
which specifies the events to be traced. The options should be separated by commas, without any spaces between them. The valid trace
options are:
Specifies to trace route events.
Specifies to trace application of protocol and
user-specified policy to routes being imported and exported.
Specifies to trace timer events.
Specifies to trace normal ( packet, timer events) protocol occurrences.
Specifies to trace normal and route events.
Specifies to trace RIPng packets in detail.
Specifies to trace only outgoing RIPng packets.
Specifies to trace only incoming RIPng packets.
Specifies to trace RIPng route request packets.
Specifies to trace RIPng route response packets.
Specifies to trace both RIPng route request and response packets.
Specifies that trace messages must not have the time stamp information.
Traces and information.
No tracing is done.
By default, no tracing is done.
Gateway Filters Configuration for RIPng
In the RIPng section of the RAMD configuration file, you can specify the gateway filter configuration that controls the transmission and
reception of RIPng updates.
These are the possible gateway specifications:
The trusted gateway list specifies the list of gateways that the RIPng router
can accept for its route updates, where gateway-list is a list of gateway addresses separated by space.
By default, RIPng router accepts route updates from all the gateways.
The source gateway list specifies a list of gateways that the RIPng
router can send for its route updates, where gateway-list is a list of gateway addresses separated by space.
By default, RIPng router sends route updates to all gateways.
Interface Configuration for RIPng
In the RIPng section of the RAMD configuration file, you can use the statement to specify RIPng related interface attribute configuration,
where interface-name denotes one of the kernel interface name.
The syntax of the configuration statement is as follows:
route-filter-name-list
where the following means:
Specifies that RIPng protocol is enabled on this interface.
Specifies that RIPng protocol is disabled on this interface.
By default, RIPng protocol is enabled on this interface.
Specifies the cost of this interface. By default, the RIPng router takes the
configuration statement value.
The RIPng section of the RAMD configuration file specifies the control of RIPng operation based on the direction.
where:
Specifies that RIPng packets received through this interface are ignored.
By default, it listens to RIPng packets on all non-loopback interfaces.
Specifies that
can process incoming updates. By default, this is enabled.
Specifies that RIPng packets are not sent on the specified interfaces.
By default, it sends RIPng packets on all interfaces.
Specifies that
can send updates. By default, this is enabled.
The statement associates a profile on a particular interface. If the profile id is not specified, a default profile (id 0) is used.
The syntax of the configuration statement is as follows:
where id specifies the profile ID on a particular interface. You can specilfy the list of route filters for a specific interface. If no
filter is configured, filter policies are not applied to the RIPng packets that are sent and received on this interface.
The syntax of the configuration statement is as follows:
route-filter-name-list
where the following means:
Specifies the direction to apply the filter.
route-filter-name-list
Specifies a space separated list of multiple route filters to associate with this filter.
Let allow or restrict route information that matches the route defined in the route filter. If the or option is not specified,
the default option is
Note: This configuration statement accepts only one filter statement per interface.
BGP SECTION OF THE CONFIGURATION FILE
The following describes the BGP section of the RAMD configuration file.
BGP Protocal Overview
BGP protocol runs over TCP. The key features of the BGP protocol are as follows:
o The BGP routing protocol uses the standard port number 179.
o The BGP routers exchange routing information with its peers. A peer in a different Autonomous System (AS) is in an external peer and
peer in the same AS is internal peer.
o The BGP routers use the path vector algorithm to select the best route for installation.
o The BGP protocol runs as a daemon process. The BGP daemon can be configured through the BGP protocol section of the RAMD configuration
file,
o The BGP routers send the best route to for updating the IPv6 kernel routing table.
o The BGP router enforces policy decisions on routes installed and advertised.
Enabling BGP
The RAMD configuration file is used to enable or disable the BGP protocol. If the BGP section is not specified in the configuration file,
by default, is
The syntax for enabling BGP is:
where the following means:
Enables or disables BGP protocol.
By default, BGP protocol is disabled.
Specifies the administrative status of the BGP protocol.
By default, administrative status is
Enables or disables SNMP support in
When is specified, subagent registers with the snmpdm(1M) master agent and accesses the SNMP operations like and supports enter-
prise-specific MIB based on SNMPv2C. implements EMANATE subagent. By default, is
Please note that and are mandatory parameters when BGP is
Using ram_monitor for BGP
can be used to monitor the BGP daemon. The BGP section in the RAMD configuration file provides a directive to specify the CLI port number.
listens for connection on port-number. If the CLI port number is not specified, does not provide CLI service.
Maximum Routes for BGP
The maxroutes statement configures the maximum routes that can store in its routing table.
The syntax of the configuration statement is as follows:
where numb-of-routes specifies the maximum routes that can store in its routing table. By default, this value is 5000.
Maximum Peers for BGP
The maxpeers statement configures the maximum peers that supports.
The syntax of the configuration statement is as follows:
where numb-of-peers pecifies the maximum peers that supports. By default, this value is 50.
Enabling Synchronization for BGP
The synchronization rule of BGP states that if an Autonomous System (AS), such as AS 1, passes traffic from one AS to another, BGP does not
advertise a route before all routers within the AS (AS 1) have learned about the routes through an Interior Gateway Protocol (IGP). The
BGP section in the RAMD configuration enables or disables synchronization of routes with IGP.
The syntax of the configuration statement is as follows:
where:
Enables synchronization.
Disables
synchronization. By default, synchronization is disabled.
Propagation of Non-BGP Routes
The propnon-bgp statement specify the control or propagation of non-bgp routes to external peer or both external and internal peers. By
default, propagates non-bgp routes to both external and internal peers.
The syntax of the configuration statement is as follows:
where:
Specifies propagation of non-bgp routes to external peers.
Specifies propagation of non-bgp routes to both external and internal peers.
Overlapping Routes for BGP
The overlap statement sets policy handling of overlapping routes. Route overlap occurs when receives a set of less and more specific
routes.
The syntax of the configuration statement is as follows:
where:
Specifies to install the less specific routes.
Specifies to install the more specific routes.
Specifies to install both less specific and more specific routes.
Route Filtering for BGP
For BGP, you can configure the update filter. applies this filter on incoming and outgoing update messages. There can be many configura-
tion statements. If no filter is configured, filter policies are not applied to the BGP packets.
The syntax of the configuration statement is as follows:
where:
Specifies the remote autonomous system (AS) number based on which
applies the filter.
prefix prefixlength
Specifies the route prefix based on which applies the filter.
Specifies the host routes on which
applies this filter.
Specifies to filter all routes.
Specifies the AS path list based on which
applies this filter.
Specifies the direction of update messages on which
applies this filter. The option applies the filter on incoming routes and the option applies the filter on outgoing
routes.
Specifies to allow or restrict the incoming or outgoing routes.
By default, allows all routes.
Route Aggregation for BGP
Route aggregation is the process of merging two or more routes to form a single route on the basis of matching bits in each route. It
reduces the number of routes in the BGP route update message. The receiving BGP neighbor router installs the aggregate route in the kernel
routing table. Hence, route aggregation reduces the number of routes in the kernel routing table. that generates aggregate routes do not
use the originated aggregate routes for packet forwarding.
The aggregate configuration statement can be used to generate aggregate routes. If the aggregate configuration statement is not specified
in the configuration file, does not perform route aggregation. Route aggregation is effective only when the configuration statement is
specified.
The syntax of the configuration statement is as follows:
[preference preference-value]
where:
prefix prefixlength
Specifies the routes that can be aggregated and its prefix length.
Specifies to advertise aggregated routes and more specific routes or advertise only aggregated routes.
Specifies the preference for the aggregated routes.
By default, this value is 130.
Specifies that must not aggregate with this route.
Local Preference (LP) for BGP
uses the configuration statement to set the preference value:
where preference-value specifies the default LP value.
The BGP section in the RAMD configuration file specifies the value for local preference attribute. uses the configuration to set prefer-
ence value based on autonomous system (AS) number, AS path or prefix. Routes with higher local preference value is preferred to those with
a low preference value. configuration statement overrides the configuration statement.
The syntax of the configuration statement is as follows:
[prefix prefixlength]
where:
Specifies the local preference value for the routes from the remote autonomous
system (AS). Applicable only for the direction.
prefix prefixlength Specifies the local preference value for the route prefix.
Specifies the local preference values for the AS path list.
Specifies the local preference value for the incoming or outgoing routes.
By default, specifies the local preference value for the incoming routes.
Specifies the value for local preference (LP).
Specifies that the local preference value must override or inherit the
LP value in the incoming updates. By default, this is
Multi Entry/Exit Discriminator (MED) for BGP
uses the configuration to set the metric value:
where metricvalue specifies the default metric value.
For BGP external peers, the metric value can be used to specify the preferred path to enter or exit in the same autonomous system (AS).
sends the specified metric value in its update messages. uses the statement to set metric value based on AS, AS path, route prefix, or
directions. uses Multi Entry or Exit Discriminator (MED) to convey the preferred path to an AS, where lower MED value is preferred over
higher MED value. By default, MED is disabled.
The syntax of the configuration statement is as follows:
[prefix prefixlength]
where the following means:
Specifies the MED value to assign for routes from the peer in the specified
autonomous system (AS).
prefix prefixlength Specifies the MED value for the route prefix.
Specifies the MED value if the update message contains the specified list
of AS numbers.
Specifies the MED value for the incoming or outgoing update messages.
By default, specifies the MED value for the incoming update messages.
Specifies the metric value for the MED.
Specifies that the MED value must override or inherit.
By default, the MED value is
uses the following configuration statement to configure MED comparison.
where:
Compares MED between the routes received from the same autonomous
system (AS). This is the default.
Compares MED between the routes received from the same or
different AS.
Tracing for BGP
You can use the BGP section in the configuration file to set BGP tracing at protocol or event level. By default, no tracing is done:
where trace-options specifies the events to be traced. The options are comma separated without any space between them. The valid trace
options are:
Disables tracing.
Enables all the trace options.
Specifies to trace route addition and deletion in the
routing table.
Specifies to trace application of protocol and user-specified policy to routes
imported, exported and advertised.
Traces timer events.
Traces at function level.
When enabled, traces every function, with entry, exit and important values used in the function.
Traces (packet, timer events) protocol occurrences. Specifies to trace and events.
Traces all BGP packets in detail.
Traces only outgoing BGP packets.
Traces only incoming BGP packets.
Traces BGP packets.
Traces BGP packets.
Traces BGP packets.
Traces BGP packets.
Traces all BGP protocol packets.
Specifies that trace messages must not have time stamp information.
Traces BGP state machine transitions.
By default, no tracing is done.
Peer Configuration for BGP
You can configure the peers of the system other than the peer group.
The syntax of the configuration statement is as follows:
This peer configuration can be specified inside the configuration or outside the configuration. The option enables the session with the
peer and option disables the session.
host-address Specifies the host address for the peer.
Specifies the interface name through which the peer is connected.
This is applicable and mandatory for peers with link local address only.
Specifies the remote autonomous system (AS) number of the peer.
Enables or disables authentication for a peer.
By default, authentication is disabled.
A MD5 password string must be specified with when it is enabled.
Specifies the default value in hold time to use when negotiating
the connection with the peer. By default, the hold time is 120 seconds.
Specifies the keep alive time value for the peer.
By default, the keep alive time is 40 seconds.
Specifies the minimum autonomous system (AS) origination interval for the peer.
By default, is 15 seconds.
Specifies the minimum route advertisement interval for the peer.
By default, the value is 30 seconds.
Specifies the address on the local end of the TCP connection with the peer.
Specifies whether peer up or down events are logged in
syslog(3C). By default, this value is
Specifies the multihop feature for a peer.
Multihop must be enabled for indirectly connected external peers. By default, is disabled.
Specifies whether the next hop address is its own address or third party
address in the update message for a peer. By default, is disabled.
Specifies the preference value for BGP routes learned from the peer.
Logs the warning messages in trace file of
when receiving questionable BGP updates such as duplicate routes and deletions of non-existing routes from the peer.
By default, is
Specifies that the aggregator ID in the aggregate attribute must be 0
instead of the router ID.
Specifies that keepalive is sent always, even when sending update packet
for a peer.
Specifies that the authentication field of the incoming packets to be 1 and
need not be checked. This configuration is ignored if authentication is enabled.
Specifies the hop limit for peer.
The maximum value of hoplimit is 255. By default, is 255.
Specifies the send buffer size in TCP socket for a specified peer.
By default, the buffer size is 65536.
Specifies the receive buffer size in TCP sockets for a specified peer.
By default, the buffer size is 65536.
Specifies to retain the routes learned from a peer even if the autonomous
system (AS) paths of the routes contain one of the exported AS numbers. By default, no routes are retained.
Specifies that no attempt must be made from this peer to establish TCP
connection with the BGP speaker. A BGP speaker is a router that sends, receives and processes BGP messages. The BGP
speaker must wait for the peer to initiate the connection. By default, all explicitly configured peers are active.
Specifies the AS number that the BGP speaker is representing to this peer.
Only if a BGP router contains a true BGP peer, configuration is valid.
Prevents routes with looped AS paths from advertising to
version 4 external peers.
Specifies the metric value to be used on all routes sent to this peer.
This overrides the and configuration.
Specifies the gateway to be used for the routes from this peer.
Group Configuration for BGP
The group statement is used to configure the peers of a system. A group consists of peers based on their type and autonomous system (AS).
The group configuration accepts multiple configuration statements.
The syntax of the configuration statement is as follows:
The group configuration accepts many groups, but each must possess a unique combination of type and peer autonomous system (AS).
Specifies that group members must be directly connected.
The group members must belong to the same AS. Routes received from external peer are by default advertised with the
received metric.
Specifies the external peers.
The peers must be directly connected unless multihop is enabled. By default, no metric is included in external advertise-
ments.
Specifies an internal group that runs in association of an interior
gateway protocol. Routes received from this group are advertised only when learns the route from the protocol specified in
the proto field.
Specifies an internal group that uses the routes of an interior protocol to
resolve next hop address. A type routing group propagates external routes between routers that are not directly connected.
It computes immediate next hop for these routes by using the BGP next hop.
Specifies an internal or external BGP router that implements a fixed policy.
Routes received from test peer is discarded. Routes are advertised to the test peer without applying any filter policy.
The BGP router allows connections only from configured peers. The configuration statement enables unconfigured peer connections from any
address in the specified range of network. All parameters for these peers must be configured in the group clause.
Allows peering with routers whose IP address are in the specified range.
Allows peering with all incoming connections.
Allows peering with specified hosts.
The clause configures an individual peer. Each peer inherits all parameters specified on a group as default.
where:
Specifies the peer address.
Specifies the administrative status of the peer.
The configuration statements specified in this peer configuration statement overrides the group configuration statements except for and
configuration statements. configuration overrides for external peer.
See the section for explanations on the rest of the group configuration statements.
Need info on if ifname {...}
IS-IS SECTION OF THE CONFIGURATION FILE
The following describes the IS-IS section of the RAMD configuration file.
IS-IS Protocal Overview
IS-IS is a link state interior gateway protocol (IGP), or Intra-Domain Routing Protocol, originally developed for routing ISO/CLNP (Inter-
national Organization for Standardization/Connectionless Network Protocol) packets. IS-IS of RAMD supports IPv6 Routing information
exchange. It transmits over data link layer. The key features of the IS-IS protocol are as follows:
o The IS-IS supports two-level routing hierarchy. Routing within an area is Level 1 routing and across areas is Level 2 routing.
o The IS-IS routers become neighbors if the hello packets contain information that meets the criteria for forming an adjacency. The crite-
ria differ depending on the type of media used. The main criteria are matching authentication, IS-type and Maximum Transmission Unit
(MTU) size.
o The IS-IS builds Link-State Packet (LSP) that communicates the reachability information to adjacent routers. Floods LSPs to all adjacent
neighbors except the interface on which they received the LSP. IS-IS uses Shortest Path Algorithm (SPF), also known as Djikstra algo-
rithm, to compute its routing table by selecting the best paths in the network. SPF runs individually for Level 1 and Level 2 database.
o The IS-IS runs as a daemon process. IS-IS can be configured using the IS-IS protocol section of the RAMD configuration file,
o The IS-IS routers provide the best path to for updating the kernel routing table.
Enabling IS-IS
The RAMD configuration file enables or disables the IS-IS protocol. If the IS-IS section is not specified in the configuration file, by
default, IS-IS is
where:
Enables or disables IS-IS protocol.
By default, IS-IS protocol is disabled.
Specifies the administrative status of the IS-IS protocol.
By default, administrative status is
Enables or disables SNMP support in
When is specified, subagent registers with the snmpdm(1M) master agent and accesses the SNMP operations like and supports enter-
prise-specific MIB based on SNMPv2C. implements EMANATE subagent. By default, is
Using ram_monitor for IS-IS
can be used to monitor IS-IS. CLI port number can be specified in the IS-IS section in the RAMD configuration file:
listens for connection. If the CLI port number is not specified, does not provide CLI service.
System Level for IS-IS
The statement in the IS-IS section of the configuration file defines the level of the interface:
specifies the IS-IS level of the interface. By default, this value is
Maximum Areas for IS-IS
The statement configures the maximum area address in a system:
where num specifies the maximum area addresses supported by IS-IS. By default, this value is 3.
Area ID for IS-IS
The statement specifies the area ID for this system. This configuration is mandatory:
where areaid specifies the area ID for this system.
Area Authentication for IS-IS
The following statement specifies the authentication type and authentication key for area authentication. Area authentication is used in
L1 Link State PDUs (LSPs) and Sequence Number PDUs (SNPs).
The syntax of the configuration statement is as follows:
string] pwdlist]
where:
Specifies the password type as plain text password.
Specifies the password to use for authentication while transmitting L1
LSPs and SNPs.
Specifies the set of area passwords used for authenticating the received
L1 LSPs and SNPs.
pwdlist Specifies the list of passwords, in the form: string1 string2 ...
Domain Authentication for IS-IS
The following statement specifies the authentication type and authentication key for domain authentication. Domain authentication is used
in L1 LSPs and SNPs.
The syntax of the configuration statement is as follows:
string] pwdlist]
where:
Specifies the password type as plain text password.
Specifies the set of passwords to use for authentication while
transmitting L2 control PDUs.
Specifies the set of domain passwords used for authenticating the received
L2 LSPs, Complete Sequence Number PDUs (CSNPs) and Partial Sequence Number PDUs (PSNPs).
pwdlist Specifies the list of passwords, in the form: string1 string2 ...
Originating LSP Buffer Size for IS-IS
The following statement specifies the buffer size for LSPs originated.
The syntax of the configuration statement is as follows:
where:
Specifies the origination buffer size for L1 and L2 LSPs.
By default, this value is
lspbufsize Specifies the origination buffer size. By default, this value is 1492.
Sitelocal Configuration for IS-IS
The sitelocal statement is used to let or sending site-local address in its route updates. By default, IS-IS does not send site-local
addresses in its route updates.
The syntax of the configuration statement is as follows:
where:
Specifies to send site-local address in its route updates.
Specifies to restrict sending the site-local address in its route updates.
LSP Maximum Regeneration Interval for IS-IS
The statement below configures the maximum time allowed to elapse without LSP regeneration.
The syntax of the configuration statement is as follows:
where time-interval specifies the time interval. By default, this is 900 seconds.
Export-Defaults Configuration for IS-IS
The following statement defines the export attributes for routes sent from
The syntax of the configuration statement is as follows:
where:
Specifies the level in which the IS-IS advertises the routes exported from
By default, it is L1 for L1 routers and L2 for L2 and L1/L2 routers.
Specifies the default metric set on IP External Reachability
Information routes under export-defaults configuration statement. By default, this value is
Specifies the default type of the metric set on IS-IS routes from
another protocol. By default, this value is
Specifies the preference value for routes exported from
By default, it inherits the preference value given by
Interface Configuration for IS-IS
The following statement can be used to enable or disable IS-IS on an interface basis.
The syntax of the configuration statement is as follows:
where:
Enables or disables
By default, this value is
Specifies to send unpadded hellos on the interface.
By default, this value is
Specifies the authentication type and authentication key for the interface.
By default, this value is
Specifies the CSNP interval time for an interface.
By default, this value is 10 seconds.
Specifies the PSNP interval time for an interface.
By default, this value is 2 seconds.
Specifies the Designate IS (DIS) hello interval time for an interface.
By default, this value is 1000 milliseconds.
Specifies the interval time for IS-IS to advertise
packets on the interface. By default, this value is 3 seconds.
Specifies the number of hello intervals between reception of a hello
before considering the neighbor IS as down. By default, this value is 10 seconds.
Specifies the minimum time to wait before regenerating LSP.
By default, this value is 5 seconds.
Specifies the level of the interface.
By default, this value is same as system level.
Specifies the metric for traversing an interface.
By default, the metric value is 10.
Specifies the interface as passive.
That is, IS-IS is and the is sent out in LSPs to other interfaces. By default, this value is
Specifies the priority of DIS election for an interface.
By default, the priority level is 64.
Specifies the external domain attribute of an interface.
By default, this value is
System ID for IS-IS
This configuration is used to specify the system ID of the router. This configuration is mandatory.
where systemid specifies the system ID of the router.
Overload for IS-IS
The following configuration specifies whether the IS-IS system enters or leaves overload state. By default, this value is
The syntax of the configuration statement is as follows:
where:
Specifies that
does not enter the overload state.
Specifies to enter overload state for L1.
Specifies to enter overload state for L2.
Specifies to enter overload state for L1 and L2.
Route Leaking for IS-IS
The following configuration specifies that IS-IS can leak L2 reachability information into L1 domain. By default, this value is
The syntax of the configuration statement is as follows:
where:
Specifies to leak from L2 to L1.
Specifies that
does not leak from L2 to L1.
Require SNP Authentication for IS-IS
The following configuration specifies whether to authenticate for SNPS or not. By default, this value is
The syntax of the configuration statement is as follows:
where:
Specifies to enable SNP authentication.
Specifies to disable SNP authentication.
Summary Configuration for IS-IS
The following configures the summary addresses. Summary configuration can be used only if the system is a L1L2 router. The following
statement defines the list of L1 router that IS-IS summarizes and propagates in L2 LSPs.
The syntax of the configuration statement is as follows:
prefix prefixlength
where:
prefix prefixlength
Specifies the route prefix and its length.
metricvalue Specifies the metric value associated with the summary address.
The following statement defines the L1 routes that IS-IS filters when advertising in L2 LSPs.
The syntax of the configuration statement is as follows:
prefix prefixlength ;
where prefix prefixlength specifies the route prefix and its length.
IPRA Configuration for IS-IS
The following configures the IP reachable addresses.
The syntax of the configuration statement is as follows:
prefix prefixlength
where:
prefix prefixlength
Specifies the route prefix and its length.
Specifies the metric associated with the IPRA.
SNPA-Address Specifies the Subnetwork Point of Attachment (SNPA) address. It must be one of the interface SNPA address or adjacency SNPA
address.
Tracing for IS-IS
You can sets IS-IS tracing at protocol or event level. By default, no tracing is done. The following specifies the events to be traced.
where the options are separated by commas without any space between them. The valid trace options are:
Disables tracing.
Enables all the trace options.
Specifies to trace at function level. When enabled, traces every function, with entry,
exit and important values used in the function.
Specifies to trace state machine transitions.
Specifies to trace application of protocol and user-specified policy
to imported and exported routes.
Specifies to trace timer events.
Specifies to trace route addition and deletion in
routing table.
Specifies to trace all the IS-IS protocol activities.
Specifies to trace the combination of route and normal trace information.
Specifies to trace without time stamp.
Specifies to trace IS-IS protocol for adjacency events.
Specifies to trace IS-IS protocol for dis-election events.
Specifies to trace IS-IS protocol for LSP database events.
Specifies to trace IS-IS protocol for LSP flooding events.
Specifies to trace IS-IS protocol for LSP events.
Specifies to trace IS-IS protocol for IS-IS PDUs.
Specifies to trace IS-IS protocol for
PDUs.
Specifies to trace IS-IS protocol for CSN PDUs.
Specifies to trace IS-IS protocol for PSN PDUs.
Specifies to trace IS-IS protocol packets in detail.
Specifies to trace IS-IS protocol only for outgoing PDUs.
Specifies to trace IS-IS protocol only for incoming PDUs.
By default, no tracing is done.
Partition for IS-IS
The following statement configures the support for partition repair. By default, this value is
The syntax of the configuration statement is as follows:
where:
Specifies to support partition repair.
Specifies that
does not support partition repair.
Maximum Routes for IS-IS
The maxroutes statement configures the maximum routes that IS-IS can store.
The syntax of the configuration statement is as follows:
where numb-of-routes specifies the maximum routes. By default, this value is 10000.
Maximum Adjacency for IS-IS
The following statement specifies the maximum adjacency that IS-IS can support.
The syntax of the configuration statement is as follows:
where adjnum specifies the maximum adjacencies. By default, this value is 255.
Maximum LSP for IS-IS
The following statement specifies maximum LSPs that IS-IS can support.
The syntax of the configuration statement is as follows:
where lsp specifies the maximum LSPs. By default, this value is 1000.
Maximum Virtual Adjacencies for IS-IS
The following statement specifies the maximum virtual support for partition repair.
The syntax of the configuration statement is as follows:
where adjnum specifies the maximum virtual adjacencies for partition table. By default, this value is 5.
Maximum Circuits for IS-IS
The following statement specifies the maximum circuits that IS-IS can support.
The syntax of the configuration statement is as follows:
where numb-of-circuits specifies the maximum circuits. By default, this value is 255.
Maximum Lifetime of LSPs for IS-IS
The following statement specifies the maximum lifetime of LSPs.
The syntax of the configuration statement is as follows:
where lspage specifies the maximum lifetime of LSPs. By default, this value is 1200 seconds.
Zero Age for IS-IS
The following statement specifies the time to wait before purging an expired LSP.
The syntax of the configuration statement is as follows:
where age specifies the time to wait before purging an expired LSP. By default, this value is 60 seconds.
Receive Buffer Size for IS-IS
The following statement specifies the size of the largest LSP that the system receives.
The syntax of the configuration statement is as follows:
where buffersize specifies the size of the largest LSP. By default, this value is 1492 bytes.
EXAMPLES
To start with the periodic route polling option disabled, include the following in the configuration file:
kernel {
routepoll off;
};
A RIPng Example
The following is the configuration to run with the listener mode on the interface:
ripng on {
admin up;
cliport 15000;
interface lan0 {
noripout;
};
};
A BGP Example
The following is the configuration to run to establish BGP sessions with external peer group members and exchange IPv6 reachability infor-
mation:
as 200;
routerid 10.4.7.191;
export static to bgp;
bgp on {
admin up;
group external peeras 400 {
holdtime 10;
keepalive 10;
minasorgtime 20;
minrtadvtime 20;
peer 3344::3344 {
holdtime 90;
keepalive 30;
noauthcheck;
passive;
};
peer 3344::3345 {
multihop on;
holdtime 120;
keepalive 40;
};
};
};
Route Aggregation Example
Consider that RIPng or BGP routers learned the following routes from its neighbors:
Route 1 - 2222::5515/128
Route 2 - 2222::4389/128
Consider that RIPng or BGP protocol section of the configuration file contains the following route aggregation statement:
aggregate {
2222::/64;
};
RIPng or BGP router applies the configured aggregate statement on Route 1 and Route 2. Since the first 64 bits of Route 1 and Route 2
matches with the aggregation configuration. RIPng or BGP router aggregates these routes and generates an aggregated route as
An IS-IS Example
The following is the configuration to run to establish IS-IS adjacencies and exchange IPv6 reachability information:
export static to isis;
export direct to isis;
isis on {
admin up;
cliport 10501;
area "49:00:01";
level both;
partition yes;
systemid "AB:00:00:00:00:00";
traceoptions "/tmp/isisd.log" size 1000 k files 3;
traceoptions packets;
interface lan1 {
enable;
};
};
The sample file gives an example to configure IS-IS as a L1L2 router and enable IS-IS on lan1 interface. The configuration file enables
partition repair support. An area becomes partitioned as a result of failure of one or more links in the area. However, if each of the
partitions has a connection to the level 2 sub domain, it is possible to repair the partition through the level 2 sub domain, provided that
the level 2 sub domain itself is not partitioned.
For example, if two L1L2 routers are connected through a single L1 link, if the L1 link goes down, the area is partitioned. If the routers
are reachable through L2 routers, the partition can be repaired. The partition option allows the partition to be repaired by having a vir-
tual L1 adjacency with the neighbor through the L2 domain.
Default configuration file for RIPng
The following is the default configuration file for RIPng:
export direct to ripng;
export static to ripng;
ripng on {
admin up;
cliport 15000;
};
AUTHOR
was developed by Future Software Ltd.
SEE ALSO
bgpd(1M), isisd(1M), ramd(1M), ram_monitor(1M), rdc(1), ripngd(1M).
ramd.conf(4)