Default | HP Routing Services -UX 11i v2 instruction

Conﬁguring gated

Conﬁguring the RIP Protocol

trustedgateways router_list ; sourcegateways router_list ; traceoptions traceoptions ;

} ] ;

Curly braces ({}) are part of the syntax for the RIP protocol statement. Square brackets ([]) are not part of the syntax; they are used here to indicate optional parameters.

yes (or on) informs gated to enable the RIP protocol at this node and to process RIP packets coming in from other nodes. no (or off) informs gated to disable the RIP protocol at this node. If gated ﬁnds fewer than two network interfaces, the node listens to RIP information. If gated ﬁnds two or more network interfaces, the node not only listens but also broadcasts or multicasts the RIP information. If you do not specify a RIP statement in your conﬁguration ﬁle, rip on is assumed.

The following describes the various options in the RIP statement:

•broadcast speciﬁes that RIP packets are always generated. If the RIP protocol is enabled and more than one interface is speciﬁed, broadcast is assumed. Specifying broadcast with only one interface is useful only when propagating static routes or routes learned from other protocols.

•nobroadcast speciﬁes that RIP packets are sent only to routers listed in the sourcegateways clause. If the RIP protocol is enabled, but only one interface is speciﬁed, nobroadcast is assumed.

•nocheckzero speciﬁes that the RIP protocol must not check whether the reserved ﬁelds in the RIP packets are zero. In RIP Version 1 (as described in RFC 1058), certain reserved ﬁelds must be zero; however, this may vary in RIP implementations.

•preference determines the order of routes from other protocols to the same destination in the routing table. gated allows one route to a destination per protocol for each autonomous system. In case of multiple routes, the route used is determined by the value of preference.

Default: 100

Range: 0 (most preferred) – 255 (least preferred)

•defaultmetric is the default metric used when propagating routes learned from other protocols.

Default: 16

Chapter 3

51

Image 51

HP Routing Services -UX 11i v2 manual Default

Contents

Manufacturing Part Number B2355-90777 August Edition Warranty Government LicenseCopyright Notice Trademark Notices Page Contents Contents Index Contents HP-UX Release Name and Release Identiﬁer Intended Audience What Is in This Document Publishing HistoryDocument Organization Chapter Description Related Documentation HP-UX Internet Services Administrator’s Guide Typographical Conventions Mbone FAQ Bold HP Encourages Your Feedback Version 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 Addresses Multicast Groups Mrouted Routing Daemon Advantages Gated Routing Daemon Deciding When to Use gated Routing Protocols RIP Ospf Comparison of RIP and Ospf Protocols RIP Ospf Gated Routing Daemon Gated Routing Daemon Chapter Conﬁguring mrouted Conﬁguring mrouted Conﬁguration Commands How to Conﬁgure mrouted Tunnel Multicast Network Example Conﬁguration How to Conﬁgure mrouted How to Conﬁgure mrouted Starting mrouted Verifying mrouted Operation Displaying mrouted Routing Tables HUP Displaying mrouted Routing Tables Netstat Tool Multicast Routing Support ToolsMrinfo Tool Map-mbone Tool Multicast Routing Support Tools Chapter Conﬁguring gated Conﬁguring gated Conﬁguration Overview Conﬁguring gated Protocol statements follow Converting the Conﬁguration File from 3.0 to Cp /etc/gated.conf /etc/gated.conf.30 RIP Protocol Statement Conﬁguring the RIP Protocol Default Range 1 Conﬁguration Options Routers Simple RIP ConﬁgurationExample of Simple RIP Conﬁguration End Systems RIP Router Example of a Large RIP Conﬁguration Single Node Major RouterCluster Node Isolated Node Root Server Cluster or Root Server Node Major Router Controlling RIP Trafﬁc Conﬁguring the RIP Protocol Conﬁguring the Ospf Protocol Areas Deﬁned in an Autonomous System AreaNetwork Router Area Conﬁguring the Ospf Protocol Planning Your Ospf Conﬁguration Enabling Ospf Deﬁning Areas Area Border Router Conﬁguration ExampleArea To Network a 193.2.1.33 Border Router To Network B Network Conﬁguration Example Networks Statement Interface Statement Conﬁguring the Ospf Protocol Default None Router 193.2.1.35 Network Multicast Router Interface Example Range 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 Conﬁguring 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 Router Area 15.13.115.156 Router a Router B Deﬁning Backbones Authentication Authkey pepe Authkey travis Cost LAN 1 LAN 2 Cost AS External Routes AS Boundary Routers Only Default Conﬁguring the Ospf Protocol Internal Router Non-Stub Area Sample Ospf Conﬁguration Area Border Router Internal Router Stub Area Accessing the Ospf MIB RDP Server Conﬁguring RDP RDP Client RDP Client Server Specifying a Default Router Installing Static RoutesCustomizing Routes Setting Interface States Specifying Tracing Options Option Effect Files Default 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 Running Troubleshooting gated Checking for Syntax Errors in the Conﬁguration FileTracing gated Activity 102 Operational User Interface for gated gdc Gated 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 table Problem 3 gated adds routes that appear to be incorrect 108 Problem 4 gated does not add routes that you think it must 109 Index 110 111 112 113 TOS