RSVP Lab Guide
RSVP Lab Guide
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
For more information about RSVP, see the section "Resource Reservation Protocol" in the chapter
"Signalling Overview" in this book.
•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.
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
•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.
Note: As soon as the Setup message is send to initiate the call, the CUCM initiate the RSVP allocate
process.
Diagram
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
sccp
codec g711ulaw
codec pass-through
rsvp
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
SAF_FORWARDER_2#show sccp
IP Precedence: 5
RSVP : ENABLED
TLS : ENABLED
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Task.- Create an MTP for HQ
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Task.- Create a MRG (HQ) for software resources (Optional)
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Task.- Associate MRGL to HQ Device Pool
Task.- Create MRG for BRA1 and associate the BRA1 MTP
If you need help, check how it was done on HQ on previous steps
Task.- Create a MRGL for BRA1 and associate MRG´s (BRA1 and SW)
If you need help, check how it was done on HQ on previous steps
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.
CM Administration > System > Location info > Location, click on HQ location
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Validation
Task.- Make a phone call from BRA1 to HQ PHONE
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
|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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
|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
|ProvideOutsideDialtone=false
|AllowDeviceOverride=false
|IsEmergencyNumber=false
|ResourcePriorityNamespace=
|PatternRouteClass=RouteClassDefault
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
|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
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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}
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
|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
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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=1 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}
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)
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
00868355.007 |18:10:13.895 |Created | |
|StationCdpc(1,100,67,147) |StationD(1,100,66,6) |
|NumOfCurrentInstances: 2
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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}
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
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]
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
00868366.000 |18:10:13.895 |SdlSig |LBMRegisterRes |wait
|ReservationMgr(1,100,113,1) |LBMInterface(1,100,180,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= 29835980
Branch= 0 Status=2 vCall=F DevicecontrolPid=1,100,66,6 DeviceCdpcPid=1,100,67,147
LBMCACReturnInfo: lbmReservedKbps=24 locationIsPhantom=F bwPreemption=F
00868367.001 |18:10:13.895 |AppInfo |RegionsServer - modeA =[0], modeB =[0], preferredIpType =[0]
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
00868368.005 |18:10:13.896 |AppInfo |MRM::getRsvpDeviceGivenMrgl GETTING MTP FROM DEFAULT
LIST
MediaResourceType : 9
ClusterID : Cluster1
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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.
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis
And now that we are fill with success and in the mood for memes of Forest Gumps…
SAF_FORWARDER_1#term mon
Nov 25 18:45:27.451: RSVP-PROXY-MERGE: No existing CAC proxy matches with the proxy being
installed, no need to merge
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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: Allocating handle entry 1/2. Type: 15, instance cnt: 30, handle_count is now
3
Nov 25 18:45:27.455: RSVP: Allocating handle entry 1/6. Type: 2, instance cnt: 13, handle_count is now
4
Nov 25 18:45:27.455: RSVP: Allocating handle entry 1/5. Type: 2, instance cnt: 14, handle_count is now
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-DB: A new (unicast) pfc is being added for GigabitEthernet0/1
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.455: RSVP: Allocating handle entry 1/6. Type: 3, instance cnt: 14, handle_count is now
5
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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: Allocating handle entry 1/11. Type: 9, instance cnt: 24, handle_count is now
6
Nov 25 18:45:27.455: RSVP: Allocating handle entry 1/9. Type: 15, instance cnt: 28, handle_count is now
7
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.455: RSVP-PROXY: rsvp_proxy_rxsb_to_signalling: do it!
Nov 25 18:45:27.455: RSVP: Allocating handle entry 1/8. Type: 4, instance cnt: 26, handle_count is now
8
Nov 25 18:45:27.459: RSVP: Freeing handle 1/8. Type: 4, instance cnt: 26, handle_count is now 7
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.459: 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.459: RSVP: Triggering outgoing Path due to incoming Path change or new Path
Nov 25 18:45:27.463: RSVP: Allocating handle entry 1/8. Type: 2, instance cnt: 27, handle_count is now
8
Nov 25 18:45:27.463: RSVP: Freeing handle 1/8. Type: 2, instance cnt: 27, handle_count is now 7
Nov 25 18:45:27.467: RSVP: Allocating handle entry 1/8. Type: 2, instance cnt: 28, handle_count is now
8
Nov 25 18:45:27.467: RSVP: Allocating handle entry 1/4. Type: 2, instance cnt: 15, handle_count is now
9
Nov 25 18:45:27.467: RSVP-DB: Could not get info for tunnel GigabitEthernet0/1
Nov 25 18:45:27.467: RSVP: Freeing handle 1/8. Type: 2, instance cnt: 28, handle_count is now 8
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.467: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: POLICY-COPS -
COPS query for Path message
Nov 25 18:45:27.471: RSVP: Allocating handle entry 1/8. Type: 4, instance cnt: 29, handle_count is now
9
Nov 25 18:45:27.471: RSVP: Allocating handle entry 1/10. Type: 4, instance cnt: 14, handle_count is now
10
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.471: RSVP: 192.168.13.241_20402->192.168.13.242_16416[0.0.0.0]: POLICY-COPS -
query for Resv message
Nov 25 18:45:27.471: RSVP: Allocating handle entry 1/12. Type: 5, instance cnt: 24, handle_count is now
11
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: Freeing handle 1/8. Type: 4, instance cnt: 29, handle_count is now 10
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.471: RSVP: session [TBD]
Nov 25 18:45:27.471: RSVP: Allocating handle entry 1/8. Type: 4, instance cnt: 30, handle_count is now
11
Nov 25 18:45:27.471: RSVP: Allocating handle entry 1/7. Type: 4, instance cnt: 31, handle_count is now
12
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:27.471: RSVP: 192.168.13.242_16416->192.168.13.241_20402[0.0.0.0]: RSVP-POLICY -
forward outgoing message
Nov 25 18:45:27.471: RSVP: Allocating handle entry 1/3. Type: 6, instance cnt: 31, handle_count is now
13
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: Freeing handle 1/8. Type: 4, instance cnt: 30, handle_count is now 12
Nov 25 18:45:27.475: RSVP: Allocating handle entry 1/8. Type: 4, instance cnt: 31, handle_count is now
13
Nov 25 18:45:27.475: RSVP: Freeing handle 1/13. Type: 4, instance cnt: 15, handle_count is now 13
Nov 25 18:45:27.475: RSVP: Freeing handle 1/8. Type: 4, instance cnt: 31, handle_count is now 12
Nov 25 18:45:28.935: RSVP: Allocating handle entry 1/8. Type: 9, instance cnt: 32, handle_count is now
13
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:28.939: RSVP: session 192.168.13.242_16416[0.0.0.0]: Received Resv message from
127.0.0.1 (on receiver host)
Nov 25 18:45:28.939: RSVP: Allocating handle entry 1/13. Type: 4, instance cnt: 16, handle_count is now
14
Nov 25 18:45:28.939: RSVP: Freeing handle 1/13. Type: 4, instance cnt: 16, handle_count is now 13
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:28.939: RSVP-PROXY:rsvp_proxy_rxsb_swap_handles: handle1=402654219
handle2=536871944
Nov 25 18:45:28.939: RSVP: Freeing handle 1/8. Type: 9, instance cnt: 32, handle_count is now 12
Nov 25 18:45:28.943: RSVP: Allocating handle entry 1/8. Type: 4, instance cnt: 33, handle_count is now
13
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:28.943: RSVP: Allocating handle entry 1/13. Type: 4, instance cnt: 17, handle_count is now
14
Nov 25 18:45:28.947: RSVP: Freeing handle 1/8. Type: 4, instance cnt: 34, handle_count is now 12
Nov 25 18:45:37.683: RSVP: Allocating handle entry 1/8. Type: 7, instance cnt: 35, handle_count is now
13
Nov 25 18:45:37.683: RSVP: rsvp_rmsg_enable_for_tmb, Enabled Reliable Messaging for this tmb
(0x23000408)
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:37.687: 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
Nov 25 18:45:37.687: RSVP: Freeing handle 1/8. Type: 7, instance cnt: 35, handle_count is now 12
Nov 25 18:45:37.687: RSVP: Freeing handle 1/3. Type: 6, instance cnt: 31, handle_count is now 11
Nov 25 18:45:37.687: RSVP: Freeing handle 1/7. Type: 4, instance cnt: 31, handle_count is now 10
SAF_FORWARDER_1#
SAF_FORWARDER_1#
SAF_FORWARDER_1#on=2
Nov 25 18:45:37.687: RSVP: Freeing handle 1/6. Type: 3, instance cnt: 14, handle_count is now 9
Nov 25 18:45:37.687: RSVP: Freeing handle 1/5. Type: 2, instance cnt: 14, handle_count is now 8
Nov 25 18:45:37.687: RSVP: Freeing handle 1/1. Type: 8, instance cnt: 29, handle_count is now 7
Nov 25 18:45:37.687: RSVP: Freeing handle 1/2. Type: 15, instance cnt: 30, handle_count is now 6
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:37.687: RSVP: Allocating handle entry 1/2. Type: 7, instance cnt: 31, handle_count is now
7
Nov 25 18:45:37.691: RSVP: rsvp_rmsg_enable_for_tmb, Enabled Reliable Messaging for this tmb
(0x1F000402)
Nov 25 18:45:37.691: RSVP: Freeing handle 1/2. Type: 7, instance cnt: 31, handle_count is now 6
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)
Nov 25 18:45:37.691: RSVP: Allocating handle entry 1/2. Type: 4, instance cnt: 32, handle_count is now
7
Nov 25 18:45:37.691: RSVP: Freeing handle 1/2. Type: 4, instance cnt: 32, handle_count is now 6
Nov 25 18:45:37.691: RSVP: Freeing handle 1/12. Type: 5, instance cnt: 24, handle_count is now 5
Nov 25 18:45:37.691: RSVP: Freeing handle 1/10. Type: 4, instance cnt: 14, handle_count is now 4
Nov 25 18:45:37.691: RSVP: Freeing handle 1/11. Type: 9, instance cnt: 24, handle_count is now 3
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
Nov 25 18:45:37.691: RSVP: Allocating handle entry 1/11. Type: 7, instance cnt: 25, handle_count is now
4
Nov 25 18:45:37.691: RSVP: rsvp_rmsg_enable_for_tmb, Enabled Reliable Messaging for this tmb
(0x1900040B)
Nov 25 18:45:37.691: RSVP: Freeing handle 1/4. Type: 2, instance cnt: 15, handle_count is now 3
Nov 25 18:45:37.691: RSVP: Freeing handle 1/11. Type: 7, instance cnt: 25, handle_count is now 2
Nov 25 18:45:37.691: RSVP: Freeing handle 1/9. Type: 15, instance cnt: 28, handle_count is now 1
Nov 25 18:45:37.695: RSVP: Allocating handle entry 1/9. Type: 15, instance cnt: 29, handle_count is now
2
Nov 25 18:45:37.695: RSVP: Allocating handle entry 1/11. Type: 7, instance cnt: 26, handle_count is now
3
Nov 25 18:45:37.695: RSVP: rsvp_rmsg_enable_for_tmb, Enabled Reliable Messaging for this tmb
(0x1A00040B)
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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: Freeing handle 1/11. Type: 7, instance cnt: 26, handle_count is now 2
Nov 25 18:45:37.695: RSVP: Freeing handle 1/9. Type: 15, instance cnt: 29, handle_count is now 1
SAF_FORWARDER_1#
SAF_FORWARDER_1#
SAF_FORWARDER_1#
RTMT
Go to RTMT > Performance > CUCM Node > Cisco Location LBM > “Select what ever you need”
Facebook Group
CCNA CCNP CCIE Collaboration - Study Group - Alexis
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
CCNA CCNP CCIE Collaboration - Study Group - Alexis