HP Routing Services -UX 11i v2 manual Starting gated, Command Line Options for gated, Flag Effect

Page 99

Configuring gated

Starting gated

Starting gated

To start gated, complete the following steps:

1. Set the environment variable GATED to 1 in the file /etc/rc.config.d/netconf to start gated automatically upon system startup.

2. Reboot your system, or issue the following command to run the

gated startup script: /sbin/init.d/gated start

 

You can also start gated by running the command gdc start. The

 

following message appears to indicate that gated has started:

 

gated started, pid 29777

 

where 29777 is the process ID (pid) of the gated process. You can specify

 

the command-line arguments for starting gated with the GATED_ARGS

 

environment variable in the file /etc/rc.config.d/netconf. Table 3-4

 

lists the commonly used command-line options for gated.

Table 3-4

Command Line Options for gated

 

 

 

 

 

Flag

Effect

 

 

 

 

 

 

-t

When used alone, -tcauses gated to log all error messages

 

 

 

and route changes. It turns on the general trace option

 

 

 

automatically. When -tis followed by one or more trace

 

 

 

options, only those options are turned on. (See “Specifying

 

 

 

Tracing Options” on page 92 for more information.)

 

 

 

Multiple trace options are separated by commas. The -t

 

 

 

flag must immediately precede the other flags.

 

 

 

 

 

 

-C

Specifies that the configuration file will be parsed for

 

 

 

syntax errors. gated exits with a status of 1 if there are

 

 

 

any errors and 0 (zero) if there are no errors.

 

 

 

 

 

 

-c

Specifies that the configuration file will be parsed for

 

 

 

syntax errors. A dump file /var/tmp/gated_dump is

 

 

 

created if there are no errors. Only the trace option

 

 

 

general is logged. See “Specifying Tracing Options” on

 

 

 

page 92 for a detailed description of all the tracing options.

 

 

 

 

 

Chapter 3

99

Image 99
Contents Manufacturing Part Number B2355-90777 August EditionWarranty Government LicenseCopyright Notice Trademark Notices Page Contents Contents Index Contents HP-UX Release Name and Release Identifier Intended AudienceWhat Is in This Document Publishing HistoryDocument Organization Chapter Description Related Documentation HP-UX Internet Services Administrator’s GuideTypographical Conventions Mbone FAQBold HP Encourages Your FeedbackVersion of HP-UX that you are using Overview Overview Mrouted Routing Daemon Multicasting OverviewDvmrp Protocol Dvmrp Tunnel Dvmrp Tunnel MulticastEndpoint Class D IP Multicast Address Format IP Multicast AddressesMulticast Groups Mrouted Routing Daemon Advantages Gated Routing DaemonDeciding When to Use gated Routing Protocols RIP Ospf Comparison of RIP and Ospf ProtocolsRIP Ospf Gated Routing Daemon Gated Routing Daemon Chapter Configuring mrouted Configuring mrouted Configuration Commands How to Configure mroutedTunnel Multicast Network Example Configuration How to Configure mrouted How to Configure mrouted Starting mrouted Verifying mrouted Operation Displaying mrouted Routing Tables HUP Displaying mrouted Routing Tables Netstat Tool Multicast Routing Support ToolsMrinfo Tool Map-mbone ToolMulticast Routing Support Tools Chapter Configuring gated Configuring gated Configuration Overview Configuring gated Protocol statements follow Converting the Configuration File from 3.0 to Cp /etc/gated.conf /etc/gated.conf.30 RIP Protocol Statement Configuring the RIP ProtocolDefault Range 1 Configuration Options Routers Simple RIP ConfigurationExample of Simple RIP Configuration End SystemsRIP Router Example of a Large RIP ConfigurationSingle Node Major RouterCluster Node Isolated Node Root ServerCluster or Root Server Node Major Router Controlling RIP TrafficConfiguring the RIP Protocol Configuring the Ospf Protocol Areas Defined in an Autonomous System AreaNetwork Router Area Configuring the Ospf Protocol Planning Your Ospf Configuration Enabling Ospf Defining Areas Area Border Router Configuration ExampleArea To Network a 193.2.1.33 Border Router To Network B Network Configuration Example Networks StatementInterface Statement Configuring the Ospf Protocol Default None Router 193.2.1.35 Network Multicast Router Interface ExampleRange 0 Non-Broadcast Router Interface ExampleRouter Network 193.2.1.35 193.2.1.33 Internet 193.2.1.46 Hellointerval value must be the same for all Ospf routers Configuring the Ospf Protocol Point-to-Point Router Interface Example Router 193.2.1.1 193.2.1.2Stub Areas 193.2.1.20 193.2.1.17 193.2.1.18 193.2.1.19 Area RouterArea 15.13.115.156 Router a Router B Defining BackbonesAuthentication Authkey pepe Authkey travisCost LAN 1 LAN 2 CostAS External Routes AS Boundary Routers Only Default Configuring the Ospf Protocol Internal Router Non-Stub Area Sample Ospf ConfigurationArea Border Router Internal Router Stub Area Accessing the Ospf MIB RDP Server Configuring RDPRDP Client RDP Client ServerSpecifying a Default Router Installing Static RoutesCustomizing Routes Setting Interface States Specifying Tracing Options Option Effect FilesDefault Preference Values of Routes Specifying Route PreferenceRoute Type Preference BGP Specifying Route Preference Importing and Exporting Routes Import StatementExport Statement Examples of import and export Statements Command Line Options for gated Starting gatedFlag Effect 100 Verifying That gated Is RunningTroubleshooting gated Checking for Syntax Errors in the Configuration FileTracing gated Activity 102 Operational User Interface for gated gdcGated Routing Table Ripquery ToolOspfmonitor Tool Common Problems Problem 1 gated does not act as expected104 Chapter 105 106 Problem 2 gated deletes routes from the routing tableProblem 3 gated adds routes that appear to be incorrect 108 Problem 4 gated does not add routes that you think it must109 Index110 111 112 113 TOS