From: Philip Allen (philipallen@xxxxxxxxxxxx)
Date: Fri May 17 2002 - 05:51:07 GMT-3
Hi, thanks for the ideas nothing has worked so far though. I think the
RSVP reservation is being dropped for some reason but I cannot see why
as I believe the configuration etc is fine.
If I enter the command Show ip rsvp host sender or receiver on spoke 1
when a call is being placed from spoke 1 - spoke 2 I can see the session
but nothing shows up on spoke 2? A debug from one spoke 2 is below,
Phil
00:36:38: RSVP 155.100.123.3_18130-155.100.123.2_16580: Static
reservation is ne
w
00:36:38: RSVP-RESV: Locally created reservation. No admission/traffic
control n
eeded
00:36:38: RSVP session 155.100.123.3_18130: Sending PATH message for
155.100.123
.3 on interface Serial0/0
00:36:38: RSVP: version:1 flags:0000 type:PATH cksum:C983 ttl:255
reserved:0 len
gth:172
00:36:38: SESSION type 1 length 12:
00:36:38: Destination 155.100.123.3, Protocol_Id 17, Don't Police
, DstPor
t 18130
00:36:38: HOP type 1 length 12: 9B647B02
00:36:38: : 00000000
00:36:38: TIME_VALUES type 1 length 8 : 00007530
00:36:38: SENDER_TEMPLATE type 1 length 12:
00:36:38: Source 155.100.123.2, udp_source_port 16580
00:36:38: SENDER_TSPEC type 2 length 36:
00:36:38: version=0, length in words=7
00:36:38: Token bucket fragment (service_id=1, length=6 words
00:36:38: parameter id=127, flags=0, parameter length=5
00:36:38: average rate=3000 bytes/sec, burst depth=200 bytes
00:36:38: peak rate =3000 bytes/sec
00:36:38: min unit=0 bytes, max unit=0 bytes
00:36:38: ADSPEC type 2 length 84:
00:36:38: version=0 length in words=19
00:36:38: General Parameters break bit=0 service length=8
00:36:38: IS Hops:1
00:36:38: Minimum Path Bandwidth (bytes/sec):8000
00:36:38: Path Latency (microseconds):0
00:36:38: Path MTU:1500
00:36:38: Guaranteed Service break bit=0 service length=8
00:36:38: Path Delay (microseconds):3000
00:36:38: Path Jitter (microseconds):187500
00:36:38: Path delay since shaping (microseconds):3000
00:36:38: Path Jitter since shaping (microseconds):187500
00:36:38: Controlled Load Service break bit=0 service length=0
00:36:38:
00:36:43: RSVP 155.100.123.2_16580-155.100.123.3_18130: remove sender
host PATH
155.100.123.3(18130) <- 155.100.123.2(17:16580)
00:36:43: RSVP 155.100.123.2_16580-155.100.123.3_18130: remove sender
host PATH
155.100.123.3(18130) <- 155.100.123.2(17:16580)
00:36:43: RSVP session 155.100.123.3_18130: send path teardown multicast
about 1
55.100.123.3 on Serial0/0
00:36:43: RSVP: version:1 flags:0000 type:PTEAR cksum:E065 ttl:255
reserved:0 le
ngth:164
00:36:43: SESSION type 1 length 12:
00:36:43: Destination 155.100.123.3, Protocol_Id 17, Don't Police
, DstPor
t 18130
00:36:43: HOP type 1 length 12: 9B647B02
00:36:43: : 00000000
00:36:43: SENDER_TEMPLATE type 1 length 12:
00:36:43: Source 155.100.123.2, udp_source_port 16580
00:36:43: SENDER_TSPEC type 2 length 36:
00:36:43: version=0, length in words=7
00:36:43: Token bucket fragment (service_id=1, length=6 words
00:36:43: parameter id=127, flags=0, parameter length=5
00:36:43: average rate=3000 bytes/sec, burst depth=200 bytes
00:36:43: peak rate =3000 bytes/sec
00:36:43: min unit=0 bytes, max unit=0 bytes
00:36:43: ADSPEC type 2 length 84:
00:36:43: version=0 length in words=19
00:36:43: General Parameters break bit=0 service length=8
00:36:43: IS Hops:0
00:36:43: Minimum Path Bandwidth (bytes/sec):2147483647
00:36:43: Path Latency (microseconds):0
00:36:43: Path MTU:-1
00:36:43: Guaranteed Service break bit=0 service length=8
00:36:43: Path Delay (microseconds):0
00:36:43: Path Jitter (microseconds):0
00:36:43: Path delay since shaping (microseconds):0
00:36:43: Path Jitter since shaping (microseconds):0
00:36:43: Controlled Load Service break bit=0 service length=0
00:36:43:
00:36:43: RSVP 155.100.123.3_18130-155.100.123.2_16580: remove receiver
host RES
V 155.100.123.2(16580) <- 155.100.123.3(17:18130)
-----Original Message-----
From: Taimoor Husain [mailto:taimoor@cisco.com]
Sent: 17 May 2002 00:35
To: elpingu; Philip Allen
Cc: ccielab@groupstudy.com
Subject: RE: RSVP over Frame relay
Also something to add is that on the command ip rsvp bandwidth, the
first parameter is the total that voice calls can reserve and the second
is the maximum that each voice call (flow) can reserve. THe dial peer
configurations are correct but you need to make sure that the voip
dial-peers on both sides are configured for rsvp. Take into
consideration that rsvp cannot consider RTP header compression at this
time. Also make sure that you have call rsvp-sync command under global
config.
Regards,
------------------------------------------------------------------------
----
----
:|: :|: Taimoor Husain
:| | |: :| | |: CCIE # 9315
.:| | | | | | |:. .:| | | | | | |:. taimoor@cisco.com
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:59 GMT-3