ramd.conf.4 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

ramd.conf(4) ramd.conf(4)

NAME

ramd.conf - Route Administration Manager Daemon (RAMD) conﬁguration ﬁle

SYNOPSIS

/etc/ramd.conf

DESCRIPTION

ramd.conf is the conﬁguration ﬁle for the Route Administration Manager daemon (RAMD) for IPv6.

This ﬁle comprises of conﬁguration statements that conﬁgures

ramd, ripngd, bgpd and isisd.

ripngd, bgpd, and isisd are referred to as routing daemons. Upon startup, the daemons read this

conﬁguration ﬁle. This ﬁle contains:

• interface conﬁguration statements,

• protocol conﬁguration statements,

• static route conﬁguration statements,

• control conﬁguration statements, and

• aggregate conﬁguration statements.

Conﬁguring RAMD

The RAMD conﬁguration ﬁle,

/etc/ramd.conf, consists of a set of conﬁguration statements that ter-

minate with a semi-colon (

;).

These conﬁguration statements are composed of tokens separated by white space. This structure

simpliﬁes the identiﬁcation of parts of the conﬁguration associated with each other and with speciﬁc pro-

tocols. Comments can be speciﬁed with a pound sign (

#) at the beginning of the line.

Syntax conventions

The syntax conventions speciﬁc to the conﬁguration ﬁle are:

highlight Highlighting indicates keywords and special characters that the parser expects.

underline Underlining (or italic) indicates a parameters whose value can be speciﬁed.

[] 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:

[

routepoll (off|on)[interval seconds] ;]

The square brackets indicate that the parameter is optional. The keywords in the example conﬁguration

statement are

routepoll, on, off, and interval. The vertical bar | indicates a choice between

and off. The underline (or italic font) seconds indicates that a value must be speciﬁed.

RAMD Conﬁguration Statement Summary

The

/etc/ramd.conf ﬁle is divided into ramd global section and routing protocol section. The

conﬁguration statements for the ramd global section are given below:

as Deﬁnes the autonomous system (AS) number.

routerid Deﬁnes the originating router (BGP).

kernel Conﬁgures kernel interface options.

preference Speciﬁes the preference order of routes to the same destination.

interface Conﬁgures speciﬁc interface attributes.

traceoptions Speciﬁes events to be traced.

redirect Speciﬁes the processing of redirect requests.

martians Speciﬁes invalid destination addresses.

route_filter Conﬁgures route ﬁltering.

static Deﬁnes static routes.

import Speciﬁes routes to be imported.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (28 pages)

PAGE 1
ramd.conf(4) ramd.conf(4) NAME ramd.conf - Route Administration Manager Daemon (RAMD) configuration file SYNOPSIS /etc/ramd.conf DESCRIPTION ramd.conf is the configuration file for the Route Administration Manager daemon (RAMD) for IPv6. This file comprises of configuration statements that configures ramd, ripngd, bgpd and isisd. ripngd, bgpd, and isisd are referred to as routing daemons. Upon startup, the daemons read this configuration file.
PAGE 2
ramd.conf(4) ramd.conf(4) Specifies routes to be exported. export RAMD Global Configuration Autonomous System Statement The as 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 as configuration statement is as follows: as asnum ; This autonomous system appears only once in an AS path.
PAGE 3
ramd.conf(4) ramd.conf(4) By default, route polling is disabled. interval poll-interval ; Specifies how often the kernel routing table is scanned for modifications. The default poll interval is 30 seconds. By default, route polling is disabled. remnantholdtime timer-value ; Specifies the duration, in minutes, for which ramd retains the remnant routes (routes retrieved from the kernel upon ramd startup) in its routing table.
PAGE 4
ramd.conf(4) ramd.conf(4) 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.
PAGE 5
ramd.conf(4) ramd.conf(4) handles the redirect message only when the redirect configuration statement is specified in the /etc/ramd.conf configuration file. The redirect configuration statement does not prevent the system from sending redirects, but only from listening to them.
PAGE 6
ramd.conf(4) ramd.conf(4) prefix prefixlength ; prefix specifies the destination network address, and prefixlength specifies the valid number of bits in the destination network address. host host-address ; Specifies the host to configure and the destination host address. all; 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 ramd starts.
PAGE 7
ramd.conf(4) restrict ramd.conf(4) 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 ramd daemon. The ramd daemon installs the best route in the kernel routing table. Export Configuration Statement The export configuration statement controls the routes that ramd advertises to other protocols.
PAGE 8
ramd.conf(4) ramd.conf(4) Enabling RIPng The RAMD configuration file enables or disables the RIPng protocol. If the ripng configuration statement is not specified in the configuration file, by default, the value is off. Only one ripng configuration statement can be specified in the configuration file. The syntax for ripng is: ripng (on|off) {admin (up|down); [snmp (on|off);]}; where the following means: ripng Enables or disables RIPng protocol. By default, RIPng protocol is disabled.
PAGE 9
ramd.conf(4) ramd.conf(4) The syntax of the sitelocal configuration statement is as follows: sitelocal (allow|restrict); where: allow Specifies that propagation of site-local routes is allowed. restrict 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.
PAGE 10
ramd.conf(4) restrict ramd.conf(4) Specifies the route that ripngd 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.
PAGE 11
ramd.conf(4) ramd.conf(4) 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: trustedgateway gateway-list ; 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.
PAGE 12
ramd.conf(4) ramd.conf(4) Route Filtering Based on Interface for RIPng 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 filter configuration statement is as follows: filter dir (in|out) route-filter-name-list [allow|restrict]; where the following means: in|out Specifies the direction to apply the filter.
PAGE 13
ramd.conf(4) ramd.conf(4) Maximum Routes for BGP The maxroutes statement configures the maximum routes that bgpd can store in its routing table. The syntax of the maxroutes configuration statement is as follows: maxroutes numb-of-routes ; where numb-of-routes specifies the maximum routes that bgpd can store in its routing table. By default, this value is 5000. Maximum Peers for BGP The maxpeers statement configures the maximum peers that bgpd supports.
PAGE 14
ramd.conf(4) ramd.conf(4) route_filter filter-name { [as asnum] [(prefix prefixlength) | (hosthost-address ) | all] [aspath aslist] dir (in|out); } (allow|restrict); where: as asnum Specifies the remote autonomous system (AS) number based on which bgpd applies the filter. prefix prefixlength Specifies the route prefix based on which bgpd applies the filter. host host-address Specifies the host routes on which bgpd applies this filter. all Specifies bgpd to filter all routes.
PAGE 15
ramd.conf(4) ramd.conf(4) value. localpref configuration statement overrides the defaultlocalpref configuration statement. The syntax of the localpref configuration statement is as follows: localpref { [as asnum] [prefix prefixlength ] [aspath aslist] [dir (in|out)] pref preference-value [override|inherit]; }; where: as asnum Specifies the local preference value for the routes from the remote autonomous system (AS). Applicable only for the in direction.
PAGE 16
ramd.conf(4) ramd.conf(4) override|inherit Specifies that the MED value must override or inherit. By default, the MED value is inherit. bgpd uses the following configuration statement to configure MED comparison. always-compare-med (on|off); where: off Compares MED between the routes received from the same autonomous system (AS). This is the default. on Compares MED between the routes received from the same or different AS.
PAGE 17
ramd.conf(4) ramd.
PAGE 18
ramd.conf(4) ramd.conf(4) showwarnings (on|off); Logs the warning messages in trace file of bgpd when receiving questionable BGP updates such as duplicate routes and deletions of non-existing routes from the peer. By default, showwarning is off. noaggregatorid; Specifies that the aggregator ID in the aggregate attribute must be 0 instead of the router ID. keepalivealways; Specifies that keepalive is sent always, even when sending update packet for a peer.
PAGE 19
ramd.conf(4) ramd.conf(4) [traceoptions trace-options;] [gateway address ;] [noaggregatorid;] [keepalivealways;] [noauthcheck;] [hoplimit hoplimit ;] [sendbuffer buffersize ;] [recvbuffer buffersize ;] [keep (all|none);] [passive;] [localas asnum;] [noasloop;] allow { [prefix prefixlength ;] [all;] [host host-address ;] }; peer host-address [up|down] if ifname {... }; }; The group configuration accepts many groups, but each must possess a unique combination of type and peer autonomous system (AS).
PAGE 20
ramd.conf(4) ramd.conf(4) 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 (International Organization for Standardization/Connectionless Network Protocol) packets. IS-IS of RAMD supports IPv6 Routing information exchange. It transmits over data link layer.
PAGE 21
ramd.conf(4) ramd.conf(4) Area ID for IS-IS The area statement specifies the area ID for this system. This configuration is mandatory: area areaid ; 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).
PAGE 22
ramd.conf(4) restrict ramd.conf(4) Specifies isisd 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 lsp-max-regeneration-interval configuration statement is as follows: lsp-max-regeneration-interval timer-interval ; where time-interval specifies the time interval. By default, this is 900 seconds.
PAGE 23
ramd.conf(4) ramd.conf(4) auth (simple... | none); Specifies the authentication type and authentication key for the interface. By default, this value is none. csn-interval time-interval [level (l1|l2|both)]; Specifies the CSNP interval time for an interface. By default, this value is 10 seconds. psn-interval time-interval [level (l1|l2|both)]; Specifies the PSNP interval time for an interface. By default, this value is 2 seconds.
PAGE 24
ramd.conf(4) ramd.conf(4) where: on Specifies to leak from L2 to L1. off Specifies that isisd 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 off. The syntax of the require-snp-auth configuration statement is as follows: require-snp-auth (on|off); where: on Specifies to enable SNP authentication. off Specifies to disable SNP authentication.
PAGE 25
ramd.conf(4) ramd.conf(4) all Enables all the trace options. function Specifies to trace at function level. When enabled, traces every function, with entry, exit and important values used in the function. state Specifies to trace state machine transitions. policy Specifies to trace application of protocol and user-specified policy to imported and exported routes. timer Specifies to trace timer events. route Specifies to trace route addition and deletion in isisd routing table.
PAGE 26
ramd.conf(4) ramd.conf(4) Maximum LSP for IS-IS The following statement specifies maximum LSPs that IS-IS can support. The syntax of the maxlsp configuration statement is as follows: maxlsp lsp ; 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.
PAGE 27
ramd.conf(4) ramd.conf(4) A BGP Example The following is the configuration to run bgpd to establish BGP sessions with external peer group members and exchange IPv6 reachability information: as 200; routerid 10.4.7.
PAGE 28
ramd.conf(4) ramd.conf(4) }; }; 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.