Deploying RIP for IP

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Deploying RIP for IP

While basic RIP version 1 functionality is easy to configure and deploy, RIP version 2 and advanced RIP capabilities, such as peer security and route filtering, require additional configuration and testing. To make troubleshooting and problem isolation easier, it is recommended that you deploy your RIP-based internetwork in the following stages:

  1. Set up basic RIP and make sure it is working.

  2. Add advanced capabilities one at a time, testing after each feature is added.

Deploying RIP

To deploy RIP, you can perform the following steps:

  1. Draw a map of the topology of your IP internetwork that shows the separate networks and the placement of routers and hosts (nonrouter computers running TCP/IP).

  2. For each IP network (a cabling system bounded by one or more routers), assign a unique IP network ID (also known as an IP network address).

  3. Assign IP addresses to each router interface. It is a common industry practice to assign the first IP addresses of an IP network to router interfaces. For example, for an IP network ID of 192.168.100.0 with a subnet mask of 255.255.255.0, the router interface is assigned an IP address of 192.168.100.1.

  4. For each router interface, designate whether that interface will be configured for RIP v1 or RIP v2. If an interface is configured for RIP v2, designate whether the RIP v2 announcements will be broadcast or multicast.

  5. By using Routing and Remote Access, add the RIP routing protocol and configure the appropriate interfaces for RIP v1 or RIP v2 for each server running Routing and Remote Access.

  6. When your configuration is complete, allow a few minutes for the routers to update each other's routing tables and then test the internetwork.

For more information, see Configure RIP for IP.

Testing a RIP internetwork

To test your RIP internetwork, you can perform the following steps:

  1. To verify that a server running Routing and Remote Access is receiving RIP announcements from all of its neighboring RIP routers, view the RIP neighbors for the router. For more information about viewing RIP neighbors, see View RIP neighbors.

  2. For each RIP router, view the IP routing table and verify that all of the routes that should be learned from RIP are present. For more information about viewing the IP routing table, see View routing tables.

  3. Use the ping and tracert commands to test connectivity between host computers so that all routing paths are checked. For more information about the ping and tracert commands, see Using the ping command and Using the tracert command.

For information about troubleshooting RIP for IP, see Troubleshooting RIP for IP.