Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
22 views2 pages

Rip Lab Solution

Uploaded by

johnymadeinchina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
22 views2 pages

Rip Lab Solution

Uploaded by

johnymadeinchina
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

# RIP Lab Solution

## 1. Basic Configurations

### Adding necessary modules and enabling interfaces:


1. Ensure all routers have the necessary modules installed.
2. For each router, enable all used interfaces:
```
Router> enable
Router# configure terminal
Router(config)# interface [interface-name]
Router(config-if)# no shutdown
Router(config-if)# exit
```
Repeat for all interfaces on each router.

### Default known routes:


By default, each router will only know about directly connected networks. To view
these:
```
Router# show ip route connected
```

## 2. Setting up RIP

### Activating RIP on each router:


```
Router> enable
Router# configure terminal
Router(config)# router rip
Router(config-router)# version 2
Router(config-router)# no auto-summary
```

### Adding known networks:


For each directly connected network:
```
Router(config-router)# network [network-address]
```

### Checking routing tables:


```
Router# show ip route
```
Note any changes after enabling RIP.

### Simulating RIP exchanges:


1. In your simulation tool (e.g., Packet Tracer, GNS3), filter to show only RIP
protocol.
2. Run the simulation for several minutes to allow multiple 30-second update
cycles.
3. Stop the simulation.

### Examining updated routing tables:


```
Router# show ip route
```
Compare with initial state and note new routes learned via RIP.
### Analyzing RIP messages:
In your simulation tool, click on a RIP message envelope to view the protocol
stack.
RIP typically uses:
- Transport Layer: UDP
- Network Layer: IP
- Data Link Layer: Ethernet (or other, depending on the connection type)

### RIP port:


RIP uses UDP port 520 by default.

## 3. Tests

### Connectivity tests:


From each station, ping all other stations:
```
Station> ping [destination-ip]
```

### Simulating link failures:


1. Remove the link between Router2 and Router0.
2. Remove the link between Router1 and Router3.
3. In CLI, this would be equivalent to:
```
Router> enable
Router# configure terminal
Router(config)# interface [interface-connecting-to-other-router]
Router(config-if)# shutdown
```
4. Repeat connectivity tests and observe changes in routing behavior.

## Additional Notes:
- RIP exchanges routing updates every 30 seconds.
- RIP uses a hop count metric with a maximum of 15 hops.
- In a production environment, you might want to consider more advanced routing
protocols like OSPF or EIGRP for larger networks.

Remember to document all your observations, especially changes in routing tables


and the results of your connectivity tests before and after simulating link
failures.

You might also like