HP Routing Services -UX 11i v2 manual Configuring the RIP Protocol, RIP Protocol Statement

Page 50

Configuring gated

Configuring the RIP Protocol

Configuring the RIP Protocol

RIP uses hopcount to determine the shortest path to a destination. Hopcount is the number of routers a packet must pass through to reach its destination. If a path is directly connected, it has the lowest hopcount of 1. If the path passes through a single router, the hopcount increases to

2.Hopcount can increase to a maximum value of 16, which is RIP’s infinity metric, an indication that a network or node cannot be reached.

If gated encounters an unreachable node, it goes into Holddown Mode. Holddown Mode stops a node from propagating routing information until the other nodes that it is communicating with stabilize their routing information.

Hosts with only one LAN interface may use the RIP protocol with gated to passively listen to routing information when multiple routers on the LAN exist. If only one router on the LAN exists (leaving only one path off the local LAN), you can configure a static route to that router in the /etc/rc.config.d/net file, or issue the route command manually, instead of running gated.

In certain cases, you may not want the traffic to follow a certain path, because it incurs an unacceptable cost or security risk. In these cases, gated allows you to assign a metric to each interface. This allows you to select or bypass a path, irrespective of its length or speed.

RIP Protocol Statement

The syntax of the RIP protocol statement is as follows:

rip yesno onoff [ { broadcastnobroadcast ; nocheckzero ; preference preference ; defaultmetric metric ;

query authentication [none[[simplemd5] password]] ; interface interface_list

[noripin][ripin] [noripout][ripout] [metricin metric] [metricout metric] [version 1][version 2 [multicastbroadcast]] [[secondary] authentication [none[simplemd5] password]

] ;

[interface ...]

50

Chapter 3

Image 50
Contents Edition Manufacturing Part Number B2355-90777 AugustCopyright Notice WarrantyGovernment License Trademark Notices Page Contents Contents Index Contents Intended Audience HP-UX Release Name and Release IdentifierDocument Organization Chapter Description What Is in This DocumentPublishing History HP-UX Internet Services Administrator’s Guide Related DocumentationMbone FAQ Typographical ConventionsHP Encourages Your Feedback BoldVersion of HP-UX that you are using Overview Overview Dvmrp Protocol Mrouted Routing DaemonMulticasting Overview Endpoint Dvmrp TunnelDvmrp Tunnel Multicast IP Multicast Addresses Class D IP Multicast Address FormatMulticast Groups Mrouted Routing Daemon Gated Routing Daemon AdvantagesDeciding When to Use gated Routing Protocols Comparison of RIP and Ospf Protocols RIP OspfRIP Ospf Gated Routing Daemon Gated Routing Daemon Chapter Configuring mrouted Configuring mrouted How to Configure mrouted Configuration CommandsTunnel 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 Map-mbone Tool Multicast Routing Support ToolsMrinfo Tool Netstat 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 Configuring the RIP Protocol RIP Protocol StatementDefault Range 1 Configuration Options End Systems Simple RIP ConfigurationExample of Simple RIP Configuration RoutersExample of a Large RIP Configuration RIP RouterRoot Server Major RouterCluster Node Isolated Node Single NodeCluster or Root Server Node Controlling RIP Traffic Major RouterConfiguring the RIP Protocol Configuring the Ospf Protocol Network Router Area Areas Defined in an Autonomous SystemArea Configuring the Ospf Protocol Planning Your Ospf Configuration Enabling Ospf Area To Network a 193.2.1.33 Border Router To Network B Defining AreasArea Border Router Configuration Example Networks Statement Network Configuration ExampleInterface Statement Configuring the Ospf Protocol Default None Multicast Router Interface Example Router 193.2.1.35 NetworkRouter 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 Configuring the Ospf Protocol Stub Areas Point-to-Point Router Interface ExampleRouter 193.2.1.1 193.2.1.2 Area Router 193.2.1.20 193.2.1.17 193.2.1.18 193.2.1.19Defining Backbones Area 15.13.115.156 Router a Router BAuthentication Authkey travis Authkey pepeCost Cost LAN 1 LAN 2AS External Routes AS Boundary Routers Only Default Configuring the Ospf Protocol Sample Ospf Configuration Internal Router Non-Stub AreaArea Border Router Internal Router Stub Area Accessing the Ospf MIB Configuring RDP RDP ServerRDP Client Server RDP ClientCustomizing Routes Specifying a Default RouterInstalling Static Routes Setting Interface States Specifying Tracing Options Files Option EffectRoute 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 Verifying That gated Is Running 100Tracing gated Activity Troubleshooting gatedChecking for Syntax Errors in the Configuration File Operational User Interface for gated gdc 102Ospfmonitor Tool Gated Routing TableRipquery Tool 104 Common ProblemsProblem 1 gated does not act as expected Chapter 105 Problem 2 gated deletes routes from the routing table 106Problem 3 gated adds routes that appear to be incorrect Problem 4 gated does not add routes that you think it must 108Index 109110 111 112 TOS 113