Medianet Reference Guide - Cisco

More documents

Recommendations

Info

Application-Specific Management Functionality Chapter 6 Medianet Management and Visibility Design Considerations Table 6-4 Cisco TelePresence Application-Specific Management Functionality (continued) Accounting management Performance management Security management • The Cisco TelePresence System web-based GUI provides access to statistics for ongoing calls, or the previous call if the Cisco TelePresence System endpoint is currently not in a call. Accounting management statistics include the call start time, duration of the call, remote number, bit rate, and the number of packets and bytes transmitted and received during the call. These statistics are also available via an SSH CLI as well as through SNMP. • The Cisco TelePresence System web-based GUI provides access to statistics for ongoing calls, or the previous call if the Cisco TelePresence System endpoint is currently not in a call. Performance management statistics include parameters such as packet loss, latency, jitter, and out-of-order packets for audio and video media streams. These can be used to assess the performance of the network infrastructure in meeting service level agreements. These statistics are also available via SNMP through the CISCO-TELEPRESENCE-CALL-MIB. • An IP service level agreements (IPSLA) responder within the Cisco TelePresence System endpoint can be enabled, allowing the Cisco TelePresence System endpoint to respond to packets sent by an IPSLA initiator. IPSLA can be used to pre-assess network performance before commissioning the Cisco TelePresence System endpoint onto a production network, or used to assess ongoing network performance or when troubleshooting. • Access control to the individual Cisco TelePresence System endpoints is currently handled via a local database, although the userid and password used for access control are centrally managed via the configuration within the Cisco Unified Communications Manager Administration web-based GUI. • SNMP notifications can be set on the Cisco TelePresence System endpoint to alert after failed access control attempts. Note Both static location-based admission control and RSVP are considered part of performance management within this document, because the scheduling of resources is not done per end user, but to ensure that necessary resources are allocated to meet service level requirements. Cisco TelePresence Manager From a management perspective, the primary functions of Cisco TelePresence Manager are resource allocation, which is part of accounting management; and fault detection, which is part of fault management. Cisco TelePresence Manager allocates Cisco TelePresence System endpoints (meeting rooms) and Cisco TelePresence Multipoint Switch segment resources based on meetings scheduled by end users through an e-mail/calendaring system such as Microsoft Exchange or IBM Lotus Domino. Note that the Cisco TelePresence Manager has no knowledge of the underlying IP network infrastructure, and therefore has no ability to schedule any network resources or provide Call Admission Control (CAC) to ensure that the TelePresence call goes through during the scheduled time. Figure 6-27 shows an example of the resource scheduling functionality of Cisco TelePresence Manager. 6-70 Medianet Reference Guide OL-22201-01
Chapter 6 Medianet Management and Visibility Design Considerations Application-Specific Management Functionality Figure 6-27 Cisco TelePresence Manager Resource Scheduling IP Phone IP CTS Codec Primary CTMS CUCM M CTS-MAN Enail/Calendaring Server User CTS-MAN discovers and monitors CTS systems in CUCM via AXL/SOAP and JTAPI CTS-MAN sends the meeting details to the CTMS CTS-MAN validates rooms in the directory server and pulls room schedules from the email/calendaring server CTS-MAN reads the event in room mailboxes User schedules meeting rooms via email/calendaring server Primary codec pushes XML content to the phone in the room User now has a “Single Button to Push”to join the meeting CTS-MAN pushes XML content to the primary codec of the CTS endpoints CTS-MAN sends meeting confirmation to the user via email 228403 Cisco TelePresence Manager periodically queries the e-mail/calendaring system to determine whether an end user has scheduled TelePresence rooms for an upcoming meeting. Having previously synchronized the TelePresence rooms defined within the Cisco Unified Communications Manager database with the TelePresence rooms defined within the e-mail/calendaring system database, the Cisco TelePresence Manager then pushes the meeting schedule the IP Phone associated with each TelePresence room. If a multipoint meeting has been scheduled by the end user, the Cisco TelePresence Manager selects an appropriate Cisco TelePresence Multipoint Switch for the meeting, and schedules the necessary resources for the meeting. The Cisco TelePresence Multipoint Switch then updates the end user via an e-mail confirmation. Note In Figure 6-27 and throughout this chapter, the CTS codec and associated IP phone together are considered the CTS endpoint. The IP phone shares the same dial extension as the CTS codec, is directly connected to it, and is used to control TelePresence meetings. The other primary management function of the Cisco TelePresence Manager is fault detection. Cisco TelePresence Manager includes the ability to centrally view error conditions in the various components of a Cisco TelePresence deployment. It also allows you to view error conditions that resulted in the failure of scheduled meetings. Figure 6-28 shows an example of the Cisco TelePresence Manager screen used to view the status of Cisco TelePresence System endpoints. OL-22201-01 Medianet Reference Guide 6-71
Page 1 and 2:
Medianet Reference Guide Last Updat
Page 3:
About the Authors Solution Authors
Page 6 and 7:
Contents Application Intelligence a
Page 8 and 9:
Contents The Globalization of the W
Page 10 and 11:
Contents NetFlow Collector Consider
Page 12 and 13:
Contents viii Medianet Reference Gu
Page 14 and 15:
Business Drivers for Media Applicat
Page 16 and 17:
Business Drivers for Media Applicat
Page 18 and 19:
Challenges of Medianets Chapter 1 M
Page 20 and 21:
Challenges of Medianets Chapter 1 M
Page 22 and 23:
Solution Chapter 1 Medianet Archite
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Conclusions Chapter 1 Medianet Arch
Page 48 and 49:
Related Documents Chapter 1 Mediane
Page 50 and 51:
Related Documents Chapter 1 Mediane
Page 52 and 53:
Measuring Bandwidth Chapter 2 Media
Page 54 and 55:
Packet Flow Malleability Chapter 2
Page 56 and 57:
Shapers Chapter 2 Medianet Bandwidt
Page 58 and 59:
Shapers versus Policers Chapter 2 M
Page 60 and 61:
Shapers versus Policers Chapter 2 M
Page 62 and 63:
Converged Video Chapter 2 Medianet
Page 64 and 65:
Bandwidth Over Subscription Chapter
Page 66 and 67:
Capacity Planning Chapter 2 Mediane
Page 68 and 69:
Load Balancing Chapter 2 Medianet B
Page 70 and 71:
EtherChannel Chapter 2 Medianet Ban
Page 72 and 73:
Bandwidth Conservation Chapter 2 Me
Page 74 and 75:
Summary Chapter 2 Medianet Bandwidt
Page 76 and 77:
Network Availability Chapter 3 Medi
Page 78 and 79:
Network Availability Chapter 3 Medi
Page 80 and 81:
Device Availability Technologies Ch
Page 82 and 83:
Device Availability Technologies Ch
Page 84 and 85:
Network Availability Technologies C
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Operational Availability Technologi
Page 106 and 107:
Summary Chapter 3 Medianet Availabi
Page 108 and 109:
Drivers for QoS Design Evolution Ch
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Cisco QoS Toolset Chapter 4 Mediane
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Enterprise Medianet Strategic QoS R
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
References Chapter 4 Medianet QoS D
Page 154 and 155:
References Chapter 4 Medianet QoS D
Page 156 and 157:
An Introduction to Securing a Media
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Medianet Security Reference Documen
Page 168 and 169:
Medianet Security Reference Documen
Page 170 and 171:
Network-Embedded Management Functio
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Cisco Network Analysis Module Chapt
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189: Cisco Network Analysis Module Chapt
Page 234 and 235: Application-Specific Management Fun
Page 250 and 251: Summary Chapter 6 Medianet Manageme
Page 252 and 253: Auto Smartports Chapter 7 Medianet
Page 276 and 277: Location Services Chapter 7 Mediane
Page 278 and 279: Summary Chapter 7 Medianet Auto Con
Page 280: References Chapter 7 Medianet Auto
show all

Medianet Reference Guide - Cisco

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?