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

LOOPBACK /32 vs /24

LOOPBACK /32 vs /24

Many of you already know that usually when you advertise a Loopback interface into OSPF it is advertised with /32 netmask (one IP address) even if the IP address under Loopback interface is with a /24 netmask. If you checked my previous post, you’ll see at the end that I’m right, and the Lo0 address is advertised with /32 netmask.

But what if you have to advertised as a /24 subnet (task require or some testing) ? There is “dirty little trick” to do it. use IP OSPF NETWOTK POINT-TO-POINT

 

 

 

 

FREEK Frame Relay End To End Keepalive

frame-relay end-to-end keepalive mode

To enable Frame Relay end-to-end keepalives, use the frame-relay end-to-end keepalive mode map-class configuration command. To disable Frame Relay end-to-end keepalives, use the no form of this command.

frame-relay end-to-end keepalive mode {bidirectional | request | reply | passive-reply}

no frame-relay end-to-end keepalive mode

Syntax Description

bidirectional	Enables bidirectional mode.
request	Enables request mode.
reply	Enables reply mode.
passive-reply	Enables passive reply mode.

Defaults

When a Frame Relay end-to-end keepalive mode is enabled, default values depend on which mode is selected. For the meaning of the parameters, see the frame-relay end-to-end keepalive timer, frame-relay end-to-end keepalive event-window, frame-relay end-to-end keepalive error-threshold, and frame-relay end-to-end keepalive success-events commands.

Command Modes

Map-class configuration

Command History

Release	Modification
12.0(5)T	This command was introduced.

Usage Guidelines

To enable Frame Relay end-to-end keepalives, Frame Relay must be configured. In addition, a map-class must be associated and a DLCI assigned to an interface, subinterface, VC or PVC. For more information on associating a frame-relay class with an interface, subinterface, VC or PVC, see the frame-relay class command. For more information on assigning a DLCI to an interface, subinterface, VC or PVC, see the frame-relay interface-dlci command.

In bidirectional mode, both ends of a virtual circuit (VC) send keepalive requests and respond to keepalive requests. If one end of the VC is configured in the bidirectional mode, the other end must also be configured in the bidirectional mode.

In request mode, the router sends keepalive requests and expects replies from the other end of the VC. If one end of a VC is configured in the request mode, the other end must be configured in the reply or passive-reply mode.

In reply mode, the router does not send keepalive requests, but waits for keepalive requests from the other end of the VC and replies to them. If no keepalive request has arrived within the timer interval, the router times out and increments the error counter by 1. If one end of a VC is configured in the reply mode, the other end must be configured in the request mode.

In passive-reply mode, the router does not send keepalive requests, but waits for keepalive requests from the other end of the VC and replies to them. No timer is set when in this mode, and the error counter is not incremented. If one end of a VC is configured in the passive-reply mode, the other end must be configured in the request mode