HP-UX Reference (11i v3 07/02) - 4 File Formats (vol 8)

g
gated.conf(4) gated.conf(4)
};
interface_parameters
};
Backbone only:
virtuallink neighborid router_id transitarea area {
interface_parameters
};
};
} ] ;
The following are the interface_parameters referred to above. The may be specified on any class of interface
and are described under the interface clause.
enable | disable ;
retransmitinterval time ;
transitdelay time ;
priority priority ;
hellointerval time ;
routerdeadinterval time ;
authkey auth_key ;
defaults
These parameters specify the defaults used when importing OSPF ASE routes into the gated routing
table and exporting routes from the gated routing table into OSPF ASEs.
preference preference
The preference is used to determine how OSPF routes compete with routes from other pro-
tocols in the gated routing table. The default value is 150.
cost cost
The cost is used when exporting a non-OSPF route from the GateD routing table into OSPF
as an ASE. The default value is 1. This may be explicitly overridden in export policy.
tag [ as ] tag
OSPF ASE routes have a 32 bit tag field that is not used by the OSPF protocol, but may be
used by export policy to filter routes. When OSPF is interacting with an egp, the tag field
may be used to propagate AS path information, in which case the as keyword is specified
and the tag is limited to 12 bits of information. If not specified, the tag is set to zero.
type 1 | 2
Routes exported from the GateD routing table into OSPF default to becoming type 1 ASEs.
This default may be explicitly changed here and overridden in export policy.
ASE export rate
Because of the nature of OSPF, the rate at which ASEs are flooded must be limited. These two param-
eters can be used to adjust those rate limits.
exportinterval time
This specifies how often a batch of ASE link state advertisements will be generated and
flooded into OSPF. The default is once per second.
exportlimit routes
This parameter specifies how many ASEs will be generated and flooded in each batch. The
default is 100.
traceoptions trace_options
Specifies the tracing options for OSPF. (See Trace Statements and the OSPF specific tracing options
below.)
monitorauthkey authkey
OSPF state may be queried using the ospf_monitor (This should be a hyperlink) utility. This utility
sends nonstandard OSPF packets which generate a text response from OSPF. By default these
requests are not authenticated, if an authentication key is configured, the incoming requests must
match the specified authentication key. No OSPF state may be changed by these packets, but the act
of querying OSPF can utilize system resources.
backbone
area area
Each OSPF router must be configured into at least one OSPF area. If more than one area is
HP-UX 11i Version 3: February 2007 − 20 − Hewlett-Packard Company 147