HP Routing Services -UX 11i v2 manual Deciding When to Use gated

Page 23

Overview

The gated Routing Daemon

•gated translates among several protocols, passing information within or between IP routing domains or autonomous systems. Autonomous system (AS) is used here to refer to a group of connected nodes and routers in the same administrative domain that exchange routing information via a common routing protocol.

•gated provides the system administrator ﬂexibility in setting up and controlling network routing. For example, gated can listen to network trafﬁc at speciﬁed routers, determine available routes, and update local routing tables accordingly.

Deciding When to Use gated

gated is mostly used in large networks, or in small networks connected to larger wide area networks.

You must run gated on routers (gateways) to send the routing information to other routers. gated supports many routing protocols that allow routers to build and maintain dynamic routing tables. However, gated also supports RIP, which runs on end systems (systems with only one network interface) as well as on routers.

NOTE	gated also supports RDP as a client. RDP will replace rdpd.

gated is useful in topologies with multiple routers and multiple paths between parts of the network. gated allows routers to exchange routing information and to change routing information dynamically to reﬂect topology changes and maintain optimal routing paths.

Alternatively, you can conﬁgure IP routes manually with the route (1M) command. For end systems in subnets with only one router (gateway) to the Internet, manually conﬁguring a default route is usually more efﬁcient than running gated. For more details on manually manipulating the routing tables, type man 1M route at the HP-UX prompt.

When connected to wide area networks, you can use gated to inject local routing information into the wide area network’s routing table.

Chapter 1

23

Image 23

Contents Manufacturing Part Number B2355-90777 August EditionCopyright Notice WarrantyGovernment License Trademark Notices Page Contents Contents Index Contents HP-UX Release Name and Release Identiﬁer Intended AudienceDocument Organization Chapter Description What Is in This DocumentPublishing History 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 Dvmrp Protocol Mrouted Routing DaemonMulticasting Overview Endpoint Dvmrp TunnelDvmrp Tunnel Multicast 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 Conﬁguring mrouted Conﬁguring mrouted Conﬁguration Commands How to Conﬁgure mroutedTunnel 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 ToolMulticast 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 ProtocolDefault Range 1 Conﬁguration Options Routers Simple RIP ConﬁgurationExample of Simple RIP Conﬁguration End SystemsRIP Router Example of a Large RIP ConﬁgurationSingle Node Major RouterCluster Node Isolated Node Root ServerCluster or Root Server Node Major Router Controlling RIP TrafﬁcConﬁguring the RIP Protocol Conﬁguring the Ospf Protocol Network Router Area Areas Deﬁned in an Autonomous SystemArea Conﬁguring the Ospf Protocol Planning Your Ospf Conﬁguration Enabling Ospf Area To Network a 193.2.1.33 Border Router To Network B Deﬁning AreasArea Border Router Conﬁguration Example Network Conﬁguration Example Networks StatementInterface Statement Conﬁguring the Ospf Protocol Default None Router 193.2.1.35 Network Multicast Router Interface ExampleRouter Network 193.2.1.35 193.2.1.33 Internet 193.2.1.46 Range 0Non-Broadcast Router Interface Example Hellointerval value must be the same for all Ospf routers Conﬁguring the Ospf Protocol Stub Areas Point-to-Point Router Interface ExampleRouter 193.2.1.1 193.2.1.2 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 Deﬁning BackbonesAuthentication Authkey pepe Authkey travisCost LAN 1 LAN 2 CostAS External Routes AS Boundary Routers Only Default Conﬁguring the Ospf Protocol Internal Router Non-Stub Area Sample Ospf ConﬁgurationArea Border Router Internal Router Stub Area Accessing the Ospf MIB RDP Server Conﬁguring RDPRDP Client RDP Client ServerCustomizing Routes Specifying a Default RouterInstalling Static Routes Setting Interface States Specifying Tracing Options Option Effect FilesRoute Type Preference Default Preference Values of RoutesSpecifying Route Preference BGP Specifying Route Preference Export Statement Importing and Exporting RoutesImport Statement Examples of import and export Statements Flag Effect Command Line Options for gatedStarting gated 100 Verifying That gated Is RunningTracing gated Activity Troubleshooting gatedChecking for Syntax Errors in the Conﬁguration File 102 Operational User Interface for gated gdcOspfmonitor Tool Gated Routing TableRipquery Tool 104 Common ProblemsProblem 1 gated does not act as expected 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