HP Routing Services -UX 11i v2 manual Planning Your Ospf Conﬁguration

Page 63

Conﬁguring gated

Conﬁguring the OSPF Protocol

it is not required that an AS boundary router be a backbone router. An AS boundary router learns about routes other than its attached AS through exchanges with other routing protocols or through conﬁguration information. Each AS boundary router calculates paths to destinations outside of its attached AS. It then advertises these paths to all routers in its AS.

Following are the two levels of routing in an AS:

•Intra-area routing, where the source and destination of a packet both reside in the same area. Routing is handled by internal routers.

•Inter-area routing, where the source and destination of a packet reside in different areas. Packets travel through an intra-area route from the source to an area border router, then travel an inter-area route on a backbone path between areas. Finally, they travel another intra-area route to the destination.

Planning Your OSPF Conﬁguration

Following is a suggested sequence of steps in planning the OSPF routing in your autonomous system:

1.If your AS exchanges routing information with other autonomous systems, you need to obtain a unique AS number from the Internet Assigned Numbers Authority.

2.Partition the AS into areas. You can partition any interconnected networks into lists of address ranges, with each address range represented as an address-mask pair. The area border routers summarize the area content for each address range and distribute the summaries to the backbone. See “The networks Statement” on page 66 for more information on specifying address ranges.

3.Identify the internal routers for each area. An internal router conﬁguration contains only one area deﬁnition.

4.Identify the area border routers and the areas to which they interface. The conﬁguration for each area border router contains multiple area deﬁnitions.

5.For each router, determine the interface type for each area. Router interfaces can be multicast, non-broadcast multi-access (NBMA), or point-to-point. See “The interface Statement” on page 67 for more information on router interfaces.

Chapter 3

63

Image 63

Contents Manufacturing Part Number B2355-90777 August EditionWarranty Government LicenseCopyright Notice Trademark Notices Page Contents Contents Index Contents HP-UX Release Name and Release Identiﬁer 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 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 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 StatementInterface Statement Conﬁguring 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 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 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 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 Conﬁguration 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