RSVP Lab Guide

RSVP
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Contents
RSVP .............................................................................................................................................................. 3
RSVP Call Flow ........................................................................................................................................... 6
Diagram ......................................................................................................................................................... 6
Previous configuration .................................................................................................................................. 7
HQ IOS RSVP Configuration........................................................................................................................... 7
Task.- Configure a dspfarm profile for MTP .............................................................................................. 7
Task.- Validate status of MTP Registration ............................................................................................... 7
HQ CUCM RSVP Configuration ...................................................................................................................... 8
Task.- Create an MTP for HQ .................................................................................................................... 9
Task.- Create a MRG for HQ and associate the HQ MTP .......................................................................... 9
Task.- Create a MRG (HQ) for software resources (Optional) ................................................................ 10
Task.- Create a MRGL on HQ and associate MRG´s ................................................................................ 10
Task.- Associate MRGL to HQ Device Pool .............................................................................................. 12
Do the same for BRA Device ....................................................................................................................... 12
Task.- Create an MTP for BRA ................................................................................................................. 12
Task.- Create MRG for BRA1 and associate the BRA1 MTP .................................................................... 12
Task.- Create a MRGL for BRA1 and associate MRG´s (BRA1 and SW) ................................................... 12
Task.- Assocaite the MRGL of BRA1 to BRA1 Device Pool ...................................................................... 12
Configure the use of Mandatory RSVP ....................................................................................................... 12
Validation .................................................................................................................................................... 14
Task.- Make a phone call from BRA1 to HQ PHONE ............................................................................... 14
Troubleshooting .......................................................................................................................................... 14
Task.- Double check ALL the configuration (and maybe triple) but could not find anything ................. 14
Task.- Turn on debugs on the RSVP Agent .............................................................................................. 14
Task.- Nothing like good old ass traces to see if I can see something. ................................................... 14
Task.- Call again from HQ phone to BRA1 phone ................................................................................... 29
Useful tools to validate RSVP assignation ................................................................................................... 31
Voice Gateway ........................................................................................................................................ 31
RTMT ....................................................................................................................................................... 51
Homework................................................................................................................................................... 52
Facebook Group
RSVP
This chapter describes the tasks for configuring the Resource Reservation Protocol (RSVP) feature, which
is an IP service that allows end systems or hosts on either side of a router network to establish a
reserved-bandwidth path between them to predetermine and ensure QoS for their data transmission.
For a complete description of the RSVP commands in this chapter, refer to the Cisco IOS Quality of
Service Solutions Command Reference. To locate documentation of other commands that appear in this
chapter, use the command reference master index or search online.
To identify the hardware platform or software image information associated with a feature, use the
Feature Navigator on Cisco.com to search for information about the feature or refer to the software
release notes for a specific release. For more information, see the "Identifying Supported Platforms"
section in the "Using Cisco IOS Software" chapter in this book.
RSVP allows end systems to request QoS guarantees from the network. The need for network resource
reservations differs for data traffic versus for real-time traffic, as follows:
 Data traffic seldom needs reserved bandwidth because internetworks provide datagram services
for data traffic. This asynchronous packet switching may not need guarantees of service quality.
End-to-end controls between data traffic senders and receivers help ensure adequate
transmission of bursts of information.
 Real-time traffic (that is, voice or video information) experiences problems when operating over
datagram services. Because real-time traffic sends an almost constant flow of information, the
network "pipes" must be consistent. Some guarantee must be provided that service between
real-time hosts will not vary. Routers operating on a first-in, first-out (FIFO) basis risk
unrecoverable disruption of the real-time information that is being sent.
Data applications, with little need for resource guarantees, frequently demand relatively lower
bandwidth than real-time traffic. The almost constant high bit-rate demands of a video conference
application and the bursty low bit-rate demands of an interactive data application share available
network resources.
RSVP prevents the demands of traffic such as large file transfers from impairing the bandwidth
resources necessary for bursty data traffic. When RSVP is used, the routers sort and prioritize packets
much like a statistical time-division multiplexer (TDM) would sort and prioritize several signal sources
that share a single channel.
RSVP mechanisms enable real-time traffic to reserve resources necessary for consistent latency. A video
conferencing application can use settings in the router to propagate a request for a path with the
required bandwidth and delay for video conferencing destinations. RSVP will check and repeat
reservations at regular intervals. By this process, RSVP can adjust and alter the path between RSVP end
systems to recover from route changes.
Facebook Group
Real-time traffic (unlike data traffic) requires a guaranteed network consistency. Without consistent
QoS, real-time traffic faces the following problems:
 Jitter. A slight time or phase movement in a transmission signal can introduce loss of
synchronization or other errors.
 Insufficient bandwidth. Voice calls use a digital signal level 0 (DS-0 at 64 kbps), video
conferencing uses T1/E1 (1.544 Mbps or 2.048 Mbps), and higher-fidelity video uses
much more.
 Delay variations. If the wait time between when signal elements are sent and when they
arrive varies, the real-time traffic will no longer be synchronized and transmission may
fail.
 Information loss. When signal elements drop or arrive too late, lost audio causes
distortions with noise or crackle sounds. The lost video causes image blurring,
distortions, or blackouts.
RSVP works in conjunction with weighted fair queueing (WFQ) or Random Early Detection (RED). This
conjunction of reservation setting with packet queueing uses two key concepts: end-to-end flows with
RSVP and router-to-router conversations with WFQ:
 RSVP flow. This is a stream that operates "multidestination simplex," because data travels across
it in only one direction: from the origin to the targets. Flows travel from a set of senders to a set
of receivers. The flows can be merged or left unmerged, and the method of merging them varies
according to the attributes of the application using the flow.
 WFQ conversation. This is the traffic for a single transport layer session or network layer flow
that crosses a given interface. This conversation is identified from the source and destination
address, protocol type, port number, or other attributes in the relevant communications layer.
RSVP allows for hosts to send packets to a subset of all hosts (multicasting). RSVP assumes that resource
reservation applies primarily to multicast applications (such as video conferencing). Although the
primary target for RSVP is multimedia traffic, a clear interest exists for the reservation of bandwidth for
unicast traffic (such as Network File System (NFS) and virtual private network management). A unicast
transmission involves a host sending packets to a single host.
Facebook Group
For more information about RSVP, see the section "Resource Reservation Protocol" in the chapter
"Signalling Overview" in this book.
RSVP cannot be configured with VIP-distributed Cisco Express Forwarding (dCEF).
RSVP Reservation Types
These are the two types of multicast flows:
•Distinct reservation. This constitutes a flow that originates from exactly one sender.
•Shared reservation. This constitutes a flow that originates from one or more senders.
RSVP describes these reservations as having certain algorithmic attributes.
Distinct Reservation
An example of a distinct reservation is a video application in which each sender emits a distinct data
stream that requires admission and management in a queue. Such a flow, therefore, requires a separate
reservation per sender on each transmission facility it crosses (such as Ethernet, a High-Level Data Link
Control (HDLC) line, a Frame Relay data-link connection identifier (DLCI), or an ATM virtual channel).
RSVP refers to this distinct reservation as explicit and installs it using a Fixed Filter style of reservation.
Use of RSVP for unicast applications is generally a degenerate case of a distinct flow.
Shared Reservation
An example of a shared reservation also is an audio application in which each sender emits a distinct
data stream that requires admission and management in a queue. However, because of the nature of
the application, a limited number of senders are sending data at any given time. Such a flow, therefore,
does not require a separate reservation per sender. Instead, it uses a single reservation that can be
applied to any sender within a set as needed.
RSVP installs a shared reservation using a Wild Card or Shared Explicit style of reservation, with the
difference between the two determined by the scope of application (which is either wild or explicit):
Facebook Group
•The Wild Card Filter reserves bandwidth and delay characteristics for any sender and is limited by the
list of source addresses carried in the reservation message.
•The Shared Explicit style of reservation identifies the flows for specific network resources.
RSVP Call Flow
Note: As soon as the Setup message is send to initiate the call, the CUCM initiate the RSVP allocate
process.
Diagram
Facebook Group
MPLS
Cl uster 1
Pub lish er – IP1
Do main1.com
HQ_ROUTER
BRAN CH1_ROUTER
PSTN
IP
IP
1XXX Device Pool Device Pool
DP_HQ DP_BRA1 2XXX
Previous configuration
 Have 2 Device pools (one for each device pool)
 Have 2 Locations configured (one for each device pool)
 Have at least 2 phones configured with a device pool belonging to each device pool
HQ IOS RSVP Configuration

Task.- Configure a dspfarm profile for MTP
sccp local GigabitEthernet0/1
sccp ccm 192.168.13.248 identifier 1 priority 1 version 7.0
sccp
sccp ccm group 1
associate ccm 1 priority 1
associate profile 1 register HQ_MTP_RSVP
dspfarm profile 1 mtp
codec g711ulaw
codec pass-through
rsvp
maximum sessions software 10
associate application SCCP
Task.- Validate status of MTP Registration
Facebook Group
SAF_FORWARDER_2#show sccp
SCCP Admin State: UP
Gateway Local Interface: GigabitEthernet0/0
IPv4 Address: 192.168.13.241
Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 192.168.13.248, Port Number: 2000
Priority: 1, Version: 7.0, Identifier: 1
MTP Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED
Active Call Manager: 192.168.13.248, Port Number: 2000
TCP Link Status: NOT_CONNECTED, Profile Identifier: 1
Reported Max Streams: 20, Reported Max OOS Streams: 0
Supported Codec: pass-thru, Maximum Packetization Period: N/A
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30
RSVP : ENABLED
TLS : ENABLED
HQ CUCM RSVP Configuration
Facebook Group
Task.- Create an MTP for HQ
Task.- Create a MRG for HQ and associate the HQ MTP
Facebook Group
Task.- Create a MRG (HQ) for software resources (Optional)
Task.- Create a MRGL on HQ and associate MRG´s
Facebook Group
Facebook Group
Task.- Associate MRGL to HQ Device Pool
Do the same for BRA Device

Task.- Create an MTP for BRA
If you need help, check how it was done on HQ on previous steps
Task.- Create MRG for BRA1 and associate the BRA1 MTP
Task.- Create a MRGL for BRA1 and associate MRG´s (BRA1 and SW)
Task.- Assocaite the MRGL of BRA1 to BRA1 Device Pool

At this point we just have 2 phones on 2 different device pools and locations and have configured an
MTP with RSVP capabilities. Now lets move to the RSVP part.
Configure the use of Mandatory RSVP

This is where we are going to configure the policy for use RSVP on each call between locations. Go to:
CM Administration > System > Location info > Location, click on HQ location
Facebook Group
On the RSVP Settings, select “Mandatory” so each call MUST use an RSVP resource.
Note: If you configure a policy between HQ and BRA1, you don’t need to do the same for BRA1 as this
configuration is bidirectional. 
Facebook Group
Validation
Task.- Make a phone call from BRA1 to HQ PHONE
“Not enough bandwith” NOW its time to troubleshoot!
Troubleshooting
Task.- Double check ALL the configuration (and maybe triple) but could not find anything
Task.- Turn on debugs on the RSVP Agent
I turn the debug “debug ip rsvp all” and I was not getting any message (YES! I configured “terminal
monitor” in case you were asking) but I got no messages… that means that the call is stucking in the
CUCM, let´s go to the next step.
Task.- Nothing like good old ass traces to see if I can see something.
Traces from Call Manager service
++++++++++++++++++++++++++++++++++++++++++++++++++
|CallingPartyNumber=2002
Facebook Group
|DialingPartition=
|DialingPattern=1002
|FullyQualifiedCalledPartyNumber=1002
|DialingPatternRegularExpression=(1002)
|DialingWhere=
|PatternType=Enterprise
|PotentialMatches=NoPotentialMatchesExist
|DialingSdlProcessId=(0,0,0)
|PretransformDigitString=1002
|PretransformTagsList=SUBSCRIBER
|PretransformPositionalMatchList=1002
|CollectedDigits=1002
|UnconsumedDigits=
|TagsList=SUBSCRIBER
|PositionalMatchList=1002
|VoiceMailbox=
|VoiceMailCallingSearchSpace=
|VoiceMailPilotNumber=
|RouteBlockFlag=RouteThisPattern
|RouteBlockCause=0
|AlertingName=HQ - 1002
|UnicodeDisplayName=HQ - 1002
|DisplayNameLocale=1
|OverlapSendingFlagEnabled=0
|WithTags=
|WithValues=
|CallingPartyNumberPi=NotSelected
|ConnectedPartyNumberPi=NotSelected
|CallingPartyNamePi=NotSelected
Facebook Group
|ConnectedPartyNamePi=NotSelected
|CallManagerDeviceType=NoDeviceType
|PatternPrecedenceLevel=Routine
|CallableEndPointName=[29df6af2-8b20-c88f-9660-d5a44041e1e6]
|PatternNodeId=[29df6af2-8b20-c88f-9660-d5a44041e1e6]
|AARNeighborhood=[]
|AARDestinationMask=[]
|AARKeepCallHistory=true
|AARVoiceMailEnabled=false
|NetworkLocation=OnNet
|Calling Party Number Type=Cisco Unified CallManager
|Calling Party Numbering Plan=Cisco Unified CallManager
|Called Party Number Type=Cisco Unified CallManager
|Called Party Numbering Plan=Cisco Unified CallManager
|ProvideOutsideDialtone=false
|AllowDeviceOverride=false
|IsEmergencyNumber=false
|AlternateMatches= Information Not Available
|TranslationPatternDetails= Information Not Available
|ResourcePriorityNamespace=
|PatternRouteClass=RouteClassDefault
00868338.000 |18:10:13.893 |SdlSig |DmPidReq |initialized

|DeviceManager(1,100,210,1) |Da(1,100,216,1)
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[T:N-H:0,N:0,L:0,V:0,Z:0,D:0] Cepn=29df6af2-
8b20-c88f-9660-d5a44041e1e6 Id=3882843384
00868338.001 |18:10:13.893 |AppInfo |SMDMSharedData::findAliasRegInfo - AliasName = 29df6af2-

8b20-c88f-9660-d5a44041e1e6 not in AliasInfo hashmap
00868338.002 |18:10:13.893 |AppInfo |DeviceManager::star_DmPidReq - RequestedName=29df6af2-

8b20-c88f-9660-d5a44041e1e6 LookupName=29df6af2-8b20-c88f-9660-d5a44041e1e6
00868338.003 |18:10:13.893 |AppInfo |SMDMSharedData::findLocalDevice - Name=1002:

Key=29df6af2-8b20-c88f-9660-d5a44041e1e6 isActvie=1 Pid=(1,178,6) found
Facebook Group
00868339.000 |18:10:13.893 |SdlSig |DmPidRes |wait |Da(1,100,216,1)
|DeviceManager(1,100,210,1) |1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-
H:0,N:0,L:0,V:0,Z:0,D:0] Cepn=29df6af2-8b20-c88f-9660-d5a44041e1e6 Id=3882843384 ccmType=4
DeviceName=1002: Pid=1,100,178,6,ad243d17-98b4-4118-8feb-5ff2e1b781ac
00868339.001 |18:10:13.893 |AppInfo |Digit analysis: wait_DmPidRes- Partition=[] Pattern=[1002]

Where=[],cmDeviceType=[UserDevice], OutsideDialtone =[0], DeviceOverride=[0],
PID=LineControl(1,100,178,6),CI=[29835979],Sender=Cdcc(1,100,224,74)
00868340.000 |18:10:13.894 |SdlSig |DaRes |setup_da

|Cdcc(1,100,224,74) |Da(1,100,216,1)
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:0,L:0,V:0,Z:0,D:0] CI=29835979 Dial
NoPotentialMatchesExist OnNet PretransformCgpn=tn=0npi=0ti=1nd=2002pi=0si0
Cgpn=tn=0npi=0ti=1nd=2002pi=0si0 DialingPartition= DialingPattern=1002 DialingRPRE=(1002)
PID=(1,178,6) PretransformCdpn=tn=0npi=0ti=1nd=1002pi=0si0 PretransformTags=SUBSCRIBER
PretransformPos=1002 CollectedDigits=tn=0npi=0ti=1nd=1002pi=0si0 Tags=SUBSCRIBER Pos=1002
CalledPartyDevicePoolPkid=c47b732e-8966-8685-a9a1-808040408cf7 eccTransactionId=0
isCdpnNonPreemptable=F isCgpnNonPreemptable=FpatternUsage =2requestID =0
00868340.001 |18:10:13.894 |AppInfo |processCCMFeatureData: operationIeIdd=0
00868340.002 |18:10:13.894 |AppInfo |findUnfiredInterceptOnPattern numOfPatterns = 0
00868341.000 |18:10:13.894 |SdlSig |CcProceedReq |restart0

|LineControl(1,100,178,7) |Cdcc(1,100,224,74)
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] CI=29835979
CI.branch=0 lPart= lPatt=2002 lModNum=tn=0npi=0ti=1nd=2002pi=1si1 lName=locale: 1 Name: BRA1 -
2002 UnicodeName: BRA1 - 2002 pi: 1 cName=locale: 1 Name: HQ - 1002 UnicodeName: HQ - 1002 pi: 0
cn:tn=0npi=0ti=1nd=1002pi=1si1 cVMbox= localPatternUsage=2 connectedPatternUsage=2 lCnPart=
lCnPatt=1002 rn:tn=0npi=0ti=1nd=1002pi=0si1 lLRPart= lLRPatt=1002 lOCdpnPart= lOCdpnPatt=1002
oCdpn:tn=0npi=0ti=1nd=1002pi=0si1 oRFR =0 lBridgePartID= lCnBridgePartID= DevCEPN=a2134bbc-
4910-76e8-9997-58690d6ed5f6 lineCEPN=917dd1f9-a378-3abf-e40e-b87e9e134e0d
CnDevCEPN=29df6af2-8b20-c88f-9660-d5a44041e1e6 cnCEPN=29df6af2-8b20-c88f-9660-
d5a44041e1e6 lrnCEPN=29df6af2-8b20-c88f-9660-d5a44041e1e6 oCdpnCEPN=29df6af2-8b20-c88f-
9660-d5a44041e1e6 lHPMemCEPN= cHPMemCEPN= ctiActive=F ctiFarEndDev=0 ctiCCMId=0
isAnnMohResourceInsertedAtParty =F media=1 isOffNetDev=F cmDeviceType=4 locPkid= locName=
deductBW=F fateShareId= videoTrafficClass=UnspecifiedSupp DTMF=0DTMF Cfg=1DTMF Payload=0 Orig
DD=tn=0npi=1ti=1nd=1002pi=0si1TransparentData=null CanSupportSIPTandN=false TransId=0
AllowBitMask=0x0 UserAgentOrServer= OrigDDName=locale: 1 Name: UnicodeName: pi: 0 mCallerId=
mCallerName= TrustRxId=TbibEnabled=0 isCgpnNonPreemptable=F isCdpnNonPreemptable=F
00868341.001 |18:10:13.894 |AppInfo |LineControl - restert0_CcProceedReq updated precedence of

CI=29835979 to 5
00868342.000 |18:10:13.894 |SdlSig |PolicyAndCACAssociateReq |wait

|ReservationMgr(1,100,113,1) |Cdcc(1,100,224,74)
Facebook Group
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] CI= 29835979
aCI=29835979 bCI=29835980 isASerCI=F isBSerCI=F sendResp=T mcNodeId=0 sideAnp=F sideBnp=F
00868343.000 |18:10:13.894 |SdlSig |CcProceedReq |call_initiated1

|LineCdpc(1,100,179,146) |LineControl(1,100,178,7)
00868343.001 |18:10:13.894 |AppInfo |LineCdpc(146): -dispatchToAllDevices-,

sigName=CcProceedReq, device=SEPBC16F517B8C8
00868344.000 |18:10:13.894 |SdlSig |CACAssociateReq |await_associate

|RSVPSession(1,100,110,74) |ReservationMgr(1,100,113,1)
aCI=29835979 bCI=29835980 isASerCI=F isBSerCI=F sendResp=F mcNodeId=0 sideAnp=F sideBnp=F
00868345.000 |18:10:13.894 |SdlSig |PolicyAndCACAssociateRes |wait

|Cc(1,100,225,1) |ReservationMgr(1,100,113,1)
00868346.000 |18:10:13.894 |SdlSig |CcProceedReq |restart0

|StationD(1,100,66,7) |LineCdpc(1,100,179,146)
Facebook Group
00868347.000 |18:10:13.894 |SdlSig |PolicyAndCACAssociateRes |tcc_register_party_b

|Cdcc(1,100,224,74) |Cc(1,100,225,1)
00868347.001 |18:10:13.894 |AppInfo |Cdcc - CcsetupReq - fCcSetupReq.bc.l=3,

fCcSetupReq.bc.uil1p=2, fCcSetupReq.bc.ur=0,
fCcSetupReq.bc.sa=0,ir=0,notx=0,norx=0,fcotx=0,fcorx=0,nosb=0,nodb=0,parity=0
00868347.002 |18:10:13.894 |AppInfo |Cdcc::sendCcSetupReq: precLvl=5
00868348.000 |18:10:13.894 |SdlSig |CcProceedReq |call_initiated1

|StationCdpc(1,100,67,146) |StationD(1,100,66,7)
00868348.001 |18:10:13.894 |AppInfo |StationCdpc: CcProceedReq -

unicodeConnectedUnicodeDisplayName='HQ - 1002' asciiConnectedDisplayName='HQ - 1002'
00868348.002 |18:10:13.894 |AppInfo |StationCdpc: CcProceedReq -

unicodeCallingPartyName='BRA1 - 2002' asciiCallingPartyName='BRA1 - 2002' callingParty='2002'
unicodeCalledPartyName='HQ - 1002' asciiCalledPartyName='HQ - 1002' calledParty='1002'
00868349.000 |18:10:13.894 |SdlSig |CcSetupReq |restart0

|LineControl(1,100,178,6) |Cdcc(1,100,224,74)
CI.branch=0 sBPL.plid=65 sBPL.l=1 sBPL.pl=5 sBPL.msd=0 FDataType=0 opId=0 ssType=0 SsKey=0
invokeId=0 resultExp=F bpda=F pi.piid=30 pi.l=0 pi2.piid=30 pi2.l=0 pi3.piid=30 pi3.l=0
Facebook Group
FQCGPN=ti=1nd=2002pi=0si1 preXCgpn=tn=0npi=0ti=1nd=2002pi=0si0 cgPart= cgPat=2002
cgpn=tn=0npi=0ti=1nd=2002pi=1si1 cgpnVM= unXCgpn=tn=0npi=0ti=1nd=2002pi=1si0 cName=locale: 1
Name: BRA1 - 2002 UnicodeName: BRA1 - 2002 pi: 1 DD=tn=0npi=1ti=1nd=1002pi=0si1
origDD=tn=0npi=1ti=1nd=1002pi=0si1 preXCdpn=tn=0npi=0ti=1nd=1002pi=0si0
preXTagsList=SUBSCRIBER preXPosMatchList=1002 cdPart= cdPat=1002
cdpn=tn=0npi=0ti=1nd=1002pi=1si1 cdpnVMbox= localPatternUsage=2 connectedPatternUsage=2
itrPart= itrPat= LRPart= LRPat=1002 LR=tn=0npi=0ti=1nd=1002pi=0si1 LRVM= LRName=locale: 1 Name:
HQ - 1002 UnicodeName: HQ - 1002 pi: 0 FQOCpdn=ti=1nd=1002pi=0si1 fFQLRNum=ti=1nd=1002pi=0si1
oPart= oPat=1002 oCpdn=tn=0npi=0ti=1nd=1002pi=0si1 oCdpnVM= oRFR=0 oName=locale: 1 Name: HQ
- 1002 UnicodeName: HQ - 1002 pi: 0 ts=SUBSCRIBER posMatches=1002 withTags= withValues=
rdn.l=0IpAddrMode=0 ipAddrType=0 ipv4=192.168.13.84:0 region=RG_BRA1 capCount=12 ctiActive=F
ctiFarEndDev=1 ctiCCMId=1 cgPtyDev=SEPBC16F517B8C8 callInst=0 confCallInst=0 OLF=1Supp
DTMF=3DTMF Cfg=1DTMF Payload=0isOffNetDev=F bc.l=3 bc.itr=1 bc.itc=0 bc.trm=0 bc.tm=4
maxForwards=70 cgpnMaskedByRedirect=F callingDP=6a8a6eb2-f354-3db2-4a76-d29bc5104a40
featCallType=0 callingUserId= UnicodeName: muteEnabled=0 associatedCallCI=0 featurePriority=1
nonTargetPolicy=0 unconsumedDigits= suppressMOH=F numPlanPkid =29df6af2-8b20-c88f-9660-
d5a44041e1e6 networkDomain= bitMask=0 SetupReason=0 routeClass=1 LmSyncAlertingCallType=0
sideACmDeviceType=4 protected=1 ControlProcessType=0 tokens=0 isPresent=F transitCount=0
geolocInfo={geolocPkid=, filterPkid=, geolocVal=, devType=4} locPkid=11e5cc1e-20bd-eb48-86b2-
718d43a07288 locName=LC_BRA1 deductBW=F fateShareId=Cluster1:29835979
videoTrafficClass=Unspecified oFromAnalogDvc=F bridgeParticipantID= callingUsr= remoteClusterID=
isEMCCDevice=F lHPMemCEPN= cHPMemCEPN= isParamSet=FTransparentData=null
CanSupportSIPTandN=false TransId=0 AllowBitMask=0x0 UserAgentOrServer= OrigDDName=locale: 1
Name: UnicodeName: pi: 0 mCallerId= mCallerName= TrustRxId=TLatentCaps=null icidVal=
icidGenAddr= oioi= tioi= ptParams= receivedPAID= routeHdr= routeCepn= requestURI=
routeHeaderURI=pi=0si1 PCVFlag=F originallyHadISUP=F isIMSFinalRoute=F IMSMode=0
SideABibEnabled= 0 isCgpnNonPreemptable=F isCdpnNonPreemptable=F origDP=c47b732e-8966-8685-
a9a1-808040408cf7 lastRedirectingDP=c47b732e-8966-8685-a9a1-808040408cf7 originalLRG=
lastRedirectingLRG= nwLoc=0 rstr= FarEndDeviceName=SEPBC16F517B8C8 ReferredByUri= Session-ID:
;remote=a2134bbc491076e8999758690d6edba0 hdrMOH=0 CAL={v=ffffffff, m=ffffffff, tDev=F, res=F,
devType=0}
00868349.001 |18:10:13.894 |AppInfo |LineControl(6) - 0 calls, 0 CiReq, busyTrigger=2, maxCall=4
00868349.002 |18:10:13.894 |Created | |

|LineCdpc(1,100,179,147) |LineControl(1,100,178,6) |
|NumOfCurrentInstances: 2
00868349.003 |18:10:13.894 |AppInfo |LineControl(6) - Get call instance=1 for CI=29835980
00868349.004 |18:10:13.894 |AppInfo |LineControl(6): restart0_CcSetupReq update State of cdpc

(147) to receive7
00868350.000 |18:10:13.894 |SdlSig |StationOutputDialedNumber |restart0

|StationD(1,100,66,7) |StationCdpc(1,100,67,146)
Facebook Group
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:4,L:0,V:0,Z:0,D:0]
DialedNumber=1002 Line=1 CI=29835979
00868350.001 |18:10:13.894 |AppInfo |StationD: (0000007) DialedNumber dialedNumber=1002

lineInstance=1 callReference=29835979.
00868351.000 |18:10:13.894 |SdlSig |StationOutputCallState |restart0

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:3,L:0,V:0,Z:0,D:0] State=12 privacy=0
Line=1 CI=29835979 SCCP P-level=4 P-Domain=0
00868351.001 |18:10:13.894 |AppInfo |StationD: (0000007) CallState callState=12 lineInstance=1

callReference=29835979 privacy=0 sccp_precedenceLv=4 precedenceDm=0
00868352.000 |18:10:13.894 |SdlSig |StationOutputCallInfo |restart0

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:2,L:0,V:0,Z:0,D:0] cdpn="1002"
cdpnVMB="" cdpnParty="locale: 1 Name: HQ - 1002 UnicodeName: HQ - 1002 pi: 0" cgpn="2002"
cgpnVMB="" cgpnParty="locale: 1 Name: BRA1 - 2002 UnicodeName: BRA1 - 2002 pi: 1" oCdpn="1002"
oCdpnVMb="" oCdpnParty="locale: 1 Name: HQ - 1002 UnicodeName: HQ - 1002 pi: 0"
OCdpnReason="0" lCdpn="1002" lCdpnVMb="" lCdpnParty="locale: 1 Name: HQ - 1002 UnicodeName:
HQ - 1002 pi: 0" lCdpnReason="0" line="1" CI="29835979" callInstance="1" callType="2"
CallSecurityStatusType="0" restrictionBits="0" huntPilot="" huntPilotParty="locale: 1 Name:
UnicodeName: pi: 0"
00868352.001 |18:10:13.894 |AppInfo |StationD: (0000007) (1,100,14,409) CallInfo

callingPartyName='BRA1 - 2002' callingParty=2002 cgpnVoiceMailbox=
alternateCallingParty= calledPartyName='HQ - 1002' calledParty=1002
cdpnVoiceMailbox= originalCalledPartyName='HQ - 1002' originalCalledParty=1002
originalCdpnVoiceMailbox= originalCdpnRedirectReason=0
lastRedirectingPartyName='HQ - 1002' lastRedirectingParty=1002 lastRedirectingVoiceMailbox=
lastRedirectingReason=0 callType=2(OutBound) lineInstance=1
callReference=29835979. version: 85720016
00868353.000 |18:10:13.894 |SdlSig |DSetCallState |restart0

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] CallState =
outgoing_call_proceeding3
00868353.001 |18:10:13.894 |AppInfo |StationD: (0000007) DEBUG- star_DSetCallState(6) State of

cdpc(146) is 4.
00868354.000 |18:10:13.894 |SdlSig |CcSetupReq |null0

|LineCdpc(1,100,179,147) |LineControl(1,100,178,6)
Facebook Group
devType=0}
00868354.001 |18:10:13.894 |AppInfo |LineCdpc(147): -dispatchToAllDevices-, sigName=CcSetupReq,

device=SEPCAFECAFECAFE
00868355.000 |18:10:13.894 |SdlSig |CcSetupReq |restart0

|StationD(1,100,66,6) |LineCdpc(1,100,179,147)
Facebook Group
devType=0}
00868355.001 |18:10:13.894 |AppInfo |CcmCcmdbHelper::setRecordingInfo - Preffered

recordingMethod = 1
00868355.002 |18:10:13.894 |AppInfo |StationD - adding linestruct at index 1
00868355.003 |18:10:13.894 |AppInfo |StationD: (0000006) DEBUG whatToDo: line=1 calls=0 limit=4,
busy=2. GCI=(1, 74), cm_PL=(5, 0).
00868355.004 |18:10:13.894 |AppInfo |StationD: (0000006) DEBUG whatToDo: busy trigger not hit...
send to open appearance
00868355.005 |18:10:13.895 |AppInfo |preFilterCapCount =[11], preFilterCaps :: (Cap)= (89) (4) (2) (86)
(7) (6) (11) (12) (15) (16) (257) No cap to filter postFilterCapCount =[11], postFilterCaps :: (Cap)= (89) (4)
(2) (86) (7) (6) (11) (12) (15) (16) (257)
00868355.006 |18:10:13.895 |AppInfo |preFilterCapCount =[0], preFilterCaps :: (Cap)= No cap to filter

postFilterCapCount =[0], postFilterCaps :: (Cap)=
Facebook Group
00868355.007 |18:10:13.895 |Created | |
|StationCdpc(1,100,67,147) |StationD(1,100,66,6) |
00868355.008 |18:10:13.895 |AppInfo |StationD: (0000006) DEBUG- getLineRingSetting: retVal=4.
00868355.009 |18:10:13.895 |AppInfo |StationD: (0000006) DEBUG- saveRinger for: ci=29835980,

line=1, mode=2, cm_precedence=5, callPhase=5.
00868355.010 |18:10:13.895 |AppInfo |StationD: (0000006) DEBUG- saveRinger: ci=29835980,

line=1, mode=2, cm_precedence=5, callPhase=5, modifier=0
00868355.011 |18:10:13.895 |AppInfo |StationD: (0000006) INFO sendCallAcceptReq: Try to send

StationLineCallAccept to cdpc=147 .
00868355.012 |18:10:13.895 |AppInfo |StationD: (0000006) playRinger for: ci=29835980.
00868356.000 |18:10:13.895 |SdlSig |CcSetupReq |null0

Facebook Group
devType=0}
00868356.001 |18:10:13.895 |AppInfo |DET-RegionsServer::matchCapabilities-- savedOption=0,

PREF_NONE, regionA=RG_BRA1 regionB=RG_HQ latentCaps(A=0, B=0) kbps=8, capACount=12,
capBCount=11
00868356.002 |18:10:13.895 |AppInfo |Locations_getLocPKIDAndName -- loc= 2; pkid= 8c951eb4-

28c1-edf2-21d7-e8344f4842f7; Name = LC_HQ
00868357.000 |18:10:13.895 |SdlSig |StationLineCallAccept |await_rsvp_reg_res

00868358.000 |18:10:13.895 |SdlSig-S |StationLineCallAccept |await_rsvp_reg_res

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |
00868359.000 |18:10:13.895 |SdlSig |StationOutputSetRinger |await_rsvp_reg_res

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:3,L:0,V:0,Z:0,D:0] Mode=InsideRing
Duration=Normal Line=1 CI=29835980
00868360.000 |18:10:13.895 |SdlSig-S |StationOutputSetRinger |await_rsvp_reg_res

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:2,L:0,V:0,Z:0,D:0] CallState = null0

cdpc(147) is 0.
00868362.000 |18:10:13.895 |SdlSig |PolicyAndCACRegisterReq |wait

|ReservationMgr(1,100,113,1) |StationCdpc(1,100,67,147)
Branch= 0 reg=RG_HQ cap=11 loc=2 MRGLPkid=48435ae2-f94e-e58c-f21e-e86e6ef56b1b PrecLev=5
bearerlessCall=F VCall=F MMCap=0x1 VCapCount=0 regiState=0 medReq=0 IsEmccD=F EmccDName=
Facebook Group
rcId= ipMode=0 eoType=0 getPort=T sRTP=F cryptocap=0 tm=4 DTMF(wantRecep=0 provOOB=0
suppMeth=3 Cfg=1 PT=0 reqMed=1) honorCodec=F distMed=F mediaEP=F rsvpQoSType=0
qosFallback=F status=0 sipOfferNeededInd=F hasSDP=FLatentCaps=null videoTrafficClass=0
nonPreemptable=F geolocInfo={geolocPkid=, filterPkid=, geolocVal=, devType=4} CAL={v=-1, m=-1,
tDev=F, res=F, devType=0} locPkid=8c951eb4-28c1-edf2-21d7-e8344f4842f7 locName=LC_HQ
deductBW=F fateShareId=Cluster1:29835980 videoTrafficClass=Unspecified lbmCACInfo:
retryVideoAsAudio=T overrideRegionBW=F sideACmDeviceType=0 isNewPartyRegWithLBM=F
videoReservedKbps=0 cacSpecificInfo.cacPartyState=0
00868362.001 |18:10:13.895 |AppInfo |ReservationMgr::wait_PolicyAndCACRegisterReq, Entries= 1,

svcp::ConfidentialAccessLevelPolicy.get() = 0

|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[R:N-H:0,N:1,L:0,V:0,Z:0,D:0] CallState =
await_rsvp_reg_res

cdpc(147) is 0.
00868364.000 |18:10:13.895 |SdlSig |CACAssociateReq |connecting

|LBMInterface(1,100,180,1) |ReservationMgr(1,100,113,1)
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[T:N-H:0,N:1,L:0,V:0,Z:0,D:0] CI= 29835979
00868364.001 |18:10:13.895 |AppInfo |LBMIF: CI: 29835979 ASSOC 29835980
00868364.002 |18:10:13.895 |AppInfo |LBMIF: CI: 29835980 ASSOC' 29835979
00868365.000 |18:10:13.895 |SdlSig |LBMRegisterReq |connecting

|LBMInterface(1,100,180,1) |ReservationMgr(1,100,113,1)
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |[T:N-H:0,N:0,L:0,V:0,Z:0,D:0] ci=29835980
location=2 locName=LC_HQ locPkid=8c951eb4-28c1-edf2-21d7-e8344f4842f7
fateShareId=Cluster1:29835980 bearerless=F videoCall=F videoCap=F videoClass=0 videoKbp=0
retryAsAudio=T ipMode=0 mediaEP=F precedence=5 nonPreemptable=F region=RG_HQ regState=0
XferMode=4 cacPartyState=0
00868365.001 |18:10:13.895 |AppInfo |LBMIF: CI: 29835980 REGISTER 1,100,66,6 dev 0xd894068
00868365.002 |18:10:13.895 |AppInfo |LBMIF: device 0xd894068 A:Y V:N I:N ; peer 0xdb72ba0
A:Y V:N I:N | UV:T QoS:F
00868365.003 |18:10:13.895 |AppInfo |RegionsServer - modeA =[0], modeB =[0], preferredIpType =[0]
00868365.004 |18:10:13.895 |AppInfo |LBMIF: CI: 29835980 BW RSV> dev 0xd894068

13043408459217764425 audio 24
00868365.005 |18:10:13.895 |AppInfo |LBMIF: CI: 29835980 BW RSV<S 13043408459217764425
Facebook Group
00868366.000 |18:10:13.895 |SdlSig |LBMRegisterRes |wait
|ReservationMgr(1,100,113,1) |LBMInterface(1,100,180,1)
Branch= 0 Status=2 vCall=F DevicecontrolPid=1,100,66,6 DeviceCdpcPid=1,100,67,147
LBMCACReturnInfo: lbmReservedKbps=24 locationIsPhantom=F bwPreemption=F
00868366.001 |18:10:13.895 |AppInfo |ReservationMgr::wait_LBMRegisterRes, sendingCrp = (1, 100,

67, 147)
00868367.000 |18:10:13.895 |SdlSig |RSVPRegisterReq |wait

|RSVPSession(1,100,110,74) |ReservationMgr(1,100,113,1)
Branch= 0 reg=RG_HQ cap=11 loc=2 MRGLPkid=48435ae2-f94e-e58c-f21e-e86e6ef56b1b PrecLev=5
bearerlessCall=F VCall=F MMCap=0x1 VCapCount=0 regiState=0 medReq=0 IsEmccD=F EmccDName=
rcId= ipMode=0 eoType=0 getPort=T sRTP=F cryptocap=0 tm=4 DTMF(wantRecep=0 provOOB=0
suppMeth=3 Cfg=1 PT=0 reqMed=1) honorCodec=F distMed=F mediaEP=F rsvpQoSType=0
qosFallback=F status=0 sipOfferNeededInd=F hasSDP=FLatentCaps=null videoTrafficClass=0
nonPreemptable=F
00868367.001 |18:10:13.895 |AppInfo |RegionsServer - modeA =[0], modeB =[0], preferredIpType =[0]

PREF_NONE, regionA=(null) regionB=(null) latentCaps(A=0, B=0) kbps=8, capACount=11, capBCount=12

PREF_NONE, regionA=(null) regionB=(null) latentCaps(A=0, B=0) kbps=8, capACount=12, capBCount=11
00868368.000 |18:10:13.896 |SdlSig |MrmAllocateRSVPResourceReq |waiting

|MediaResourceManager(1,100,142,1) |RSVPSession(1,100,110,74)
RSVPLocationPairPolicy=4 CI=29835981 MRGLPkid=48435ae2-f94e-e58c-f21e-e86e6ef56b1b Kpbs=0
RegionA=RG_HQ CapA=11 RegionB=RG_BRA1 CapB=21 SuppressFlag=4 DeviceCapability= [0x110
PT_CAP MM_CAP] MandatoryCapabilities= [0x0] Type=2 Resource Count=1 Try PassThru=T
IsEMCCDevice=F EMCCDevName= RemoteClusterId=
00868368.001 |18:10:13.896 |AppInfo

|MediaResourceManager::waiting_MrmAllocateRSVPResourceReq - RsvpPolicy=4, CI=29835981,
Resource Requested=1 CapCountA=11, capCountB=21, regionA=RG_HQ, regionB=RG_BRA1,
Suppression=4, deviceCapbility=272, mandatoryCaps=0, TryPassThru=1, IsEMCCDevice=0
00868368.002 |18:10:13.896 |AppInfo |MRM::convertScmStringToStdString

MRG_HQ_HW:MRG_HQ_SW
00868368.003 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceGivenMrgl
00868368.004 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceGivenMrgl DeviceName=HQ_MTP_RSVP

DeviceType=83 Group=0 Counter=0 Capability=0 MultiCast=0 MRGL=
Facebook Group
00868368.005 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceGivenMrgl GETTING MTP FROM DEFAULT
LIST
00868368.006 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceGivenMrgl GETTING XCODE FROM

DEFAULT LIST
00868368.007 |18:10:13.896 |AppInfo |MediaResourceCdpc(0)::createTempDeviceTable - Entries

copied in the Temp Device Table = 1
00868368.008 |18:10:13.896 |Created | |

|MediaResourceCdpc(1,100,143,71) |MediaResourceManager(1,100,142,1) |
00868369.000 |18:10:13.896 |SdlSig |Start |start

|MediaResourceCdpc(1,100,143,71) |MediaResourceCdpc(1,100,143,71)
|1,100,14,409.109^192.168.13.84^SEPBC16F517B8C8 |*TraceFlagOverrode
00868369.001 |18:10:13.896 |AppInfo |MediaResourceCdpc(71) - Started
00868370.000 |18:10:13.896 |SdlSig |MrmAllocateRSVPResourceReq |waiting

|MediaResourceManager(1,100,142,1) |RSVPSession(1,100,110,74)
RSVPLocationPairPolicy=4 CI=29835982 MRGLPkid= Kpbs=0 RegionA=RG_BRA1 CapA=12
RegionB=RG_HQ CapB=21 SuppressFlag=4 DeviceCapability= [0x110 PT_CAP MM_CAP]
MandatoryCapabilities= [0x0] Type=2 Resource Count=1 Try PassThru=T IsEMCCDevice=F
EMCCDevName= RemoteClusterId=
00868370.001 |18:10:13.896 |AppInfo

|MediaResourceManager::waiting_MrmAllocateRSVPResourceReq - RsvpPolicy=4, CI=29835982,
Resource Requested=1 CapCountA=12, capCountB=21, regionA=RG_BRA1, regionB=RG_HQ,
Suppression=4, deviceCapbility=272, mandatoryCaps=0, TryPassThru=1, IsEMCCDevice=0
00868370.002 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceDefaultMrgl GETTING MTP FROM

DEFAULT LIST
00868370.003 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceDefaultMrgl GETTING XCODE FROM

DEFAULT LIST
00868370.004 |18:10:13.896 |AppInfo |MediaResourceManager::sendAllocationResourceErr - ERROR -

no RSVP device configured
00868370.005 |18:10:13.896 |AppInfo |GenAlarm: AlarmName = MediaResourceListExhausted, subFac

= CALLMANAGERKeyParam = , severity = 4, AlarmMsg = MediaResourceListName : NULL_LIST
MediaResourceType : 9
MediaResourceTypeValue : Resource Reservation Protocol Agent(RSVP)
AppID : Cisco CallManager
ClusterID : Cluster1
Facebook Group
NodeID : labcucm
++++++++++++++++++++++++++++++++++++++++++++++++
Kind of weird right? I double check and the MTP is associated to the MRGL and the MRGL is associated
to the Device Pool which is assigned to the phones… mmmmm…..
Lets try configuring the MRGL on each phone (This should not be the fix), but lets try it.
And do the same for BRA1
Task.- Call again from HQ phone to BRA1 phone
Facebook Group
Success!!!
I was just want to make a note on this… This configuration (assign MRGL individually on each phone)
should NOT be the fix, as the MRGL should be assigned by the device pool… anyway… I think shits
happends right? Like Forest Gumps would say…
Facebook Group
And now that we are fill with success and in the mood for memes of Forest Gumps…
Useful tools to validate RSVP assignation

Voice Gateway
I mean there are a lot of debug you can turn on this… I am more interested on the “path” messages. If
you want you want turn more debus on your lab.
“debug ip rsvp path”
SAF_FORWARDER_1#debug ip rsvp path
SAF_FORWARDER_1#term mon
Nov 25 18:45:27.451: RSVP-PROXY-MERGE: rsvp_proxy_mgr_merge_proxy: args=3DA28674
Nov 25 18:45:27.451: RSVP-PROXY: rsvp_proxy_find_path: session=229277B8 template=229277A0
Nov 25 18:45:27.451: RSVP-PROXY-MERGE: No existing CAC proxy matches with the proxy being
installed, no need to merge
Nov 25 18:45:27.451: RSVP-PROXY-MERGE: 0 --> CAC/MD
Nov 25 18:45:27.451: RSVP-API: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Processing

PATH request [id=0x22D0248C]...
Nov 25 18:45:27.451: RSVP-PROXY: rsvp_proxy_path: handle=0 objects=3DA586A4 len=228

input_if=00000000, callback=331155C8 tied=0 flags=00000000 api_info=3DA28678
Facebook Group
Nov 25 18:45:27.451: RSVP-PROXY: rsvp_proxy_examine_handle: handle=0, type=8
Nov 25 18:45:27.451: RSVP: Allocating handle entry 1/1. Type: 8, instance cnt: 29, handle_count is now
2
Nov 25 18:45:27.451: RSVP-DB: PXSB 3A00C34C allocated
Nov 25 18:45:27.451: RSVP-PROXY: rsvp_proxy_find_path: session=21957B60 template=21957BE4
Nov 25 18:45:27.451: RSVP-PROXY: rsvp_proxy_path: searched handle = 00000000
3
Nov 25 18:45:27.451: RSVP: Session inserted: 3DA278BC
4
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Received Path

message from 127.0.0.1 (on sender host)
5
Nov 25 18:45:27.455: RSVP: Freeing handle 1/6. Type: 2, instance cnt: 13, handle_count is now 4
Nov 25 18:45:27.455: RSVP: new path message passed parsing, continue...
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: PATH: FLR is

enabled on this PSB
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]:

[rsvp_examine_and_mark_md_events] Incoming PSB MD = Ignore
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]:

[rsvp_examine_and_mark_tspec_events] Incoming PSB TSpec = Create
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]Multiple Routes for

192.168.13.241 do not Exist in tableid-0
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]IP route lookup for

192.168.13.241 in tableid-0 passed: GigabitEthernet0/1-192.168.13.241
Nov 25 18:45:27.455: RSVP: RSVP-Route: 192.168.13.242_0->192.168.13.241_0[0.0.0.0]: RIB route

lookup: GigabitEthernet0/1-192.168.13.241
Nov 25 18:45:27.455: RSVP-Route: 192.168.13.242_0->192.168.13.241_0[0.0.0.0]: Setting next_hop =

192.168.13.241 on intf GigabitEthernet0/1
Nov 25 18:45:27.455: RSVP-DB: A new (unicast) pfc is being added for GigabitEthernet0/1
Facebook Group
5
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]:

rsvp_rmsg_enable_for_pfc, Enabled Reliable Messaging for this PFC (0xE000406)
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: RSVP-POLICY -

Path query
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: POLICY-LOCAL -

query for inbound Path message

Path from 192.168.13.242 originated in AS 8918
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: POLICY-LOCAL - no

decision (can't find a matching policy)

AS-based policy lookup for Path not possible due to aggregated route for 192.168.13.242
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: POLICY-COPS -

COPS query for Path message
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: POLICY-COPS - no

active COPS server entry for this session. Ignoring

granting default policy for Path

received decision for Path message

accept incoming message
Nov 25 18:45:27.455: RSVP-SNMP: Creating a new sender (# 20)
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Notifying proxy of

path create event
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_sig_path_event: psb=3DAC20F0
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_sig_path_create: psb=3DAC20F0
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_match_path_and_execute: psb=3DAC20F0, event=10,

reason=0
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_search_for_awaiting_rxsbs: psb=3DAC20F0
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Processing MD

related events
Facebook Group
Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Not notifying MD
client as it is not a valid MD event
Nov 25 18:45:27.455: RSVP: Triggering outgoing Path due to incoming Path change or new Path
Nov 25 18:45:27.455: RSVP: Triggering outgoing Path refresh
Nov 25 18:45:27.455: RSVP-PROXY: signalling accepted pxsb=3A00C34C
Nov 25 18:45:27.455: RSVP-DB: PXSB 3A00C34C inserted; Session=3DA278BC, Count=1
Nov 25 18:45:27.455: RSVP-API: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Created Path

state [id=0x22D0248C
Nov 25 18:45:27.455: RSVP-API: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]Multiple

Routes for 192.168.13.241 do not Exist in tableid-0
Nov 25 18:45:27.455: RSVP-API: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]IP route lookup

for 192.168.13.241 in tableid-0 passed: GigabitEthernet0/1-192.168.13.241


Nov 25 18:45:27.455: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: FLR: Insignificant

Route Change for PSB.

RESV request [id=0x22D0269C]...
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_resv: handle=0 objects=3DA586A4 len=188

input_if=00000000, callback=33114A7C tied=0 flags=00000000 api_info=229278F4
6
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_find_resv: session=3FFEC51C hop=3FFEC528

style=3FFEC5A0 filter=3FFEC5CC
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_resv: searched handle = 00000000
7
Nov 25 18:45:27.455: RSVP: Session inserted: 3DA277D4
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_submit_rxsb_to_signalling: rxsb=3DA33274

sig_status=22927760
Facebook Group
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_rxsb_to_signalling: do it!
Nov 25 18:45:27.455: RSVP: session 192.168.13.242_16416[0.0.0.0]: Received Resv message from

127.0.0.1 (on receiver host)
8
Nov 25 18:45:27.459: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Successfully

parsed Resv message from 127.0.0.1 (on receiver host)
Nov 25 18:45:27.459: RSVP-MSG: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: no matching

path state for Resv
Nov 25 18:45:27.459: RSVP-PROXY: signalling accepted rxsb=3DA33274, however, no matching PATH

was found
Nov 25 18:45:27.459: RSVP-API: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Created RESV

state [id=0x22D0269C]
Nov 25 18:45:27.459: RSVP-API: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]Multiple

Routes for 192.168.13.241 do not Exist in tableid-0
Nov 25 18:45:27.459: RSVP-API: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]IP route lookup

for 192.168.13.241 in tableid-0 passed: GigabitEthernet0/1-192.168.13.241


Nov 25 18:45:27.459: rsvp_if_ip_addr: address is 192.168.13.242
Nov 25 18:45:27.459: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Path refresh,

Event: rmsg not enabled or ack rcvd, State: trigger to normal
Nov 25 18:45:27.459: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Path refresh

(msec), config: 30000 curr: 30000 xmit: 30000

Path query

query for outbound Path message

Facebook Group




send outgoing message to GigabitEthernet0/1
Nov 25 18:45:27.459: RSVP: Triggering outgoing Path due to incoming Path change or new Path
Nov 25 18:45:27.459: RSVP: Triggering outgoing Path refresh
Nov 25 18:45:27.463: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]Multiple Routes for

192.168.13.241 do not Exist in tableid-0
Nov 25 18:45:27.463: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]IP route lookup for



Nov 25 18:45:27.463: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Path refresh,

Nov 25 18:45:27.463: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Path refresh

Nov 25 18:45:27.463: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Sending Path

message to 192.168.13.241
8
Nov 25 18:45:27.463: rsvp_get_if_addr: address is 192.168.13.242
Nov 25 18:45:27.463: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: building hop

object with src addr: 192.168.13.242
Facebook Group
Nov 25 18:45:27.463: RSVP: session 192.168.13.241_20402[0.0.0.0]:
Outgoing Path, I/F=Gi0/1, Layer=IP, Link=IPv4, NHOP=192.168.13.241, Prerouted=Y
IP HDR: 192.168.13.242->192.168.13.241, TOS=0x00, V6_FL=0, Len=260, TTL=255, RA=Y
RSVP HDR: RRC=N, TTL=255, Len=236, Cksum=0x7C2E
Nov 25 18:45:27.467: RSVP: session [TBD]
Incoming Path, I/F=Gi0/1, Layer=IP, Link=IPv4
IP HDR: 192.168.13.241->192.168.13.242, TOS=0x00, Len=236, TTL=254, RA=Y
RSVP HDR: RRC=N, TTL=255, Len=236, Cksum=0x7532
Nov 25 18:45:27.467: RSVP-DB: Session head found: 3DA277D4
8
Nov 25 18:45:27.467: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Received Path

message from 192.168.13.241 (on GigabitEthernet0/1)
9
Nov 25 18:45:27.467: RSVP-DB: Could not get info for tunnel GigabitEthernet0/1
Nov 25 18:45:27.467: RSVP: new path message passed parsing, continue...
Nov 25 18:45:27.467: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]RIB lookup for

Nov 25 18:45:27.467: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]:

[rsvp_examine_and_mark_md_events] Incoming PSB MD = Ignore
Nov 25 18:45:27.467: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]:

[rsvp_examine_and_mark_tspec_events] Incoming PSB TSpec = Create

Path query

query for inbound Path message

Facebook Group




Nov 25 18:45:27.467: RSVP-SNMP: Creating a new sender (# 21)
Nov 25 18:45:27.467: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Notifying proxy of

path create event
Nov 25 18:45:27.467: RSVP-PROXY: rsvp_proxy_sig_path_event: psb=3DAC1E28
Nov 25 18:45:27.467: RSVP-PROXY: rsvp_proxy_sig_path_create: psb=3DAC1E28
Nov 25 18:45:27.467: RSVP-PROXY: rsvp_proxy_match_path_and_execute: psb=3DAC1E28, event=10,

reason=0
Nov 25 18:45:27.467: RSVP-PROXY: rsvp_proxy_search_for_awaiting_rxsbs: psb=3DAC1E28
Nov 25 18:45:27.467: RSVP-PROXY: rsvp_proxy_reprocess_rxsb: rxsb=3DA33274 data_ptr=3DAC1E28
Nov 25 18:45:27.471: RSVP-PROXY: rsvp_proxy_submit_rxsb_to_signalling: rxsb=3DA33274

sig_status=3DA3C800

9

10
Nov 25 18:45:27.471: RSVP-SNMP: Creating a new receiver (# 20)

Resv query
Facebook Group
query for Resv message


granting default policy for Resv

received decision for Resv (74)


accept resv alloc

forward outgoing message
Nov 25 18:45:27.471: RSVP-RESV: Admitting new reservation: 3DACA344
Nov 25 18:45:27.471: RSVP-RESV: Locally created reservation. No admission/traffic control needed
Nov 25 18:45:27.471: RSVP-PROXY:rsvp_proxy_sig_resv_create: rsb=3DACA344 psb=3DAC1E28
11
Nov 25 18:45:27.471: RSVP-SNMP: Creating a new request (# 10)
Nov 25 18:45:27.471: RSVP-SNMP: Can't send NEWFLOW SNMP trap for reservation
192.168.13.241:20402->192.168.13.242:16416 - no rsvp_info for interface (receiver host)
Nov 25 18:45:27.471: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: start requesting

96 kbps FF reservation on GigabitEthernet0/1, neighbor 192.168.13.241
Nov 25 18:45:27.471: RSVP-PROXY: rsvp_proxy_reprocess_rxsb: resubmission was a success
Nov 25 18:45:27.471: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Processing MD

related events
Nov 25 18:45:27.471: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Not notifying MD

client as it is not a valid MD event
Nov 25 18:45:27.471: RSVP-PROXY: rsvp_proxy_sig_resv_change: rsb=3DACA344 psb=3DAC1E28

Facebook Group
Incoming Resv, I/F=Gi0/1, Layer=IP, Link=IPv4
IP HDR: 192.168.13.241->192.168.13.242, TOS=0x00, Len=196, TTL=254, RA=N
RSVP HDR: RRC=N, TTL=255, Len=196, Cksum=0x617F
Nov 25 18:45:27.471: RSVP-DB: Session head found: 3DA278BC

192.168.13.241 (on GigabitEthernet0/1)
11

parsed Resv message from 192.168.13.241 (on GigabitEthernet0/1)
Nov 25 18:45:27.471: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]:

rsvp_rmsg_disable_for_pfc, Disabled Reliable Messaging for this PFC (0xE000406)
Nov 25 18:45:27.471: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: reservation not

found--new one
12
Nov 25 18:45:27.471: RSVP-SNMP: Creating a new receiver (# 21)

Resv query






accept resv alloc
Facebook Group
Nov 25 18:45:27.471: RSVP-RESV: Admitting new reservation: 3DACA1A4
Nov 25 18:45:27.471: RSVP-TC: Attempting to install QoS for rsb 3DACA1A4
13
Nov 25 18:45:27.471: RSVP-DB: Allocated TCSB 3E4E305C
Nov 25 18:45:27.471: RSVP-TC: Adding new tcsb 1F000403 for rsb 3DACA1A4
Nov 25 18:45:27.475: RSVP-TC: Associating tcsb 0x1F000403, rsb 0x3DACA1A4, fsb 0x2105E450
Nov 25 18:45:27.475: RSVP-TC: Assigning NO resource provider to tcsb 1F000403
Nov 25 18:45:27.475: RSVP-DB: Inserted TCSB 3E4E305C into database
Nov 25 18:45:27.475: RSVP-TC: Consulting policy for tcsb 1F000403

Conv query, TCSB handle = 0x1F000403, requested bw=96000 old bw=0

query for admission control, TCSB handle = 0x1F000403

decision (no RSBs on this TCSB have local policy)

query for Resv Alloc

active COPS server entry for this TCSB. Ignoring

granting default policy for admission control

received decision for Resv Alloc

accept resv alloc
Nov 25 18:45:27.475: RSVP-TC: Policy granted QoS for tcsb 1F000403
Nov 25 18:45:27.475: RSVP-TC: Allocation succeeded for tcsb 1F000403
Nov 25 18:45:27.475: rsvp_tc_process_waiting_callback: Reset psb->retry
Nov 25 18:45:27.475: rsvp_api_notify_bw_change: RSVP Successfully notified client about bandwidth

change on GigabitEthernet0/1
Facebook Group
Nov 25 18:45:27.475: RSVP-TC: fsb 0x2105E450 activated for tcsb 0x1F000403
Nov 25 18:45:27.475: RSVP-RESV: reservation was installed: 3DACA1A4
Nov 25 18:45:27.475: RSVP-PROXY:rsvp_proxy_sig_resv_create: rsb=3DACA1A4 psb=3DAC20F0
Nov 25 18:45:27.475: RSVP-PROXY:rsvp_proxy_sig_resv_create: making upcall to 331155C8 for

pxsb=3A00C34C
Nov 25 18:45:27.475: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Refresh RESV,

req=23545E90 [cleanup timer is not awake]
Nov 25 18:45:27.475: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Resv refresh,

Nov 25 18:45:27.475: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Resv refresh


request query
13

Resv query


unicast FF outbound request. Attempting to grant cached policy




Nov 25 18:45:27.475: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Sending Resv

message to 192.168.13.241
Facebook Group
14

Nov 25 18:45:27.475: RSVP: session 192.168.13.242_16416[0.0.0.0]:
Outgoing Resv, I/F=Gi0/1, Layer=IP, Link=IPv4, NHOP=192.168.13.241, Prerouted=N
IP HDR: 192.168.13.242->192.168.13.241, TOS=0x00, V6_FL=0, Len=216, TTL=255, RA=N
RSVP HDR: RRC=N, TTL=255, Len=196, Cksum=0x5A81

RESV request [id=0x0]...
Nov 25 18:45:28.935: RSVP-PROXY: rsvp_proxy_find_resv: session=3DA586A4 hop=3DA586B0

style=3DA58728 filter=3DA58754
Nov 25 18:45:28.935: RSVP-PROXY: rsvp_proxy_resv: handle=402654219 objects=3DA586A4 len=188

input_if=00000000, callback=33114A7C tied=0 flags=00000000 api_info=2292782C
Nov 25 18:45:28.935: RSVP-PROXY: rsvp_proxy_examine_handle: modify is TRUE
13
Nov 25 18:45:28.935: RSVP-PROXY: rsvp_proxy_find_resv: session=2353C244 hop=2353C250

style=2353C2C8 filter=2353C2F4
Nov 25 18:45:28.935: RSVP-PROXY: rsvp_proxy_resv: searched handle = 1800040B
Nov 25 18:45:28.935: RSVP-PROXY: rsvp_proxy_submit_rxsb_to_signalling: rxsb=3DA331B0

sig_status=22927698
Facebook Group
14

Nov 25 18:45:28.939: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Resv changed:

FLOWSPEC,
Nov 25 18:45:28.939: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]:

process_reservation_change: Resv change requires triggering of Resv upstream

Resv query






accept resv alloc

Nov 25 18:45:28.939: RSVP-RESV: accept_reservation_change: 3DACA344
Nov 25 18:45:28.939: RSVP-RESV: Locally created reservation. No admission/traffic control needed
Nov 25 18:45:28.939: RSVP-PROXY: rsvp_proxy_sig_resv_change: rsb=3DACA344 psb=3DAC1E28

Nov 25 18:45:28.939: RSVP-PROXY: signalling accepted rxsb=3DA331B0
Facebook Group
Nov 25 18:45:28.939: RSVP-PROXY:rsvp_proxy_rxsb_swap_handles: handle1=402654219
handle2=536871944
Nov 25 18:45:28.939: RSVP-API: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Modified

RESV state [id=0x0]
Nov 25 18:45:28.943: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Refresh RESV,

req=23545E90 [cleanup timer is not awake]
Nov 25 18:45:28.943: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Resv refresh,

Nov 25 18:45:28.943: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Resv refresh


request query
13

Resv query


unicast FF outbound request. Attempting to grant cached policy




Nov 25 18:45:28.943: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Sending Resv

message to 192.168.13.241
Facebook Group
14
Nov 25 18:45:28.947: rsvp_tc_process_waiting_callback: Reset psb->retry

Nov 25 18:45:28.947: RSVP-TC: fsb 0x2105E450 activated for tcsb 0x1F000403
Nov 25 18:45:28.947: RSVP-RESV: reservation was installed: 3DACA1A4
Nov 25 18:45:28.947: RSVP-PROXY: rsvp_proxy_sig_resv_change: rsb=3DACA1A4 psb=3DAC20F0
Nov 25 18:45:28.947: RSVP-PROXY:rsvp_proxy_sig_resv_change: making upcall to 331155C8 for

pxsb=3A00C34C
Nov 25 18:45:37.683: RSVP-PROXY-MERGE: rsvp_proxy_mgr_merge_proxy: args=3DA28674
Nov 25 18:45:37.683: RSVP-PROXY: rsvp_proxy_find_path: session=229277D0 template=229277B8
Nov 25 18:45:37.683: RSVP-PROXY: rsvp_proxy_examine_handle: modify is TRUE
Nov 25 18:45:37.683: RSVP-PROXY-MERGE: CAC --> 0
Nov 25 18:45:37.683: RSVP-PROXY-MERGE: args->action = Delete, merge_result = success

PATH delete [id=0x0]...
Nov 25 18:45:37.683: RSVP-PROXY: rsvp_proxy_find_path: session=229277C0 template=229277A8
Nov 25 18:45:37.683: RSVP-PROXY: rsvp_proxy_remove_path: handle=486540289
Nov 25 18:45:37.683: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Expiring sender

host PATH state, reason: Local application requested tear
13
Nov 25 18:45:37.683: RSVP: rsvp_rmsg_enable_for_tmb, Enabled Reliable Messaging for this tmb
(0x23000408)
Facebook Group
Nov 25 18:45:37.687: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]:

rsvp_rmsg_disable_for_tmb, Disabled Reliable Messaging for this tmb (0x23000408)
Nov 25 18:45:37.687: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Sending PathTear

message to 192.168.13.241
Nov 25 18:45:37.687: RSVP: session 192.168.13.241_20402[0.0.0.0]:
Outgoing PathTear, I/F=Gi0/1, Layer=IP, Link=IPv4, NHOP=192.168.13.241, Prerouted=Y
IP HDR: 192.168.13.242->192.168.13.241, TOS=0x00, V6_FL=0, Len=152, TTL=255, RA=Y
RSVP HDR: RRC=N, TTL=255, Len=128, Cksum=0x9AAC
Nov 25 18:45:37.687: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Expiring

GigabitEthernet0/1 RESV state, reason: Local application requested tear
Nov 25 18:45:37.687: RSVP-Ingress: Proceeding with flow disassociation rsb 3DACA1A4
Nov 25 18:45:37.687: RSVP-TC: Attempting to remove QoS for rsb 3DACA1A4
Nov 25 18:45:37.687: RSVP-TC: tcsb 1F000403 found for rsb 3DACA1A4
Nov 25 18:45:37.687: RSVP-TC: fsb 0x2105E450 deactivated for tcsb 0x1F000403

Nov 25 18:45:37.687: RSVP-DB: Removing TCSB 3E4E305C from database
Nov 25 18:45:37.687: RSVP-TC: Deleting tcsb 0x1F000403
Nov 25 18:45:37.687: RSVP-DB: Freeing TCSB 3E4E305C
Nov 25 18:45:37.687: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: expire_reason =

Local application requested tear,flow_notify = RSVP_EXPIRE_RESERVATION

GigabitEthernet0/1 RESV state, reason: Local application requested tear (17:16416)
Nov 25 18:45:37.687: RSVP-PROXY: rsvp_proxy_sig_resv_delete: rsb=3DACA1A4 psb=3DAC20F0

reason=2
Nov 25 18:45:37.687: RSVP-PROXY: rsvp_proxy_sig_path_delete: psb=3DAC20F0 reason=2

Facebook Group
Nov 25 18:45:37.687: RSVP-PROXY: rsvp_proxy_match_path_and_execute: psb=3DAC20F0, event=13,
reas
SAF_FORWARDER_1#
SAF_FORWARDER_1#
SAF_FORWARDER_1#on=2
Nov 25 18:45:37.687: RSVP-DB: PXSB 3A00C34C removed; Session=3DA278BC Count=0
Nov 25 18:45:37.687: RSVP-DB: freeing PXSB 3A00C34C
Nov 25 18:45:37.687: RSVP-DB: Session head delete: 3DA278BC
Nov 25 18:45:37.687: RSVP-API: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Deleted PATH

state [id=0x0]

RESV delete [id=0x0]...
Nov 25 18:45:37.687: RSVP-PROXY: rsvp_proxy_find_resv: session=229277D0 hop=22927800

style=229277B0 filter=229277B8
Nov 25 18:45:37.687: RSVP-PROXY: rsvp_proxy_remove_resv: handle=402654219
Nov 25 18:45:37.687: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Expiring RESV

state, reason: Local application requested tear
Nov 25 18:45:37.687: RSVP-TC: No tcsb found for rsb 3DACA344
Nov 25 18:45:37.687: RSVP-TC: Attempting to remove QoS for rsb 3DACA344
Nov 25 18:45:37.687: RSVP-TC: No tcsb found for rsb 3DACA344
Nov 25 18:45:37.687: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: expire_reason =

Local application requested tear,flow_notify = RSVP_EXPIRE_RESERVATION
Nov 25 18:45:37.687: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Expiring receiver

host RESV state, reason: Local application requested tear (17:20402)

GigabitEthernet0/1 RESV request state, reason: Local application requested tear
Facebook Group
7
(0x1F000402)
Nov 25 18:45:37.691: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Sending ResvTear

message to 192.168.13.241
Nov 25 18:45:37.691: RSVP: session 192.168.13.242_16416[0.0.0.0]:
Outgoing ResvTear, I/F=Gi0/1, Layer=IP, Link=IPv4, NHOP=192.168.13.241, Prerouted=N
IP HDR: 192.168.13.242->192.168.13.241, TOS=0x00, V6_FL=0, Len=108, TTL=255, RA=N
RSVP HDR: RRC=N, TTL=255, Len=88, Cksum=0x89DA
Nov 25 18:45:37.691: RSVP-SNMP: Can't send LOSTFLOW SNMP trap for reservation
192.168.13.241:20402->192.168.13.242:16416 - no rsvp_info for interface (receiver host)
7
Nov 25 18:45:37.691: RSVP-PROXY: rsvp_proxy_sig_resv_delete: rsb=3DACA344 psb=3DAC1E28

reason=2
Nov 25 18:45:37.691: RSVP-API: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: Deleted RESV

state [id=0x0]
Incoming PathTear, I/F=Gi0/1, Layer=IP, Link=IPv4
IP HDR: 192.168.13.241->192.168.13.242, TOS=0x00, Len=128, TTL=254, RA=Y
RSVP HDR: RRC=N, TTL=255, Len=128, Cksum=0x93B0
Facebook Group
4
(0x1900040B)
Nov 25 18:45:37.691: RSVP-MSG: 192.168.13.241_20402->192.168.13.242_16416[0
SAF_FORWARDER_1#.0.0.0]: Received PathTear message from 192.168.13.241 (on GigabitEthernet0/1)
Nov 25 18:45:37.691: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]:

[rsvp_md_process_event_path_delete] Not notifying MD initiator of MD delete event
Nov 25 18:45:37.691: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: flow_notify =

RSVP_PATH_TEARDOWN

GigabitEthernet0/1 PATH state, reason: PathTear arrival
Nov 25 18:45:37.691: RSVP-PROXY: rsvp_proxy_sig_path_delete: psb=3DAC1E28 reason=0
Nov 25 18:45:37.691: RSVP-PROXY: rsvp_proxy_match_path_and_execute: psb=3DAC1E28, event=13,

reason=0
Nov 25 18:45:37.691: RSVP-DB: Session head delete: 3DA277D4
Incoming ResvTear, I/F=Gi0/1, Layer=IP, Link=IPv4
IP HDR: 192.168.13.241->192.168.13.242, TOS=0x00, Len=88, TTL=254, RA=N
RSVP HDR: RRC=N, TTL=255, Len=88, Cksum=0x90D8
2
Nov 25 18:45:37.695: RSVP: Session inserted: 3DA278BC
3
(0x1A00040B)
Facebook Group
Nov 25 18:45:37.695: RSVP-MSG: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Received
ResvTear message from 192.168.13.241 (on GigabitEthernet0/1)
Nov 25 18:45:37.695: RSVP-MSG: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: Dropping

ResvTear with unrecognized LIH in HOP (may be due to a state which was already deleted)
Nov 25 18:45:37.695: RSVP-DB: Session head delete: 3DA278BC
SAF_FORWARDER_1#
SAF_FORWARDER_1#
SAF_FORWARDER_1#
RTMT
Go to RTMT > Performance > CUCM Node > Cisco Location LBM > “Select what ever you need”
I select the following:
I just made a call and NOW I can see this:
Facebook Group
Is RTMT amazing or what?
Homework
What is the benefit of using RSVP?
What will happened if you have two independent clusters and want to do RSVP?
Can you do RSVP and ALSO use DiffServ to put Voice Traffic on a low priority queue?
If you are using RSVP, will this configuration will kill video on a call?
Facebook Group

RSVP Lab Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RSVP Lab Guide

Uploaded by

Copyright:

Available Formats

RSVP

RSVP cannot be configured with VIP-distributed Cisco Express Forwarding (dCEF).

RSVP Reservation Types

These are the two types of multicast flows:

RSVP describes these reservations as having certain algorithmic attributes.

RSVP Call Flow

HQ IOS RSVP Configuration

sccp local GigabitEthernet0/1

sccp ccm 192.168.13.248 identifier 1 priority 1 version 7.0

sccp ccm group 1

associate ccm 1 priority 1

associate profile 1 register HQ_MTP_RSVP

dspfarm profile 1 mtp

maximum sessions software 10

associate application SCCP

Task.- Validate status of MTP Registration

SCCP Admin State: UP

Gateway Local Interface: GigabitEthernet0/0

IPv4 Address: 192.168.13.241

Port Number: 2000

User Masked Codec list: None

Call Manager: 192.168.13.248, Port Number: 2000

Priority: 1, Version: 7.0, Identifier: 1

MTP Oper State: ACTIVE_IN_PROGRESS - Cause Code: CCM_REGISTER_FAILED

Active Call Manager: 192.168.13.248, Port Number: 2000

TCP Link Status: NOT_CONNECTED, Profile Identifier: 1

Reported Max Streams: 20, Reported Max OOS Streams: 0

Supported Codec: pass-thru, Maximum Packetization Period: N/A

Supported Codec: g711ulaw, Maximum Packetization Period: 30

Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30

Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30

Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30

HQ CUCM RSVP Configuration

Task.- Create a MRG for HQ and associate the HQ MTP

Task.- Create a MRGL on HQ and associate MRG´s

Do the same for BRA Device

Task.- Assocaite the MRGL of BRA1 to BRA1 Device Pool

Configure the use of Mandatory RSVP

“Not enough bandwith” NOW its time to troubleshoot!

|Calling Party Number Type=Cisco Unified CallManager

|Calling Party Numbering Plan=Cisco Unified CallManager

|Called Party Number Type=Cisco Unified CallManager

|Called Party Numbering Plan=Cisco Unified CallManager

|AlternateMatches= Information Not Available

|TranslationPatternDetails= Information Not Available

00868338.000 |18:10:13.893 |SdlSig |DmPidReq |initialized

00868338.001 |18:10:13.893 |AppInfo |SMDMSharedData::findAliasRegInfo - AliasName = 29df6af2-

00868338.002 |18:10:13.893 |AppInfo |DeviceManager::star_DmPidReq - RequestedName=29df6af2-

00868338.003 |18:10:13.893 |AppInfo |SMDMSharedData::findLocalDevice - Name=1002:

00868339.001 |18:10:13.893 |AppInfo |Digit analysis: wait_DmPidRes- Partition=[] Pattern=[1002]

00868340.000 |18:10:13.894 |SdlSig |DaRes |setup_da

00868340.001 |18:10:13.894 |AppInfo |processCCMFeatureData: operationIeIdd=0

00868340.002 |18:10:13.894 |AppInfo |findUnfiredInterceptOnPattern numOfPatterns = 0

00868341.000 |18:10:13.894 |SdlSig |CcProceedReq |restart0

00868341.001 |18:10:13.894 |AppInfo |LineControl - restert0_CcProceedReq updated precedence of

00868342.000 |18:10:13.894 |SdlSig |PolicyAndCACAssociateReq |wait

00868343.000 |18:10:13.894 |SdlSig |CcProceedReq |call_initiated1

00868343.001 |18:10:13.894 |AppInfo |LineCdpc(146): -dispatchToAllDevices-,

00868344.000 |18:10:13.894 |SdlSig |CACAssociateReq |await_associate

00868345.000 |18:10:13.894 |SdlSig |PolicyAndCACAssociateRes |wait

00868346.000 |18:10:13.894 |SdlSig |CcProceedReq |restart0

00868347.000 |18:10:13.894 |SdlSig |PolicyAndCACAssociateRes |tcc_register_party_b

00868347.001 |18:10:13.894 |AppInfo |Cdcc - CcsetupReq - fCcSetupReq.bc.l=3,

00868347.002 |18:10:13.894 |AppInfo |Cdcc::sendCcSetupReq: precLvl=5