Re: RSVP over Frame relay

From: elpingu (elping@xxxxxxxxxx)
Date: Thu May 16 2002 - 20:16:08 GMT-3


   
I setup rsvp with VIOP and these are my findings

make sure that the rsvp commands are in the interfaces that lead to your
other peer.the path via routing tables.and enable fairqueing

fair que

interface Serial0/0.7 point-to-point
 ip address 135.13.3.7 255.255.255.0
 frame-relay interface-dlci 52
 ip rsvp bandwidth 10 10 <--------------reseves bandwith

in order to see the sh rsvp reservations you must request it.so make a phone
call .and configure on what peer will request RSVP

specify on the peer to requst RSVP
dial-peer voice 11 voip
 destination-pattern 1111
 session target ipv4:11.11.11.11
 req-qos controlled-load <---------this request the rsvp resevation

Philip Allen wrote:

> Can any one please help with the following, basically I am trying to
> setup and test end to end VOIP with RSVP over frame relay, the voice
> call works fine but I cannot see any reservations using the command show
> ip rsvp installed etc? Any one have any ideas, config below.
>
> Thanks
>
> Phil
>
> HUB
> interface Serial0
> no ip address
> encapsulation frame-relay
> no arp frame-relay
> frame-relay traffic-shaping
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> ip rsvp bandwidth 1158 1158
>
> interface Serial0.1 multipoint
> ip address 155.100.123.1 255.255.255.0
> ip pim sparse-dense-mode
> ip ospf message-digest-key 1 md5 cisco
> no arp frame-relay
> frame-relay class rsvp
> frame-relay map ip 155.100.123.1 104
> frame-relay map ip 155.100.123.2 104 broadcast
> frame-relay map ip 155.100.123.3 105 broadcast
> no frame-relay inverse-arp
> ip rsvp bandwidth 350 350
>
> map-class frame-relay rsvp
> frame-relay cir 128000
> frame-relay mincir 64000
> no frame-relay adaptive-shaping
> frame-relay fair-queue
> frame-relay fragment 80
>
> SPOKE 1
>
> interface Serial0/0
> ip address 155.100.123.2 255.255.255.0
> ip pim sparse-dense-mode
> encapsulation frame-relay
> ip ospf message-digest-key 1 md5 cisco
> ip ospf priority 0
> no arp frame-relay
> frame-relay class rsvp
> frame-relay traffic-shaping
> frame-relay map ip 155.100.123.1 401 broadcast
> frame-relay map ip 155.100.123.2 401
> frame-relay map ip 155.100.123.3 401 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> ip rsvp bandwidth 350 350
>
> dial-peer voice 3001 pots
> destination-pattern 3001
> port 1/0/0
> !
> dial-peer voice 4001 voip
> destination-pattern 4001
> session target ipv4:155.100.123.3
> req-qos guaranteed-delay
> acc-qos guaranteed-delay
> ip precedence 5
>
> SPOKE 2
>
> interface Serial0/1
> ip address 155.100.123.3 255.255.255.0
> ip pim sparse-dense-mode
> encapsulation frame-relay
> ip ospf message-digest-key 1 md5 cisco
> ip ospf priority 0
> no arp frame-relay
> frame-relay traffic-shaping
> frame-relay class rsvp
> frame-relay map ip 155.100.123.1 501 broadcast
> frame-relay map ip 155.100.123.2 501 broadcast
> frame-relay map ip 155.100.123.3 501
> no frame-relay inverse-arp
> ip rsvp bandwidth 350 350
>
> dial-peer voice 4001 pots
> destination-pattern 4001
> port 1/0/0
> !
> dial-peer voice 3001 voip
> destination-pattern 3001
> req-qos guaranteed-delay
> acc-qos guaranteed-delay
> ip precedence 5
> session target ipv4:155.100.123.2



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:59 GMT-3