TS - MPLSv3 vrf map Filter

TS5 - MST Problem

RIP Troubleshooting

 

Troubleshooting Routing Information Protocol (RIP)

 

Commands that you can use to gather information about the Routing Information Protocol (RIP) routing protocol in order to assist in your troubleshooting and problem resolution are covered.

Getting network information

To start this process, look at the ip route command, which in addition to listing routes, can display summary information letting you know how many RIP-based networks exist in the routing table.

Router2>enable
Password:
Router2#show ip route summary
IP routing table name is Default-IP-Routing-Table(0)
IP routing table maximum-paths is 16
Route Source    Networks    Subnets     Overhead    Memory (bytes)
connected       2           0           144         272
static          1           0           72          136
rip             1           0           72          136
Total           4           0           288         544

To ensure that the routing protocol is up and functioning, use the show ip protocols command, which provides similar output to the following. However, first note some important things to look for in the output:

• Timers and when the next update will be sent to neighboring routers
• Version of RIP in use
• Interfaces in use for RIP
• Networks being routed by RIP
• Address from which you are receiving RIP information

Router2>enable
Password:

Router2#show ip protocols
Routing Protocol is "rip"
  Sending updates every 30 seconds, next due in 12 seconds
  Invalid after 180 seconds, hold down 180, flushed after 240
  Outgoing update filter list for all interfaces is not set
  Incoming update filter list for all interfaces is not set
  Redistributing: rip
  Default version control: send version 2, receive version 2
    Interface             Send  Recv  Triggered RIP  Key-chain
    FastEthernet0/0       2     2
    FastEthernet0/1       2     2
  Automatic network summarization is not in effect
  Maximum path: 4
  Routing for Networks:
    192.168.1.0
    192.168.5.0
  Routing Information Sources:
    Gateway         Distance      Last Update
    192.168.1.1          120      00:32:42
  Distance: (default is 120)

Note the last item, which lists the administrative distance. This point becomes important when using multiple routing protocols, because each protocol has a different default distance that determines which routing protocol is favored when a remote network is advertised on multiple routing protocols.

 

Seeing information RIP receives

You can view the contents of the RIP database to find out what information RIP has received. Doing so shows you the networks that are part of RIP, the summarization settings, and from which routers your router has learned routes.

Router2>enable
Password:
Router2#show ip rip database
192.168.1.0/24    auto-summary
192.168.1.0/24    directly connected, FastEthernet0/0
192.168.5.0/24    auto-summary
192.168.5.0/24    directly connected, FastEthernet0/1
192.168.10.0/24    auto-summary
192.168.10.0/24
    [1] via 192.168.1.1, 00:00:20, FastEthernet0/0

Debugging RIP

Finally, you have the system debug command. In regard to RIP, the debug command is limited to database changes. In the following output, you see the types of data you can get from debug command, which are also listed here:

• The RIP information your router is sending out and the networks included in the update
• The RIP version being used
• The RIP data being received, including the interface it arrived on, the router it came from, and the networks that are included

If you are using debug through a remote console, you use terminal monitor to see the debug information the remote console's screen.

Router2>enable
Password:
Router2#debug ip rip ?
  database  RIP database events
  events    RIP protocol events
  trigger   RIP trigger extension
  <cr>
Router2#debug ip rip
RIP protocol debugging is on
Router2#
*Mar 17 22:57:39.842: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/1 (192.168.5.1)
*Mar 17 22:57:39.842: RIP: build update entries
*Mar 17 22:57:39.842:   network 192.168.1.0 metric 1
*Mar 17 22:57:39.842:   network 192.168.10.0 metric 2
*Mar 17 22:57:46.870: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.240)
*Mar 17 22:57:46.870: RIP: build update entries
*Mar 17 22:57:46.870:   network 192.168.5.0 metric 1
*Mar 17 22:57:53.654: RIP: received v1 update from 192.168.1.1 on FastEthernet0/0
*Mar 17 22:57:53.654:      192.168.10.0 in 1 hops
Router2#no debug ip rip

 

 

 

 

 

FRAME-RELAY NETWORK TYPE

Network-type:  Point-to-Multipoint

·         OSPF treats Point-to-Multipoint networks as a series of point-to-point links, mirroring the layer 2 topology.

·         Point-to-Multipoint networks don’t have DR/BDR relationships.

·         Point-to-Multipoint networks advertise /32 routes for all the frame-realy endpoints.

·         Point-to-Multipoint networks have Hello and Dead intervals of 30 seconds and 120 seconds respectively.

·         Point-to-Multipoint non-broadcast networks are very similar to point-to-multipoint networks except that they work over layer 2 topologies that have no broadcast capability

·         Point-to-Multipoint non-broadcast networks allow you to define cost on a per neighbor

POINT –TO MULTIPOINT  à   Diventano  NEIGHBOR solo mettendo “broadcast” nelle frame-relay-map

R1#sh ip osp ne

 

Neighbor ID     Pri   State           Dead Time   Address         Interface

3.3.3.3           0   FULL/  -        00:01:48    172.16.13.3     Serial0/0

2.2.2.2           0   FULL/  -        00:01:48    172.16.13.2     Serial0/0

 

R2#sh ip os neighbor

 

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           0   FULL/  -        00:01:52    172.16.13.1     Serial0/0

 

R3#sh ip osp neighbor

 

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           0   FULL/  -        00:01:59    172.16.13.1     Serial0/0 

 

 

ESEMPIO  (togliendo broadcast si perde la neighborship)

 

R1

interface Serial0/0

 ip address 172.16.13.1 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.2 102 broadcast

 frame-relay map ip 172.16.13.3 103 broadcast

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

router-id 1.1.1.1

network 0.0.0.0 255.255.255.255 area 0

 

 

R2

 

interface Serial0/0

 ip address 172.16.13.2 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 201 broadcast

 frame-relay map ip 172.16.13.3 201

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

 router-id 2.2.2.2

 network 0.0.0.0 255.255.255.255 area 0

 

R3

 

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301 broadcast

 frame-relay map ip 172.16.13.2 301

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

 router-id 3.3.3.3

network 0.0.0.0 255.255.255.255 area 0

 

R1#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

C       1.1.1.1 is directly connected, Loopback0

     2.0.0.0/32 is subnetted, 1 subnets

O       2.2.2.2 [110/65] via 172.16.13.2, 00:00:47, Serial0/0

     3.0.0.0/32 is subnetted, 1 subnets

O       3.3.3.3 [110/65] via 172.16.13.3, 00:00:47, Serial0/0

     172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks

C       172.16.13.0/29 is directly connected, Serial0/0

O       172.16.13.3/32 [110/64] via 172.16.13.3, 00:00:47, Serial0/0    -----> multipoint avvisa reti /32

O       172.16.13.2/32 [110/64] via 172.16.13.2, 00:00:49, Serial0/0    -----> multipoint avvisa reti /32

 

 

R2#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

O       1.1.1.1 [110/65] via 172.16.13.1, 00:01:09, Serial0/0

     2.0.0.0/32 is subnetted, 1 subnets

C       2.2.2.2 is directly connected, Loopback0

     3.0.0.0/32 is subnetted, 1 subnets

O       3.3.3.3 [110/129] via 172.16.13.1, 00:01:09, Serial0/0

     172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks

O       172.16.13.1/32 [110/64] via 172.16.13.1, 00:01:09, Serial0/0   -----> multipoint avvisa reti /32 

C       172.16.13.0/29 is directly connected, Serial0/0

O       172.16.13.3/32 [110/128] via 172.16.13.1, 00:01:11, Serial0/0  -----> multipoint avvisa reti /32  

 

 

 

R3#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

O       1.1.1.1 [110/65] via 172.16.13.1, 00:01:26, Serial0/0

     2.0.0.0/32 is subnetted, 1 subnets

O       2.2.2.2 [110/129] via 172.16.13.1, 00:01:26, Serial0/0

     3.0.0.0/32 is subnetted, 1 subnets

C       3.3.3.3 is directly connected, Loopback0

     172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks

O       172.16.13.1/32 [110/64] via 172.16.13.1, 00:01:26, Serial0/0    -----> multipoint avvisa reti /32

C       172.16.13.0/29 is directly connected, Serial0/0

O       172.16.13.2/32 [110/128] via 172.16.13.1, 00:01:28, Serial0/0   ----> multipoint avvisa reti /32

 

 

  

Network-type:  Point-to-Multipoint  NON BROADCAST 

 

Simile al Point-to-Multipoint,  NO DR, necessario “NEIGHBOR” sotto l’OSPF  dell’HUB

 

POINT –TO MULTIPOINT  à   Diventano NEIGHBOR solo  aggiungendo  “neighbor ” nel processo ospf (solo sull’HUB)  eliminare “broadcast” nelle frame-relay map

R1

interface Serial0/0

 ip address 172.16.13.1 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint non-broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.2 102

 frame-relay map ip 172.16.13.3 103

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

 router-id 1.1.1.1

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0

neighbor 172.16.13.3

neighbor 172.16.13.2

 

 

R2

interface Serial0/0

 ip address 172.16.13.2 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint non-broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 201

 frame-relay map ip 172.16.13.3 201

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

 router-id 2.2.2.2

network 0.0.0.0 255.255.255.255 area 0

 

  

R3

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint non-broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301

 frame-relay map ip 172.16.13.2 301

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

router-id 3.3.3.3

network 0.0.0.0 255.255.255.255 area 0

 

 

LE NETWORK TYPE MULTICAST (anche NON BROADCAST)    NON HANNO IL DR/BDR

 

R1#sh ip osp neighbor

 

Neighbor ID     Pri   State           Dead Time   Address         Interface

3.3.3.3           0   FULL/  -        00:01:31    172.16.13.3     Serial0/0

2.2.2.2           0   FULL/  -        00:01:31    172.16.13.2     Serial0/0

 

 

R2#sh ip osp neighbor

 

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           0   FULL/  -        00:01:37    172.16.13.1     Serial0/0

 

R3#sh ip ospf ne

 

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           0   FULL/  -        00:01:42    172.16.13.1     Serial0/0

 

 

 

R1#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

C       1.1.1.1 is directly connected, Loopback0

     2.0.0.0/32 is subnetted, 1 subnets

O       2.2.2.2 [110/65] via 172.16.13.2, 00:16:18, Serial0/0

     3.0.0.0/32 is subnetted, 1 subnets

O       3.3.3.3 [110/65] via 172.16.13.3, 00:16:18, Serial0/0

     172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks

C       172.16.13.0/29 is directly connected, Serial0/0

O       172.16.13.3/32 [110/64] via 172.16.13.3, 00:16:18, Serial0/0   -------> multipoint avvisa reti /32

O       172.16.13.2/32 [110/64] via 172.16.13.2, 00:16:20, Serial0/0  -------> multipoint avvisa reti /32

 

 

 

R2#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

O       1.1.1.1 [110/65] via 172.16.13.1, 00:16:48, Serial0/0

     2.0.0.0/32 is subnetted, 1 subnets

C       2.2.2.2 is directly connected, Loopback0

     3.0.0.0/32 is subnetted, 1 subnets

O       3.3.3.3 [110/129] via 172.16.13.1, 00:16:48, Serial0/0

     172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks

O       172.16.13.1/32 [110/64] via 172.16.13.1, 00:16:48, Serial0/0

C       172.16.13.0/29 is directly connected, Serial0/0

O       172.16.13.3/32 [110/128] via 172.16.13.1, 00:16:50, Serial0/0

 

 

R3#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

O       1.1.1.1 [110/65] via 172.16.13.1, 00:17:12, Serial0/0

     2.0.0.0/32 is subnetted, 1 subnets

O       2.2.2.2 [110/129] via 172.16.13.1, 00:17:12, Serial0/0

     3.0.0.0/32 is subnetted, 1 subnets

C       3.3.3.3 is directly connected, Loopback0

     172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks

O       172.16.13.1/32 [110/64] via 172.16.13.1, 00:17:12, Serial0/0

C       172.16.13.0/29 is directly connected, Serial0/0

O       172.16.13.2/32 [110/128] via 172.16.13.1, 00:17:13, Serial0/0

R3#

 

 

 

Network-type: Broadcast

 

BROADCAST  à   Diventano NEIGHBOR solo  aggiungendo  “broadcast” nelle frame-relay-map

 

interface Serial0/0

 ip address 172.16.13.1 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.2 102 broadcast

 frame-relay map ip 172.16.13.3 103 broadcast

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

router-id 1.1.1.1

network 0.0.0.0 255.255.255.255 area 0

 

R2

interface Serial0/0

 ip address 172.16.13.2 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 201 broadcast

 frame-relay map ip 172.16.13.3 201 broadcast

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

router-id 2.2.2.2

network 0.0.0.0 255.255.255.255 area 0

 

 

 

R3

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301 broadcast

 frame-relay map ip 172.16.13.2 301 broadcast

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

 router-id 3.3.3.3

network 0.0.0.0 255.255.255.255 area 0

 

 

 

R1#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

2.2.2.2           1   FULL/DROTHER    00:00:30    172.16.13.2     Serial0/0

3.3.3.3           1   FULL/DR                 00:00:30    172.16.13.3      Serial0/0

 

R2#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           1   FULL/BDR        00:00:38    172.16.13.1     Serial0/0

 

R3#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           1   FULL/BDR        00:00:39    172.16.13.1     Serial0/0

 

 

 

L’HUB DEVE ESSERE IL DR  à AGIRE SULLA PRIORITY SOTTO l’INTERFACCIA 

(priority 0 diventi DROTHER)

(priority 255 diventi DR)

 

 

 

PRIORITY    Si mette priority 0  sugli SPOKE     in modo che l’HUB sia il DR

 

 

 

R1#sh ip osp neighbor

Neighbor ID     Pri   State           Dead Time   Address         Interface

2.2.2.2           0   FULL/DROTHER    00:00:32    172.16.13.2     Serial0/0

3.3.3.3           0   FULL/DROTHER    00:00:31    172.16.13.3     Serial0/0

 

R2#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           1   FULL/DR         00:00:38    172.16.13.1     Serial0/0

R2

 

R3#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           1   FULL/DR         00:00:33    172.16.13.1     Serial0/0

R3#

 

 

R2

interface Serial0/0

 ip address 172.16.13.2 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network broadcast

 ip ospf priority 0

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 201 broadcast

 frame-relay map ip 172.16.13.3 201 broadcast

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

 

R3

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network broadcast

 ip ospf priority 0

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301 broadcast

 frame-relay map ip 172.16.13.2 301 broadcast

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

 

 

R1#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

C       1.1.1.1 is directly connected, Loopback0

     2.0.0.0/32 is subnetted, 1 subnets

O       2.2.2.2 [110/65] via 172.16.13.2, 00:06:23, Serial0/0

     3.0.0.0/32 is subnetted, 1 subnets

O       3.3.3.3 [110/65] via 172.16.13.3, 00:06:23, Serial0/0

     172.16.0.0/29 is subnetted, 1 subnets

C       172.16.13.0 is directly connected, Serial0/0

 

 

 

 

R2#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

O       1.1.1.1 [110/65] via 172.16.13.1, 00:11:18, Serial0/0

     2.0.0.0/32 is subnetted, 1 subnets

C       2.2.2.2 is directly connected, Loopback0

     3.0.0.0/32 is subnetted, 1 subnets

O       3.3.3.3 [110/65] via 172.16.13.3, 00:11:18, Serial0/0

     172.16.0.0/29 is subnetted, 1 subnets

C       172.16.13.0 is directly connected, Serial0/0

R2#

 

 

 

R3#sh ip route

Gateway of last resort is not set

 

     1.0.0.0/32 is subnetted, 1 subnets

O       1.1.1.1 [110/65] via 172.16.13.1, 00:11:58, Serial0/0

     2.0.0.0/32 is subnetted, 1 subnets

O       2.2.2.2 [110/65] via 172.16.13.2, 00:11:58, Serial0/0

     3.0.0.0/32 is subnetted, 1 subnets

C       3.3.3.3 is directly connected, Loopback0

     172.16.0.0/29 is subnetted, 1 subnets

C       172.16.13.0 is directly connected, Serial0/0

R3#

 

 

Summary:

·         For topologies where you have one hub, ensure the hub is the DR or use a network type that doesn’t require a DR

·         For topologies that have more than one hub, use a network type that doesn’t require a DR

·         In partial mesh topologies, the hubs should use a broadcast frame-relay map on DLCI’s to all connected spokes. This is to stop redundant broadcasts

·         In partial mesh topologies, the spokes should use a broadcast frame-relay map on DLCI’s to the hub only. This is to stop redundant broadcasts

 

 

Network type: Non broadcast

 

BROADCAST  à   Diventano NEIGHBOR solo  aggiungendo  “neighbor ” nel processo ospf (solo sull’HUB)  eliminare “broadcast” nelle frame-relay map

  

OSPF network type Non-Broadcast requires a DR, 

 

 

R1

interface Serial0/0

 ip address 172.16.13.1 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network non-broadcast

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.2 102

 frame-relay map ip 172.16.13.3 103

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

 router-id 1.1.1.1

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0

neighbor 172.16.13.2

neighbor 172.16.13.3

 

 

R2

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network non-broadcast

 serial restart-delay 0

 ip ospf priority 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301

 frame-relay map ip 172.16.13.2 301

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

 router-id 3.3.3.3

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0

 

 

R3

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network non-broadcast

 serial restart-delay 0

 ip ospf priority 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301

 frame-relay map ip 172.16.13.2 301

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

!

router ospf 1

 router-id 3.3.3.3

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0

 

 

 

Network type: Point-to-Point

·         OSPF Point-to-Point network are designed to be used when there is a single pair of routers on a network segment.

·         Point-to-Point networks don’t have DR/BDR relationships.

·         Point-to-Point networks have Hello and Dead intervals of 10 seconds and 40 seconds respectively.

·         OSPF Loopback Network Type is a special network type used on loopback interfaces only.

·         Loopback Network types are treated as a stub host in the OSPF routing domain, and are advertised as a /32 route by default.

·         We can change the network type of a loopback using the ip ospf network command. This allows us to advertise the route as something other than a /32 route.

  

The Point-to-Point network type does not require a DR to operate

  

R1

interface Serial0/0

ip address 192.168.1.1 255.255.255.0

encapsulation frame-relay

ip ospf network point-to-point

serial restart-delay 0

no dce-terminal-timing-enable

frame-relay map ip 192.168.1.2 102 broadcast

no frame-relay inverse-arp

!

router ospf 1

router-id 1.1.1.1

network 0.0.0.0 255.255.255.255 area 0

 

interface Serial0/0

 ip address 192.168.1.2 255.255.255.0

 encapsulation frame-relay

 ip ospf network point-to-point

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 192.168.1.1 201 broadcast

 no frame-relay inverse-arp

!

router ospf 1

 router-id 2.2.2.2

network 0.0.0.0 255.255.255.255 area 0

 

R1#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

2.2.2.2           0   FULL/  -        00:00:37    192.168.1.2     Serial0/0

 

R2#sh ip osp ne

Neighbor ID     Pri   State           Dead Time   Address         Interface

1.1.1.1           0   FULL/  -        00:00:34    192.168.1.1     Serial0/0

 

 

The default timers on a Point-to-Point link is 10 and 40 seconds for hello and dead intervals respectively . We can change this using the ip ospf hello-interval and ip ospf dead-interval commands. We will be taking a look at changing the default timers in our next article when we mix and match ospf network types.

 

 

 

R1

interface Serial0/0

 ip address 172.16.13.1 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.2 102 broadcast

 frame-relay map ip 172.16.13.3 103 broadcast

 frame-relay interface-dlci 102

 frame-relay interface-dlci 103

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

 router-id 1.1.1.1

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0

 neighbor 172.16.13.3

 neighbor 172.16.13.2

 

 

R2

 

interface Serial0/0

 ip address 172.16.13.2 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 201 broadcast

 frame-relay map ip 172.16.13.3 201 broadcast

 frame-relay interface-dlci 201

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

 router-id 2.2.2.2

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0

 

R3

 

interface Serial0/0

 ip address 172.16.13.3 255.255.255.248

 encapsulation frame-relay IETF

 ip ospf network point-to-multipoint

 serial restart-delay 0

 no dce-terminal-timing-enable

 frame-relay map ip 172.16.13.1 301 broadcast

 frame-relay map ip 172.16.13.2 301 broadcast

 frame-relay interface-dlci 301

 no frame-relay inverse-arp

 frame-relay lmi-type ansi

 

router ospf 1

 router-id 3.3.3.3

 log-adjacency-changes

 network 0.0.0.0 255.255.255.255 area 0